CN116028981A - Block chain-based data processing method and related equipment - Google Patents
Block chain-based data processing method and related equipment Download PDFInfo
- Publication number
- CN116028981A CN116028981A CN202111242740.2A CN202111242740A CN116028981A CN 116028981 A CN116028981 A CN 116028981A CN 202111242740 A CN202111242740 A CN 202111242740A CN 116028981 A CN116028981 A CN 116028981A
- Authority
- CN
- China
- Prior art keywords
- data
- owner
- sensitive hash
- ownership
- blockchain
- 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.)
- Pending
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present disclosure provides a data processing method and related device based on a blockchain, wherein a target blockchain system stores local sensitive hash digests of a plurality of data and rights relations between each local sensitive hash digest and data owners of corresponding data, and the method includes: receiving an ownership right confirming request for first data sent by a data verification party, wherein the ownership right confirming request carries a first local sensitive hash abstract of the first data, and the first local sensitive hash abstract is obtained after local sensitive hash processing is carried out on the first data; matching the first local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining second data with similarity greater than a first threshold value with the first data in the plurality of data; determining a second data owner having second data according to the rights relation; it is determined that the second data owner owns the ownership of the first data.
Description
Technical Field
The disclosure relates to the technical field of computers and the internet, in particular to a data processing method and device based on a blockchain, electronic equipment and a computer readable storage medium.
Background
With the advent of the big data age, the potential value of data is being developed and exploited. Since data is an important asset of an enterprise, the data validation problem is necessarily involved in the transaction and circulation process. The validation of data rights can ensure that digital assets of businesses and individuals are not illegally infringed, while the definition of data rights and responsibilities can also ensure traceability of fraudulent or illegal data transactions. Data validation has been one of the challenges facing large data transactions, and data validation has been related to the development of data markets and the development and utilization of data value.
The data right is mainly aimed at data from different sources, and the property rights of the data are definitely attributed through means such as technology and law, so that data integration is promoted, data sharing and circulation are accelerated, transaction cost is reduced, and data asset value is activated. Traditional data validation is mainly in a mode of submitting ownership evidence and expert review, but the fairness of the right validation result cannot be guaranteed by the method.
Disclosure of Invention
The disclosure aims to provide a data processing method, a device, an electronic device and a computer readable storage medium based on a blockchain, wherein the fairness of right confirmation can be ensured by confirming a data owner of first data through a blockchain system.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.
The embodiment of the disclosure provides a data processing method based on a blockchain, which comprises the following steps: receiving an ownership right request for first data sent by a data verification party, wherein the ownership right request carries a first local sensitive hash abstract of the first data, and the first local sensitive hash abstract is obtained after local sensitive hash processing is carried out on the first data; matching the first locally sensitive hash digest with a locally sensitive hash digest of a plurality of data stored in the blockchain system, and determining second data with similarity to the first data being greater than a first threshold value from the plurality of data; determining a second data owner having the second data according to the rights relation; determining that the second data owner owns ownership of the first data.
In some embodiments, prior to receiving the ownership right request for the first data sent by the data verifier, the method further comprises: receiving a data right confirmation transaction sent by the second data owner for the second data, wherein the data right confirmation transaction carries a second local sensitive hash abstract corresponding to the second data; matching the second locally sensitive hash digest with the locally sensitive hash digests of the plurality of data stored in the blockchain system, and determining that data with similarity exceeding a second threshold value with the second data does not exist in the plurality of data in the target blockchain system; determining that the second locality sensitive hash digest has a rights relationship with the second data owner; and carrying out uplink storage on the second local sensitive hash digest and the ownership of the second data owner so as to determine that the second data owner owns the ownership of the second data.
In some embodiments, the method further comprises: matching the second local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining that data with similarity to the second data exceeding the second threshold exists in the plurality of data in the target blockchain system; and sending a data right confirming transaction failure prompt to the second data owner to prompt the second data owner that the second data has been confirmed.
In some embodiments, the data validator is a data demander; wherein, before receiving the ownership right request for the first data sent by the data verification party, the method further comprises:
receiving a data demand request sent by the data demand party; broadcasting the data demand request to each node in the target blockchain, the each node including a first node controlled by a first data owner; receiving a data providing response sent by the first data owner in response to the data demand request by the first node, wherein the data providing response carries a first data interface; and sending a data providing response sent by the data owner to the data demander so that the data demander can acquire the first data according to the first data interface.
In some embodiments, the data demand request carries a data demand specification; matching the first locally sensitive hash digest with the locally sensitive hash digests of a plurality of data stored in the blockchain system, determining second data with similarity greater than a first threshold value with the first data in the plurality of data, including: determining whether the first data meets the data requirement specification; if the first data meets the data requirement specification, matching the first local sensitive hash digest with local sensitive hash digests of a plurality of data stored in the blockchain system, and determining second data with similarity greater than a first threshold value with the first data in the plurality of data; and if the first data does not meet the data requirement specification, sending a risk prompt that the data does not meet the requirement to the data requirement party.
In some embodiments, the data demand request carries a data demand specification; wherein after broadcasting the data demand request to each node in the target blockchain, before receiving, by the first node, a data provision response sent by the first data owner in response to the data demand request, the data provision response carrying a first data interface, the method further comprises: receiving, by the first node, data description information for first data sent by the first data owner in response to the data requirement specification; transmitting data description information for the first data to the data demander so that the data demander determines whether the first data meets the requirement of the data requirement specification; receiving response information of the data demand side for the data description information of the first data; and sending the response information to the first data owner, so that the first data owner responds to the data demand request to send a data providing response carrying the first data interface.
In some embodiments, prior to receiving the ownership right request for the first data sent by the data verifier, the method further comprises: receiving a registration request sent by the second data owner, wherein the registration request carries a registration public key; responding to the registration request, and sending an identity attribute information acquisition request encrypted by the registration public key to the second data owner; receiving an identity attribute information response sent by the second data owner and encrypted by the registration public key, wherein the identity attribute information response carries the identity attribute information of the second data owner and the public key of the second data owner; binding the second data owner with identity attribute information corresponding to the second data owner, and generating an identity certificate for the second data owner; and the identity attribute information and the identity certificate are subjected to uplink processing so as to verify the identity of the second data owner when the second data owner confirms the transaction for the second data sending data right.
The embodiment of the disclosure provides a data processing device based on a blockchain, which comprises: the system comprises an ownership right request acquisition module, a summary matching module, a data owner determining module and an ownership relation determining module.
The ownership right request acquisition module is used for receiving an ownership right request for first data sent by a data verification party, wherein the ownership right request carries a first local sensitive hash abstract of the first data, and the first local sensitive hash abstract is obtained after local sensitive hash processing is carried out on the first data; the digest matching module may be configured to match the first locally sensitive hash digest with a locally sensitive hash digest of a plurality of data stored in the blockchain system, and determine, from the plurality of data, second data having a similarity with the first data greater than a first threshold; the data owner determination module may be configured to determine a second data owner having the second data based on the ownership; the ownership determination module may be configured to determine that the second data owner owns ownership of the first data.
The embodiment of the disclosure provides an electronic device, which comprises: one or more processors; a storage means for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the blockchain-based data processing method of any of the above.
The disclosed embodiments provide a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a blockchain-based data processing method as set forth in any of the above.
Embodiments of the present disclosure propose a computer program product or a computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions to cause the computer device to perform the blockchain-based data processing method described above.
According to the data processing method, the device, the electronic equipment and the computer readable storage medium based on the blockchain, on one hand, the local sensitive hash abstract corresponding to the data is bound with the data owner of the data on the blockchain to realize the confirmation and reservation of the rights relation, the data are fairly and equitably subjected to the right confirmation processing, and in the use process of the first data, the data owner with the first data ownership can be fairly confirmed, so that the fairness of the data right confirmation is improved, and the efficiency of the data right confirmation is also improved; on the other hand, in the technical scheme provided by the disclosure, in the process of data right request and data right confirmation, the data can be expressed through the local sensitive hash digest of the data so as to express similar data as the same local sensitive hash digest, and further, the similar data can be found timely, the situation that the similar data cannot be compared and analyzed due to overlarge data is avoided, and further, illegal attackers can be prevented from infringing the data after modifying the data.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
FIG. 1 is a schematic diagram of a block chain based data processing system according to an embodiment of the present disclosure.
Fig. 2 is a schematic diagram of a blockchain network provided by embodiments of the present disclosure.
Fig. 3 is a schematic block diagram according to an embodiment of the disclosure.
Fig. 4 is a schematic diagram of a new block generation process provided by an embodiment of the present disclosure.
Fig. 5 is a diagram illustrating a method of node registration according to an example embodiment.
FIG. 6 is a flowchart illustrating a blockchain-based data processing method in accordance with an exemplary embodiment.
Fig. 7 is a flow chart illustrating a method of data validation processing according to an example.
Fig. 8 is a flow chart illustrating a method of data acquisition according to an exemplary embodiment.
Fig. 9 is a schematic diagram of a data validation structure, according to an example embodiment.
FIG. 10 is a block diagram illustrating a blockchain-based data processing device in accordance with an exemplary embodiment.
Fig. 11 shows a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted.
The described features, structures, or characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. However, those skilled in the art will recognize that the aspects of the present disclosure may be practiced with one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.
The drawings are merely schematic illustrations of the present disclosure, in which like reference numerals denote like or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and not necessarily all of the elements or steps are included or performed in the order described. For example, some steps may be decomposed, and some steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
In the present specification, the terms "a," "an," "the," "said" and "at least one" are used to indicate the presence of one or more elements/components/etc.; the terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements/components/etc., in addition to the listed elements/components/etc.; the terms "first," "second," and "third," etc. are used merely as labels, and do not limit the number of their objects.
In order that the above-recited objects, features and advantages of the present invention can be more clearly understood, a more particular description of the invention will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings, it being understood that the embodiments and features of the embodiments may be combined with each other without conflict.
The disclosed embodiments relate to blockchain (or blockchain) technology, which is a novel application mode of computer technology such as distributed data storage, peer-to-Peer (P2P) transmission, consensus mechanism, encryption algorithm, etc., and is essentially a decentralised database, which is a series of data blocks generated by association using a cryptography method, and each data block contains information of a batch of network transactions for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product service layer, and an application service layer; the blockchain may be composed of a plurality of serial transaction records (also known as blocks) that are cryptographically concatenated and protected from content, and the distributed ledgers concatenated by the blockchain enable multiple parties to effectively record transactions and permanently verify the transactions (non-tamperable). The common recognition mechanism is a mathematical algorithm for establishing trust and obtaining rights among different nodes in the block chain system, namely the common recognition mechanism is a mathematical algorithm commonly recognized by all network nodes of the block chain.
As shown in fig. 1, a blockchain-based data processing system provided by an embodiment of the present disclosure may include a blockchain system 100 and a plurality of terminal devices, in fig. 1, three terminal devices are taken as an example, a first terminal 201, a second terminal 202, and a third terminal 203, respectively. Wherein the first terminal 201, the second terminal 202, and the third terminal 203 may be used to obtain transaction data (including transaction data generated by a transaction request or by executing a transaction request) from the blockchain system, or upload transaction data to the blockchain system.
As shown in fig. 2, the blockchain system 100 in the embodiment of fig. 1 may include a plurality of node devices 101, where the plurality of node devices 101 may refer to clients in the blockchain system, and the blockchain system 100 refers to a system for performing data sharing between the node devices 101 and the node devices 101. Each node device 101 may receive transaction data while operating normally and maintain shared data within the blockchain system 100 based on the received transaction data. To ensure interworking of information within the blockchain system 100, there may be an information connection between each node device 101 in the blockchain system 100, through which information may be transferred between the node devices 101. For example, when any node device 101 in the blockchain system 100 receives transaction data, other node devices 101 in the blockchain system 100 acquire the transaction data according to a consensus algorithm, and store the transaction data as data in shared data, so that the data stored on all node devices 101 in the blockchain system 100 are consistent.
The node device 101, the first terminal 201, the second terminal 202, and the third terminal 203 in the blockchain system 100 may be any electronic device, including but not limited to a mobile phone, a tablet computer, a notebook computer, a palm computer, a smart sound, a mobile internet device (mobile internet device, MID), a POS (Point Of sale) machine, a wearable device (e.g., a smart watch, a smart bracelet, etc.); the system can also be a stand-alone server, or a server cluster formed by a plurality of servers, or a cloud computing center.
For each node device 101 in the blockchain system 100, there is a node device identification corresponding thereto, and each node device 101 in the blockchain system 100 may store the node device identifications of other node devices 101 in the blockchain system 100 for subsequent broadcasting of the generated block to other node devices 101 in the blockchain system 100 according to the node device identifications of the other node devices 101. Each node device 101 may maintain a node device identifier list as shown in table 1 below, and store the node device name and the node device identifier in the node device identifier list. The node device identifier may be an IP (Internet Protocol, protocol of interconnection between networks) address, and any other information that can be used to identify the node device, and table 1 is only illustrated by taking an IP address as an example. Wherein N is a positive integer greater than or equal to 1.
TABLE 1
Node name | Node identification |
Node 1 | 117.114.151.174 |
Node 2 | 117.116.189.145 |
… | … |
Node N | 119.123.789.258 |
Each node device 101 in the blockchain system 100 stores one and the same blockchain. The blockchain is composed of a plurality of blocks, each block contains a cryptographic hash (which can be represented by a hash value calculated by the merck tree) algorithm, a corresponding timestamp, and transaction data, and the design makes the content of the block difficult to tamper with.
Referring to fig. 3, the blockchain is composed of a plurality of blocks, the starting block comprises a block head and a block main body, the block head stores transaction data characteristic values, version numbers, time stamps and difficulty values, and the block main body stores transaction data; the next block of the starting block takes the starting block as a father block, the next block also comprises a block head and a block main body, the block head stores transaction data characteristic values of the current block, block head characteristic values, version numbers, time stamps and difficulty values of the father block, and the like, so that the block data stored in each block in the block chain are associated with the block data stored in the father block, and the security of the transaction data in the block is ensured.
When each block in the blockchain is generated, referring to fig. 4, when node equipment where the blockchain is located receives transaction data, checking the transaction data, after the checking is completed, storing the transaction data into a memory pool, and updating a hash tree used for recording the transaction data; and then updating the updating time stamp to the time of receiving the transaction data, trying different random numbers, and calculating the characteristic value for a plurality of times, so that the calculated characteristic value can meet the following formula:
SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))<TARGET (1)
Wherein SHA256 is a eigenvalue algorithm used to calculate eigenvalues; version (version number) is version information of the related block protocol in the block chain; the prev_hash is the block header characteristic value of the parent block of the current block; the merkle_root is a characteristic value of transaction data; ntime is the update time of the update timestamp; the nbits is the current difficulty, is a fixed value in a period of time, and is determined again after exceeding a fixed period of time; x is a random number; TARGET is a eigenvalue threshold that can be determined from nbits.
Thus, when the random number meeting the formula is calculated, the information can be correspondingly stored to generate the block head and the block main body, and the current block is obtained. And then, the node equipment of the block chain respectively sends the newly generated blocks to other node equipment in the block chain system 100 according to the node equipment identifications of other node equipment in the block chain system 100, the other node equipment checks the newly generated blocks, and the newly generated blocks are added into the block chain stored in the block chain after the checking is completed.
Fig. 5 is a diagram illustrating a method of node registration according to an example embodiment.
Node registration may be performed in a blockchain system with reference to fig. 5 prior to performing the embodiments described below. The nodes in the embodiment shown in fig. 5 may be nodes corresponding to the data demander, may be nodes corresponding to the data owner, or may be nodes corresponding to the data supervisor, which is not limited in this disclosure.
Wherein, the data demander may refer to an object that needs to obtain the right to use the data. The data owner may refer to an object that requires an authorization operation (request to confirm ownership, use, or disposition of a certain data) in the blockchain system to obtain ownership, use, or disposition of the data, and the data supervisor may refer to a third party authority, such as a public inspection authority having administrative authority on the data, or a corporate high-level management authority, etc., to which the present disclosure is not limited.
Wherein the identities of the data demander, the data owner and the data supervisor can be interchanged. Meanwhile, one object can be a data requiring party, a data all party and a data supervising party, and the disclosure is not limited to this.
Referring to fig. 5, the above-described node registration method may include the following steps. 1. The blockchain 504 receives a registration request from a user (e.g., the data demander 501, the data owner 502, or the data supervisor 503), the registration request carrying a registration public key (issued by the blockchain 504 for registration by the user or node) and a user ID; 2. the blockchain 504 sends an identity attribute information acquisition request encrypted by a registration public key to a user in response to the registration request; 3. the user obtains the user public key userPK and the user private key ueseSK and sends the user public key userPK and the user private key ueseSK to the blockchain 504. 4. The blockchain 504 receives an identity attribute information response sent by the second data owner and encrypted by the registration public key, wherein the identity attribute information response carries the identity attribute information of the user and the user public key; 5. the blockchain 504 binds the user ID with the identity attribute information corresponding to the user and generates an identity certificate userCert for the user; 6. blockchain 504 performs a process of linking the identity attribute information and the identity credential to verify the identity of the second user when the second user confirms the transaction for the second data transmission data ownership and returns the user credential to the user.
Through the steps, each user can finish node registration so as to initiate a data right confirmation request, a data demand request or a data ownership confirmation request to the blockchain later.
Fig. 6 is a flowchart illustrating a blockchain-based data processing method, which may be performed by a target node in a target blockchain system, where a locally sensitive hash digest of a plurality of data and a ownership of each locally sensitive hash digest and a data owner of corresponding data are stored in the target blockchain system, and a process of a locally sensitive hash digest of a plurality of data and a chaining of ownership of each locally sensitive hash digest and a data owner of corresponding data may be specifically referred to the embodiment shown in fig. 7, which is not repeated in this embodiment.
Referring to fig. 6, a blockchain-based data processing method provided by an embodiment of the present disclosure may include the following steps.
Step S602, receiving an ownership right request for the first data sent by the data verifier, where the ownership right request carries a first locally sensitive hash digest of the first data, and the first locally sensitive hash digest is obtained after performing a locally sensitive hash process on the first data.
Where data ownership may refer to having possession, dominance, use, benefit, and disposition of certain data. An ownership right request for first data may refer to a request to confirm who the data owner owning the first data is.
In some embodiments, a data verifier may refer to an object that requires verification from the blockchain of a data owner requesting some data. Any object having authentication rights can be the data authenticator of the present embodiment.
In some embodiments, during the process of a data supervisor (a data verifier) supervising first data, the data supervisor may initiate a data ownership request for the first data to the blockchain system; when a certain data owner (a data verifier) finds that some objects are using first data, and the first data is similar to data which is already authenticated on a chain, a data ownership right-confirming request for the first data can be initiated to a blockchain system, so that when the blockchain considers that the owner of the first data is self, an infringement litigation is initiated to the objects; also, when a data requesting party (a data verifier) obtains first data from an object, a data ownership right request for the first data may be initiated like a blockchain system to confirm whether the object has ownership of the first data, etc. The present disclosure does not limit an application scenario of the ownership right request for the first data sent by the data verifier.
Basic idea of locality sensitive hashing LSH processing: after two adjacent data in the high-dimensional data space are mapped into the low-dimensional data space, the two adjacent data have high probability of being adjacent; while two data that are not originally adjacent will have a high probability of not being adjacent in a low dimensional space. By such a mapping, we can find neighboring data points in the low-dimensional data space, avoiding finding in the high-dimensional data space, which can be time consuming. Therefore, through the local sensitive hash LSH processing, two originally similar data can be mapped into the same hash value to a great extent, and further if the same hash digest is obtained after two different data are processed through the local sensitive hash LSH, the similarity of the two data can be considered to be very high.
In step S604, the first locally sensitive hash digest is matched with the locally sensitive hash digests of the plurality of data stored in the blockchain system, and second data having a similarity with the first data greater than a first threshold is determined from the plurality of data.
In some embodiments, a locally sensitive hash digest of a plurality of data may be stored in advance in a blockchain system, and a data owner is bound to the locally sensitive hash digest of the data to indicate that the data owner has ownership of the locally sensitive hash digest. For example, if the target object has ownership of the target data, the blockchain system may bind the target object to the locally sensitive hash digest of the target data to indicate that the target data is owned by the target object.
In some embodiments, the locally sensitive hash digests of the more highly similar data may be identical after processing by the local hash digests. Therefore, by matching the locally sensitive hash digests, whether the data similar to the first data exists in the blockchain system can be simply and conveniently determined. The first data, if any, may be considered similar to the already-authorized data in the blockchain. I.e. the first data may be the already-authorized data or may be generated by simply tampering with the already-authorized data, then the first data should also be owned by the data owner of the similar data.
Thus, if the second data having a similarity with the first data greater than the first threshold value is determined among the plurality of data by the first locality-sensitive hash digest, it can be considered that the data owner of the second data also has ownership of the first data.
Step S606, determining a second data owner having the second data according to the ownership.
In some embodiments, the blockchain has bound the data owner to the data it owns through a sensitive hash digest, so the data owner of the second data—the second data owner, can be determined by the ownership.
Step S608, determining that the second data owner owns the ownership of the first data.
Since the locality-sensitive hash of the first data is the same as the locality-sensitive hash of the second data, the similarity between the first data and the second data is also greater than the preset threshold, so that the first data can be considered to be obtained after a simple modification (or no modification at all) to the second data, and thus the second data owner should also have ownership of the first data.
The block chain technology is a technical scheme which does not depend on a third party and performs storage, verification, transmission and communication of network data through self-distributed nodes, and has the characteristics of decentralization, non-falsification, traceability, transparency, no third party endorsement and the like.
The technical scheme provided by the embodiment utilizes the blockchain technology to realize a user identity management scheme in the multiparty data transaction or sharing process, and solves the multiparty trust problem. Secondly, the implementation utilizes a Local Sensitive Hash (LSH) technology to process the data and store the data as a data fingerprint in a uplink manner, so that the ownership of the data is clarified.
Fig. 7 is a flow chart illustrating a method of data validation processing according to an example.
The data right processing method provided in this embodiment may be executed before receiving the right-of-ownership request for the first data sent by the data verifier. Referring to fig. 7, the above-described right processing method may include the following steps.
In step S702, a data right confirmation transaction sent by the second data owner for the second data is received, where the data right confirmation transaction carries a second locally sensitive hash digest corresponding to the second data.
Wherein a data ownership acknowledgement for the second data may refer to a request to acknowledge that ownership of the second data is obtained.
Step S704, matching the second local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining that data with similarity exceeding a second threshold value with the second data does not exist in the plurality of data in the target blockchain system.
In some embodiments, step S706 may be performed after determining that the second data has not completed the validation operation in the blockchain system after the matching is completed by the second locally sensitive hash digest.
If the second locally sensitive hash digest does not exist in the blockchain system, then it is considered that the second data is not subject to an acknowledgement operation in the blockchain system, i.e., the second data is not owned by another object, and the blockchain system performs step S706.
Step S706, determining that the second locally sensitive hash digest has a rights relationship with the second data owner.
In some embodiments, the second locally sensitive hash digest may be bound to a second data owner to generate a corresponding ownership relationship.
Step S708, the second locality-sensitive hash digest is stored in a uplink with the ownership of the second data owner, so as to determine that the second data owner has ownership of the second data.
In some embodiments, the ownership between the second locally sensitive hash digest and the second data owner may be stored in a uplink to complete the validation operation on the second data by the second data owner.
Step S710, matching the second local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining that data with similarity exceeding a second threshold value exists in the plurality of data in the target blockchain system.
In some embodiments, if it is determined that the second locally sensitive hash digest is already stored in the blockchain system, it is determined that there is data in the target blockchain system that has a similarity to the second data that exceeds a second threshold, that is, the second data corresponding to the second locally sensitive hash digest has been authorized by other objects in the blockchain.
Step S712, sending a data rights confirmation transaction failure prompt to the second data owner to prompt the second data owner that the second data has been validated.
According to the technical scheme, the data is represented through the local sensitive hash, the local sensitive hash is bound with the data owner and stored in the block chain, so that the data owner can realize the right-confirming treatment of the ownership of the data, and on one hand, the authority and fairness of the right-confirming of the data are improved; on the other hand, the data is authorized by using the blockchain, so that the data transaction/sharing process is transparent, and the data security compliance can be audited and traced.
In addition, the traditional data fingerprint uplink method based on the blockchain is to perform common hash operation (such as SHA-256) on source data, if source data of a data owner are simply tampered, then the data fingerprint of the source data is not matched with ownership certificates on the blockchain, namely, after the source data are shared out by the data owner, a malicious attacker can classify the ownership of the data as existing only by simply tampering the source data, and new challenges are provided for protecting rights of the data. The method and the device adopt the locally sensitive hash to carry out the abstract extraction operation on the data, so that the data which are similar to each other can be mapped into the same abstract to a great extent. Therefore, in the data right-confirming process, only the fact that two data have the same local sensitive hash abstract is found, the probability of the two data being extremely high is considered to be similar, or the similarity of the two data exceeds a certain threshold value, and then the two data are considered to be owned by the same data owner, so that the fact that certain data are simply tampered by an illegal attacker and then used can be avoided.
The distributed user identity management scheme is established through the blockchain technology, and the data transaction/sharing participants all join the blockchain network in a blockchain node mode to finish identity registration and acquire an authentication certificate and a public and private key pair. Trust problems between multiple parties can be solved using blockchain technology. Meanwhile, the blockchain has the characteristic of traceability, so that the key links of the data transaction/sharing process can be subjected to uplink certification, and the whole process traceability audit is ensured. Meanwhile, the hash value generated by the LSH algorithm is used as the data fingerprint to finish the confirmation of the data authority, so that the similarity matching of the homologous data can be better finished, and the problems of data infringement and the like can be found in time.
Fig. 8 is a flow chart illustrating a method of data acquisition according to an exemplary embodiment.
The data acquisition method provided in this embodiment may be performed before receiving the ownership right request for the first data sent by the data verifier.
In some embodiments, the data validator in the embodiment shown in FIG. 6 may be the data demander.
Referring to fig. 8, the above-described data acquisition method may include the following steps.
Step S802, a data request sent by a data demander is received.
In some embodiments, the data demand request may include a data demand description issued by the data demander for indicating that the data demander needs to obtain usage rights for data satisfying the data demand description.
In step S804, the data demand request is broadcast to each node in the target blockchain, each node including a first node controlled by a first data owner.
In some embodiments, when the first data owner receives the data demand request issued by the data demand party, and finds that the first data owned by the first data owner meets the data demand description, the first data owner sends data description information of the first data to the blockchain system, and the blockchain system receives, through the first node, the data description information for the first data sent by the first data owner in response to the data demand description; and transmitting data description information for the first data to the data demander so that the data demander determines whether the first data satisfies the demand data demand specification.
The data demand party obtains data description information for the first data sent by the first data owner through the block chain system so as to determine whether the first data is the data which the data demand party wants; after the data demand side determines that the first data is the data which is wanted by the data demand side, response information of data description information of the first data is sent to the blockchain; the block chain system receives response information of the data requesting party aiming at the data description information of the first data; the response information is then sent to the first data owner so that the first data owner sends a data-providing response carrying the first data interface in response to the data-demand request.
In step S806, the first node receives a data providing response sent by the first data owner in response to the data demand request, where the data providing response carries the first data interface.
Step S808, transmitting the data providing response transmitted by the data owner to the data demander, so that the data demander obtains the first data according to the first data interface.
In some embodiments, the data demander, after obtaining the first data through the first data interface, initiates an acknowledgement request to the blockchain system for the first data to determine whether ownership of the first data is owned by the data owner or whether the first data meets its own data demand specification.
In some embodiments, the blockchain system may receive an ownership right request for the first data sent by the data verifier, where the ownership right request carries a first locally sensitive hash digest of the first data, and the first locally sensitive hash digest is obtained after performing a locally sensitive hash process on the first data; matching the first local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining second data with similarity greater than a first threshold value with the first data in the plurality of data; determining a second data owner having second data according to the rights relation; it is determined that the second data owner owns the ownership of the first data.
In some embodiments, if the second data owner is the first data owner in this embodiment, it may be confirmed that the first data is owned by the first data owner.
In some embodiments, the first data may be stored in the blockchain system, and the data request may include a data request description that describes characteristics of the data (e.g., data source, number of data, data size, data time limit, data acquisition time, etc.) that the data requesting party wants to acquire.
After receiving an ownership right request for the first data sent by the data verification party, the blockchain determines whether the first data meets the data requirement specification; if the first data meets the data requirement specification, matching the first local sensitive hash digest with local sensitive hash digests of a plurality of data stored in the blockchain system, and determining second data with similarity greater than a first threshold value from the plurality of data; and if the first data does not meet the data requirement specification, sending a risk prompt that the data does not meet the requirement to the data requirement party.
Fig. 9 is a schematic diagram of a data validation structure, according to an example embodiment.
The embodiment provides a data right-confirming method based on a block chain, replaces the original centralized data right-confirming mechanism with the block chain, and provides a user identity management scheme realized through the block chain, thereby solving the multi-party trust problem in the data transaction/sharing process. And meanwhile, a data fingerprint uplink method is realized by utilizing an LSH algorithm.
The embodiment is divided into two phases, namely a user registration phase, a certificate acquisition phase and a data right confirmation phase.
The data transaction/sharing participants all join in the blockchain network in a blockchain node mode to finish identity registration, certificate acquisition and generate public and private key pairs for subsequent identity authentication and communication encryption. The flow is shown in fig. 5, and the specific steps are as follows:
1. blockchain 504 receives a registration request from a user (e.g., data demander 501, data owner 502, or data supervisor 503), the registration request carrying a registration public key and a user ID; 2. the blockchain 504 sends an identity attribute information acquisition request encrypted by a registration public key to a user in response to the registration request; 3. the user obtains a user public key userPK and a user private key usesk through processing. 4. The blockchain 504 receives an identity attribute information response sent by the second data owner and encrypted by the registration public key, wherein the identity attribute information response carries the identity attribute information of the user and the user public key; 5. the blockchain 504 binds the user ID with the identity attribute information corresponding to the user and generates an identity certificate userCert for the user; 6. blockchain 504 performs a process of linking the identity attribute information and the identity credential to verify the identity of the second user when the second user confirms the transaction for the second data transmission data ownership and returns the user credential to the user.
In some embodiments, the scheme architecture of the data validation phase is shown in FIG. 9, which may be divided into four parts: data owners 901, 902, or 903, data requesters 906, data supervisors 907, and blockchain networks 908. The specific contents are as follows:
data owners 901, 902, or 903 contain mainly three modules:
(1) Extracting digital fingerprints based on a Local Sensitive Hash (LSH) algorithm: the LSH algorithm can perform quick similarity matching on massive high-dimensional data. In the data right-determining scenario, the data owner can perform LSH hash calculation through the data asset, and the calculation result is used as the data fingerprint to be stored in a uplink manner. In the subsequent data transaction process, if a malicious attacker simply falsifies the data of all the data parties, the data is applied to other improper scenes, and economic benefits are illegally achieved. The behavior can be timely discovered by carrying out similarity matching on the data through the LSH algorithm, so that the rights and interests of data owners are better protected.
(2) Submitting a data validation transaction: and (3) carrying out uplink storage on the data fingerprint, initiating data right-confirming transaction, and writing the result into a transaction block.
(3) Data encryption: and encrypting the data transmission process to ensure the confidentiality of the data.
(two) data demander 906 mainly includes three modules:
(1) Submitting data requirements: and initiating data transaction through the intelligent contract and submitting data demand description.
(2) Data encryption: and encrypting the data transmission process to ensure the confidentiality of the data.
(3) And (3) data calculation: and analyzing and calculating the acquired transaction/sharing data.
The blockchain network mainly comprises four modules of data ownership preservation, user identity management, data transaction/sharing process record and supervision interface.
And (III) the data supervisor 907 accesses the blockchain as a supervisory node and supervises and audits the whole flow of data transactions/shares.
Referring to fig. 9, the data right determining process may include the steps of:
1) The data owner extracts the fingerprint through LSH algorithm and initiates the data right to the blockchain to confirm the transaction.
2) Each node in the blockchain firstly verifies whether the identity certificate of the data owner is legal or not, and if the identity certificate is legal, the transaction is accepted and broadcast to other surrounding nodes.
3) If no node is opposite to the pen-changing transaction for a period of time, the node is finally updated into a block of the block chain, and the ownership of the data is determined to be attributed to the data owner.
After the data ownership is clear, the subsequent data transaction/sharing flow can be performed, and the key links are stored in a uplink mode, so that the supervision node can conveniently supervise and audit the data transaction/sharing flow.
The present application has advantages and effects over the prior art.
And (5) decentralizing. The data right-confirming method provided by the invention does not need a third party to endorse, and can solve the authority and fairness problems of a centralized right-confirming system.
The method is suitable for data right confirmation under a big data scene. The data infringement behavior aiming at homologous data tampering can be timely discovered by a data validation mechanism based on an LSH algorithm and a blockchain.
Can be audited. The key links of data transaction/sharing are uplink, and the blockchain has the characteristics of traceability and non-falsification, and can meet the supervision and audit requirements of related management institutions.
FIG. 10 is a block diagram illustrating a blockchain-based data processing device in accordance with an exemplary embodiment. Referring to fig. 10, a blockchain-based data processing device 1000 provided by an embodiment of the present disclosure may include: an ownership request acquisition module 1001, a digest matching module 1002, a data owner determination module 1003, and an ownership determination module 1004.
The ownership right request obtaining module 1001 may be configured to receive an ownership right request for first data sent by a data verifier, where the ownership right request carries a first locally sensitive hash digest of the first data, and the first locally sensitive hash digest is obtained after performing a locally sensitive hash process on the first data; the digest matching module 1002 may be configured to match the first locally sensitive hash digest with a locally sensitive hash digest of a plurality of data stored in the blockchain system, and determine, from the plurality of data, second data having a similarity to the first data greater than a first threshold; the data owner determination module 1003 may be configured to determine a second data owner having second data according to the ownership relationship; the ownership determination module 1004 may be used to determine that the second data owner owns ownership of the first data.
In some embodiments, the blockchain-based data processing device further includes: the system comprises a data right confirming transaction acquisition module, a first abstract matching module, a right relation determining module and a uplink storage module.
The data right confirming transaction acquisition module is used for receiving a data right confirming transaction sent by a second data owner for second data before receiving the right confirming request for the ownership of the first data sent by the data verification party, wherein the data right confirming transaction carries a second local sensitive hash abstract corresponding to the second data; the first digest matching module is used for matching the second local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining that the data with the similarity exceeding a second threshold value with the second data does not exist in the plurality of data in the target blockchain system; the right relation determining module is used for determining that the second local sensitive hash digest has a right relation with a second data owner; the uplink storage module is used for carrying out uplink storage on the second local sensitive hash digest and the ownership of the second data owner so as to determine that the second data owner has ownership of the second data.
In some embodiments, the blockchain-based data processing device further includes: the system comprises a second abstract matching module and a transaction failure prompting module.
The second digest matching module is used for matching the second local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining that data with the similarity exceeding a second threshold value exists in the plurality of data in the target blockchain system; the transaction failure prompting module is used for sending a data right to confirm the transaction failure prompt to the second data owner so as to prompt the second data owner that the second data has been confirmed.
In some embodiments, the data validator is a data demander; wherein the blockchain-based data processing device further includes: the system comprises a data demand request acquisition module, a broadcasting module, a data providing response acquisition module and a data providing response forwarding module.
The data demand request acquisition module is used for receiving a data demand request sent by the data demand party before receiving an ownership right request for the first data sent by the data verification party; the broadcasting module is used for broadcasting the data demand request to all nodes in the target block chain, wherein each node comprises a first node controlled by a first data owner; the data providing response acquisition module is used for receiving a data providing response sent by a first data owner in response to the data demand request through the first node, wherein the data providing response carries a first data interface; the data providing response forwarding module is used for sending the data providing response sent by the data owner to the data demand party so that the data demand party can acquire the first data according to the first data interface.
In some embodiments, the data demand request carries a data demand specification; the summary matching module 1002 may include: the system comprises a data demand matching unit, a satisfaction judging unit and a non-satisfaction judging unit.
Wherein the data requirement matching unit may be configured to determine whether the first data satisfies the data requirement specification; the satisfaction judging unit can use Yu Redi data to meet the data requirement specification, then match the first local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determine second data with similarity greater than a first threshold value with the first data in the plurality of data; the unsatisfied judging unit may use Yu Redi to indicate that the data is not satisfied, and send a risk prompt that the data is not satisfied to the data requiring party.
In some embodiments, the data demand request carries a data demand specification; wherein the blockchain-based data processing device further includes: the system comprises a data description information acquisition module, a data description information forwarding module, a response information acquisition module and a response information forwarding module.
The data description information acquisition module may be configured to, after broadcasting the data demand request to each node in the target blockchain, receive, by the first node, a data providing response sent by the first data owner in response to the data demand request, and before the data providing response carries the first data interface, receive, by the first node, data description information for the first data sent by the first data owner in response to the data demand description; the data description information forwarding module may be configured to send data description information for the first data to the data demander so that the data demander determines whether the first data meets the demand data demand specification; the response information acquisition module may be configured to receive response information of the data demander for the data description information of the first data; the response information forwarding module may be configured to send response information to the first data owner so that the first data owner sends a data provision response carrying the first data interface in response to the data demand request.
In some embodiments, the blockchain-based data processing device further includes: the system comprises a registration request acquisition module, an identity attribute information acquisition request module, an identity attribute information acquisition module, an information binding module and a uplink module.
The registration request acquisition module may be configured to receive a registration request sent by a second data owner before receiving an ownership right request for the first data sent by the data verifier, where the registration request carries a registration public key; the identity attribute information acquisition request module may be configured to send, in response to the registration request, an identity attribute information acquisition request encrypted by the registration public key to the second data owner; the identity attribute information acquisition module may be configured to receive an identity attribute information response sent by the second data owner and encrypted by the registration public key, where the identity attribute information response carries the identity attribute information of the second data owner and the public key of the second data owner; the information binding module can be used for binding the second data owner with the identity attribute information corresponding to the second data owner and generating an identity certificate for the second data owner; the uplink module may be configured to uplink the identity attribute information and the identity credential to verify the identity of the second data owner upon confirmation of the transaction for the second data transmission data ownership.
Since each function of the apparatus 1000 is described in detail in the corresponding method embodiments, the disclosure is not repeated herein.
The modules and/or sub-units involved in the embodiments of the present application may be implemented in software, or may be implemented in hardware. The described modules and/or sub-units may also be provided in a processor. Wherein the names of the modules and/or sub-units do not in some cases constitute limitations of the modules and/or sub-units themselves.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
Fig. 11 shows a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure. It should be noted that the electronic device 1100 shown in fig. 11 is only an example, and should not impose any limitation on the functions and usage scope of the embodiments of the present disclosure.
As shown in fig. 11, the electronic device 1100 includes a Central Processing Unit (CPU) 1101 that can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1102 or a program loaded from a storage section 1108 into a Random Access Memory (RAM) 1103. In the RAM 1103, various programs and data necessary for the operation of the electronic device 1100 are also stored. The CPU 1101, ROM 1102, and RAM 1103 are connected to each other by a bus 1104. An input/output (I/O) interface 1105 is also connected to bus 1104.
The following components are connected to the I/O interface 1105: an input section 1106 including a keyboard, a mouse, and the like; an output portion 1107 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 1108 including a hard disk or the like; and a communication section 1109 including a network interface card such as a LAN card, a modem, and the like. The communication section 1109 performs communication processing via a network such as the internet. The drive 1110 is also connected to the I/O interface 1105 as needed. Removable media 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is installed as needed on drive 1110, so that a computer program read therefrom is installed as needed into storage section 1108.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 1109, and/or installed from the removable media 1111. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 1101.
It should be noted that the computer readable storage medium shown in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable storage medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
As another aspect, the present application also provides a computer-readable storage medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer-readable storage medium carries one or more programs which, when executed by a device, cause the device to perform functions including: receiving an ownership right request for first data sent by a data verification party, wherein the ownership right request carries a first local sensitive hash abstract of the first data, and the first local sensitive hash abstract is obtained after local sensitive hash processing is carried out on the first data; matching the first locally sensitive hash digest with a locally sensitive hash digest of a plurality of data stored in the blockchain system, and determining second data with similarity to the first data being greater than a first threshold value from the plurality of data; determining a second data owner having the second data according to the rights relation; determining that the second data owner owns ownership of the first data.
According to one aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the methods provided in the various alternative implementations of the above-described embodiments.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, aspects of the disclosed embodiments may be embodied in a software product, which may be stored on a non-volatile storage medium (which may be a CD-ROM, a U-disk, a mobile hard disk, etc.), comprising instructions for causing a computing device (which may be a personal computer, a server, a mobile terminal, or a smart device, etc.) to perform a method according to embodiments of the disclosure, e.g., one or more of the steps shown in fig. 6, 7, or 8.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the disclosure is not to be limited to the details of construction, the manner of drawing, or the manner of implementation, which has been set forth herein, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (10)
1. A blockchain-based data processing method, wherein the method is performed by a target node in a target blockchain system, the target blockchain system storing therein locally sensitive hash digests of a plurality of data and ownership relationships of data owners of the respective locally sensitive hash digests and corresponding data, comprising:
receiving an ownership right request for first data sent by a data verification party, wherein the ownership right request carries a first local sensitive hash abstract of the first data, and the first local sensitive hash abstract is obtained after local sensitive hash processing is carried out on the first data;
Matching the first locally sensitive hash digest with a locally sensitive hash digest of a plurality of data stored in the blockchain system, and determining second data with similarity to the first data being greater than a first threshold value from the plurality of data;
determining a second data owner having the second data according to the rights relation;
determining that the second data owner owns ownership of the first data.
2. The method of claim 1, wherein prior to receiving the ownership right request for the first data sent by the data verifier, the method further comprises:
receiving a data right confirmation transaction sent by the second data owner for the second data, wherein the data right confirmation transaction carries a second local sensitive hash abstract corresponding to the second data;
matching the second locally sensitive hash digest with the locally sensitive hash digests of the plurality of data stored in the blockchain system, and determining that data with similarity exceeding a second threshold value with the second data does not exist in the plurality of data in the target blockchain system;
determining that the second locality sensitive hash digest has a rights relationship with the second data owner;
And carrying out uplink storage on the second local sensitive hash digest and the ownership of the second data owner so as to determine that the second data owner owns the ownership of the second data.
3. The method according to claim 2, wherein the method further comprises:
matching the second local sensitive hash digest with the local sensitive hash digests of the plurality of data stored in the blockchain system, and determining that data with similarity to the second data exceeding the second threshold exists in the plurality of data in the target blockchain system;
and sending a data right confirming transaction failure prompt to the second data owner to prompt the second data owner that the second data has been confirmed.
4. The method of claim 1, wherein the data validator is a data demander; wherein, before receiving the ownership right request for the first data sent by the data verification party, the method further comprises:
receiving a data demand request sent by the data demand party;
broadcasting the data demand request to each node in the target blockchain, the each node including a first node controlled by a first data owner;
Receiving a data providing response sent by the first data owner in response to the data demand request by the first node, wherein the data providing response carries a first data interface;
and sending a data providing response sent by the data owner to the data demander so that the data demander can acquire the first data according to the first data interface.
5. The method of claim 4, wherein the data demand request carries a data demand specification; matching the first locally sensitive hash digest with the locally sensitive hash digests of a plurality of data stored in the blockchain system, determining second data with similarity greater than a first threshold value with the first data in the plurality of data, including:
determining whether the first data meets the data requirement specification;
if the first data meets the data requirement specification, matching the first local sensitive hash digest with local sensitive hash digests of a plurality of data stored in the blockchain system, and determining second data with similarity greater than a first threshold value with the first data in the plurality of data;
And if the first data does not meet the data requirement specification, sending a risk prompt that the data does not meet the requirement to the data requirement party.
6. The method of claim 4, wherein the data demand request carries a data demand specification; wherein after broadcasting the data demand request to each node in the target blockchain, before receiving, by the first node, a data provision response sent by the first data owner in response to the data demand request, the data provision response carrying a first data interface, the method further comprises:
receiving, by the first node, data description information for first data sent by the first data owner in response to the data requirement specification;
transmitting data description information for the first data to the data demander so that the data demander determines whether the first data meets the requirement of the data requirement specification;
receiving response information of the data demand side for the data description information of the first data;
and sending the response information to the first data owner, so that the first data owner responds to the data demand request to send a data providing response carrying the first data interface.
7. The method of claim 1, wherein prior to receiving the ownership right request for the first data sent by the data verifier, the method further comprises:
receiving a registration request sent by the second data owner, wherein the registration request carries a registration public key;
responding to the registration request, and sending an identity attribute information acquisition request encrypted by the registration public key to the second data owner;
receiving an identity attribute information response sent by the second data owner and encrypted by the registration public key, wherein the identity attribute information response carries the identity attribute information of the second data owner and the public key of the second data owner;
binding the second data owner with identity attribute information corresponding to the second data owner, and generating an identity certificate for the second data owner;
and the identity attribute information and the identity certificate are subjected to uplink processing so as to verify the identity of the second data owner when the second data owner confirms the transaction for the second data sending data right.
8. A blockchain-based data processing apparatus, wherein the method is performed by a target node in a target blockchain system, wherein a locally sensitive hash digest of a plurality of data and a ownership relationship of each locally sensitive hash digest with a data owner of corresponding data are stored in the target blockchain system, comprising:
The ownership right request acquisition module is used for receiving an ownership right request for first data sent by a data verification party, wherein the ownership right request carries a first local sensitive hash digest of the first data, and the first local sensitive hash digest is obtained after local sensitive hash processing is carried out on the first data;
the digest matching module is used for matching the first local sensitive hash digest with local sensitive hash digests of a plurality of data stored in the blockchain system, and determining second data with similarity greater than a first threshold value with the first data in the plurality of data;
a data owner determining module, configured to determine a second data owner having the second data according to the ownership relationship;
and the possession relation determining module is used for determining that the second data owner owns the ownership of the first data.
9. An electronic device, comprising:
a memory; and
a processor coupled to the memory, the processor being configured to perform the blockchain-based data processing method of any of claims 1-7 based on instructions stored in the memory.
10. A computer readable storage medium having stored thereon a program which when executed by a processor implements a blockchain-based data processing method as claimed in any of claims 1-7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111242740.2A CN116028981A (en) | 2021-10-25 | 2021-10-25 | Block chain-based data processing method and related equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111242740.2A CN116028981A (en) | 2021-10-25 | 2021-10-25 | Block chain-based data processing method and related equipment |
Publications (1)
Publication Number | Publication Date |
---|---|
CN116028981A true CN116028981A (en) | 2023-04-28 |
Family
ID=86089959
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202111242740.2A Pending CN116028981A (en) | 2021-10-25 | 2021-10-25 | Block chain-based data processing method and related equipment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116028981A (en) |
-
2021
- 2021-10-25 CN CN202111242740.2A patent/CN116028981A/en active Pending
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US12021992B2 (en) | System and method for authenticating user identity | |
US11818265B2 (en) | Methods and systems for creating and recovering accounts using dynamic passwords | |
JP7181539B2 (en) | METHOD AND APPARATUS FOR MANAGING USER IDENTIFICATION AND AUTHENTICATION DATA | |
US10728042B2 (en) | System and method for blockchain-based cross-entity authentication | |
US20200013026A1 (en) | Systems and methods for blockchain addresses and owner verification | |
CN111144881A (en) | Selective access to asset transfer data | |
CN112215608A (en) | Data processing method and device | |
CN112804218A (en) | Data processing method, device and equipment based on block chain and storage medium | |
US20220269754A1 (en) | Decentralized system and method for asset registry and authentication | |
US11310044B2 (en) | Authenticate transactions of secured file in blockchain | |
CN114978635A (en) | Cross-domain authentication method and device, and user registration method and device | |
US20210012447A1 (en) | Method and System for Processing Firearm-Related Data | |
Alexander et al. | Cybersecurity, information assurance, and big data based on blockchain | |
CN110276693B (en) | Insurance claim settlement method and system | |
US20230208640A1 (en) | Selective audit process for privacy-preserving blockchain | |
CN113328854B (en) | Service processing method and system based on block chain | |
CN115147224A (en) | Transaction data sharing method and device based on alliance chain | |
US20210110357A1 (en) | Digital notarization intermediary system | |
US20240129113A1 (en) | Method for providing oracle service of blockchain network by using zero-knowledge proof and aggregator terminal using the same | |
CN116684160A (en) | Public service litigation data security sharing and privacy protecting method and system | |
TWI776590B (en) | System, method and computer readable medium for authenticaion and transfer traceability of digital documents | |
CN116028981A (en) | Block chain-based data processing method and related equipment | |
CN113468600B (en) | Data authorization method, device and equipment | |
CN118862178A (en) | Data processing method, device, equipment and medium based on trusted execution environment | |
CN118337396A (en) | Block chain-based privacy protection transaction verification method, device, equipment and medium |
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 |