Blockchain-based data processing method and related device

Abstract

The present disclosure provides a kind of data processing method and related equipment based on blockchain, local sensitive hash summary of multiple data stored in target blockchain system and the ownership relationship of each local sensitive hash summary and the data owner corresponding to data, the method comprises: receiving the ownership confirmation request of first data sent by data verification party, the first local sensitive hash summary of first data is carried in ownership confirmation request, and the first local sensitive hash summary is obtained after local sensitive hash processing to first data;First local sensitive hash summary and the local sensitive hash summary of multiple data stored in blockchain system are matched, and the second data with the similarity greater than first threshold in multiple data is determined with first data;Second data owner who possesses second data is determined according to ownership relationship;It is determined that second data owner possesses the ownership of first data.

Description

Technical Field

[0001] This disclosure relates to the field of computer and internet technology, and in particular to a data processing method and apparatus, electronic device and computer-readable storage medium based on blockchain. Background Technology

[0002] With the advent of the big data era, the potential value of data is being developed and utilized. Since data is a crucial asset for enterprises, the issue of data ownership inevitably arises during its trading and circulation. Confirming data rights ensures that the digital assets of enterprises and individuals are not illegally infringed upon, while defining data rights and responsibilities ensures the traceability of fraudulent or illegal data transactions. Data ownership has always been one of the challenges facing big data transactions, as it relates to the development of the data market and the exploitation and utilization of data value.

[0003] Data ownership confirmation primarily targets data from different sources, clarifying ownership through technical and legal means to promote data integration, accelerate data sharing and circulation, reduce transaction costs, and activate the value of data assets. Traditional data ownership confirmation mainly employs a model of submitting ownership certificates and expert review; however, this method cannot guarantee the impartiality of the rights confirmation results. Summary of the Invention

[0004] The purpose of this disclosure is to provide a data processing method, apparatus, electronic device, and computer-readable storage medium based on blockchain, which can ensure the fairness of ownership confirmation by confirming the data owner of the first data through the blockchain system.

[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0006] This disclosure provides a blockchain-based data processing method, comprising: receiving an ownership confirmation request for first data sent by a data verification party, the ownership confirmation request carrying a first local sensitive hash digest of the first data, the first local sensitive hash digest being obtained by performing local sensitive hash processing on the first data; matching the first local sensitive hash digest with local sensitive hash digests of multiple data stored in the blockchain system, and determining, among the multiple data, a second data whose similarity to the first data is greater than a first threshold; determining, according to the ownership relationship, a second data owner who owns the second data; and determining that the second data owner owns the first data.

[0007] In some embodiments, before receiving a request for ownership confirmation of the first data sent by a data verification party, the method further includes: receiving a data ownership confirmation transaction sent by the second data owner for the second data, the data ownership confirmation transaction carrying a second local sensitive hash digest corresponding to the second data; matching the second local sensitive hash digest with local sensitive hash digests of multiple data stored in the blockchain system to determine that there is no data in the multiple data in the target blockchain system whose similarity to the second data exceeds a second threshold; determining that there is an ownership relationship between the second local sensitive hash digest and the second data owner; and storing the ownership relationship between the second local sensitive hash digest and the second data owner on the blockchain to determine that the second data owner owns the second data.

[0008] In some embodiments, the method further includes: matching the second local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system to determine that there is data in the multiple data in the target blockchain system whose similarity to the second data exceeds the second threshold; and sending a data ownership confirmation transaction failure prompt to the owner of the second data to indicate that the second data has been confirmed.

[0009] In some embodiments, the data verification party is a data requester; wherein, before receiving the ownership confirmation request for the first data sent by the data verification party, the method further includes: The system receives a data request from the data requester; broadcasts the data request to each node in the target blockchain, including a first node controlled by the first data owner; receives a data provision response from the first data owner in response to the data request through the first node, the data provision response carrying a first data interface; and sends the data provision response sent by the data owner to the data requester so that the data requester can obtain the first data according to the first data interface.

[0010] In some embodiments, the data request carries a data requirement description; wherein, matching the first Locally Sensitive Hash Digest (LSHD) with the LSHDs of multiple data stored in the blockchain system, and determining a second data among the multiple data whose similarity to the first data is greater than a first threshold, includes: determining whether the first data satisfies the data requirement description; if the first data satisfies the data requirement description, then matching the first LSHD with the LSHDs of multiple data stored in the blockchain system, and determining a second data among the multiple data whose similarity to the first data is greater than a first threshold; if the first data does not satisfy the data requirement description, then sending a risk warning that the data does not meet the requirements to the data requester.

[0011] In some embodiments, the data request carries a data requirement description; wherein, after broadcasting the data request to each node in the target blockchain, and before receiving a data provision response sent by the first data owner in response to the data request through the first node, the data provision response carrying a first data interface, the method further includes: receiving data description information for first data sent by the first data owner in response to the data requirement description through the first node; sending the data description information for the first data to the data requester so that the data requester can determine whether the first data meets the data requirement description; receiving response information from the data requester regarding the data description information for the first data; and sending the response information to the first data owner so that the first data owner can send a data provision response carrying the first data interface in response to the data request.

[0012] In some embodiments, before receiving the ownership confirmation request for the first data sent by the data verification party, the method further includes: receiving a registration request sent by the second data owner, the registration request carrying a registration public key; in response to the registration request, sending a request to the second data owner to obtain identity attribute information encrypted with the registration public key; receiving a response from the second data owner containing identity attribute information encrypted with the registration public key, the identity attribute information response carrying the identity attribute information of the second data owner and the public key of the second data owner; binding the second data owner with the corresponding identity attribute information to generate an identity certificate for the second data owner; and uploading the identity attribute information and the identity certificate to the blockchain so as to verify the identity of the second data owner when the second data owner sends a data ownership confirmation transaction for the second data.

