SPaT Challenge Webinar SeriesWebinar #5: Design Considerations, Part 3

2:00 – 3:30 PM (Eastern) | May 15, 2018

2

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

3

Agenda• Welcome and Introduction Blaine Leonard, Utah DOT

• RSU Specification v4.1 Deborah Curtis, USDOT Ed Leslie, Leidos

• Roadside Equipment & Backhaul Communications Raj Ponnaluri, Florida DOT Brian Reed, WSP

• DSRC Licensing Yang Tao, City of Madison

• Q&A

4

SPaT ChallengeTo challenge state and local public sector transportation infrastructure owners and operators (IOOs) to deploy DSRC infrastructure with SPaT (and MAP) broadcasts in at least one corridor or network (approximately 20 signalized intersections) in each state by January 2020

20 intersections in 50 states by 2020!

Two years of progress:35 Locations

25 States

500 RSUs Operating

2340 RSUs Planned

5

SPaT Challenge Webinars to Datehttps://transportationops.org/spatchallenge/webinarseries

• Four webinars conducted to date Recordings available on SPaT Challenge website

1. Initial SPaT Challenge Activities (March 6) SPaT Challenge introduction Systems Engineering Approach Overview of Model Concept of Operations and

Requirements documents Costs, Procurement, and Corridor Selection

6

SPaT Challenge Webinars to Datehttps://transportationops.org/spatchallenge/webinarseries

2. Design Considerations, Part 1 (March 20) SPaT Messages, Data Assembly, and the Signal Controller

Interface V2I Hub Overview Agency experience with deploying on-board units

3. Design Considerations, Part 2 (April 17) Overview of MAP Messages Utah DOT’s MAP Message Creation Approach Vehicle Position Correction Need and Solutions

4. MAP Creator Tool Demonstration (April 24)

7

SPaT Challenge Resource Pagehttps://transportationops.org/spatchallenge/resources

8

SPaT Challenge Resource Pagehttps://transportationops.org/spatchallenge/resources

9

SPaT Challenge Resource Pagehttps://transportationops.org/spatchallenge/resources

10

Next SPaT Challenge Webinar• Deployment & Validation June 12, 2018 2:00-3:30pm ET Procurement, validation, verification, and

security of SPaT deployments

Register and find more information at: https://transportationops.org/event/webinar-5-spat-challenge-deployment-validation

Overview of USDOT Roadside Unit Specification v4.1Deborah Curtis, USDOT Chris Stanley, LeidosEd Leslie, Leidos

12

Roadside devices to enable communication between connected vehicles and existing traffic control equipment & systems

Federal Highway AdministrationSaxton Transportation Operations Lab

USDOT Roadside Unit 4.1 Specifications

13

RSU Overview

• RSU provides information about infrastructure (e.g. SPaT/MAP from traffic controller or TIM)

• RSU collects information about vehicles (e.g. BSM, PVD)

• On-Board Unit (OBU) receives and process the messages based on its current GPS co-ordinates

• RSU broadcasts wave service advertisements (WSA) which are received by OBU and OBU sets the channel and routing information accordingly

• IP connectivity to OBU is achieved by running WSA and IP service applications on RSU

14

RSU with 3.0 vs. 4.1 Hardware and Software

RSU with 4.1 Devices• Hardware: 4.1 devices should include a hardware

security module (HSM) to provide secure storage and processing (required by SCMS)

• Software:• requires more use of Simple Network Management Protocol

(SNMP) and provides a MIB

• adds health and status monitoring features

• increases security requirements (e.g. passwords, ports, etc.)• Require the latest (2016) version of connected vehicle

(CV) specifications with examples

15

SNMP Specifications

Intent is to move toward Simple Network Management Protocol (SNMP) rather than direct loading of message files by SCP, etc.• Simplify device interaction• Improve security• Simplify management of a large number of devices

16

Message Forwarding Specifications

Should the RSU forward (1609) headers?• Headers contain useful information• Make it configurable (through NTCIP 1218)

How should the WSA handle Immediate Forward messages?• IF messages don’t have a predefined duration• Advertise the service as long as the message is

