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.


Monthly Meeting: First Thursday of every month, 5-6pm CEST (Zoom Link) (Subscribe to Community Calendar to stay up to date)

Next Milestone:  TBD

AOSP home page: Automotive AOSP App Framework Standardization Expert Group

General Information

Slack: #Entertainment

GitHub: TBD

Leads:

Compliance statement:

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

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.

Weekly Notes

  • 06.02.2025 Bi-weekly

    • Meeting Notes
      • Decided to go to a monthly meeting, first Thursday of every month 4-5pm CET
      • Leads plan to take a step back an identify what is needed
      • Planning workshop to engage with providers
      • Some common items that have been identified with experience on Automotive AOSP are 
        • Not having a physical back button
        • No gesture control
        • Accessibility - not being able to increase font size

  • 23.01.2025 Bi-weekly

    • Meeting Notes 
      • 3SS met with biggest steaming providers and each OEM independently.  Concluded standardization of certain pieces needs to be there:
        • cybersecurity, maintenance, content discovery, UX...
      • Some major providers want to be preinstalled
      • Group leads what to set workshop with content providers to discuss requirements for the in-car entertainment
        • Also need automaker buy-in
        • workshop could be held online/virtual, at AMM in May, or at AutoTech Detroit
        • The desire is to create a playbook - requirements - no commitment upfront
        • Gather and start to align requirements from big streaming providers
          • e.g. DRM, codes, SoCs
      • Could COVESA host a reverse Geocoding service?
        • To date, COVESA has not hosted such services.  It is possible to have such a project in COVESA where such a service is developed.  But an instance would not be hosted by COVESA.

  • 14.11.2024 Bi-weekly

    • Agenda

      • In-Car Gaming
        • Present shortly the use case: in-car gaming using a smartphone as a controller
        • Brief from AirConsole:
          • What was special about the integration (Android app, access to car's interior lighting, and more)
          • What challenges were you faced?
        • Brief from BMW:
          • What was done on the AAOS level to support it
          • What could be done in the future to allow more innovative use cases like AirConsole
      • Geolocation
        • Finalize the proposal and share the next steps
    • Next steps
      • Specify API requirements for immersive gaming experience and share the use case with the VSS group
      • Understand the specification of COVESA Generic Connector for 3rd party app developers (gaming + media) to build immersive apps for cars
      • Follow up on the proposal for geolocation solution

  • 31.10.2024 Bi-weekly

    • Agenda
      • Utilize the existing AM/FM Tuner for reverse geocoding - presented by Globant
    • Next Steps
      • Create a list of basic technical requirements for all regions to be supported on AAOS requested by Content Providers (GPS antenna, connectivity, geolocation etc.)
      • Create an action plan for geocoding
    • Topics for the next session
      • tracking unique device identification with 3rd party apps (cross-apps)
      • in-car gaming use case & vehicle API integration 

  • 05.09.2024 Bi-weekly

    • Agenda

      • COVESA Entertainment Workshop @ IBC

    • Next Steps
      • Dan to follow up with cloud vendors to join AMM
      • Paul to speak with event planner to fit geolocation session with cloud vendors
      • Tomek & Richard to sync on AMM agenda

    • Presentation

    • COVESA Entertainment Workshop @ IBC

      • Want to Join Virtually?

        1. Be part of this unique event only following two steps:

          1. Please register in 3Ready+ from here.

          2. Join the workshop via Live-stream from here.

      • Date: 13.09.2024 (Friday)

      • Time:

        • CET: 2:00 pm – 4:00 pm (EU)

        • EDT: 8:00 am – 10:00 am (Detroit)

        • PDT: 5:00 am – 7:00 am (Bay area)

        • JST: 9:00 pm – 11:00 pm (Tokyo)

  • 08.08.2024 Bi-weekly

    • Agenda

      • COVESA Entertainment Workshop @ IBC → link to register

      • Topic Survey → collect topics that will be discussed during IBC with Content Providers

      • Geolocation & Geofencing

      • Insights from yacht entertainment → Globant

    • Presentation
    • Next Steps
      • COVESA at IBC
      • Globant to follow-up with Google Cloud team on geolocation and come with proposal within 2-3 weeks
        • later, we need to internally evaluate the interest from OEMs and CPs

  • 11.07.2024 Bi-weekly

    • Presentation
    • Next Steps
      • 3SS to follow up with Globant on the potential solutions for geocoding
        • geocoding is important for content providers and their legal advisors to prove that automotive platform can satisfy their licensing agreements
      • Globant to follow-up about similar challenge (geocoding) tackled by yacht industry
      • COVESA members to find out the hardware for testing

  • 13.06.2024 Kick-off

    • it was discussed that the Group should involve Content Providers
    • we should move from Monthly to bi-weekly
    • clear milestones & objectives needs to included in the Charter


Workstream Concept & Approach

Mission

Reducing access barriers for video content providers by standardizing the technical implementation in the car.​

Scope

  1. DRM
    1. Challenge: closing the gap between GAS Systems with Widevine DRM L1 vs. non-GAS​
    2. Solution: defining the minimal requirements and standardizing the certification process​
  2. GEOLOCATION
    1. Challenge: using IP for geo-blocking streaming content is not feasible when using a local IP hub
    2. Solution: standardize non-IP-based location sharing following privacy laws​
  3. CERTIFICATION
    1. Challenge: clustered and undefined process per car brand
    2. Solution:
      1. Introducing a standardized way to certify entertainment apps for automotive ​
      2. introducing readiness on non-GAS systems (streaming technologies, codecs, frame rates, …)​
  4. ANALYTICS
    1. Challenge: lack of device & app monitoring capabilities
    2. Solution:
      1. standardization of streaming analytics data and reporting formats to easily track​
      2. standardization of the quality of experience across all automotive platforms (average bitrate, error rate, …)​
  5. TECHNOLOGY
    1. Challenge: automotive hardware not seen as a relevant content distribution platform
    2. Solution:
      1. defining the minimum requirements on hardware performance and software testing & specs​
      2. defining the requirements to become attractive for global streaming providers
      3. Multi-screen behaviour & the right aspect ratio & sidepanel reusage for wider display (gradient/ambient)


Presentations


Working Model

  • Problem gathering & feedbacks from various OEMs and Content Partners
  • High-level backlog & prioritization
  • Key challenges to focus within 3 month sprint
  • Kick-off workshop / planning
  • Monthly follow up sync → might be increased when necessary
  • Sprint Review / Demo Review session
  • Joint Backlog refinement  
  • Next topic iteration


Charter



  • No labels

Privacy Policy | Cookie Policy