[0013] This disclosure provides a blockchain-based data processing device, including: an ownership confirmation request acquisition module, a digest matching module, a data owner determination module, and an ownership relationship determination module.

[0014] The ownership confirmation request acquisition module is used to receive an ownership confirmation request for the first data sent by the data verification party. The ownership confirmation request carries a first local sensitive hash digest of the first data, which is obtained by performing local sensitive hash processing on the first data. The digest matching module can be used to match the first local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system, and determine a second data among the multiple data whose similarity to the first data is greater than a first threshold. The data owner determination module can be used to determine the second data owner who owns the second data according to the ownership relationship. The ownership relationship determination module can be used to determine that the second data owner owns the first data.

[0015] This disclosure provides an electronic device comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the blockchain-based data processing method described above.

[0016] This disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the blockchain-based data processing method as described in any of the preceding embodiments.

[0017] This disclosure provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned blockchain-based data processing method.

[0018] The data processing method, apparatus, electronic device, and computer-readable storage medium based on blockchain provided in this disclosure, on the one hand, bind the Local Sensitive Hash Digest (LSHDD) corresponding to the data with the data owner on the blockchain to confirm and retain ownership, thus fairly and impartially processing data ownership. During the use of the first data, the data owner with ownership of the first data can be fairly confirmed, improving the fairness and efficiency of data ownership confirmation. On the other hand, the technical solution provided in this disclosure, during the data ownership request and ownership confirmation process, can express the data through LSHD, so that similar data can be expressed as the same LSHD, thereby promptly discovering similar data and avoiding the inability to compare and analyze similar data due to its large size, thus preventing unauthorized attackers from modifying and using the data for infringing purposes.

[0019] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this disclosure. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0021] Figure 1 This is a schematic diagram of the architecture of a blockchain-based data processing system provided in this embodiment.

[0022] Figure 2 This is a schematic diagram of a blockchain network provided in an embodiment of this disclosure.

[0023] Figure 3 This is a schematic diagram of the structure of a block provided in an embodiment of this disclosure.

[0024] Figure 4 This is a schematic diagram of a new block generation process provided in an embodiment of this disclosure.

[0025] Figure 5 This is a node registration method illustrated according to an exemplary embodiment.

[0026] Figure 6 This is a flowchart illustrating a blockchain-based data processing method according to an exemplary embodiment.

[0027] Figure 7 This is a flowchart illustrating a data ownership confirmation process according to an example.

[0028] Figure 8 This is a flowchart illustrating a data acquisition method according to an exemplary embodiment.

[0029] Figure 9 This is a schematic diagram of a data ownership structure according to an exemplary embodiment.

[0030] Figure 10 This is a block diagram illustrating a blockchain-based data processing apparatus according to an exemplary embodiment.

[0031] Figure 11 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. Detailed Implementation

[0032] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0033] The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more specific details omitted, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0034] The accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus omitting repeated descriptions of them. Some block diagrams shown in the drawings do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0035] The flowchart shown in the accompanying drawings is merely illustrative and does not necessarily include all content and steps, nor does it require execution in the described order. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0036] In this specification, the terms “a,” “an,” “the,” “the,” and “at least one” are used to indicate the presence of one or more elements / components / etc.; the terms “comprising,” “including,” and “having” are used to indicate an open-ended inclusion and to mean that there may be other elements / components / etc. in addition to the listed elements / components / etc.; the terms “first,” “second,” and “third,” etc., are used only as markings and are not a limitation on the number of objects.

[0037] To better understand the above-mentioned objectives, features and advantages of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0038] This disclosure relates to blockchain technology, a novel application model of computer technologies such as distributed data storage, peer-to-peer (P2P) transmission, consensus mechanisms, and encryption algorithms. Essentially, it is a decentralized database, a chain of data blocks linked using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include a blockchain underlying platform, a platform product service layer, and an application service layer. A blockchain can consist of multiple linked transaction records (also known as blocks) whose content is protected by cryptography. The distributed ledger linked by the blockchain allows multiple parties to effectively record transactions and permanently verify these transactions (immutable). The consensus mechanism refers to the mathematical algorithm used in the blockchain system to establish trust and acquire rights among different nodes; that is, the consensus mechanism is a mathematical algorithm commonly recognized by all network nodes in the blockchain.

[0039] like Figure 1 As shown, the blockchain-based data processing system provided in this embodiment may include a blockchain system 100 and multiple terminal devices. Figure 1 Taking the example of three terminal devices, namely the first terminal 201, the second terminal 202, and the third terminal 203, the first terminal 201, the second terminal 202, and the third terminal 203 can be used to obtain transaction data (including transaction requests or transaction data generated after executing transaction requests) from the blockchain system, or to upload transaction data to the blockchain system.

[0040] like Figure 2 As shown, Figure 1The blockchain system 100 in this embodiment may include multiple node devices 101, which can refer to various clients within the blockchain system. The blockchain system 100 refers to a system used for data sharing between the node devices 101. Each node device 101, during normal operation, can receive transaction data and maintain shared data within the blockchain system 100 based on the received transaction data. To ensure information interoperability within the blockchain system 100, information connections can exist between each node device 101, allowing information transmission between them. For example, when any node device 101 in the blockchain system 100 receives transaction data, other node devices 101 in the blockchain system 100 obtain the transaction data according to a consensus algorithm and store it as part of the shared data, ensuring consistency of data stored on all node devices 101 in the blockchain system 100.

[0041] In the blockchain system 100, the node device 101, the first terminal 201, the second terminal 202, and the third terminal 203 can be any electronic device, including but not limited to mobile phones, tablets, laptops, PDAs, smart speakers, mobile internet devices (MIDs), POS (Point of Sales) machines, wearable devices (such as smartwatches, smart bracelets, etc.); it can also be an independent server, a server cluster composed of several servers, or a cloud computing center.