transmitted?

RSUTMC

17

RSU Set Specifications

• Intent is to allow a large intersection with poor line-of-sight to be equipped with multiple RSUs that will provide the same messages and improve the coverage of DSRC radios

• Operate as a single unit and appear to vehicles and to a traffic management center (TMC) as a single unit

RSUMASTER

RSU SLAVE

TMC

RSU SLAVE

RSU SLAVE

18

Functional Test Summary

• Physical• Positioning• SNMP• Logging• Security• Message Forwarding• Wave Service Advertisement (WSA)

19

Future Releases

A 5.0 release is expected before widespread deployment (years away)• Account for lessons learned• Build on experience of Pilots, SPaT challenge

participants, and other deployers

FAQ document will be availableFurther questions can be asked through the CVCS support site

RSU 4.1 Specification: https://rosap.ntl.bts.gov/view/dot/3600

RSU 4.1 Test plan: https://rosap.ntl.bts.gov/view/dot/3621

20

Connected Vehicle Support Serviceshttps://cvcs.samanage.com/ Toll-free #: 1-844-DOT-CVCS (1-844-368-2827)

Business hours: Monday-Friday, 8:00AM - 5:00PM EST

Ed LeslieLeidosSaxton Transportation Operations Lab Edward.M.Leslie@Leidos.com

Roadside Equipment & Backhaul Communications Raj Ponnaluri, Florida DOT

Signal Phase and Timing Challenge UpdateRaj Ponnaluri, P.E., PhD., PTOE, PMPFlorida Department of Transportation

23

Agenda

• AASTHO Challenge• SPaT Pilot Project• Technologies• Pre-Deployment Testing• Deployment

24

TSM&O Strategic Plan – Primary Focus Areas

25

Statewide Arterial Management Program

26

Florida’s CV Program

27

AASHTO SPaT Challenge

• Challenge state and local public sector transportation Instructure Owners & Operators (IO&Os) to deploy Dedicated Short Range Communication (DSRC) infrastructure with SPaT broadcasts in at least one coordinated corridor or network (approximately 20 signalized intersections) in each state by January 2020.

• 20 Intersection in 50 states by 2020!

28

21 signalized intersections along US 90 (Mahan Drive) in Tallahassee

FDOT and City of Tallahassee Partnership City installed equipment

Pre-deployment testing at the Traffic Engineering Research Laboratory (TERL)

Vendor selected in Q4 2017

Deployment completed

SPaT Pilot Project

29

System Knowledge – Controller/Roadside Unit Communication

Questions to ask prior to installation and deployment:• Is there anything that needs to be installed (physically or

software) to the existing infrastructure?• How will the controller communicate to the Roadside Unit

(RSU)?• MAP file configuration – during testing phase

Both Google (or other map site) and onsite inspection need to be performed

Need controller phase/lane assignment or some indications will display incorrectly

• Where will the MAP file reside?• Any other considerations for the MAP file?

30

Traffic Controller• Ensure the traffic controller firmware and any other

SPaT/CV software/hardware are compatible and installed in the cabinet.

31

Roadside Units (RSU)

• Designate and configure the unit before installation Note: MAC, IP, and other unique attributes before

installation• Tallahassee location (based on RSU

manufacturer) required two RSUs per intersection at multiple locations Conduct a study to verify if two RSUs at one

intersection is needed for line of sight• Ensure antennae, cable entry, and any other

access points to the device are secured and water tight

Pre-Deployment Installation at TERL

RSU and Antenna Placement on Mast Arm/Spanwire

Radio Antenna on the Vehicle

35

Multi-Channel Test Tool (MCTT)• Used to verify signal strength and quality as well as

display raw data being received from the RSUs• Can be a DSRC radio reserved specifically for use as

and configured to detect RSU messages with laptop computer or other device

• Designate and configure unit before installation Note: MAC, IP, and other unique attributes before installation

36

On-Board Unit (OBU)• Configuration varies Some manufacturer OBUs do not

require the external computer Ensure the OBU can process

