National Transportation Communications for Intelligent Transportation System Protocol

Last updated December 16, 2023

The National Transportation Communications for Intelligent Transportation System Protocol (NTCIP) is a family of standards designed to achieve interoperability and interchangeability between computers and electronic traffic control equipment from different manufacturers.

NTCIP has been around for over 20 years, but is increasingly in use in smart city initiatives and by suppliers of technology. For example, riders who want to know where the next bus will arrive at their stop are using apps that use NTCIP, such as in the Siemens initiatives in Seattle and elsewhere.^[1] In the future, NTCIP will be used for two way communication between vehicles and traffic signals, such as the ability for buses to control traffic lights as done by SinWaves.^[2]

The protocol is the product of a joint standardization project guided by the Joint Committee on the NTCIP, which is composed of six representatives each from the National Electrical Manufacturers Association (NEMA), the American Association of State Highway and Transportation Officials (AASHTO), and the Institute of Transportation Engineers (ITE). The Joint Committee has in turn formed 14 technical working groups to develop and maintain the standards, and has initiated or produced over 50 standards and information reports.^[3]

The project receives funding under a contract with the United States Department of Transportation (USDOT) and is part of a wider effort to develop a comprehensive family of intelligent transportation system (ITS) standards.^[4]

History of the NTCIP Development

NEMA initiated the development of the NTCIP in 1992. In early 1993, the US Federal Highway Administration (FHWA) brought together transportation industry representatives to discuss obstacles to installing field equipment for new Intelligent Transportation Systems (ITS). The representatives said that the number one priority was the need for an industry-wide standard data communications protocol. Since the NEMA Transportation Section members had already started work on a new industry standard, they offered to expedite and expand the scope of their activities.

The key objectives of the new NTCIP protocol were the interchangeability of similar roadside devices, and the interoperability of different types of devices on the same communications channel.

In 1996, the FHWA suggested a partnership of standards developing organizations to expand both user and industry involvement. AASHTO and ITE signed an agreement with NEMA to establish the Joint Committee on the NTCIP, and to work together on developing and maintaining the NTCIP standards.^[3]

NTCIP Communications Standards

Center to Field Device Communications

NTCIP has enabled the center to field communication and command/control of equipment from different manufacturers to be specified, procured, deployed, and tested. NTCIP communications standards for field devices are listed below: (the corresponding NTCIP document number is shown in parentheses):^[5]

Traffic signals (NTCIP 1202)
Dynamic message signs (NTCIP 1203)
Environmental sensor stations (NTCIP 1204)
Closed circuit television cameras (NTCIP 1205)
Vehicle count stations (NTCIP 1206)
Freeway ramp meters (NTCIP 1207)
Video switches (NTCIP 1208)
Transportation sensor systems (NTCIP 1209)
Field master stations for traffic signals (NTCIP 1210)
Transit priority at traffic signals (NTCIP 1211)
Street lights (NTCIP 1213)

Center to Center Communications

Center to center (C2C) communication involves peer-to-peer communications between computers involved in information exchange in real-time transportation management in a many-to-many network. This type of communication is similar to the Internet, in that any center can request information from, or provide information to, any number of other centers.

An example of center to center communications is two traffic management centers that exchange real-time information about the inventory and status of traffic control devices. This allows each center system to know what timing plan, for example, the other center system is running to allow traffic signal coordination across center geographic boundaries. Other examples of this type of communication include:^[5]

Two or more traffic signal systems exchanging information (including second-by-second status changes) to achieve coordinated operation of traffic signals managed by the different systems and to enable personnel at one center to monitor the status of signals operated from another center;
A transit system reporting schedule adherence exceptions to a transit customer information system and to a regional traveler information system, while also asking a traffic signal management system to instruct its signals to give priority to a behind-schedule transit vehicle;
An emergency management system reporting an incident to a freeway management system, to a traffic signal management system, to two transit management systems and to a traveler information system;
A freeway management system informing an emergency management system of a warning message just posted on a dynamic message sign on the freeway in response to its notification of an incident; and
A weather monitoring system (environmental sensors) informing a freeway management system of ice forming on the roadway so that the freeway management system is able to post warning messages on dynamic message signs as appropriate.

NTCIP communications standards for center to center communications are listed below: (the corresponding NTCIP document number is shown in parentheses):^[5]

Data Exchange - DATEX-ASN (NTCIP 2304)
Web Services - XML (NTCIP 2306)

The NTCIP has coordinated with other information level standards development organizations during development of the center-to-center application profiles and supports the: ITE Traffic Management Data Dictionary (ITE TMDD), IEEE 1512 Incident Management (IEEE 1512), APTA Transit Communications Interface Profiles (APTA TCIP), and SAE J2354 Advanced Traveler Information Systems standards.

NTCIP Standards Framework

The NTCIP Framework is based primarily on the open standards of the Internet Engineering Task Force (IETF), World Wide Web Consortium (W3C), and ISO, plus NTCIP data dictionary standards specific for the task of ITS device communications. A layered, or modular, approach to communications standards, is used to represent data communications between two computers or other electronic devices.

NTCIP refers to “levels” in NTCIP, rather than “layers” to distinguish the hierarchical architecture applied from those defined by the Open System Interconnection Reference Model (OSI Model) of ISO and the Internet Engineering Task Force (IETF). The five NTCIP levels are: information level, application level, transport level, subnetwork level, and plant level.^[5]

The figure below (used with permission) shows the structure of the NTCIP Information, Application, Transport, Subnetwork, and Plant Levels.

To ensure a working system, deployers should select and specify at least one NTCIP protocol or profile at each level. A discussion of each level, and NTCIP standards that apply at that level, follows:^[5]

NTCIP Information Level — Information standards define the meaning of data and messages and generally deal with ITS information (rather than information about the communications network). This is similar to defining a dictionary and phrase list within a language. These standards are above the traditional ISO seven-layer OSI model. Information level standards represent the functionality of the system to be implemented.
NTCIP Application Level — Application standards define the rules and procedures for exchanging information data. The rules may include definitions of proper grammar and syntax of a single statement, as well as the sequence of allowed statements. This is similar to combining words and phrases to form a sentence, or a complete thought, and defining the rules for greeting each other and exchanging information. These standards are roughly equivalent to the Session, Presentation and Application Layers of the OSI model.
NTCIP Transport Level — Transport standards define the rules and procedures for exchanging the Application data between point 'A' and point 'X' on a network, including any necessary routing, message disassembly/re-assembly and network management functions. This is similar to the rules and procedures used by the telephone company to connect two remotely located telephones. Transportation level standards are roughly equivalent to the Transport and Network Layers of the OSI model.
NTCIP Subnetwork Level — Subnetwork standards define the rules and procedures for exchanging data between two 'adjacent' devices over some communications media. This is equivalent to the rules used by the telephone company to exchange data over a cellular link versus the rules used to exchange data over a twisted pair copper wire. These standards are roughly equivalent to the Data Link and Physical Layers of the OSI model.
NTCIP Plant Level — The Plant Level is shown in the NTCIP Framework only as a means of providing a point of reference to those learning about NTCIP. The Plant Level includes the communications infrastructure over which NTCIP communications standards are to be used and has a direct impact on the selection of an appropriate Subnetwork Level for use over the selected communications infrastructure. The NTCIP standards do not prescribe any one media type over another. In most cases, communications media selections are made early in the design phase.

The NTCIP Framework does not preclude combinations beyond those expressly indicated on the diagram.

Related Research Articles

The Internet Control Message Protocol (ICMP) is a supporting protocol in the Internet protocol suite. It is used by network devices, including routers, to send error messages and operational information indicating success or failure when communicating with another IP address, for example, an error is indicated when a requested service is not available or that a host or router could not be reached. ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to exchange data between systems, nor is it regularly employed by end-user network applications.

IEEE 802.2 is the original name of the ISO/IEC 8802-2 standard which defines logical link control (LLC) as the upper portion of the data link layer of the OSI Model. The original standard developed by the Institute of Electrical and Electronics Engineers (IEEE) in collaboration with the American National Standards Institute (ANSI) was adopted by the International Organization for Standardization (ISO) in 1998, but it remains an integral part of the family of IEEE 802 standards for local and metropolitan networks.

The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the set of communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP). Early versions of this networking model were known as the Department of Defense (DoD) model because the research and development were funded by the United States Department of Defense through DARPA.

<span class="mw-page-title-main">OSI model</span> Model of communication of seven abstraction layers

The Open Systems Interconnection model is a conceptual model from the International Organization for Standardization (ISO) that "provides a common basis for the coordination of standards development for the purpose of systems interconnection." In the OSI reference model, the communications between systems are split into seven different abstraction layers: Physical, Data Link, Network, Transport, Session, Presentation, and Application.

The protocol stack or network stack is an implementation of a computer networking protocol suite or protocol family. Some of these terms are used interchangeably but strictly speaking, the suite is the definition of the communication protocols, and the stack is the software implementation of them.

Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) are standardized protocols that transfer multiple digital bit streams synchronously over optical fiber using lasers or highly coherent light from light-emitting diodes (LEDs). At low transmission rates data can also be transferred via an electrical interface. The method was developed to replace the plesiochronous digital hierarchy (PDH) system for transporting large amounts of telephone calls and data traffic over the same fiber without the problems of synchronization.

Simple Network Management Protocol (SNMP) is an Internet Standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behavior. Devices that typically support SNMP include cable modems, routers, switches, servers, workstations, printers, and more.

The Infrared Data Association (IrDA) is an industry-driven interest group that was founded in 1994 by around 50 companies. IrDA provides specifications for a complete set of protocols for wireless infrared communications, and the name "IrDA" also refers to that set of protocols. The main reason for using the IrDA protocols had been wireless data transfer over the "last one meter" using point-and-shoot principles. Thus, it has been implemented in portable devices such as mobile telephones, laptops, cameras, printers, and medical devices. The main characteristics of this kind of wireless optical communication are physically secure data transfer, line-of-sight (LOS) and very low bit error rate (BER) that makes it very efficient.

