“Spain” Pilot siteeCall for P2W

HeERO International Conference

21 November 2013

Bucharest, Romania

#heero

Alfonso Brazalez

abrazalez@ceit.es

• Strategy for the e-Call Deployment in Spain

• Consortium

• Spanish pilot Architecture

• Where we are and next steps

• eCall for P2W

2

Summary

-3-

Spanish Emergency PSAPs

Emergencies centralized in 112

But by regions

• Coordinator

• Sub-directorate General for Mobility

• Administrations

• DGT (Level1 PSAP) y 112 (Level 2 PSAP)

• Companies & Research Institutes

• Advisory board

• Sub-directorate General for Civil Protection

• Sub-directorate General of Network and

Telecommunication Operators

-4-

Consortium

2009/02/19Page 5

Accident

Vehicle

position

GNSS

MNO

eCall

raised Dissemination to Traffic Centres

MSD Data

for TM

Traffic Control Centers (DGT-CGT) /(Highway C.C.) / RACC Infotransit

ITS TrafficData

Aditional

Data

ITS Traffic Data

Most appropiate 112

Reroute

Data + Voice

Traffic

IncidentService detail

Stopped vehicles and injuries14/09/2011 15:02

There are two cars involved in an

accident, stopped at lane right side.

Human injuries are confirmed.

Traffic Event

DATEX II

Intermediate

PSAP

Spanish Pilot. Architecture

-6-

Spanish pilot. Tests

Level 1: Intermediate PSAP in DGT- Madrid

• MSD reception, decoding and filtering. Send MSD to regional 112

• Intermediate PSAP assessment

• Communication con TCC/TIC in own DGT building and Traffic Police

• Relation of MSD with the Spanish VIN and accident database (DGT)

Level 2: Regional 112 PSAPs: Castilla León, Galicia, Madrid y Valencia (WP2)

• Integration of eCall in own 112 emergency system

• MSD reception

MNO

• Implementation of eflag in mobile telecommunication network

• Assessment of MSD correct transmission in mobile network

IVS: equipment of vehicle M1 & L3 classes

Added Value

• PTW: sensor in helmets, eCall testing & proposal for future eCall standard

extension

• eCall Interoperability between 2 regional 112

-7-

Spanish pilot. Main features

Vehicles ready

for testing

-8-

HMI MODULE

Example of IVS system composed by IVS and HMI

And PSAP in DGT

-9-

Equipment already installed

Now

Verifying global system

Definition of evaluation methodology

In 2014

Training operators

Test and results

-10-

Spanish Pilot. Situation

P2W: powered two wheelers

Needs

eCall – P2W

Detection Call

• No trigger• Additional limitations

• Weight• Cost

Global Architecture

• Different source information integration

– Sensors • Acelerometers

• Compass

• Gyroscope

• GPS

• Previous phases

– P2W accidents classification

– Algorithm implementation

– Initial test in races

– Algorithm tunning

Detection. Architecture

• MSD: proposal of additional information

• Development: PSAP simulator of u-blox

Call. Features

• 2 functions:

– Voice communication during call by bluetooth

– Accident severity detection• Developed by NZI

• Fusion of information given by 12 sensors

• Helps to complete MSD

• Communication with the main module by Bluetooth

On board unit & helmet integration

MSD proposal

Name Size [B] Type DescriptionControl 1 IntegerVIN 20 String VIN number according to ISO 3779Time stamp 4 Integer UTC secondsLocation 4 Integer Latitude (WGS-84) in msService provider Service providerVehicle type 1 Integer PTWPTW Control 1 Integer b7 Master sensor in vehicle

b6 Master sensor in helmetb5 Slave sensor communication lostb4 Presence of passenger

Slave location 4 Integer Latitude (WGS-84) in msLongitude (WGS-84) in msDirection on degrees

Master severity 1 Integer Detection of severity of master deviceSlave severity 1 Integer Detection of severity of slave device

Questionnaire

• Helps to define really important issues for MSD

• Questionnaire for PSAP.

• Useful information for emergency services

• First approach

19

• Is it useful to communicate the orientation of the driver and the motorbike in the MSD?

• Is it useful to communicate the distance between the driver and the motorbike in the MSD?

20

• Is it useful to differentiate between the position of the driver and the position of the motorbike in the MSD?

Post crash. Position & orientation

• How often the positions of the driverhave to be updated?

• How long should be the duration of the update of the positions of the driver?

• How often the positions of the motorbike have to be updated?

• How long should be the duration of the update of the positions of the motorbike?

•21

Updating position & orientation

• Is it useful to know if there is any passengeron the motorbike?

22

Passenger related questions

• Is it useful to know if the communication between the driver and the motorbike has been lost?

• Is it useful to know previous motorbike information regarding precrashinformation, e.g. velocity, time to stop…?

23

Communication related question

• Is it useful to know a “crash severity index” given by the data registered in the motorbike?

• Is it useful to know a “crash severity index” given by the data registered in the helmet?

24

Crash severity related questions

• Which additional information makes sense in the MSD for P2V?

25

Generic additional question

• Preliminary tests for the integration OBU-Helmet in lab

• Test for the detection in races

– First meeting for the installation in motorcycle

• Test for the global integration with PSAP in a controlled environment. Simulating automatic eCall.

– Distance between motorcycle and helmet

– Automatic and manual triggered eCall

Tests. Planning and status

• Proposal for MSD for P2W

• Adaptation of the OBU for the integration with the helmet sensors has been completed

• The integration tests have been finished

• The OBU has been integrated in a racing motorcycle

• The season is over. Use of riding school for testing the algorithm and eCall trigger

• Preliminary controlled test done with Intermediate PSAP in Madrid

• Controlled tests programmed for next moths.

Conclussions

Thank you for your attention!Questions?

28

Alfonso Brazalez (abrazalez@ceit.es)