From Horsepower to Processing Power: The Rise of Software-Defined Vehicles
Understanding the Software-Defined Vehicle Revolution
From Hardware to Software: The Automotive Revolution
One fateful morning, you wake up and see that your car has upgraded and acquired the ability to drive autonomously or maneuver itself out of tight parking spaces, while this scenario sounds something out of a science fiction show like Knight Rider ( I got my eyes on you, Rivian) or Black Mirror but actually is the reality today for most vehicles. In a similar story, Volvo had announced EX90, an electric version of its flagship SUV, XC90 to be launched by the end of 2024. Buyers who had pre-booked it woke up to an email that redirected to this webpage which mentions the features that the car will be missing at launch. Most of the features missing are safety system related, and infotainment based, which will be added later with an OTA (Over the Air) update. This phenomenon of adding features later is reminiscent of technology we see in our smartphones and tablets and has existed for a while. The process of heading down to the retailer or service station for updating your vehicle’s software will soon be the thing of the past as most vehicles are moving towards a Software-Defined Vehicle state. While most forums discuss whether hybrids or alternative fuel or electrics are the future of automobiles, the actual transformation in the automotive sector is the software-defined vehicle.
Image generated by Imagen.
Defining the Software-Defined Vehicle
What is Software-Defined Vehicle (SDV) one might ask. The term Software-Driven Vehicle has not one specific definition and as the technology is evolving, so is the definition of Software-Defined Vehicle.  Vehicles operate on the Electrical/Electronic (E/E) architecture, which is a synergy of software and hardware components systems where hardware components such as ECU count was higher than the software count inside the vehicle. Software-Defined Vehicles, in simple terms are any vehicle where majority of its functions, operations and features are controlled via software or the software count triumph the hardware count. Heralded as the next evolution in automobiles, software-defined vehicles are slowly changing the way we drive. As we transitioned from feature-based phones that were dominated by hardware buttons to smart phones which are mostly governed by its software, the shift with automotive technology is similar, as software slowly controls all the important aspects of the vehicle, especially with battery electric vehicles (BEVs). Although some car enthusiasts may be hesitant about software-controlled vehicles, the widespread adoption of these technologies demonstrates their growing acceptance and effectiveness as almost all cars today use software not just to control the infotainment system but also with other systems that handle the performance such as damping settings, fuelling, traction to braking. All the fundamental systems in cars ranging from basic to high performance use software to control these parameters. The issue with present vehicles is the addition of a new feature usually resulted in addition of a new ECU unit and the wiring that followed, Software-Defined Vehicle manufacturers like Tesla and Rivian have adopted an interesting approach called zonal architecture to combat that issue. In traditional domain architecture where every function has it’s separate ECU and wiring that is connected to the main control unit of the car resulting in complex and labyrinth of wiring, zonal architecture in contrast, groups smaller ECUs in different zones and communication is handled with ethernet cables instead which helps in reducing the internal wiring and subsequently the weight. Notably, Tesla Model 3’s wiring was reduced to 50% and Rivian was able to go from 17 to 7 ECUs and eliminate 1.6 miles of internal wiring all by switching to zonal architecture.
Types of architecture, image from Marvell Technology
State of SDV today
The manufacturers which are harnessing this technology on a higher level presently are Tesla and Rivian, with more manufacturers joining the club with each passing day. The brilliance of this technology was initially observed in Tesla vehicles where over the air updates added new safety features overnight while charging. In an equivalent manner, owners of Rivian R1T were welcomed with a pleasant surprise when a software update changed the suspension settings of their vehicles resulting in a much better ride and handling quality. As the demand for the features rise among consumers, legacy automakers are also joining the bandwagon, while BEVs are an easier platform to adopt this architecture due to a lower number of mechanical parts, the ICE (Internal Combustion Engine) counterparts are also gaining certain features especially in their infotainment and safety system.
Why SDV Matters
Safety plays a major factor for most car buyers today, and the implementation of safety features and its integration is a key prospect of SDV. SDV also brings in a lot of other benefits including:
Ability to add new features and functions via updates.
Telemetry data can help in optimizing driving behaviour and improve range.
3rd party apps can open up a new world within the infotainment system.
A certain amount of future proofing that is mostly limited by hardware features.
Possibility to communicate with urban infrastructure which can enhance traffic management.
Telematics allow better diagnostics and effective preventative maintenance.
Improvement in driving experience with software updates.
Improved connectivity and communication with the vehicle.
Improved safety due to higher level of encryption.
The Architecture of SDVs
SDV can be divided into four layers in a vehicle, Hardware, Embedded Core Software (OS), Instrumentation (Safety/ADAS)), Interface E-Cockpit/IVI)
Hardware
Sensors: Essential for collecting data about the vehicle's environment, including cameras, LiDAR, and radar systems. These sensors enable features like collision avoidance and lane-keeping assistance.
Computing Units: High-performance processors that manage data from various sensors and execute complex algorithms for real-time decision-making.
Connectivity Modules: Facilitate communication between the vehicle and external networks, supporting features like Vehicle-to-Everything (V2X) technology.
Embedded Core Software (OS)
Real-Time Operating Systems (RTOS): Designed for safety-critical applications, ensuring timely responses to sensor inputs, and maintaining system stability under various conditions.
Middleware: Provides essential services for communication between different software applications and hardware components, ensuring seamless integration.
Safety Protocols: Implementations of standards such as ISO 26262 that govern functional safety processes, ensuring that software behaves reliably in safety-critical situations.
Instrumentation (Safety/ADAS)
Advanced Driver Assistance Systems (ADAS): Software applications that utilize real-time data to enhance driving safety. Features include:
Automatic Emergency Braking (AEB): Engages brakes automatically to prevent collisions.
Adaptive Cruise Control: Adjusts the vehicle speed to maintain a safe distance from other vehicles.
Functional Safety Mechanisms: Systems designed to ensure that critical functions can operate safely even in the event of a malfunction. This includes fail-silent systems that revert to a safe state if a failure occurs.
Interface (E-Cockpit/IVI)
E-Cockpit Systems: Integrate various functionalities into a unified interface, providing drivers with access to navigation, vehicle status, and infotainment options through touchscreens or voice commands.
In-Vehicle Infotainment (IVI): Software platforms that enable entertainment, navigation, and connectivity features. IVI systems are designed for easy updates via over-the-air (OTA) technologies, allowing manufacturers to introduce new features without physical modifications.
Architecture of Software-Defined Vehicle. Image from Blackberry QNX
Advantages and hurdles
Vehicles are considered a necessity more than a luxury for most consumers, and the market for low end and affordable vehicles is significantly bigger than the performance and luxury counterparts. While it’s easier to build a SDV roadmap for halo models and luxury models, the same cannot be said about the lower priced offerings as SDV comes with its costs in terms of hardware, software, and design.
Similar to an app store in smartphones, SDV opens the possibility of 3rd party developers to build entertainment and personalization apps, also provide an avenue to manufacturers to offer features as a subscription as seen with Tesla’s FSD (Full Self Driving), Rivian’s Connect + and the infamous BMW heated seats subscription. While some subscription models prove valuable to customers, a lot of consumers are still skeptical about the option to subscribe for features after purchasing a vehicle for a large amount of money.
Efforts have been made to standardize the SDV software architecture with SOAFEE (Scalable Open Architecture for Embedded Edge) which is a collaborative initiative aimed at developing cloud-native software solutions for SDV. While other consortiums and alliances namely AUTOSAR *, COVESA **, Eclipse SDV intersect with SOAFFE, they maintain separate objectives and frameworks that may not align with SOAFEE’s specific cloud-native approach. Â
* AUTOSAR (AUTomotive Open System ARchitecture) is a global developmental partnership between manufacturers, OEM suppliers and software companies which focussed on standardization of the Automobile software with a focus on in vehicle network and overall system architecture
** COVESA (Connected Vehicle Systems Alliance) is a non-profit automotive industry alliance with an aim to standardize the vehicle hardware and software architecture with focus on vehicle data, services, and cloud interaction.
The Road Ahead: Future of SDV
While the SDV is still evolving, the future has countless possibilities. Some of the innovative predictions include:
Elevated levels of personalization that include identifying of driver to adjust seat settings, temperature, infotainment settings and driving profiles to even route recommendations.
SDVs can monitor the driving style, pattern and, performance and diagnose the vehicle to identify potential issues and, predict maintenance.
Vehicle to Everything (V2X) communication is set to revolutionize the way we travel, SDVs can communicate with other vehicle, traffic and urban infrastructure which could lead to smoother traffic flow and optimized routes while reducing traffic mishaps and accidents.
SDVs come with higher levels of encryption that is further strengthened with over the air security fixes and updates. These advancements will help in reducing hacking attempts and intrusions.
While most of the functions inside the vehicles are operated via touch screen, the advancement in generative AI is going to change the way we interact with vehicles and help bring more context driven interfaces.
The ability to add new features post purchase opens a new market for 3rd party applications that will help in increasing the value of the vehicle and help in future proofing it.
Plug Into Progress: Embracing the Software-Defined Vehicle Era
The future of driving is here, and it's software-defined. As we stand on the brink of this automotive revolution, it's time to ask yourself: Are you ready to be part of it? Whether you're a tech enthusiast, a car lover, or simply curious about the future of transportation, there's a place for you in this new era. Stay informed about SDV advancements, engage with manufacturers embracing this technology, and consider how these innovations might reshape your daily commute. The road ahead is exciting, your next car might just be the smartest device you own!