Page History

...

• Update from Mercedes about Push Notifications details about 360 degree camera:
  • Request to have requirements that will support external 360 degree camera.
  • Mercedes will use their own services. Follow up needed on using COVESA interface (standardized API) - Mercedes feedback by 30th of Oct, 2023.
• Overview from Harman and Snapp about emulator capabilities and alignment  alignment on next steps:
  • Presentation from Saverio Labella/Harman:

  • Link to COVESA Licensing - https://covesa.global/sites/default/files/COVESA-Public-Policy-for-Open-Source-Licensing.pdf

  • Need to decide as a group, where the emulator will be stored and who will update/maintain the emulator - Feedback from Chairs by November 6th, 2023.
• CES 2024: GM/Mercedes/Cariad regarding panel discussion and vehicle demo:
  • GM - Decision currently on hold
  • Cariad - Internal discussion on this topic, feedback to follow
  • Mercedes - No plan at this moment
  • CES Registration details:
    • Image Added

    • Pictures from CES 2023, COVESA area - https://covesa.smugmug.com/COVESA-at-CES2023

• Maxi/BMW to discuss with Vamsi/mavi.io about how to bring both POCs together and how are next steps to define necessary feature set
  • In-vehicle camera: Are we confident enough to move forward with reference implementation, given the positive feedback from GM, BMW, Mercedes, Harman, Faurecia Aptoide

  --> Who could take over doing this (call to action for Tier 1!)

  --> Next step: Potentially extending reference implementation with 360 degree input

  • Honda: Will send you participants and time slot
  • • Mavi to follow up with BMW offline on the POC to verify if the API works.
    • Mavi to share the API with GM offline, to conduct internal POC and provide feedback.
  • Internal and External camera reference implementation support from Tier 1, next steps:
    • Faurecia Aptoide to provide feedback by 30th of Oct, 2023
  • • Harman  
      • Camera API 
        • Harman agreed with the Camera API proposal.
        • LENS_FACING_FRONT should be similar to AUTOMOTIVE_LENS_FACING and map to default camera, OEM to decide default mapping for INTERIOR_SEAT_ROW_1_LEFT|RIGHT|CENTER based on model and RHD/LHD
        • If a 3P wants to have finer controls documentation should include information on how to get the VehiclePropertyIds.INFO_DRIVER_SEAT in order to know if the car is RHD or LHD
        • 3D surround camera may need specific Camera2 value, OEMs to request it. In the meantime it could be mapped by default to EXTERIOR_OTHER
        • Evaluating Emulator Virtual device support for testing (same virtual scenes + special text overly identifying automotive camera used)
        • 3P feedback
        • LENS_FACING_FRONT, LENS_FACING_BACKOk, in the future may consider specific cameras.

        Image Added

      • Push Notification:
        • Harman agreed with UnifiedPush proposal.
        • Harman is currently evaluating Common Emulator distributor for testing
        • 3P feedback
          • Using pushing, interesting, may need to check backend change
  • Honda and Hyundai: request to know who will participate and need to have an agreed time slot (across 3 time zones):
    • Paul/COVESA and Richard/GM to follow up with Honda and Hyundai on this topic.
    Hyundai I will reach out asking for participant list and time slot
  • Harman: Feedback from which 3rd Parties they could get feedback about camera (did we cover everything?) /push notifications (e.g. Zoom/WebEx/TikTok)
    • On going discussion with 3rd party app providers, mostly positive.

  16th October 2023 - Agenda

  ...