Blockchain Data Storage Split Between Public and Confidential Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data storage systems lack flexibility in managing data treatment for each participant entity, and there is a need for improved systems that balance data usability and reliability, particularly in blockchain networks.

Innovation Solution

A data storage system that separates data into confidential and public components, stores public data on a blockchain and confidential data on a local server, using tamper proofs to ensure data integrity and flexibility in data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is stored in a single location, then storage simplicity is maintained, but data loss risk increases due to media failure or destruction

Engineering Contradiction:
Improvedata loss riskVSAvoidstorage system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides data into multiple independent segments and stores them across different storage media and locations. This segmentation ensures that if one medium fails, other segments remain intact and can be used to recover the complete data set, thereby reducing data loss risk while distributing storage complexity across multiple independent units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a hierarchical storage architecture where data segments are organized in nested structures across multiple layers: local storage media, distributed storage nodes, and cloud-based repositories. This nested arrangement allows data to be accessed from multiple levels, providing redundancy and fault tolerance without requiring complete system duplication.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If data is backed up to multiple locations, then data security is improved, but storage time and resources increase

Engineering Contradiction:
Improvedata securityVSAvoidstorage time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent establishes predetermined data distribution rules and storage pathways before data loss occurs. Data segments are pre-configured with metadata indicating their location and recovery priorities, enabling rapid retrieval and reconstruction without requiring time-consuming analysis during emergency recovery scenarios.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements automated data replication and distribution mechanisms that operate without manual intervention. Data segments are automatically distributed across storage media according to predefined policies, and recovery processes are self-initiated when data loss is detected, reducing the time investment required for manual backup and recovery operations.

Inventive Principle:
Principle #25Self-service

3Reliability

If data is segmented and distributed across multiple storage media, then data loss risk is reduced, but data retrieval complexity increases

Engineering Contradiction:
Improvedata loss riskVSAvoiddata retrieval complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent incorporates metadata tracking systems that continuously monitor the location and status of data segments across distributed storage media. This feedback mechanism provides real-time information about data segment positions, enabling the retrieval system to automatically construct efficient recovery pathways without requiring complex manual coordination or exhaustive searching.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4302219B1Data storage system and data storing method
Publication Date: 2026.05.20 DENSO CORP
  • EP4302219B1 patent drawingFigure 1
  • EP4302219B1 patent drawingFigure 2
  • EP4302219B1 patent drawingFigure 3

AI summary

A data storage system (10) includes a node (16) configured to store a blockchain (BC) and a data storage server (26). The node (16) is further configured to, upon receiving the data from a data source, separate the data into confidential data and public data, obtain a tamper proof of the confidential data, send the separated confidential data to the data storage server (26), and store the public data and the tamper proof on the blockchain (BC). The data storage server (26) is configured to store the confidential data upon receiving the confidential data from the node (16).