No abstract

Time-Sensitive Networking (TSN) extends IEEE 802.1 Ethernet for safety-critical and real-time applications in several areas, for example, automotive, aerospace or industrial automation. However, many of these systems also have stringent security requirements, and security attacks may impair safety. Given a TSN-based distributed architecture, a set of applications with tasks and messages as well as a set of security and redundancy requirements, the authors are interested to synthesise a system configuration such that the real-time, safety and security requirements are upheld. The Timed Efficient Stream Loss-Tolerant Authentication (TESLA) low-resource multicast authentication protocol is used to guarantee the security requirements and redundant disjunct message routes to tolerate link failures. The authors consider that tasks are dispatched using a static cyclic schedule table and that the messages use the time-sensitive traffic class in TSN, which relies on schedule tables (called Gate Control Lists, GCLs) in the network switches. A configuration consists of the schedule tables for tasks as well as the disjoint routes and GCLs for messages. A Constraint Programing-based formulation, which can be used to find an optimal solution with respect to the cost function, is proposed. Additionally, a Simulated Annealing-based metaheuristic, which can find good solution for large test cases, is proposed. The authors evaluate both approaches on several test cases.

No abstract

Distributed real-time systems often rely on timetriggered communication and task execution to guarantee endto-end latency and time-predictable computation. Such systems require a reliable synchronized network time to be shared among end-systems. The IEEE 1588 Precision Time Protocol (PTP) enables such clock synchronization throughout an Ethernet-based network. While security was not addressed in previous versions of the IEEE 1588 standard, in its most recent iteration (IEEE 1588(IEEE -2019, several security mechanisms and recommendations were included describing different measures that can be taken to improve system security and safety. One proposal to improve security and reliability is to add redundancy to the network through modifications in the topology. However, this recommendation omits implementation details and leaves the question open of how it affects synchronization quality.This work investigates the quality impact and security properties of redundant PTP deployment and proposes an observation window-based multi-domain, PTP end-system, design to increase fault-tolerance and security. We implement the proposed design inside a discrete-event network simulator and evaluate its clock synchronization quality using two test-case network topologies with simulated faults.

Time-Sensitive Networking (TSN) aims to extend the IEEE 802.1Q Ethernet standard with real-time and time-aware capabilities. Each device's transmission of time-critical frames is done according to a so-called Gate Control List (GCL) schedule via the timed-gate mechanism described in IEEE 802.1Qbv. Most schedule generation mechanisms for TSN have a constraining assumption that both switches and end-systems in the network must have at least the TSN capabilities related to scheduled gates and time synchronization. However, many TSN networks use off-the-shelf end-systems, e.g., for providing sensor data, which are not scheduled and/or synchronized.In this paper, we propose a more flexible scheduling strategy that considers a worst-case delay analysis within the scheduling synthesis step, leveraging the solution's optimality to support TSN networks with unscheduled and unsynchronized end-systems while still being able to guarantee bounded latency for critical messages. Our method enables real-world systems that feature offthe-shelf microcontrollers and sensor nodes without TSN capabilities connected to state-of-the-art TSN networks to communicate critical messages in a real-time fashion. We evaluate our approach using both synthetic and real-world test cases, comparing it with existing scheduling mechanisms. Furthermore, we use OMNET++ to validate the generated GCL schedules.