and handle the flood of SPaT/MAP messages when multiple RSUs are within range of the OBU.

• Designate and configure unit before installation

37

On-Board Unit (OBU)

Modem

New ModemPi

Complete OBU (except for the tablet)OBUs can comprise of a DSRC radio and GPS connected to a Raspberry Pi, and includes a cellular modem and a router with WiFi to an tablet.

Pre-Deployment Testing

SPaT Pilot Project – Pre-Deployment Testing

Field Deployment

SPaT Pilot Project – Lessons Learned

• Two stage FCC licensing: First: blanket approval for use of DSRC Second: Location (GPS detail, mounting height of devices,

make and model of RSU’s and OBU’s)• Ensure devices are licensed by FCC for deployment• Proposers should ask questions during the procurement

process regarding device compatibility with controllers • Ensure the MAPs are properly coded and the Uper Hex code

is validated for field testing; offer vendors to develop their own• Consider expanding SPaT with other CV technologies

including bike-ped safety, etc.

42

Thank you!

Raj Ponnaluri, P.E., PhD., PTOE, PMPConnected Vehicles and Arterial Management EngineerTransportation System Management & Operations (TSM&O)Florida Department of TransportationRaj.Ponnaluri@dot.state.fl.us

Roadside UnitsBrian Reed, WSP USAManager Geospatial & Applied Technology

45

Agenda• Introduction to Licensing – FCC• RSU Site Selection• Procurement• Cabinet Audit/Installations• Management and Monitoring (SoH)• O&M Recommendations

46

Introduction to Licensing RSUs

• Dedicated Short Range Communication 5.9G band FCC Governing Agency Initial pilots – use under USDOT license grant Effectively a fixed radio roadside unit (RSU)

• New sites/deployments Need to request FCC site specific license Includes SPaT Challenge locations

47

DSRC Licensing 1011. Perform Site Selection – gather GPS position for RSU2. Check TOWAIR -

http://wireless2.fcc.gov/UlsApp/AsrSearch/towairSearch.jsp3. Get determination of No Hazard - File FAA Form 854.4. Apply for Geographic License - FCC FORM 601 Main

Form and Schedule D5. Register sites under the Geographic license – FCC Form

601 and Schedule M6. Certify construction of the RSU – FCC Form 601 and

Schedule K. http://wireless.fcc.gov/uls/index.htm?job=home

48

Source – Toyota Technology Center, USA

DSRC Spectrum Allocation

49

RSU Design Considerations• Collocation: Wherever feasible, CV equipment will be

collocated at CCTV, DMS or traffic signal locations sites to take advantage of the existing roadside infrastructure, power and communications equipment.

• USDOT Compliance - The RSU to be installed on projects shall meet the latest “5.9GHz DSRC Roadside Equipment” Device Specification issued by the USDOT v4.1a.

• Mounting Height - Per the FCC regulations the DSRC radio shall be mounted at a maximum height of 8 meters or around 26 feet above the roadway surface before a maximum Equivalent Isotopically Radiated Power (EIRP) limitation occurs.

50

Site Selection• Clear Line of Sight - RSU mounting location shall be optimized

to achieve clear line of sight free of RF signal path interference from trees, bridges, overpasses and other structures. • Needs to be hard fixed mount location• Avoid sway/vibration. • 18-24” off mast/strain poles

• Spectrum Analysis - DSRC spectrum coordination must be completed to assure all FCC regulatory requirements are met and to ensure no interference with other existing RF signals is present.

• Detection Range: A maximum detection range of 1200 meter radius using for the RSU placement.

51

Path Analysis – 3DLIDAR SurfaceProduction Mapping – various broadcast radii (by attenuation)

52

Typicals for Installation

53

Typicals for Installation

54

Cabinet Audits - Considerations• Backhaul communications• Determine local cabinet switch capable to

handle new backplane requirements (SPaT, BSM forward, SRM, etc.) Key decision point IP4/IP6 dual stack

• Power sufficiency (DC vs. AC) Ready for PoE+ (328’ max Ethernet cabling distance) Remote device reset required (e.g. iBoot)

