Enabling easy interoperability of parts, flexibility and choice
Developing common solutions and software
Enabling access to all data we want to exchange
Controlling access to data
Enabling user privacy and data security
Facilitating business opportunities and contractual agreements
Agreeing on names, roles, responsibilities
- Addressing shared technical challenges, improved software designs, and project-related questions in the industry adoption of Android Automotive into vehicles.
Survey and compare choices MQTT-style, WAMP, RESTful/Web technology and other messaging level protocols
Deep dive: SOME/IP - where is it applicable, and where is it not?
- Discuss and reach consensus.
Industry preferred options: Say, among 10-15 choices now, find 3-5 recommended (and for which scenarios they are recommended)
Completed. Evaluating possible extension)
Challenge: Consistent distributed HMI experience across distributed and diverse multi-ECU systems.
- Top-level compositing across domains for the same physical display, with or without mixed safety levels
- Diverse operating systems and HMI technologies
- Distributed HMIs - Wayland/Waltham... other
- + Graphics transfer encoding/technology
- Combining Linux (Wayland) and Android graphics stacks.
Challenge: The complexity of debugging and running robustly automotive computing systems with today's constant connectivity, data distribution, consolidation/virtualization and cross-domain interactions.
Seeking out, evaluating, consolidating and recommending Tools and Standards that support development of virtualized or connected, distributed systems with cross-domain interactions.
User Input Distribution and
Coordination (not started)
(possibly a sub-project of Graphics Sharing & Distributed HMI Compositing)
Challenge: Multiple inputs, varying by car model, technology, etc. bound to very complex multi-modal user interactions.