Limitations of Validity Intervals in Data Freshness Management

TL;DR

This paper examines the limitations of validity intervals for enforcing data freshness in real-time databases used in CPS/IoT and intelligent data services. It identifies a feasibility gap where the data retrieval and analysis times, $R_i(O_i)$ and $A(O_i)$, can exceed the validity interval $VI(O_i)$, causing indefinite restarts and potential deadline misses, even under low contention. To address this, it proposes a feasibility condition $VI(O_i) \ge R_i(O_i) + A(O_i)$, a multi-version data approach to preserve temporal consistency, and update-reduction strategies such as On-Demand Updates, Flexible Validity Intervals, and adaptive updates leveraging data redundancy or prediction. The discussion points to future directions including new freshness metrics and a framework that lets applications specify acceptable data age and value changes to guide system optimization.

Abstract

In data-intensive real-time applications, such as smart transportation and manufacturing, ensuring data freshness is essential, as using obsolete data can lead to negative outcomes. Validity intervals serve as the standard means to specify freshness requirements in real-time databases. In this paper, we bring attention to significant drawbacks of validity intervals that have largely been unnoticed and introduce a new definition of data freshness, while discussing future research directions to address these limitations.