ITS Standards for Dummies

ITS Standards for Dummies ITS Georgia Celebrating ten years of ITS! Tuesday October 2, 2007 Bob Rausch, P.E. robert.rausch@transcore.com 1

Outline Background How we got here.... Development Process Discuss Content Standards Center to field NTCIP Center to center NTCIP C2C (2306) Traffic Management Data Dictionary ATIS (SAE J2354) Incident Management (IEEE 1512) ATC/2070 2

ITS National Architecture Identified the Links Requiring Standardization Remote Access Subsystems Personal Information Access Remote Traveler Support Information Service Provider Center Subsystems Traffic Management Emissions Management Emergency Management Transit Management Toll Administration Freight & Fleet Management Commercial Vehicle Admin Archived Data Management Maintenance & Construction Wide Area Mobile Fixed Communications Vehicle Roadway Vehicle to Vehicle Transit Commercial Vehicle Emergency Subsystems Maintenance & Construction Short Range Wireless Toll Collection Parking Management Commercial Vehicle Check Roadside Subsystems 3

Standardization assigned to various SDO s Remote Access Subsystems Personal Information Access Remote Traveler Support Information Service Provider Center Subsystems Traffic Management Emissions Management Emergency Management Transit Management Toll Administration Freight & Fleet Management Commercial Vehicle Admin Archived Data Management Maintenance & Construction Subject of ATIS Message Set Subject of TMDD and Message Set Subject of IEEE Message Sets Wide Area Mobile Fixed Communications Subject of NTCIP Communication Protocols Vehicle to Vehicle Vehicle Transit Commercial Vehicle Emergency Subsystems Maintenance & Construction Short Range Wireless Roadway Toll Collection Parking Management Commercial Vehicle Check Roadside Subsystems Subject of NTCIP Data Elements Subject of ASTM/IEEE 1609/802.11p 4

The Physical Implementation View TMC EMC TMDD C2C NTCIP IEEE 1512 C2C NTCIP TMC SAE J2354 TMDD C2C NTCIP ISP C2F NTCIP IEEE DSRC Roadside Devices Other DMS ASC ATMS TMDD NTCIP ATIS In Vehicle SAE 5

ITS Standards Are Really Quite Simple! Center to field standards describe Management of the parameters that govern a device s operation, monitor its status, collect data How to exchange that information protocols Dialogues sequence of messages/rules of interaction Center to center standards Address traffic management in a regional context Freeways & Surface streets Transit, traveler information Emergency services and incident management How to exchange that information protocols Dialogues 6

Center to Field (C2F) Standards The primary domain of NTCIP National Transportation Communications for ITS Protocol 7

So... Where do you start? ITS Devices Identify their operations Display a message Run a timing pattern Identify their operational status Working normally Running Plan X; displaying message Y Identify their configuration Number of lines (DMS) Number of Phases (traffic controller) Identify the fundamental data collected Volume and occupancy 8

Data elements (or objects) Data elements (words) Smallest entity of information Unambiguous definition Data Element Data Element Data Element Each element manages an operation (command), identifies a parameter, status, device configuration, etc. 9

Data Element Data element is structured based on the ASN.1 standard (Example from NTCIP 1202 for Actuated Traffic Controllers) phasewalk OBJECT TYPE SYNTAX INTEGER (0..255) ACCESS STATUS read write mandatory DESCRIPTION "Phase Walk Parameter in seconds (0 255 sec). This shall control the amount of time the Walk indication shall be displayed. " ::= { phaseentry 8 } 10

NTCIP Information/Device Level Interface Standards NTCIP 1201 NTCIP 1202 NTCIP 1203 NTCIP 1204 NTCIP 1205 NTCIP 1207 Global Object Definitions Actuated Traffic Signal Controller (ASC) Dynamic Message Signs (DMS) Environmental Sensor Systems (ESS) Closed Circuit Television (CCTV) Ramp Meter Control (RMC) WWW.NTCIP.ORG By the way these are free (DNLD) 11

