Blockchain Entity Certification via Distributed Node Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, dependency on network connectivity, limited access, and lack of data redundancy, which hinder efficient management of entity certification processes, especially in blockchain-based food supply chains where authenticity and integrity of certificates are critical.

Innovation Solution

A decentralized database system using blockchain technology that enables distributed storage, immutability, and smart contracts to manage entity certifications, ensuring origin and integrity through digital signatures and endorsement processes, allowing multiple participants to securely share and validate certification information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a centralized database is used to store certification data, then data management and control are simplified, but system reliability deteriorates due to single point of failure

Engineering Contradiction:
Improvedata management complexityVSAvoidsystem reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the centralized database into multiple distributed nodes across different locations. Each node stores a copy of the certification data, eliminating the single point of failure. The system segments data storage and processing across multiple independent entities, maintaining simplicity through standardized interfaces while improving reliability through redundancy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements multiple copies of certification data stored across different database nodes. Instead of a single centralized copy, the system maintains replicated data across distributed locations, ensuring that if one node fails, other nodes continue to provide access to the certification information, thereby improving system reliability.

Inventive Principle:
Principle #26Copying

2Device complexity

If a centralized database is used, then data storage is simplified, but data accessibility deteriorates due to network dependency and bottlenecks

Engineering Contradiction:
Improvestorage system complexityVSAvoiddata access speed
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments data access into parallel queries that can be executed simultaneously across multiple distributed nodes. Instead of a single sequential access path through a centralized database, the system divides read operations into concurrent requests to multiple nodes, reducing network bottleneck effects and improving overall data access speed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a single-point data storage model to a multi-dimensional distributed storage architecture. Data is replicated across multiple spatial locations (different database nodes), allowing access from multiple directions simultaneously, which reduces the impact of network latency and improves productivity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Device complexity

If a centralized database maintains a single copy of data, then data consistency is simplified, but data redundancy is insufficient leading to loss upon failure

Engineering Contradiction:
Improvedata consistency managementVSAvoiddata redundancy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent creates multiple copies of certification data across distributed database nodes. Each node maintains a replica of the data, ensuring that if the primary node or any single node fails, the replicated copies continue to preserve the data. This multi-copy approach significantly improves data redundancy and protection against failure.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent implements data replication before any failure occurs, creating a cushion of redundant data copies that can compensate for future failures. By maintaining multiple copies in advance, the system prepares ahead of time to continue operating and accessing certification data even if one or more nodes fail, thereby improving reliability without adding complex failure detection mechanisms.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Adaptability or versatility

If multiple participants are involved in certification, then certification comprehensiveness is improved, but system complexity increases due to multiple authentication requirements

Engineering Contradiction:
Improvecertification process flexibilityVSAvoidauthentication system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal authentication mechanism that handles multiple participants and certification types through a single standardized interface. The database system provides unified access methods for different certifiers and certificate types, allowing the system to accommodate multiple participants without proportionally increasing complexity through standardized protocols and consistent data structures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11856109B2Entity certification management
Publication Date: 2023.12.26 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11856109B2 patent drawing
  • US11856109B2 patent drawing
  • US11856109B2 patent drawing

AI summary

An example operation may include one or more of receiving, by a certificate issuer node, an asset certification request from an asset producer node over a blockchain, endorsing, by the certificate issuer node, an asset certificate in response to detection of the asset certificate issued to the asset producer node by another certificate issuer node, and recording a signature of the certificate issuer node into an asset producer node certification record on the blockchain.