TickTalk -- Timing API for Dynamically Federated Cyber-Physical Systems

TL;DR

Addresses the absence of time-related constructs in CPS programming by proposing TickTalk, a framework that integrates timing concepts across language, runtime, network, and device layers for dynamically federated CPS (DFCPS). Models FCPS as $FCPS = (C, E, B)$, where C are reference clocks, E ensembles with local clocks, and B code blocks, and translates programs into a dataflow graph governed by a Run-Time Manager. Defines timing semantics—frequency-based sensing, syntonization/synchronization, simultaneous actions, and latency-based constraints—and discusses runtime and network mechanisms to balance precision, power, and heterogeneity. The paper argues for networked computation (cloudlets/fog) to reduce latency, supports dynamic clock virtualization to enable multi-tenancy, and outlines a path toward verifiable timing properties in large-scale smart-city deployments.

Abstract

Although timing and synchronization of a dynamically-changing set of elements and their related power considerations are essential to many cyber-physical systems (CPS), they are absent from today's programming languages, forcing programmers to handle these matters outside of the language and on a case-by-case basis. This paper proposes a framework for adding time-related concepts to languages. Complementing prior work in this area, this paper develops the notion of dynamically federated islands of variable-precision synchronization and coordinated entities through synergistic activities at the language, system, network, and device levels. At the language level, we explore constructs that capture key timing and synchronization concepts and, at the system level, we propose a flexible intermediate language that represents both program logic and timing constraints together with run-time mechanisms. At the network level, we argue for architectural extensions that permit the network to act as a combined computing, communication, storage, and synchronization platform and at the device level, we explore architectural concepts that can lead to greater interoperability, easy establishment of timing constraints, and more power-efficient designs.

Figures (3)

• Figure 1: Dynamically enrolling separately-managed cameras scattered around a city to track a truck
• Figure 2: Pseudo-code for tracking a moving object using scattered cameras in the city.
• Figure 3: The proposed architecture. High-level programs are decomposed to an intermediate-level form in which time-based operations are explicitly represented.