...
- AASIG status report is here
Participants:
- to be inserted
Maria (Bosch), Johan (Melco), Stephen (Renesas), Piotr, Stefan (TietoEVRY), Steven (General Motors), Charnjiv (Mercedes-Benz), Wassim (BMW), Gunnar, Steve, Philippe (GENIVI)
Minutes
Status report
- Philippe delivers the status report
- slide #4
- Philippe: the light brown box on the right is the IVI unit running Android Automotive, the blank box on the left is to the external data server
- Philippe: explains the rationale for the External Data Server (EDS) PoC, currently the number of vehicle properties defined by Google is very limited as compared to the many vehicle data OEMs are considering for their connected vehicles, this External Data Server PoC intends to validate the concept of accessing the vehicle dataset as described by W3C VSS from apps using a web socket, 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 instance Some/IP
- Philippe: the other blank boxes contain the list of work items to be realized for implementing the PoC
- slide #5
- Gunnar: explains which execution platforms will be used by the PoC, the embedded targets are the ones available in the GENIVI test farm (Renesas R-Car H3 and NXP)
- slide #6
- Philippe: presents the 4 PoCs identified by the team, priorities attached to PoCs indicate only the preferences of the GENIVI team for developing the PoCs
- the priorities do not indicate whether one PoC architectural design is recommed for a production project
- Internal Data Server PoC is only a variant of the External Data Server where the VSS server is inside the Android Automotive framework
- SomeIP stack inside the Framework PoC relates to a Some/IP running in Android Automotive, we could expect software vendors to show this for instance at the Spring AMM
- Google VHAL + OEM Extensions inside PoC relates to the coexistence at VHAL level of the implementation of the Google vehicle properties and the access to the extended data set needed by OEMs
- we expect currently that the project participants will volunteer for taking over some of the work items listed for the External Data Server PoC, the ownership of work items are to be added in this wiki page (link shown on the slide)
- we expect to have a partial demo of the EDS PoC by Spring AMM
- Philippe: presents also the roadmap, the rationale for the Go to Google miletstone is to make sure we have worked out a sufficiently comprehensive implementation of the first PoC before recontacting Google
- Philippe: presents the 4 PoCs identified by the team, priorities attached to PoCs indicate only the preferences of the GENIVI team for developing the PoCs
- slide #7
- Philippe: explains the expected content of the Spring AMM technical tracks
- for the AASIG team, we expect reports and demos and also a discussion on additional topics to be investigated by the team
- for instance, we start now analysing whether there is an opportunity to launch a new project on LBS (Location Based Services) in the AASIG, the rationale is that some OEMs would like to plug their own navigation software instead of Google Maps
- the other topics that are expected to be presented at the AMM are listed in the slide, it is time to make proposals which are welcome and will be reviewed by the so-called program committee made of the PMO participants and GENIVI marketing team
- recap
- all participants are invited to volunteer for taking over the work items of the External Data Server PoC
28 January 2020 Meeting
- AASIG status report is here
...