Cross-Ledger Gateway for Distributed Ledger Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing distributed ledger systems lack interoperability, making it difficult for multiple ledgers to communicate and share data securely and efficiently.

Innovation Solution

The implementation of a Cross-Ledger Gateway (CLG) that registers with Distributed Ledger Management Systems (DLMS) to facilitate cross-ledger recordation requests, allowing for the creation of records on one distributed ledger while recording a reference to these records on another ledger.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If distributed ledger systems operate independently with their own protocols, then each ledger maintains security and data integrity, but interoperability between ledgers is lost

Engineering Contradiction:
Improvedata integrityVSAvoidinteroperability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a Cross-Ledger Gateway (CLG) as an intermediary component that receives cross-ledger recordation requests from one distributed ledger system and forwards them to another distributed ledger system. The CLG acts as a mediator that enables communication and data exchange between independent ledger systems while preserving their individual security models and protocols, thus resolving the contradiction between maintaining data integrity and achieving interoperability

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If cross-ledger recordation is implemented without a gateway, then direct communication between ledgers is achieved, but security and protocol compatibility issues arise

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The Cross-Ledger Gateway serves as a security intermediary that validates, authenticates, and manages cross-ledger communications. It implements security protocols, permission verification, and data validation mechanisms before forwarding requests between ledgers, ensuring that communication efficiency is maintained while security and protocol compatibility are preserved through the gateway's mediation layer

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple distributed ledgers use different protocols, then each ledger can be optimized for its specific use case, but complexity of integration increases

Engineering Contradiction:
Improveprotocol flexibilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Cross-Ledger Gateway is designed as a universal interface that can handle multiple different distributed ledger protocols and communication formats. It provides a standardized method for receiving and forwarding cross-ledger requests across diverse ledger systems, allowing each ledger to maintain its protocol optimizations while the gateway handles the integration complexity through its multi-functional capability to support various protocols

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

Data Source

PatentUS12298964B2Systems and methods for secure cross-ledger recordation
Publication Date: 2025.05.13 VERIZON PATENT & LICENSING INC
  • US12298964B2 patent drawing
  • US12298964B2 patent drawing
  • US12298964B2 patent drawing

AI summary

A system described herein may receive a cross-ledger recordation request that includes an information payload, an indication of a target distributed ledger to which the information payload should be recorded, and an indication of a second distributed ledger to which a reference that refers to the first distributed ledger should be recorded. The system may provide the information payload to a second system that implements the first distributed ledger. The system may determine that at least a portion of the information payload has been recorded to the first distributed ledger based on providing the information payload to the second system that implements the first distributed ledger. Based on determining that at least the portion of the information payload has been recorded to the second distributed ledger, the system may record the reference, that refers to the first distributed ledger, to the second distributed ledger.