Status in source: mandatory.
Names: scpBlockGetControl
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"scpBlockGetControl",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"2",
".",
".",
"12",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> An OER encoded string of reference parameters for SCP Block Uploads. The parameter values in this string are: scpBlockDataType INTEGER (0..255) scpBlockDataID INTEGER (0..255) scpBlockIndex1 INTEGER (0..255) if needed scpBlockQuantity1 INTEGER (0..255) if needed scpBlockIndex2 INTEGER (0..255) if needed scpBlockQuantity2 INTEGER (0..255) if needed scpBlockIndex3 INTEGER (0..255) if needed scpBlockQuantity3 INTEGER (0..255) if needed scpBlockIndex4 INTEGER (0..255) if needed scpBlockQuantity4 INTEGER (0..255) if needed scpBlockIndex5 INTEGER (0..255) if needed scpBlockQuantity5 INTEGER (0..255) if needed A GET of scpBlockData shall utilize values currently in this object to define the data to be returned. A SET of this object shall be evaluated for validity and Error Status of badValue(3) be returned for the following conditions: 1) scpBlockDataType is not supported 2) scpBlockDataID is not supported 3) scpBlockIndex1 is zero or not supported 4) scpBlockQuantity1 is zero or scpBlockIndex1 + scpBlockQuantity1 - 1 is not supported 5) scpBlockIndex2 is zero or not supported 6) scpBlockQuantity2 is zero or scpBlockIndex2 + scpBlockQuantity2) - 1 is not supported 7) scpBlockIndex3 is zero or not supported 8) scpBlockQuantity3 is zero or scpBlockIndex3 + scpBlockQuantity3) - 1 is not supported 9) scpBlockIndex4 is zero or not supported 10) scpBlockQuantity4 is zero or scpBlockIndex4 + scpBlockQuantity4) - 1 is not supported 11) scpBlockIndex5 is zero or not supported 12) scpBlockQuantity5 is zero or scpBlockIndex5 + scpBlockQuantity5) - 1 is not supported 13) if the SET length is zero or incorrect for scpBlockDataType & scpBlockDataID 14) if the GetResponse length for a GET on scpBlockData using maximum data field sizes would exceed a local limitation When this validity check fails, scpBlockErrorStatus shall be set equal to the Bullet Value above that generated the error. <DescriptiveName> NTCIP-1211::SCP.scpBlockGetControl <DataConceptType> Data Frame <Unit>\"",
"::=",
"{",
"scpBlock",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
2,
12
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> An OER encoded string of reference parameters for SCP Block Uploads. The parameter values in this string are: scpBlockDataType INTEGER (0..255) scpBlockDataID INTEGER (0..255) scpBlockIndex1 INTEGER (0..255) if needed scpBlockQuantity1 INTEGER (0..255) if needed scpBlockIndex2 INTEGER (0..255) if needed scpBlockQuantity2 INTEGER (0..255) if needed scpBlockIndex3 INTEGER (0..255) if needed scpBlockQuantity3 INTEGER (0..255) if needed scpBlockIndex4 INTEGER (0..255) if needed scpBlockQuantity4 INTEGER (0..255) if needed scpBlockIndex5 INTEGER (0..255) if needed scpBlockQuantity5 INTEGER (0..255) if needed A GET of scpBlockData shall utilize values currently in this object to define the data to be returned. A SET of this object shall be evaluated for validity and Error Status of badValue(3) be returned for the following conditions: 1) scpBlockDataType is not supported 2) scpBlockDataID is not supported 3) scpBlockIndex1 is zero or not supported 4) scpBlockQuantity1 is zero or scpBlockIndex1 + scpBlockQuantity1 - 1 is not supported 5) scpBlockIndex2 is zero or not supported 6) scpBlockQuantity2 is zero or scpBlockIndex2 + scpBlockQuantity2) - 1 is not supported 7) scpBlockIndex3 is zero or not supported 8) scpBlockQuantity3 is zero or scpBlockIndex3 + scpBlockQuantity3) - 1 is not supported 9) scpBlockIndex4 is zero or not supported 10) scpBlockQuantity4 is zero or scpBlockIndex4 + scpBlockQuantity4) - 1 is not supported 11) scpBlockIndex5 is zero or not supported 12) scpBlockQuantity5 is zero or scpBlockIndex5 + scpBlockQuantity5) - 1 is not supported 13) if the SET length is zero or incorrect for scpBlockDataType & scpBlockDataID 14) if the GetResponse length for a GET on scpBlockData using maximum data field sizes would exceed a local limitation When this validity check fails, scpBlockErrorStatus shall be set equal to the Bullet Value above that generated the error. <DescriptiveName> NTCIP-1211::SCP.scpBlockGetControl <DataConceptType> Data Frame <Unit>"
],
null,
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1211 v02, Object Definitions for Signal Control and Prioritization (SCP) Published September 2014 — original PDF
· Official record
Module: CO-MIB1
See published definition above
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: The DESCRIPTION contains an interior ASCII quotation mark that incorrectly terminates the string before OR'ed. Normalize only the interior opening quote to typographic form in the parser copy, retaining the original definition. No numeric assignment changes.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of scp. 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: This module uses explicit parent OID expressions with an omitted SMI type: priorityStrategyServer ::= { scp 3 }, priorityStrategyMessages ::= { scp 4}. These assignments are interpreted as OID groupings for the native child objects. The type omission and original expressions remain visible; consult the original PDF before implementation.
Related ASN.1 definitions
priorityStrategyServer ::= { scp 3 }priorityStrategyMessages ::= { scp 4}
Related source files and packages: