Over-the-Air Software Updates: Deployment Strategies

Transcription

1 Over-the-Air Software Updates: Deployment Strategies John Cain Head of Business Development Arynga, Inc. September, 2014

2 Topics Covered What is OTA/FOTA/SOTA? How does it work? How and who does it benefit? How is it being deployed today? What are the challenges? Security Cloud based structure and data transmission, configuration, complexity, repository interfaces. Connectivity Embedded challenges: Memory headroom and other challenges How will these challenges be addressed? 2

3 Over-The-Air Updating: OTA What is OTA/SOTA/FOTA? OTA: Over-The-Air SOTA: Software Over-The-Air FOTA: Firmware Over-The-Air Wireless delivery of Software and Firmware updates Utilizes multiple connectivity channels: Wi-Fi, Bluetooth, Cellular, Satellite Typically delivering from cloud based systems: Direct to the vehicle Through a proxy: Wi-Fi router, smart device, other Physical media or scan tool may be also be part of the delivery mechanism 3

4 Typical OTA Architecture Tier 1 (Update) OEM Backoffice System Data Analytics Cloud Based Management System: Release Package/Differential Tool In-Vehicle Software Client Safety & Security Chassis Body & Comfort Power Train Infotainment & Telematics

5 How OTA Works: The Process Cycle Determine baseline Monitor system and report Apply new release Vehicle Software Management Determine need for new release Create new release Deliver new release

6 How OTA Works: The Process Steps 1. OEM/Tier 1 uploads new SW/FW to cloud based management system; 1. Validation 2. Compress & Encrypt 3. Distribute to all affected vehicles 2. Wireless delivery through secure transportation protocol: SSL, HTTPS 3. In-vehicle receives updates: 1. Unpack 2. Validate 3. Distribute throughout the vehicle Firmware Software Meta Data Validate, Compress, Encrypt, Distribute 6

7 Who Benefits OEMs: Eliminates Software based Recalls, Decreases associated warranty costs Increases Customer Satisfaction and brand loyalty End Consumers: Alleviates lengthy visits to the dealership Consistent up-to-date applications and features Tier 1 & 2 Suppliers: Differentiator in support of OEMs and Consumers Example: Mentor ATP Integration with Arynga OTA Framework 7

8 Current Industry Status Vehicle ECU Software Updating Recalls: Updating at Dealership Manual (Physical Media) Update by Consumer Actual OTA Updating: A few OEMs currently practicing A few of the vehicle s ecus are being updated, typically Head Unit, Telematics Control Unit, Instrument Cluster and Powertrain Control Unit. (Currently the 2015 S-Class and the 7-Series have the highest vehicle ecu count each at 86 ecus). Most updates are typically small files 8

9 OTA Development Considerations: Security End-to-end solution is a necessity: Cloud, wireless transmission, and embedded security Wireless Transmission Security: AES or other defined encryption methodology Secure protocol: SSL, HTTPS OMA DM, OMA LW and/or other security layers Embedded (In-Vehicle) Security: Certificate Management Hypervisor, multicore, and Gateways 9

10 Comprehensive Backend Cloud based Management System: Robust: Manage SW/FW/HW Dependencies Scalable: Accommodate billions of annual transactions with zero downtime ***Evaluate/consider OTP-Erlang based cloud structures vs Java based User Portal: Tiered user roles/management: OEMs, Tier 1, Dealership, etc. Intuitive interface for managing the creation and distribution of update campaigns. Automatic verification/validation of updates: Consideration of SW/FW dependencies Verification the update is the correct for the given Manufacturer, ECU, vehicle, and/or group of vehicles 10

11 11

12 12

13 13

14 Connectivity Considerations for connectivity loss: Rollback and Resume feature for data transmission interruption (also effected by power loss) Necessity to work with, or at a minimum evaluate all connectivity mediums; Wi-Fi, Cellular, Bluetooth, Satellite, etc. While Cellular/LTE is currently predominant, Satellite connectivity has its advantages and is being developed by tier ones and oems as a transmission medium as well. 14

15 Embedded Memory Considerations for OTA Rule of thumb: Memory allocation for OTA feature will require: ~ 2Meg for the in-vehicle gateway/client (Arynga Gateway) + 2X the memory required for all s/ware or f/ware being updated. Evaluate Differential engine s: File Compression limits Patch time limits Configuration limits to achieve one or both of above parameters 15

16 What s Next Where is OTA Headed? - Some OEMs, LTE Predominant, IVI/TCUs, HS CAN is Predominant - Half or more of OEMs, LTE Predominant w/sat growing, IVI/TCUs, Ptrain and Body HS CAN is Predominant, with Ethernet growing - Most if not all OEMs, LTE and SAT, Most if not all ecus, Ethernet or FD CAN - All OEMs, LTE and SAT, All ecus, Ethernet or FD CAN 2014 to to to and Beyond 16

17 Future Deployment: The End Game Tier 1 (Update) OEM Backoffice System Data Analytics Cloud Based Management System: Release Package/Differential Tool In-Vehicle Software Client Safety & Security Chassis Body & Comfort Power Train Infotainment & Telematics 17

18 Thank you! For additional information please contact us at: 18

19