GENIVI Executive Overview

GENIVI Highlights and Current Status May 22st / 11:00 | Vehicle ICT Arena Program

Dashboard image reproduced with the permission of Visteon and 3M Corporation GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 23-May-14 Copyright © GENIVI Alliance 2014 1 Agenda GENIVI Highlights and Current Status

GENIVI objectives and strategy Alwin Bakkenes, CEO Pelagicore & GENIVI Board Member

Introduction to working with GENIVI Philippe Robin, PMO GENIVI Alliance

GENIVI Technology overview Pavel Konopelko, Software Architect, Visteon & GENIVI Lead Architect

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 5/23/2014 Copyright © GENIVI Alliance 2014 2 GENIVI objectives and strategy Alwin Bakkenes, CEO Pelagicore & GENIVI Board Member

Mission • GENIVI is a non-profit industry alliance committed to driving the broad adoption of an In-Vehicle Infotainment (IVI) based on a compliance statement. • GENIVI will accomplish this by aligning requirements, delivering reference implementations, offering certification programs and fostering a vibrant open source IVI community

Purpose • Ease IVI product integration • Enable open innovation and inheritance from adjacent industries

Deliverables • Aligned IVI requirements across a broad base of OEMs • Code that “satisfies” the requirements and “demonstrates” the compliance statements • A compliance program against which commercial and FOSS offerings can be certified and ISVs can develop.

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 23-May-14 Copyright © GENIVI Alliance 2014 4 GENIVI Alliance Ecosystem Based on a community, not a specific supplier dependency

OEMs 160+ Members

First Tiers • 12 Automakers OSV, Middleware, Hardware, and Services Suppliers • 22 Tier1 Suppliers • 18 Silicon Suppliers • 127 Major Software & Service Suppliers

Silicon

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 5/23/2014 Copyright © GENIVI Alliance 2014 5 HMI - Human Machine Interface • Differentiation Automaker and • Integration Tier1 Supplier • Commercial and Proprietary Domain solutions OSV • Implementation Competition Apps Extensions Libs

• Non-differentiating features Open Source IVI Stack Alliance • Consolidated Requirements Domain • Auto Specific Middleware • Validation/Compliance Open Source Linux Kernel

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 9-Apr-14 Copyright © GENIVI Alliance 2014 6 GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 9-Apr-14 Copyright © GENIVI Alliance 2014 7 Component vs. Platform Compliance

Product-Specific Software HMI Component Applications Compliance (Works with Software Platform GENIVI™) Product- Middleware Specific Product- Kernel Specific Platform Compliance (GENIVI GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries Compliant™) 23-May-14 Copyright © GENIVI Alliance 2014 8 Benefits for OEMs and Integrators

Simplifies the vendor selection process

Ensures adherence to standard APIs

Eases integration

Results in a trusted network of suppliers

Increases the value of the GENIVI platform

Enables re-deployment of platform developers

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other 2-Apr-14 countries 10 GENIVI is a registered trademark ofCopyright the GENIVI © GENIVIAlliance Alliancein the USA 2014 and other countries 2-Apr-14 Copyright © GENIVI Alliance 2014 10 Liaison with Automotive Grade Linux

• Joint webinars organized since beginning 2014 – Licence compliance (19 Feb) (BearingPoint) – Media manager (19 Mar) (JLR) • Kickoff of joint work on requirements & use cases • Media manager proof-of-concept – Open source project funded by GENIVI (media indexer, media playback, media browser) – Kickoff expected in early April, first results scheduled for Spring GENIVI AMM, first version available for ALS- Tokyo on 1-2 July, full version for September • Upcoming events in Japan: papers submitted – (ALS) ADIT: IVI layer management – (ALS) PSA: navigation applications based on GENIVI lbs apis – (ALS) Pelagicore: genivi stack overview – (ALS) JLR: media manager – GENIVI / AGL collaboration – (JSAE) Denso: driver workload assessor

• BMW has launched it’s first serial product in 2013, it is now being deployed on several car- lines. • Open Source Components do not always fulfill performance requirements yet, but it will be improved along developments. • GENIVI gathers the lessons learned from on- going serial developments to improve Open Source SW components, either upstream in Open Source Community or in GENIVI Open Source Projects

• Some Tier1 suppliers (i.e Bosch,…) base their offer on a Linux GENIVI platform. OEMs buying a black box might not care. GENIVI lessons learned process also uses these Tier1 developments.

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 2-Apr-14 Copyright © GENIVI Alliance 2014 12 Introduction to working with GENIVI Philippe Robin, PMO GENIVI Alliance

Alignment Development

Board - Subcommittee

Program Management Office Open Open Source Source

Project Project Expert Expert eam T

Group Group Open Source Open Source Project Project Expert Expert Open Source Open Source rchitecture Group Group Project Project A

Expert Expert Open Source Open Source ystem

S Group Group Project Project

Baseline Integration Team License Review Team DDevelopmentevelopment B Baselinesaselines

GENIVI System Architecture Team Expert Aligned Requirements Selected Groups Software Components

OSS Code Assigned Priority & Projects Specificity

Baseline Members Integration Team GENIVI Compliant Products Baselines Compliance Statement GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 2-Apr-14 Copyright © GENIVI Alliance 2014 15 GENIVI Open Source Projects

• http://projects.genivi.org • http://git.projects.genivi.org/

