Distributed Ledger Data Provisioning with Cryptographic Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data provisioning systems rely on a single data provider and lack transparency, leading to security and trust issues as they do not allow other parties to verify the validity of data and requests, which limits data authenticity and requires intermediaries for validation.

Innovation Solution

A data provisioning system utilizing a distributed ledger accessible to all parties, enabling data and requests to be validated through public and private keys, allowing multiple data providers to be accessed in a single interaction and ensuring data authenticity by recording interactions on a decentralized ledger.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single data provider is used in conventional provisioning systems, then system complexity is reduced, but data authenticity and trust are compromised

Engineering Contradiction:
Improvedata authenticityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized verification function into distributed nodes that each maintain copies of the ledger and independently verify data authenticity through cryptographic signatures, eliminating the need for a single trusted intermediary while maintaining system reliability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a distributed ledger as an intermediary layer that mediates between multiple data providers and requesters, enabling trustless verification through cryptographic proofs without requiring direct trust between parties

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a centralized database is used to store provisioned data, then data access is simplified, but security and trust verification become problematic

Engineering Contradiction:
Improvedata accessVSAvoidsecurity and trust
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into a distributed ledger replicated across multiple nodes, where each node maintains an independent copy of the data, eliminating single points of failure while maintaining ease of access through standardized query interfaces

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables each node to have local copies of the ledger data, allowing nodes to independently verify data authenticity using locally stored cryptographic keys and signatures without requiring constant communication with a central authority

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If multiple data providers are accessed through conventional systems, then data variety increases, but the number of interactions and verification steps increases

Engineering Contradiction:
Improvedata provider accessibilityVSAvoidverification time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges multiple data provider interactions into a single unified interface where the distributed ledger handles all verification operations simultaneously through parallel processing across nodes, eliminating sequential verification delays

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs preliminary cryptographic signing of data by providers and preliminary verification by nodes before actual data access requests, so that when multiple providers are accessed, verification has already been completed in advance

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10749685B2Network provisioning systems and methods
Publication Date: 2020.08.18 FIRST DATA CORP
  • US10749685B2 patent drawing
  • US10749685B2 patent drawing
  • US10749685B2 patent drawing

AI summary

Provisioning a data rate includes receiving a digitally signed request from a requester device for data and appending the request to a distributed ledger. At least one set of digitally signed data is received from at least one data provider system. Each data set is appended to the ledger and a particular data set is selected from the at least one data set. The selected data set is provided to the requester device. A digitally signed command to provision the selected data set is received from the requester device. The command is digitally signed using the public key of the requester device. The command to provision the selected data set is appended to the ledger, causing the data provider system to be notified, and the selected data set is provisioned.