Decentralized Document Management via Blockchain Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing documents in a small organization with multiple PCs without an expensive server is challenging due to synchronization and consistency issues, security concerns when sharing information between organizations, and the difficulty of preventing malicious falsification and proving non-falsification.

Innovation Solution

A peer-to-peer document management system that synchronizes document data across PCs using hash values and blockchain technology, with a remote server for backup and reference authority confirmation, allowing for decentralized document management and non-falsification proof.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a server is used to manage documents in an organization, then document management reliability and security are improved, but system cost and complexity increase

Engineering Contradiction:
Improvedocument management reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the centralized server system into multiple distributed PC nodes that each maintain document copies and participate in blockchain validation. This segmentation eliminates the single point of failure inherent in server-based systems while distributing the management function across multiple independent units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each PC node in the patent autonomously maintains its own document copies and participates in blockchain validation without requiring centralized server control. The nodes self-organize into a peer-to-peer network where each participant contributes to the overall system reliability through decentralized document storage and verification.

Inventive Principle:
Principle #25Self-service

2Device complexity

If multiple PCs are connected without a server to reduce cost, then system cost decreases, but document synchronization and consistency become problematic

Engineering Contradiction:
Improvesystem complexityVSAvoiddocument consistency
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism through blockchain technology where each document update is hashed and recorded in a distributed ledger. All PC nodes continuously verify document consistency by comparing their local copies against the blockchain record, creating a self-correcting system that automatically detects and resolves synchronization issues.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies preliminary action by pre-hashing document data before distribution and recording the hash values in the blockchain in advance. This allows each PC node to verify document integrity and consistency before actual document updates occur, preventing synchronization conflicts rather than resolving them after they arise.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If document data is shared between organizations to enable collaboration, then information accessibility improves, but security risks and falsification vulnerabilities increase

Engineering Contradiction:
Improveinformation sharing capabilityVSAvoiddata security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces blockchain technology as an intermediary layer between collaborating organizations. Instead of directly sharing document files between organizations, the system shares cryptographically hashed document records on the blockchain. This intermediary mechanism enables verification of document authenticity and integrity without exposing the actual document contents to potential tampering or unauthorized access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates cryptographic copies of document data in the form of hash values that are distributed across the blockchain network. These copies serve as verifiable proofs of document existence and integrity without requiring organizations to share or store the actual document files, thereby enabling security verification while minimizing security exposure.

Inventive Principle:
Principle #26Copying

4Reliability

If a centralized server is used to prevent falsification, then document authenticity is maintained, but the system becomes vulnerable to administrator privilege abuse

Engineering Contradiction:
Improvedocument authenticityVSAvoidadministrator privilege risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the centralized authentication authority into multiple distributed PC nodes that collectively validate document authenticity through blockchain consensus. No single node or administrator has the power to unilaterally alter document records, as changes require consensus across the distributed network, thereby eliminating the administrator privilege vulnerability inherent in centralized systems.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12086280B2Document management system
Publication Date: 2024.09.10 INST OF MEDICAL INFORMATION TECH CO LTD
  • US12086280B2 patent drawing
  • US12086280B2 patent drawing
  • US12086280B2 patent drawing

AI summary

[Problem] To ensure security in document management in small-scale organizations without using expensive servers by establishing peer-to-peer connection of a plurality of PCs, and to enable mutual non-tampering certification among connected organizations.[Solution] Provided is a document management system in which is formed a PC group in which a plurality of small electronic computers for creating, recording, and viewing a document are connected via a communication channel, said system comprising i) an in-PC cluster document synchronization means which causes a document recorded on one PC to be incorporated in recordings of other PCs belonging to a cluster, (ii) a document hash value generation means which generates a hash value of the document, and (iii) a blockchain generation means which assembles a plurality of the generated hash values and forms a block, connects the block to the existing blocks and forms a blockchain, and synchronizes and records same on the PCs within the PC cluster.