Status in source: mandatory.
Names: rmcBlockData
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcBlockData",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"2",
".",
".",
"484",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> An OER encoded string used for uploading and downloading RMC parameters. See SECTION 4 for encoding and decoding the block. A SET on this object shall require the use of 'dbCreateTransaction' defined in NTCIP 1201 v03 Clause 2.3.1. A SET of this object shall be evaluated for validity and an Error Status of badValue(3) be returned for the following conditions: 1) rmcBlockDataType is not supported 2) rmcBlockDataID is not supported 3) rmcBlockIndex1 is zero or is greater than the table's maximum number of rows 4) rmcBlockQuantity1 is zero or rmcBlockIndex1 + rmcBlockQuantity1 - 1 is greater than the table's maximum number of rows 5) rmcBlockIndex2 is zero or is greater than the table's maximum number of rows 6) rmcBlockQuantity2 is zero or rmcBlockIndex2 + rmcBlockQuantity2 - 1 is greater than the table's maximum number of rows 7) rmcBlockIndex3 is zero or is greater than the table's maximum number of rows 8) rmcBlockQuantity3 is zero or rmcBlockIndex3 + rmcBlockQuantity3 - 1 is greater than the table's maximum number of rows 9) rmcBlockIndex4 is zero or is greater than the table's maximum number of rows 10) rmcBlockQuantity4 is zero or rmcBlockIndex4 + rmcBlockQuantity4 - 1 is greater than the table's maximum number of rows 11) rmcBlockIndex5 is zero or is greater than the table's maximum number of rows 12) rmcBlockQuantity5 is zero or rmcBlockIndex5 + rmcBlockQuantity5 - 1 is greater than the table's maximum number of rows 13) if the SET length is zero or incorrect for rmcBlockDataType & rmcBlockDataID 14) if the SET (SEQUENCE OF) value is incorrect. When this validity check fails, rmcBlockErrorStatus shall be set equal to the Bullet Value above that generated the error. Because of SNMP, it cannot be determined in advance which error of multiple, simultaneous errors will be reported. A SET that includes an unsupported value for a supported data element shall return an Error Status of badValue(3) and rmcBlockErrorStatus shall be set equal to: (data Sequence # * 100) + data Element # A SET that includes a non-zero or non-null value in the position of an unsupported data element shall return an Error Status of badValue(3) and rmcBlockErrorStatus shall be set equal to: (data Sequence # * 100) + data Element # A GET on this object shall utilize values currently in rmcBlockGetControl to define the data to be returned. When rmcBlockGetControl has invalid data, an Error Status of badValue(3) shall be returned. A GET shall return a zero or null value in the position of an unsupported object. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.7.2\"",
"::=",
"{",
"rmcBlock",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
2,
484
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> An OER encoded string used for uploading and downloading RMC parameters. See SECTION 4 for encoding and decoding the block. A SET on this object shall require the use of 'dbCreateTransaction' defined in NTCIP 1201 v03 Clause 2.3.1. A SET of this object shall be evaluated for validity and an Error Status of badValue(3) be returned for the following conditions: 1) rmcBlockDataType is not supported 2) rmcBlockDataID is not supported 3) rmcBlockIndex1 is zero or is greater than the table's maximum number of rows 4) rmcBlockQuantity1 is zero or rmcBlockIndex1 + rmcBlockQuantity1 - 1 is greater than the table's maximum number of rows 5) rmcBlockIndex2 is zero or is greater than the table's maximum number of rows 6) rmcBlockQuantity2 is zero or rmcBlockIndex2 + rmcBlockQuantity2 - 1 is greater than the table's maximum number of rows 7) rmcBlockIndex3 is zero or is greater than the table's maximum number of rows 8) rmcBlockQuantity3 is zero or rmcBlockIndex3 + rmcBlockQuantity3 - 1 is greater than the table's maximum number of rows 9) rmcBlockIndex4 is zero or is greater than the table's maximum number of rows 10) rmcBlockQuantity4 is zero or rmcBlockIndex4 + rmcBlockQuantity4 - 1 is greater than the table's maximum number of rows 11) rmcBlockIndex5 is zero or is greater than the table's maximum number of rows 12) rmcBlockQuantity5 is zero or rmcBlockIndex5 + rmcBlockQuantity5 - 1 is greater than the table's maximum number of rows 13) if the SET length is zero or incorrect for rmcBlockDataType & rmcBlockDataID 14) if the SET (SEQUENCE OF) value is incorrect. When this validity check fails, rmcBlockErrorStatus shall be set equal to the Bullet Value above that generated the error. Because of SNMP, it cannot be determined in advance which error of multiple, simultaneous errors will be reported. A SET that includes an unsupported value for a supported data element shall return an Error Status of badValue(3) and rmcBlockErrorStatus shall be set equal to: (data Sequence # * 100) + data Element # A SET that includes a non-zero or non-null value in the position of an unsupported data element shall return an Error Status of badValue(3) and rmcBlockErrorStatus shall be set equal to: (data Sequence # * 100) + data Element # A GET on this object shall utilize values currently in rmcBlockGetControl to define the data to be returned. When rmcBlockGetControl has invalid data, an Error Status of badValue(3) shall be returned. A GET shall return a zero or null value in the position of an unsupported object. <Object Identifier> 1.3.6.1.4.1.1206.4.2.2.7.2"
],
null,
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1207 v02, Object Definitions for Ramp Meter Control (RMC) Units Published September 2014 — original PDF
· Official record
Module: N207v0214-MIB
See published definition above
Module imports
{'NTCIP': ['ramp'], 'RFC-1212': ['OBJECT-TYPE']}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: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: The PDF prints an invalid ASN.1 module label (1207v0214-MIB). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP. 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 NTCIP1207v0214hj.pdf — N207v0214-MIB (MIB transcription)
Related source files and packages:
Show more related files and packages