[0042] Each node device 101 in the blockchain system 100 has a corresponding node device identifier. Each node device 101 can also store the node device identifiers of other node devices 101 in the blockchain system 100, so that the generated block can be broadcast to the other node devices 101 in the blockchain system 100 based on their node device identifiers. Each node device 101 can maintain a node device identifier list as shown in Table 1, storing the node device name and node device identifier in this list. The node device identifier can be an IP (Internet Protocol) address or any other information that can be used to identify the node device; Table 1 only uses IP addresses as an example. N is a positive integer greater than or equal to 1.

[0043] Table 1

[0044] Each node device 101 in the blockchain system 100 stores the same blockchain. The blockchain consists of multiple blocks, each block containing the cryptographic hash of the previous block (represented by a hash value calculated using a Merkle tree algorithm), the corresponding timestamp, and transaction data. This design makes the block content difficult to tamper with.

[0045] See Figure 3 A blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores transaction data feature values, version number, timestamp, and difficulty value, while the block body stores the transaction data. The next block after the genesis block takes the genesis block as its parent block. The next block also includes a block header and a block body. The block header stores the transaction data feature values ​​of the current block, the block header feature values ​​of the parent block, version number, timestamp, and difficulty value, and so on. This ensures that the block data stored in each block is related to the block data stored in the parent block, guaranteeing the security of transaction data within each block.

[0046] When generating the individual blocks in the blockchain, see Figure 4 When a node device hosting the blockchain receives transaction data, it verifies the data. After verification, it stores the transaction data in a memory pool and updates its hash tree used to record transaction data. Then, it updates the timestamp to the time the transaction data was received and attempts to calculate the feature value multiple times using different random numbers, ensuring that the calculated feature value satisfies the following formula: (1) Wherein, SHA256 is the feature value algorithm used to calculate the feature value; version (version number) is the version information of the relevant block protocol in the blockchain; prev_hash is the block header feature value of the parent block of the current block; merkle_root is the feature value of the transaction data; ntime is the update time of the update timestamp; nbits is the current difficulty, which is a fixed value for a period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the feature value threshold, which can be determined based on nbits.

[0047] Thus, when a random number satisfying the above formula is calculated, the information can be stored accordingly, generating a block header and a block body to obtain the current block. Subsequently, the node device where the blockchain resides sends the newly generated block to other node devices in the blockchain system 100 according to the node device identifiers of other node devices in the blockchain system 100. The other node devices verify the newly generated block and add it to their stored blockchain after verification.

[0048] Figure 5 This is a node registration method illustrated according to an exemplary embodiment.

[0049] Before performing the following embodiments, you may refer to Figure 5 Node registration is performed within the blockchain system. Figure 5 The nodes in the illustrated embodiments may be nodes corresponding to data requesters, nodes corresponding to data owners, or nodes corresponding to data regulators; this disclosure does not impose any restrictions on this.

[0050] In this context, "data demander" can refer to any entity that needs to obtain the right to use data. "Data owner" can refer to any entity that needs to conduct a rights confirmation operation in the blockchain system (requesting confirmation that it owns, uses, or disposes of certain data) to obtain the ownership, use, or disposal rights of the data. "Data regulator" can refer to a third-party authoritative institution, such as public security, procuratorial, or judicial departments with regulatory authority over data, or senior management departments of a company, etc. This disclosure does not impose any restrictions on this.

[0051] The roles of data demander, data owner, and data regulator can be interchanged. Furthermore, an entity can be a data demander, a data owner, and a data regulator simultaneously; this disclosure does not impose any restrictions on this.

[0052] refer to Figure 5 The node registration method described above may include the following steps: 1. Blockchain 504 receives a registration request from a user (e.g., data requester 501, data owner 502, or data regulator 503). The registration request carries a registration public key (issued by blockchain 504 for user or node registration) and a user ID. 2. In response to the registration request, blockchain 504 sends a request to the user to obtain identity attribute information encrypted with the registration public key. 3. The user obtains the user public key userPK and the user private key ueseSK, and sends them to blockchain 504. 4. Blockchain 504 receives a response from the second data owner, containing identity attribute information encrypted with the registration public key. This response carries the user's identity attribute information and the user public key. 5. Blockchain 504 binds the user ID to the user's corresponding identity attribute information and generates an identity certificate userCert for the user. 6. Blockchain 504 processes the identity attribute information and identity certificate on the blockchain so that the identity of the second user can be verified when the second user sends a data ownership confirmation transaction for the second data, and the user certificate is returned to the user.

[0053] Through the above steps, each user can complete node registration so that they can subsequently send data ownership confirmation requests, data demand requests, or data ownership confirmation requests to the blockchain.

[0054] Figure 6 This is a flowchart illustrating a blockchain-based data processing method according to an exemplary embodiment. The method can be executed by a target node in the target blockchain system. The target blockchain system stores local sensitive hash digests of multiple data sets and the ownership relationships between each local sensitive hash digest and the corresponding data owner. For details on the on-chain process of storing the local sensitive hash digests of multiple data sets and the ownership relationships between each local sensitive hash digest and the corresponding data owner, please refer to... Figure 7 The embodiment shown is not described in detail here.

[0055] Reference Figure 6 The blockchain-based data processing method provided in this disclosure may include the following steps.

[0056] Step S602: Receive an ownership confirmation request for the first data sent by the data verification party. The ownership confirmation request carries a first local sensitive hash digest of the first data, which is obtained by performing local sensitive hash processing on the first data.

[0057] Data ownership can refer to the right to possess, control, use, profit from, and dispose of certain data. A request to confirm ownership of primary data can refer to a request to confirm who owns the primary data.

[0058] In some embodiments, a data verifier can refer to an object that needs to request verification of the data owner of certain data from the blockchain. Any object with verification permissions can become a data verifier in this embodiment.

