Automotive Grade Android (AGA)

Automotive Grade Android (AGA)

Niclas Lindmark

Swedspot

Overview of Dev Zone Automotive Grade Android Vehicle ICT Arena

Collaboration is a key issue! If it fails, it might look like this...


Transforming from todays closed solutions to open solutions

Vehicle integrated & “closed”

Vehicle centric Existing

App App

App App App

Smart phones / retrofit devices

Open platform

Existing

In-vehicle platform

App

Vehicle integrated device

Open platform The future with AGA

App App App App


Automotive Grade Android - AGA

Open-innovation eco-system for in-vehicle software and connected services

Open-source

Piggy-back on a dynamic and large eco-system

Light-weight framework that stays in sync with Android

VISION CORNER STONES AGA

Where developers and system builders meet

A marketplace for developers

A standardized framework for system builders


Customer Offer for Developers

http://developer.lindholmen.se/

Developer Zone an open and shared community an open portal enabling downloads of artefacts and information

SDK software libraries and interfaces enabling infotainment application development for vehicles

Developer Guidelines a collection that eases how to write safe and automotive adapted applications

Simulation Environment tools for developers enabling test without having access to a real target environment

Reference Platform the AGA SDK is deployable on hardware


FMS Signals in AGA API

Configuration and Identification: VIN, Brand, Model, FuelType…

Running Status VehicleSpeed, Pedal position

Maintenance: batteryStatus, Odometer , malfunctionIndicator, …

Personalization DriverIdentification, seatAdjustment, mirrorPan/Tilt…

Driving Safety AirbagStatus, ABS enabled/engaged

Climate Temperature, RainSensor, WiperStatus, …

Vision and Parking LaneDepartureDetection, ParkingBrake,...


Customer Offer for System Builders

http://developer.lindholmen.se/

A framework that is maintained and further developed by a community

Compatibility with a large set of Apps developed for AGA

Well-defined interface for easy integration with hardware

Security/policy enforcement Comprises security mechanisms to ensure only safe operations are permitted

Reference implementation


OAA and AGA Android Auto SDK (OAA) AGA SDK

Audio

Messaging

Driver distraction

Hardware buttons

Vehicle signals

Policy management Navigation


Adoption of IVI-platform based on Linux

Bottom-up approach IVI builders first

Top-down approach developers first

Open innovation in vehicle

Extends Android with interfaces for automotive

Complete IVI

Genivi vs AGA

Genivi AGA


Stop


Vehicle management

Driver time management

Security/safety services

Dynamic Service Planning

Remote diagnostics

Remote SW updates

Navigation & traffic info.

Infotainment (Internet)

Messaging

Breakdown services

Vehicle/fleet operator

Driver / passengers

OEM / dealer workshops

Goods / people owner/forwarder

CO2 reporting

Goods tracking

Authorities / road operators

Finance / insurance companies


Vehicle management


…

Pay-as-you-drive solutions

Traffic, transport management

Driver security (e-call)

Transport management

Vehicle centric services

Transport and person centric services

Traffic management

Vehicle management

Many services for open innovation

Many stake holders Short tail and long tail … Many opportunities to offer customer value ! Open innovation is key to be cost-effective


Northbound interface • Read from vehicle • Write to vehicle • React on driver distraction changes

Automotive Grade Android

Southbound i/f

Northbound i/f

Applications

OEM integration

Applications Applications

Southbound interface • Integrate vehicle data • Integrate hardware buttons • Set access policies • Change driver distraction level

SDK • Build ROMs • Emulator • Simulator • Documentation

Automotive Grade Android - Architecture


3PP

Proxy

SDK

OEM

Policy Manager

Automotive API

Application

Automotive Manager

Policy Decision

Point

Signal Configuration

Driver Distraction

VIL VIL VIL VIL

Get API using my Certificate

OEM Policy

Implementation

OEM Signal

Integration

OEM Driver Distraction Implementation

Get VIL Implementations

Tube Gets Config

Package Manager

App Manager

Bro

ad

cast

Certificate, Proxy Port, ...

Tube

Hardware button

controller

VIL

OEM Button

integration

To Android

OEM Signals

Properties Configurtion

Automotive Grade Android – Technical Architecture


Developer Zone

Wiki

Continuous integration Repo


Developers Zone status Developer Zone in operation

Repository: Gitolite

Continuous Integration: Jenkins

Wiki and tracking: Redmine

SDK @ Developer Zone

Code available

HMI Guidelines @ Developer Zone

FFI SICS-project co-operation

Simulation Environment

Support for FMS signals


Summary Business Drivers The connected eco-system will grow rapidly when installed base of open innovation platforms reach critical mass Automotive Grade Android can piggy back on the existing large Eco-system Open integrated platforms will be there …but there will be many different kinds from various OEM’s initially - to enable the connected eco-system and open collaboration The app store model is well suited to manage the collaboration model between OEM’s, aftermarket suppliers and 3PP service providers, especially when a wider range of aftermarket services are required

