Versions Compared

Old Version 59

changes.mady.by.user Sabine Hofschen

Saved on

compared with

New Version Current

changes.mady.by.user Sabine Hofschen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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

...

2025-05-08 tbd

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

2025-04-24 Agenda Proposal

2025-04-17 Cancelled

2025-04-03 Meeting notes

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 Working Session AMM 2025Requirements – to be continued next week.

...

  • 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 Working Session AMM 2025Requirements - 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.

...

  • 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.
  • Please have a look at and add your thoughts to Android Vehicle Data Working Session AMM 2025Requirements
  • 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

...

  • 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 Working Session AMM 2025Requirements

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.

...