[0059] In some embodiments, when a data regulator (a data verifier) ​​is supervising the first data, the data regulator may initiate a data ownership confirmation request to the blockchain system regarding the first data. When a data owner (a data verifier) ​​discovers that some objects are using the first data, and the first data is similar to data for which they have already confirmed ownership on the blockchain, they may initiate a data ownership confirmation request to the blockchain system regarding the first data, so that if the blockchain identifies them as the owner of the first data, they can initiate an infringement lawsuit against that object. Furthermore, when a data requester (a data verifier) ​​obtains the first data from an object, they may initiate a data ownership confirmation request to the blockchain system to confirm whether that object owns the first data. This disclosure does not limit the application scenarios for the data verification party's request for ownership confirmation of the first data.

[0060] The basic idea behind Locality Sensitive Hashing (LSH) is that two adjacent data points in a high-dimensional data space, after being mapped to a low-dimensional data space, will have a high probability of remaining adjacent; conversely, two data points that were not originally adjacent will also have a high probability of not being adjacent in the low-dimensional space. Through this mapping, we can find adjacent data points in the low-dimensional data space, avoiding the time-consuming search in the high-dimensional space. Therefore, LSH can map two originally similar data points to the same hash value to a large extent. Consequently, if processing two different data points using LSH yields the same hash digest, then the two data points can be considered to have a high degree of similarity.

[0061] Step S604: Match the first local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system, and determine the second data among the multiple data whose similarity to the first data is greater than the first threshold.

[0062] In some embodiments, a blockchain system may pre-store Local Sensitive Hash Digests (LSHDs) of multiple data sets and bind the data owner to the LSHD of that data to indicate that the data owner has ownership of the LSHD. For example, if a target object owns target data, the blockchain system can bind the target object to the LSHD of the target data to indicate that the target data is owned by the target object.

[0063] In some embodiments, after local hash digest processing, data with high similarity may have the same local sensitive hash digest. Therefore, by matching local sensitive hash digests, it is simple and convenient to determine whether there is data similar to the first data in the blockchain system. If so, the first data can be considered similar to data that has already been claimed in the blockchain. That is, the first data may be the already claimed data, or it may be generated after simple tampering with the already claimed data. In this case, the first data should also be owned by the data owner of the similar data.

[0064] Therefore, if a second data with a similarity greater than a first threshold to the first data is identified among multiple data using the first local sensitive hash digest, it can be assumed that the data owner of the second data also owns the first data.

[0065] Step S606: Determine the owner of the second data based on the ownership relationship.

[0066] In some embodiments, the blockchain has already bound the data owner to the data they own through a sensitive hash digest, so the data owner of the second data can be determined through this ownership relationship.

[0067] Step S608: Determine that the second data owner owns the first data.

[0068] Because the local sensitive hash of the first data is the same as that of the second data, the similarity between the first data and the second data is greater than the preset threshold. Therefore, it can be considered that the first data is obtained by simply modifying the second data (or by not modifying it at all). Therefore, the owner of the second data should also have ownership of the first data.

[0069] Blockchain technology is a technical solution that stores, verifies, transmits, and exchanges network data without relying on third parties, and features decentralization, immutability, traceability, transparency, and no need for third-party endorsement.

[0070] The technical solution provided in this embodiment utilizes blockchain technology to implement a user identity management scheme during multi-party data transactions or sharing, thereby resolving the multi-party trust issue. Secondly, this embodiment uses Local Sensitive Hash (LSH) technology to process the data and store it on the blockchain as a data fingerprint, clearly defining data ownership.

[0071] Figure 7 This is a flowchart illustrating a data ownership confirmation process according to an example.

[0072] The data ownership confirmation method provided in this embodiment can be executed before receiving the ownership confirmation request for the first data sent by the data verification party. (See reference...) Figure 7 The above-mentioned method for confirming property rights may include the following steps.

[0073] Step S702: Receive the data ownership confirmation transaction sent by the second data owner for the second data. The data ownership confirmation transaction carries the second local sensitive hash digest corresponding to the second data.

[0074] In this context, the confirmation of data ownership for the second data can refer to requesting confirmation of ownership of the second data.

[0075] Step S704: Match the second local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system to determine that there is no data in the target blockchain system whose similarity to the second data exceeds the second threshold.

[0076] In some embodiments, step S706 can be executed after a match is completed on the blockchain using the second local sensitive hash digest and it is determined that the second data has not completed the ownership confirmation operation in the blockchain system.

[0077] If the second local sensitive hash digest does not exist in the blockchain system, it is considered that the second data has not been confirmed in the blockchain system, that is, the second data is not owned by other objects, and the blockchain system will execute step S706.

[0078] Step S706: Determine the ownership relationship between the second local sensitive hash digest and the second data owner.

[0079] In some embodiments, a second local sensitive hash digest can be bound to a second data owner to generate a corresponding ownership relationship.

[0080] Step S708: Store the second local sensitive hash digest and the ownership relationship of the second data owner on the blockchain to determine that the second data owner has ownership of the second data.

[0081] In some embodiments, the ownership relationship between the second local sensitive hash digest and the second data owner can be stored on the blockchain to complete the confirmation of ownership of the second data by the second data owner.

[0082] Step S710: Match the second local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system to determine that there is data in the target blockchain system whose similarity to the second data exceeds the second threshold.

[0083] In some embodiments, if it is determined that a second local sensitive hash digest has already been stored in the blockchain system, then it is determined that among the multiple data in the target blockchain system, there is data whose similarity to the second data exceeds a second threshold. In other words, the second data corresponding to the second local sensitive hash digest has been confirmed by other objects in the blockchain.

[0084] Step S712: Send a data ownership confirmation transaction failure notification to the second data owner to indicate that the second data has been confirmed.

[0085] The technical solution provided in this application represents data through Local Sensitive Hash (LSH), binds the LSH to the data owner, and stores it in the blockchain. This enables the data owner to confirm their ownership of the data, thereby improving the authority and fairness of data ownership confirmation. On the other hand, using the blockchain to confirm data ownership makes the data transaction / sharing process transparent and allows for auditing and traceability of data security and compliance.

