This document discusses the challenges of over-the-air (OTA) updates for connected cars. It notes that while OTA updates are common for mobile devices, they are more complex for cars which have over 100 electronic control units (ECUs) from multiple vendors and evolving software. An OTA platform is proposed to intelligently manage updates across this heterogeneous environment through features like adaptive delta compression, a message bus, and support for various vehicle networks and file formats. The platform aims to standardize OTA updates for cars in a way that is scalable, secure, and handles the large sizes and dependencies between vehicle software components.
Mastering Mercedes Engine Care Top Tips for Rowlett, TX Residents
Over-the-air (OTA) updates and the Connected car
1. The Over-The-Air update for the
Connected Car
Pratik Desai, PhD
Lead Scientist & Architect
Movimento Inc.
@chheplo
2. 100+ year old industry
Focused on optimizing the manufacturing process
Highly regulated
90M cars a year
Automotive Industry is not
built like the Software Industry
11. @chheplo
100M CAR
100+ ECUs
Different hardware architecture
Different computation and storage capability
Ever increasing Software complexity
100+ ECU
Multiple Firmware versions
Per Firmware dependencies
Inter-module dependencies
100+ Vendor
Different software development cycle
Increasing system complexity
More independent software suppliers
Organization structure not suitable to run SW development
100M+ line of code
No central repository
Missing Vehicle knowledge Management
Missing Dependency resolver mechanism
99 Problems
12. …
Binary files for ECUs
or other firmware
updates
Maps data for
onboard navigation
Music, photos,
videos and user
generated content
Operating systems,
applications and
software packages
Other updates
• Updates are fundamentally different in terms of content and size
• Receiving units are heterogeneous in terms of available resources
One delta-compression technique cannot provide an optimal
solution across all updates
Type of updates
14. • Persistence management of user, roles, campaigns, vehicles, components
and software packages.
• Scalable, distributed infrastructure to support high availability and high
volume.
• User friendly interface, operation flow, reporting and visualization.
• Intelligent context resolver for vehicle, component and software packages.
• Multilevel security and layered authentication support.
• Extensive API support and modular platform architecture.
• Adaptive Delta Compression.
• Supports OMA DM 2.0
• Big Data analytics ready.
@chheplo
OTA Server features
15. • Agnostic to hardware and CPU
• Runs on multiple OSes through POSIX compliance
• Development Guidelines adherence – MISRA C/C++
• Provides internal/external vehicle security framework
• Supports standard OBD (J1939-73, ISO 14229, ISO15765, …) and
proprietary OEM diagnostics
• Supports Self Update and Multiple External Module Updates through
common business logic
• Supports native flash file formats
• Supports multiple vehicle networks (CAN, LIN, FlexRay, AutoIP, ...)
• Support Rollback and recovery
@chheplo
OTA Client features
16. • Adaptive Delta Compression methodology selects compression tool
according to Automaker’s requirements among,
• Parameters can be customized according to requirements and adjusted to
hardware resources on the client-side
• Standardized technologies ensures no proprietary vendor lock-in or
licensing
File size and bandwidth Time to generate and reconstruct Priority of update
Adaptive Delta Compression Methodology