Focus · Road safety
SIGNIS
Vehicle traffic safety
The vehicle itself reports the hazard: within seconds, and only to those about to arrive.
DNAGE Holding MGM Lab
October 2026
The problem

Today the warning arrives when the hazard is already there

Drivers arriving in the first minutes get no warning
t = 0

The event: crash, obstacle, slippery road

+ minutes

Someone calls emergency services or reports it by hand in an app

≈ 10 min

The warning appears in navigation apps

and then…

Variable message signs, often after the event is over

Indicative times described in the project document. SIGNIS times are targets to be validated in trials.
SIGNIS02
What changes

Three limits to overturn

Timeliness

Seconds, not minutes: the data is born on the vehicle involved, without waiting for someone to report it.

Content

Not just queues: grip, visibility, obstacles, stopped vehicles, crashes.

Selectivity

The warning reaches only those travelling that stretch, in that direction, in the following minutes.

Select a card to open the details
At 130 km/h, 5 minutes is about 11 km upstream of the event.
SIGNIS03
What already exists

Who warns approaching drivers today · and the gap that remains

Starting from a person

Emergency calls and manual reports in apps. The warning arrives minutes later.

Starting from the vehicle, but…

Only on new cars of one brand, only from emergency vehicles, or they only alert emergency services or the fleet manager.

SIGNIS

From the vehicle, automatically, on any brand, including vehicles already on the road. It warns approaching drivers within seconds, by radio and over the network.

Tools cited by category.
SIGNIS04
The data source

Every moving vehicle is already a sensor

rain · temperature ABS · ESC · ASR steering · brake · pedals GNSS · accelerometers TPMS OBD-II
Weather

Rain sensor, outside temperature, headlights and wipers

Grip

ABS, ESC and ASR interventions, wheel slip

Manoeuvres

Steering angle, brake, pedals: swerves and emergency braking

Dynamics

GNSS, accelerometers, TPMS, airbags, seat belts, engine

Where this data comes through: the OBD-II port
See the technical detail →
SIGNIS05
The device

One on-board unit, two ways to install it

Vehicle networkCAN · OBD-II · control units Own GNSS + IMUposition, heading, impacts On-board unitclassifies the event secure signature · pseudonymous certificates V2X radio 5.9 GHz→ approaching vehicles · seconds Modem 4G/5G→ operator, emergency, platform
New vehicles

factory-fitted by the manufacturer

Vehicles on the road

retrofit on the OBD-II port, with the same functions

Select a block to open the details
SIGNIS06
A case, step by step

A1 motorway, km 234: a car is stopped in the middle of the carriageway

Illustrative example
t = 0 s

Vehicle A gets a puncture, loses control, hits the guardrail and stops in the carriageway.

t = 0

Puncture, loss of control, guardrail impact

< 1 s

On-board data fusion: tyres, deceleration, ESP, airbags, occupants, engine running

≈ 1 s

Signed V2X message, only to vehicles approaching in that direction

seconds

Alert with full data to the road operator, 112, traffic police, rescue and recovery

minutes

Passing vehicles confirm the event; traffic updates in navigation apps

Times shown: project targets, to be validated in trials.
SIGNIS07
Communication

Two phases, two channels, two alert levels

Only vehicles on that carriageway are warned, within 5 minutes upstream
Standard message

European DENM format over 5.9 GHz radio, signed. No mobile coverage needed.

Only who needs it

Relevance zone: the event’s carriageway and direction. At 130 km/h, 5 minutes ≈ 11 km.

Even in tunnels

The message hops from vehicle to vehicle until the first one with 4G/5G coverage.

!SEVERE imminent obstacle in the carriageway ↓CAUTION slow down, possible hazard
SIGNIS08
The alert on board

Lighting up the dashboard warning lights: the knot to untie

Retrofit solution

The device reads from the vehicle network and warns through its own interface: display, lights, audible signal, Android Auto or CarPlay.

Vehicle cybersecurity

UNECE R155 and R156: mandatory on all new EU vehicles since July 2024.

Access to the OBD port

CJEU C-296/22: read while driving; write only when stationary.

Permitted security measures

Delegated Reg. (EU) 2026/699 on the OBD port.

Always: two levels, colour plus word and sound, never colour alone. · Select a constraint for details
SIGNIS09
The regulatory framework

The rules the project has to work with

Traffic and safety
Dir. 2010/40/EU, amended by 2023/2661ITS framework: safety information service on the TEN-T network by 2026
Delegated Reg. (EU) 886/2013 · SRTI8 categories of safety events; under EU review
Emergency and real-time traffic
Reg. (EU) 2015/758 · Delegated Reg. 2024/1084eCall and NG eCall over 4G/5G; PSAPs ready from 1/1/2026
Delegated Reg. (EU) 2022/670 · RTTIReal-time traffic via National Access Points
Italy
Ministerial Decree 70/2018 «Smart Road»Naples ring road: first certified infrastructure, June 2026
Radio and cybersecurity
ETSI EN 302 637-3 · EN 302 636 · 5.9 GHzDENM and GeoNetworking messages on the dedicated ITS band
UNECE R155 / R156 · Reg. (EU) 2018/858Cybersecurity, software updates, secure access to the OBD port
Personal and vehicle data
GDPR · European C-ITS PKIMinimal data and rotating pseudonymous certificates
Reg. (EU) 2023/2854 · Data ActAccess to and sharing of vehicle data
The framework is favourable

But it must be respected: the ITS Directive asks precisely for safety information services on the core network.

Select a card for details
SIGNIS10
How we prove it

A road pilot, three simple questions

How many seconds until the warning reaches approaching drivers?

From the event to the first vehicle warned.

Does it reach only those on that stretch, in that direction?

Who should have received it and who should not.

Does it work in tunnels too, with no network?

Hopping from vehicle to vehicle until the first one with coverage.

Pilot hypothesis: a fleet of buses or heavy vehicles on one corridor, measured and validated by a university, joining the European Data for Road Safety ecosystem.

What remains to be solved, said up front
Manufacturer data

ABS, ESC, steering, pedals, TPMS and seats travel as each manufacturer’s own CAN messages: their specifications are needed.

Writing to the dashboard

From the OBD port, while driving, you can only read. Dashboard integration goes through factory fit, with the manufacturer.

Anonymity

Location data is hardly ever «fully anonymous» under the GDPR: we work with pseudonyms, minimal data and rotating certificates.

SIGNIS11
The strategy

The ambition: from fleets to manufacturers

EU precedents
Seat beltsstandard fitment
TPMSnew cars since 2014
eCall · SOSnew types since 2018
GSR2 2019/2144ISA, EDR, emergency braking

Standard on every new vehicle, worldwide, available to everyone.

SIGNIS12
The ecosystem

From the device to the platform

Road network digital twin

simulates roadworks, abnormal loads and escorts before carrying them out

Data for road operators

real-time events to road operators and National Access Points

Connected platforms

Smart Place and Nexus Health use the same data

Select a system to open the details
SIGNIS13
Next steps

From prototype to manufacturers

STEP 1
Retrofit prototype

OBD reading, IMU, V2X radio and own interface

STEP 2
Pilot on a fleet

Buses or heavy vehicles on one corridor, measured and validated by a university

STEP 3
Manufacturers

Dashboard integration, R155, local alerts in the Euro NCAP 2026 protocol

STEP 4
Scale

More fleets, law enforcement, road operators

Timing and resources for each step to be defined.
SIGNIS14
Who warns those about to arrive?
SIGNIS · the vehicle itself, within seconds.
DNAGE Holding MGM Lab
www.dnagesrl.it
Contact us