A software defined vehicle requires the design and development of software entities(uEs) that are distributed by nature, and deployed in many different os/hw environments such as vehicle-mechatronics, vehicle-high-compute SoCs, mobile phones, infrastructure, the cloud, etc....
Each environment has their own software development languages, deployment solutions, and communication protocols making application and service development for connected vehicles challenging and often OEM/vendor specific.
The currently are no common protocols that cross automotive and cloud boundaries for messaging/RPC, existing solutions are tailored for specific use cases and each come with their own pro's and cons (ex. it works in the cloud but not for safety critical ASIL-D messages).
Finally, given the lack of connections between the embedded automotive and Internet/cloud worlds, there is no standard way to safely and securely discover, connect, and communicate with software across the various above mentioned deployments so more often than not OEMs are left with implementing proprietary communication solutions.
Eclipse uProtocol-Android provides a reference Android implementation of uProtocol, a communication protocol that connects Software Defined vehicles components, running on top of AAOS (Android Automotive OS).
In-Scope:
- Reference Android implementation of uProtocol using the uProtocol-SDK
Connecting Automotive Apps and Services, Everywhere
A software defined vehicle requires the design and development of software entities (uEs) that are distributed by nature and deployed in many different os/hw environments such as vehicle-mechatronics, vehicle-high-compute SoCs, mobile phones, infrastructure, the cloud, etc....
Every environment have their own software development languages, deployment platforms, and communication protocols making application and service development for connected vehicles very complex. Currently there are no common protocols that cross automotive and cloud boundaries as many of the existing messaging/RPC solutions come with various pro's and cons not to mention their own "baggage" (i.e. it works in the cloud but not for safety critical ASIL-D use cases and vice versa. Furthermore, given the lack of connections between the embedded automotive and Internet/cloud worlds, there is no standard way to safely discover, connect, and communicate with software between these environments so OEMs are left with implementing proprietary solutions.
The purpose of this project shall be to provide the reference Android implementation of uProtocol that runs on top of AAOS (Android Automotive OS)
The value we hope to give (and get) are:
- Collect valueable feedback and insite from the industry
- Avoid fragmentation (OEM/vendor specific solutions)
- Rally around a common vision for the software defined vehicle
- Harmonize across the automotive projects to a common vision such that we can expand the deployments and functionality supported by this underlining protocol
Release of the source code will be in September (post incubation period to allow for feedback from the community)
Add-ons for uProtocol for Android