The existing ”app store” 70/30 split model might work, but for B2B it might need to offer additional business models


The connected eco-system

Connected society

Connected dealers &

workshops

Connected

drivers

Connected OEMs &

suppliers

Connected

fleet operators

Connected people and goods

Connected

goods and people


Use Case: Truck OEM ”App store model” Description

The OEM factory fit in-vehicle units in new trucks

The OEM provide cloud portal with back-end and app-store

Customer offer

The OEM market its´ own brand as leading in-vehicle integrator and cloud-portal

Controlled access and management of vehicle data

Safe use of systems while driving

Customer specific business integration and accessories by local suppliers

Enabling safe use of third party apps and services in the in-vehicle infotainment systems

System and Services Upgradeable on aftermarket

Business driver

Additional revenue from IVU and own services

Enabling additional revenue from connectivity services at low cost

Increase business innovation and technical innovation


Use Case: After Market Connectivity Supplier Description

The AM Connectivity Supplier provide a complete customer adapted solution, integrates the in-vehicle unit towards the OEMs open interface, provide cloud portal with a back-end and an app-store and services

Customer offer

Customer specific solution

Controlled access and management of vehicle data

Safe use of systems while driving

Enabling Android apps from Google Play to be used in the in-vehicle system

Business driver

Revenue from complete solution (products and services) app-store, IVU and own services

Enabling 3PP connectivity services at low investment


Use Case: App service supplier Description

The App service supplier provide a complete customer adapted services

Customer offer

Customer adaptation of generic service

Business driver

Revenue from connectivity services


OAA and AGA The Open Automotive Alliance has presented a non-IVI solution, similar to MirrorLink and CarPlay, where you connect your Android device via USB to access Android applications. It is called Android Auto.

The IVI system can be Android Auto enabled using Automotive Grade Android

The Automotive Grade Android is an IVI solution based on Android, that extends the APIs to include access to Vehicle data and driver distraction information


GENIVI and AGA The Genivi IVI solution is based on open source software, but does not include a defined API that provides access to Vehicle data and driver distraction information

The Automotive Grade Android is an IVI solution based on Android, that extends the APIs to include access to Vehicle data and driver distraction information


Summary Our vision is to develop an open innovation global eco-system for in-vehicle software and connected services based on open source.

Developers Zone for Automotive Grade Android is launched for open source on September 4th 2014

developer.lindholmen.se

Hosted by Vehicle ICT Arena, Lindholmen Science Park

Governance of Dev Zone by Combitech AB


The governance model used by an open source project encapsulates all the hard questions about a project.

Who decides on the project roadmap? How transparent are the decision-making processes? Can anyone follow the discussions and meetings taking place in the community? Can anyone create derivates based on the project? What compliance requirements are there, and how are these enforced?

Governance determines who has influence and control over the project/platform – beyond what is legally deemed in the open source license: it is not enough to understand the open source license used by a project.

It is the governance model that determines whether or not decision making within an open source project is open, accessible, and transparent to all users or whether it is concentrated amongst a specific set of users.

Governance of Open Source


Governance overview Governance model

Access

Development

Project Roles

Decision Process

Contribution Process

Support

Derivates

Community

AGA


Governance of AGA, proposal based on the Open Governance Index (OGI) criterias

Access: developer support mechanisms, availability of latest source code, public roadmap, and transparency of decision making

Development: Decision and Contribution processes that ease the ability of developers to influence the content and direction of the project

Derivatives: the ability for developers to create and distribute derivatives of the source code

Community: a community structure that does not discriminate between developers


Governance - Access Source code is freely available to all developers, at the same time.

Source code is available under a permissive OSI-approved license: Apache 2.0

Developer support mechanisms: project mailing lists, forums, bug-tracking databases, source code repositories, developer documentation, and developer tools are available to all developers.

The project backlog is available publicly.

Transparency of decision mechanisms – project meeting minutes/discussions are publicly available such that it is possible to understand why and how decisions are made relating to the project.


Governance – Development 1(2) Transparency of contributions and acceptance process – the code contribution and acceptance process is moderated by the maintainer, with progress updates of contributions.

Transparency of contributions to the project – possibility to identify from whom source code contributions originate.

Accessibility to become a committer – all developers can potentially become committers and are accepted by the maintainer

Transparency of committers – all committers to the project can be identified.


Governance – Development 2(2) Project Roles and Responsibilities

• User, Maintainer, Contributor, Project Management Committee , Vehicle ICT Arena Board

Decision Process • Roadmap and project backlog management

Contribution Process • Use of developer zone resources

Support


Governance - Derivatives No trademarks are used to control how and where the platform is used via enforcing a compliance process prior to distribution.

This is managed by the respective member companies

Are go-to-market channels for applications derivatives constrained by the project in terms of approval, distribution, or discovery?

No


Governance - Community Structure Flat community structure, i.e. no tiered rights depending on membership status

Maintainer role elected by the Vehicle ICT Arena Board

Automotive Grade Android (AGA)

Documents

Transcript of Automotive Grade Android (AGA)