[0086] Furthermore, traditional blockchain-based methods for uploading data fingerprints involve performing ordinary hash operations (such as SHA-256) on the source data. If the source data of the data owner is simply tampered with, its data fingerprint will no longer match the ownership proof on the blockchain. This means that after the data owner shares the source data, a malicious attacker can easily claim ownership by simply modifying it, posing a new challenge to data ownership protection. This application employs Locality Sensitive Hashing (LSH) to extract data digests, ensuring that similar data largely maps to the same digest. Therefore, during data ownership confirmation, if two pieces of data are found to share the same LSH digest, they can be considered highly likely to be similar, or their similarity exceeds a certain threshold, thus indicating that the two pieces of data belong to the same owner. This prevents unauthorized attackers from easily modifying and using certain data.

[0087] This application establishes a distributed user identity management scheme using blockchain technology. All participants in data transactions / sharing join the blockchain network as blockchain nodes, completing identity registration and obtaining authentication certificates and public / private key pairs. Blockchain technology can solve trust issues between multiple parties. Furthermore, due to the traceability of blockchain, key steps in the data transaction / sharing process can be recorded on the chain, ensuring full traceability and auditability. Simultaneously, the hash value generated by the LSH algorithm is used as a data fingerprint to confirm data ownership, enabling better matching of similar data from the same source and timely detection of data infringement issues.

[0088] Figure 8 This is a flowchart illustrating a data acquisition method according to an exemplary embodiment.

[0089] The data acquisition method provided in this embodiment can be executed before receiving a request for ownership confirmation of the first data sent by the data verification party.

[0090] In some embodiments, Figure 6 In the illustrated embodiment, the data verification party can be the data requester.

[0091] refer to Figure 8 The above data acquisition method may include the following steps.

[0092] Step S802: Receive the data request sent by the data requester.

[0093] In some embodiments, a data requirement request may include a data requirement statement issued by the data requester to indicate that the data requester needs the right to use data that meets the data requirement statement.

[0094] Step S804: Broadcast the data request to each node in the target blockchain, including the first node controlled by the first data owner.

[0095] In some embodiments, when the first data owner receives a data request from the data requester and finds that its own first data meets the aforementioned data requirement description, the first data owner will send the data description information of the first data to the blockchain system. The blockchain system receives the data description information of the first data sent by the first data owner in response to the data requirement description through the first node; and sends the data description information of the first data to the data requester so that the data requester can determine whether the first data meets the required data requirement description.

[0096] The data requester will obtain the data description information for the first data sent by the first data owner through the blockchain system to determine whether the first data is the data they want. After the data requester determines that the first data is the data they want, they will send a response information for the data description information for the first data to the blockchain. The blockchain system will receive the response information for the data description information for the first data from the data requester and then send the response information to the first data owner so that the first data owner can respond to the data request by sending a data provision response carrying the first data interface.

[0097] Step S806: The first node receives a data provision response sent by the first data owner in response to the data request, the data provision response carrying the first data interface.

[0098] Step S808: The data provider response sent by the data owner is sent to the data requester so that the data requester can obtain the first data according to the first data interface.

[0099] In some embodiments, after obtaining the first data through the first data interface, the data requester may initiate a confirmation request to the blockchain system to determine whether the ownership of the first data is held by the data owner, or to determine whether the first data meets their data requirement description.

[0100] In some embodiments, the blockchain system receives an ownership confirmation request for first data sent by a data verification party. The ownership confirmation request carries a first local sensitive hash digest of the first data, which is obtained by performing local sensitive hash processing on the first data. The system then matches the first local sensitive hash digest with local sensitive hash digests of multiple data stored in the blockchain system to identify a second data among the multiple data whose similarity to the first data is greater than a first threshold. Based on the ownership relationship, the system determines the owner of the second data and confirms that the owner of the second data owns the first data.

[0101] In some embodiments, if the second data owner is the same as the first data owner in this embodiment, then it can be confirmed that the first data is owned by the first data owner.

[0102] In some embodiments, the blockchain system may store first data, and the data request may include a data requirement description, which describes the characteristics of the data that the data requester wants to obtain (such as data source, number of data, data size, data time limit, data acquisition time, etc.).

[0103] After receiving a request from a data verification party to confirm ownership of the first data, the blockchain will determine whether the first data meets the data requirement specifications. If the first data meets the data requirement specifications, it will match the first local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system, and determine the second data among the multiple data whose similarity to the first data is greater than a first threshold. If the first data does not meet the data requirement specifications, it will send a risk warning to the data requester that the data does not meet the requirements.

[0104] Figure 9 This is a schematic diagram of a data ownership structure according to an exemplary embodiment.

[0105] This embodiment proposes a blockchain-based data ownership confirmation method, replacing the original centralized data ownership confirmation mechanism with blockchain. It proposes a user identity management scheme using blockchain to solve the multi-party trust problem in data transactions / sharing processes. Simultaneously, it utilizes the LSH algorithm to implement a data fingerprinting method on the blockchain.

[0106] This embodiment is divided into two stages: the user registration and certificate acquisition stage, and the data ownership confirmation stage.

[0107] All participants in data transactions / sharing join the blockchain network as blockchain nodes, completing identity registration, certificate acquisition, and generating public-private key pairs for subsequent identity authentication and communication encryption. The process is as follows: Figure 5 As shown, the specific steps are as follows: 1. Blockchain 504 receives a registration request from a user (e.g., data requester 501, data owner 502, or data regulator 503), the registration request carrying a registration public key and user ID; 2. In response to the registration request, Blockchain 504 sends a request to the user to obtain identity attribute information encrypted with the registration public key; 3. The user obtains the user public key userPK and user private key useresk through processing; 4. Blockchain 504 receives a response from the second data owner, containing identity attribute information encrypted with the registration public key, this response carrying the user's identity attribute information and user public key; 5. Blockchain 504 binds the user ID with the user's corresponding identity attribute information and generates an identity certificate userCert for the user; 6. Blockchain 504 processes the identity attribute information and identity certificate on the blockchain so that when the second user sends a data ownership confirmation transaction for the second data, the identity of the second user can be verified, and the user certificate is returned to the user.

