OID reference
1.3.6.1.4.1.1206.4.2.1.7.3
<Definition> This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3
Identification
{1 3 6 1 4 1 1206 4 2 1 7 3}
Definitions may combine these properties differently.
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 3 distinct definitions; some records may not include a definition.
sequenceTable OBJECT-TYPE
SYNTAX SEQUENCE OF SequenceEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION "<Definition> This table contains all the sequence plans
for the controller. A sequence plan shall consist of one row for
each ring that the CU supports. Each row defines the phase
service order for that ring.
<TableType> static
<Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3"
::= { ring 3 }sequenceTable OBJECT-TYPE
SYNTAX SEQUENCE OF SequenceEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table contains all the sequence plans for the controller. A sequence plan shall consist
of one row for each ring that the CU supports. Each row defines the phase service order for
that ring."
::= { ring 3 }sequenceTable OBJECT-TYPE
SYNTAX SEQUENCE OF SequenceEntry
ACCESS not-accessible
STATUS optional
DESCRIPTION
"<Definition> This table contains all the sequence
plans for the controller. A sequence plan shall
consist of one row for each ring that the CU
supports. Each row defines the phase service order
for that ring.
<TableType> static
<DescriptiveName> NTCIP-1202::ASC.sequenceTable
<DataConceptType> Entity Type"
::= { ring 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition> This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3
NTCIP published standard MIB annexes (reviewed modules)
Description 2
This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring.
NTCIP published standard MIB annexes (reviewed modules)
Description 3
<Definition> This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring. <TableType> static <DescriptiveName> NTCIP-1202::ASC.sequenceTable <DataConceptType> Entity Type
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: sequenceTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sequenceTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"SequenceEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3\"",
"::=",
"{",
"ring",
"3",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"SequenceEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.1.7.3"
],
null,
null,
null,
null
]
}Module: NTCIP1202-v03
See published definition above
{'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:
Module: NTCIP1202-v03
Same published definition (formatting differs; exact original is in the source file)
{'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-1202v0328A.pdf — NTCIP1202-v03 (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: sequenceTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sequenceTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"SequenceEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring.\"",
"::=",
"{",
"ring",
"3",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"SequenceEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring."
],
null,
null,
null,
null
]
}Module: ASC_MIB1
See published definition above
{'TMIB': ['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: TMIB. 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 NTCIP1202v0107d.pdf — ASC_MIB1 (MIB transcription)Status in source: optional.
Names: sequenceTable
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sequenceTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"SequenceEntry",
"ACCESS",
"not-accessible",
"STATUS",
"optional",
"DESCRIPTION",
"\"<Definition> This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring. <TableType> static <DescriptiveName> NTCIP-1202::ASC.sequenceTable <DataConceptType> Entity Type\"",
"::=",
"{",
"ring",
"3",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"SequenceEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"<Definition> This table contains all the sequence plans for the controller. A sequence plan shall consist of one row for each ring that the CU supports. Each row defines the phase service order for that ring. <TableType> static <DescriptiveName> NTCIP-1202::ASC.sequenceTable <DataConceptType> Entity Type"
],
null,
null,
null,
null
]
}Module: NTCIP1202-200x
See published definition above
{'TMIB-II': ['OwnerString', 'devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}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: TMIB-II. 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 NTCIP1202v0219f.pdf — NTCIP1202-200x (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.1.7.3.1 | sequenceEntry | 3 | 3 |
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.1.7.1 | maxRings | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.7.2 | maxSequences | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.7.4 | maxRingControlGroups | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.1.7.5 | ringControlGroupTable | 1 | 10 | |
| 1.3.6.1.4.1.1206.4.2.1.7.6 | ringStatusTable | 1 | 2 |