Main thread: External Data Server Proof-Of-Concept - Work Breakdown Structure
Next Meeting -
...
5 May April 5:00pm CET
...
- VSS feeder update: connecting the graphql schema
- EDS PoC implementation
- virtual meeting workshop preparation: gathering of agenda items
- AOB
Backlog
Expand Backlog
- Android Compatibility Definition Document
- Software architectural task force : Vehicle Data architecture for Android
- Comparison of how vehicle properties are managed by Android 9 and 10 (Q) - further inputs
- question to address in the group: what do participating companies intend to do with the JAPI (Java API similar to CommonAPI for Android) ? this building block is currently missing
- Signal to service translation
- Secure access control in Some/IP
...
Tuesday 21 April - 500pm CET
Participants
- Johan (Melco), Andrii (EPAM), Piotr (TietoEVRY), Stefan (TietoEVRY), Alexander (BMW), Gunnar (GENIVI), Philippe (GENIVI)
- guests: Blake Lyman, Richard Isley, Robert Goldie (Jaguar Land Rover) (JLR)
- apologies: Sachin (Mercedes Benz Research)
Agenda
- roundtable
- introduction to External Data Server proof-of-concept
- overview of architectural design options for the Vehicle Data Interface
- VSS feeder proof-of-concept demo
- graphql and nodeJS installation, graphql schema example
- virtual tech summit : AASIG VHAL workshop preparation
- AOB
Minutes
roundtable
- quick introduction of each participants for JLR guests
introduction to External Data Server proof-of-concept
- Gunnar: shows the External Data Server Proof-Of-Concept - Work Breakdown Structure and explains the architectural design approach the team is investigating with the proof-of-concept implementation
overview of architectural design options for the Vehicle Data Interface
- (introduction added offline) Philippe: the outcome of the February 4-5 F2F meeting is described in this slide deck
- the team identified 4 options for the Vehicle Data Interface design (and 4 proof-of-concepts that could be implemented for experimenting and validating the design options)
- the team has set up priorities for the proof-of-concepts implementation, the PoC priorities do not refer to which architecture should be deployed in production, they reflect rather the team preference for which PoC to start implementing first
- Gunnar shows the following slide deck Vehicle HAL Architectural Design Concepts and explains the design options
- External Data Server option corresponds to slide #13 of Vehicle HAL Architectural Design Concepts (current team focus as of today)
- Internal Data Server option is only a variant of the previous with the Data Server inside the Framework
- SomeIP stack inside the Framework option corresponds to slide #14 of Vehicle HAL Architectural Design Concepts (note there is a port of vsomeip component to Android currently going on in GENIVI github)
- Google VHAL + OEM Extensions inside option corresponds to slide #12 of Vehicle HAL Architectural Design Concepts
VSS feeder proof-of-concept demo
- Philippe: browses quickly through the slidedeck presented by Stefan two weeks ago
- Stefan: will resume this week the work suspended because of the Easter break
graphql and nodeJS installation, graphql schema example
- Alex: will finalize the upload of the graphql schema example and instructions for installing graphql and nodeJS this week after last week's Easter break
virtual tech summit : AASIG VHAL workshop preparation
- Philippe: we need to start gathering the items for the agenda of the AASIG VHAL workshop and the AASIG VHAL project report at the upcoming virtual technical summit
- Philippe: the abstract of the workshop is the following (published on the virtual tech summit registration page)
"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:
- External Data Server proof-of-concept versioning w.r.t. roadmap milestones
- Early assessment of implementation TRL (Technical Readiness Level)
- Ensure project participants have opened, or are planning, a discussion to achieve synchronization of activities with Google's Android team
- Other proof-of-concepts implementation"
- Philippe: will contact Alex offline for the preparation of the sessions
Tuesday 7 April - 500pm CET
...