• Traffic Signal Controller (make, mode, firmware) Ready for SPaT direct to RSU V2I hub min-SPaT format/syntax

55

Procurement• Evaluation of USDOT Specification 4.1a Define DSRC needs for my deployment Select or define DSRC applications (new vs.

minimum) Evaluate SNMP for Management and Monitoring

• Standards continuing to evolve (SAE, IEEE)• Evaluate selection criteria, evaluation-based

RFP Recommend including bench test units prior to

purchase (or in the RFP selection criteria) Define unit quantities over a timeframe

56

State of Health (SoH)• Management and Monitoring or SoH SNMP v3 DTLS required Define SNMP client type MIBs and more MIBs Not all are equitable (yet) Commercial tool challenges

57

Cloud Service State of Heath - custom MIB

58

Cloud Service State of Heath - custom MIB

58

59

Cloud Service State of Heath - custom MIB

59

60

O&M Recommendations• Need to research and learn standards• Define data elements for storage/analysis BSM Part 1, Part 2

• Define On-board Unit use for Fleet vehicles Likely to need custom development Define demonstration vs. trial use only

• SNMPv3 as requirement• Bench testing in each DSRC procurement

process/document

Backhaul CommunicationsBrian Reed, WSP USAManager Geospatial & Applied Technology

62

Agenda• Role Backhaul• Introduction to Security• Data Transfer• Remote distribution of Infrastructure-based

messaging• Backhaul scenarios: Ann Arbor – shared use fiber Michigan DOT – ITS and mixed wireless/fiber ITS World Congress – pure wireless

63

Backhaul Communications Role

• Support Security and Encrypted Message-set Broadcast Security Certificates – every 2w SCMS Production Certificates for deployment Test Certificates for initial test

• Data to back office (Agency, USDOT)• Remote Device O&M• Remote Message-set updates (TIM)• TSP/SRM

64

Introduction to Security

• Security Credential Management System• Security method to protect

data transmissions between V2V and V2I

• Provides authentication and certificate for all CV message sets

• Registration Authority• https://standards.ieee.org/dev

elop/regauth/psid/index.html• AID/PSID Assignment

Numbers

65

SCMS Supported V2X/PSIDs

66

SCMS 201• Commercial SCMS providers First use in production - GreenhillsTLS (443 in/out)IP6 use so far, IP4 untestedRecommend terms to Service Level Agreements

Variances likely with others in marketPrice, Performance, Implementation Requirements

• Request PSIDs by application SPaT (0x82), MAP (0x20-40-97), TIM (0x83),

WSA (0x87), PSM (0x27), PDM (0x84)

67

Data Transfer - Example

68

Data Transfer and remote messages intro

• RSU (WSA) < OBUs• RSU (PDM) < OBUs• RSU (SPaT/MAP) < OBUs• RSU (TIM) < OBUs• OBUs (Probe Vehicle Data) < RSUs• OBUs (BSM) < OBUs and RSUs• OBUs (SRM) < RSUs

69

Remote Distribution Message-sets• SSH to RSU remotely Unit login CLI config changes

• Datawarehouse Tool as it stands Remote send specific – TIM and MAP

• State of Health Management and Monitoring SNMPv3 – monitor and troubleshooting/management

• Configuration Management Tool SNMP v3 – high-res MAP, TIM RSU configuration changes

70

Backhaul scenarios

• 1) Shared use fiber – SPMD/AACVTE• 2) Mixed user fiber/wireless – MDOT• 3) All wireless – ITS World Congress

71

Wireline - example

72

Wireline/Wireless - example

73

Wireless - exampleRSU

DSRCIP6/IP4

Cab Switch GBEIP6/IP4

Typical DSRC System ArchitecturePer Cabinet

SCMSIP6

Host DataMgtIP6/IP4

HostO&M/SoH

IP6/IP4

LTE PrivateSHA Cloud

ATT DigiCell

Aggregator

INTERNET IP/Services PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 1

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 2

ATT DigiCell

Aggregator

PoE+ IP30 Switch

