Challenge: Enable the full data-oriented connected vehicle architecture
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
Challenge: Efficient realization of the move from networked system to consolidated systems
Challenge: Too many choices, too much diversity, too much boiler-plate code, adaption layers, and incompatibility.
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?
Industry preferred options: Say, among 10-15 choices now, find 3-5 recommended (and for which scenarios they are recommended)
(→ However a small spin-off topic is still active on Android+Wayland graphics stack combination)
Challenge: Consistent distributed HMI experience across distributed and diverse multi-ECU systems.
(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.
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.
2 November, 2017.