[0108] In some embodiments, the architecture diagram for the data ownership confirmation stage is as follows: Figure 9 As shown, it can be divided into four parts: data owner 901, 902, or 903; data requester 906; data regulator 907; and blockchain network 908. The specific details are as follows: (a) Data Ownership 901, 902, or 903 mainly includes three modules: (1) Extracting digital fingerprints based on the Locality Sensitive Hash (LSH) algorithm: The LSH algorithm can perform fast similarity matching on massive high-dimensional data. In data ownership confirmation scenarios, data owners can perform LSH hash calculations on their data assets and save the calculation results as data fingerprints on the blockchain. In subsequent data transactions, if malicious attackers simply tamper with the data owner's data and apply it to other improper scenarios to illegally seek economic benefits, similarity matching using the LSH algorithm can promptly detect such behavior, thereby better protecting the rights and interests of data owners.

[0109] (2) Submit data ownership confirmation transaction: Store the data fingerprint on the blockchain and initiate a data ownership confirmation transaction. The result is written into the transaction block.

[0110] (3) Data encryption: Encrypt the data transmission process to ensure the confidentiality of the data.

[0111] (II) Data Requester 906 mainly includes three modules: (1) Submit data requirements: Initiate a data transaction through a smart contract and submit a description of the data requirements.

[0112] (2) Data encryption: Encrypt the data transmission process to ensure the confidentiality of the data.

[0113] (3) Data calculation: Analyze and process the acquired transaction / shared data.

[0114] The blockchain network mainly consists of four modules: data ownership preservation, user identity management, data transaction / sharing process recording, and regulatory interface.

[0115] (iii) Data regulator 907 connects to the blockchain as a regulatory node and supervises and audits the entire process of data transaction / sharing.

[0116] refer to Figure 9 The data ownership confirmation process described above may include the following steps: 1) The data owner extracts fingerprints using the LSH algorithm and initiates a data ownership confirmation transaction to the blockchain.

[0117] 2) Each node in the blockchain first verifies whether the identity certificate of the data owner is valid. If it is valid, the node accepts the transaction and broadcasts it to other nodes in the vicinity.

[0118] 3) If no node objects to the modified transaction within a certain period of time, it will eventually be updated into the blockchain block, confirming that the data ownership belongs to the data owner.

[0119] Once data ownership is clearly defined, subsequent data trading / sharing processes can proceed, and key steps will be stored on the blockchain to facilitate oversight and auditing of these processes by regulatory nodes.

[0120] The advantages and effects of this application compared to the prior art.

[0121] Decentralized. The data ownership confirmation method proposed in this invention does not require third-party endorsement, thus solving the problems of authority and fairness in centralized ownership confirmation systems.

[0122] A data ownership confirmation method applicable to big data scenarios. A data ownership confirmation mechanism based on the LSH algorithm and blockchain can promptly detect data infringement activities involving the tampering of data from the same source.

[0123] Auditable. Key steps in data transactions / sharing are recorded on the blockchain. Blockchain's traceability and immutability meet the regulatory and auditing requirements of relevant authorities.

[0124] Figure 10 This is a block diagram illustrating a blockchain-based data processing apparatus according to an exemplary embodiment. (Refer to...) Figure 10 The blockchain-based data processing device 1000 provided in this embodiment may include: an ownership confirmation request acquisition module 1001, a digest matching module 1002, a data owner determination module 1003, and an ownership relationship determination module 1004.

[0125] The ownership confirmation request acquisition module 1001 can be used to receive an ownership confirmation request for the first data sent by the data verification party. The ownership confirmation request carries a first local sensitive hash digest of the first data, which is obtained by performing local sensitive hash processing on the first data. The digest matching module 1002 can be used to match the first local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system, and determine the second data among the multiple data whose similarity to the first data is greater than a first threshold. The data owner determination module 1003 can be used to determine the owner of the second data according to the ownership relationship. The ownership relationship determination module 1004 can be used to determine that the owner of the second data owns the first data.

[0126] In some embodiments, the blockchain-based data processing device further includes: a data ownership confirmation transaction acquisition module, a first digest matching module, an ownership relationship determination module, and an on-chain storage module.

[0127] The data ownership confirmation transaction acquisition module is used to receive a data ownership confirmation transaction sent by the second data owner for the second data before receiving the ownership confirmation request for the first data sent by the data verification party. The data ownership confirmation transaction carries a second local sensitive hash digest corresponding to the second data. The first digest matching module is used to match the second local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system to determine that there is no data in the target blockchain system whose similarity to the second data exceeds a second threshold. The ownership relationship determination module is used to determine that there is an ownership relationship between the second local sensitive hash digest and the second data owner. The on-chain storage module is used to store the ownership relationship between the second local sensitive hash digest and the second data owner on the blockchain to determine that the second data owner owns the second data.

[0128] In some embodiments, the blockchain-based data processing device further includes a second digest matching module and a transaction failure notification module.

[0129] The second digest matching module is used to match the second local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system to determine that there is data in the target blockchain system whose similarity to the second data exceeds the second threshold; the transaction failure prompt module is used to send a data ownership confirmation transaction failure prompt to the owner of the second data to indicate that the ownership of the second data has been confirmed.

[0130] In some embodiments, the data verification party is the data requester; wherein, the blockchain-based data processing device further includes: a data request acquisition module, a broadcast module, a data provision response acquisition module, and a data provision response forwarding module.

