Block chain data processing method, platform, system and device and electronic equipment
Patent Information
- Application Number
- CN202380008554.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-31
- Publication Date
- 2024-12-03
Smart Images

Figure CN119072898A_ABST
Abstract
Description
Blockchain data processing method, platform, system, device and electronic device Technical Field
[0001] The present disclosure relates to the field of blockchain technology, and more specifically, to a blockchain data processing method, platform, system, device, electronic device, and storage medium. Background Art
[0002] Blockchain is a distributed ledger composed of sequentially linked data blocks in chronological order, ensuring immutability and forgery through cryptographic means. On-chain data within a blockchain network is isolated, preventing interoperability between different blockchains. This hinders the development of data application ecosystems across different blockchains. To improve the utilization of blockchain data, cross-chain data processing methods can be used to enable data sharing between blockchains.
[0003] Summary of the Invention
[0004] The present disclosure provides a blockchain data processing method, platform, system, device, electronic device, and storage medium.
[0005] According to one aspect of the present disclosure, a blockchain data processing method is provided, comprising: in response to receiving a data processing request from a first client device, obtaining at least one first blockchain data from a first blockchain network based on object identification information carried in the data processing request; confirming the ownership of the first client device based on the encrypted verification information carried in the data processing request; and upon determining that the first client device has completed the ownership confirmation, sending the at least one first blockchain data to the first client device, so that the first client device decrypts the at least one first blockchain data using a block body private key corresponding to each of the at least one first blockchain data to obtain at least one second blockchain data.
[0006] According to another aspect of the present disclosure, a blockchain data processing platform is provided, including: a blockchain data source management module, configured to, in response to receiving a data processing request from a first client device, obtain at least one first blockchain data from a first blockchain network based on object identification information carried in the data processing request; a private key control module, configured to confirm the ownership of the first client device based on the encrypted verification information carried in the data processing request; and a data processing module, configured to, upon determining that the first client device has completed the confirmation of ownership, send the at least one first blockchain data to the first client device, so that the first client device decrypts the at least one first blockchain data using the block body private key corresponding to each of the at least one first blockchain data to obtain at least one second blockchain data.
[0007] According to another aspect of the present disclosure, a blockchain data processing system is provided, comprising: a first client device, a first blockchain network, a blockchain data processing platform, and a distributed private key network; wherein the blockchain data processing platform is configured to: in response to receiving a data processing request from the first client device, obtain at least one first blockchain data from the first blockchain network based on object identification information carried in the data processing request; confirm the ownership of the first client device based on the encrypted verification information carried in the data processing request; and send the at least one first blockchain data to the first client device when it is determined that the first client device has completed the ownership confirmation; the first client device is configured to: decrypt the at least one first blockchain data using the block body private key corresponding to each of the at least one first blockchain data to obtain at least one second blockchain data.
[0008] According to another aspect of the present disclosure, a blockchain data processing device is provided, including: a first acquisition module, configured to, in response to receiving a data processing request from a first client device, acquire at least one first blockchain data from a first blockchain network based on object identification information carried in the data processing request; a rights confirmation module, configured to confirm the rights of the first client device based on the encrypted verification information carried in the data processing request; and a first sending module, configured to, upon determining that the first client device has completed the rights confirmation, send the at least one first blockchain data to the first client device, so that the first client device decrypts the at least one first blockchain data using a block body private key corresponding to each of the at least one first blockchain data to obtain at least one second blockchain data.
[0009] According to another aspect of the present disclosure, an electronic device is provided, including a memory and a processor, wherein instructions executable by the processor are stored in the memory, and when the instructions are executed by the processor, the processor executes the method described above.
[0010] According to another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable a computer to execute and implement the method described above.
[0011] According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program, which implements the method described above when executed by a processor.
[0012] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The accompanying drawings are provided to facilitate a better understanding of the present invention and do not constitute a limitation of the present disclosure.
[0014] FIG1 schematically illustrates an exemplary system architecture to which a blockchain data processing method according to an embodiment of the present disclosure may be applied.
[0015] FIG2 schematically shows a flowchart of a blockchain data processing method according to an embodiment of the present disclosure.
[0016] FIG3 schematically shows a flowchart of a blockchain data processing method according to another embodiment of the present disclosure.
[0017] FIG4 schematically shows a flowchart of a blockchain data processing method according to another embodiment of the present disclosure.
[0018] FIG5A schematically shows a schematic diagram of a method for asynchronously viewing blockchain data according to an embodiment of the present disclosure.
[0019] FIG5B schematically illustrates a method for synchronously viewing blockchain data according to an embodiment of the present disclosure.
[0020] FIG6 schematically shows a schematic diagram of a blockchain data sharing method according to an embodiment of the present disclosure.
[0021] FIG7 schematically shows a schematic diagram of a blockchain data calling method according to an embodiment of the present disclosure.
[0022] FIG8 schematically shows a block chain data processing platform according to an embodiment of the present disclosure.
[0023] FIG9 schematically shows a block chain data processing system according to an embodiment of the present disclosure.
[0024] FIG10 schematically shows a block diagram of a blockchain data processing device according to an embodiment of the present disclosure.
[0025] FIG11 schematically shows a block diagram of an electronic device suitable for implementing a blockchain data processing method according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0026] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the detailed description below, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.
[0027] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise," "include," etc. used herein indicate the presence of the features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.
[0028] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.
[0029] When expressions such as “at least one of A, B, and C, etc.” are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (e.g., “a system having at least one of A, B, and C” should include but is not limited to systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, and C, etc.). When expressions such as “at least one of A, B, or C, etc.” are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (e.g., “a system having at least one of A, B, or C” should include but is not limited to systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, and C, etc.).
[0030] In the technical solutions disclosed herein, the collection, storage, use, processing, transmission, provision, disclosure and application of the data involved (including but not limited to user personal information) comply with the provisions of relevant laws and regulations, take necessary confidentiality measures, and do not violate public order and good morals.
[0031] In the technical solution disclosed herein, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.
[0032] It should be noted that, unless it is explicitly stated that there is a sequence of execution between different operations shown in the flowchart in the embodiments of the present disclosure, or there is a sequence of execution between different operations in technical implementation, otherwise, the execution order between multiple operations may not be prioritized, and multiple operations may also be executed simultaneously.
[0033] To adapt to the demands of information technology development and business expansion, enterprises typically develop business information systems, such as ERP (Enterprise Resource Planning), Office Automation (OA), and Customer Relationship Management (CRM). These systems can standardize business processes and establish standardized business models. They also aggregate business data within system databases, accumulating data assets for the enterprise. Simultaneously, with increasing public concern about data privacy, blockchain, with its decentralized, tamper-proof, and encrypted storage capabilities, is gradually replacing system databases as the storage unit for business information systems. However, on-chain data within blockchain networks is isolated, preventing interoperability and unified utilization across different blockchains. This has hindered the further development of a data application ecosystem across different blockchains.
[0034] Taking the medical blockchain as an example, the development of medical data presents numerous challenges, including the inability of institutions to quickly and conveniently share data. Hospital systems and software are largely developed and maintained by third-party software companies, a market characterized by a mixed bag of quality and vulnerability, while medical data is highly private and valuable. Furthermore, disputes exist regarding the ownership and access rights of medical data. Related technologies typically store medical data directly on the blockchain, significantly increasing network costs and making throughput a bottleneck hindering technological development. Furthermore, there is confusion over data ownership, meaning even patients cannot fully own their medical data. Storing medical data in hospitals complicates data sharing procedures, making large-scale data sharing impractical.
[0035] In view of this, embodiments of the present disclosure provide a blockchain data processing method. In response to receiving a data processing request from a first client device, the method comprises: obtaining at least one first blockchain data from a first blockchain network based on object identification information carried in the data processing request; confirming the ownership of the first client device based on encrypted verification information carried in the data processing request; and, upon determining that the first client device has completed the ownership confirmation, sending the at least one first blockchain data to the first client device so that the first client device decrypts the at least one first blockchain data using a block body private key corresponding to each of the at least one first blockchain data to obtain at least one second blockchain data.
[0036] To facilitate understanding, relevant concepts involved in the embodiments of the present disclosure are first described below.
[0037] Blockchain is a solution that uses a chained data structure to verify and store data, a distributed node consensus algorithm to generate and update data, cryptography to ensure secure data transmission and access, and smart contracts composed of automated script code to collectively maintain a reliable database. Therefore, blockchain has fundamental characteristics such as openness, decentralization, information sharing, tamper-proofing, and traceability. Blockchain can replace reliance on centralized servers with blocks.
[0038] A block is a container data structure that aggregates data and is included in a blockchain. A block can include a block header and a block body. The block header may include a version, timestamp, parent block hash, nonce, difficulty coefficient, and Merkle root. The timestamp indicates the moment the block was created. The parent block hash can be used to reference the previous block. The block body may include transaction details, a transaction counter, and the block size.
[0039] Smart contracts are executable code stored on the blockchain. This executable code defines the smart contract's execution conditions and business processing logic. Specifically, it defines the conditions for initiating the smart contract and how to handle business processing requests received after the smart contract is activated. Once stored on the blockchain, smart contracts are difficult to edit or modify. For example, the execution of a smart contract can be triggered by events. For example, the execution of a smart contract is recorded as a transaction on the blockchain and is recorded there.
[0040] Based on the scope of the network, blockchains can be categorized as public, private, consortium, and hybrid. A consortium chain is a blockchain jointly participated in and managed by several organizations, each of which can operate at least one blockchain node. Consortium chain data is only accessible to organizations within the consortium chain system for reading, writing, and transacting. Digital certificates are used to implement a PKI (Public Key Infrastructure)-based identity management system, initiate transactions, or initiate proposals, and reach consensus through joint signature verification by participating parties. In the disclosed embodiments, the type of blockchain can be determined based on actual business needs and is not limited here. For example, the blockchain network is a consortium chain.
[0041] A blockchain network can include multiple blockchain nodes. Blockchain nodes communicate via peer-to-peer (P2P) networking. Blockchain nodes can act as both clients and servers, requesting services from other nodes and providing services to other nodes or external applications.
[0042] Figure 1 schematically illustrates an exemplary system architecture to which the blockchain data processing method according to an embodiment of the present disclosure can be applied. It should be noted that Figure 1 is merely an example of a system architecture to which the present disclosure embodiment can be applied, to help those skilled in the art understand the technical content of the present disclosure, and does not imply that the present disclosure embodiment cannot be applied to other devices, systems, environments, or scenarios.
[0043] As shown in FIG1 , the system architecture 100 according to this embodiment may include a terminal device 101 , a server 102 , and a blockchain network 103 .
[0044] The terminal device 101 may be any electronic device with a display screen, including but not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, and the like.
[0045] Server 102 can be any type of server that provides various services. For example, a server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system. It solves the management difficulties and poor business scalability of traditional physical hosts and VPS (Virtual Private Server) services. The server can also be an edge server. The server can also be a server in a distributed system or a server integrated with blockchain.
[0046] The blockchain network 103 may include multiple blockchain nodes, each of which may be a client device or a server.
[0047] The server 102 and the terminal device 101, and the server 102 and each blockchain node of the blockchain network 103 can communicate through the network, and the network may include various connection types, such as wired and / or wireless communication links.
[0048] It should be noted that the blockchain data processing method provided in the embodiment of the present disclosure can generally be executed by the server 102. Accordingly, the blockchain data processing device provided in the embodiment of the present disclosure can also be set in the server 102.
[0049] For example, a user may perform input, selection, or other operations in a client application on terminal device 101. Terminal device 101 may generate a data processing request based on the input, selection, or other operations and send the data processing request to server 102. In response to receiving the data processing request from terminal device 101, server 102 may obtain the first blockchain data from blockchain network 103 based on the object identification information carried in the data processing request. Simultaneously, server 102 may verify the ownership of terminal device 101 based on the encrypted verification information carried in the data processing request. Upon determining that terminal device 101 has completed the verification, server 102 returns the first blockchain data to terminal device 101. Terminal device 101 may decrypt the first blockchain data using the block private key corresponding to the first blockchain data to obtain the second blockchain data.
[0050] It should be understood that the number of terminal devices, servers, and blockchain networks in Figure 1 is merely illustrative. Any number of terminal devices, servers, and blockchain networks may be used as needed.
[0051] FIG2 schematically shows a flowchart of a blockchain data processing method according to an embodiment of the present disclosure.
[0052] As shown in FIG. 2 , the method includes operations S210 to S230 .
[0053] In operation S210, in response to receiving a data processing request from a first client device, at least one first blockchain data is obtained from a first blockchain network based on object identification information carried in the data processing request.
[0054] In operation S220 , the first client device is authenticated based on the encrypted verification information carried in the data processing request.
[0055] In operation S230, when it is determined that the first client device has completed the right confirmation, the at least one first blockchain data is sent to the first client device, so that the first client device uses the block body private key corresponding to the at least one first blockchain data to decrypt the at least one first blockchain data and obtain at least one second blockchain data.
[0056] According to embodiments of the present disclosure, a client device may be an electronic device installed with various client applications. Client applications can be categorized into different types based on different classification perspectives. For example, based on the service functions provided by the client application, client applications can be categorized into personal client applications and service client applications. Personal client applications may refer to client applications that users use to perform business operations using the functions provided by the client application. Service client applications may refer to client applications that support users in performing business services. Based on the client application development framework, client applications can be categorized into program client applications and web client applications. Program client applications may refer to client applications that load application programs (APPs). Web client applications may refer to web client applications. Web client applications may include web browsers. Client applications can be categorized into registered client applications and unregistered client applications based on whether the user has registered. A registered client application may refer to a client application that the user has registered while using at least one of the functions provided by the client application itself and the functions provided by an application loaded into the client application. An unregistered client application may refer to a client application that the user has not registered while using either the functions provided by the client application itself or the functions provided by an application loaded into the client application. A program client application can be a personal client application, a service client application, a registered client application, or an unregistered client application. The web client application may be a personal client application, a service client application, a registered client application, or an unregistered client application.
[0057] According to embodiments of the present disclosure, a data processing request may be initiated by a first client device, or initiated by another client device and forwarded by the first client device, to obtain blockchain data from various blockchain networks. The data processing request may be generated by the client device based on user input, selection, or other operations. An input operation may, for example, be information input by a user using an input device such as a keyboard or microphone within an input control within a client application interface on the client device. A selection operation may, for example, be information selection by a user using a mouse, touch, or other means within a selection control within a client application interface on the client device. The first client device may send the data processing request to the blockchain data processing platform.
[0058] According to embodiments of the present disclosure, object identification information may refer to information uniquely identifying the requester of a data processing request. The requester of a data processing request may be the user who controls the client device to initiate the data processing request. Accordingly, the object identification information may include information such as the user's username, user ID, or user identification number.
[0059] According to an embodiment of the present disclosure, the first blockchain network may be a blockchain network created by a blockchain data processing platform, and the server-side device of the blockchain data processing platform may serve as at least a bookkeeping node of the first blockchain network. The type of the first blockchain network may include, but is not limited to, a public chain, a consortium chain, a private chain, a side chain, or a branch chain. Preferably, since the TPS (transactions per second) of a public chain network is significantly lower than that of a consortium chain network or a private chain network, for example, the TPS of the Ethereum blockchain is generally 20, while the TPS of a private chain can be close to 100,000, in order to improve the reading and writing efficiency of blockchain data, the type of the first blockchain network may be a consortium chain network or a private chain network, and accordingly, the server-side device of the blockchain data processing platform may serve as an authorized node in the consortium chain network or the private chain network.
[0060] According to an embodiment of the present disclosure, the blockchain data recorded in the first blockchain network may be user data originating from different data sources. After obtaining the user's authorization, the user data may be packaged into blocks and the blocks may be uploaded to the first blockchain network.
[0061] According to an embodiment of the present disclosure, obtaining the first blockchain data based on the object identification information can be performed by matching the object identification information with the relevant party identification in the block header of each block in the first blockchain network to determine the relevant target block, and the block body data of the relevant target block is the first blockchain data that needs to be obtained.
[0062] According to an embodiment of the present disclosure, the first blockchain data may include block body data of one or more blocks of the first blockchain network.
[0063] According to an embodiment of the present disclosure, the encrypted verification information may include information used to authenticate the identity and permissions of the first client device. For example, the encrypted verification information may include a username and password, biometric information, answers to preset specific questions, a password lock combination, etc. As an optional implementation, the encrypted verification information may be obtained by encrypting the above-mentioned types of information. For example, the above-mentioned types of information may be hashed, and the resulting hash value is the encrypted verification information. Furthermore, to ensure the security of the encrypted verification information during information transmission, the resulting hash value may be encrypted using a digital signature method, an encryption method, etc., thereby obtaining confidential verification information. After determining that the first client device has passed identity authentication based on the encrypted verification information, permission management methods such as DAC (Discretionary Access Control), MAC (Mandatory Access Control), RBAC (Role-based Access Control), etc. may be used to determine the permissions of the first client device. Permissions may include data access rights, data ownership, etc. For example, if the first client device is determined to have data access rights, the first blockchain data can be obtained from the first blockchain network, or the second blockchain data obtained by decrypting the first blockchain data can be obtained. If the first client device is determined to have data ownership rights, the first blockchain data in the first blockchain network can also be shared, modified, etc., if a sharing, modification, etc. request is received from the first client device.
[0064] According to an embodiment of the present disclosure, the second blockchain data may be plaintext data corresponding to the first blockchain data.
[0065] According to the embodiments of the present disclosure, the first client device can be authenticated based on the encrypted verification information. Once authentication is complete, it can be determined that the first client device has permission to access the first blockchain data, at which point the first blockchain data can be returned to the first client device. Through the aforementioned technical means, the data communication link between devices only transmits ciphertext data, and the blockchain private key used to decrypt the first blockchain data is not exposed to the public in either plaintext or ciphertext. This effectively ensures the security of blockchain network data and contributes to further data fidelity and tamper-proofing.
[0066] According to an embodiment of the present disclosure, a distributed private key network may be a distributed network composed of multiple nodes. The block-level private key generated when a user registers in the blockchain network may be distributedly stored on specific nodes of the distributed private key network. The storage format of the block-level private key in the distributed private key network is not limited. For example, the block-level private key may be divided into multiple sub-keys, each of which may be stored in a node. Alternatively, the block-level private key may be re-encrypted, the re-encrypted block-level private key stored in one node, and the key used for the re-encryption stored in another node.
[0067] According to an embodiment of the present disclosure, confirming the ownership of the first client device based on the encrypted verification information may include the blockchain data processing platform and the distributed private key network sequentially confirming the ownership of the first client device. Specifically, the encrypted verification information may be obtained by the first client device digitally signing private key summary information using the object private key, and the private key summary information may be obtained by the first client device concatenating and hashing the block private keys corresponding to at least one first blockchain data. Confirming the ownership of the first client device based on the encrypted verification information carried in the data processing request may include the following operations:
[0068] Based on the object identification information, an object public key is obtained, where the object public key corresponds to the object private key. The encrypted verification information is signed using the object public key to obtain first summary information, where if the encrypted verification information is successfully signed, the first summary information is private key summary information. The object identification information and the first summary information are sent to a distributed private key network, so that the distributed private key network can determine at least one blockchain private key based on the object identification information, concatenate and hash the at least one blockchain private key to obtain second summary information, and determine the ownership confirmation result for the first client device based on the matching result of the first summary information and the second summary information.
[0069] According to an embodiment of the present disclosure, the object identification information may include information that can represent the first client device and / or the requester of the data processing request. Through this information, the blockchain data processing platform can obtain the object public key corresponding to the first client device and / or the requester of the data processing request from the storage unit.
[0070] According to an embodiment of the present disclosure, verifying the encrypted verification information by using the object public key may be decrypting the encrypted verification information by using the object public key.
[0071] According to an embodiment of the present disclosure, the first summary information may be the same as or different from the private key summary information. Specifically, if either the object identification information or the encryption verification information is tampered with or disturbed during data transmission from the first client device to the blockchain data processing platform, the obtained first summary information may differ from the private key summary information. When both the object identification information and the encryption verification information are correct, the obtained first summary information may be the private key summary information. Furthermore, if the first summary information differs from the private key summary information, the first summary information will inevitably not match the second summary information.
[0072] According to an embodiment of the present disclosure, the private key summary information, the first summary information, and the second summary information can all be represented as a hash value. The above hash values can be calculated using the same hash algorithm. The hash algorithm can be selected according to the specific application scenario and is not limited here.
[0073] According to an embodiment of the present disclosure, when it is determined that the first summary information and the second summary information match, a title confirmation result indicating that the first client device has completed the title confirmation can be obtained, and when it is determined that the first summary information and the second summary information do not match, a title confirmation result indicating that the first client device has not completed the title confirmation can be obtained.
[0074] According to an embodiment of the present disclosure, by sequentially confirming the ownership of the first client device through a blockchain data processing platform and a distributed private key network, data centralization can be avoided, thereby ensuring data security.
[0075] According to an embodiment of the present disclosure, when the requesting party initiates a data processing request for the first time, that is, when at least one first blockchain data does not exist in the first blockchain network, at least one first blockchain data can be obtained from at least one second blockchain network through cross-chain data acquisition.
[0076] According to embodiments of the present disclosure, a second blockchain network can serve as a storage unit for a business information system. Users can register and authorize on the second blockchain network. As users conduct business using the business information system, the system collects the business data generated. The encrypted data is then uploaded to the second blockchain network. Business data can be encrypted using a blockchain public key. The blockchain public key can be generated during the user registration process on the second blockchain network. For example, a user can utilize an encryption client application configured on their client device to generate a blockchain public key and a blockchain private key based on a user-entered string. The blockchain public key is then sent to the business information system during the registration process. When uploading data to the blockchain, business data generated within a fixed time period can be packaged into a block and uploaded to the second blockchain network. The block header of this block can include plaintext information such as the upload time, the identifiers of the parties involved, and the hash value of the parent block.
[0077] FIG3 schematically shows a flowchart of a blockchain data processing method according to another embodiment of the present disclosure.
[0078] As shown in FIG. 3 , the method includes operations S310 to S330 .
[0079] In operation S310, in response to the data processing request, if at least one first blockchain data cannot be obtained from the first blockchain network, cross-chain data acquisition is performed on at least one second blockchain network based on the object identification information to obtain at least one first blockchain data.
[0080] In operation S320 , the first client device is authenticated based on the encrypted verification information carried in the data processing request.
[0081] In operation S330, when it is determined that the first client device has completed the right confirmation, the at least one first blockchain data is sent to the first client device, so that the first client device uses the block body private key corresponding to each of the at least one first blockchain data to decrypt the at least one first blockchain data and obtain at least one second blockchain data.
[0082] According to an embodiment of the present disclosure, at least one first blockchain data cannot be obtained from the first blockchain network, that is, the object identification information cannot be matched with any of the block headers of the multiple blocks included in the first blockchain network.
[0083] According to an embodiment of the present disclosure, the method of operations S320 to S330 may be implemented using the same or similar method provided in the aforementioned embodiment, which will not be described in detail here.
[0084] According to an embodiment of the present disclosure, based on the object identification information carried in the data processing request, cross-chain acquisition of the first blockchain data from each blockchain network of at least one blockchain network can be achieved using a cross-chain method. The cross-chain method can, for example, be a cross-chain method based on a cross-chain node. Specifically, the cross-chain method can include the following operations:
[0085] For each second blockchain network, a cross-chain node of the second blockchain network is determined. Based on the node type of the cross-chain node, the first blockchain data is obtained through the cross-chain node.
[0086] According to an embodiment of the present disclosure, a cross-chain node may be a blockchain node that can provide a communication interface to the outside world, and an external device may establish a communication link with the cross-chain node through the communication interface using an agreed communication protocol.
[0087] According to an embodiment of the present disclosure, the type of cross-chain node may be related to the type of the second blockchain network, specifically, the node permission allocation of different types of second blockchain networks. For example, if the second blockchain network is a consortium chain network, since the read permission, transaction permission, and accounting permission of the consortium chain network are all allocated to authorized nodes in the consortium chain network, external unauthorized nodes cannot access it. Therefore, the cross-chain node can be an authorized node in the consortium chain network. For another example, if the second blockchain network is a private chain network, since the read permission is completely private in the private chain network, the transaction permission and accounting permission are allocated to a limited number of authorized nodes. Therefore, when performing data read operations, the cross-chain node can be an authorized node or an unauthorized node in the private chain network, while when performing data update operations, the cross-chain node can only be a limited number of authorized nodes in the private chain network.
[0088] According to an embodiment of the present disclosure, for example, in a case where the second blockchain network is a public blockchain network, anyone can have read, transaction, and accounting permissions on the public blockchain network. Therefore, a cross-chain node can be any node in the public blockchain network, such as a light node or full node, or any node outside the public blockchain network. A light node in the second blockchain network can be a node that does not store or maintain the complete blockchain ledger, but only stores a minimal amount of state to send or transmit transaction information. A light node can only store the block headers of all blocks in the blockchain ledger and, using the Merkle root in the block header, can verify the existence of a payment transaction. A full node can be a node that has a complete blockchain ledger. A full node requires memory to synchronize all blockchain data, can independently verify all transactions on the blockchain, and update data in real time. It is primarily responsible for broadcasting and verifying blockchain transactions. Data recorded on different full nodes can be synchronized through a consensus mechanism.
[0089] According to an embodiment of the present disclosure, the cross-chain acquisition method of the first blockchain data may be different depending on the types of cross-chain nodes of different second blockchain networks in at least one second blockchain network.
[0090] For example, if the cross-chain node is determined to be a full node, a data acquisition request including object identification information can be sent to the cross-chain node to obtain the first blockchain data based on the first feedback data returned by the cross-chain node. In this case, the acquisition efficiency of the first blockchain data is relatively high.
[0091] According to an embodiment of the present disclosure, the first feedback data may be obtained by the cross-chain node from the cross-chain node's ledger based on the object identification information. The specific method for obtaining the first feedback data is not limited herein. The cross-chain node's ledger may refer to a complete blockchain ledger maintained in the cross-chain node's storage unit.
[0092] According to an embodiment of the present disclosure, the first feedback data returned by the cross-chain node may be a data message including one or more blocks. The first blockchain data may be obtained based on the first feedback data by removing the block headers of the one or more blocks included in the data message and then combining or concatenating them to obtain the first blockchain data.
[0093] According to an embodiment of the present disclosure, by directly setting the cross-chain node as a full node of the public chain network, the time consumption of the data acquisition business can be reduced and bandwidth can be saved.
[0094] For another example, when the cross-chain node is determined to be a light node, a data acquisition request including object identification information can be sent to the full node of the second blockchain network through the cross-chain node, so as to obtain the first blockchain data based on the second feedback data returned by the full node through the cross-chain node.
[0095] According to an embodiment of the present disclosure, the second feedback data is obtained by the full node from the full node's ledger based on the object identification information forwarded by the cross-chain node. The specific method for obtaining the second feedback data is not limited herein. The full node's ledger may refer to the complete blockchain ledger maintained in the full node's storage unit.
[0096] According to an embodiment of the present disclosure, a light node can act as a proxy node to forward instructions received through an interface to a full node. As an optional embodiment, before forwarding instructions, the light node can also use the block headers of each block in the light node's ledger to pre-verify the instructions, and instructions that fail pre-verification may not be forwarded. For example, when querying a payment transaction, the Merkle root included in the block header can be used for pre-verification, that is, to determine whether the payment transaction has been verified. When it is determined that the payment transaction has been verified, it can be determined that the payment transaction has been recorded in the second blockchain network.
[0097] According to an embodiment of the present disclosure, each full node in the second blockchain network can be represented as a distributed network. That is, the full node can be logically represented as a single node in the second blockchain network, and physically, the full node can be composed of multiple distributed nodes. Accordingly, the blockchain ledger of the full node can be divided into multiple sub-ledgers, and the multiple sub-ledgers can be distributed and stored in multiple distributed nodes, thereby achieving performance expansion of the full node and avoiding data hijacking problems. The light node can broadcast a data acquisition request to each distributed node in the full node. The multiple distributed nodes can respectively extract sub-data from their respective sub-ledgers and send the sub-data to the light node. The light node can combine and splice the various sub-data to obtain the second feedback data.
[0098] According to an embodiment of the present disclosure, when a cross-chain node is any node outside a public blockchain network, the cross-chain node can access the public blockchain network through a URL (Universal Resource Locator) address, a specific interface, etc., and obtain the first blockchain data from each node of the public blockchain network. Specifically, for each second blockchain network, if the second blockchain network is a public blockchain network, a data acquisition request including object identification information can be broadcast to multiple blockchain nodes included in the second blockchain network. The first blockchain data is then obtained based on the third feedback data of each of the multiple blockchain nodes.
[0099] According to an embodiment of the present disclosure, the third feedback data may be obtained by the blockchain node from the ledger of the blockchain node based on the object identification information.
[0100] According to an embodiment of the present disclosure, obtaining the first blockchain data based on the third feedback data returned by each of the multiple blockchain nodes can be to compare the multiple third feedback data to use the third feedback data with the highest frequency as the first blockchain data.
[0101] According to the embodiments of the present disclosure, by leveraging the broadcast mechanism of the public chain network, the range of data source nodes can be further expanded, thereby improving the reliability of the acquired data.
[0102] According to an embodiment of the present disclosure, as an optional implementation, the first client device can also be authenticated by the blockchain data processing platform alone. Specifically, before processing the first blockchain data, the first client device can be authenticated to determine whether the requesting party has the corresponding authority. If the authentication is completed, it can be determined that the requesting party has the corresponding authority, and it can be considered that the user's authorization has been obtained, and the decryption of the first blockchain data can continue. If the authentication is not completed, it can be considered that the user may be an illegal user and has not obtained the authorization of the legal user. Since the first blockchain data is encrypted data, the first blockchain data obtained at this time can be displayed as garbled data, which does not affect the privacy and security of the blockchain data. As an optional implementation, the first client device can also be authenticated first. After confirming that the first client device has completed the authentication, the first blockchain data can be obtained from at least one second blockchain network across chains based on the object identification information. This is not limited here.
[0103] According to an embodiment of the present disclosure, the information on which the rights confirmation process is based can be encrypted verification information. In order to ensure that the encrypted verification information is credible, that is, the encrypted verification information has not been tampered with during the information transmission process, the original verification information can be encrypted. The encryption processing method can include symmetric encryption, asymmetric encryption, digital signature, etc. Taking digital signature as an example, the first client device can use the object private key it holds to encrypt the plaintext of the verification information to obtain the encrypted verification information. In other words, the encrypted verification information can be obtained by the first client device using the object private key to digitally sign the plaintext of the verification information.
[0104] According to an embodiment of the present disclosure, the plain text of the verification information may be obtained by performing a hash calculation on the encrypted combination information by the first client device.
[0105] According to an embodiment of the present disclosure, an object key pair can be generated by the first client device based on data such as a random number, a device serial number, and a device generation date. The object key pair includes an object private key and an object public key. The object private key can be burned into the device's hardware, ensuring that it is held only by the first client device and cannot be accessed by external devices. The object public key can be published in advance so that other devices can use it for signature verification.
[0106] According to an embodiment of the present disclosure, confirming the authorization of the first client device based on the encrypted verification information carried in the data processing request may include the following operations:
[0107] Based on the object identification information, the reserved encrypted combination information and the object public key are obtained, where the object public key corresponds to the object private key. The encrypted verification information is signed using the object public key to obtain first verification information. A hash calculation is performed on the reserved encrypted combination information to obtain second verification information. Based on the matching result of the first verification information and the second verification information, the authentication result of the first client device is determined.
[0108] According to an embodiment of the present disclosure, the object identification information may include information that can represent the first client device, through which the reserved encryption combination information and the object public key corresponding to the first client device can be obtained from the storage unit.
[0109] According to an embodiment of the present disclosure, the encrypted combination information may be the information provided by the requester of a data processing request during registration. For example, the encrypted combination information may include at least one of the following: answers to preset questions, a password string, and biometric information. During registration, the requester may be required to provide answers to one or more preset questions by setting security questions or password retrieval questions. The answers to the preset questions include the question numbers selected by the requester during registration and the answers provided. The password string may be a secondary password, security password, or a random number or random string entered by the requester during registration. Biometric information may include information such as the requester's facial features, iris, fingerprint, and voiceprint. Biometric information may be collected by the first client device. Accordingly, the reserved encrypted combination information may be information stored by the blockchain data processing platform when the requester of a data processing request registers and provides information. The reserved encrypted combination information may also include at least one of the following: answers to preset questions, a password string, and biometric information.
[0110] According to an embodiment of the present disclosure, the plaintext verification information can be a hash value. The hash value can be directly input into the first client device by the requesting party when initiating a data processing request. Alternatively, the first client device can maintain a mapping table, each entry of which includes a mapping from a simple information to a hash value. The requesting party can input the simple information when initiating a data processing request, and the first client device can use the simple information to obtain the corresponding plaintext verification information from the mapping table. The simple information can include a string of characters, a combination of numbers, etc.
[0111] According to an embodiment of the present disclosure, verifying the encrypted verification information by using the object public key may be decrypting the encrypted verification information by using the object public key.
[0112] According to an embodiment of the present disclosure, the first verification information may be the same as or different from the plaintext verification information. Specifically, if either the object identification information or the encrypted verification information is tampered with or disturbed during data transmission from the first client device to the blockchain data processing platform, the obtained first verification information may differ from the plaintext verification information. When both the object identification information and the encrypted verification information are correct, the obtained first verification information may be the plaintext verification information. Furthermore, if the first verification information differs from the plaintext verification information, the first verification information will inevitably not match the second verification information.
[0113] According to an embodiment of the present disclosure, when it is determined that the plain text of the verification information and the reserved verification information match, a confirmation result indicating that the first client device has completed the confirmation can be obtained, and when it is determined that the plain text of the verification information and the reserved verification information do not match, a confirmation result indicating that the first client device has not completed the confirmation can be obtained.
[0114] According to an embodiment of the present disclosure, by using reserved verification information to confirm the ownership of the first client device, it is convenient for users to remember and data centralization can be avoided, thereby ensuring data security.
[0115] According to an embodiment of the present disclosure, the decryption process of the first blockchain data can be performed in a distributed private key network.
[0116] FIG4 schematically shows a flowchart of a blockchain data processing method according to another embodiment of the present disclosure.
[0117] As shown in FIG. 4 , the method includes operations S410 to S430 .
[0118] In operation S410, in response to receiving a data processing request from a first client device, at least one first blockchain data is obtained from a first blockchain network based on object identification information carried in the data processing request.
[0119] In operation S420 , the first client device is authenticated based on the encrypted verification information carried in the data processing request.
[0120] In operation S430, when it is determined that the first client device has completed the right confirmation, the object identification information and the at least one first blockchain data are sent to the distributed private key network, so that the distributed private key network decrypts the corresponding at least one first blockchain data according to the object identification information using the respective block body private keys of the at least one second blockchain network to obtain the at least one second blockchain data.
[0121] According to embodiments of the present disclosure, a block private key can be distributedly stored in multiple distributed nodes of a distributed private key network, or stored in at least some of the multiple distributed nodes. The private key data stored by each distributed node can be partial plaintext data of the block private key, or partial ciphertext data of the block private key obtained using various encryption methods, without limitation herein. The private key data stored by each distributed node can be partial data of a single block private key, or can include partial data of multiple block private keys, without limitation herein.
[0122] According to the embodiments of the present disclosure, by maintaining the block private key in a distributed private key network, the block private key will not be exposed to the outside in the form of plain text or ciphertext, that is, the block private key will not be accessed and obtained by external devices, thereby ensuring the security of data in the blockchain network.
[0123] The blockchain data processing method shown in FIG. 2 will be further described below with reference to FIG. 5A to FIG. 5B , FIG. 6 and FIG. 7 in combination with specific embodiments.
[0124] According to an embodiment of the present disclosure, after obtaining the first blockchain data or the second blockchain data, the blockchain data processing platform can display the data on the first client device in a non-disk viewing mode. Non-disk viewing of blockchain data can include asynchronous data viewing, synchronous data viewing, and other modes.
[0125] FIG5A schematically shows a schematic diagram of a method for asynchronously viewing blockchain data according to an embodiment of the present disclosure.
[0126] As shown in FIG5A , the blockchain data asynchronous viewing method can be used when the requester initiates a data processing request for the first time. Alternatively, the blockchain data asynchronous viewing method can be used when the requester determines that there is new data in at least one second blockchain network.
[0127] According to an embodiment of the present disclosure, in response to receiving a data processing request 503 from a first client device 502, the blockchain data processing platform 501 can obtain first blockchain data 505 from various second blockchain networks 504 across chains based on the object identification information contained in the data processing request 503. After confirming that the first client device 502 has completed the ownership confirmation, the blockchain data processing platform 501 can send the first blockchain data 505 and the object identification information in the data processing request 503 to the distributed private key network 506. The distributed private key network 506 can decrypt the first blockchain data 505 using the block private key 507 based on the object identification information to obtain second blockchain data 508. The distributed private key network 506 can then return the second blockchain data 508 to the blockchain data processing platform 501.
[0128] According to an embodiment of the present disclosure, for each second blockchain network 504, the blockchain data processing platform 501 may perform text normalization on the received second blockchain data 508 to obtain first normalized data 509. The first normalized data 509 may then be encrypted to obtain second normalized data 510. The blockchain data processing platform 501 may write the second normalized data 510 into the memory 511.
[0129] According to an embodiment of the present disclosure, a first client device 502 can initiate an asynchronous data viewing request by accessing memory 511 using a preset interface. In response to detecting that the first client device 502 has accessed memory 511 through the preset interface, the blockchain data processing platform 501 can send second normalized data 510 for at least one second blockchain network 504 to the first client device 502. For each second blockchain network 504, the first client device 502 can decrypt the second normalized data 510 using the block body private key 507 corresponding to the second blockchain network 504 to obtain first normalized data 509, and render and display the first normalized data 509 on the display interface 512 of the first client device 502.
[0130] According to embodiments of the present disclosure, text normalization can be achieved using, for example, a text classification service. Through normalization, the various phrases used in the second blockchain data 508 can be unified. For example, for the item "spoon," the second blockchain data 508 may use multiple aliases such as "spoon," "ladle soup," "porcelain soup," "spoon soup," "soup shell," "rice shell," and "water shell." After normalization, these various aliases can be unified into one single name: "spoon." Furthermore, through normalization, the various types of data designed in the second blockchain data 508 can be categorized according to preset types. For example, using data in a medical blockchain, the second blockchain data 508 can be categorized into user name, user gender, consultation time, disease type, medication type, and other categories.
[0131] According to an embodiment of the present disclosure, the data stored in the memory 511 can be cleaned up regularly according to cleaning rules. For example, the cleaning rules may include cleaning up according to user viewing time, cleaning up according to data storage time, etc.
[0132] According to an embodiment of the present disclosure, after completing the response to the requesting party's data processing request, that is, when at least one first blockchain data is obtained cross-chain from at least one second blockchain network, the at least one first blockchain data can be uploaded to the first blockchain network.
[0133] FIG5B schematically illustrates a method for synchronously viewing blockchain data according to an embodiment of the present disclosure.
[0134] As shown in Figure 5B, the blockchain data synchronization viewing method can be used when the requesting party initiates a data processing request for the second or subsequent time. That is, when the data synchronization viewing method is used, at least one first blockchain data item may have already been recorded in the first blockchain network. Alternatively, the blockchain data synchronization viewing method can also be used when the requesting party initiates a data processing request for the first time, without limitation.
[0135] According to an embodiment of the present disclosure, in response to receiving a data processing request 503 from a first client device 502, the blockchain data processing platform 501 can obtain at least one first blockchain data 505 from the first blockchain network 513 based on the object identification information carried by the data processing request 503.
[0136] According to an embodiment of the present disclosure, the blockchain data processing platform 501 may write at least one first blockchain data 505 into the memory 511 .
[0137] According to an embodiment of the present disclosure, a first client device 502 may access a memory 511 through a preset interface while initiating a data processing request 503. In response to detecting that the first client device 502 has accessed the memory 511 through the preset interface, the blockchain data processing platform 501 may send first blockchain data 505 of at least one second blockchain network 504 to the first client device 502.
[0138] According to an embodiment of the present disclosure, the first client device 502 can use the block private key 507 corresponding to the at least one second blockchain network 504 to decrypt the first blockchain data 505 of the at least one second blockchain network 504 to obtain at least one second blockchain data 508, call the text classification service to normalize the at least one second blockchain data 508 to obtain at least one first normalized data 509, and render and display the at least one first normalized data 509 on the display interface 512 of the first client device.
[0139] According to an embodiment of the present disclosure, by viewing the data without writing it to the disk as described above, the second normalized data or the first blockchain data will not be written to the disk related to the blockchain data processing platform, thereby reducing the possibility of data leakage.
[0140] According to embodiments of the present disclosure, the requester of a data processing request can be the owner of the second blockchain data. The second blockchain data can be generated by the requester within the network and collected by at least one second blockchain network. The requester can define differentiated definitions for the second blockchain data it holds, implementing different processing policies for different data. For example, the requester can make some of its second blockchain data public and share it with other users to obtain other services provided by the blockchain data processing platform.
[0141] FIG6 schematically shows a schematic diagram of a blockchain data sharing method according to an embodiment of the present disclosure.
[0142] As shown in FIG6 , when displaying the second blockchain data 508, the blockchain data processing platform 501 can provide data sharing options for each piece of second blockchain data 508. The requesting party can determine the second blockchain data to be shared by selecting the options for each piece of second blockchain data 508. The first client device 502 can generate a data sharing request 601 based on the second blockchain data to be shared.
[0143] According to an embodiment of the present disclosure, the blockchain data processing platform 501 may respond to a data sharing request 601 from a first client device 502 and obtain first target blockchain data 602 included in the data sharing request 601. The blockchain data processing platform 501 may perform text normalization on the first target blockchain data 602 to obtain third normalized data 603. The blockchain data processing platform 501 may encrypt the third normalized data 603 to obtain fourth normalized data 604. The blockchain data processing platform 501 may upload the fourth normalized data 604 to the third blockchain network 605.
[0144] According to an embodiment of the present disclosure, the encryption of the third normalized data 603 can be implemented using various encryption methods. The various encryption methods can include any symmetric encryption method, such as DES (Data Encryption Standard), AES (Advanced Encryption Standard), etc., and can also include any asymmetric encryption method, such as RSA, ECC (Elliptic Curve Cryptography), etc., without limitation herein.
[0145] According to the embodiments of the present disclosure, taking the medical blockchain as an example, for example, the requester may be a patient user who urgently needs bone marrow typing. The requester's first target blockchain data may be the requester's matching data. By sharing this first target blockchain data, bone marrow typing mutual assistance can be more conveniently achieved. For another example, the requester's first target blockchain data may be the diagnosis and treatment process of a certain disease, which may include medication data. By sharing this first target blockchain data, it can be used as one of the basic contents of big data to guide medication recommendations for more uncured patients.
[0146] According to an embodiment of the present disclosure, after the fourth normalized data is uploaded to the third blockchain network, any user can call the fourth normalized data.
[0147] FIG7 schematically shows a schematic diagram of a blockchain data calling method according to an embodiment of the present disclosure.
[0148] As shown in Figure 7, after the blockchain data processing platform 501 uploads the fourth normalized data 604 to the third blockchain network 605, the blockchain data processing platform 501 can respond to the data call request 702 from the second client device 701 and determine the data call model 703 based on the call type information carried by the data call request 702.
[0149] According to an embodiment of the present disclosure, the blockchain data processing platform 501 can use the data call model 703 to process the fourth blockchain data 704 included in the third blockchain network 605 to obtain the second target blockchain data 705.
[0150] According to an embodiment of the present disclosure, the blockchain data processing platform 501 can decrypt the second target blockchain data 705 and send the decrypted second target blockchain data 706 to the second client device 701.
[0151] According to an embodiment of the present disclosure, the data call model 703 may be a data model in a preset algorithm library. The data models in the preset algorithm library may include recommendation models, matching models, prediction models, etc., and may be configured according to specific application scenarios, which are not limited here. The input and output ports of each data model may be provided to the corresponding interface of the blockchain data processing platform 501. Through this interface, the blockchain data processing platform 501 can input data into the data model and extract data processed by the data model from the data model.
[0152] According to an embodiment of the present disclosure, in addition to including the fourth normalized data 604 provided by the requester of the data processing request 503, the fourth blockchain data 704 may also include blockchain data shared by other users to the third blockchain network 605, which is not limited here.
[0153] According to an embodiment of the present disclosure, taking data call model 703 as an example of a user recommendation model in a medical blockchain, user A can input user information through the user recommendation model's input interface, such as specific attribute values for attributes such as "user name," "user gender," "consultation time," "disease type," and "drug type." These specific attribute values can form user vector A. The user recommendation model can then calculate a similarity match with user vector A using a data matrix based on the underlying big data content. This results in another set of user vectors, B, composed of specific attribute values for attributes such as "user name," "user gender," "consultation time," "disease type," and "drug type," being fed back to user A through an output interface. Based on the identity information, such as "user gender," in user vector B, user A can query the third blockchain network to obtain detailed information about the diagnosis and treatment process provided by user B. Alternatively, the platform can provide user A with multiple sets of user vectors, such as user vector B, user vector C, and user vector D, for user A to select.
[0154] As an optional implementation, the second target blockchain data 705 can be decrypted using a decryption method corresponding to the encryption method used to encrypt the third normalized data 603. Taking asymmetric encryption as an example, the blockchain data processing platform 501 can generate a platform private key and a platform public key. When users share data, the blockchain data processing platform 501 can use the platform private key to encrypt the shared data and then link the encrypted shared data to the third blockchain network. When other users request data, the blockchain data processing platform 501 can use the platform public key to decrypt the requested data and then send the decrypted data to other users. Alternatively, the blockchain data processing platform 501 can provide the platform public key to users authorized to request data. When the user requests data, the blockchain data processing platform 501 can directly send the requested data from the third blockchain network to the user, who then uses the platform public key to decrypt the requested data.
[0155] FIG8 schematically shows a block chain data processing platform according to an embodiment of the present disclosure.
[0156] As shown in Figure 8, the blockchain data processing platform 501 may include a blockchain data source management module 5011, a private key control module 5012 and a data processing module 5013.
[0157] The blockchain data source management module 5011 is configured to, in response to receiving a data processing request from a first client device, obtain at least one first blockchain data from the first blockchain network based on the object identification information carried in the data processing request.
[0158] The private key control module 5012 is configured to confirm the authority of the first client device based on the encrypted verification information carried in the data processing request.
[0159] The data processing module 5013 is configured to send at least one first blockchain data to the first client device when it is determined that the first client device has completed the ownership confirmation, so that the first client device can use the block body private key corresponding to the at least one first blockchain data to decrypt the at least one first blockchain data and obtain at least one second blockchain data.
[0160] According to an embodiment of the present disclosure, the encrypted verification information is obtained by the first client device using the object private key to digitally sign the private key summary information, and the private key summary information is obtained by the first client device splicing and hashing the block private keys corresponding to the at least one first blockchain data.
[0161] According to an embodiment of the present disclosure, the private key control module 5012 is configured to: obtain an object public key based on object identification information, wherein the object public key corresponds to the object private key; verify the encrypted verification information using the object public key to obtain first summary information; wherein, if the encrypted verification information is successfully verified, the first summary information is the private key summary information; send the object identification information and the first summary information to a distributed private key network, so that the distributed private key network can determine at least one blockchain private key based on the object identification information, concatenate and hash the at least one blockchain private key to obtain second summary information, and determine the ownership confirmation result of the first client device based on the matching result of the first summary information and the second summary information.
[0162] According to an embodiment of the present disclosure, the blockchain data source management module 5011 is configured to: in response to a data processing request, if at least one first blockchain data cannot be obtained from the first blockchain network, perform cross-chain data acquisition on at least one second blockchain network based on object identification information to obtain at least one first blockchain data.
[0163] According to an embodiment of the present disclosure, the blockchain data source management module 5011 is configured to: for each second blockchain network, determine a cross-chain node of the second blockchain network, and obtain the first blockchain data through the cross-chain node based on the node type of the cross-chain node.
[0164] According to an embodiment of the present disclosure, the blockchain data source management module 5011 is configured to, upon determining that the cross-chain node is a full node, send a data acquisition request including object identification information to the cross-chain node, so as to obtain first blockchain data based on first feedback data returned by the cross-chain node. The first feedback data is obtained by the cross-chain node from the cross-chain node's ledger based on the object identification information.
[0165] According to an embodiment of the present disclosure, the blockchain data source management module 5011 is configured to, when determining that the cross-chain node is a light node, send a data acquisition request including object identification information to a full node of the second blockchain network via the cross-chain node, so as to obtain the first blockchain data based on the second feedback data returned by the full node via the cross-chain node. The second feedback data is obtained by the full node from the full node's ledger based on the object identification information forwarded by the cross-chain node.
[0166] According to an embodiment of the present disclosure, the blockchain data source management module 5011 is configured to: for each second blockchain network, if the second blockchain network is a public blockchain network, broadcast a data acquisition request including object identification information to multiple blockchain nodes included in the second blockchain network. The first blockchain data is obtained based on third feedback data returned by each of the multiple blockchain nodes, where the third feedback data is obtained by the blockchain node from the blockchain node's ledger based on the object identification information.
[0167] According to an embodiment of the present disclosure, the encrypted verification information is obtained by the first client device digitally signing the verification information plaintext using the object private key, and the verification information plaintext is obtained by the first client device performing hash calculation on the encrypted combination information.
[0168] According to an embodiment of the present disclosure, the private key control module 5012 is configured to: obtain reserved encrypted combination information and the object public key based on the object identification information, wherein the object public key corresponds to the object private key; verify the encrypted verification information using the object public key to obtain first verification information; wherein, if the verification of the encrypted verification information is successful, the first verification information is the plaintext verification information; perform a hash calculation on the reserved encrypted combination information to obtain second verification information; and determine the authentication result of the first client device based on the matching result of the first verification information and the second verification information.
[0169] According to an embodiment of the present disclosure, the encrypted combination information or the reserved encrypted combination information includes at least one of the following: an answer text to a preset question, a password string, and biometric information.
[0170] According to an embodiment of the present disclosure, the private key control module 5012 is configured to: when it is determined that the first client device has completed the right confirmation, send object identification information and at least one first blockchain data to the distributed private key network, so that the distributed private key network can decrypt the corresponding at least one first blockchain data based on the object identification information using the respective block private keys of at least one second blockchain network to obtain at least one second blockchain data.
[0171] According to an embodiment of the present disclosure, the data processing module 5013 is configured to: for each second blockchain network, perform text normalization processing on the second blockchain data of the second blockchain network to obtain first normalized data. The first normalized data is encrypted using the block body public key corresponding to the second blockchain network to obtain second normalized data, wherein the block body public key corresponds to the block body private key. The second normalized data is written to the memory. In response to detecting that the first client device accesses the memory through a preset interface, the second normalized data of at least one second blockchain network is sent to the first client device, wherein the first client device is configured to decrypt the second normalized data of the second blockchain network using the block body private key corresponding to the second blockchain network for each second blockchain network to obtain first normalized data, and render and display the first normalized data on the display interface of the first client device.
[0172] According to an embodiment of the present disclosure, the data processing module 5013 is configured to: when at least one first blockchain data is obtained cross-chain from at least one second blockchain network, put the at least one first blockchain data on the chain in the first blockchain network.
[0173] According to an embodiment of the present disclosure, the data processing module 5013 is configured to: write at least one first blockchain data into a memory; in response to detecting that the first client device accesses the memory through a preset interface, send the at least one first blockchain data to the first client device; wherein the first client device is configured to decrypt the at least one first blockchain data using a block private key corresponding to each of the at least one first blockchain data to obtain at least one second blockchain data; call a text classification service to normalize the at least one second blockchain data to obtain at least one first normalized data; and render and display the at least one first normalized data on a display interface of the first client device.
[0174] According to an embodiment of the present disclosure, the data processing module 5013 is configured to: in response to a data sharing request from a first client device, obtain first target blockchain data included in the data sharing request; perform text normalization on the first target blockchain data to obtain third normalized data; encrypt the third normalized data to obtain fourth normalized data; and upload the fourth normalized data to a third blockchain network.
[0175] According to an embodiment of the present disclosure, the data processing module 5013 is configured to: in response to a data call request from a second client device, determine a data call model based on call type information carried in the data call request; use the data call model to process fourth blockchain data included in the third blockchain network to obtain second target blockchain data, wherein the fourth blockchain data includes fourth normalized data; decrypt the second target blockchain data, and send the decrypted second target blockchain data to the second client device.
[0176] It should be noted that the blockchain data processing platform part in the embodiments of the present disclosure corresponds to the blockchain data processing method part in the embodiments of the present disclosure. The description of the blockchain data processing platform part specifically refers to the blockchain data processing method part and will not be repeated here.
[0177] FIG9 schematically shows a block chain data processing system according to an embodiment of the present disclosure.
[0178] As shown in FIG9 , the blockchain data processing system may include a first client device 502 , a first blockchain network 513 , a blockchain data processing platform 501 , and a distributed private key network 506 .
[0179] The blockchain data processing platform 501 is configured to, in response to receiving a data processing request from a first client device, obtain at least one first blockchain data item from the first blockchain network based on the object identification information included in the data processing request. Based on the encrypted verification information included in the data processing request, the platform performs a verification of the ownership of the first client device. If verification of the ownership of the first client device is determined to be complete, the platform transmits the at least one first blockchain data item to the first client device.
[0180] The first client device 502 is configured to: use the block body private key corresponding to the at least one first blockchain data to decrypt the at least one first blockchain data to obtain the at least one second blockchain data.
[0181] According to an embodiment of the present disclosure, the blockchain data processing system may further include at least one second blockchain network 504 .
[0182] According to an embodiment of the present disclosure, the blockchain data processing platform 501 can be configured to: in response to a data processing request, if at least one first blockchain data cannot be obtained from the first blockchain network, perform cross-chain data acquisition on at least one second blockchain network based on object identification information to obtain at least one first blockchain data.
[0183] According to an embodiment of the present disclosure, the blockchain data processing platform 501 can be configured to: when it is determined that the first client device has completed the right confirmation, send object identification information and at least one first blockchain data to the distributed private key network.
[0184] According to an embodiment of the present disclosure, the distributed private key network 506 can be configured to: decrypt the corresponding at least one first blockchain data using the respective block body private keys of at least one second blockchain network based on the object identification information to obtain at least one second blockchain data.
[0185] According to an embodiment of the present disclosure, the distributed private key network 506 may be configured to: in response to receiving object identification information and at least one first blockchain data from a blockchain data processing platform, determine at least one target node from a plurality of distributed nodes based on the object identification information; obtain the respective block-body private keys of at least one second blockchain network based on the respective private key data stored by the at least one target node; decrypt the corresponding at least one first blockchain data using the respective block-body private keys of the at least one second blockchain network to obtain at least one second blockchain data; and transmit the at least one second blockchain data to the blockchain data processing platform.
[0186] According to an embodiment of the present disclosure, the private key data stored in the target node is character string data.
[0187] According to an embodiment of the present disclosure, the distributed private key network 506 may be configured to: for each target node, obtain concatenation sequence information and target string data based on the private key data stored by the target node. Based on the concatenation sequence information of at least one target node, concatenate the target string data of at least one target node to obtain a target block private key. Based on a preset character length of the block private key, segment the target block private key to obtain a block private key for at least one second blockchain network.
[0188] According to an embodiment of the present disclosure, when a distributed private key network stores at least one block-body private key belonging to the same requesting party, it may first concatenate the at least one block-body private key to obtain a target block-body private key. Alternatively, the at least one concatenated block-body private key may be further encrypted to obtain a target block-body private key. The target block-body private key may be divided into multiple parts. Based on the number of parts, a corresponding number of target nodes may be determined from multiple distributed nodes, and a string parameter having the same size as the target block-body private key may be generated in each target node. The parameter value of the string parameter may be empty. When performing storage allocation of the target block-body private key, the element at the corresponding position in the string parameter of the target node may be replaced based on the position of each part of the target block-body private key in the original block-body private key to obtain private key data, thereby realizing the storage of the target block-body private key of this part in the target node.
[0189] According to embodiments of the present disclosure, when obtaining a block-level private key, the distributed private key network can obtain, for each target node, concatenation order information and target string data based on the private key data stored by the target node. Specifically, the concatenation order information can be obtained based on the position of non-empty string data within each private key data. The target string data can be non-empty string data within the private key data.
[0190] According to an embodiment of the present disclosure, the distributed private key network can splice the target string data of at least one target node based on the splicing sequence information of at least one target node to obtain the target block private key.
[0191] According to an embodiment of the present disclosure, since at least one block private key can be generated using an encryption algorithm with the same number of bits, the target block private key can be split based on the preset character length of the block private key to obtain the block private keys of at least one blockchain network.
[0192] According to an embodiment of the present disclosure, the number of bits in at least one block's private key can be different. During the process of generating a target block's private key, the concatenation order and number of bits of each block's private key can be recorded, and the target block's private key can be segmented based on this record.
[0193] According to an embodiment of the present disclosure, the private key data stored in the target node may be curve coordinate data.
[0194] According to an embodiment of the present disclosure, the distributed private key network 306 may be configured to: perform curve fitting on the private key data stored in each of at least one target node based on a curve template to obtain a target curve; concatenate multiple parameter values included in the target curve to obtain a target block private key; and segment the target block private key based on a preset character length of the block private key to obtain a block private key for each of at least one second blockchain network.
[0195] According to an embodiment of the present disclosure, when storing at least one block-body private key belonging to the same requester, the distributed private key network can first concatenate the at least one block-body private key and further process the concatenated at least one block-body private key into an integer value. A curve template can be selected based on the number of digits of the integer value, and the integer value can be split into multiple parameter values according to the specified number of digits of each parameter in the curve template. The multiple parameter values are then assigned to each parameter of the curve template to obtain the target curve. For example, the integer value can be 12345678, and the selected curve template can be expressed as y=ax 2 +bx 2 +cx+d, the number of digits for each parameter can be 2, so the parameters of the curve template can be assigned values of a=12, b=34, c=56, and d=78 respectively. After the assignment is completed, the target curve can be expressed as y=12x 2 +23x 2 +56x+78. After determining the target curve, multiple coordinate points can be randomly selected from the target curve. The number of selected coordinate points can be greater than or equal to the number of parameters in the curve template. Based on the number of coordinate points, a corresponding number of target nodes can be selected from the multiple distributed nodes, and the curve coordinate data of the multiple coordinate points can be written to each target node.
[0196] According to embodiments of the present disclosure, when obtaining a block private key, the distributed private key network can perform curve fitting on the private key data stored by at least one target node based on a curve template to obtain a target curve. Multiple parameter values included in the target curve can be concatenated to obtain a target block private key. The target block private key can be segmented based on a preset character length of the block private key to obtain the block private key of at least one blockchain network.
[0197] According to the embodiments of the present disclosure, by utilizing distributed nodes to distribute the storage of block private keys, the single point risk of information storage can be avoided, which helps to ensure the privacy and security of the user's block private key, thereby indirectly protecting the privacy and security of the user's blockchain data.
[0198] According to an embodiment of the present disclosure, the blockchain data processing system includes a first client device, a first blockchain network, at least one second blockchain network, a blockchain data processing platform, and a distributed private key network, which can be used to implement the blockchain data processing method described in the embodiment of the present disclosure. Please refer to the description of the corresponding parts above and will not be repeated here.
[0199] FIG10 schematically shows a block diagram of a blockchain data processing device according to an embodiment of the present disclosure.
[0200] As shown in FIG10 , the blockchain data processing device 1000 may include a first acquisition module 1010 , a rights confirmation module 1020 and a first sending module 1030 .
[0201] The first acquisition module 1010 is configured to, in response to receiving a data processing request from a first client device, acquire at least one first blockchain data from the first blockchain network based on object identification information carried in the data processing request.
[0202] The authentication module 1020 is configured to authenticate the first client device based on the encrypted authentication information carried in the data processing request.
[0203] The first sending module 1030 is used to send at least one first blockchain data to the first client device when it is determined that the first client device has completed the ownership confirmation, so that the first client device uses the block body private key corresponding to the at least one first blockchain data to decrypt the at least one first blockchain data and obtain at least one second blockchain data.
[0204] According to an embodiment of the present disclosure, the encrypted verification information is obtained by the first client device using the object private key to digitally sign the private key summary information, and the private key summary information is obtained by the first client device splicing and hashing the block private keys corresponding to the at least one first blockchain data.
[0205] According to an embodiment of the present disclosure, the title confirmation module 1020 includes a first title confirmation unit, a second title confirmation unit, and a third title confirmation unit.
[0206] The first right confirmation unit is used to obtain the object public key based on the object identification information, wherein the object public key corresponds to the object private key.
[0207] The second right confirmation unit is used to use the object public key to verify the signature of the encrypted verification information to obtain first summary information, wherein when the signature verification of the encrypted verification information is successful, the first summary information is private key summary information.
[0208] The third right confirmation unit is configured to send the object identification information and the first summary information to the distributed private key network, so that the distributed private key network determines at least one blockchain private key based on the object identification information, concatenates and hashes the at least one blockchain private key to obtain second summary information, and determines the right confirmation result of the first client device based on the matching result of the first summary information and the second summary information.
[0209] According to an embodiment of the present disclosure, the blockchain data processing device 1000 further includes a second acquisition module.
[0210] The second acquisition module is used to respond to the data processing request and, if the at least one first blockchain data cannot be obtained from the first blockchain network, perform cross-chain data acquisition on the at least one second blockchain network based on the object identification information to obtain the at least one first blockchain data.
[0211] According to an embodiment of the present disclosure, the second acquisition module includes a first acquisition unit and a second acquisition unit.
[0212] The first acquisition unit is used to determine, for each second blockchain network, a cross-chain node of the second blockchain network.
[0213] The second acquisition unit is configured to acquire the first blockchain data through the cross-chain node based on the node type of the cross-chain node.
[0214] According to an embodiment of the present disclosure, the second acquiring unit includes a first acquiring sub-unit.
[0215] The first acquisition subunit is configured to, when the cross-chain node is determined to be a full node, send a data acquisition request including object identification information to the cross-chain node, so as to obtain the first blockchain data based on first feedback data returned by the cross-chain node. The first feedback data is obtained by the cross-chain node from the cross-chain node's ledger based on the object identification information.
[0216] According to an embodiment of the present disclosure, the second acquiring unit includes a second acquiring sub-unit.
[0217] The second acquisition subunit is configured to, when the cross-chain node is determined to be a light node, send a data acquisition request including object identification information to a full node of the second blockchain network via the cross-chain node, so as to obtain the first blockchain data based on second feedback data returned by the full node via the cross-chain node. The second feedback data is obtained by the full node from the full node's ledger based on the object identification information forwarded by the cross-chain node.
[0218] According to an embodiment of the present disclosure, the second acquisition module includes a third acquisition unit and a fourth acquisition unit.
[0219] The third acquisition unit is used to broadcast a data acquisition request including object identification information to multiple blockchain nodes included in the second blockchain network for each second blockchain network when the second blockchain network is a public blockchain network.
[0220] The fourth acquisition unit is used to obtain the first blockchain data based on the third feedback data returned by each of the multiple blockchain nodes, wherein the third feedback data is obtained by the blockchain node from the ledger of the blockchain node based on the object identification information.
[0221] According to an embodiment of the present disclosure, the encrypted verification information is obtained by the first client device digitally signing the verification information plaintext using the object private key, and the verification information plaintext is obtained by the first client device performing hash calculation on the encrypted combination information.
[0222] According to an embodiment of the present disclosure, the title confirmation module 1020 includes a fourth title confirmation unit, a fifth title confirmation unit, a sixth title confirmation unit, and a seventh title confirmation unit.
[0223] The fourth right confirmation unit is used to obtain the reserved encryption combination information and the object public key based on the object identification information, wherein the object public key corresponds to the object private key.
[0224] The fifth authentication unit is configured to verify the encrypted authentication information using the object public key to obtain first authentication information, wherein when it is determined that the encrypted authentication information is successfully verified, the first authentication information is the authentication information plain text.
[0225] The sixth right confirmation unit is used to perform a hash calculation on the reserved encryption combination information to obtain second verification information.
[0226] The seventh authentication unit is configured to determine an authentication result of the first client device based on a matching result between the first verification information and the second verification information.
[0227] According to an embodiment of the present disclosure, the encrypted combination information or the reserved encrypted combination information includes at least one of the following: an answer text to a preset question, a password string, and biometric information.
[0228] According to an embodiment of the present disclosure, the blockchain data processing device 1000 further includes a second sending module.
[0229] The second sending module is used to send object identification information and at least one first blockchain data to the distributed private key network when it is determined that the first client device has completed the right confirmation, so that the distributed private key network can decrypt the corresponding at least one first blockchain data based on the object identification information using the respective block body private keys of the at least one second blockchain network to obtain at least one second blockchain data.
[0230] According to an embodiment of the present disclosure, the blockchain data processing device 1000 further includes a first processing module, a first encryption module, a first writing module and a third sending module.
[0231] The first processing module is configured to perform text normalization processing on the second blockchain data of each second blockchain network to obtain first normalized data.
[0232] The first encryption module is configured to encrypt the first normalized data using a block public key corresponding to the second blockchain network to obtain second normalized data, wherein the block public key corresponds to the block private key.
[0233] The first writing module is used to write the second normalized data into the memory.
[0234] The third sending module is configured to send, in response to detecting that the first client device accesses the memory through the preset interface, the second normalized data of at least one second blockchain network to the first client device, wherein the first client device is configured to decrypt the second normalized data of the second blockchain network using the block body private key corresponding to the second blockchain network for each second blockchain network to obtain first normalized data, and render and display the first normalized data on the display interface of the first client device.
[0235] According to an embodiment of the present disclosure, the blockchain data processing device 1000 further includes a first on-chain module.
[0236] The first on-chain module is used to upload the at least one first blockchain data to the first blockchain network when the at least one first blockchain data is obtained from the at least one second blockchain network across the chain.
[0237] According to an embodiment of the present disclosure, the blockchain data processing device 1000 further includes a second writing module and a fourth sending module.
[0238] The second writing module is used to write at least one first blockchain data into the memory.
[0239] A fourth sending module is configured to send at least one first blockchain data to the first client device in response to detecting that the first client device accesses the memory through a preset interface, wherein the first client device is configured to use a block body private key corresponding to each of the at least one first blockchain data to decrypt the at least one first blockchain data to obtain at least one second blockchain data, call a text classification service to normalize the at least one second blockchain data to obtain at least one first normalized data, and render and display the at least one first normalized data on a display interface of the first client device.
[0240] According to an embodiment of the present disclosure, the blockchain data processing device 1000 further includes a third acquisition module, a second processing module, a second encryption module and a second chain module.
[0241] The third acquisition module is used to respond to the data sharing request from the first client device and obtain the first target blockchain data carried in the data sharing request.
[0242] The second processing module is used to perform text normalization processing on the first target blockchain data to obtain third normalized data.
[0243] The second encryption module is used to encrypt the third normalized data to obtain fourth normalized data.
[0244] The second on-chain module is used to upload the fourth normalized data to the third blockchain network.
[0245] According to an embodiment of the present disclosure, the blockchain data processing device 1000 further includes a determination module, a third processing module and a fifth sending module.
[0246] The determination module is configured to determine a data call model in response to a data call request from a second client device based on call type information carried in the data call request.
[0247] The third processing module is used to use the data call model to process the fourth blockchain data included in the third blockchain network to obtain the second target blockchain data, wherein the fourth blockchain data includes fourth normalized data.
[0248] The fifth sending module is used to decrypt the second target blockchain data and send the decrypted second target blockchain data to the second client device.
[0249] According to the module of the embodiment of the present disclosure, submodule, unit, subunit, any multiple, or at least part of the function of any multiple thereof can be realized in a module. According to the module of the embodiment of the present disclosure, submodule, unit, subunit, any one or more can be split into multiple modules to realize. According to the module of the embodiment of the present disclosure, submodule, unit, subunit, any one or more can be at least partially realized as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be realized by hardware or firmware of any other reasonable way of integrating or encapsulating the circuit, or by any one of the three implementation modes of software, hardware and firmware or by a suitable combination of any of them. Or, according to the module of the embodiment of the present disclosure, submodule, unit, subunit, one or more can be at least partially realized as a computer program module, When the computer program module is run, the corresponding function can be executed.
[0250] For example, any multiple of the first acquisition module 1010, the confirmation module 1020, and the first sending module 1030 can be combined into one module / unit / sub-unit for implementation, or any one of the modules / units / sub-units can be split into multiple modules / units / sub-units. Alternatively, at least part of the functions of one or more of these modules / units / sub-units can be combined with at least part of the functions of other modules / units / sub-units and implemented in one module / unit / sub-unit. According to an embodiment of the present disclosure, at least one of the first acquisition module 1010, the confirmation module 1020, and the first sending module 1030 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in an appropriate combination of any of them. Alternatively, at least one of the first acquisition module 1010, the right confirmation module 1020 and the first sending module 1030 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.
[0251] It should be noted that the blockchain data processing device part in the embodiments of the present disclosure corresponds to the blockchain data processing method part in the embodiments of the present disclosure. The description of the blockchain data processing device part specifically refers to the blockchain data processing method part, which will not be repeated here.
[0252] Figure 11 schematically illustrates a block diagram of an electronic device suitable for implementing a blockchain data processing method according to an embodiment of the present disclosure. The electronic device shown in Figure 11 is merely an example and should not limit the functionality and scope of use of the embodiments of the present disclosure.
[0253] As shown in Figure 11, the electronic device 1100 according to an embodiment of the present disclosure includes a processor 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 part 1108 into a random access memory (RAM) 1103. The processor 1101 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (such as an application-specific integrated circuit (ASIC)), etc. The processor 1101 may also include an onboard memory for caching purposes. The processor 1101 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.
[0254] Various programs and data required for the operation of the electronic device 1100 are stored in the RAM 1103. The processor 1101, the ROM 1102, and the RAM 1103 are connected to each other via a bus 1104. The processor 1101 executes the various operations of the method flow according to the embodiment of the present disclosure by executing the programs in the ROM 1102 and / or the RAM 1103. It should be noted that the programs may also be stored in one or more memories other than the ROM 1102 and the RAM 1103. The processor 1101 may also execute the various operations of the method flow according to the embodiment of the present disclosure by executing the programs stored in the one or more memories.
[0255] According to an embodiment of the present disclosure, electronic device 1100 may further include an input / output (I / O) interface 1105, which is also connected to bus 1104. System 1100 may also include one or more of the following components connected to I / O interface 1105: an input section 1106 including a keyboard, mouse, etc.; an output section 1107 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and speakers; a storage section 1108 including a hard disk; and a communication section 1109 including a network interface card such as a LAN card or a modem. 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 magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in drive 1110 as needed, so that computer programs read from the removable media can be installed into storage section 1108 as needed.
[0256] According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1109, and / or installed from the removable medium 1111. When the computer program is executed by the processor 1101, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.
[0257] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments, or may exist independently and not be incorporated into the device / apparatus / system. The computer-readable storage medium carries one or more programs, and when executed, implements the method according to the embodiments of the present disclosure.
[0258] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM (Erasable Programmable Read Only Memory, EPROM) or flash memory), a portable compact disk read-only memory (Computer Disc Read-Only Memory, CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, 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.
[0259] For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 1102 and / or the RAM 1103 described above and / or one or more memories other than the ROM 1102 and the RAM 1103 .
[0260] Embodiments of the present disclosure also include a computer program product, which includes a computer program, which contains program code for executing the method provided by the embodiments of the present disclosure. When the computer program product is run on an electronic device, the program code is used to enable the electronic device to implement the blockchain data processing method provided by the embodiments of the present disclosure.
[0261] When the computer program is executed by the processor 1101, the above functions defined in the system / device of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.
[0262] In one embodiment, the computer program may be stored on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may be transmitted and distributed in the form of a signal on a network medium, downloaded and installed via the communication portion 1109, and / or installed from removable media 1111. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to wireless, wired, or any suitable combination thereof.
[0263] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, languages such as Java, C++, Python, "C" or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect via the Internet).
[0264] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of the systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, program segment, or portion of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the boxes may occur in an order different from that marked in the accompanying drawings. For example, two boxes shown in succession may actually be executed substantially in parallel, or they may sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, as well as the combination of boxes in the block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or may be implemented using a combination of dedicated hardware and computer instructions. It will be understood by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or coupled in various ways, even if such combinations or couplings are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or coupled in various ways, and all such combinations and / or couplings fall within the scope of the present disclosure.
[0265] The embodiments of the present disclosure are described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although each embodiment has been described separately above, this does not mean that the measures in each embodiment cannot be used in combination to advantage. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present disclosure.
Claims
1. A blockchain data processing method, include: In response to receiving a data processing request from a first client device, obtaining at least one first blockchain data from a first blockchain network based on the object identification information carried in the data processing request; Confirming the authorization of the first client device based on the encrypted verification information carried in the data processing request; as well as When it is determined that the first client device has completed the right confirmation, the at least one first blockchain data is sent to the first client device so that the first client device uses the block body private key corresponding to the at least one first blockchain data to decrypt the at least one first blockchain data to obtain at least one second blockchain data.
2. The method according to claim 1, in, The encrypted verification information is obtained by the first client device digitally signing the private key summary information using the object private key, and the private key summary information is obtained by the first client device concatenating and hashing the block private keys corresponding to the at least one first blockchain data; The step of confirming the identity of the first client device based on the encrypted verification information carried in the data processing request includes: Based on the object identification information, obtaining an object public key, wherein the object public key corresponds to the object private key; Using the object public key to verify the encrypted verification information, to obtain first summary information, wherein, if the encrypted verification information is successfully verified, the first summary information is the private key summary information; and The object identification information and the first summary information are sent to a distributed private key network, so that the distributed private key network determines at least one blockchain private key according to the object identification information, performs concatenation and hash calculation on the at least one blockchain private key to obtain second summary information, and determines the confirmation result of the first client device based on the matching result of the first summary information and the second summary information.
3. The method according to claim 1, further comprising: include: In response to the data processing request, if the at least one first blockchain data cannot be obtained from the first blockchain network, based on the object identification information, cross-chain data acquisition is performed on at least one second blockchain network to obtain the at least one first blockchain data.
4. The method according to claim 3, in, The step of acquiring cross-chain data from at least one second blockchain network based on the object identification information to obtain the at least one first blockchain data includes: For each of the second blockchain networks, determining a cross-chain node of the second blockchain network; and Based on the node type of the cross-chain node, the first blockchain data is obtained through the cross-chain node.
5. The method according to claim 4, in, The acquiring the first blockchain data through the cross-chain node based on the node type of the cross-chain node includes: In the case where it is determined that the cross-chain node is a full node, sending a data acquisition request including the object identification information to the cross-chain node, so as to obtain the first blockchain data based on the first feedback data returned by the cross-chain node; The first feedback data is obtained by the cross-chain node from the account book of the cross-chain node based on the object identification information.
6. The method according to claim 4, in, The acquiring the first blockchain data through the cross-chain node based on the node type of the cross-chain node includes: In the case where it is determined that the cross-chain node is a light node, sending a data acquisition request including the object identification information to a full node of the second blockchain network through the cross-chain node, so as to obtain the first blockchain data based on the second feedback data returned by the full node through the cross-chain node; The second feedback data is obtained by the full node from the ledger of the full node based on the object identification information forwarded by the cross-chain node.
7. The method according to claim 3, in, The step of acquiring cross-chain data from at least one second blockchain network based on the object identification information to obtain the at least one first blockchain data includes: For each of the second blockchain networks, when the second blockchain network is a public blockchain network, broadcasting a data acquisition request including the object identification information to multiple blockchain nodes included in the second blockchain network; and The first blockchain data is obtained based on the third feedback data returned by each of the multiple blockchain nodes, wherein the third feedback data is obtained by the blockchain node from the ledger of the blockchain node based on the object identification information.
8. The method according to claim 3, in, The encrypted verification information is obtained by the first client device digitally signing the verification information plaintext using the object private key, and the verification information plaintext is obtained by the first client device performing a hash calculation on the encrypted combination information; The step of confirming the identity of the first client device based on the encrypted verification information carried in the data processing request includes: Based on the object identification information, the reserved encryption combination information and the object public key are obtained, wherein the object public key The key corresponds to the private key of the object; Using the object public key to verify the encrypted verification information, to obtain first verification information, wherein, when it is determined that the verification of the encrypted verification information succeeds, the first verification information is the plain text of the verification information; Performing a hash calculation on the reserved encrypted combination information to obtain second verification information; and Based on the matching result of the first verification information and the second verification information, an authentication result of the first client device is determined.
9. The method according to claim 8, in, The encryption combination information or the reserved encryption combination information includes at least one of the following: Answer text to preset questions, password string, biometric information.
10. The method according to claim 1, further comprising: include: When it is determined that the first client device has completed the right confirmation, the object identification information and at least one of the first blockchain data are sent to the distributed private key network, so that the distributed private key network can decrypt the corresponding at least one of the first blockchain data according to the object identification information and use the respective block private keys of the at least one second blockchain network to obtain at least one second blockchain data.
11. The method according to claim 10, further comprising: include: For each of the second blockchain networks, performing text normalization processing on the second blockchain data of the second blockchain network to obtain first normalized data; Encrypting the first normalized data using a block public key corresponding to the second blockchain network to obtain second normalized data, wherein the block public key corresponds to the block private key; Writing the second normalized data into a memory; and In response to detecting that the first client device accesses the memory through a preset interface, the second normalized data of each of the at least one second blockchain network is sent to the first client device, wherein the first client device is configured to decrypt the second normalized data of the second blockchain network for each second blockchain network using the block body private key corresponding to the second blockchain network to obtain the first normalized data, and render and display the first normalized data on the display interface of the first client device.
12. The method according to any one of claims 1 to 11, further comprising: include: In the case where the at least one first blockchain data is obtained from the at least one second blockchain network across chains, the at least one first blockchain data is put on the chain in the first blockchain network.
13. The method according to any one of claims 1 to 11, further comprising: include: Writing the at least one first blockchain data into a memory; as well as In response to detecting that the first client device accesses the memory through a preset interface, the at least one first blockchain data is sent to the first client device, wherein the first client device is configured to use the block body private key corresponding to each of the at least one first blockchain data to decrypt the at least one first blockchain data to obtain at least one second blockchain data, call the text classification service to normalize the at least one second blockchain data to obtain at least one first normalized data, and render and display the at least one first normalized data on the display interface of the first client device.
14. The method according to any one of claims 1 to 11, further comprising: include: In response to a data sharing request from the first client device, obtaining first target blockchain data carried in the data sharing request; Performing text normalization processing on the first target blockchain data to obtain third normalized data; Encrypting the third normalized data to obtain fourth normalized data; as well as The fourth normalized data is uploaded to the third blockchain network.
15. The method according to claim 14, further comprising: include: In response to a data call request from a second client device, determining a data call model based on call type information carried in the data call request; Using the data call model to process fourth blockchain data included in the third blockchain network to obtain second target blockchain data, wherein the fourth blockchain data includes the fourth normalized data; and The second target blockchain data is decrypted, and the decrypted second target blockchain data is sent to the second client device.
16. A blockchain data processing platform, include: A blockchain data source management module is configured to, in response to receiving a data processing request from a first client device, obtain at least one first blockchain data from a first blockchain network based on object identification information carried in the data processing request; a private key control module, configured to confirm the authority of the first client device based on the encrypted verification information carried by the data processing request; as well as The data processing module is configured to send the at least one first blockchain data to the first client device when it is determined that the first client device has completed the right confirmation, so that the first client device can use the block body private key corresponding to each of the at least one first blockchain data to decrypt the at least one first blockchain data and obtain at least one second blockchain data.
17. The platform according to claim 16, in, The encrypted verification information is obtained by the first client device digitally signing the private key summary information using the object private key, and the private key summary information is obtained by the first client device concatenating and hashing the block private keys corresponding to the at least one first blockchain data; Wherein, the private key control module is configured as follows: Based on the object identification information, obtaining an object public key, wherein the object public key corresponds to the object private key; Using the object public key to verify the signature of the encrypted verification information to obtain first summary information, wherein, if the signature verification of the encrypted verification information succeeds, the first summary information is the private key summary information; The object identification information and the first summary information are sent to a distributed private key network, so that the distributed private key network determines at least one blockchain private key according to the object identification information, performs concatenation and hash calculation on the at least one blockchain private key to obtain second summary information, and determines the confirmation result of the first client device based on the matching result of the first summary information and the second summary information.
18. The platform according to claim 16, in, The blockchain data source management module is configured as follows: In response to the data processing request, if the at least one first blockchain data cannot be obtained from the first blockchain network, based on the object identification information, cross-chain data acquisition is performed on at least one second blockchain network to obtain the at least one first blockchain data.
19. The platform according to claim 18, in, The blockchain data source management module is configured as follows: For each of the second blockchain networks, determining a cross-chain node of the second blockchain network; as well as Based on the node type of the cross-chain node, the first blockchain data is obtained through the cross-chain node.
20. The platform according to claim 19, in, The blockchain data source management module is configured as follows: In the case where it is determined that the cross-chain node is a full node, sending a data acquisition request including the object identification information to the cross-chain node, so as to obtain the first blockchain data based on the first feedback data returned by the cross-chain node; The first feedback data is obtained by the cross-chain node from the account book of the cross-chain node based on the object identification information.
21. The platform according to claim 19, in, The blockchain data source management module is configured as follows: In the case where it is determined that the cross-chain node is a light node, sending a data acquisition request including the object identification information to a full node of the second blockchain network through the cross-chain node, so as to obtain the first blockchain data based on the second feedback data returned by the full node through the cross-chain node; The second feedback data is generated by the full node based on the object tag forwarded by the cross-chain node. The identification information is obtained from the ledger of the full node.
22. The platform according to claim 18, in, The blockchain data source management module is configured as follows: For each of the second blockchain networks, when the second blockchain network is a public blockchain network, broadcasting a data acquisition request including the object identification information to multiple blockchain nodes included in the second blockchain network; as well as The first blockchain data is obtained based on the third feedback data returned by each of the multiple blockchain nodes, wherein the third feedback data is obtained by the blockchain node from the ledger of the blockchain node based on the object identification information.
23. The platform according to claim 19, in, The encrypted verification information is obtained by the first client device digitally signing the verification information plaintext using the object private key, and the verification information plaintext is obtained by the first client device performing a hash calculation on the encrypted combination information; Wherein, the private key control module is configured as follows: Based on the object identification information, obtain reserved encryption combination information and an object public key, wherein the object public key corresponds to the object private key; Using the object public key to verify the encrypted verification information, to obtain first verification information, wherein, when it is determined that the verification of the encrypted verification information succeeds, the first verification information is the plain text of the verification information; Performing a hash calculation on the reserved encrypted combination information to obtain second verification information; and Based on the matching result of the first verification information and the second verification information, an authentication result of the first client device is determined.
24. The platform according to claim 23, in, The encryption combination information or the reserved encryption combination information includes at least one of the following: Answer text to preset questions, password string, biometric information.
25. The platform according to claim 16, wherein the private key control module is configured to: When it is determined that the first client device has completed the right confirmation, the object identification information and at least one of the first blockchain data are sent to the distributed private key network, so that the distributed private key network can decrypt the corresponding at least one of the first blockchain data according to the object identification information and use the respective block private keys of the at least one second blockchain network to obtain at least one second blockchain data.
26. The platform according to claim 25, in, The data processing module is configured as follows: For each of the second blockchain networks, performing text normalization processing on the second blockchain data of the second blockchain network to obtain first normalized data; Encrypting the first normalized data using a block public key corresponding to the second blockchain network to obtain second normalized data, wherein the block public key corresponds to the block private key; Writing the second normalized data into a memory; and In response to detecting that the first client device accesses the memory through a preset interface, the second normalized data of each of the at least one second blockchain network is sent to the first client device, wherein the first client device is configured to decrypt the second normalized data of the second blockchain network for each second blockchain network using the block body private key corresponding to the second blockchain network to obtain the first normalized data, and render and display the first normalized data on the display interface of the first client device.
27. The platform according to any one of claims 16 to 26, in, The data processing module is configured as follows: In the case where the at least one first blockchain data is obtained from the at least one second blockchain network across chains, the at least one first blockchain data is put on the chain in the first blockchain network.
28. The platform according to any one of claims 16 to 26, in, The data processing module is configured as follows: Writing the at least one first blockchain data into a memory; and In response to detecting that the first client device accesses the memory through a preset interface, the at least one first blockchain data is sent to the first client device, wherein the first client device is configured to use the block body private key corresponding to each of the at least one first blockchain data to decrypt the at least one first blockchain data to obtain at least one second blockchain data, call the text classification service to normalize the at least one second blockchain data to obtain at least one first normalized data, and render and display the at least one first normalized data on the display interface of the first client device.
29. The platform according to any one of claims 16 to 26, in, The data processing module is configured as follows: In response to a data sharing request from the first client device, obtaining first target blockchain data carried in the data sharing request; Performing text normalization processing on the first target blockchain data to obtain third normalized data; Encrypting the third normalized data to obtain fourth normalized data; as well as The fourth normalized data is uploaded to the third blockchain network.
30. The platform according to claim 29, in, The data processing module is configured as follows: In response to a data call request from a second client device, based on a call carried in the data call request Type information, determining the data call model; Using the data call model to process fourth blockchain data included in the third blockchain network to obtain second target blockchain data, wherein the fourth blockchain data includes the fourth normalized data; and The second target blockchain data is decrypted, and the decrypted second target blockchain data is sent to the second client device.
31. A blockchain data processing system, include: a first client device, a first blockchain network, a blockchain data processing platform, and a distributed private key network; Wherein, the blockchain data processing platform is configured as follows: In response to receiving a data processing request from a first client device, obtaining at least one first blockchain data from a first blockchain network based on the object identification information carried in the data processing request; Confirming the authorization of the first client device based on the encrypted verification information carried in the data processing request; When it is determined that the first client device has completed the confirmation of ownership, sending the at least one first blockchain data to the first client device; The first client device is configured as: Using the block private key corresponding to each of the at least one first blockchain data, the at least one first blockchain data is decrypted to obtain at least one second blockchain data.
32. The system according to claim 31, further comprising: include: At least one second blockchain network; Wherein, the blockchain data processing platform is configured as follows: In response to the data processing request, if the at least one first blockchain data cannot be obtained from the first blockchain network, based on the object identification information, cross-chain data acquisition is performed on at least one second blockchain network to obtain the at least one first blockchain data.
33. The system according to claim 32, in, The blockchain data processing platform is configured to: When it is determined that the first client device has completed the confirmation of ownership, sending the object identification information and at least one of the first blockchain data to the distributed private key network; The distributed private key network is configured as follows: According to the object identification information, the corresponding at least one first blockchain data is decrypted using the respective block body private keys of the at least one second blockchain network to obtain at least one second blockchain data.
34. The system according to claim 33, in, The distributed private key network is configured as follows: In response to receiving object identification information and at least one of the first blockchain data from a blockchain data processing platform, determining at least one target node from a plurality of distributed nodes based on the object identification information; Based on the private key data stored by each of the at least one target node, obtain the block body private key of each of the at least one second blockchain networks; Decrypting the corresponding at least one first blockchain data using the respective block body private key of the at least one second blockchain network to obtain at least one second blockchain data; as well as Send the at least one second blockchain data to the blockchain data processing platform.
35. The system according to claim 34, in, The private key data stored in the target node is a string of data; Wherein, the distributed private key network is configured as follows: For each of the target nodes, based on the private key data stored in the target node, obtaining the splicing sequence information and the target string data; Based on the splicing sequence information of each of the at least one target node, splicing the target string data of each of the at least one target node to obtain a target block body private key; and Based on the preset character length of the block body private key, the target block body private key is divided to obtain the block body private keys of the at least one second blockchain network.
36. The system according to claim 34, in, The private key data stored in the target node is curve coordinate data; Wherein, the distributed private key network is configured as follows: Based on the curve template, curve fitting is performed on the private key data stored in each of the at least one target node to obtain a target curve; splicing multiple parameter values included in the target curve to obtain a target block private key; and Based on the preset character length of the block body private key, the target block body private key is divided to obtain the block body private keys of the at least one second blockchain network.
37. A blockchain data processing device, include: A first acquisition module, configured to, in response to receiving a data processing request from a first client device, acquire at least one first blockchain data from a first blockchain network based on object identification information carried in the data processing request; An authentication module, configured to authenticate the first client device based on the encrypted authentication information carried in the data processing request; as well as The first sending module is used to send the at least one first blockchain data to the first client device when it is determined that the first client device has completed the right confirmation, so that the first client device can use the block body private key corresponding to the at least one first blockchain data to decrypt the at least one first blockchain data and obtain at least one second blockchain data.
38. An electronic device comprising a memory and a processor, wherein the memory stores instructions executable by the processor, and when the instructions are executed by the processor, the processor executes the method according to any one of claims 1 to 15.
39. A non-transitory computer-readable storage medium storing computer instructions, in, The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 15.
40. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 15.
