Jump to content

Draft:Software-defined Vehicles

From Wikipedia, the free encyclopedia

A software-defined vehicle (SDV) uses software to define and control various aspects of its functionality, including driving assistance systems, infotainment, and powertrain. This is in contrast to traditional vehicles, where these functions are largely controlled by hardware. SDVs allow for greater flexibility and customization, as well as the ability to update and improve functionality over time through software updates.

History

[edit]

While the term "software-defined vehicle" is relatively new, the underlying concepts have been evolving for decades. The increasing integration of electronics and software in vehicles laid the groundwork for the SDV revolution. Early examples of software-driven functionalities include electronic engine control units (ECUs), anti-lock braking systems (ABS), and electronic stability control (ESC).[1]

Implementing service-oriented architecture (SOA)[2] is a critical enabler of SDVs. SOA allows vehicle functions to be decoupled from specific hardware components and accessed as services over a network. This approach enables greater flexibility, modularity, and scalability in-vehicle software development.

Etymology

[edit]

The term "software-defined vehicle" is used to describe vehicles where software plays a central role in defining and controlling the vehicle's functionality.[3] This contrasts with traditional vehicles where hardware components largely determine the vehicle's capabilities.

The term "software-defined" is borrowed from the IT industry, where it refers to systems that can be dynamically configured and controlled through software[3]. This concept has been applied to various domains, including networking, storage, and data centers. In the automotive context, "software-defined" emphasizes the shift towards software-centric architectures and the ability to update and modify vehicle functionality through software updates.

Industry transition

[edit]

The automotive industry is rapidly embracing SDVs as the foundation for the next generation of vehicles. This transition is driven by several factors:

  • Consumer demand for advanced features: Consumers are increasingly demanding vehicles with advanced features such as connectivity, personalization, and autonomous driving capabilities. SDVs provide the platform to deliver these features and continuously improve them through software updates.[4]

This transition to SDVs requires significant changes in the automotive industry:

Software development capabilities: Automakers need to invest in software development expertise and build robust software platforms to support SDV development.[5]

References

[edit]
  1. ^ . 2023-10-01. doi:10.54499/2023.04459.bd https://doi.org/10.54499/2023.04459.bd. {{cite journal}}: Cite journal requires |journal= (help); Missing or empty |title= (help)
  2. ^ . 2023-10-01. doi:10.3030/101139749 https://doi.org/10.3030/101139749. {{cite journal}}: Cite journal requires |journal= (help); Missing or empty |title= (help)
  3. ^ a b Goswami, Partha (2024-03-06). The Software-defined Vehicle and Its Engineering Evolution: Balancing Issues and Challenges in a New Paradigm of Product Development (Report). Warrendale, PA: SAE Technical Paper.
  4. ^ . 2023-10-01. doi:10.54499/2023.04459.bd https://doi.org/10.54499/2023.04459.bd. {{cite journal}}: Cite journal requires |journal= (help); Missing or empty |title= (help)
  5. ^ Koon, John (2023-11-02). "For SDVs, Software Is The Biggest Challenge". Semiconductor Engineering. Retrieved 2025-01-23.