[0131] The data request acquisition module is used to receive a data request sent by a data requester before receiving a request for ownership confirmation of the first data sent by a data verification party; the broadcast module is used to broadcast the data request to each node in the target blockchain, including the first node controlled by the first data owner; the data provision response acquisition module is used to receive the data provision response sent by the first data owner in response to the data request through the first node, and the data provision response carries the first data interface; the data provision response forwarding module is used to send the data provision response sent by the data owner to the data requester so that the data requester can obtain the first data according to the first data interface.

[0132] In some embodiments, the data requirement request carries a data requirement description; wherein, the summary matching module 1002 may include: a data requirement matching unit, a satisfaction judgment unit, and a non-satisfaction judgment unit.

[0133] The data requirement matching unit can be used to determine whether the first data meets the data requirement description; the satisfaction judgment unit can be used to match the first local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system if the first data meets the data requirement description, and determine the second data with a similarity greater than the first data among the multiple data; the non-satisfaction judgment unit can be used to send a risk warning that the data does not meet the requirements to the data requester if the first data does not meet the data requirement description.

[0134] In some embodiments, the data request carries a data request description; wherein, the blockchain-based data processing device further includes: a data description information acquisition module, a data description information forwarding module, a response information acquisition module, and a response information forwarding module.

[0135] The data description information acquisition module can be used to receive, after broadcasting the data request to each node in the target blockchain, the data provision response sent by the first data owner in response to the data request, before receiving the data provision response carrying the first data interface through the first node, and the data provision response carrying the first data interface. The data description information forwarding module can be used to send the data description information for the first data to the data requester so that the data requester can determine whether the first data meets the data requirement description. The response information acquisition module can be used to receive the response information of the data requester regarding the data description information for the first data. The response information forwarding module can be used to send the response information to the first data owner so that the first data owner can send a data provision response carrying the first data interface in response to the data request.

[0136] In some embodiments, the blockchain-based data processing device further includes: a registration request acquisition module, an identity attribute information acquisition request module, an identity attribute information acquisition module, an information binding module, and an on-chain module.

[0137] The system includes the following modules: a registration request acquisition module, which receives a registration request from the second data owner before receiving a request from the data verification party to confirm ownership of the first data; an identity attribute information acquisition request module, which responds to the registration request by sending an identity attribute information acquisition request encrypted with the registration public key to the second data owner; an identity attribute information acquisition module, which receives an identity attribute information response encrypted with the registration public key from the second data owner; an information binding module, which binds the second data owner with its corresponding identity attribute information and generates an identity certificate for the second data owner; and an on-chain module, which processes the identity attribute information and identity certificate on-chain so that the identity of the second data owner can be verified when the second data owner sends a data ownership confirmation transaction for the second data.

[0138] Since the functions of the device 1000 have been described in detail in their respective method embodiments, they will not be repeated here.

[0139] The modules and / or sub-units described in the embodiments of this application can be implemented in software or hardware. The described modules and / or sub-units can also be located in a processor. The names of these modules and / or sub-units do not, in some cases, constitute a limitation on the module and / or sub-unit itself.

[0140] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0141] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this disclosure and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0142] Figure 11 A schematic diagram of an electronic device suitable for implementing embodiments of the present disclosure is shown. It should be noted that... Figure 11 The illustrated electronic device 1100 is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0143] like Figure 11 As shown, the electronic device 1100 includes a central processing unit (CPU) 1101, which can perform 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. The RAM 1103 also stores various programs and data required for the operation of the electronic device 1100. The CPU 1101, ROM 1102, and RAM 1103 are interconnected via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0144] The following components are connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1108 including a hard disk, etc.; and a communication section 1109 including a network interface card such as a LAN card, modem, etc. The communication section 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to I / O interface 1105 as needed. Removable media 1111, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1110 as needed so that computer programs read from them can be installed into storage section 1108 as needed.

[0145] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1109, and / or installed from removable medium 1111. When the computer program is executed by central processing unit (CPU) 1101, it performs the functions defined above in the system of this application.

[0146] It should be noted that the computer-readable storage medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable storage medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable storage medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0147] In another aspect, this application also provides a computer-readable storage medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable storage medium carries one or more programs, which, when executed by the device, enable the device to perform the following functions: receiving an ownership confirmation request for first data sent by a data verification party, the ownership confirmation request carrying a first local sensitive hash digest of the first data, the first local sensitive hash digest being obtained after performing local sensitive hash processing on the first data; matching the first local sensitive hash digest with local sensitive hash digests of multiple data stored in the blockchain system, and determining, among the multiple data, a second data whose similarity to the first data is greater than a first threshold; determining, based on the ownership relationship, a second data owner who owns the second data; and determining that the second data owner owns the first data.

[0148] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional implementations of the above embodiments.

[0149] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions of the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or smart device, etc.) to execute the method according to the embodiments of this disclosure, for example... Figure 6 , Figure 7 ,or Figure 8 One or more of the steps shown.

