VEG - Requirements Meeting Eindhoven

As in many other vertical markets, the OSGi technology gets an higher adoption in the automotive industry as well.?Therefore the OSGi-Alliance is organizing automotive workshops, with key people from the OSGi-Alliance as well as from various OEMs, tier-1 suppliers and telematics service providers in order to align the standardization activities of the OSGi Vehicle Expert Group with the demands of the automotive industry.

Based on the success of the automotive workshop in Troy, Michigan, we are organizing another OSGi automotive workshop on March 22nd in Europe. Siemens VDO is so kind to host the meeting in Eindhoven, Netherlands. The exact room as well as directions will be provided later.

Moderator: Peter Kriens, Technical Director & Evangelist, OSGi-Alliance

VEG - Requirements Meeting Eindhoven Results

This page describes the results of the VEG meeting at 2007/03/22 in Eindhoven. During this meeting we discussed issues that the VEG should be working on. The following presentations were given as input:

Presentations

• Introductory presentation
• AONIX
• CTAG
• Volkswagen
• Siemens VDO
• Solid DB
• PTV

Top Requirements

Christoph Poggeman (PTV) had prepared a mind map that we extended with all the requirements. These requirements were then placed in a excel list and voted upon. All attendants had 10 votes they could distribute. This resulted in the following top 8:

1. Vehicle API - Uniform access to the static and dynamic vehicle information, read write, cross manufacturer, cross bus. A Vehicle Object model. There are currently three proposals on the table: GST, OSGi, Volkswagen (based on OSGi). Requires security and authorization.
2. Navigation API - An API for location based services. POI, positioning, routing, guidance, map handling (update/extend the map OTA), traffic information.
3. Communication Manager - Enables application to choose a communication link. Central administration point for comm. Channels. Enumerate the channels. Unify different comm. Technologies. Cheapest, fastest, only local hotspot, �, nearest roadside unit. From an appl. perspective it should simplify access to a comm. link.Should address sharing. Prioritization.
4. Universal OSGi - Allows native code to be deployed and managed as bundles, as well as enableing native code to use the service registry. Enable distributing the firmware to other components? AutoSAR link?
5. Hard/soft real time.
6. Integration with AutoSAR - How to communicate between an AutoSAR defined system and OSGi based applications. Market force. Can OSGi integrate with the AutoSAR tools?
7. Persistence - Simple embedded database or interface to a database. Persistence storage of data, maybe higher level model like hibernate, toplink, JDO, etc. Higher level than JDBC.
8. HMI - Provide an API to HMI. Bindings to different UI technologies. Abstraction for UI events/event handling. Separate logic from the UI, where is the edge thin client. Look at themes and how bundles can integrate into resident themes. Non graphic Uis.

This is list is similar to the meeting in Troy.

Actions

The top requirements have been divided in workstreams that have an owner. The owners will drive an RFP for the different areas.