In the seven-layer OSI model of computer networking, the network layer is layer 3. The network layer is responsible for packet forwarding including routing through intermediate routers.

An application layer is an abstraction layer that specifies the shared communication protocols and interface methods used by hosts in a communications network. An application layer abstraction is specified in both the Internet Protocol Suite (TCP/IP) and the OSI model. Although both models use the same term for their respective highest-level layer, the detailed definitions and purposes are different.

IEEE 802.15.4 is a technical standard which defines the operation of a low-rate wireless personal area network (LR-WPAN). It specifies the physical layer and media access control for LR-WPANs, and is maintained by the IEEE 802.15 working group, which defined the standard in 2003. It is the basis for the Zigbee, ISA100.11a, WirelessHART, MiWi, 6LoWPAN, Thread, Matter and SNAP specifications, each of which further extends the standard by developing the upper layers which are not defined in IEEE 802.15.4. In particular, 6LoWPAN defines a binding for the IPv6 version of the Internet Protocol (IP) over WPANs, and is itself used by upper layers like Thread.

Internet security is a branch of computer security. It encompasses the Internet, browser security, web site security, and network security as it applies to other applications or operating systems as a whole. Its objective is to establish rules and measures to use against attacks over the Internet. The Internet is an inherently insecure channel for information exchange, with high risk of intrusion or fraud, such as phishing, online viruses, trojans, ransomware and worms.

Dedicated short-range communications (DSRC) is a technology for direct wireless exchange of vehicle-to-everything (V2X) and other intelligent transportation systems (ITS) data between vehicles, other road users, and roadside infrastructure. DSRC, which can be used for both one- and two-way data exchanges, uses channels in the licensed 5.9 GHz band. DSRC is based on IEEE 802.11p.

The Open Systems Interconnection protocols are a family of information exchange standards developed jointly by the ISO and the ITU-T. The standardization process began in 1977.

Manufacturing Message Specification (MMS) is an international standard dealing with messaging systems for transferring real time process data and supervisory control information between networked devices or computer applications. The standard is developed and maintained by the ISO Technical Committee 184 (TC184). MMS defines the following

Profinet is an industry technical standard for data communication over Industrial Ethernet, designed for collecting data from, and controlling equipment in industrial systems, with a particular strength in delivering data under tight time constraints. The standard is maintained and supported by Profibus and Profinet International, an umbrella organization headquartered in Karlsruhe, Germany.

A computer network is a set of computers sharing resources located on or provided by network nodes. Computers use common communication protocols over digital interconnections to communicate with each other. These interconnections are made up of telecommunication network technologies based on physically wired, optical, and wireless radio-frequency methods that may be arranged in a variety of network topologies.

Stream Reservation Protocol (SRP) is an enhancement to Ethernet that implements admission control. In September 2010 SRP was standardized as IEEE 802.1Qat which has subsequently been incorporated into IEEE 802.1Q-2011. SRP defines the concept of streams at layer 2 of the OSI model. Also provided is a mechanism for end-to-end management of the streams' resources, to guarantee quality of service (QoS).

The VHF Data Link or VHF Digital Link (VDL) is a means of sending information between aircraft and ground stations. Aeronautical VHF data links use the band 117.975–137 MHz assigned by the International Telecommunication Union to Aeronautical mobile (R) service. There are ARINC standards for ACARS on VHF and other data links installed on approximately 14,000 aircraft and a range of ICAO standards defined by the Aeronautical Mobile Communications Panel (AMCP) in the 1990s. Mode 2 is the only VDL mode being implemented operationally to support Controller Pilot Data Link Communications (CPDLC).

A long-running debate in computer science known as the Protocol Wars occurred from the 1970s to the 1990s, when engineers, organizations and nations became polarized over the issue of which communication protocol would result in the best and most robust computer networks. This culminated in the Internet–OSI Standards War in the 1980s and early 1990s, which was ultimately "won" by the Internet protocol suite (TCP/IP) by the mid-1990s and has since resulted in most other protocols disappearing.

References

↑ "Shaping connected mobility".
↑ "Home". sinwaves.com.
1 2 NEMA - NTCIP
↑ US Department of Transportation ITS Standards Program
1 2 3 4 5 The NTCIP Guide

External links

NTCIP (Official website)
The NTCIP Guide (NTCIP 9001 v04)
Testing Guide for NTCIP Center-to-Field Communications (NTCIP 9012 v01)
US Department of Transportation ITS Standards Program (USDOT)
National Electrical Manufacturers Association (NEMA)
American Association of State Highway and Transportation Officials (AASHTO)
Institute of Transportation Engineers (ITE)

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.

[ITS-1] "Shaping connected mobility".

[SinWaves-2] "Home". sinwaves.com.

[history-3] 1 2 NEMA - NTCIP

[usdot-4] US Department of Transportation ITS Standards Program

[ntcip-guide-5] 1 2 3 4 5 The NTCIP Guide

[1]

[2]

[3]

[4]

[5]