Additional NTCIP Device Interface Standards NTCIP 1206 Data collection and monitoring DCM (Dev) NTCIP 1208 Video Switches (RS) NTCIP 1209 Transportation Sensor Systems TSS (UCD) NTCIP 1210 Elements for Field Masters FM (UCD) NTCIP 1211 Signal Control Priority SCP (RS) NTCIP 1213 Electrical Lighting Management Systems (RS) ELMS Future may consider UPS (Battery backup supply) and CMU (cabinet monitoring unit) 12

How to use the standards Identify the operations, data, etc. you need Scheduler Etc. Identify the value ranges Number of timing plans? Fonts to be supported? Size of queues Review the standards Develop the MIB or Protocol Requirements List Management Information Base 13

Develop Management Information Base (MIB) To comply with NTCIP, mandatory object Must be Required Mandatory Objects User Must Specify Optional Needs Optional Objects MIB 14

Agency/Vendor Specific Extensions Vendor specific objects must be delivered in ASN.1 standardized format functionality must be defined Agency specific objects must be specified in ASN.1 and functionality must be defined Vendor specific CAUTION! This approach may add hidden costs, risks, complexity during system integration, and higher maintenance for proprietary features MIB objects Make the MIB public! 15

C2F Protocols The rules for exchanging the data 16

ITS Standards Framework NTCIP Levels Data dictionaries and message sets Information Level NTCIP 12XX Standard Protocol Application Level NTCIP 2301 AP STMF NTCIP 2302 AP TFTP NTCIP 2303 AP FTP NTCIP 1103 TMP Can be the same for both center tocenter and center to field Transport Level Subnetwork Level NTCIP 2201 PT NULL TT NTCIP 2202 TP INTERNET NTCIP 2101 SP PMPP/RS 232 NTCIP 2102 SP PMPP/FSK NTCIP 2103 SP PPP/RS232 NTCIP 2104 SP Ethernet 17

Status of Profile Standards These standards support data transmission NTCIP 2101 SP PMPP/RS232 NTCIP 2102 SP SP PMPP/FSK NTCIP 2103 SP PPP/RS232 NTCIP 2104 SP Ethernet NTCIP 2201 PT NULL NTCIP 2202 TP INTERNET NTCIP 2301 AP STMF NTCIP 2302 AP TFTP NTCIP 2303 AP FTP NTCIP 2304 AP DATEX NTCIP 2306 AP C2C XML Published Published Completed Published Published Published Published Published Published Published (ISO) Completed C2C 18

Additional Considerations for C2F Basic Standards (NTCIP 2301) req. SNMP Simple Network Management Protocol SET/GET/GET NEXT Wireless media NTCIP 1103 and traps Slow speed media Consider STMP Simple Transportation Management Protocol Recently developed SFMP Simple Fixed Message Protocol not yet deployed Talk to your vendors Buyer beware 19

Current Status of Deployment Global objects 1201 recently updated for DST DMS everyone uses 1203 ASC 1202 works beware of vendor ½ truth s ESS 1204 works STMP only for ASC SNMP everyone supports CCTV some deployment 20

Center to center (C2C) Mission critical for Regional Integration 21

