Private Blockchain Data Sharing Using Decentralized Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Customers are burdened with duplicative data entry when providing information to multiple institutions, leading to a cumbersome and inefficient process.

Innovation Solution

Utilizing a shared and private blockchain to securely share customer information between partner institutions, employing decentralized identifiers (DIDs) for enhanced security and immutability, eliminating the need for duplicative data entries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If customer information is shared between multiple institutions, then data redundancy is eliminated and customer convenience is improved, but data security and privacy protection become more challenging

Engineering Contradiction:
Improvecustomer convenienceVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments customer data into distinct components stored across different blockchain nodes and institutions. Each institution holds only the specific data elements they need, while the blockchain network collectively maintains the complete customer profile. This segmentation allows data sharing for convenience while distributing security responsibilities across multiple entities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The blockchain network serves as an intermediary layer between customer data and participating institutions. Rather than direct access to customer information, institutions interact through the blockchain protocol which mediates data requests and responses. This intermediary mechanism enables convenient data sharing while maintaining security through protocol-level controls and cryptographic protection.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If a shared blockchain system is implemented, then duplicative data entry is eliminated, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improvedata entry efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The blockchain network performs multiple functions simultaneously: it serves as a distributed database, a security layer, a consensus mechanism, and an interoperability protocol. By consolidating these functions into a single universal infrastructure, the system eliminates duplicative data entry across institutions while managing complexity through multi-functionality rather than requiring separate systems for each function.

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

Solution Approach 2:

The blockchain system is designed to be self-managing through automated consensus mechanisms, smart contracts, and decentralized validation. Once implemented, the system automatically maintains data integrity, validates transactions, and coordinates between institutions without requiring complex centralized management. This self-service capability reduces operational complexity despite the initial implementation challenge.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12457265B2Blockchain-enabled sharing of private data
Publication Date: 2025.10.28 AMERICAN EXPRESS TRAVEL RELATED SERVICES CO INC
  • US12457265B2 patent drawing
  • US12457265B2 patent drawing
  • US12457265B2 patent drawing

AI summary

Disclosed are various embodiments for utilizing a shared blockchain to facilitate collaboration between partner institutions in collecting customer information. To begin, a computing device can receive an identifier associated with a user and a partner institution. Then, the computing device can obtain, based at least in part on the identifier, at least a user decentralized identifier (user DID) associated with the user and a partner decentralized identifier (partner DID) associated with the partner institution. Next, the computing device can identify a blockchain based at least in part on the partner DID. The computing device can then determine user data from the blockchain based at least in part on the user DID. Finally, the computing device can send the user data to a processing service.