Anonymous Private Shared Partitions for Secure Blockchain Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches for managing digital corollaries, which are digital representations of physical components, face challenges in secure and efficient data storage, access, sharing, and authenticity due to centralized systems that lack trusted data provenance, audit, and tamper-proof transactions.

Innovation Solution

A blockchain-based data management method is proposed, utilizing decentralized storage and smart contracts to ensure secure, trusted, and immutable data sharing among participants, with anonymous private shared partitions enabling secure operation recording on a blockchain network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If centralized systems are used for data storage and management, then data access and sharing are simplified, but data security, authenticity, and tamper-proof transaction records deteriorate

Engineering Contradiction:
Improvedata access and sharingVSAvoiddata authenticity and tamper-proof records
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments data into public and private partitions on the blockchain. Public partitions contain operation identifiers and hashed symmetric keys accessible to all nodes, while private partitions contain encrypted operation details accessible only to authorized participants. This segmentation enables simplified data access through public interfaces while maintaining reliability through cryptographic protection in private partitions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces symmetric encryption keys and hashing functions as intermediaries between data and storage. Operation details are encrypted with symmetric keys, which are then hashed and stored on the blockchain alongside operation identifiers. This intermediary layer enables centralized-like ease of access while ensuring decentralized tamper-proof verification, resolving the contradiction between operational simplicity and data reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If all operation details are recorded on the blockchain, then data provenance and auditability are improved, but data privacy and security deteriorate

Engineering Contradiction:
Improvedata provenance and auditabilityVSAvoiddata privacy exposure
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system applies local quality by storing different types of data with different security requirements in different partitions. Operation identifiers, timestamps, and hashed symmetric keys are stored in public partitions for auditability, while sensitive operation details are stored in private partitions with restricted access. This local differentiation maintains data provenance through public records while protecting privacy through selective encryption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies preliminary action by encrypting operation details with symmetric keys before storing them on the blockchain. The symmetric keys are then hashed and stored in public partitions, enabling future verification of data integrity without exposing the actual data. This preliminary encryption action ensures privacy is maintained while auditability is preserved through the hashed key references.

Inventive Principle:
Principle #10Preliminary action

3Object-affected harmful factors

If encryption is applied to protect data privacy, then data security is improved, but data access complexity and processing time worsen

Engineering Contradiction:
Improvedata privacy protectionVSAvoiddata access and processing time
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The system extracts the symmetric encryption keys from the main data storage and stores only their hashes on the blockchain. The actual encrypted data remains in private partitions, while the hashed keys in public partitions enable rapid verification without requiring decryption operations. This extraction reduces processing time by avoiding repeated encryption/decryption cycles while maintaining privacy protection.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a cryptographic copy (hash) of the symmetric key and stores it on the blockchain alongside the operation identifier. This hash copy serves as a verification reference that can be quickly accessed and compared without requiring access to the original encrypted data or the symmetric key itself, significantly reducing data access time while maintaining security.

Inventive Principle:
Principle #26Copying

4Reliability

If decentralized blockchain storage is implemented, then data security and tamper-proof records are improved, but system complexity and implementation difficulty worsen

Engineering Contradiction:
Improvetamper-proof transaction recordsVSAvoidsystem implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies homogeneity by using uniform symmetric encryption for all private partition data and consistent hashing algorithms for all symmetric keys. This standardized approach across all data types simplifies implementation compared to using different encryption schemes for different data types. The homogeneous structure makes the decentralized system easier to implement while maintaining tamper-proof reliability through consistent cryptographic verification.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS12126716B2Anonymous private shared partitions in a global total order broadcast domain networks using random symmetric encryption keys
Publication Date: 2024.10.22 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12126716B2 patent drawing
  • US12126716B2 patent drawing
  • US12126716B2 patent drawing

AI summary

An operator for a global total order broadcast domain may send an operation out of band to nodes of participating parties, receive a certificate and a signature on an operation identifier for each participating node, generate a randomness vectors for each party participating in the operation, generate a random symmetric encryption key, encrypt the certificates, the signatures, and the randomness vector for each participating party with the symmetric encryption key, encrypt the symmetric encryption key under each public key for each participating party, and hash the symmetric encryption key, and recording, by the operator, the hashed symmetric encryption key on the global total order broadcast domain.