Description 1
A static table containing the parameters associated with each signal control priority request. The number of rows in this table is equal to 10.
Sources for this description
NTCIP published standard MIB annexes (reviewed modules)
OID reference
prsBusy
1.3.6.1.4.1.1206.4.2.11.1.2
Description
A static table containing the parameters associated with each signal control priority request. The number of rows in this table is equal to 10.
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.1206.4.2.11.1 (priorityRequestServer)
- Node code
- 2
- Node names
- prsBusy
- priorityRequestTable
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.1206.4.2.11.1.2
- URN notation
- urn:oid:1.3.6.1.4.1.1206.4.2.11.1.2
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 1206 4 2 11 1 2}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) prsBusy(2)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityRequestServer(1) priorityRequestTable(2)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/1206/4/2/11/1/2
- /ISO/Identified-Organization/6/1/4/1/1206/4/2/11/1/2
- /ISO/3/6/1/4/1/1206/4/2/11/1/2
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/scp/priorityRequestServer/prsBusy
- /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/scp/priorityRequestServer/priorityRequestTable
- Additional combinations skipped.
SNMP properties
- Value type
- SEQUENCE OF PriorityRequestEntry, TrueFalse
- Maximum access defined by MIB
- not-accessible, read-only
- Status in MIB
- optional, mandatory
Definitions may combine these properties differently.
Compare 3 source variants
Variant 1 — NTCIP published standard MIB annexes (reviewed modules)
- Value type
- SEQUENCE OF PriorityRequestEntry
- Maximum access defined by MIB
- not-accessible
- Status in MIB
- optional
Variant 2 — NTCIP published standard MIB annexes (reviewed modules)
- Value type
- TrueFalse
- Maximum access defined by MIB
- read-only
- Status in MIB
- optional
Variant 3 — NTCIP published standard MIB annexes (reviewed modules)
- Value type
- TrueFalse
- Maximum access defined by MIB
- read-only
- Status in MIB
- mandatory
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Published definitions
Available source records contain 3 distinct definitions; some records may not include a definition.
Show 3 published definitions
priorityRequestTable · optional
priorityRequestTable OBJECT-TYPE
SYNTAX SEQUENCE OF PriorityRequestEntry
ACCESS not-accessible
STATUS optional
DESCRIPTION
"A static table containing the parameters associated with each
signal control priority request. The number of rows in this table is
equal to 10."
::= { priorityRequestServer 2 }prsBusy · optional
prsBusy OBJECT-TYPE
SYNTAX TrueFalse
ACCESS read-only
STATUS optional
DESCRIPTION
"This object is used to indicate to a CO that the PRS is
initializing or otherwise processing and, when TRUE, the information
included with it in a prsServiceRequest response is not valid. It
is used to synchonize exchanges between a PRS and CO.
When the CO is acting as manager and the PRS is acting as an agent,
prsBusy is set TRUE when the CO performs a SetRequest
prsServiceRequest.
When the PRS is acting as a manager and the CO is acting as the
agent, the value shall always be set to FALSE.
::= { priorityRequestServer 2 }prsBusy · mandatory
prsBusy OBJECT-TYPE
SYNTAX TrueFalse
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This object is used to indicate to a CO that the PRS 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 CO is acting as manager and the PRS is acting as an
agent, prsBusy is set TRUE when the CO performs a SetRequest
prsServiceRequest.
When the PRS is acting as a manager and the CO is acting as the
agent, prsBusy is set TRUE when the CO responds to a GetRequest
prsServiceRequest from the PRS with coBusy set to FALSE.”
::= { priorityRequestServer 2 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 2
This object is used to indicate to a CO that the PRS is initializing or otherwise processing and, when TRUE, the information included with it in a prsServiceRequest response is not valid. It is used to synchonize exchanges between a PRS and CO. When the CO is acting as manager and the PRS is acting as an agent, prsBusy is set TRUE when the CO performs a SetRequest prsServiceRequest. When the PRS is acting as a manager and the CO is acting as the agent, the value shall always be set to FALSE.
Sources for this description
NTCIP published standard MIB annexes (reviewed modules)
Description 3
This object is used to indicate to a CO that the PRS 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 CO is acting as manager and the PRS is acting as an agent, prsBusy is set TRUE when the CO performs a SetRequest prsServiceRequest. When the PRS is acting as a manager and the CO is acting as the agent, prsBusy is set TRUE when the CO responds to a GetRequest prsServiceRequest from the PRS with coBusy set to FALSE.
Sources for this description
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1NTCIP published standard MIB annexes (reviewed modules)
priorityRequestTable · optionalNTCIP published standard MIB annexes (reviewed modules)
Status in source: optional.
Names: priorityRequestTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"priorityRequestTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"PriorityRequestEntry",
"ACCESS",
"not-accessible",
"STATUS",
"optional",
"DESCRIPTION",
"\"A static table containing the parameters associated with each signal control priority request. The number of rows in this table is equal to 10.\"",
"::=",
"{",
"priorityRequestServer",
"2",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"PriorityRequestEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"A static table containing the parameters associated with each signal control priority request. The number of rows in this table is equal to 10."
],
null,
null,
null,
null
]
}- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1211 v01, Object Definitions for Signal Control and Prioritization Published May 2008 (superceded by NTCIP 1211 v02) — original PDF
· Official record
Module: PRS-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 published prsBusy DESCRIPTION lacks its closing quote. Close the string in a blank character immediately before its explicit assignment; no OID or description words are supplied.
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: priorityRequestServer ::= {scp 1}, priorityRequestMessages ::= { scp 2 }. 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.
· Download 1211v0138p-2008b_Final.pdf — PRS-MIB1 (MIB transcription)Related ASN.1 definitions
priorityRequestServer ::= {scp 1}priorityRequestMessages ::= { scp 2 }Related source files and packages:
- NTCIP 1211 v01, Object Definitions for Signal Control and Prioritization Published May 2008 (superceded by NTCIP 1211 v02) — original PDF
- NTCIP 8004 v02 (2010) — normative namespace, pages 43–44
- RFC 1155 — original SMI enterprise namespace
Show more related files and packages
Records for description 2NTCIP published standard MIB annexes (reviewed modules)
prsBusy · optionalNTCIP published standard MIB annexes (reviewed modules)
Status in source: optional.
Names: prsBusy
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"prsBusy",
"OBJECT-TYPE",
"SYNTAX",
"TrueFalse",
"ACCESS",
"read-only",
"STATUS",
"optional",
"DESCRIPTION",
"\"",
"This",
"object",
"is",
"used",
"to",
"indicate",
"to",
"a",
"CO",
"that",
"the",
"PRS",
"is",
"initializing",
"or",
"otherwise",
"processing",
"and",
",",
"when",
"TRUE",
",",
"the",
"information",
"included",
"with",
"it",
"in",
"a",
"prsServiceRequest",
"response",
"is",
"not",
"valid",
".",
"It",
"is",
"used",
"to",
"synchonize",
"exchanges",
"between",
"a",
"PRS",
"and",
"CO",
".",
"When",
"the",
"CO",
"is",
"acting",
"as",
"manager",
"and",
"the",
"PRS",
"is",
"acting",
"as",
"an",
"agent",
",",
"prsBusy",
"is",
"set",
"TRUE",
"when",
"the",
"CO",
"performs",
"a",
"SetRequest",
"prsServiceRequest",
".",
"When",
"the",
"PRS",
"is",
"acting",
"as",
"a",
"manager",
"and",
"the",
"CO",
"is",
"acting",
"as",
"the",
"agent",
",",
"the",
"value",
"shall",
"always",
"be",
"set",
"to",
"FALSE",
".",
"::=",
"{",
"priorityRequestServer",
"2",
"}"
],
"syntax_tree": [
[
"row",
"TrueFalse"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"This object is used to indicate to a CO that the PRS is initializing or otherwise processing and, when TRUE, the information included with it in a prsServiceRequest response is not valid. It is used to synchonize exchanges between a PRS and CO. When the CO is acting as manager and the PRS is acting as an agent, prsBusy is set TRUE when the CO performs a SetRequest prsServiceRequest. When the PRS is acting as a manager and the CO is acting as the agent, the value shall always be set to FALSE."
],
null,
null,
null,
null
]
}- NTCIP published standard MIB annexes (reviewed modules)
· Official record
Module: PRS-MIB1
See published definition above
Related ASN.1 definitions
priorityRequestServer ::= {scp 1}priorityRequestMessages ::= { scp 2 }
Records for description 3NTCIP published standard MIB annexes (reviewed modules)
prsBusy · mandatoryNTCIP published standard MIB annexes (reviewed modules)
Status in source: mandatory.
Names: prsBusy
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"prsBusy",
"OBJECT-TYPE",
"SYNTAX",
"TrueFalse",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"",
"This",
"object",
"is",
"used",
"to",
"indicate",
"to",
"a",
"CO",
"that",
"the",
"PRS",
"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",
"CO",
"is",
"acting",
"as",
"manager",
"and",
"the",
"PRS",
"is",
"acting",
"as",
"an",
"agent",
",",
"prsBusy",
"is",
"set",
"TRUE",
"when",
"the",
"CO",
"performs",
"a",
"SetRequest",
"prsServiceRequest",
".",
"When",
"the",
"PRS",
"is",
"acting",
"as",
"a",
"manager",
"and",
"the",
"CO",
"is",
"acting",
"as",
"the",
"agent",
",",
"prsBusy",
"is",
"set",
"TRUE",
"when",
"the",
"CO",
"responds",
"to",
"a",
"GetRequest",
"prsServiceRequest",
"from",
"the",
"PRS",
"with",
"coBusy",
"set",
"to",
"FALSE",
".",
"”",
"::=",
"{",
"priorityRequestServer",
"2",
"}"
],
"syntax_tree": [
[
"row",
"TrueFalse"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This object is used to indicate to a CO that the PRS 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 CO is acting as manager and the PRS is acting as an agent, prsBusy is set TRUE when the CO performs a SetRequest prsServiceRequest. When the PRS is acting as a manager and the CO is acting as the agent, prsBusy is set TRUE when the CO responds to a GetRequest prsServiceRequest from the PRS with coBusy 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: PRS-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: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. 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: priorityRequestServer ::= {scp 1}, priorityRequestMessages ::= { scp 2 }. 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.
· Download NTCIP1211-v0224j.pdf — PRS-MIB1 (MIB transcription)Related ASN.1 definitions
priorityRequestServer ::= {scp 1}priorityRequestMessages ::= { scp 2 }Related source files and packages:
Registration
Registration authorities
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)
Direct children (1)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.11.1.2.1 | priorityRequestTableEntry | 13 | 13 |
Siblings (13)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.11.1.1 | priorityRequestTable | 1 | 15 | |
| 1.3.6.1.4.1.1206.4.2.11.1.3 | priorityRequestTimeToLiveValue | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.4 | priorityRequestReserviceTimer | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.5 | priorityRequestReserviceClass1Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.6 | priorityRequestReserviceClass2Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.7 | priorityRequestReserviceClass3Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.8 | priorityRequestReserviceClass4Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.9 | priorityRequestReserviceClass5Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.10 | priorityRequestReserviceClass6Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.11 | priorityRequestReserviceClass7Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.12 | priorityRequestReserviceClass8Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.13 | priorityRequestReserviceClass9Time, PriorityRequestReserviceClass9Time | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.11.1.14 | priorityRequestReserviceClass10Time | 0 | 0 |