Abstract

The vehicle-embedded system also known as the electronic control unit (ECU) has transformed the humble motorcar, making it more efficient, environmentally friendly, and safer, but has led to a system which is highly dependent on software. As new technologies and features are included with each new vehicle model, the increased reliance on software will no doubt continue. It is an undeniable fact that all software contains bugs, errors, and potential vulnerabilities, which when discovered must be addressed in a timely manner, primarily through patching and updates, to preserve vehicle and occupant safety and integrity. However, current automotive software updating practices are ad hoc at best and often follow the same inefficient fix mechanisms associated with a physical component failure of return or recall. Increasing vehicle connectivity heralds the potential for over the air (OtA) software updates, but rigid ECU hardware design does not often facilitate or enable OtA updating. To address the associated issues regarding automotive ECU-based software updates, a new approach in how automotive software is deployed to the ECU is required. This paper presents how lightweight virtualisation technologies known as containers can promote efficient automotive ECU software updates. ECU functional software can be deployed to a container built from an associated image. Container images promote efficiency in download size and times through layer sharing, similar to ECU difference or delta flashing. Through containers, connectivity and OtA future software updates can be completed without inconveniences to the consumer or incurring expense to the manufacturer.

Highlights

  • In 1886, Karl Benz built what was considered the first modern motor vehicle: the Benz Patent-Motorwagen, the humble car has transformed, not just in looks but function

  • In 1977, General Motors released the Oldsmobile Toronado, which is regarded as the first car to include an electronic control unit (ECU) [1]; this first implementation managed the electronic spark timing of the combustion process

  • The focus of this paper is to propose and investigate how specific lightweight virtualisation known as containers can be deployed within the automotive E/E architecture to promote periodic remote Over the Air (OtA) software updates [23]

Read more

Summary

Introduction

In 1886, Karl Benz built what was considered the first modern motor vehicle: the Benz Patent-Motorwagen, the humble car has transformed, not just in looks but function. 100 ECUs can be found within the automotive E/E architecture of many modern motor vehicles providing vehicle functions from engine management to passenger comfort [3,4] These diverse functions make the modern motorcar one of the most software-intensive systems we use in our day-to-day lives [3,5,6]. Current rigid ECU hardware designs do not facilitate or promote an architecture that can benefit from an OtA software update mechanism. A container-based ECU can address many of the current software updating issues identified within this paper It can provide a scalable and updateable solution that is not dependant on many applications of individual ECU hardware systems, which is the standard practice in current automotive E/E architecture design. As more lines of code are included it raises specific issues related to an increased dependency on software

Software Bugs and Errors
Software Associated Security Threats
Ageing and Out of Date Code
Aftermarket Sales and Additional Functionality
Automotive Software Updating
Software Update Mechanism
Current Automotive Software Re-Flashing Techniques
Full Binary Re-Flashing
Container-Based Software Updating
Offline Update
Online Update
Dynamic Update
Implementation and Evaluation of Container-Based Software Updating
Individual Container Image Downloads
Findings
Conclusions
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call