Edge Hub Lineage Metadata for Data Provisioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In scenarios where data from geographically distributed sources, such as IoT devices, cannot be continuously transmitted to a central location quickly enough to meet Service Level Agreements or are inefficiently processed due to re-execution of analytical processes at inappropriate locations, leading to inefficiencies and non-desirable outcomes.
Innovation Solution
The implementation of a system that uses lineage metadata to identify and re-execute analytical processes on a hub device, acquiring input data from edge devices based on stored lineage metadata, allowing for efficient data processing and reducing the need for continuous data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is continuously transmitted from geographically distributed sources to a central location, then data availability for processing is improved, but transmission time and network bandwidth consumption increase
Solution Approach 1:
The patent stores lineage metadata in advance at both edge devices and hub devices, so that when re-execution is needed, the metadata is already available locally without requiring transmission from the central location. This preliminary storage of metadata resolves the contradiction by making data available immediately while avoiding continuous transmission.
Solution Approach 2:
The patent enables each hub device to have local copies of lineage metadata specific to its needs, rather than requiring all devices to access a central repository. This localization allows fast access to metadata at the edge, improving data availability without increasing transmission time or bandwidth consumption.
2Measurement precision
If analytical processes are re-executed at the original edge device location, then processing accuracy is maintained, but processing efficiency decreases due to repeated computations
Solution Approach 1:
The patent creates copies of lineage metadata from edge devices to hub devices. These metadata copies enable hub devices to re-execute analytical processes independently without needing to access the original edge device, maintaining processing accuracy while significantly improving efficiency by avoiding repeated computations at the source.
Solution Approach 2:
The patent segments the analytical workflow by separating metadata storage and process re-execution capabilities from the original data source. Hub devices can independently execute processes using local metadata copies, dividing the system into autonomous units that improve overall processing efficiency while maintaining accuracy through faithful metadata representations.
3Stability of the object's composition
If lineage metadata is stored at the central location only, then storage consistency is maintained, but data access time for edge devices increases
Solution Approach 1:
The patent implements a nested metadata storage structure where hub devices contain copies of lineage metadata that are themselves copies from the central location. This nested arrangement allows edge devices to access metadata through intermediate hub devices, maintaining the authority and consistency of the central repository while dramatically reducing access time through local cached copies.
Data Source
AI summary
Examples disclosed herein relate to data provisioning for an analytical process based on lineage metadata. In an example, a value of a parameter related to execution of an analytical process on a remote hub device may be determined based on lineage metadata stored on an edge device, wherein the analytical process is part of an analytical workflow that may be implemented at least in part on the edge device and the remote hub device. In response to a determination that the value of the parameter is above a predefined threshold, the edge device may provide to the remote hub device, input data for a future execution of the analytical process in advance of execution of the analytical process on the remote hub device without a request for the input data by the remote hub device.