Layered Blockchain Data Access for Secure Node Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing single-layer, unified P2P solutions for blockchain networks are not suitable for applications involving sensitive data, such as personal privacy or national security, due to inefficiencies in data acquisition and security concerns, and existing P2P protocols like Gossip cause message delays and redundancy.
Innovation Solution
Implementing a layered blockchain network with a witness network for service nodes and a consensus network for full nodes, using a gateway device for data allocation management to recommend access nodes based on data storage information, enabling asymmetric data deployment and efficient data acquisition.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored in a distributed ledger across multiple nodes, then data security and reliability are improved, but storage space consumption and system complexity increase
Solution Approach 1:
The patent segments data into different types (sensitive vs. non-sensitive) and stores them in different locations. Sensitive data is stored locally in encrypted form, while non-sensitive data is stored in the distributed ledger. This segmentation reduces the complexity burden on each node while maintaining overall system reliability through distributed storage of critical information.
Solution Approach 2:
The patent introduces an intermediary encryption mechanism that mediates between local storage and distributed ledger storage. Data is encrypted before being stored in the distributed ledger, and decryption keys are managed separately. This intermediary layer simplifies the complexity by providing a standardized interface for secure data storage while maintaining the benefits of distributed storage.
2Reliability
If all nodes verify and store complete data, then data reliability is improved, but processing time and energy consumption increase
Solution Approach 1:
The patent applies local quality by allowing different nodes to store different types of data based on their local needs and capabilities. Each node stores sensitive data locally for immediate access, while non-sensitive data is distributed across the network. This approach maintains data reliability through distributed storage while reducing processing time by enabling local access to frequently needed data.
3Reliability
If data is encrypted and stored distributedly, then data security is improved, but data access efficiency and processing speed decrease
Solution Approach 1:
The patent segments data into sensitive and non-sensitive portions, encrypting only the sensitive portions with separate key management. Non-sensitive data can be accessed more efficiently from the distributed ledger without heavy encryption overhead. This selective segmentation maintains high security for critical data while improving overall access efficiency.
Solution Approach 2:
The patent performs preliminary encryption and data preparation before storage in the distributed ledger. Data is pre-processed, encrypted, and structured in advance, which reduces the computational burden during access operations. This preliminary action maintains security while improving access efficiency by avoiding real-time encryption/decryption overhead during data retrieval.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A data processing method based on a blockchain network and a related device. The method comprises: receiving a data acquisition request sent by a target service node; determining a target node set from nodes included in a blockchain network according to the data type and a data identifier set of the data needing to be acquired by the target service node carried by the data acquisition request and the recorded data storage information of the nodes in the blockchain network; and sending feedback information carrying the node information included in the target node set to the target service node, the feedback information being used for instructing the target service node to acquire the requested data from the corresponding node according to the node information included in the target node set