Blockchain Service Data Encryption via Permission-Based Key Derivation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain technology lacks privacy protection for service data, as it is a public ledger, necessitating additional measures to ensure data security and privacy.
Innovation Solution
A blockchain-based service data encryption method and apparatus that uses a node device of a key distributor and a node device of a key receiver to derive and distribute keys based on service data permission types, allowing for secure encryption and decryption of service data, ensuring privacy through consensus verification on a distributed database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If blockchain technology is used to record service data in a distributed database, then data transparency and synchronization speed are improved, but data privacy protection deteriorates because the ledger is public
Solution Approach 1:
The patent applies preliminary action by pre-distributing encryption keys to authorized nodes before data is written to the blockchain. The key distributor node generates and distributes encryption keys to key receiver nodes in advance, based on their permission types. This preliminary key distribution enables subsequent encryption of service data without requiring complex real-time key management during data recording operations.
Solution Approach 2:
The patent segments the encryption system into distinct functional nodes: a key distributor node that generates and manages encryption keys, and key receiver nodes that use these keys to encrypt and decrypt data. This segmentation separates the key management function from the data recording function, allowing the blockchain to maintain its transparent structure while adding layered encryption protection for specific data access.
2Reliability
If encryption keys are distributed to multiple key receiver nodes with different permission types, then data privacy isolation between different permission types is improved, but key distribution and management complexity increases
Solution Approach 1:
The patent applies local quality by assigning different encryption keys to key receiver nodes based on their specific permission types. Each node receives encryption keys tailored to its authorized access level and data category. This localized key assignment ensures that each node can only decrypt and access service data corresponding to its permission type, achieving fine-grained data privacy isolation without requiring a centralized key management system.
Solution Approach 2:
The patent introduces a key distributor node as an intermediary that manages the generation and distribution of encryption keys to multiple key receiver nodes. This intermediary node simplifies the overall system by centralizing key generation while distributing usage rights, reducing the complexity that would otherwise exist in direct peer-to-peer key management between all nodes.
3Reliability
If service data is encrypted before being recorded on the blockchain, then data security is improved, but the ability to quickly synchronize and record data deteriorates due to additional encryption steps
Solution Approach 1:
The patent applies preliminary action by performing encryption key distribution before data recording operations. Since keys are already distributed and stored in the nodes' memory, the actual encryption of service data requires only a simple cryptographic operation rather than complex key management during the recording process. This minimizes the impact on data recording speed while maintaining security.
Data Source
AI summary
Blockchain-based service data encryption methods and apparatuses are provided wherein by a first derived key is obtained by a node device of a key receiver, the first derived key distributed by a node device of a key distributor, wherein the first derived key is derived from a derived key of the key distributor based on a service data permission type of the key receiver and service data is encrypted based on the first derived key to obtain encrypted service data. The encrypted service data is sent to a blockchain, so that the encrypted service data is recorded in a distributed database of the blockchain after the blockchain performs consensus verification on the encrypted service. Because the derived key of the key distributor can decrypt the service data encrypted by the first derived key, the key distributor can decrypt, monitor, and manage service data uploaded by the key receiver.