General Information

Welcome to the COVESA Automotive AOSP Data Workstream Meeting!

Weekly Meeting: Thursday, 3:00-4:00 pm CEST, zoom link: https://us06web.zoom.us/j/86051210072?pwd=fe2BinfbRCCx9zac7nbbDuXZCqzvbp.1

Slack: https://covesacommunity.slack.com/archives/C05EB6A6J5R

GitHub: https://github.com/COVESA/aosp-app-framework-standardizatiion

Leads:

Compliance statement:

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

Meeting Notes 2025

30rd January 2025 Agenda

• See Next Steps Below

23rd January 2025 Kickoff Minutes

• Participants: COVESA, Tietoevry, Allianz, Ford, FORVIA, Appning by FORVIA, WirelessCar, General Motors, Elektrobit, Renesas, Geotab, Paradox Cat, BMW
• Presentation Stefan, Tietoevry 
  on previous challenges and achievements, including youtube - Links:
  •  
  • External Data Server Framework
  • Mapping VSS to Android Properties
  • Possible Work Packages
• Questions / Tasks:
  
  • which data points are available in which granularity & frequency?
  • which data points on ADAS side are already available in VSS?
  • identify the gap between VHAL and VSS → which data from this gap would be needed (first, and then later)
    → add them to Google Properties or define as COVESA-OEM-vendor properties?
  • authentication details
  • permissions challenge:
    • fleet management signature from OEMs would have to be solved.
    • how to give permissions to an app in runtime?
  • link to capabilities group → how to deal with e.g. different set of seat properties from basic set to advanced sets depending on car capabilities.
• Next steps:
  • set up a weekly + establish a lead
  • define a problem statement
  • set up a project proposal/one pager (what we plan on doing and how we plan on doing it.  Does not need to be heavyweight)
  • find the right focus to start with
  • deal with the questions/tasks above
  • next meeting: presentation from BMW, VSS group, depending on availability.

23rd January 2025 Kickoff Agenda

Kickoff the AOSP Data Workstream with a overview/review of what has been done in the past in COVESA.  

Goals:

• Recruit and engage those that want to participate, collaborate, and contribute
• Review meaningful past efforts around AOSP and data especially as related to VSS.  
• Identify focus and propose work product/scope moving forward.
• Identify leads
• Start charter

Agenda:

• Overview
• Presentation of what meaningfully was done in the Android SIG in the past.
• Identify/Confirm Leads
• Next Steps