Distributed Ledger Data Provenance Graph
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Financial institutions face challenges in tracing and recording the origin and movement of data, leading to difficulties in identifying the source of data leakage and ensuring compliance with regulations like GDPR, especially when data is shared across multiple entities.
Innovation Solution
A method using distributed ledgers (such as blockchains) to maintain data provenance by recording operation transactions and creating a provenance graph, which tracks the creation, movement, and deletion of data items, including their sources and recipients, to determine the origin and compliance with retention policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is shared across multiple entities in open banking, then service capability and data utility are improved, but the ability to trace data origin and ensure compliance deteriorates
Solution Approach 1:
The patent applies preliminary action by embedding provenance metadata (origin identifier, creation timestamp, operation history) into data items before they are shared across entities. This preliminary tagging ensures that when data moves through multiple banks and third-party providers, its origin and transformation history are already recorded and can be traced without adding complexity to the sharing mechanism itself.
Solution Approach 2:
The patent introduces an intermediary provenance tracking system that mediates between data sharing needs and traceability requirements. This intermediary layer captures data operation events (creation, access, modification, deletion) across multiple entities and maintains a unified provenance record, allowing organizations to share data freely while the intermediary ensures compliance tracking.
2Ease of operation
If traditional data tracking methods are used, then implementation simplicity is maintained, but the ability to identify data leakage sources and ensure regulatory compliance deteriorates
Solution Approach 1:
The patent merges provenance tracking functionality with existing data management operations by integrating it into data lakes and data warehouses. Instead of implementing a separate complex tracking system, the provenance metadata is combined with standard data operations (INSERT, UPDATE, DELETE), allowing organizations to maintain simple data management workflows while simultaneously achieving reliable compliance tracking and data leakage identification.
3Measurement precision
If detailed provenance tracking is implemented, then data origin identification capability is improved, but system complexity and implementation difficulty worsen
Solution Approach 1:
The patent reduces system complexity through preliminary action by pre-defining a standardized provenance schema that includes essential metadata fields (origin identifier, creation timestamp, operation history). This preliminary structuring allows detailed tracking precision to be achieved without ad-hoc complexity, as the framework is established upfront and can be applied consistently across all data operations.
Solution Approach 2:
The patent applies parameter changes by implementing a hierarchical provenance tracking approach where organizations can adjust the level of detail captured based on their specific compliance needs. The system allows parameter adjustment in terms of which metadata fields are tracked and the granularity of operation logging, enabling detailed tracking when needed while maintaining simpler operation in less complex scenarios.
Data Source
AI summary
Data provenance techniques are provided using distributed ledgers. An exemplary method comprises obtaining an indication of a data operation that operates on a data item, wherein the data operation comprises an operation type; creating an operation transaction in a first data ledger for the data operation, wherein the operation transaction comprises an identifier of the operation type, an identifier of an operator entity that performs the data operation; an identifier of the data item, and a timestamp of the data operation; and maintaining a provenance graph comprising a provenance graph transaction for a plurality of data operations in the first data ledger and/or a second data ledger, wherein a given provenance graph transaction comprises an identifier of source data items used to create the data item associated with the given provenance graph transaction and sources of the source data items, wherein the first data ledger and/or the second data ledger are used to determine an origin and/or recipients of one or more data items.