Skip to main navigation Skip to search Skip to main content

Using run-time checking to provide safety and progress for distributed cyber-physical systems

Research output: Contribution to conferencePaperpeer-review

6 Scopus citations

Abstract

Cyber-physical systems (CPS) may interact and manipulate objects in the physical world, and therefore ideally would have formal guarantees about their behavior. Performing static-time proofs of safety invariants, however, may be intractable for systems with distributed physical-world interactions. This is further complicated when realistic communication models are considered, for which there may not be bounds on message delays, or even that messages will eventually reach their destination. In this work, we address the challenge of proving safety and progress in distributed CPS communicating over an unreliable communication layer. This is done in two parts. First, we show that system safety can be verified by partially relying upon run-time checks, and that dropping messages if the run-time checks fail will maintain safety. Second, we use a notion of compatible action chains to guarantee system progress, despite unbounded message delays. We demonstrate the effectiveness of our approach on a multi-agent vehicle flocking system, and show that the overhead of the proposed run-time checks is not overbearing.

Original languageEnglish
Pages287-296
Number of pages10
DOIs
StatePublished - 2013
Externally publishedYes
Event2013 IEEE 19th International Conference on Embedded and Real-Time Computing Systems and Applications, RTCSA 2013 - Taipei, Taiwan, Province of China
Duration: 19 Aug 201321 Aug 2013

Conference

Conference2013 IEEE 19th International Conference on Embedded and Real-Time Computing Systems and Applications, RTCSA 2013
Country/TerritoryTaiwan, Province of China
CityTaipei
Period19/08/1321/08/13

Fingerprint

Dive into the research topics of 'Using run-time checking to provide safety and progress for distributed cyber-physical systems'. Together they form a unique fingerprint.

Cite this