Personal Blockchain Unit Files for Scalable Transaction Finality

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional blockchain and distributed ledger technologies face scalability issues, finality challenges, and difficulties in deleting transactions, leading to inefficiencies and high power consumption, particularly when managing virtual currency and sensitive data like personal information and medical treatment.

Innovation Solution

An information processing system that generates and updates unit files containing transaction histories for each user account independently, using a distributed ledger system with personal blockchains and finality transaction files, ensuring secure and efficient management of data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional blockchain or distributed ledger is used to manage transactions, then data security and tamper resistance are improved, but scalability and transaction approval speed deteriorate

Engineering Contradiction:
Improvedata securityVSAvoidtransaction approval speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the distributed ledger into unit files that are segmented by specific objects (e.g., by account, by transaction type, by time period). Each unit file contains only the transactions related to its specific object, allowing parallel processing and retrieval of only relevant data. This segmentation enables the system to maintain security through distributed storage while improving scalability and transaction approval speed by reducing the data volume that must be processed for each transaction.

Inventive Principle:
Principle #1Segmentation

2Reliability

If conventional blockchain or distributed ledger is used to manage transactions, then data security is improved, but power consumption increases

Engineering Contradiction:
Improvedata securityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by stationary object

Solution Approach 1:

The patent extracts and stores only the necessary transaction data related to specific objects in unit files, rather than storing and processing the entire distributed ledger for every operation. By extracting and maintaining only relevant transaction histories in organized unit files, the system reduces the computational burden and data transmission requirements, thereby lowering power consumption while maintaining data security through selective verification.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If transactions are approved by a large number of nodes, then data security and tamper resistance are improved, but device complexity and management difficulty increase

Engineering Contradiction:
Improvetamper resistanceVSAvoidsystem management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements local quality by organizing unit files with specific structures optimized for their particular purposes (e.g., different formats for different transaction types, hierarchical organization by account and time). Each unit file can be managed independently with appropriate access controls and verification mechanisms tailored to its specific content, reducing overall system complexity while maintaining tamper resistance through localized security measures.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12598090B2Information processing system
Publication Date: 2026.04.07 NO 1 SOLUTIONS INC
  • US12598090B2 patent drawing
  • US12598090B2 patent drawing
  • US12598090B2 patent drawing

AI summary

A personal blockchain generation unit 51 of a service providing server group 1 generates or updates a unit file containing a history of transaction of data change related to a predetermined unit such as an account and a data for a plurality of users in an account management service of virtual currencies or medical information management service. A finality transaction file generating unit 52 generates a file containing a content of the transaction when the transaction in which the predetermined user is involved for each of the transaction related to the predetermined unit is finished. A management control unit 53 performs a control for storing the unit file independently from the other units and managing the unit file separately from the other units file for each of the units in a predetermined service. At this time, the unit file is managed as a block of a blockchain.