ITS Standards for Dummies

ITS Standards for Dummies 

ITS Georgia

Celebrating ten years of ITS!

Session 5 

Tuesday October 2, 2007  Bob Rausch, P.E. 

ITS Standards Are Really Quite Simple ! 

uCenter­to­field standards describe ­ 

l Management of the parameters that govern a device’s 

operation, monitor its status, collect data 

l How to exchange that information – protocols 

l Dialogues – sequence of messages/rules of interaction 

Center­to­Field (C2F) Standards 

The primary domain of NTCIP

National Transportation Communications 

phaseWalk OBJECT­TYPE SYNTAX INTEGER (0..255) ACCESS read­write

STATUS mandatory

DESCRIPTION "Phase Walk Parameter in seconds (0­255 sec). This shall control the amount of time the Walk indication shall be displayed. "

Data Element 

uData element  is structured based on the 

ASN.1 standard 

NTCIP Information/Device Level Interface Standards 

u NTCIP 1201 Global Object Definitions

u NTCIP 1202 Actuated Traffic Signal Controller (ASC) u NTCIP 1203 Dynamic Message Signs (DMS)

u NTCIP 1204 Environmental Sensor Systems (ESS) u NTCIP 1205  Closed Circuit Television (CCTV) 

u NTCIP 1207 Ramp Meter Control (RMC)

WWW.NTCIP.ORG 

Additional NTCIP Device Interface Standards 

u NTCIP 1206 – Data collection and monitoring ­ DCM ­(Dev)  u NTCIP 1208 – Video Switches (RS) 

u NTCIP 1209 – Transportation Sensor Systems – TSS ­(UCD)  u NTCIP 1210 – Elements for Field Masters – FM ­ (UCD) 

u NTCIP 1211 – Signal Control Priority – SCP ­ (RS) 

u NTCIP 1213 – Electrical Lighting Management Systems (RS) 

ELMS 

Develop Management Information Base (MIB)

To comply with NTCIP,

mandatory object Must be Required

Status of Profile Standards 

u NTCIP 2101­SP­PMPP/RS232 Published u NTCIP 2102­SP­SP­PMPP/FSK Published u NTCIP 2103­SP­PPP/RS232 Completed u NTCIP 2104­SP­Ethernet Published u NTCIP 2201­PT­NULL Published u NTCIP 2202­TP­INTERNET Published u NTCIP 2301­AP­STMF Published u NTCIP 2302­AP­TFTP Published u NTCIP 2303­AP­FTP Published

u  NTCIP 2304­AP­DATEX  Published (ISO) 

u  NTCIP 2306­AP­C2C XML  Completed 

These standards support data transmission 

Additional Considerations for C2F 

uBasic Standards (NTCIP 2301) req. SNMP – Simple Network Management Protocol

l SET/GET/GET NEXT

uWireless media

l NTCIP 1103 and traps

uSlow speed media

l Consider STMP ­ Simple Transportation Management Protocol

uRecently developed SFMP ­ Simple Fixed Message Protocol – not yet deployed

Talk to your  vendors 

Current Status of Deployment 

uGlobal objects – 1201 recently updated for DST 

uDMS – everyone uses 1203 

uASC – 1202 works – beware of vendor ½ truth’s 

uESS – 1204 works 

uSTMP – only for ASC 

uSNMP – everyone supports 

Center­to­center (C2C) 

Domain of ITS C2C Standards  Center  System  Message In  Message Out  Message In  Message Out  C2C  S tand a rds  S y s te m  In te rfac e 

u Standards only standardize the

messages and data elements

u Standards only standardize the interface to the system, not the system functions

u Standards were developed at the national level and may include

information that local systems will not use

u Standards may need to be

The C2C Development Process

Concept of Operations Functional Requirements

Message Sets Required Data Elements Required 

Why we want our systems to  communicate – User Needs 

The system interaction 

requirements to meet needs

Dialogs for the Exchanges