RSUsDSRC

IP6/IP4

Cab Switch GBEIP6/IP4

Site 3

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 4

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 5

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 6

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 7

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 8

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 9

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 10

ATT DigiCell

Aggregator

PoE+ IP30 Switch

Cab Switch GBEIP6/IP4

Site 11

ATT DigiCell

Aggregator

PoE+ IP30 Switch

GbpsWireless Ethernet

APs

74

ResourcesDSRC RSU Specification (4.1a – April 2017)• https://transportationops.org/publications/dedicate

d-short-range-communications-roadside-unit-specifications

SAE DSRC Standards (J2735 - Message Set Dictionary/ASN, J2945/9, J2945/1, J2540/2, J2354, J2630) • https://www.sae.org/search/?qt=DSRCCAMP SCMS PoC V2X Applications• https://wiki.campllc.org/display/SCP/SCMS+PoC+

Supported+V2X+Applications

DSRC LicensingYang Tao, PhD, PECity of Madison, Wisconsin

76

77

Madison Smart Park St Corridor

• Pilot and deploy connected vehicle technology to improve: Safety Mobility Bus on-time performance Equity

• Vehicle to infrastructure (V2I), Vehicle to Vehicle (V2V), Vehicle to Everything (V2X)

• Madison and Wisconsin as the Upper Midwest hub for CV & AV

78

DSRC• Part of the Intelligent Transportation

Systems radio service communication frequency band

• 5.9 GHz band (5850-5925 MHz)• CRF 47 Parts 90 and 95• FCC Rules Part 90, Subpart M• Coexists with other NTIA authorized federal

users and some commercial satellite operators

79

Agency Responsibilities

• Reviewing FCC service rules, regulations, and technical requirements

• Deployment planning• Licensing administration• Coordination with other users

to reduce interference• Ongoing management

80

DSRC Licensing Steps• FCC Registration Number (FRN)• Non-Exclusive Geographic Area License• Individual RSU Registration• Plan for 3 months

81

FCC Registration Number (FRN)• FCC Commission Registration • System (CORES)• Registration login information• AASHTO list of radio frequency

coordinators:http://aashto.radiosoft.com/Pages/statecoord.html• Existing FRNs and contacts:https://apps.fcc.gov/coresWeb/publicHome.do

82

Non-Exclusive Geographic Area License

• Based on the public or private entity’s legal jurisdictional area of operations

• All channels in 5.9 GHz band• Granted for 10 years and may be renewed• Public entities: IQ radio service; Private or

commercial entities: QQ radio service• FCC Form 601 and Schedule D16• Universal Licensing System (ULS):https://wireless2.fcc.gov/UlsEntry/licManager/login.jsp

83

Individual RSU Registration• An application required for each RSU• Batch application available• Make and model, serial number, antennas,

latitude/longitude/height, support structure• FCC Form 601 and Schedule M to register• FCC Form 601 and Schedule K to certify

construction• Universal Licensing System (ULS):https://wireless2.fcc.gov/UlsEntry/licManager/login.jsp

84

Ongoing Considerations• File a notice of construction within a

year• Termination Pending status otherwise• Terminated automatically if the

licensee does not file a timely petition for reconsideration

• Inactive license or site registration will be discontinued in a year

• Licensee’s responsibility to delete from registration database

85

ResourcesFHWA CV Environment Guide• https://rosap.ntl.bts.gov/view/dot/3577/dot_

3577_DS1.pdf

NOCoE DSRC Licensing Guide• https://transportationops.org/spatchallenge/

resources/Recommended-Practices-for-DSRC-Licensing-and-Spectrum-Management

86

Next SPaT Challenge Webinar• Deployment & Validation June 12, 2018 2:00-3:30pm ET Procurement, validation, verification, and

security of SPaT deployments

Register and find more information at: https://transportationops.org/event/webinar-5-spat-challenge-deployment-validation

Q&ASubmit questions and comments in chat or Q&A section of webinar window

Upcoming SPaT Challenge WebinarDeployment & Validation June 12, 2018 2:00-3:30pm ET