Distributed Ledger Cross-System Communication Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud computing environments, ensuring the security and verifiability of communication between separate computer systems with different security measures, such as firewalls, leads to independent message handling, resulting in differing 'truths' about message transmission and receipt.

Innovation Solution

Implementing distributed ledger technology, like blockchain, to create immutable ledger entries based on timestamps and encryption keys for interaction flows across system boundaries, establishing a single source of truth for communication without relying on a central authority.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate systems implement independent message handling with different security measures, then each system maintains its own security controls, but different truths emerge regarding message transmission and receipt

Engineering Contradiction:
Improvemessage transmission verificationVSAvoidcommunication truth consistency
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent merges separate system ledgers into a single shared distributed ledger that all systems reference. Each system's message handling events are recorded in the same ledger, creating a unified truth about message transmission and receipt that all parties can verify without conflicting records.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The distributed ledger acts as an intermediary between separate systems with different security measures. It provides a neutral, shared record that both systems can trust, eliminating the need for one system to fully trust another's security implementation while maintaining verification of message handling events.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If systems communicate across boundaries with different security measures, then security control is maintained, but verification of cross-system communication becomes complex

Engineering Contradiction:
Improvecross-system communication securityVSAvoidverification mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The distributed ledger provides a universal verification mechanism that works across all systems regardless of their individual security measures. The same ledger structure and verification process applies to all cross-system communications, simplifying the approach compared to creating system-specific verification mechanisms.

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

Solution Approach 2:

The shared ledger serves as an intermediary that simplifies verification by providing a single source of truth. Instead of complex point-to-point verification between systems with different security measures, all verification is done against the same distributed ledger, reducing overall complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If independent message handling is implemented, then system autonomy is preserved, but discrepancies in message handling records arise between systems

Engineering Contradiction:
Improvesystem independenceVSAvoidmessage handling consistency
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system maintains segmentation by allowing each organization to operate independently while referencing the same distributed ledger. Each system can continue its autonomous message handling but records events in the shared ledger, achieving both independence and consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent combines separate system records into a single distributed ledger that all systems reference. This merging eliminates discrepancies while preserving system independence, as each system continues to operate autonomously but writes to and reads from the same shared record.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20240111756A1Communications Interface Between Separate Systems Referencing Distributed Ledger
Publication Date: 2024.04.04 SAP SE
  • US20240111756A1 patent drawing
  • US20240111756A1 patent drawing
  • US20240111756A1 patent drawing

AI summary

Embodiments utilize distributed ledger technology (e.g., blockchain) to handle interaction flows for processes occurring between separate/distinct systems. A first system initiates an interaction flow, creating a first ledger entry (e.g., blockchain transaction) based upon an original timestamp and encryption keys. The interaction flow is then communicated across a boundary of the first system to a second system. The second system receives the interaction flow, and creates a second ledger entry (e.g., second blockchain transaction in the blockchain) based upon a subsequent timestamp and hash of the first ledger entry. Further cross-system interactions are similarly handled by creating additional immutable ledger entries (e.g., more blockchain transactions in the blockchain). Thus, the stored interaction flows serve as the single source of truth for communication across system boundaries. This allows verification of cross-system communications without resort to a central authority, and moreover can serve as the basis for analytical querying regarding cross-system interaction.