Provenance Storage Prioritization for Cloud Data Pipelines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Provenance systems in distributed cloud environments face challenges in managing vast arrays of configuration and policy combinations, leading to cumbersome handling and inefficient storage of metadata, which hinders effective utilization of provenance information.

Innovation Solution

A method and arrangement for managing provenance information in a distributed cloud environment that involves obtaining declarative intents, deriving storage requirements and priorities, estimating storage capacity, and reducing data amounts by compressing, removing indexing, or moving provenance information to remote storage when thresholds are met, ensuring efficient storage and access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If provenance systems capture a massive amount of provenance information over time, then the completeness and usefulness of provenance data is improved, but the storage capacity requirements and system complexity increase significantly

Engineering Contradiction:
Improveprovenance information completenessVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments provenance information into different priority levels (first level priority and second level priority), allowing the system to manage and store different types of provenance data differently. This segmentation enables the system to maintain complete provenance information while reducing complexity by organizing data hierarchically based on importance and access frequency.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a vast array of configuration and policy combinations are provided for provenance systems, then the adaptability and customization options are improved, but the ease of operation and configuration difficulty worsen

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidconfiguration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system automatically derives storage requirements and priority levels from declarative intents without requiring manual configuration of complex policies. The configuration component autonomously determines storage capacity needs, data amount reductions, and priority assignments based on simple intent statements, eliminating the need for operators to navigate vast arrays of configuration options while maintaining adaptability.

Inventive Principle:
Principle #25Self-service

3Quantity of substance

If the data amount for storage of provenance information is reduced by compressing or moving data, then the storage capacity efficiency is improved, but the access time and data retrieval speed may worsen

Engineering Contradiction:
Improvestorage capacity utilizationVSAvoiddata access time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent applies different storage strategies to different priority levels of provenance information. First level priority data (which requires frequent access) is stored with higher quality and accessibility, while second level priority data (which can tolerate longer access times) is compressed or moved to remote storage. This local quality differentiation optimizes both storage capacity utilization and data access performance based on specific data characteristics.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20260010314A1Managing provenance information for data processing pipelines
Publication Date: 2026.01.08 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20260010314A1 patent drawing
  • US20260010314A1 patent drawing
  • US20260010314A1 patent drawing

AI summary

A configuration component configured to manage provenance information associated with one or more interconnected provenance entities in a provenance system for data processing pipelines in a distributed cloud environment over a network interface. Each of the data processing pipelines is configured to read in data, transform the data, and output transformed data.