SPaT Challenge Webinar Series Webinar #2: Design Considerations, - PowerPoint PPT Presentation

SPaT Challenge Webinar Series Webinar #2: Design Considerations, Part 1 2:00 – 3:30 PM (Eastern) | March 20, 2018

Webinar Logistics • All lines are muted • Webinar will be recorded • Submit questions and comments in chat or Q&A section of webinar window • Questions will be answered at webinar conclusion 2

Agenda • Welcome and Introduction • SPaT Messages, Data Assembly, and the Signal Controller Interface  Patrick Chan, ConSysTec • V2I Hub  Chris Stanley, Leidos • Agency experience with deploying on-board units  Faisal Saleem, Maricopa County DOT • Q&A 3

SPaT Challenge To challenge state and local public sector transportation IOOs to cooperate together to achieve deployment of DSRC infrastructure with SPaT broadcasts in at least one corridor or network (approximately 20 signalized intersections) in each state by January 2020 4

First SPaT Challenge Webinar March 6, 2018 • Topics included:  Introduction to the SPaT Webinar Series and SPaT Challenge  Systems Engineering Approach to the SPaT Challenge  Overview of the Model Concept of Operations and Requirements documents  Costs, Procurement, and Corridor Selection 5

SPaT Challenge Resource Page https://transportationops.org/spatchallenge/resources 6

SPaT Challenge Resource Page https://transportationops.org/spatchallenge/resources 7

SPaT Challenge Resource Page https://transportationops.org/spatchallenge/resources 8

Upcoming SPaT Challenge Webinars • Design Considerations, Part 2  April 17, 2018 2:00-3:30pm ET  MAP messages, vehicle position correction, and DSRC licensing • MAP Creator Tool Demonstration  April 24, 2018 1:00-2:30pm ET  Live technical demonstration and step-by-step training on using the MAP creator tool • Design Considerations, Part 3  May 15, 2018 2:00-3:30pm ET  Backhaul infrastructure, intersection, and roadside equipment specification, design and installation • Deployment & Validation  June 12, 2018 2:00-3:30pm ET  Procurement, validation, verification, and security of SPaT deployments 9

Signal Controller Interface for SPaT messages Patrick Chan, ConSysTec

Overview of Presentation • Introduction to the SPaT Message • Introduction to NTCIP 1202 v03 • SPaT Implementations 11

Introduction to the SPaT Message Roadside Unit Signal Controller Traffic Management Unit Center Connected Devices 12

Introduction to the SPaT Message • SAE J2735 – DSRC Message Set Dictionary  Current version: SAE J2735_201603  Developed with international community input  S ignal P hase a nd T iming Message 13

J2735 SPaT Message Message: MSG_SignalPhaseAndTiming Field Object Description Req/Opt timestamp data element timestamp optional MinuteOfTheYear name data element Name for the collection of optional DescriptiveName intersections intersections data frame List of each intersection required IntersectionStateList SPaT data is provided regional data frame Regional extensions, if optional RegionalExtension any A single SPaT message can provide signal timing data for up to 32 intersections. 14

J2735 SPaT Message Data Frame: IntersectionState Field Object Description Req/Opt id data element Unique regional identifier required IntersectionReferenceID for the intersection required revision data element MsgCount Version of the message* status data element General status of the required IntersectionStatusObject intersection states data frame MovementList The status of each required movement at the intersection * ISO TS 19091 indicates MsgCount should only be incremented when the message content changes. 15

J2735 SPaT Message Data Frame: MovementState • Are we allowed to move? • When will it change? 16

J2735 SPaT Message Data Frame: MovementState For each movement: Field Object Description Req/Opt signalGroup data element Identifier for an allowed required SignalGroupID movement. Tied to the MAP message (to a lane or set of lanes) eventState data element Phase state (protected, required MovementPhaseState permissive, yellow, red, etc.) timing data element Time stamps for an event optional TimeChangeDetails speeds data frame Speed advisories for optional AdvisorySpeedList general or specific vehicles 17

J2735 SPaT Message Data Frame: TimeChangeDetails Field Object Description Req/Opt startTime data element Time when the event first started optional TimeMark minEndTime data element Earliest time the event will end required TimeMark maxEndTime data element Latest time the event will end optional TimeMark likelyTime data element Most likely time the event will end optional TimeMark confidence data element Confidence level of the likely time optional TimeMark nextTime data element When the event will occur again optional TimeMark 18

J2735 SPaT Message Other Optional fields Field Object Description Req/Opt enabledLanes dataFrame Tied to MAP optional EnabledLaneList message, indicates which lanes are currently active. maneuverAssistList data frame Details about traffic optional ManueverAssistList flow for specific lanes and maneuvers (e.g, queue length, potential pedestrian or bicycle conflicts) 19

J2735 SPaT Message Maneuver assist • Left allowed in Lane 23 Enabled Lanes: • To Lane 13 or 14 • Lane 1 = parking lane 11 12 13 14 • Queue length • Lane 5 = travel lane • Ped conflict? 1 / 5 21 2 22 3 23 4 24 31 32 33 34 20

J2735 SPaT Message • Used in conjunction with a MAP message  The MAP message defines the lanes and the possible movements at the intersection  The MAP message does not change unless the roadway geometry changes  The SPaT message identifies the enabled lanes and additional dynamic information for a movement  signalGroupId – links the SPaT with the MAP 21

NTCIP 1202 v03 Roadside Unit Signal Controller Traffic Management Unit Center Connected Devices 22

NTCIP 1202 v03 • Object Definitions for Actuated Signal Controllers (ASC) Interfaces  Version 3 adds systems engineering content, support for the cabinet environment, managing I/O mapping, exception reporting, and support for connected vehicles  Version 3 is currently in ballot. 23

NTCIP 1202 v03 • Connected Vehicles Interface  Configure the interface between a controller and a RSU  Generate and exchange SPaT data  Generate and exchange MAP data  Receive Basic Safety Messages and Personal Safety Messages as detector inputs 24

NTCIP 1202 v03 25

NTCIP 1202 v03 • Different physical architectures  The ASC process is part of the controller unit  The CV Roadside process  In the same physical unit as the DSRC radio  In the same physical unit as the controller unit  Its own separate physical unit 26

NTCIP 1202 v03 • Supports different architectures between the ASC and RSU  Who is the manager?  Does the ASC “push” SPaT data to the RSU, or does the RSU “pull” SPaT data from the ASC  Each has benefits and issues  May be determined by the policies of each agency  Must be defined in the specification • Let the market decide 27

NTCIP 1202 v03 • Configure the RSU interface  Manage the ports  Manage the watchdog 28

NTCIP 1202 v03 • Generate and exchange SPaT data  Objects were created to address all SPAT- related mandatory and optional data elements in SAE J2735_201603 except:  start time for a movement  Regional extensions  Adds performance requirements  How often is SPaT data provided  How quickly SPaT data is provided after an event 29

NTCIP 1202 v03 • Generate and exchange SPaT data  Issues:  Time reference – The controller may have a different time source than the RSU  Controller provides timestamps in ticks (1/10 th of a second) elapsed since the top of the hour, and allows the RSU to resolve time 30

NTCIP 1202 v03 • Generate and exchange MAP data  Objects were created to address all MAP- related mandatory data elements for intersections in SAE J2735_201603  Necessary to ensure the SPaT data and MAP data are synchronized  Provides a check that the correct MAP is in effect  Provides a check that mutually exclusive enabled lanes are not in effect 31

NTCIP 1202 v03 • Receive Basic and Personal Safety Messages as detector inputs  Creates virtual detectors that are tied to the ASC detector inputs  Detector boundaries can be a lane or a geofence  Provide filters such as vehicle type, direction of travel, speed 32

NTCIP 1202 v03 • SignalGroupID = channel output number • Current Status  Standard in ballot soon  Some vendors have started adopting the balloted standard  Some risk involved • Changes • Lessons Learned 33

SPaT Implementations • USDOT CV Pilots in New York City and Tampa • Multi-Modal Intelligent Traffic Signal Systems (MMITSS) 34

NYC CV Pilot • Implementing the balloted version of NTCIP 1202 v03 to provide SPaT data  Working with the ASC Working Group on implementation issues  Only sends SPaT data when there’s a change in movement status (state or timestamps)  Sending SPaT data to Amazon Cloud to support PED applications for the visually impaired 35