Federated Data Management via Blockchain Notarized Root Hashes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data management systems face challenges in securely and efficiently sharing and verifying data between enterprises with different technological systems, particularly in cross-company supply chains, due to the resource-intensive nature of manual data management and the high costs associated with replicating data on blockchain networks.

Innovation Solution

Implementing a federated data management system that uses a blockchain network for notarizing root hash values of data objects, enabling secure and lightweight communication between partner systems through peer-to-peer verification and event management, allowing for data authenticity verification without replicating complete data copies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete data copies are replicated on blockchain networks for verification, then data authenticity and security are improved, but computational resources and storage costs increase significantly

Engineering Contradiction:
Improvedata authenticity verificationVSAvoidcomputational resources for data verification
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential verification element (hash value) from the complete data object and stores it on the blockchain. This allows verification of data authenticity without replicating the entire data copy, significantly reducing storage requirements and computational resources while maintaining the ability to verify data integrity through hash comparison.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses cryptographic hashing to create a compact digital fingerprint (hash value) of the complete data object. This hash copy serves as a lightweight representation that can be stored and verified on the blockchain, enabling authentication without physically copying the original large data files.

Inventive Principle:
Principle #26Copying

2Device complexity

If manual data management is used between enterprises, then system complexity is reduced, but security and efficiency of data exchange deteriorate

Engineering Contradiction:
Improvesystem architecture simplicityVSAvoiddata exchange security
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent introduces a blockchain-based intermediary layer that sits between enterprise systems. This intermediary automatically verifies data authenticity through hash comparison and manages verification processes, providing enhanced security without requiring complex changes to the underlying enterprise systems. The blockchain acts as a trusted mediator that both parties can rely on.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If root hash values are notarized on blockchain network, then data sharing security is improved, but system configuration complexity increases

Engineering Contradiction:
Improvedata sharing securityVSAvoidsystem configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal notarization interface that can handle multiple data types and verification scenarios through a single standardized mechanism. The hash-based verification system serves multiple purposes: authentication, integrity verification, and audit trail creation, reducing the need for separate configuration systems for different verification needs.

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

Data Source

PatentUS11880383B2Federated data management between partner systems
Publication Date: 2024.01.23 SAP SE
  • US11880383B2 patent drawing
  • US11880383B2 patent drawing
  • US11880383B2 patent drawing

AI summary

Methods, systems, and computer-readable storage media for notarized communication between platform systems is provided. A first data object is notarized by storing a first root hash value at a blockchain network. The first root hash value is notarized in response to a transaction request received through a first notarization interface instantiated at a first platform system. A subscription for the first platform system is established to provide notification events in relation to a second data object. The first root hash value comprises an object reference to a second root hash value for the second data object. A notification event is sent for the second data object to the first platform system, comprising a third root hash value of a third data object associated with the second data object. The third data objects is notarized at the blockchain network by the second platform system through a second notarization interface.