On the Runtime Enforcement of Timed Properties

Abstract

Runtime enforcement refers to the theories, techniques, and tools for enforcing correct behavior of systems at runtime. We are interested in such behaviors described by specifications that feature timing constraints formalized in what is generally referred to as timed properties. This tutorial presents a gentle introduction to runtime enforcement (of timed properties). First, we present a taxonomy of the main principles and concepts involved in runtime enforcement. Then, we give a brief overview of a line of research on theoretical runtime enforcement where timed properties are described by timed automata and feature uncontrollable events. Then, we mention some tools capable of runtime enforcement, and we present the TiPEX tool dedicated to timed properties. Finally, we present some open challenges and avenues for future work.

Online Shielding for Stochastic Systems

“…Runtime enforcement (RE) [12,30,41] covers a wide range of techniques to enforce the correctness of a controller at run-time. The concept of a correct-byconstruction safety-shield to enforce such correctness with respect to a temporal logic specification was first proposed in [7].…”

Runtime Enforcement with Reordering, Healing, and Suppression

“…We can mention security automata [26]; which can stop the underlying system upon property violation, edit-automata [23] and generic enforcement monitors [12] which can insert or suppress actions. Regarding runtime enforcement of timed properties, [13] provides a recent overview of related work. As an example, [9] considers runtime enforcement for timed specifications modelled as timed automata.…”

“…Runtime verification aims at verifying whether an execution trace satisfies a given correctness property. Runtime enforcement [13,20,21,24] goes beyond classic runtime verification by correcting the execution that deviates from its expected behaviour to ensure the satisfaction of a given property. To do so, a so-called enforcement monitor (or enforcer in short) accepts as input a sequence of actions and generates as output a sequence of actions respecting the property.…”

Runtime enforcement of timed properties usinggames

“…In case of timed properties, the EM acts as a delaying lter on the input ([PFJ + 13, PFJM14b, PFJM15]) ; see [FP19] for a recent overview. It uses a buer in order to store input events and releases them only at an instant where the satisfaction of the property is ensured (possibly never).…”