• GENIVI employs an "upstream first" model and actively adopts and/or adapts existing components residing in the FOSS community to meet the defined requirements for its IVI software platform. • In some cases, however, software to meet defined requirements does not exist in any upstream project. • In those cases, GENIVI hosts projects that facilitate the development of required functionality in an open and collaborative manner, consistent with the best practices of other FOSS projects.

100+ bugzilla issues (features, bugs, etc.) 75+ code > 500 KLOC contributors

20+ git source code repositories First projects launched end 15 mailing 2012 lists

Ex : German newspaper « Elektronik Automotive » teaching how to start with GENIVI.

• Draft W3C specification for vehicle data web APIs released at GENIVI Spring AMM • New topics for standardization – Navigation web APIs – Radio web APIs – Speech web APIs • genivi@w3C team – objective: coordination of the contributions from GENIVI W3C

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 2-Apr-14 Copyright © GENIVI Alliance 2014 20 GENIVI Technology overview Pavel Konopelko, Software Architect, Visteon & GENIVI Lead Architect

• Technical view on GENIVI mission • GENIVI compliance programs • Examples of GENIVI software projects

A proper technology needs to address at least two aspects:

1. Solving the right problem – Understand and control the system scope and design constraints— GENIVI Software Platform is a part of a bigger system 2. Solving the problem right – Organize the available development resources in a way that is efficient and compatible with open-sources development practices

Vehicle

Electronic Control Unit

System on Chip

Software Platform

Software Component

• Yocto meta-ivi layer • www.yoctoproject.org Baselines • Baserock morphology • www.baserock.org

• Platform Compliance Specification Compliance Program • Component requirements and specifications • UML model

• 17 public projects addressing IVI functionality Software Projects and tools • projects.genivi.org

System Architecture Team CE Connectivity EG

HMI-Application Korea REG Framework EG

Compliance Specification

System Location-Based Infrastructure Services EG EG

Networking EG Baseline Integration Team

Vehicle Requirements All EGs All EGs Acceptance Test and Use Cases and SAT and BIT Software Platform System Test Requirements

Component Architecture Integration Test Design

Component Component Specification (Black Box) Test

Component Unit (White Box) Design Test

Individual Implementation EG

• Technical view on GENIVI mission • GENIVI compliance programs • Examples of GENIVI software projects

Product-Specific Software

HMI

Works with GENIVI™ Applications (Component Compliance) Software Platform

Product- Middleware Specific GENIVI Compliant™ (Platform Product- Kernel Compliance) Specific

• Compliance Specification is a list of components – 3 component types: Placeholder, Abstract, Specific: – 2 component priorities: P1 (mandatory), P2 (desired): • Compliant implementation must include all P1 components

• Placeholder Component Component that is defined only by a set of requirements that its specific implementation has to fulfill. The requirements are typically specified as informal textual statements about the component responsibilities and the services it provides. • Abstract Component Component that is defined by its provided and required interfaces as well as its behavior, but does not refer to any specific implementation. Interfaces are defined by their operation signatures. Behavior can be defined in any convenient way. • Specific Component Component that is ultimately defined by its implementation available in form of the source code.

Specific Component

Source Abstract Code Component • Produces Placeholder Component component Component implementation • Produces Vehicle Software Need Component Level Platform Specification (including the • Based on • Produces • Produces API and feature or vehicle-level component behavior) technology to actors, use architecture be supported cases and and software • Produces a requirements platform level scope requirements description GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 5/23/2014 Copyright © GENIVI Alliance 2013 33 Component Types by Release

90 80 70 30 32 60 26 29 50 30 30 40 22 27 28 30 5 12 16 20 27 10 25 24 25 24 24 0 1.0 2.0 3.0 4.0 5.0 6.0 Specific Abstract Placeholder

• Technical view on GENIVI mission • GENIVI compliance programs • Examples of GENIVI software projects

Application Code

generated code IPC CommonAPI C++ CommonAPI C++ runtime library

middleware agnostic - remains the same

generated code IPC MiddlewareCommonAPI X C++ CommonAPIMiddleware C++ XD -Bus D-Busruntime runtime library library

middleware dependent

D-Bus communication infrastructure Middleware X communication infrastructure

Package Product Component Platform Component Node State Node State Node Startup Machine Manager Controller

Supply <> Manager <> <> <> systemd Supply Node State Boot <> Management Management Management

cgroup Thermal Power Resource <> service Management Management Management Thermal <> Manager <>

<> <> Node Health Power Event Node Monitor Collector Resource Mgr GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries 5/23/2014 Copyright © GENIVI Alliance 2014 38 Audio Management

Legacy ILM Application ivi_client ivi_client ILM Client API Application Application

Dispatch input events Manage and update surfaces

Wayland ivi_controller Compositor Manage layers Weston + and surfaces ivi-shell

Linux kernel

• IPC Common API C++ • Audio Manager – http://projects.genivi.org/com – http://projects.genivi.org/audio monapi -manager • ECU Lifecycle • IVI Layer Management – http://projects.genivi.org/node- – http://projects.genivi.org/ivi- startup-controller layer-management – http://projects.genivi.org/node- – http://wayland.freedesktop.org state-manager – Coming soon: Node Health • All GENIVI software projects Monitor – http://projects.genivi.org

Questions?