The Detailed Standards Data content and messages Traffic Management Data Dictionary (TMDD ITE (www.ite.org/tmdd) IEEE Incident Management (IEEE 1512) Traveler Information (SAE J2354) Protocols for exchange DATEX XML/SOAP 22

Domain of ITS C2C Standards Center System System Interface C2C Standards Message In Message Out Message In Message Out Standards only standardize the messages and data elements Standards only standardize the interface to the system, not the system functions Standards were developed at the national level and may include information that local systems will not use Standards may need to be supplemented with additional information (to meet local needs) 23

The C2C Development Process Concept of Operations Functional Requirements Data Elements Required Message Sets Required Dialogs for the Exchanges Why we want our systems to communicate User Needs The system interaction requirements to meet needs Information content Standards TMDD, IM, ATIS, Etc. Protocol Rules or how to exchange the information 24

TMDD C2C Supported Operations TMDD identifies the operational needs (from the concept of operations) Manage assets and other entities Manage information Monitor status Control devices 25

High Level Requirements The concept of operations is translated into detailed functional requirements Example to support remote sharing of DMS: DMS inventory information #lines, type/technology, location, etc. DMS status information DMS control requests: Display message request Cancel message request Provide message library contents Responses to a DMS request 26

Message Sets in the TMDD ADMINISTRATIVE MESSAGES SECURITY MESSAGES EVENT MESSAGES DEVICE MESSAGES CCTV MESSAGES DMS MESSAGES ESS MESSAGES GATE CONTROL MESSAGES HIGHWAY ADVISORY RADIO (HAR) MESSAGES LANE CONTROL SIGNALS (LCS) MESSAGES RAMP METER MESSAGES TRAFFIC SIGNAL CONTROL MESSAGES TRAFFIC NETWORK DATA MESSAGES TRAFFIC DETECTOR MESSAGES VIDEO SWITCH (VS) MESSAGES 27

TMDD Future Directions Next Update of TMDD standard (V3) Add dialogs for each operational concept Correct current inconsistencies Support for Weather information Support for Archive Data Services Includes feedback received from deployments Include WSDL Web site www.ite.org/tmdd 28

Incident Management IEEE 1512 Emergency Management Center Data Elements and Message Sets 29

IEEE 1512 Emergency Management Center Addresses the exchange of data about transportation related incidents among emergency management centers through common incident management message sets Available from IEEE and they are NOT free 30

IEEE 1512 Is A Family Of Standards 1512 1512a Emergency Management Data Dictionary (EMDD) Base Standard 1512.1 Traffic Incident Management Messages Sets 1512.2 Public Safety Incident Management Message Sets 1512.3 Hazardous Material Incident Management Message Sets 1512a Emergency Management Data Dictionary (EMDD) 1 2 3 Traffic Public Safety Hazmat Disaster Management (Forthcoming) Implementation Guide (Forthcoming) Future Volumes Incident Management Base Standard 31

Advanced Traveler Information Functional Area ATIS Data Elements and Messages SAE J2354 These are NOT free but V2 is out for review NOW 32

Goal: Provide Interoperable Exchange of Traveler Information Inter organizational exchange of traveler information: Between agencies within a state Between states Between gov t agencies and private sector Easy re use, automated processing (for different applications, devices, and transmission media) Feeds to 511 systems 33

Current SAE ATIS Standards Information flow from Centers to Travelers Standards Data Dictionary (J2354) Message Set (J2354) Mayday (J2313) Reduced Bandwidth (J2369) 34

Types of Information in ATIS Information Response Events Incidents Road/Link Information Weather Itineraries (driving and/or transit) Flights Parking 35

Status of SAE ATIS Standards Current effort: Maintenance revision of current standards Incorporate lessons learned from deployed services Harmonize with Traffic Management Data Dictionary Ensure stability of core elements Expand basic XML message content to full Web Services model (subscribe/publish, request reply, etc.) 36

Center to Center ITS Standards Center to center (C2C) Protocols Rules for data exchange 37

C2C Standards Efforts There are currently two ITS standards based approaches: DATEX XML Fixed Messaging Approach Web Services Messaging Approach Note: CORBA has been abandoned for C2C 38

DATEX ASN.1 DATa EXchange is a fixed message based protocol Based on ISO standards (14827 1 & 2) Has been adopted as an international standard Fixed messages are known to both TMC Both TMCs make connection & deploy common protocol DATEX TMC 39

NTCIP 2306 Web Services Description, XML Encoding, and Transport Encoding XML SOAP Transport FTP GET HTTP POST and GET Dialogs One Way = Supports Bulk Data Transfer (file retrieval by name) Request Response Subscription Publication Simple Complex 40

XMLDirect Approach (NTCIP 2306) XML Direct is an NTCIP C2CXML concept. Extends WSDL to support a file sharing based approach for information exchange. Useful for bulk data transfer and simple posting of files on a web server. Files contain XML content Is implemented using FTP and HTTP and is useful for very loosely coupled systems 41

C2C using web services Example Web Service Function: Share DMS Inventory Message Input DMS Inventory Request Message Output DMS Inventory Message Encoding SOAP Message Transport HTTP Operation: Manage DMS Inventory Request Local Center System DMS DMS Manage DMS Inventory Request System Interface DMS Inventory Request DMS Inventory Response 42

Where do I get more information for the C2C Standards? 43

Where To Find The Standards? IEEE 1512 and SAE J2354 XML schemas are available from the ITS Standards Forum web site at http://www.itsstandards.org/bb/index.php Once there, click on XML Schemas at the top of the page. TMDD From the ITE web site at http://www.ite.org/tmdd/ NTCIP 2306 From the NTCIP web site at http://www.ntcip.org Once there, click on Library and then Document Links at the top of the page. Select 2306 from the list. TCIP From the APTA web site at http://www.apta.com/about/committees/rsrchtec/tcip/index.cfm 44

Advanced Traffic Controller Standards ATC 45

ATC Family of Standards Controller 2070 ATC 5.2b Cabinet (ITS Cabinet) Application Programming Interface (API) 46

Controller, 2070 ATC 2070 v01.05 Drafts Standards STILL undergoing revisions Supports VME (Versa Module Eurpoa) Expansion Bus NEMA Interface adaptor (optional) Various versions most common 2070L Over 30,000 units deployed www.ite.org/standards Serious Problems: Under powered Ethernet or clock Power interruption 47

Controller, ATC ATC Standard v5.2b Standardized input / output architecture interfaces, connectors, etc. Interchangeable engine board The only internally interchangeable component Portable software with a standard API and operating system (Linux) 48

Controller, ATC Engine Board 2070 HOST CARD NEMA HOST CARD RAM EPROM RTC CPU DUART SERIAL I/O ATC ENGINE BOARD 49

Cabinet ITS Cabinet Similar to TS2 Serial interfaces to all devices Cabinet monitoring is 2 units Revised version is being deployed in Harris County, TX 50

ITS Cabinet Subsystems Input Assembly Detectors Output Assembly Load Switches Flash Transfer Relays Power Distribution Assembly Modular Buses Power & Data Cabinet Monitoring System CMU & AMU Cabinet Communications System SIU & 3 serial buses Power Bus ATC Controller Input Assembly Output Assembly Power Dist Assembly AMU SIU SIU CMU Data Bus 51

Cabinet Monitoring System CMU/AMU replaces the classic MMU/210/2010 AMU provides most of the monitoring functions CMU provides control of the over ride functions Datake is used to program the CMU ATC SB #1 CMU SB #3 AMU Output File AMU Output File 52

Application Programming Interface ATC required Linux 2.6+ (Board Support Package BSP defined in ATC 5.2b) API not designed to run on OS9 (Old 2070) API focused on support for multiple applications Shared user interface Shared I/O functions 53

ATC Software Organization USER DEVELOPER OPERATIONAL USER USER LAYER INTERFACE AND BEHAVIOR DEFINED BY API STANDARD API SOFTWARE APPLICATION SW APPLICATION LAYER API SOFTWARE LAYER LINUX DEVICE DRIVERS LINUX KERNEL ATC DEVICE DRIVERS ATC BOARD SUPPORT PACKAGE LAYER HARDWARE LAYER 54

DSRC Dedicated Short Range Communications Vehicle to/from roadside 55

Dedicated Short Range Communications (DSRC) First there is no standard for tolling systems IAG consortium proprietary technology Proprietary most of the country Title 21 CALTRANS 56

Future Directions Driven by the deployment of the Vehicle Infrastructure Integration (VII) program Combine other in vehicle applications with tolling applications Probes SAE Developing J2735 RSE Vehicle Cooperative Intersection Collision Avoidance (CICAS) Tests underway now include a tolling application 57

DSRC Dedicated Short Range Communications Basis for VII IEEE 802.11p finalized 1609.1 Resource manager 1609.2 Security 1609.3 Network Layer 1609.4 MAC layer Testing and verification with POC DTW 58

Summary The ITS standards work! You have to know how to use them Proprietary MIB s defeat the purpose of the standard They have been widely deployed for some devices Some are still changing (DMS, TSS, DCM, Global) Testing is time consuming Beware the ATC understand what you are specifying and interchangeability is not there yet! 59

Questions Read the NTCIP Guide Document: 9001 60