Search Results

Back in the first two decades of automobile development, electric propulsion was a serious competitor for the internal combustion engine. Electrically-propelled vehicles, however, soon proved unable to satisfy users' increasing performance demands in terms of range, acceleration, top speed and hill-climbing, together with such factors as operating life, initial purchase price, running costs and reliability. Engineers investigating electric propulsion today face precisely the same unwelcome legacy as their predecessors, despite many and varied attempts in the meantime to improve the components of the electric vehicle's drive system (energy storage device, motors, controller). Progress in battery development, particularly in the case of the NaS system, has nevertheless enabled us at least partly to overcome the previous problems associated with electric drive systems, though it cannot be claimed that all obstacles to its commercial application have been eliminated as yet.

The idea of keeping a vehicle safe and secure throughout its whole life cycle, as well as having the opportunity to add functionality after initial delivery, is the key motivation behind automotive software updates. Today, safety or security issues that appear after vehicle delivery need to be resolved by starting a recall campaign. These campaigns require the vehicle user to visit a car repair workshop to get an update. Over The Air (OTA) software updates, being location-independent, can pave the way for higher update frequencies and more efficiency regarding customer satisfaction, resource consumption as well as safety and security. In this paper we analyze requirements for OTA software updates phrased in various standards and regulations as well as in existing development and type approval processes. Prevailing challenges for OTA updates are extracted to identify necessary activities and artifacts within the procedure.