OID reference

preemptExitType

1.3.6.1.4.1.1206.4.2.1.6.2.1.28

Description

<Definition> This object defines the exit strategy (type) to be used following the end of the preempt. The exit types are as follows: exitPhases: the CU immediately enters the exit phases to be active as configured queueDelayRecovery: the CU immediately enters the phase with the highest demand or longest wait time sho…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.1.6.2.1 (preemptEntry)
Node code
28
Node name
preemptExitType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.1.6.2.1.28
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.1.6.2.1.28
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 1 6 2 1 28}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) preempt(6) preemptTable(2) preemptEntry(1) preemptExitType(28)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/1/6/2/1/28
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/1/6/2/1/28
  • /ISO/3/6/1/4/1/1206/4/2/1/6/2/1/28
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/asc/preempt/preemptTable/preemptEntry/preemptExitType
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Enumerated values

ValueName
1exitPhases
2queueDelayRecovery
3shortService
4exitCoord

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In NTCIP1202-v03, the row index preemptNumber is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.1.6.2.1.28.<preemptNumber>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.1.6.2.1.28

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

preemptExitType · unconfirmed

preemptExitType OBJECT-TYPE
      SYNTAX INTEGER { exitPhases (1),
            queueDelayRecovery (2),
            shortService (3),
            exitCoord (4)}
      ACCESS read-write
      STATUS mandatory
      DESCRIPTION "<Definition> This object defines the exit strategy (type)
            to be used following the end of the preempt. The exit types are
            as follows:
            exitPhases: the CU immediately enters the exit phases to be
                  active as configured
            queueDelayRecovery: the CU immediately enters the phase with the
                  highest demand or longest wait time
            shortService: the CU immediately enters the first short service
                  phase. The first short service phase is a phase where only
                  the preempt minimum green time was serviced during the
                  advanced preemption time or the right-of-way transfer time
            exitCoord: the CU immediately returns to the place in the
                  coordinated cycle where the ASC would have been if there
                  was no preempt
      <Object Type> P
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27"
::= { preemptEntry 28 }

preemptExitType · unconfirmed

preemptExitType OBJECT-TYPE
      SYNTAX INTEGER { exitPhases (1),
            queueDelayRecovery (2),
            shortService (3),
            exitCoord (4)}
      ACCESS read-write
      STATUS mandatory
      DESCRIPTION "<Definition> This object defines the exit strategy (type)
            to be used following the end of the preempt. The exit types are
            as follows:
            exitPhases: the CU immediately enters the exit phases to be
                  active as configured
            queueDelayRecovery: the CU immediately enters the phase with the
                  highest demand or longest wait time
            shortService: the CU immediately enters the first short service
                  phase. The first short service phase is a phase where only
                  the preempt minimum green time was serviced during the
                  advanced preemption time or the right-of-way transfer time
            exitCoord: the CU immediately returns to the place in the
                  coordinated cycle where the ASC would have been if there
                  was no preempt
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27"
::= { preemptEntry 28 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

<Definition> This object defines the exit strategy (type) to be used following the end of the preempt. The exit types are as follows: exitPhases: the CU immediately enters the exit phases to be active as configured queueDelayRecovery: the CU immediately enters the phase with the highest demand or longest wait time shortService: the CU immediately enters the first short service phase. The first short service phase is a phase where only the preempt minimum green time was serviced during the advanced preemption time or the right-of-way transfer time exitCoord: the CU immediately returns to the place in the coordinated cycle where the ASC would have been if there was no preempt <Object Type> P <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> This object defines the exit strategy (type) to be used following the end of the preempt. The exit types are as follows: exitPhases: the CU immediately enters the exit phases to be active as configured queueDelayRecovery: the CU immediately enters the phase with the highest demand or longest wait time shortService: the CU immediately enters the first short service phase. The first short service phase is a phase where only the preempt minimum green time was serviced during the advanced preemption time or the right-of-way transfer time exitCoord: the CU immediately returns to the place in the coordinated cycle where the ASC would have been if there was no preempt <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 1

preemptExitType · unconfirmedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unconfirmed.

Names: preemptExitType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "preemptExitType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "exitPhases",
    "(",
    "1",
    ")",
    ",",
    "queueDelayRecovery",
    "(",
    "2",
    ")",
    ",",
    "shortService",
    "(",
    "3",
    ")",
    ",",
    "exitCoord",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object defines the exit strategy (type) to be used following the end of the preempt. The exit types are as follows: exitPhases: the CU immediately enters the exit phases to be active as configured queueDelayRecovery: the CU immediately enters the phase with the highest demand or longest wait time shortService: the CU immediately enters the first short service phase. The first short service phase is a phase where only the preempt minimum green time was serviced during the advanced preemption time or the right-of-way transfer time exitCoord: the CU immediately returns to the place in the coordinated cycle where the ASC would have been if there was no preempt <Object Type> P <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27\"",
    "::=",
    "{",
    "preemptEntry",
    "28",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "exitPhases",
            1
          ],
          [
            "queueDelayRecovery",
            2
          ],
          [
            "shortService",
            3
          ],
          [
            "exitCoord",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object defines the exit strategy (type) to be used following the end of the preempt. The exit types are as follows: exitPhases: the CU immediately enters the exit phases to be active as configured queueDelayRecovery: the CU immediately enters the phase with the highest demand or longest wait time shortService: the CU immediately enters the first short service phase. The first short service phase is a phase where only the preempt minimum green time was serviced during the advanced preemption time or the right-of-way transfer time exitCoord: the CU immediately returns to the place in the coordinated cycle where the ASC would have been if there was no preempt <Object Type> P <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

preemptExitType · unconfirmedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unconfirmed.

Names: preemptExitType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "preemptExitType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "exitPhases",
    "(",
    "1",
    ")",
    ",",
    "queueDelayRecovery",
    "(",
    "2",
    ")",
    ",",
    "shortService",
    "(",
    "3",
    ")",
    ",",
    "exitCoord",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object defines the exit strategy (type) to be used following the end of the preempt. The exit types are as follows: exitPhases: the CU immediately enters the exit phases to be active as configured queueDelayRecovery: the CU immediately enters the phase with the highest demand or longest wait time shortService: the CU immediately enters the first short service phase. The first short service phase is a phase where only the preempt minimum green time was serviced during the advanced preemption time or the right-of-way transfer time exitCoord: the CU immediately returns to the place in the coordinated cycle where the ASC would have been if there was no preempt <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27\"",
    "::=",
    "{",
    "preemptEntry",
    "28",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "exitPhases",
            1
          ],
          [
            "queueDelayRecovery",
            2
          ],
          [
            "shortService",
            3
          ],
          [
            "exitCoord",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object defines the exit strategy (type) to be used following the end of the preempt. The exit types are as follows: exitPhases: the CU immediately enters the exit phases to be active as configured queueDelayRecovery: the CU immediately enters the phase with the highest demand or longest wait time shortService: the CU immediately enters the first short service phase. The first short service phase is a phase where only the preempt minimum green time was serviced during the advanced preemption time or the right-of-way transfer time exitCoord: the CU immediately returns to the place in the coordinated cycle where the ASC would have been if there was no preempt <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.6.2.1.27"
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF · Official record

    Module: NTCIP1202-v03

    See published definition above

    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'null'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['OwnerString', 'OerString', 'devices']}

    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.1.6.2.1.28, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.1.6.2.1.27. 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-1202v0328A.pdf — NTCIP1202-v03 (MIB transcription)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (27)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.1.6.2.1.1 preemptNumber00
