Project Title:Open Vehicular Secure Platform

Project acronym: OVERSEE

Project title:Open Vehicular Secure Platform

Project ID:248333

Call ID: FP7-ICT-2009-4

Programme:7th Framework Programme for Research and Technological Development

Objective:ICT-2009.6.1: ICT for Safety and Energy Efficiency in Mobility

Contract type:Collaborative project

Duration:01-01-2010 to 30-06-2012 (30 months)

Deliverable D6.2:

Prototype Demonstration

D6.2: Prototype Demonstration

Abstract

This document outlines the scenario for the final project demonstration event. Therefore, the prototype platforms that shall be presented and in particular the showcases are described.

It contains a comprehensive description of the different demonstration elements. Those are, the in-vehicle demonstrator, the model-car testbed and the platform demonstration setup. All of those were carefully selected during the project progress; to show the most important OVERSEE key features based on possible OVERSEE applications.

The final version of this document will also include a report on the demonstration event.

Abstract

Contents

List of Figures

List of Tables

List of Abbreviations

Document History

1Introduction

1.1Outline

1.2General Procedure

1.2.1Proof-of-Concept Use Cases and Prototype Platforms

1.2.2Agenda and Organisation

1.3Event Location and Dates

2Demonstration of Near-term Use Cases

2.1Prototype Setup

2.2eCall Showcase

2.2.1Use Case Description

2.2.2Demonstration Procedure

2.3Approaching Emergency Vehicle Warning Showcase

2.3.1Use Case Description

2.3.2Demonstration Procedure

3Demonstration of Long-term Use Cases on Model Cars

3.1Prototype Setup

3.2Active Brake Showcase

3.2.1Use Case Description

3.2.2Demonstration Procedure

3.3Platooning Showcase

3.3.1Use Case Description

3.3.2Demonstration Procedure

4Demonstration of OVERSEE Platform Features

4.1Prototype Setup

4.2Infotainment Showcase

4.2.1Use Case Description

4.2.2Demonstration Procedure

4.3Isolation Showcase

4.3.1Use Case Description

4.3.2Demonstration Procedure

4.4Real-time OSEK Showcase

4.4.1Use Case “Direction Indicators”

4.4.2Demonstration Procedure

5Report on the Event

References

List of Figures

Figure 1: The model car prototype

Figure 2: Photography of the model car demo table

Figure 3: Software Architecture for media player and flash drive access use case

Figure 4: Isolation showcase architecture

Figure 5: Architecture and configuration of the real-time platform demonstration

Figure 6: Architecture of OSEK demo use case

List of Tables

Table 1: Overview of demonstration highlights

Table 2: Preliminary time schedule

List of Abbreviations

ALSAAdvanced Linux Sound Architecture

CANController–area Network

eCallEmergency Call

GNUGNU's not UNIX

GPIOGeneral Purpose Input/Output

GPSGlobal Positioning System

HMIHuman Machine Interface

HWHardware

I/OInput Output

IPInternet Protocol

IRInfrared

ITSIntelligent Transportation System

JREJava Runtime Environment

LEDLight-emitting diode

MILSMultiple Independent Levels of Security and Safety

NICNetwork Interface Card

OSOperating System

OSEKOffene Systeme und deren Schnittstellen für die Elektronik im Kraftfahrzeug

OVERSEEOpen Vehicular Secure Platform

PoCProof of Concept

SLAPSLAP is a lightweight asynchronous Protocol

SMSShort Message Service

UDPUser Datagram Protocol

USBUniversal Serial Bus

V2VVehicle-to-Vehicle

V2XVehicle-to-X

Document History

Version / Date / Changes
0.1 Draft / 21-10-2011 / Initial version based on contributions to the Integration Plan (RG)
0.2 Draft / 01-11-2011 / Added introductive and general parts, improved demo description (RG)
0.3 Draft / 24-01-2012 / Improved outline and revised complete document (RG)
0.4 Draft / 25-01-2012 / Internal review and updates (FF)
0.5 Draft / 01-02-2012 / Added contributions from UniSiegen (JH) , TUB (JZ), and improvements (RG)
0.6 Draft / 06-02-2012 / Added contribution from OpenTech (NM) and refined contribution from TUB (JZ)
0.7 Draft / 09-02-2012 / Volkswagen contributed chapter 2 (MF)
0.8 Draft / 13-02-2012 / Added “part 2” of OpenTech (NM), improved the document, Abbr., Ref, etc. (RG)
0.9 Draft / 13-02-2012 / Added revision of UPV (JS), minor improvements (RG)

D6.2: Prototype Demonstration

1 Introduction

In this document, the plan for the OVERSEE final demonstration event is outlined. Each presented use case and its relation to OVERSEE is briefly introduced. Additionally, the demonstration procedure including all organizational and technical issues is described in detail.

The audience of this document is on the one hand the OVERSEE Consortium with the intention to synchronize and harmonize our demonstration ideas and setups. On the other hand, it is primarily directed to the OVERSEE Advisory Board and the project reviewers, to give them a deeper insight to our demonstration plans. Our main goal for writing this document is to get feedback and advices to improve the final demonstration.

1.1 Outline

The general procedure, including the scenario for the project presentation is described in the introduction. A brief description of the various prototype platforms is given.

Chapter 2 contains the description of the in-vehicle demonstration setup.

Chapter 3 contains the description of the model-car testbed setup.

Chapter 4 contains the description of the platform feature setup.

Finally, Chapter 5 contains a report on the demonstration event.

1.2 General Procedure

1.2.1 Proof-of-Concept Use Cases and Prototype Platforms

The demonstration includes three classes of uses cases, which are presented on different prototype platforms and emphasize particular aspects of the OVERSEE platform. In the following, all prototype platforms are briefly described. Table 1 shows a complete overview of all demonstration use cases and their assigned prototype platforms.

Near-term ITS use cases demonstrated in real cars. Volkswagen will provide a real car that is equipped with an OVERSEE platform and an additional car that is equipped with an OVERSEE-compatible communication stack.

Long-term ITS use cases that cannot safely be demonstrated on real cars are shown on the model car platform. The model car setting will provide a 1:18 scaled down version of real cars, where the physical properties are appropriately modelled to show reactions of the vehicle based on input from the OVERSEE platform. In particular, communication based safety applications or autonomous driving applications will be of interest in this setting.

Platform-related use cases that show the particular aspects of the OVERSEE platform are demonstrated on the bare (stand-alone) platform.

Table 1 gives a complete overview of use case types, demonstration showcases and their assigned prototype platforms. The chapters 2, 0, and 4 introduce the showcases and prototype platforms in detail. Even more detailed descriptions (from a technical perspective) are found in the Deliverable D5.1 [1] and D5.2 [2] for the use cases and D6.1 [3] for the prototype platforms.

Use-case type / Prototype platform / Showcase
Near-tem / Real car prototype / eCall
Approaching Emergency Vehicle Warning
Long-term / Model car prototype / Active Brake
Platooning
Platform-related / Stand-alone prototypes / Infotainment (USB media access)
Isolation
Real-time (OSEK)

Table 1: Overview of demonstration highlights

1.2.2 Agenda and Organisation

The use cases of each class are presented together, so that the demonstration event will consist of three parts:

The in-car demonstration, which will take place outside.
The long-term ITS use case demonstration, which is presented with model cars at a suitable location.
The platform-related use case demonstration, which is shown on stand-alone platforms and includes three separate setups.

Since some of the demonstrations are restricted in the number of spectators, all use cases will be shown in parallel to small groups. After each presentation, the groups should rotate to watch the next demo. Table 2 lists a preliminary time schedule.

1.3 Event Location and Dates

The final demonstration event will be located on the premises of Volkswagen at Wolfsburg. The outdoor demonstration of the in-car use cases will take place on the MobileLifeCampus.

Originally, the final demonstration was scheduled for June 2012, but due to the (pending) project extension, it will most probable take place either in the last week of September or in the first week of October 2012. It will be a one-day event.

