Skip to main content
  • Log in
  • Manage Cookies
projects.eclipse.org
Download
  • Projects
  • Working Groups
  • Members
  • Community
    • Marketplace
    • Events
    • Planet Eclipse
    • Newsletter
    • Videos
    • Blogs
  • Participate
    • Report a Bug
    • Forums
    • Mailing Lists
    • Wiki
    • IRC
    • Research
  • Eclipse IDE
    • Download
    • Learn More
    • Documentation
    • Getting Started / Support
    • How to Contribute
    • IDE and Tools
    • Newcomer Forum
  • More
      • Community

      • Marketplace
      • Events
      • Planet Eclipse
      • Newsletter
      • Videos
      • Blogs
      • Participate

      • Report a Bug
      • Forums
      • Mailing Lists
      • Wiki
      • IRC
      • Research
      • Eclipse IDE

      • Download
      • Learn More
      • Documentation
      • Getting Started / Support
      • How to Contribute
      • IDE and Tools
      • Newcomer Forum
    • Search

  1. Home
  2. Projects
  3. Eclipse Automotive
  4. Eclipse uProtocol-Android
×

Status message

A creation review has been created for this proposal.

Eclipse uProtocol-Android

Basics
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Parent Project: 
Eclipse Automotive
Background: 

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.

Scope: 

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
Description: 

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)

Why Here?: 

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
Licenses: 
Apache License, Version 2.0
Project Scheduling: 

Release of the source code will be in September (post incubation period to allow for feedback from the community)

Future Work: 

Add-ons for uProtocol for Android 

People
Project Leads: 
Steven Hartley
Committers: 
Steven Hartley
Frank Ghenassia
Mikhail Petrov
Mayuresh Karandikar
Pranav Udas
Brian Eaton
Linson Ittoop
Mentors: 
Naci Dai
Interested Parties: 

This project is backed by General Motors and is part of the SDV initiative.

Source Code
Initial Contribution: 

We will release the following initially:

  • Application Layer (uP-L3) Core Platform uEs: uSubscription, uDiscovery, etc...
  • Communication Layer (uP-L2) dispatchers: uBus and uStreamer
  • Transport Layer (uP-L1): Binder (iwithin Android) & MQTT (Android to the cloud)
Source Repository Type: 
GitHub
  • Sign in to post comments.

Eclipse Foundation

  • About Us
  • Contact Us
  • Sponsor
  • Members
  • Governance
  • Code of Conduct
  • Logo and Artwork
  • Board of Directors
  • Careers

Legal

  • Privacy Policy
  • Terms of Use
  • Copyright Agent
  • Eclipse Public License
  • Legal Resources

Useful Links

  • Report a Bug
  • Documentation
  • How to Contribute
  • Mailing Lists
  • Forums
  • Marketplace

Other

  • IDE and Tools
  • Projects
  • Working Groups
  • Research@Eclipse
  • Report a Vulnerability
  • Service Status

Copyright © Eclipse Foundation. All Rights Reserved.

Back to the top