Automotive Protocols and Integration in Android Development
Evaluation project on generic protocols in the automotive industry, focusing on SOA in Android development and integration of SOME/IP. Scenarios involve legacy and third-party apps accessing car signals. Developer perspectives explore interface options and extension possibilities. Points of interest include managing communication and data flow between Android and ECUs.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
Presentation Transcript
GPRO & Android Prepared by: GENIVI Generic Protocols Evaluation Project Team Presented by: Giovanni Vergine Visteam GPRO Team Lead
Generic Protocols Evaluation Project Franca/ARA::COM (CommonAPI/AUTOSAR Adaptive) interoperability Study of protocols used today in the Automotive Industry
Service Oriented Architecture in Android Current area of interest: - Research SOA paradigms used today in Android - Mapping between SOME/IP and Android SOA concepts - Can SOME/IP be one of the building blocks of SOA in Android ?
Scenarios - Legacy Android App that need to access to Car Signals (GAS, Vanilla, System apps, ) - 3rd party application that need to access to Car Signals (eg. Waze) - OEM application that need to access to Car Signals (e.g. OEM Navigation App) The three scenarios may use different APIs with different privileges
Integration of SOME/IP in Android Current areas of interest: - SOME/IP running in Android - vsomeip maintainer plan to release support for Android soon (https://github.com/GENIVI/vsomeip/issues/55) - Tooling/Frameworks around SOME/IP to be available for Android - CommonAPI, AUTOSAR Adaptive, - Definition of possible ways to communicate with SOME/IP ECUs - Define the level of integration: - Where is most useful to use SOME/IP ? (BSP level, Android Service level, App Level, ?) - Multiple levels of integration?
Developer/Integrator perspective - Developer/Integrator interested to this could be - OEM/Tier1 Android developers - 3rd party app providers Which interface to provide to developers/integrators? - Explicit and generic java/kotlin someip interface? - Higher level (CommonApi-Like) java interface? - Adapt vsomeipd to use native android messaging systems? - Both? - Other options? Is there a possibility to extend Franca to Adaptive Autosar tool also to support Android communication systems? (e.g. FIDL to AIDL)
Additional points of interest How to forbid specific communication from Android to the other ECUs? Prevent flooding/DDos from Android to other ECUs How to ensure specific data to don t be shared to Android? Authorization/Authentication mechanisms?
Q&A Thanks!