[0150] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0151] It should be understood that this disclosure is not limited to the detailed structures, drawing arrangements or implementations shown herein; rather, this disclosure is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A data processing method based on blockchain, characterized in that, The method is executed by a target node in the target blockchain system, which stores local sensitive hash digests of multiple data items and the ownership relationships between each local sensitive hash digest and the corresponding data owner, including: The system receives a request for ownership confirmation of the first data from a data verification party. The ownership confirmation request carries a first local sensitive hash digest of the first data, which is obtained by performing local sensitive hash processing on the first data. The first local sensitive hash digest is matched with the local sensitive hash digests of multiple data stored in the blockchain system, and a second data with a similarity greater than a first threshold is determined from the multiple data. The ownership party of the second data is determined based on the aforementioned ownership relationship; It is determined that the owner of the second data owns the first data; The method further includes, prior to receiving the ownership confirmation request for the first data sent by the data verification party: Receive a data ownership confirmation transaction sent by the owner of the second data for the second data, the data ownership confirmation transaction carrying a second local sensitive hash digest corresponding to the second data; The second local sensitive hash digest is matched with the local sensitive hash digests of multiple data stored in the blockchain system to determine that there is no data in the multiple data of the target blockchain system whose similarity to the second data exceeds the second threshold; It is determined that there is an ownership relationship between the second local sensitive hash digest and the owner of the second data; The second local sensitive hash digest and the ownership relationship of the second data owner are stored on the blockchain to determine that the second data owner has ownership of the second data; The method further includes, prior to receiving the ownership confirmation request for the first data sent by the data verification party: Receive a registration request from the second data owner, the registration request carrying a registration public key; In response to the registration request, a request to obtain identity attribute information encrypted with the registration public key is sent to the second data owner; Receive the identity attribute information response sent by the second data owner, which is encrypted with the registered public key. The identity attribute information response carries the identity attribute information of the second data owner and the public key of the second data owner. Bind the second data owner to the identity attribute information corresponding to the second data owner, and generate an identity certificate for the second data owner; The identity attribute information and the identity certificate are processed on the blockchain so that the identity of the second data owner can be verified when the second data owner sends a data ownership confirmation transaction for the second data.

2. The method according to claim 1, characterized in that, The method further includes: The second local sensitive hash digest is matched with the local sensitive hash digests of multiple data stored in the blockchain system to determine that there is data in the target blockchain system whose similarity to the second data exceeds the second threshold; A data ownership confirmation transaction failure notification is sent to the second data owner to indicate that the second data has been confirmed as owned.

3. The method according to claim 1, characterized in that, The data verification party is the data requester; wherein, before receiving the ownership confirmation request for the first data sent by the data verification party, the method further includes: Receive the data request sent by the data requester; The data request is broadcast to each node in the target blockchain, including a first node controlled by the first data owner. The first node receives a data provision response sent by the first data owner in response to the data request, the data provision response carrying the first data interface; The data owner sends a response to the data requester, so that the data requester can obtain the first data according to the first data interface.

4. The method according to claim 3, characterized in that, The data request carries a data requirement description; wherein, the first Local Sensitive Hash Digest is matched with the Local Sensitive Hash Digests of multiple data stored in the blockchain system, and a second data with a similarity greater than a first threshold is determined from the multiple data, including: Determine whether the first data meets the data requirement description; If the first data meets the data requirement description, then the first local sensitive hash digest is matched with the local sensitive hash digests of multiple data stored in the blockchain system, and a second data with a similarity greater than a first threshold is determined from the multiple data. If the first data does not meet the data requirement description, a risk warning that the data does not meet the requirements will be sent to the data requester.

5. The method according to claim 3, characterized in that, The data request carries a data request description; wherein, after broadcasting the data request to each node in the target blockchain, and before receiving a data provision response from the first data owner in response to the data request via the first node, wherein the data provision response carries a first data interface, the method further includes: The first node receives data description information for the first data in response to the data requirement statement sent by the first data owner. The data description information for the first data is sent to the data requester so that the data requester can determine whether the first data meets the data requirement description. Receive response information from the data requester regarding the data description information of the first data; The response information is sent to the first data owner so that the first data owner can send a data provision response carrying the first data interface in response to the data request.

6. A data processing device based on blockchain, characterized in that, The device is deployed on a target node in the target blockchain system, which stores local sensitive hash digests of multiple data and the ownership relationships between each local sensitive hash digest and the corresponding data owner, including: The ownership confirmation request acquisition module is used to receive an ownership confirmation request for first data sent by a data verification party. The ownership confirmation request carries a first local sensitive hash digest of the first data, which is obtained by performing local sensitive hash processing on the first data. The digest matching module is used to match the first locality sensitive hash digest with the locality sensitive hash digests of multiple data stored in the blockchain system, and determine the second data among the multiple data whose similarity to the first data is greater than a first threshold; A data ownership determination module is used to determine the second data owner who owns the second data based on the ownership relationship; The ownership relationship determination module is used to determine whether the owner of the second data owns the first data. Blockchain-based data processing devices also include: The data ownership confirmation transaction acquisition module is used to receive a data ownership confirmation transaction sent by the second data owner for the second data before receiving the ownership confirmation request for the first data sent by the data verification party. The data ownership confirmation transaction carries a second local sensitive hash digest corresponding to the second data. The first digest matching module is used to match the second local sensitive hash digest with the local sensitive hash digests of multiple data stored in the blockchain system, and determine that there is no data in the multiple data of the target blockchain system whose similarity to the second data exceeds a second threshold; The ownership determination module is used to determine whether there is an ownership relationship between the second local sensitive hash digest and the second data owner; The on-chain storage module is used to store the second local sensitive hash digest and the ownership relationship of the second data owner on the chain to determine that the second data owner has ownership of the second data; Blockchain-based data processing devices also include: The registration request acquisition module is used to receive a registration request sent by the second data owner before receiving the ownership confirmation request for the first data sent by the data verification party. The registration request carries a registration public key. The identity attribute information acquisition request module is used to send an identity attribute information acquisition request encrypted with the registration public key to the second data owner in response to the registration request. The identity attribute information acquisition module is used to receive an identity attribute information response encrypted with the registration public key sent by the second data owner, 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; The information binding module is used to bind the second data owner with the identity attribute information corresponding to the second data owner and generate an identity certificate for the second data owner. The on-chain module is used to process the identity attribute information and the identity certificate on the blockchain so as to verify the identity of the second data owner when the second data owner sends a data ownership confirmation transaction for the second data.

7. An electronic device, characterized in that, include: Memory; as well as A processor coupled to the memory, the processor being used to execute the blockchain-based data processing method as described in any one of claims 1-5, based on instructions stored in the memory.

8. A computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the blockchain-based data processing method as described in any one of claims 1-5.

Images