Protocol 

Information content  Standards 

TMDD, IM, ATIS, Etc. 

TMDD C2C Supported Operations 

uTMDD identifies the operational needs (from

the concept of operations)

l

Manage assets and other entities 

Manage information

High Level Requirements 

The concept of operations is translated into detailed 

Message Sets in the TMDD  u ADMINISTRATIVE MESSAGES u  SECURITY MESSAGES  u EVENT MESSAGES u DEVICE MESSAGES u CCTV MESSAGES u DMS MESSAGES u ESS MESSAGES

u GATE CONTROL MESSAGES

u HIGHWAY ADVISORY RADIO (HAR) MESSAGES u LANE CONTROL SIGNALS (LCS) MESSAGES u RAMP METER MESSAGES

u TRAFFIC SIGNAL CONTROL MESSAGES u TRAFFIC NETWORK DATA MESSAGES u TRAFFIC DETECTOR MESSAGES

Incident Management 

IEEE 1512 

IEEE 1512  Emergency Management Center  uAddresses the exchange of data about  transportation­related incidents among  emergency management centers through  common incident management message sets 

Advanced Traveler Information  Functional Area

ATIS Data Elements and Messages SAE J2354

Goal: Provide Interoperable Exchange  of Traveler Information 

u  Inter­organizational exchange of traveler information: 

l Between agencies within a state  l Between states 

l Between gov’t agencies and private sector 

Center­to­Center ITS Standards 

Protocols 

Rules for data exchange 

DATEX­ASN.1 

u DATa EXchange  is a fixed message­based protocol  u Based on ISO standards (14827­1 & 2) 

u Has been adopted as an international standard

TMC

TMC

DATEX

Both TMCs make connection & deploy common protocol Fixed messages

NTCIP 2306 – Web Services Description,  XML Encoding, and Transport  u Encoding  l  XML  l  SOAP  u Transport  l  FTP ‘GET’ 

l  HTTP ‘POST’ and ‘GET’ 

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

DMS Inventory  Response  DMS Inventory  Request  C2C using web services  u Example Web Service  l  Function:  uShare DMS Inventory  l  Message Input  uDMS Inventory  Request  l  Message Output  uDMS Inventory  l  Message Encoding  uSOAP  l  Message Transport  Local  Center  System  DMS  Manage  DMS  Inventory  Request

Operation: Manage DMS Inventory Request

Where To Find The Standards? 

u IEEE 1512 and SAE J2354 

l  XML schemas are available from the ITS Standards Forum web 

site at http://www.itsstandards.org/bb/index.php 

l  Once there, click on “XML Schemas” at the top of the page. 

u TMDD 

l  From the ITE web site at http://www.ite.org/tmdd/ 

u NTCIP 2306 

l  From the NTCIP web site at http://www.ntcip.org 

l  Once there, click on “Library” and then “Document Links” at the 

top of the page. 

l  Select 2306 from the list. 

Controller, ATC  uATC Standard v5.2b  uStandardized input / output architecture  l interfaces, connectors, etc.  uInterchangeable “engine board”  l The only internally interchangeable component 

uPortable software – with a standard API and 

Application Programming Interface 

u

ATC required Linux 2.6+ (Board Support

Package – BSP defined in ATC 5.2b)

u

API not designed to run on OS9 (Old 2070)

u

API focused on support for multiple

applications

DSRC – Dedicated Short Range  Communications 

Dedicated Short Range Communications  (DSRC) 

uFirst – there is no standard for tolling systems 

l IAG – consortium – proprietary technology  l Proprietary most of the country 

Summary 

uThe  ITS standards work! 

uYou have to know how to use them ­ ­ 

uProprietary MIB’s defeat the purpose of the standard 

uThey have been widely deployed for some devices 

uSome are still changing (DMS, TSS, DCM, Global) 

uTesting is time consuming ­ ­ ­ 

uBeware the ATC – understand what you are 

Questions