...

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-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 MoterMOTER. 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 Stefan 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

• Renjith-VolvoCars (6. Feb. 2025, 15:34)

...

• are investigating usage of Protectionlevel respecting Android security
  • https://developer.android.com/guide/topics/manifest/permission-element#plevel
  • "knownSigner" A permission that the system grants only if the requesting application is signed with an allowed certificate.
    If the requester's certificate is listed, the system automatically grants the permission without notifying the user or asking for the user's explicit approval.
  • → short presentation to follow in one of next meetings.

• Discussion on how to proceed and what has to be addressed:
  • Granularity
granularity
• • of permissions,
    • e.g. there are different permission kinds
for→
• • • → assessment 
different  properties  to  be  done
• • • for different  properties to be done, e.g.:

      • https://developer.android.com/reference/android/car/VehiclePropertyIds#ENGINE_RPM

        https://developer.android.com/reference/android/car/VehiclePropertyIds#DOOR_POS

    • frequency/sampling.... also a matter of system load.
    • accuracy might be interesting for app level as well.
• How to proceed:
  • •  
  • idea: first PoC with subset of viable properties, like from Allianz, to be defined and shown to the group, e.g. at AMM.
  • does PoC really help? Key is to solve the permission issue. Concept proposal for permission is missing.
    

    https://source.android.com/docs/core/permissions/android-rolesso I understand we are talking about roles?

    Key is to solve the permission issue.

    We also need consent framework

  • Privacy is also an issue
  • 2nd problem is that there are properties missing.
    
    
• Who could contribute: 
  • Stefan from Allianz offers to reach out to Valtech Mobility.

  • At AMM, if we show a PoC, further companies maybe to further companies might get on board.

2025-01-30 Meeting Notes

...