JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
Name | Short Descripition | Topic | Reference |
---|---|---|---|
Usable by 3rd Party Apps | All vehicle properties must be usable by apps installed from the app store. | SYSTEM vs. VENDOR properties | https://cs.android.com/android/platform/superproject/main/+/main:hardware/interfaces/automotive/vehicle/aidl_property/android/hardware/automotive/vehicle/VehiclePropertyGroup.aidl |
Consistent cross-OEM IDs | All vehicle properties must have consistent ID regardless of the OEM. | https://cs.android.com/android/platform/superproject/main/+/main:packages/services/Car/car-lib/src/android/car/VehiclePropertyIds.java | |
Extensible outside the platform | Vehicle properties should be extendable outside the AOSP platform code. | ||
Permission per vehicle property | Each vehicle property must be protected by a specific permission to enable fine grain access. | https://cs.android.com/android/platform/superproject/main/+/main:packages/services/Car/car-lib/src/android/car/hardware/property/VehicleVendorPermission.java | |
Permission per read/write | Read and write access must have different permissions to enable read or write-only. | ||
OEM defined access | OEM must be able to define which app may get access to which properties (read/write) | https://developer.android.com/guide/topics/permissions/overview | |
Dynamic permission grants | OEM must be able to grant or revoke access per app and vehicle property over the lifetime of the vehicle | Runtime, Dangerous permissions without user interaction | |