An integrated architecture for future car generations

Obermaisser, Roman; Peti, P.; Tagliabò, Fulvio

doi:10.1007/s11241-007-9015-4

Cited by 7 publications

(3 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Fortunately, there are also several description methods available for this purpose. Examples are SysML or a modelling language presented by Huber to describe execution platforms in DECOS .…”

Section: Discussionmentioning

confidence: 99%

The Real‐Time Systems Compiler: migrating event‐triggered systems to time‐triggered systems

Scheler

Schröder-Preikschat

2011

Softw Pract Exp

View full text Add to dashboard Cite

SUMMARY In this paper, we present a prototype of the Real‐Time Systems Compiler (RTSC). The RTSC is a compiler‐based tool that enables the migration from event‐triggered to time‐triggered real‐time systems. This is achieved by replacing the real‐time systems architecture of a given real‐time system. The real‐time systems architecture governs the structural properties of the white‐box view of a real‐time system: how are tasks attached to events and how are dependencies between different tasks implemented. The RTSC uses an abstraction called Atomic Basic Blocks (ABBs) to hide the real‐time systems architecture and capture all relevant dependencies of an event‐triggered system in a global ABB‐graph. The RTSC automatically extracts that ABB‐graph from an event‐triggered real‐time system given as source code, transforms that ABB‐graph appropriately, and maps it to a statically computed schedule that could be executed by standard time‐triggered real‐time operating systems. Important temporal properties of the physical environment of the real‐time system needed for that transformation are stored in a system model provided as additional input to the RTSC. Furthermore, we demonstrate the applicability of our approach and the operation of our prototype by transforming an event‐triggered control application into a time‐triggered equivalent. Copyright © 2011 John Wiley & Sons, Ltd.

show abstract

Section: Discussionmentioning

confidence: 99%

The Real‐Time Systems Compiler: migrating event‐triggered systems to time‐triggered systems

Scheler

Schröder-Preikschat

2011

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…For instance, modern cars rely on microcontrollers, interconnected by a Controller Area Network (CAN), for a variety of functions from controlling the brakes and engine to on-board entertainment. Driven by the increasing complexity of microcontrollers, and in an effort to simplify architecture design and save cost, manufacturers are integrating functionality onto a smaller number of those microcontrollers [28]. This means that sensitive applications now run alongside non-critical ones, increasing the need for security mechanisms to protect confidentiality and integrity.…”

Section: Introductionmentioning

confidence: 99%

Atlas: Application Confidentiality in Compromised Embedded Systems

Maene

Götzfried

Müller

et al. 2019

IEEE Trans. Dependable and Secure Comput.

View full text Add to dashboard Cite

Due to the requirements of the Internet-of-Things, modern embedded systems have become increasingly complex, running different applications. In order to protect their intellectual property as well as the confidentiality of sensitive data they process, these applications have to be isolated from each other. Traditional memory protection and memory management units provide such isolation, but rely on operating system support for their configuration. However, modern operating systems tend to be vulnerable and cannot guarantee confidentiality when compromised. We present Atlas, a hardware-based security architecture, complementary to traditional memory protection mechanisms, ensuring code and data confidentiality through transparent encryption, even when the system software has been exploited. Atlas relies on its zero-software trusted computing base to protect against system-level attackers and also supports secure shared memory. We implemented Atlas based on the LEON3 softcore processor, including toolchain extensions for developers. Our FPGA-based evaluation shows minimal cycle overhead at the cost of a reduced maximum frequency.

show abstract

“…Thus, despite hardware limitations, the applicability of low-end devices may still coincide with scenarios of non-trivial complexity and impose challenges on software design. Moreover, certain use cases may involve long-lived battery operations [122,200,57,5] or integration into physically confined areas [136,48,56].…”

Section: Constraintsmentioning

confidence: 99%

Criteria for Securing Operating Systems Supporting Low-End Devices in the Internet of Things

Karim¹

View full text Add to dashboard Cite

The Internet of Things (IoT) is now comprised of tens of billions of Internet-connected devices. As the IoT continues to grow in size and complexity, need for specialized IoT operating systems (OSs) becomes increasingly important to facilitate rapid development of secure and portable applications. However, providing such support for the subset of lowend devices called for in resource-constrained environments introduces additional design challenges, particularly with respect to security.In this thesis, we propose nine criteria to collectively encapsulate several important aspects and considerations for securing OSs supporting low-end devices in the IoT. To begin, we discuss key characteristics, use cases, and OS support for low-end devices in the IoT. For context, we also select and provide a summary of two actively developed IoT OSs with academic origins, RIOT and Tock. We then present our three main contributions, each of which builds upon one another to inform and end in our proposed IoT OS security criteria.First, we review the role of foundational hardware-and software-based mechanisms relating to OS security. We discuss the need for such mechanisms and identify several relating to IoT OSs supporting low-end devices, accompanying each with a case study pertaining to a real-world example. Second, we experimentally examine the use of such mechanisms in both of our selected IoT OSs running on an ARM Cortex-M based low-end device. Finally, we combine these contributions with a literature review to derive, support, and propose nine criteria for securing OSs supporting low-end devices, we further evaluate and compare each proposed criterion against the aforementioned IoT OSs.

show abstract

An integrated architecture for future car generations

Cited by 7 publications

References 29 publications

The Real‐Time Systems Compiler: migrating event‐triggered systems to time‐triggered systems

The Real‐Time Systems Compiler: migrating event‐triggered systems to time‐triggered systems

Atlas: Application Confidentiality in Compromised Embedded Systems

Criteria for Securing Operating Systems Supporting Low-End Devices in the Internet of Things

Contact Info

Product

Resources

About