Time / Agenda item / Presenter/Responsible
9:00 / Registration and coffee / Volkswagen
10:00 / Introduction and Welcome / escrypt
10:30 / Demonstration slot 1
(all demos in parallel) / Volkswagen (real cars)
TUB, FOKUS (model cars)
UPV, UniSiegen, OpenTech (platform)
12:00 / Lunch break
13:00 / Demonstration slot 2
(all demos in parallel) / Volkswagen (real cars)
TUB, FOKUS (model cars)
UPV, UniSiegen, OpenTech (platform)
14:30 / Coffee break
15:00 / Demonstration slot 3
(all demos in parallel) / Volkswagen (real cars)
TUB, FOKUS (model cars)
UPV, UniSiegen, OpenTech (platform)
16:30 / Conclusion and discussion / escrypt

Table 2: Preliminary time schedule

2 Demonstration of Near-term Use Cases

2.1 Prototype Setup

The OVERSEE platform that is developed within the project will be integrated in a research vehicle to demonstrate near-term use cases, in particular eCall and Emergency Vehicle Warning.

To demonstrate these use cases within realistic driving scenarios the research vehicle is extended by several components that care about safe vehicle data access, external communication capabilities and human machine interfaces.

Safe vehicle data access is ensured through an additional physical gateway that only forwards use case relevant CAN messages to the OVERSEE platform. Any access to this domain does not influence the original vehicle systems.

The vehicle antenna is extended by 802.11p capabilities and in combination with a dedicated communication hardware the OVERSEE platform gets access to cellular and ad-hoc networks.

The human machine interfaces of the research vehicle, in particular the display of the instrument cluster and the display and controls of the radio navigation system, are extended by additional hardware to utilize them for the OVERSEE platform.

[Image TBD]

2.2 eCall Showcase

2.2.1 Use Case Description

The use case eCall running in one isolated domain of the OVERSEE platform generates a driver triggered emergency call. All information according to European Standard EN 15722 [5] are transmitted via SMS and represented on the OVERSEE’s human machine interface. The eCall data are received by a mobile device that symbolises the emergency operations centre. To lay emphasise on this prototypical implementation, eCall is triggered by the driver through a button within the showcase.

The eCall is triggered right after a third party application, running in a different domain of the OVERSEE platform, is crashed deliberately. This demonstrates that the OVERSEE platform has the capability to isolate highly reliable and highly available functions.

[Image TBD]

2.2.2 Demonstration Procedure

This use case can be demonstrated either in driving or in standing vehicle conditions. The research vehicle offers space for three additional passengers. One demonstration round will take about ten minutes.

The ignition and engine of the car is turned on
A third party application of the OVERSEE platform is started through the OVERSEE’s human machine interface
The third party application is crashed remotely by one passenger
The eCall is triggered through the graphical user interface of the eCall application visualized on the display of the radio navigation system
The eCall data is sent and visualized on the same display
The eCall data is received by the mobile device
Meanwhile, the partition of the OVERSEE platform that holds the third party application and the third party application itself is restarted

[Image TBD]

2.3 Approaching Emergency Vehicle Warning Showcase

2.3.1 Use Case Description

The use case Emergency Vehicle Warning running in one isolated domain of the OVERSEE platform generates a warning within the instrument cluster of the research vehicle when an emergency vehicle approaches. This warning includes the course and the distance of the approaching emergency vehicle.

Within the showcase the emergency vehicle approaches right after a third party application, running in a different domain of the OVERSEE platform, is crashed deliberately. This is nearly the same scenario described in 2.2 and lay emphasis on OVERSEE’s capabilities to isolate highly reliable and highly available functions.

[Image TBD]

2.3.2 Demonstration Procedure

The ignition and engine of the car is turned on
A third party application of the OVERSEE platform is started through the OVERSEE’s human machine interface
The third party application is crashed remotely by one passenger
The emergency vehicle starts heading toward the research vehicle and/or vice versa
The warning for an approaching emergency vehicle is visualized on the display of the instrument cluster
Meanwhile, the partition of the OVERSEE platform that holds the third party application and the third party application itself is restarted

[Image TBD]

3 Demonstration of Long-term Use Cases on Model Cars

The model car demonstration involves the long-term use cases, i.e., Active Brake and Platooning. These use cases will be presented together in a joined model car demonstration. Active Brake will then affect the whole platoon (all cars will stop, if the platoon leader does).

3.1 Prototype Setup

D6.2: Prototype Demonstration

