Cart
0
Product
Products
(empty)
No products
To be determined
Shipping
$0.00
Total
Product successfully added to your shopping cart
Quantity
Total
There are 0 items in your cart.
There is 1 item in your cart.
Total products
Total shipping
To be determined
Total
Sale!
View larger
View larger
NTCIP 1211
New product
NTCIP 1211 2014 Edition, September 1, 2014 National Transportation Communications for ITS Protocol Object Definitions for Signal Control and Prioritization (SCP)
More info
Description / Abstract:
The scope of NTCIP 1211 v02 is the definition of management
information and the operations related to Signal Control and
Prioritization (SCP). It covers the management of preferential
treatment (priority) of different classes of vehicles (such as
transit, emergency service, other priority vehicles, which might
include commercial fleet vehicles, etc.) and the implementation of
special coordination operation within a Traffic Signal Controller.
To affect a priority request, its scope includes the content of
messages to be exchanged between a prioritizing entity and a
controller, the sequence in which messages are exchanged, and
associated functions within a controller related to SCP. The scope
includes the configuration and monitoring of a prioritizing entity
and those aspects of coordination that relate to SCP. The process
of generating priority requests is not defined by NTCIP 1211
v02.
NTCIP 1211 v02 deals, primarily, with granting priority while still maintaining coordination with adjacent intersections. The functionality expressed here is intended to work in conjunction with the coordination object definitions and functions as defined in NTCIP 1202. The coordination objects and functions can also be invoked when an intersection is operating in a non-coordinated mode.
Granting absolute priority irrespective of coordination is considered pre-emption and is covered in NTCIP 1202:2005. The process of generating a priority request is also not covered here. For transit vehicles, this process is defined in the American Public Transportation Association's (APTA) Transit Communications Interface Profiles (TCIP) standard.
The remainder of NTCIP 1211 v02 provides the following main sections, each building on the previous section(s):
a) Concept of Operations – This section provides a description of user needs (needs for features and needs related to the operational environment) applicable to SCP.
b) Functional Requirements – This section defines the functional requirements that address the user needs identified in the Concept of Operations. It includes a Protocol Requirements List (PRL) Table that defines conformance requirements thereby allowing users to select the desired options for a particular project.
c) Dialogs – This section describes how functional requirements that require more complex implementations are fulfilled. The dialogs define the standardized procedure for a management station to manage a device and define the responses expected by the device.
d) Management Information Base (MIB) – This section defines the data exchanged during communications (an update of NTCIP 1211 v01 Sections 3 and 4)
e) Requirements Traceability Matrix – This annex provides a table that associates each requirement to a dialog, an interface, and its associated list of objects.
f) Test Procedures – This annex is a placeholder for future test procedures, which ensure that a requirement is met and is validated.
The first two of these sections are presented at a high level and areof interest to most readers of NTCIP 1211 v02; the later sections entail more detailed design issues that are of interest to implementers, integrators, and testers.
Additional annexes provide information on certain topics such as changes between NTCIP 1211 v01 and NTCIP 1211 v02, and the Generic SNMP Interface description.
NTCIP 1211 v02 deals, primarily, with granting priority while still maintaining coordination with adjacent intersections. The functionality expressed here is intended to work in conjunction with the coordination object definitions and functions as defined in NTCIP 1202. The coordination objects and functions can also be invoked when an intersection is operating in a non-coordinated mode.
Granting absolute priority irrespective of coordination is considered pre-emption and is covered in NTCIP 1202:2005. The process of generating a priority request is also not covered here. For transit vehicles, this process is defined in the American Public Transportation Association's (APTA) Transit Communications Interface Profiles (TCIP) standard.
The remainder of NTCIP 1211 v02 provides the following main sections, each building on the previous section(s):
a) Concept of Operations – This section provides a description of user needs (needs for features and needs related to the operational environment) applicable to SCP.
b) Functional Requirements – This section defines the functional requirements that address the user needs identified in the Concept of Operations. It includes a Protocol Requirements List (PRL) Table that defines conformance requirements thereby allowing users to select the desired options for a particular project.
c) Dialogs – This section describes how functional requirements that require more complex implementations are fulfilled. The dialogs define the standardized procedure for a management station to manage a device and define the responses expected by the device.
d) Management Information Base (MIB) – This section defines the data exchanged during communications (an update of NTCIP 1211 v01 Sections 3 and 4)
e) Requirements Traceability Matrix – This annex provides a table that associates each requirement to a dialog, an interface, and its associated list of objects.
f) Test Procedures – This annex is a placeholder for future test procedures, which ensure that a requirement is met and is validated.
The first two of these sections are presented at a high level and areof interest to most readers of NTCIP 1211 v02; the later sections entail more detailed design issues that are of interest to implementers, integrators, and testers.
Additional annexes provide information on certain topics such as changes between NTCIP 1211 v01 and NTCIP 1211 v02, and the Generic SNMP Interface description.