Summary of all contributions in 2025:

List of Requirements

Android Vehicle Data Requirements,

feel free to contribute and to fill in which concept meets with which requirements.

Concept presentation Volvo, Renjith

COVESA_Optional-SDK-Car-Data-access.pdf
and Discussion:

• investigating usage of Protectionlevel respecting Android security

• 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.
  
  

• 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.

Concept Presentation Elektrobit, Patrick Loschmidt

202502_EBcorbosLink_security_concept.pdf

Concept Presentation BMW, Jan Kubovy

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 Stefan, Tietoevry 

on previous challenges and achievements, including youtube - Links: