A short Introduction
What is GENIVI?
GENIVI is a non-profit industry alliance committed to driving the broad adoption of an In-Vehicle Infotainment (IVI) open-source development platform. GENIVI will accomplish this through three top-level activities:
- aligning requirements
- delivering reference implementations
- offering certification programs.
GENIVI (pronounced gen-ee-vee) is a concatenation of Geneva, the international city of peace, and the acronym IVI, for In-Vehicle Infotainment, heralding a new era of cooperation among automakers, suppliers and technology providers in the interest of streamlining the development and support of connected services to cars aligned with mobile devices
GENIVI FAQ
What is In-Vehicle Infotainment (IVI)?
IVI covers entertainment and information features and functionality available in automobiles. IVI is a rapidly changing and expanding field within the automotive industry. It covers many types of vehicle infotainment applications including music, news and multimedia, navigation and location services, telephony, internet services and more.
GENIVI FAQ
Who is part of the GENIVI Alliance?
GENIVI is open to all organizations engaged in the automotive, consumer electronics, communications, application development and entertainment industries that are interested the success of IVI systems and related product.
GENIVI FAQ
What are GENIVI's goals?
GENIVI's objective is to foster a vibrant open-source IVI community by:
- Delivering a reusable, open-source platform consisting of Linux-based core services, middleware, and open application layer interfaces.
- Engaging developers to deliver compliant applications.
- Sponsoring technical, marketing and compliance programs.
GENIVI FAQ
What characterizes an IVI open-source development platform?
The GENIVI open-source platform consists of Linux-based core services, middleware and open application layer interfaces. These are the essential but non-differentiating core elements of the overall IVI solution set. The automobile manufacturers and their suppliers will use this platform as their common underlying framework and add to it their differentiated products and services (the consumer facing applications and interfaces). GENIVI is identifying these common automotive infotainment industry requirements to establish a higher baseline from which to develop products for the common good of the ecosystem.
GENIVI FAQ
Will elements such as HMI/user interfaces and their design/styles be included in the GENIVI platform?
The GENIVI IVI platform does not address the highly competitive areas such as user interfaces and logic that defines the end-user experience. The alliance is built on the notion that user interfaces and logic distinguish products and, thus, should remain in the domain of the vendors who design and deliver the device and software.
What are the functional units of a GENIVI IVI software platform?
Expert Groups (1/2)
Automotive
Diagnostic Log and Trace, Software Management, Virtualization, CAN-based networkingConnectivity
Bluetooth, Media Playback, Audio Processing, DLNA, Smart DeviceHMI & Application Framework
HTML5, PlugIn Architecture, Pop-Up Management, Speech InterfaceLocation-Based Services
Positioning, Navigation, Traffic Provider, POI Provider
Expert Groups (2/2)
Media & Graphics
Audio Manager, Layer Manager, Graphics Back End Server, Web and Radio Tuner, Graphics APINetworking
Browser, Data Transfer, Ethernet, Inter Node CommunicationSystem Infrastructure
Lifecycle, Persistence, User Management & Personalization, IPC, Franca IDL, Common API
EG Location-Based Services
Objective
EG Location-Based Services
Contributors
| Name | Company |
Project |
|---|---|---|
| Marco Residori | XS embedded | Architecture |
| Philippe Colliot | PSA | Project Lead |
| Stephan Wiehr | Alpine | Navigation API |
| Peter Goedegebure | TomTom | Traffic Provider |
| Kang-Joon Verniers | Aisin | Traffic Provider |
| Ali Chousein | TomTom | POI Provider |
| Helmut Schmidt | Continental | Positioning |
| Torsten Mosis | Harman | Migration to Franca IDL |
EG Location-Based Service
Terms & Definitions
A Placeholder Component is a component that is defined only by a set of requirements that its specific implementation has to fulfill.
An Abstract Component is a component that is defined only by its interfaces and behavior. It does not refer to any specific implementation but it must provide a Proof of Concept (PoC).
A Proof of Concept is a software implementation that follows some specification and is intended to demonstrate the feasibility of chosen aspects of that specification. A Proof of Concept can be realized by any suitable means. There are no restrictions on the hardware platform, operating system and run-time environment. Maintaining a Proof of Concept in the Build System Repository is an option, but not a requirement.
A Specific Component is a component where a real implementation exists.
EG Location-Based Services
Architecture Overview
EG Location-Based Services
Available APIs
EG Location-Based Services
Proof of Concept
The implementation of a proof of concept (PoC) is a prerequisite for the standardization of GENIVI interfaces.
The LBS Expert Group identified Navit as the best candidate in the open source community with which to build a proof of concept.
The Navit team agreed to take over the implementation of the prototype.
Navit plugins are implementing the LBS EG interfaces. Additionally a Test HMI is provided
See Demonstration
GENIVI
By Torsten Mosis
