SDV level 0
Software-enabled		 SDV level 1
Connected		 SDV level 2
Updateable		 SDV level 3
Upgradeable		 SDV level 4
Software Platform		 SDV level 5
Innovation Platform

Customer Experience

Mechanical functions made possible via software

Information and control via connectivity

Vehicle maintenance via OTA updates

New functions via software upgrades

Car always feels new via cross- generation software upgrades

Full customization via ecosystem of 3rd party functions

Scope of adaptability and dynamics

  • No Updates

  • No Connectivity

  • Static software

  • Dynamic environment

  • Static functionality

  • Dynamic software

  • Static target hardware

  • Dynamic functionality

  • Singular software provider

  • Dynamic target hardware

  • Diverse software providers

Example

  • Parking assistance

  • Adaptive cruise control

  • Live traffic information

  • Mobile phone companion app

  • Navigation update

  • Security patches

  • New function in a single car line

  • New function delivered to all vehicle generations

  • New 3rd party function deployed in a multi-brand fleet

Optional Domain restriction

Example: SDV level 4 for cockpit domain

EE architecture enablers

  • Microcontroller-based ECUs

  • In-vehicle networks

  • Central connectivity unit

  • Mobile connection

  • Microprocessor-based ECUs Infotainment system with display and touch control

  • A/B memory on ECUs

  • Limited over-allocation of hardware resources

  • Zonal architectures with reduced number of ECUs

  • Reduction of hardware variants across vehicles and vehicle generations

Software architecture enablers

  • High-level operating systems

  • Internet communication

  • Layered security architecture

  • In-vehicle update verification

  • Dynamic operating systems

  • Partially updateable ECU architecture

  • Service-oriented architectures

  • Virtualization

  • Containerization

  • SDK with version and variant handling

  • Hardware-independent applications

  • Strong isolation technology within ECUs

  • In-ECU intrusion detection

  • Data-access/Device-access authorization

Development enablers

  • Convergence of internet technology and in-vehicle software

  • Automated CI/CT/CD environments

  • Virtual testing

  • Controlled deprecation of software and API versions

  • Automated security scanning and vetting process of functions

Business enablers

  • Subscription for long-term use of services

  • Maintenance contracts with data providers

  • Subscription for updates

  • Maintenance contracts with ECU suppliers

  • Aftermarket revenue generation for new functions

  • OEMs directly sourcing or developing software platform

  • Subscription for platform upgrades

  • Decoupling of vehicle and software platform business

  • Monetization possibilities for 3rd party function providers