With regard to SDV (Software Defined Vehicle), not only issues related to ECU rewriting, but also issues related to automated driving, ECU architecture, security, data centers, AI, CPUs for AI (GPUs, NPUs, SoCs), high-speed memory, etc. are mentioned. This post is organized to include past posts on SDV. Please note that I am not an expert on SDV, so there may be differences from actual SDV. Please understand.
Development phase of SDV
SDVs would be divided into the following development phases.
| Development Phase | Main Functions | Outline | Development |
|---|---|---|---|
| Phase 1 OTA function installed | Over The Air(OTA) | – ECU Re-Programming function – Re-Programming Security | 1-1 OTA 1-2 Security（Standard and Proprietary standards） 1-3 Next-generation in-vehicle equipment and ECU architecture definition 1-4 MBD Agile Development Environment |
| Phase 2 Enhanced telematics functionality | User’s Application | – Applications for smartphones and PCs SNS, GAME, VOD, Payment, Generate AI, Concierge AI, Private Information Security | 2-1 User personal information security (usage history and information concealment) |
| Phase 3 Automated Driving and Ridesharing | Automated Driving | – Ridesharing – Payment – Automated Driving – Automatic parking | 3-1 Automated AI 3-2 Image-Recognition AI 3-3 CPU(GPU, NPU, SoC) for Automated AI 3-4 Memory for in-vehicle AI |
SDV Network
The SDV network configuration for Phase 3 would be as follows.
SDV Software
The in-vehicle software subject to SDV in Phase 3 would be as follows
| SDV software | In-vehicle equipment: Software | Software Developer and Provider | OS |
|---|---|---|---|
| OTA (Security included) | Telematics: OTA | OEM, Tire1 | Linux, Android, iOS |
| Integrated ECU | OEM, Tire1 | Linux, RTOS | |
| ECU | OEM, Tire1 | Each ECU RTOS | |
| ADAS ECU | OEM, Tire1 | RTOS, SoC | |
| User’s Application | Telematics: User’s Application | Application provider | Android, iOS |
| Telematics: User’s Application(Private Information Security) | OEM, Tire1 | Android, iOS | |
| AI Learning Information (Security included) | Telematics: Vehicle Control AI* | OEM, Tire1, AI Service | Linux, SoC |
| Integrated ECU | OEM, Tire1 | Linux, RTOS | |
| Image AI* | OEM, Tire1, AI Service | Linux, SoC | |
| Traffic Information and Automated service (Security included) | Telematics: Navigation | Navi Service, Automated Service | Android, iOS |
| VICS Center | Android, iOS | ||
| Telematics: Vehicle Control AI* | OEM, Tire1, AI Service | Linux, SoC |
* In-vehicle AI requires high-performance CPUs (GPUs, NPUs, SoCs) and fast memory, developed by OEMs, Tier 1 and Tier 2
Phase 1-3 Next Generation In-Vehicle Equipment and ECU Architecture Definition
I would like to consider Phase 1-3 Next Generation Onboard Equipment and ECU Architecture Definition, which is closely related to OSS-ECAL.
ECU System
Regarding the ECU (Electronic Control Unit) domain architecture, ECUs are summarized in the table below. In the future, SDV will change to a zone architecture that integrates multiple ECU functions.
| System | Unit Name | System Role |
|---|---|---|
| Powertrain system | ECU (Engine Control Unit) | Control of engine fuel injection, ignition, idle, etc. |
| ICU (Inverter Control Uint) | Control of EV/HEV motor drive (inverter/converter) | |
| TCU (Transmission Control Unit) | Control of AT/CVT/DCT gear shifting, etc. | |
| BMS (Battery Management System) | Management of EV/HEV battery level and temperature | |
| EMS (Energy Management System) | Control of energy optimization of the entire vehicle | |
| Chassis system | VCU (Vehicle Control Unit) | Integrated control of driving modes and vehicle behavior |
| EPS (Electric Power Steering System) | Steering wheel rudder angle control | |
| ESC (Electronic Stability Control) | Brake control to prevent slipping and rollover | |
| ABS (Anti-lock Braking System) | Brake control to prevent tire lock | |
| ECS (Electronic Controlled Suspension) | Suspension stiffness control | |
| AWD (All-Wheel Drive) | Control of driving force distribution for 4WD vehicles | |
| Body system | BCM (Body Control Module) | Control of lights, power windows, door locks, etc. |
| KOS (Keyless Operation System) | Keyless entry control, Engine start control | |
| HVAC (Heating, Ventilation, and Air Conditioning) | Control of temperature and air volume adjustment of air conditioners and heaters | |
| LCU (Lamp Control Unit) | Control of headlights, taillights, and indicators | |
| SCU (Seat Control Unit) | Electric seat positioning and heater control | |
| RCU (Roof Control Unit) | Sunroof and convertible roof opening/closing control | |
| ADAS system | ADAS (Advanced Driver Assistance System) | Integrated control of collision avoidance, lane keeping, ACC, etc. |
| LKA (Lane Keep Assist) | Lane departure prevention and steering correction control | |
| AEB (Autonomous Emergency Braking) | Automatic braking control for collision avoidance | |
| ACC (Adaptive Cruise Control) | Control of maintaining distance from the vehicle ahead | |
| APA (Automatic Parking Assist) | Automatic parking assist control | |
| AVM (Around View Monitor) | Combines multiple camera images to display the vehicle’s surroundings |
Main components of the ECU architecture
Whether the ECU architecture is a domain architecture or a zone architecture, there is basically no significant change in the configuration of sensors and actuators.
This section introduces the basic structure of the Sensor ECU Layer, Actuator ECU Layer, and External Memory ECU Layer.
Sensor ECU Layer
The sensor consists of an ECU Layer as shown in the figure below.
Actuator ECU Layer
The actuator consists of the ECU Layer as shown in the figure below.
External memory ECU Layer
The external memory consists of ECU Layers as shown in the figure below.
ECU Architecture and OSS-ECAL
OSS-ECAL is basically software designed to be installed in a wide variety of products (HAL and MCU).Therefore, OSS-ECAL has a high affinity with ECU Layer: any sensor or actuator supported by OSS-ECAL can be easily moved to other ECUs even if they are rearranged.OSS-ECAL is also supported by Linux-based in-vehicle devices.
From now on, OSS-ECAL, our in-vehicle counterpart, would like to contribute to the development of the automotive industry by taking the following actions.
- Expansion of Automotive Electronic Components.
- OSS-ECAL add-on development for each MCU SDK tool.
- OSS-ECAL add-on development for Eclipse SDV and other SDV tools.
- Slimulink model development for OSS-ECAL
OEMs and Tire1 are requested to contact electronic component manufacturers or electronic component trading companies for any OSS-ECALs they require.
Postscript
We will gather more information about SDV and update this post as needed. Please check back from time to time as the content may have changed.
We will also work with electronic component manufacturers to expand OSS-ECAL for in-vehicle electronic components. We look forward to your continued support.