Search Results

The emphasis on vehicle fuel economy and tailpipe emissions, coupled with a trend toward greater system functionally, has prompted automotive engineers to develop on-board control systems with increased requirements and complexity. Mainstream engine controllers regulate fuel, spark, and other subsystems using custom solutions that incorporate off-the-shelf hardware components. Although the digital processor core and the peripheral electronics may be similar, these controllers are targeted to fixed engine architectures which limit their flexibility across vehicle platforms. Moreover, additional software needs are emerging as electronics continue to permeate the ground transportation sector. Thus, automotive controllers will be required to assume increased responsibility while effectively communicating with distributed hardware modules.

Android Automotive OS (AAOS) has been gaining popularity in recent years, with several OEMs across the world already deploying it or planning to in the near future. Besides the benefit of a well-known, customizable and secure operating system for OEMs, AAOS allows third-party app developers to offer their apps on vehicles of several manufacturers at the same time. Currently, there are 55 apps for AAOS that can be categorized as media, navigation or point-of-interest apps. Specifically the latter two categories allow the third-parties to collect certain sensor data directly from the vehicle. Furthermore, the latest version of AAOS also allows the OEM to configure and collect In-Vehicle Infotainment (IVI) and vehicle data (called OEM telemetry). However, increasing connectivity and integration with the in-vehicle network comes at the expense of user privacy. Previous works have shown that vehicular sensor data often contains personally identifiable information (PII).

Recent trends in autonomy have emphasized end-to-end deep-learning-based methods that have shown a lot of promise in overcoming the requirements and limitations of feature-engineering. However, while promising, the black-box nature of deep-learning frameworks now exacerbates the need for testing with end-to-end deployments. Further, as exemplars of systems-of-systems, autonomous vehicles (AVs) engender numerous interconnected component-, subsystem and system-level interactions. The ensuing complexity creates challenges for verification and validation at the various component, subsystem- and system-levels as well as end-to-end testing. While simulation-based testing is one promising avenue, oftentimes the lack of adequate fidelity of AV and environmental modeling limits the generalizability. In contrast, full-scale AV testing presents the usual limitations of time-, space-, and cost.

This paper presents an approach for performing software in the loop testing of autonomous vehicle software developed in the Autoware framework. Autoware is an open source software for autonomous driving that includes modules such as localization, detection, prediction, planning and control [8]. Multitudes of autonomous driving frameworks exist today, each having its own pros and cons. Often, MATLAB-Simulink is used for rapid prototyping, system modeling and testing, specifically for the lower-level vehicle dynamics and powertrain control features. For the autonomous software, the Robotic Operating System (ROS) is more commonly used for integrating distributed software components so that they can easily share information through a publish and subscribe paradigm. Thorough testing and evaluation of such complex, distributed software, implemented on a physical vehicle poses significant challenges in terms of safety, time, and cost, especially when considering rare edge cases.

Over the years, the complexity of autonomous vehicle development (and concurrently the verification and validation) has grown tremendously in terms of component-, subsystem- and system-level interactions between autonomy and the human users. Simulation-based testing holds significant promise in helping to identify both problematic interactions between component-, subsystem-, and system-levels as well as overcoming delays typically introduced by the default full-scale on-road testing. Software in Loop (SiL) simulation is utilized as an intermediate step towards software deployment for autonomous vehicles (AV) to make them reliable. SiL efforts can help reduce the resources required for successful deployment by helping to validate the software for millions of road miles. A key enabler for accelerating SiL processes is the ability to use Simulation as a Service (SaaS) rather than just isolated instances of software.

Robust communications are crucial for autonomous military fleets. Ground vehicles function as mobile local area networks utilizing Controller Area Network (CAN) backbones. Fleet coordination between autonomous platforms relies on the Robot Operating System (ROS) publish/subscribe robotic middleware for effective operation. To bridge communications between the CAN and ROS network segments, the CAN2ROS bridge software supports bidirectional data flow with message mapping and node translation. Fuzzing, a software testing technique, involves injecting randomized data inputs into the target system. This method plays a pivotal role in identifying vulnerabilities. It has proven effective in discovering vulnerabilities in online systems, such as the integrated CAN/ROS system. In our study, we consider ROS implementing zero-trust access control policies, running on a Gazebo test-bed connected to a CAN bus.