 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev15 [issued: 01-30-07]
-
151 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
Flow of events
1.
Vehicle “A” sends MSG_BasicSafetyMessageFrame, Part I.
2.
Vehicle “B” receives message
3.
Vehicle “B” recognizes that Vehicle A’s message is relevant (crossing road segment via
map and/or heading)
4.
Vehicle “B” alerts its driver to a straight crossing path hazard.
Hardware Devices:
DSRC radio
Positional Sensors
Human-Machine Interface
Occupant
Vehicle
System
Driver
Passenge
r
Service
Provider
Road
Department
Actors: (What entities play an
active role in use)
X
X
Support information:
CAMP-VSC Task 3 Report, 2003
Concept of Operations
For this application, it is assumed that all identified subject vehicles would be equipped with DSRC units. It is also
assumed that messages from each vehicle would be sent to conflicting vehicles on other intersection legs,
necessitating clear line of sight or relaying techniques.
Upon receipt of each broadcast of MSG_BasicSafetyMessageFrame, Part I message, the recipient needs to
implement an algorithm to determine if a crossing path conflict is present. Once a conflict is determined the
vehicle could use appropriate human machine interface (HMI) techniques aboard the vehicle to issue a warning to
the driver.
Sensors and Other System Needs
A map database could help to provide information whether crossing path vehicles are in the vicinity of an
intersection. If lane resolution is possible, lane position of the crossing path vehicle can be used in the algorithm,
e.g., if a crossing path vehicle is in a left-turn pocket and it is known in advance that the left-turn and straight-
through phases are different, then the left-turning vehicle is no longer a likely threat.