02/25/11 Connected Vehicle Design Review Southwest Research Institute 1

Agenda Operational Concept System Architecture –J2735 Driver –Subsystem GUI Mockups –Device Status –TAMs –Configuration –Alerting Additional Configuration 2 03/02/11Connected Vehicle Design Review

Operational Concept SunGuide will handle specific messages from the SAE J 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 3 03/02/11Connected Vehicle Design Review

Operational Concept SDN –Send Probe data –Send TAMs C2C –Provide demonstrators access Probe Data TAMs Standard SunGuide C2C data 4 03/02/11Connected Vehicle Design Review

System Architecture 5 03/02/11Connected Vehicle Design Review

Architecture Diagram 03/02/11Connected Vehicle Design Review

Driver Architecture 03/02/11Connected Vehicle Design Review

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 8 03/02/11Connected Vehicle Design Review

Subsystem Architecture 9 03/02/11Connected Vehicle Design Review

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 10 03/02/11Connected Vehicle Design Review

RSE Status Option 1: Single Device Status 11 03/02/11Connected Vehicle Design Review

RSE Status Option 2: Tabular 12 03/02/11Connected Vehicle Design Review

TAM Creation Option /02/11Connected Vehicle Design Review

TAM Creation Option /02/11Connected Vehicle Design Review

Manually Defined TAM Presentation Region 15 03/02/11Connected Vehicle Design Review

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 16 03/02/11Connected Vehicle Design Review

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 17 03/02/11Connected Vehicle Design Review

RSE Configuration – Option 1: Single Device View 18 03/02/11Connected Vehicle Design Review

RSE Configuration – Option 2: Tabular View 19 03/02/11Connected Vehicle Design Review

Alerting - Option 1: Through IDS 20 03/02/11Connected Vehicle Design Review

Alerting - Discussion 21 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

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 22 03/02/11Connected Vehicle Design Review

Requirements 23 03/02/11Connected Vehicle Design Review Attached with Presentation Materials

Questions 24 03/02/11Connected Vehicle Design Review