Decentralized Data Sharing via Blockchain Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases are inefficient for secure and precise data sharing among multiple clients, as they lack decentralized solutions for secure data access and management.

Innovation Solution

A decentralized system using a blockchain-based approach, where multiple nodes communicate to share data securely through a distributed ledger, utilizing smart contracts and consensus protocols for secure and precise data sharing among multiple clients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used for data storage and sharing, then data management and control are easy, but data sharing efficiency and security among multiple clients are poor

Engineering Contradiction:
Improvedata management and controlVSAvoiddata sharing efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent divides the centralized database into multiple distributed nodes across a blockchain network. Each node maintains a copy of the ledger, eliminating the single-point bottleneck while enabling parallel data access and sharing operations across multiple clients simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces smart contracts as intermediary automated protocols that mediate data access requests between clients. These self-executing contracts enforce access policies, validate requests, and manage data sharing permissions without requiring manual intervention, thereby improving both efficiency and security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If a centralized database is used for data storage, then data redundancy is minimized, but secure data sharing among multiple services is inefficient

Engineering Contradiction:
Improvedata redundancyVSAvoidsecure data sharing
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent creates replicated copies of the data ledger across multiple distributed nodes in the blockchain network. Each node holds an identical copy, ensuring data availability and redundancy while maintaining consistency through consensus mechanisms. This enables reliable secure sharing among multiple services without excessive redundancy.

Inventive Principle:
Principle #26Copying

3Reliability

If decentralized data sharing is implemented, then data accessibility and security are improved, but system complexity increases

Engineering Contradiction:
Improvedata security and accessibilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal blockchain infrastructure that handles multiple functions including data storage, access control, authentication, and transaction management within a single integrated system. This multi-functional platform reduces the need for separate systems and simplifies the overall architecture despite the decentralized nature.

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

Solution Approach 2:

The patent employs smart contracts that automatically execute data access policies and authentication procedures without requiring manual intervention or complex centralized coordination. The system self-regulates through automated consensus mechanisms, reducing operational complexity while maintaining high security and accessibility standards.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11271742B2Decentralized secure data sharing
Publication Date: 2022.03.08 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11271742B2 patent drawing
  • US11271742B2 patent drawing
  • US11271742B2 patent drawing

AI summary

An example operation may include one or more of authenticating, by a first service node, to a first client node, receiving, by the first service node, a data access request from the first client node, comprising request parameters and a request token, generating, by the first service node, a receipt key corresponding to the data access request, and sharing data with a second client node based on the request token and the receipt key.