Software Defined Vehicle
Software Defined Vehicle (SDV), or software-defined vehicle, is an automobile that implements core functions in software instead of hardware. The main features range from update capabilities to AI control on multiple levels. The SDV represents a paradigm shift in automotive engineering from mechanical engineering to cars being a platform for software products representing the majority of the value added.[1]
History
[edit]The use of microprocessors in motor vehicles comes from requirements of exhaust aftertreatment with catalytic converters and injury prevention with airbags which became commonplace in the US by 1974. In the following years the sensors and controllers were increasingly attached to bus systems, with the CAN bus taking over as standard by 1986. This enabled further integration of electronic components allowing new driver assistance systems in the 1990s.
The software functions were originally distributed across multiple components from several suppliers. The automaker Tesla started to centralize the functions coining the term "software-defined" for that in 2012. The characteristics of a software-defined vehicle were defined differently in the next years. In 2024, the European Commission started the SDVoF initiative (software-defined vehicle of the future)[2] and the Verband der Automobilindustrie (VDA) started the S-CORE project (Eclipse Safe Open Vehicle Core)[3] leading to a cross-manufacturer approach with the definition of 5 readiness levels for SDV.
The shift to software-defined vehicles correlates with the mass production of electric cars. It is triggered by electric cars having fewer mechanical parts that contribute to the value, and their large batteries supporting the energy consumption of computer technology required for self-driving vehicles, which adds a new practical value. The connection is technically not necessary, but it results from a relative shift in product development to higher investments in IT which increases its impact on corporate decisions. This includes productivity paradoxes seen earlier in other areas.
SDV Level
[edit]The readiness levels of software-defined vehicles are defined as[4]
- SDV Level 0: Mechanically Controlled Vehicle
- the majority of vehicle functions are performed mechanically; only individual components such as the engine control unit contain electronics.
- SDV Level 1: E/E Controlled Vehicle
- several ECUs (Electronic Control Units) are installed, providing E/E functions, i.e. being based on electrical and electronic connections. The used microcontrollers run specialized embedded software.
- SDV Level 2: Software Controlled Vehicle
- the components are connected to one or more control buses (CANopen) which can connect sensors and actuators at several megabits/sec. The software updates are still performed in workshops, with the exception of non-safety-critical areas such as infotainment systems.
- SDV Level 3: Partial Software Defined Vehicle
- an operating system for the car is defined that allows to integrate multiple functions on a highly integrated System on a chip (SoC) using a module concept and APIs. These software modules can be updated with bug fixes and improved features via over-the-air updates.
- SDV Level 4: Full Software Defined Vehicle
- the components are connected via a multi-gigabit/s network, enabling the decoupling of software and hardware. The processor for the software is independent from the controls and the software can be switched to a different chip. The update capability allows new functions to be installed in a vehicle that has already been sold.
- SDV Level 5: Software Defined Ecosystem
- the computing power of the electronic components allows for the use of AI control (SAE J3016 automation). The vehicle's software cano connect to additional plugged-in components and smartphones via standard protocols. The further development of the software functionality follows product cycles and versioning schemes as defined in software development processes.
From level 3 onwards, a vehicle is considered an SDV, being a software-defined vehicle.
References
[edit]- ^ Nand Kochhar (2025-08-22). "The complete guide to software-defined vehicles: transforming automotive with Siemens software". Siemens Software.
- ^ "Europäisches digitales Fahrzeug-Ökosystem". Europäische Kommission. November 2025.
- ^ Florian Treiß (2025-06-25). "Autobranche startet Bündnis für Softwareentwicklung". Electrive.
- ^ "What is an SDV (Software Defined Vehicle)? Defining SDVs beyond just vehicles". PwC - Price Waterhouse Cooper. 2024-10-03.