Bringing Runtime Verification Home

Abstract

We use runtime verification (RV) to check various specifications in a smart apartment. The specifications can be broken down into three types: behavioral correctness of the apartment sensors, detection of specific user activities (known as activities of daily living), and composition of specifications of the previous types. The context of the smart apartment provides us with a complex system with a large number of components with two different hierarchies to group specifications and sensors: geographically within the same room, floor or globally in the apartment, and logically following the different types of specifications. We leverage a recent approach to decentralized RV of decentralized specifications, where monitors have their own specifications and communicate together to verify more general specifications. This allows us to re-use specifications, and combine them to: (1) scale beyond existing centralized RV techniques, and (2) greatly reduce computation and communication costs.

AllenRV: An Extensible Monitor for Multiple Complex Specifications with High Reactivity

“…T, N ight), the satisfaction of the formula is signalled as soon as the delay T has elapsed since the door has been opened, without waiting for a new event to happen. In contrast, many existing monitors [2,1,6] wait for a next event, or rely on an artificial clock event to ensure reactivity. The problem in this case is that more the clock event is fine-grained, more the monitor is overloaded by processing these artificial events, decreasing its efficiency.…”

“…-It supports highly reactive applications that rely on the quick detection of conditions being satisfied or violated, by computing changes in the output signals even when they occur between two input events. In contrast, many of the available RV monitoring tools (e.g., [2,1,6]) only recompute output signals upon change events, and rely on the introduction of regular clock events for ensuring their reactivity; however, increasing the rate of regular clock events typically hampers efficient monitoring, and therefore is subject to a reactivity vs. efficiency tradeoff. AllenRV does not impose such a dilemma, thanks to the self-generation of timeout events relative to value changes, which trigger additional output signals recomputing, without waiting the next input event.…”

COST Action IC 1402 ArVI: Runtime Verification Beyond Monitoring -- Activity Report of Working Group 1

“…Each monitor is a Moore automaton where the transition label is restricted to only atomic propositions related to the component on which the monitor is attached, and references to other monitors. Decentralized specifications were successfully applied to the monitoring of smart homes [28] where they proved to allow a better scaling than with traditional specification formalisms.…”

Oblivious Online Monitoring for Safety LTL Specification via Fully Homomorphic Encryption

“…For example, a smart home system can save lives by raising an alarm when a gas stove is left on to prevent a fire. Such a system is realized by the continuous monitoring of the data from the IoT devices in the house [8,18]. Another application of IoT devices is medical IoT (MIoT) [16].…”