1.3.6.1.4.1.1206.4.2.1.6.2.1.2 preemptControl00
1.3.6.1.4.1.1206.4.2.1.6.2.1.3 preemptLink00
1.3.6.1.4.1.1206.4.2.1.6.2.1.4 preemptDelay00
1.3.6.1.4.1.1206.4.2.1.6.2.1.5 preemptMinimumDuration00
1.3.6.1.4.1.1206.4.2.1.6.2.1.6 preemptMinimumGreen00
1.3.6.1.4.1.1206.4.2.1.6.2.1.7 preemptMinimumWalk00
1.3.6.1.4.1.1206.4.2.1.6.2.1.8 preemptEnterPedClear00
1.3.6.1.4.1.1206.4.2.1.6.2.1.9 preemptTrackGreen00
1.3.6.1.4.1.1206.4.2.1.6.2.1.10 preemptDwellGreen00
1.3.6.1.4.1.1206.4.2.1.6.2.1.11 preemptMaximumPresence00
1.3.6.1.4.1.1206.4.2.1.6.2.1.12 preemptTrackPhase00
1.3.6.1.4.1.1206.4.2.1.6.2.1.13 preemptDwellPhase00
1.3.6.1.4.1.1206.4.2.1.6.2.1.14 preemptDwellPed00
1.3.6.1.4.1.1206.4.2.1.6.2.1.15 preemptExitPhase00
1.3.6.1.4.1.1206.4.2.1.6.2.1.16 preemptState00
1.3.6.1.4.1.1206.4.2.1.6.2.1.17 preemptTrackOverlap00
1.3.6.1.4.1.1206.4.2.1.6.2.1.18 preemptDwellOverlap00
1.3.6.1.4.1.1206.4.2.1.6.2.1.19 preemptCyclingPhase00
1.3.6.1.4.1.1206.4.2.1.6.2.1.20 preemptCyclingPed00
1.3.6.1.4.1.1206.4.2.1.6.2.1.21 preemptCyclingOverlap00
1.3.6.1.4.1.1206.4.2.1.6.2.1.22 preemptEnterYellowChange00
1.3.6.1.4.1.1206.4.2.1.6.2.1.23 preemptEnterRedClear00
1.3.6.1.4.1.1206.4.2.1.6.2.1.24 preemptTrackYellowChange00
1.3.6.1.4.1.1206.4.2.1.6.2.1.25 preemptTrackRedClear00
1.3.6.1.4.1.1206.4.2.1.6.2.1.26 preemptSequenceNumber00
1.3.6.1.4.1.1206.4.2.1.6.2.1.27 preemptExitType00