Status in source: unconfirmed.
Names: rsuSignalStatusBlock
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rsuSignalStatusBlock",
"OBJECT-TYPE",
"SYNTAX",
"OerString",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> An OER encoded string of the mandatory data required from an ASC to support a SPaT message as defined below. This object is used for uploading SPaT data from the ASC in a bandwidth efficient manner. rsuSignalStatus ::= SEQUENCE { rsuAscCurrentTick.0, -- Bytes 1 & 2 rsuSpatStatus.0 -- 2 BYTES rsuSpatEnabledLanesCount.0 -- 1 BYTE rsuSpatEnabledLanesStatus.0 -- n BYTES rsuSignalGroupEntryCount.0 -- 1 BYTE rsuSignalData2 SEQUENCE OF RsuSignalStatusData2 OPTIONAL } RsuSignalStatusData2 ::== SEQUENCE { rsuSignalGroupEntryNumber.y -- 1 BYTE rsuSignalState2.y.x -- 1 BYTE rsuSignalStateMinEndTick2.y.x -- 2 BYTES rsuSignalStateMaxEndTick2.y.x -- 2 BYTES rsuSignalStateNextTick2.y.x -- 2 BYTES rsuSignalStateStartTick.y.x -- 2 BYTES } where: n = rsuSpatEnabledLanesCount. This is the number of octets in the OCTET STRING of rsuSpatEnabledLanesStatus rsuSignalGroupEntryCount is a count of the number of rsuSignalGroupEntryNumber included in this object y is the rsuSignalGroupEntryNumber in the rsuSignalStatusTable x is the movementEventNumber for the rsuSignalStatusTable. Only a value of 1 (current interval) and 2 (next interval) are used. It is necessary that the rsuSignalGroupIntersection and rsuSignalGroupID objects in the rsuSignalStatusTable be populated before the rsuSignalStatusBlock be used. Although this object theoretically allows up to 255 rsuSignalGroupEntryNumbers, check that the number does not exceed the Maximum Transmission Unit (MTU) of the lower layers used. <Object Identifier> 1.3.6.1.4.1.1206.4.18.21.13.1.3\"",
"::=",
"{",
"rsuSpatEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"OerString"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> An OER encoded string of the mandatory data required from an ASC to support a SPaT message as defined below. This object is used for uploading SPaT data from the ASC in a bandwidth efficient manner. rsuSignalStatus ::= SEQUENCE { rsuAscCurrentTick.0, -- Bytes 1 & 2 rsuSpatStatus.0 -- 2 BYTES rsuSpatEnabledLanesCount.0 -- 1 BYTE rsuSpatEnabledLanesStatus.0 -- n BYTES rsuSignalGroupEntryCount.0 -- 1 BYTE rsuSignalData2 SEQUENCE OF RsuSignalStatusData2 OPTIONAL } RsuSignalStatusData2 ::== SEQUENCE { rsuSignalGroupEntryNumber.y -- 1 BYTE rsuSignalState2.y.x -- 1 BYTE rsuSignalStateMinEndTick2.y.x -- 2 BYTES rsuSignalStateMaxEndTick2.y.x -- 2 BYTES rsuSignalStateNextTick2.y.x -- 2 BYTES rsuSignalStateStartTick.y.x -- 2 BYTES } where: n = rsuSpatEnabledLanesCount. This is the number of octets in the OCTET STRING of rsuSpatEnabledLanesStatus rsuSignalGroupEntryCount is a count of the number of rsuSignalGroupEntryNumber included in this object y is the rsuSignalGroupEntryNumber in the rsuSignalStatusTable x is the movementEventNumber for the rsuSignalStatusTable. Only a value of 1 (current interval) and 2 (next interval) are used. It is necessary that the rsuSignalGroupIntersection and rsuSignalGroupID objects in the rsuSignalStatusTable be populated before the rsuSignalStatusBlock be used. Although this object theoretically allows up to 255 rsuSignalGroupEntryNumbers, check that the number does not exceed the Maximum Transmission Unit (MTU) of the lower layers used. <Object Identifier> 1.3.6.1.4.1.1206.4.18.21.13.1.3"
],
null,
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1218 v01A, Object Definitions for Roadside Units (RSUs) — original PDF
· Official record
Module: NTCIP1218-v01
See published definition above
Module imports
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DateAndTime', 'RowStatus', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE', 'enterprises'], 'URI-TC-MIB': ['Uri255', 'Uri1024'], 'NTCIP8004v02': ['devices', 'OerString'], 'SYSLOG-TC-MIB': ['SyslogSeverity'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
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: NTCIP8004v02. 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.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.18.21.13.1.3, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.18.21.13.1.3. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP-1218-v01A-2024-AsPublished.pdf — NTCIP1218-v01 (MIB transcription)
Related source files and packages:
Show more related files and packages