...

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

2025-06 ff for the moment no next meeting planned. Slots in AOSP Monday meetings. 

2025-06-12 AOSP Vehicle Data  

• Participants: appning, COVESA, BMW → just the chairs, next meetings cancelled, topic back to Monday meeting.
• Planning the next steps.

2025-06-05 AOSP Vehicle Data agenda

• Participants:
• Potentially Meeting of a Core Team to start working on the solution proposals for the permissions.
  Will be decided in AOSP meeting on Monday: Agenda proposal 2025-06-02

2025-05-29 Cancelled (Public Holiday)

2025-05-22 AOSP Vehicle Data Meeting Notes

• Participants: BMW, GM, Appning by FORVIA, Volvo Group (trucks, fleet), Elektrobit
• Synch on AMM Berlin meeting.
• Next steps: define a core team which starts working on the solution proposals for the permissions.

2025-05-15 Cancelled (AMM week).

COVESA All Member Meeting ~ May 14-15, 2025

2025-05-08 AOSP Vehicle Data Meeting notes

• Participants: BMW, GM, Spotify
• Work in Progress: Draft presentation AOSP Data for AMM Berlin
• offline: Jan Kubovy, BMW and Moritz Neukirchner, Elektrobit prepare presentation for AMM.

2025-05-01 Cancelled (Public holiday in Germany)

2025-04-24 AOSP Vehicle Data Meeting notes

• Participants: BMW, GM, Appning by FORVIA, Elektrobit, CARIAD SE, Allianz
  
  
• Who will be there and present at AOSP Data presentation slot at AMM Wednesday? https://www.eventleaf.com/e/ammberlin
  → Summary of our thoughts, of what we are addressing, requirements, of first solution ideas.
  → Sabine sends mail to all people involved to get (summary) slides on storyline and compiles the slides:
  
  • open issues, requirements on getting vehicle data - problem statement (1 slide).
  • concept1 (1-2 slides)
  • concept2 (1-2 slides)
  • concept3 (1-2 slides)

 → Finalize AMM AOSP Data Presentation on next AOSP Data Meeting, May 08, just before AMM.

as of today, the slot looks like this:
Image Added

• Next Steps:
  • different concepts presented so far: AOSP Data: Use Cases and potential Concepts - compare PoCs & ideas - pros/cons
    
  • Android Vehicle Data Requirements → mapping them to the Concepts.
  • Overview vehicle properties that are already available today, plan for future. → ask ParadoxCat next week and move forward from there.

• for information: Dev Workshop AMM is a pure Dev Workshop + breakout meetings on AOSP in the afternoon:
  AMM 20250525 Automotive AOSP App Framework Expert Group Workshop Agenda
  
  
• set next meeting date → May, 08 to finalize the presentation.
• next AOSP Monday meeting, please feel invited to attend: Agenda proposal 2025-04-28

2025-04-17 Cancelled

2025-04-03 Meeting notes

• Participants: BMW, GM, Volvo, Forvia, Bosch, Allianz, Geotab
• short AMM workshop agenda review: AMM 20250525 Automotive AOSP App Framework Expert Group Workshop Agenda.
  https://forms.gle/EMLX4AtnEB27ffZ2A. 
• short Follow-up Android Vehicle Data Requirements

2025-03-27 Meeting notes

• Participants: COVESA, Cariad, Geotab, Tietoevry, Volvo, Appning by Forvia, Bosch, Paradox Cat, BMW
• AMM news from Paul:
  The registration form is up for the AOSP workshop in Berlin (on Thursday).  Please register.  Please let me know if you see problems, have questions, suggestions, etc…  https://forms.gle/EMLX4AtnEB27ffZ2A. FYI - Registration for the Workshop is separate from registration for the AMM.
• Follow-up Android Vehicle Data Requirements – to be continued next week.

2025-03-20 Meeting notes

• Participants: COVESA, Volvo, BMW, Appning by Forvia, Tietoevry, Geotab, Elektrobit.
• Jan Kubovy, see also presentation from 2025-02-20

...

• Meeting notes: BMW: Mapper contribution to Github.
  Discussion on access control requirements in this approach vs. approach Volvo last week (OEM controlled, user controlled).
  Android 15 will see changes.
• Follow-up Android Vehicle Data Requirements - went through the table, please feel invited to contribute to this table
  which will be the basis to compare different solution ideas/proposals.
• Quicksort AMM status → please register for participation for Thursday concept workshops and developer session, agenda will be sent out shortly.

2025-03-13 Meeting notes

• Participants: COVESA, VOLVO, GM, FORVIA, FORD, Renesas, Tietoevry, Elektrobit, Geotab, Allianz, BMW
• Concept Presentation from Volvo: COVESA_Optional-SDK-Car-Data-access.pdf
  and Discussion:

  • Protection level topics still have to be solved.

  • Idea for permission groups

  • Configuration management in the backend would be needed, also to be able
    to cope with changes (car ownership, change of insurance contract etc.).

  • Availability of a PoC also depends on effects Android 15 might have.

• Follow-up AMM sessions → as for Thursday, we are planning for Workshops, everybody is invited
  to get back to us with inputs and who will be participating, Paul will be setting up a page for pre-registration.
  
  • COVESA AOSP AMM technical sessions - Prep Co-Chairs
    
  • https://www.eventleaf.com/e/ammberlin
• Please have a look at and add your thoughts to Android Vehicle Data Requirements
• fyi: announced in AOSP Monday meeting: hands-on session in Munich on Friday, March 14, details see Meeting notes 2025-03-10
• fyi: pdf from presentation Elektrobit, see 2025-02-27 Meeting notes

2025-03-06 Meeting notes

• Participants: COVESA, GM, VOLVO, CARIAD SE, Appning by FORVIA, Tietoevry, Paradox Cat, Elektrobit, Geotab, BMW
• Volvo - intro to presentation next week, first discussion:
  • it is a POC, based on system app.
  • SDK is custom, Java-SDK, Android security model will be obeyed.
  • emulator availability? → summary on emulator activities. discussion on emulator flavours.
• AOSP Data Ideas for talks & workshop on AMM, for discussion:
  COVESA AOSP AMM technical sessions - Prep Co-Chairs
• Table to compare concepts: Android Vehicle Data Requirements

2025-02-27 Meeting notes

• Participants: COVESA, FORVIA, Appning by FORVIA, GM, Elektrobit, CARIAD SE, BMW, Tietoevry, Geotab, Paradox Cat, Allianz, Valtech Mobility
• Presentation Elektrobit: 202502_EBcorbosLink_security_concept.pdf
• Discussion on how to proceed together - Paul setting up github repo for vhal.

2025-02-20 Meeting notes

• Participants: COVESA, Bosch, FORVIA, Appning by FORVIA, GM, Volvo, CARIAD SE, BMW, Allianz, Valtech Mobility, Tietoevry, Geotab, Elektrobit, Paradox Cat
  
  
• Presentation BMW, Jan Kubovy on Car API, HAL, Android VHAL.
  Car API, HAL, Android VHAL (COVESA).pdf
  
  • Discussion/Q&A:
  • Permissions as in the manifest can be granted at install time (so e.g. a user could agree before driving),
    and at run time (by OEM).
  • Each OEM can have his own config. config list can be fetched at runtime.
  • For test purposes in a PoC, assumption could be that the app store is trusted. Later we will need infrastructure for that.
  • question: is config file same as privapp allowlist that whitelist packages that can access privileged properties ?
  • the mapper is planned as contribution to COVESA.
    
• Presentation Bosch, Andreas Klein, on

...

• presentation Bosch on fleet management use case for accessing Vehicle Properties.
  

...

• 2025-02-20-COVESA_AOSP_Data_Use_Cases-v4.pdf
• Space for planning first step → can be prepared in First AOSP Data PoC

2025-02-

...

13 Meeting notes

• Participants: COVESA, FORVIA, Appning by FORVIA, GM, Volvo, BMW, Bosch, Elektrobit, Valtech Mobility, Tietoevry, Geotab, Paradox Cat
• one step back before discussing the details: our approach (Sabine, BMW):
  • What is the approach of the COVESA AOSP Data Workstream:
    • to technically enable 3rd party app developers within the COVESA Automotive Android app ecosystem, see https://covesa.global/aosp-framework/,
      to access vehicle properties, i.e. "data".
    • see also Automotive AOSP App Framework Standardization Expert Group#Charter:
      

      Vehicle Data collection

      Vehicle data collection using vehicle properties and making them available to the Android OS. Proposal: Create COVESA Vehicle Signals to AOSP translator.

  • AOSP offers standard vehicle properties as well as vendor vehicle properties, accessible for system apps with permissions.
  • What we need:
    • future 3rd party in-vehicle apps, i.e. use cases that need properties
    • solution to the permission challenge.
    • bridge the gap between VSS to Android properties as needed.
      
      
• update on presentations / potential PoCs:
  • BMW presentation availability as talked about on 2025-01-30
  • Volvo presentation availability as talked about on 2025-02-06
  • tbd: Valtech Mobility information.
  • definition of first PoC based on excel from Allianz → BMW to start with first set of properties.
• Discussion:
  • Permission topic approach:
    • learn how different PoCs / OEMs deal with it today → find a standardized way, do a workshop for a deep dive to work on it.
    • COVESA SDK for ambient lights .... one example also depending on permissions.
    • AOSP links:
      • https://developer.android.com/guide/topics/permissions/defining#grant-signature-permissions
      • https://developer.android.com/guide/topics/manifest/permission-element#plevel
    • Granularity as of today not good enough, maybe special categories of permissions needed for different use cases.
    • Each app obviously can only be signed with one certificate.
    • First: read access only.

    • https://developer.android.com/guide/topics/permissions/defining#grant-signature-permissions  granularity.

      https://developer.android.com/guide/topics/manifest/permission-element#plevel

    • System service has to
    be continued. - WIP
    • keep the list of certificates. Client app will have a SDK level jar file to use the APIs.

    • OEMs could look in the store and app could access the permission level then.

    • idea: 

      https://source.android.com/docs/core/ota/modular-system 

  • Simulation on the emulator: pre-recorded dataa for simulation, see Volvo presentation at AMM one yer back.

• • Use Cases as of today would be:
    • Valtech Mobility, Allianz, Bosch: data from VSS,
      main usecase for Allianz so far was crash detection, pay-as-you-drive (mileage) and pay-how-you-drive. Usually just pay-how-you-drive has a visualization part to teach during driving.
      
    • Forvia: SW permission system for 3^rd party apps, like:
      • speed, rpm basic stuff. Ev apps battery capacity
        
      • build a dummy reference app.

2025-02-06 Meeting Notes

• Participants: Paradox Cat, Bosch, BMW, FORVIA, Appning by FORVIA, Tietoevry, Volvo, General Motors, Elektrobit, Allianz
• Recap on meeting last week.
  
  
• Which Properties will be needed:
  • list of use cases with properties needed from Allianz and MOTER. see link from COVESA Commercial Vehicle Group
    • links shared for VSS data:
      

      https://docs.google.com/spreadsheets/d/1FMtSLhJy1REgadlnSwAqPX7r57rqdLYyw4W7ZsWyg8E/edit?gid=2020824572#gid=2020824572

      Fleet Management Data [PUBLIC]

      https://docs.google.com/spreadsheets/d/1Np9uLvwEESZ09dMcXoSvoyoyj5L_Le0k/edit?gid=1250108163#gid=1250108163
      MOTER VSS Data additions v2 - Shared publically
      
      

    • https://wiki.covesa.global/download/attachments/12124756/AOSP-VSS-Mapping-v1.7.xlsx?version=1&modificationDate=1676939208750&api=v2
      
      

    • → lists from Allianz to be checked, updated. Ted would know. →  to be followed up in Slack channel and sub-page to this page.
      
      
  • further use cases → FORVIA App Challenge shows
    • there are properties but permission not there.
    • needs the platform signature.
    • not possible for 3rd parties at the moment.
    • First step see demos below.
    • e.g. odometer: https://source.android.com/docs/automotive/vhal/system-properties#perf_odometer

...