Page History

...

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

Agenda 2025-02-13 (tbc)

• Participants:
• 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.
      
      
• summary up to today (Sabine).
• 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 → how to proceed.
    
    
• AMM revisited
  
  
• Planning topics : 
  • Use Cases 
  • Timelines
  • Teaming up with VSS / VISS / Capability teams revisited.

...