Today most automotive manufacturers have their vehicles connected, bringing data to the cloud. Since at least the mid 1990s with General Motors' OnStar, that information has been leaving the vehicle and sent to internet servers. Vehicles have evolved into networks of miniature control units many with embedded logic, sending and receiving signals information. This document is expected to evolve as the conversation continues. Certain topics that are already well covered by other initiatives, will be referenced and drawn from. This document will address some concerns for this larger landscape. This data model and API can be used multiple ways and is but a component in a wider telematics ecosystem. Where possible these Best Practices are generalized and not specific to this standard so these conventions can be used more broadly. W3C+GENIVI Common Vehicle Interface Initiative (CVII) activity includes a common data model and standard API that resides on vehicles. We feel many of the concerns from these sometimes opposing sides can be addressed, enabling tremendous innovation and interoperability opportunities. We hope to define practices that take into account the perspectives of different stakeholders in connected vehicle space. As such expectations are not properly set, adequate protections not provided nor are underlying computing resources appropriately regulated. Nor do these APIs define constraints beyond interactions with it directly. These API act as an enabler for interoperability but even with security and privacy considerations as part of their design, do not sufficiently address the range of concerns raised by various stakeholders. Standard and proprietary APIs exist for allowing application to reside and operate in the vehicle, accessing and potentially setting various underlying signals and calling functions. The purpose in creating an in-vehicle application best practice document would be to facilitate conversations with prospective partners and application creators, defining reasonable behavior and clearly providing enforceable parameters of what is reasonable and permitted. The intention is to take these notes and publish a formal document either within W3C or COVESA Security Expert Group. Applicable to OEM specific in-vehicle APIs. Organizing space for best practices for in-vehicle services VISS version 2, potentially the Vehicle Service Catalog (RPC interface under development with COVESA).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |