Status in source: mandatory.
Names: coBusy
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"coBusy",
"OBJECT-TYPE",
"SYNTAX",
"TrueFalse",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This object is used to indicate to a PRS that the CO is initializing or otherwise processing and when TRUE, the information included with it in a prsServiceRequest response is not valid. It is used to synchronize exchanges between a PRS and CO. When the PRS is acting as manager and the CO is acting as an agent, coBusy is set TRUE when the PRS performs a SetRequest prsServiceRequest. When the CO is acting as a manager and the PRS is acting as the agent, coBusy is set TRUE when the PRS responds to a GetRequest prsServiceRequest from the CO with prsBusy set to FALSE. \"",
"::=",
"{",
"priorityStrategyServer",
"3",
"}"
],
"syntax_tree": [
[
"row",
"TrueFalse"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This object is used to indicate to a PRS that the CO is initializing or otherwise processing and when TRUE, the information included with it in a prsServiceRequest response is not valid. It is used to synchronize exchanges between a PRS and CO. When the PRS is acting as manager and the CO is acting as an agent, coBusy is set TRUE when the PRS performs a SetRequest prsServiceRequest. When the CO is acting as a manager and the PRS is acting as the agent, coBusy is set TRUE when the PRS responds to a GetRequest prsServiceRequest from the CO with prsBusy set to FALSE."
],
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: