Status in source: mandatory.
Names: signalStatusBlock
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"signalStatusBlock",
"OBJECT-TYPE",
"SYNTAX",
"OerString",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> An OER encoded string of the signalStatusTable structure as defined below. This object is used for uploading configuration data from the ASC in a bandwidth efficient manner. The following data is repeated for each channel. OPTIONAL fields shall be present only if there are changes in the data values and if the data is supported by the implementation. The OPTIONAL fields shall be omitted for any data that has not changed from a previously transmitted object or not supported by the implementation. signalStatus ::= SEQUENCE { ascCurrentTick.0, -- @NTCIP1202-v03, Bytes 1 & 2 channelData SEQUENCE OF channelSignalData OPTIONAL } channelSignalData ::== SEQUENCE { channelNumber.x -- 1 BYTE @NTCIP1202-v03 signalStatusBitMask.x -- 1 BYTE signalState.x OPTIONAL, -- 1 BYTE @NTCIP1202-v03 signalStateMinEndTick.x OPTIONAL, -- 2 BYTES @NTCIP1202-v03 signalStateMaxEndTick.x OPTIONAL, -- 2 BYTES @NTCIP1202-v03 signalStateLikelyEndTick.x OPTIONAL, -- 2 BYTES @NTCIP1202-v03 signalStateTickConfidence.x OPTIONAL, -- 1 BYTE @NTCIP1202-v03 signalNextTick.x OPTIONAL -- 2 BYTES @NTCIP1202-v03 } where: signalStatusBitMask is a bit mask (INTEGER (0..255)) defining the data that follows in the OerString. When a bit=1, the data is included in the OerString. If a bit=0, the corresponding data is omitted and not in the OER string. Bit 7: Reserved Bit 6: Reserved Bit 5: signalNextTick - reference tick to next green state data is present. Values are 0..36001. 36001 means could not calculate or undefined. Bit 4: signalStateTickConfidence data for this channel is present (1 byte). Bit 3: signalStateLikelyEndTick data for this channel is present (2 bytes). Values are 0..36001. 36001 means could not calculate or undefined. Bit 2: signalStateMaxEndTick data for this channel is present (2 bytes). Values are 0..36001. 36001 means could not calculate or undefined. Bit 1: signalStateMinEndTick data for this channel is present (2 bytes). Values are 0..36001. 36001 means could not calculate or undefined. Bit 0: signalState data for this channel is present (1 byte). <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.8\"",
"::=",
"{",
"spat",
"8",
"}"
],
"syntax_tree": [
[
"row",
"OerString"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> An OER encoded string of the signalStatusTable structure as defined below. This object is used for uploading configuration data from the ASC in a bandwidth efficient manner. The following data is repeated for each channel. OPTIONAL fields shall be present only if there are changes in the data values and if the data is supported by the implementation. The OPTIONAL fields shall be omitted for any data that has not changed from a previously transmitted object or not supported by the implementation. signalStatus ::= SEQUENCE { ascCurrentTick.0, -- @NTCIP1202-v03, Bytes 1 & 2 channelData SEQUENCE OF channelSignalData OPTIONAL } channelSignalData ::== SEQUENCE { channelNumber.x -- 1 BYTE @NTCIP1202-v03 signalStatusBitMask.x -- 1 BYTE signalState.x OPTIONAL, -- 1 BYTE @NTCIP1202-v03 signalStateMinEndTick.x OPTIONAL, -- 2 BYTES @NTCIP1202-v03 signalStateMaxEndTick.x OPTIONAL, -- 2 BYTES @NTCIP1202-v03 signalStateLikelyEndTick.x OPTIONAL, -- 2 BYTES @NTCIP1202-v03 signalStateTickConfidence.x OPTIONAL, -- 1 BYTE @NTCIP1202-v03 signalNextTick.x OPTIONAL -- 2 BYTES @NTCIP1202-v03 } where: signalStatusBitMask is a bit mask (INTEGER (0..255)) defining the data that follows in the OerString. When a bit=1, the data is included in the OerString. If a bit=0, the corresponding data is omitted and not in the OER string. Bit 7: Reserved Bit 6: Reserved Bit 5: signalNextTick - reference tick to next green state data is present. Values are 0..36001. 36001 means could not calculate or undefined. Bit 4: signalStateTickConfidence data for this channel is present (1 byte). Bit 3: signalStateLikelyEndTick data for this channel is present (2 bytes). Values are 0..36001. 36001 means could not calculate or undefined. Bit 2: signalStateMaxEndTick data for this channel is present (2 bytes). Values are 0..36001. 36001 means could not calculate or undefined. Bit 1: signalStateMinEndTick data for this channel is present (2 bytes). Values are 0..36001. 36001 means could not calculate or undefined. Bit 0: signalState data for this channel is present (1 byte). <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.8"
],
null,
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF
· Official record
Module: NTCIP1217-v01
See published definition above
Module imports
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['Devices', 'OerString'], 'NTCIP1202-v03': ['channelNumber']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of devices. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP-1202v0328A.pdf — NTCIP1217-v01 (MIB transcription)
Related source files and packages: