102/25/11
Connected Vehicle Design Review
Southwest Research Institute
2
Agenda
Operational Concept System Architecture
– J2735 Driver– Subsystem
GUI Mockups– Device Status– TAMs– Configuration– Alerting
Additional Configuration
03/02/11Connected Vehicle Design Review
3
Operational Concept
SunGuide will handle specific messages from the SAE J2735 - DSRC Message Set Dictionary– Basic Safety Message (BSM)– Probe Vehicle Data Message (PVDM)– Traveler Advisory Message (TAM)
GUI– Aggregated Probe Data display– Manually create/manage TAMs by RSE
Response Plans– Pre-selects RSEs
• Automatically generated presentation region
03/02/11Connected Vehicle Design Review
4
Operational Concept
SDN– Send Probe data– Send TAMs
C2C– Provide demonstrators access
• Probe Data• TAMs• Standard SunGuide C2C data
03/02/11Connected Vehicle Design Review
5
System Architecture
03/02/11Connected Vehicle Design Review
Architecture Diagram
03/02/11Connected Vehicle Design Review
Driver Architecture
03/02/11Connected Vehicle Design Review
8
J2735 Driver
Probe Support– Support an incoming message from RSEs– Send incoming raw Probe data to SDN– Decode Probe data– Populate into XML formatting– Send to Subsystem
TAM– Decode XML from Subsystem– Send to SDN via web service interface– J2735 Encode– Send to RSEs at regular intervals
03/02/11Connected Vehicle Design Review
9
Subsystem Architecture
03/02/11Connected Vehicle Design Review
10
Subsystem Tasks
Probe– Collect Probe data by RSE– Log Probe data to the database– Send out to C2C and Operator Map– Generate Alerts based on Probe Data
TAM– Receive TAM add/modify/delete messages– Maintain list of current messages– Notify J2735 Driver of message queue changes
03/02/11Connected Vehicle Design Review
11
RSE Status Option 1: Single Device Status
03/02/11Connected Vehicle Design Review
12
RSE Status Option 2: Tabular
03/02/11Connected Vehicle Design Review
13
TAM CreationOption 1
03/02/11Connected Vehicle Design Review
14
TAM CreationOption 2
03/02/11Connected Vehicle Design Review
15
Manually Defined TAM Presentation Region
03/02/11Connected Vehicle Design Review
16
RSE Selection in Response Plans
Recommend selection based on radius search– Device linking is direction of travel based and could
miss RSEs that need to be selected
– RSEs are broadcast devices, similar to HAR• Messages can be picked up by anywhere but only
displayed when the OBE is in the presentation region• Even though a vehicle receives a message, there is
no guarantee they will ever enter the presentation region and display the message
03/02/11Connected Vehicle Design Review
17
Automatic Presentation Region Selection
Recommend selection based on device linking– RSE does not need to be in device linking for the
device linking to generate a presentation region– Region is generated by taking each involved
device linking segment and extending it in all upstream directions by a configurable amount
– Accurate device linking file required
03/02/11Connected Vehicle Design Review
18
RSE Configuration – Option 1: Single Device View
03/02/11Connected Vehicle Design Review
19
RSE Configuration – Option 2: Tabular View
03/02/11Connected Vehicle Design Review
20
Alerting - Option 1: Through IDS
03/02/11Connected Vehicle Design Review
21
Alerting - Discussion
03/02/11Connected Vehicle Design Review
Pros:– Familiar dialog to users– Re-use of exist GUI dialog
Cons– Requires a new IDS driver
Option 2:– WPF dialog with the same choices– Alert logging stays in CVS tables instead of IDS tables– Concept is similar to Pricing with different
acknowledgement options– For demo purposes, look of alert would be similar to
the other CV dialogs
22
Additional Configuration
Config File– Driver
• Port for incoming BSM and Probe Data• SDN
– Host and port– URL for the TAM Interface
Admin Editor– Response Plan Template
• Default Message• Amber Alert
EM– TAM presentation region offset
03/02/11Connected Vehicle Design Review
23
Requirements
03/02/11Connected Vehicle Design Review
Attached with Presentation Materials
24
Questions
03/02/11Connected Vehicle Design Review