Android Automotive SIG #1 - Vehicle Data APIs / Vehicle (HAL) - Start Time: 3:00PM CEST, 6:00AM PDT, 9:00AM EDT, 2:00PM WEST, 10:00PM KST, 6:30PM IST.
3:00 PM - 6:00 PMWed
The AASIG VHAL / Vehicle Data APIs project team will present a status report of the EDS proof-of-concept implementation and explain the design choices made.
The AASIG VHAL / Vehicle Data APIs project has detailed a delivery roadmap for its initial deliverables. During a successful face-to-face meeting hosted at the beginning of February by BMW in Munich, the project team identified four proofs-of-concept (coding projects) corresponding to the various software architectural options that have been debated since last November’s GENIVI Technical Summit, held in Troy, Michigan. The first proof-of-concept implementation is the External Data Server (EDS) proof-of-concept that investigates how to extend Android access to vehicle data. The rationale for this work is that the number of vehicle properties currently defined in standard Android is very limited as compared to the thousands of vehicle-related signals OEMs are considering for their connected vehicles. Although the project could propose to expand the standard vehicle property list in Android, the integration of Android into a complex electrical and connected vehicle architecture suggests a bigger picture to consider.
Standard data access methods should be applied in the entire vehicle and in cloud-connected services. This EDS proof-of-concept intends to validate the concept of a data server accessing the vehicle dataset as described by VSS (Vehicle Signal Specification standard), which is used also in W3C Automotive Group, and enabling authenticated Android apps to access the vehicle data through a web socket protocol. The actual values of the vehicle signals will be queried/updated thanks to a VSS feeder that will connect to the rest of the vehicle using, for example, Some/IP.
The AASIG VHAL / Vehicle Data APIs project team will present a status report of the EDS proof-of-concept implementation and explain the design choices made. The following next steps will be then comprehensively debated:
1. External Data Server proof-of-concept versioning w.r.t. roadmap milestones
2. Early assessment of implementation TRL (Technical Readiness Level)
3. Ensure project participants have opened, or are planning, a discussion to achieve synchronization of activities with Google's Android team
4. Other proof-of-concepts implementation