You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 34.205.0.0/16 has been blocked (disabled) by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 05:44, 30 September 2026.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 05:38, 21 February 2024
- Expiry of block: 05:38, 21 February 2029
Your current IP address is 34.205.92.177. The blocked range is 34.205.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((Multiple issues|
((technical|date=September 2011))
((more citations needed|date=September 2011))
((more footnotes needed|date=September 2011))
))

The '''National Transportation Communications for Intelligent Transportation System Protocol''' ('''NTCIP''') is a family of standards designed to achieve [[interoperability]] and [[interchangeable parts|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.<ref name="ITS">((Cite web|url=https://w3.usa.siemens.com/mobility/us/en/road-solutions/Pages/ITS.aspx|title = Shaping connected mobility))</ref>  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.<ref name="SinWaves">((cite web |url=https://www.sinwaves.com/ |title=Home |website=sinwaves.com))</ref>

The [[Communications protocol|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.<ref name="history">[http://www.nema.org/stds/ntcip.cfm NEMA - NTCIP]</ref>

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.<ref name="usdot">[http://www.standards.its.dot.gov/ US Department of Transportation ITS Standards Program]</ref>

==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.<ref name="history"/>

==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):<ref name="ntcip-guide">[http://www.ntcip.org/library/standards/default.asp?documents=yes&qreport=no&standard=9001 The NTCIP Guide]</ref>  
* Traffic signals [https://www.ntcip.org/wp-content/uploads/2018/11/NTCIP1202v0107d.pdf (NTCIP 1202)]
* Dynamic message signs [https://www.ntcip.org/wp-content/uploads/2018/11/NTCIP1203v02-35a.pdf (NTCIP 1203)]
* Environmental sensor stations [https://www.ntcip.org/wp-content/uploads/2018/11/NTCIP1204v0224r.pdf (NTCIP 1204)]
* Closed circuit television cameras [https://www.ntcip.org/wp-content/uploads/2018/11/NTCIP1205v0108b.pdf (NTCIP 1205)]
* Vehicle count stations [https://www.ntcip.org/wp-content/uploads/2018/11/NTCIP1206v0123f-1.pdf (NTCIP 1206)]
* Freeway ramp meters [https://www.ntcip.org/file/2018/11/NTCIP1207v0214hj.pdf (NTCIP 1207)]
* Video switches [https://www.ntcip.org/file/2018/11/NTCIP1208v0112f.pdf (NTCIP 1208)]
* Transportation sensor systems [https://www.ntcip.org/file/2018/11/NTCIP1209v0218jp.pdf (NTCIP 1209)]
* Field master stations for traffic signals [https://www.ntcip.org/file/2018/11/NTCIP1210v0155r.pdf (NTCIP 1210)]
* Transit priority at traffic signals [https://www.ntcip.org/file/2018/11/NTCIP1211-v0224j.pdf (NTCIP 1211)]
* Street lights [https://www.ntcip.org/file/2018/11/NTCIP1213v02.pdf (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:<ref name="ntcip-guide"/>
* 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):<ref name="ntcip-guide"/>  
* Data Exchange - DATEX-ASN [http://www.ntcip.org/library/standards/default.asp?documents=yes&qreport=no&standard=2304 (NTCIP 2304)]
* Web Services  - XML [http://www.ntcip.org/library/standards/default.asp?documents=yes&qreport=no&standard=2306 (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 [http://www.ite.org/standards/tmdd/ (ITE TMDD)], IEEE 1512 Incident Management [https://web.archive.org/web/20090419201437/http://grouper.ieee.org/groups/scc32/imwg/index.html (IEEE 1512)], APTA Transit Communications Interface Profiles [http://www.aptastandards.com/StandardsPrograms/ITStandardsProgram/TCIPProgram/tabid/113/Default.aspx (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 [[International Organization for Standardization|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 [[International Organization for Standardization|ISO]] and the [[Internet Engineering Task Force]] (IETF). The five NTCIP levels are:  information level, application level, transport level, subnetwork level, and plant level.<ref name="ntcip-guide"/>

The figure below (used with permission) shows the structure of the NTCIP Information, Application, Transport, Subnetwork, and Plant Levels.
[[File:NTCIP Framework.png|thumb|alt=NTCIP Framework. Reprinted from NTCIP 9001 v04 'The NTCIP Guide' by permission of NEMA.|NTCIP Framework.]]

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:<ref name="ntcip-guide"/>

* '''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.

==References==
<references />

==External links==
*[http://www.ntcip.org/ NTCIP] (Official website)
*[http://www.ntcip.org/library/standards/default.asp?documents=yes&qreport=no&standard=9001 The NTCIP Guide] (NTCIP 9001 v04)
*[http://www.ntcip.org/library/standards/default.asp?documents=yes&qreport=no&standard=9012 Testing Guide for NTCIP Center-to-Field Communications] (NTCIP 9012 v01)
*[http://www.standards.its.dot.gov/ US Department of Transportation ITS Standards Program] (USDOT)
*[http://www.nema.org/ National Electrical Manufacturers Association] (NEMA)
*[http://www.transportation.org American Association of State Highway and Transportation Officials] (AASHTO)
*[http://www.ite.org Institute of Transportation Engineers] (ITE)

[[Category:Intelligent transportation systems]]
[[Category:Application layer protocols]]
[[Category:Open standards]]
[[Category:Traffic signals]]

Pages transcluded onto the current version of this page (help):

National Transportation Communications for Intelligent Transportation System Protocol (edit)
Template:Ambox (view source) (template editor protected)
Template:Cite web (view source) (protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:More footnotes needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Technical (view source) (template editor protected)
Template:Yesno (view source) (protected)
Template:Yesno-no (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to National Transportation Communications for Intelligent Transportation System Protocol.

Retrieved from "https://en.wikipedia.org/wiki/National_Transportation_Communications_for_Intelligent_Transportation_System_Protocol"