HTML5 for Auto: Already Here or Still Arriving?

Transcription

1 HTML5 for Auto: Already Here or Still Arriving? Dr. Philipp W3C Deputy Director This project is funded by the European Union through the Seventh Framework Programme (FP7/ ) under grant agreement n HTML5Apps

2 2014: A Historic Year! It was 25 years ago

3 Why HTML5 for Auto?

4 Apps for Auto: Approaches Develop OEM-specific platforms Adopt native mobile platforms Adopt HTML5

5 Issues with Non-HTML5 Develop vehicle-specific platforms Not attractive for app developers since small market App development expensive Re-develop for each platform Special skills required for each platform Adopt native mobile platforms Controlled by single vendors App development expensive (re-develop, special skills)

6 HTML5 Benefits Bigger market - develop once Apps work cross-vehicle, OEM (needs standards) Apps work across native platforms In HTML5 runtime As hybrid App (Cordova, ) More Web developers, less costly to develop Open standard Nobody owns HTML5, no vendor lock-in Will be supported for long time Enables fresh vehicle UI Web designed for network updates

7 HTML5 Auto Projects HTML5 at OEMs: Lots going on but not in public informal survey: Please understand I can t say the names of OEMs, but we got many OEM s RFP, RFI. I hear that all of them are playing with it Publically known (conservative): General Motors Developer APIs, Mazda (with OpenCar), HTML5 Platforms: Genivi, LG, Obigo, OpenCar, QNX: HTML5 SDK QNX CAR 2, Tizen IVI,

8 Web Standards for Auto

9 W3C Leading the Web to its Full Potential Directed by Web inventor Tim Berners-Lee since 1994 Standards: HTML5, Web APIs, XML, Web Services, RDF, VoiceXML,... Consortium with ~390 members Royalty-free policy for standards

10 W3C Automotive & Web Business Group Start: February 2013 Chairs Intel OpenCar 46+ companies, 107 individuals Monthly teleconferences Face-to-Face Meetings hosted by Genivi Automotive Linux Summit Intel

11 Members

12 Vehicle API Specification Standard API across OEMs for HTML5/Javascript applications Access vehicle properties Speed Tire pressure Engine rotation speed (RPM) OEMs are free to select properties they want to expose Apps can run on in-vehicle system or connected mobile phone Target: Passenger vehicles

13 Existing Specs Considered Genivi QNX Tizen IVI Webinos AUTOSAR Main input: Which vehicle properties are available in each?

14 Basic API Architecture Vehicle Interface Get property value Set property value Subscribe to property value changes Properties can be in Zones Front/Middle/Rear/Right/Left/ Driver/Passenger All vehicle API properties are optional OEM decides

15 Vehicle API Properties Configuration and Identification: VIN, WMI, Brand, Model, doorcount, FuelType, Running Status: Acceleration, cruisecontrolstatus, vehiclespeed, Maintenance: batterystatus, Odometer, malfunctionindicator, Personalization: DriverIdentification, seatadjustment, mirrorpan/tilt, Driving Safety: airbagstatus, ABS enabled/engaged Climate: Temperature, RainSensor, WiperStatus, Vision and Parking: LaneDepartureDetection, ParkingBrake,

16 HTML5 Security Controlling access to vehicle on-board unit OEM decides which features are available App declares which APIs it will use in config file Javascript is interpreted, so no stack buffer overflows HTML5 apps run in walled-off container App crash won t bring down whole system Container has restricted access Web engine networking and GUI well-verified With Cloud hosting: Less code on vehicle - GUI only, Business logic in cloud

17 Next Steps for Auto BG May 2014: Finalize Vehicle API spec Launch new task forces - candidates Multimedia in vehicle Navigation Speech and Multi-modal Security Containerization and off-line storage managing this in a secure way Next f2f meeting: 23 May, Gothenborg, Sweden (co-located with Genivi) October 2014: create W3C Working Group to launch formal standardisation

18 Summary HTML5 is strategic for Automotive W3C automotive activity getting started Vehicle API standardization Other topics on horizon Great time to get involved!