OID reference

agencySignalStateControlType

1.3.6.1.4.1.1206.4.2.1.16.12.1.3

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.1.16.12.1 (agencySignalStateEntry)
Node code: 3
Node name: agencySignalStateControlType
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.1.16.12.1.3
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.1.16.12.1.3

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 1206 4 2 1 16 12 1 3}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) asc(1) ascSpat(16) agencySignalStateTable(12) agencySignalStateEntry(1) agencySignalStateControlType(3)}

OID-IRI notation

/1/3/6/1/4/1/1206/4/2/1/16/12/1/3
/ISO/Identified-Organization/6/1/4/1/1206/4/2/1/16/12/1/3
/ISO/3/6/1/4/1/1206/4/2/1/16/12/1/3

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/asc/ascSpat/agencySignalStateTable/agencySignalStateEntry/agencySignalStateControlType
Additional combinations skipped.

SNMP properties

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

Enumerated values

Value	Name
1	other
2	vehicle
3	pedestrian

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 agencySignalStateNumber 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.16.12.1.3.<agencySignalStateNumber>. 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.16.12.1.3

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.

Published definition

The displayed source records contain one distinct definition. Compare its source records.

agencySignalStateControlType OBJECT-TYPE
      SYNTAX    INTEGER {
             other (1),
             vehicle (2),
             pedestrian (3) }
      ACCESS    read-write
      STATUS    mandatory
      DESCRIPTION "<Definition> This object defines the type of control for
             the signal group (Vehicle Phase, Pedestrian Phase, Overlap or
             Pedestrian Overlap) to be used to determine the movement phase
             state to broadcast in a SPaT message:
      other: The signal group is not defined by the standard. Per NTCIP 8004
             v02, an attempt to write a value of 'other' shall return a
             badValue error. A user- or manufacturer-specific object is
             permitted to extend the possible states.
      vehicle: The signal group is is configured in the signalGroupEntryTable
             with a control type of phaseVehicle (3) or overlap (5) or
             queueJump (7).




                                                                                    

                                                                                              
                                                                                             

      pedestrian: The signal group is configured in the signalGroupEntryTable
            with a control type of phasePedestrian (4) or pedOverlap (6).
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.12.1.3
      <Object Type> P"
::= { agencySignalStateEntry 3 }

Meaning

Descriptions

1 unique

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

<Definition> This object defines the type of control for the signal group (Vehicle Phase, Pedestrian Phase, Overlap or Pedestrian Overlap) to be used to determine the movement phase state to broadcast in a SPaT message: other: The signal group is not defined by the standard. Per NTCIP 8004 v02, an attempt to write a value of 'other' shall return a badValue error. A user- or manufacturer-specific object is permitted to extend the possible states. vehicle: The signal group is is configured in the signalGroupEntryTable with a control type of phaseVehicle (3) or overlap (5) or queueJump (7). pedestrian: The signal group is configured in the signalGroupEntryTable with a control type of phasePedestrian (4) or pedOverlap (6). <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.12.1.3 <Object Type> P

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

1 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

agencySignalStateControlType · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: agencySignalStateControlType

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "agencySignalStateControlType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "vehicle",
    "(",
    "2",
    ")",
    ",",
    "pedestrian",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> This object defines the type of control for the signal group (Vehicle Phase, Pedestrian Phase, Overlap or Pedestrian Overlap) to be used to determine the movement phase state to broadcast in a SPaT message: other: The signal group is not defined by the standard. Per NTCIP 8004 v02, an attempt to write a value of 'other' shall return a badValue error. A user- or manufacturer-specific object is permitted to extend the possible states. vehicle: The signal group is is configured in the signalGroupEntryTable with a control type of phaseVehicle (3) or overlap (5) or queueJump (7). pedestrian: The signal group is configured in the signalGroupEntryTable with a control type of phasePedestrian (4) or pedOverlap (6). <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.12.1.3 <Object Type> P\"",
    "::=",
    "{",
    "agencySignalStateEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "vehicle",
            2
          ],
          [
            "pedestrian",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> This object defines the type of control for the signal group (Vehicle Phase, Pedestrian Phase, Overlap or Pedestrian Overlap) to be used to determine the movement phase state to broadcast in a SPaT message: other: The signal group is not defined by the standard. Per NTCIP 8004 v02, an attempt to write a value of 'other' shall return a badValue error. A user- or manufacturer-specific object is permitted to extend the possible states. vehicle: The signal group is is configured in the signalGroupEntryTable with a control type of phaseVehicle (3) or overlap (5) or queueJump (7). pedestrian: The signal group is configured in the signalGroupEntryTable with a control type of phasePedestrian (4) or pedOverlap (6). <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.16.12.1.3 <Object Type> P"
    ],
    null,
    null,
    null,
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — 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.
· Download NTCIP-1202v03.35e-aspublished.pdf — NTCIP1202-v03 (MIB transcription)
Related source files and packages:
Show more related files and packages
- NTCIP8004-NEMA.mib — ITE namespace dependency
- NTCIP8004-Transportation.mib — ITE namespace dependency

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (4)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.1.16.12.1.1	agencySignalStateNumber	0	0
1.3.6.1.4.1.1206.4.2.1.16.12.1.2	agencySignalStateColor	0	0
1.3.6.1.4.1.1206.4.2.1.16.12.1.4	agencySignalStateOptions	0	0
1.3.6.1.4.1.1206.4.2.1.16.12.1.5	agencySignalStateValue	0	0