The model car setting will provide a scaled down version of real cars, where the physical properties are appropriately modelled to show reactions of the vehicle based on input from the OVERSEE platform. In particular, communication based safety applications or cooperative automated driving applications will be of interest in this particular setting. The model car prototype platform is designated to present long-term use cases, which could not be easily or safely shown in real vehicles.

Figure 1: The model car prototype

D6.2: Prototype Demonstration

The model car demonstration requires a specific setup. The usual operating place of the model cars is indoors with the result that conventional GPS-based positioning systems are unsuitable. Also, the reduced form factor (1:18) requires a substantially higher precision compared to real-sized cars. As a solution, an indoor navigation system is utilized. It consists of a camera mounted on the ceiling above the testing area and markers on top of the model cars.

The demonstration will be shown on two or more model cars. All of them can be controlled remotely – either manually or following a predefined trace. Additionally, they have the option to drive autonomously to certain degree, depending on use- and test-case.

Figure 2: Photography of the model car demo table

3.2 Active Brake Showcase

3.2.1 Use Case Description

The use case Active Brake exploits V2V communications to slow down vehicles automatically in dangerous situations. It demonstrates how V2X messages may lead the vehicle to a safety reaction. Based on these messages and additional sensor values (e.g., distance sensors or radar), drivers are warned and in case of emergency their cars are actively braked to avoid a crash.

Each vehicle reacts on its own on obstacles detected by a built-in sensor. Whenever an obstacle is recognized, the vehicle stops automatically in a safe distance and broadcasts warning messages via the V2X network to other vehicles in the area. Model cars receiving the warning message indicate the reception through red lighting. Their velocity is reduced distinctly in the region of the obstacle.

3.2.2 Demonstration Procedure

For demonstration, this use case can be triggered through the front IR distance sensors, which detect obstacles. The presenter could place an obstacle in in front of a model car, which would trigger an emergency brake and result in broadcasting a V2X warning message. Consequently, the following vehicles should stop, too.

The model cars are setup according to the common platform setup. Each vehicle drives along a predefined route. All involved model cars are enabled to support active brake as well as platooning.

The demonstration scenario comprises the following steps:

The vehicles drive autonomously on the predefined routes, keeping a sufficient distance and a constant velocity.
The presenter places an obstacle on the table.
The first vehicle detects the obstacle based on its sensor values. It stops right ahead the obstacle and sends V2X warning messages.
Oncoming vehicles will show a red light once entering the message area and will reduce their speed visibly, when closing in to the obstacle. Ultimately, they will stop autonomously in a safe distance.

3.3 Platooning Showcase

3.3.1 Use Case Description

The Platooning use case enables automated lateral and longitudinal control of a vehicle group (platoon) in order to let the vehicles travel closely one behind another in a safe manner. Driving inside a platoon promises to enhance traffic safety, to reduce fuel consumption and to better use available road space. Besides sensor values, a number of different V2X message types is used for coordination of vehicles inside a platoon.

3.3.2 Demonstration Procedure

To demonstrate the Platooning use case, the leading vehicle is controlled remotely. Vehicles following this vehicle will automatically try to form a platoon by closing in on the leader vehicle. The platoon (which consists of at least one additional vehicle) follows autonomously. As an option, people from the audience could take over the remote control of the leading vehicle – giving routing instructions directly to the leader (making turns, possibly adjusting the speed).

The model cars are setup according to the common platform setup. Each vehicle is controlled manually. All involved model cars (i.e. two) are enabled to support active brake as well as platooning.

The demonstration scenario comprises the following steps:

The model cars are controlled remotely and drive around the table.
As soon as one vehicle reaches a position closely behind another vehicle, the platooning function can be activated.
As vehicles negotiate the Platoon, a blue blinking light is visible.
If the negotiation is successful, die follower vehicles close the gap to the leader, forming the platoon.
As soon, as the platoon is established, a constant blue light will be visible to the audience, symbolizing the platoon.
Instructions given to the leader vehicle will be followed by all other platooning vehicles.

4 Demonstration of OVERSEE Platform Features

4.1 Prototype Setup

Some use cases are not well suited for presentation on real or model cars. The main reasons for that issue are: