Blockchain Subscription Service for Decentralized Data Entitlements

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, dependency on network connectivity, bottlenecks during high traffic, and limited data access, which hinder efficient data management and security.

Innovation Solution

A decentralized database system using blockchain technology, where multiple nodes communicate to store and validate data, ensuring immutability, security, and accessibility through smart contracts and consensus protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used to store and maintain data at one location, then data management and control are simplified, but the system has a single point of failure and limited data access

Engineering Contradiction:
Improvedata managementVSAvoidfault tolerance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across a blockchain network. Each node maintains a copy of the data, eliminating the single point of failure while preserving data management capabilities through distributed consensus mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates multiple copies of the data across different nodes in the blockchain network. Each node stores and validates identical data copies, ensuring that data remains accessible and intact even if some nodes fail, thus resolving the reliability issue while maintaining operational simplicity.

Inventive Principle:
Principle #26Copying

2Ease of operation

If a centralized database is used, then security control is simplified, but data access is limited and bottlenecks occur during high traffic

Engineering Contradiction:
Improvesecurity controlVSAvoiddata access efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent divides the centralized security control into distributed security validation across multiple nodes. Each node independently validates data access requests according to the smart contract rules, eliminating bottlenecks while maintaining consistent security policies through the decentralized consensus mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges security control functions across multiple distributed nodes into a unified decentralized security system. All nodes collectively enforce access policies through consensus, combining their computational resources to handle high traffic without creating single-point bottlenecks while maintaining coherent security control.

Inventive Principle:
Principle #5Merging (Combining)

3Quantity of substance

If data is stored in a single location, then data redundancy is minimized, but data loss is difficult to retrieve

Engineering Contradiction:
Improvedata redundancyVSAvoiddata retrieval
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent creates multiple identical copies of the data across different nodes in the blockchain network. Each node stores a complete copy of the data, providing inherent redundancy that enables data retrieval even if some nodes are compromised or fail, thus resolving the data loss issue while maintaining minimal unnecessary redundancy.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11646900B2Subscription service for networks
Publication Date: 2023.05.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11646900B2 patent drawing
  • US11646900B2 patent drawing
  • US11646900B2 patent drawing

AI summary

An example operation may include one or more of releasing, by a subscription service node, at least one blockchain transaction to a plurality of subscribing blockchain nodes requiring direct entitlement access, executing, by the subscription service node, a smart contract to calculate secondary entitlements triggered by the at least one blockchain transaction, determining, by the subscription service node, portions of second entitlement data sets allowed to be accessed by a subset of the plurality of the subscribing blockchain nodes, and sending verification data to the plurality of the subscribing blockchain nodes for verification of the second entitlement data sets.