OID reference

dcmDataStructureTable

1.3.6.1.4.1.1206.4.2.9.6.30

Description

This is a doubly-indexed table. It defines how the data for each type of study (binned, pvr, event) shall be stored within the data files. This table is not accessible to any application. It’s purpose is to define a data structure for decoding purposes within the data files. The 2nd index is used as a count (sequence …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.9.6 (dcmStudyDataSetup)
Node code
30
Node name
dcmDataStructureTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.9.6.30
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.9.6.30
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 9 6 30}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dcm(9) dcmStudyDataSetup(6) dcmDataStructureTable(30)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/9/6/30
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/9/6/30
  • /ISO/3/6/1/4/1/1206/4/2/9/6/30
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/dcm/dcmStudyDataSetup/dcmDataStructureTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF DcmDataStructureEntry
Maximum access defined by MIB
not-accessible
Status in MIB
optional

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

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

dcmDataStructureTable OBJECT-TYPE
 SYNTAX   SEQUENCE OF DcmDataStructureEntry



                                                                                        

                      
       



 ACCESS   not-accessible
 STATUS   optional
 DESCRIPTION
 "This is a doubly-indexed table. It defines how the data for each type of
study (binned, pvr, event) shall be stored within the data files. This table
is not accessible to any application.      It’s purpose is to define a data
structure for decoding purposes within the data files. The 2nd index is used
as a count (sequence number) associated with the Data Structure Table. When
the application is decoding the data, it can use the 2nd index to verify if
the data file contains all of the data packets for a specified study (2nd
index is sequential with no missing numbers for the specified study).”
::= {dcmStudyDataSetup 30}

Meaning

Descriptions

1 unique

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

This is a doubly-indexed table. It defines how the data for each type of study (binned, pvr, event) shall be stored within the data files. This table is not accessible to any application. It’s purpose is to define a data structure for decoding purposes within the data files. The 2nd index is used as a count (sequence number) associated with the Data Structure Table. When the application is decoding the data, it can use the 2nd index to verify if the data file contains all of the data packets for a specified study (2nd index is sequential with no missing numbers for the specified study).

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 · 2 sources

Description 1

dcmDataStructureTable · optionalNTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: optional.

Names: dcmDataStructureTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcmDataStructureTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "DcmDataStructureEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"",
    "This",
    "is",
    "a",
    "doubly-indexed",
    "table",
    ".",
    "It",
    "defines",
    "how",
    "the",
    "data",
    "for",
    "each",
    "type",
    "of",
    "study",
    "(",
    "binned",
    ",",
    "pvr",
    ",",
    "event",
    ")",
    "shall",
    "be",
    "stored",
    "within",
    "the",
    "data",
    "files",
    ".",
    "This",
    "table",
    "is",
    "not",
    "accessible",
    "to",
    "any",
    "application",
    ".",
    "It",
    "’",
    "s",
    "purpose",
    "is",
    "to",
    "define",
    "a",
    "data",
    "structure",
    "for",
    "decoding",
    "purposes",
    "within",
    "the",
    "data",
    "files",
    ".",
    "The",
    "2",
    "nd",
    "index",
    "is",
    "used",
    "as",
    "a",
    "count",
    "(",
    "sequence",
    "number",
    ")",
    "associated",
    "with",
    "the",
    "Data",
    "Structure",
    "Table",
    ".",
    "When",
    "the",
    "application",
    "is",
    "decoding",
    "the",
    "data",
    ",",
    "it",
    "can",
    "use",
    "the",
    "2",
    "nd",
    "index",
    "to",
    "verify",
    "if",
    "the",
    "data",
    "file",
    "contains",
    "all",
    "of",
    "the",
    "data",
    "packets",
    "for",
    "a",
    "specified",
    "study",
    "(",
    "2",
    "nd",
    "index",
    "is",
    "sequential",
    "with",
    "no",
    "missing",
    "numbers",
    "for",
    "the",
    "specified",
    "study",
    ")",
    ".",
    "”",
    "::=",
    "{",
    "dcmStudyDataSetup",
    "30",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "DcmDataStructureEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "This is a doubly-indexed table. It defines how the data for each type of study (binned, pvr, event) shall be stored within the data files. This table is not accessible to any application. It’s purpose is to define a data structure for decoding purposes within the data files. The 2nd index is used as a count (sequence number) associated with the Data Structure Table. When the application is decoding the data, it can use the 2nd index to verify if the data file contains all of the data packets for a specified study (2nd index is sequential with no missing numbers for the specified study)."
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Data Collection and Monitoring (DCM) Devices Published November 2005 — original PDF · Official record

    Module: DCM-MIB1

    See published definition above

    Module imports
    {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

    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 DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    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: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    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 NTCIP1206v0123f.pdf — DCM-MIB1 (MIB transcription)
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1206:2005, Object Definitions for Daqta Collection and Monitoring (DCM) Devices Published November 2005 (superceded by NTCIP 1206 v02) — original PDF · Official record

    Module: DCM-MIB1

    Same published definition

    Module imports
    {'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}

    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 DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    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: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    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 NTCIP1206v0123f-1.pdf — DCM-MIB1 (MIB transcription)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.9.6.30.1 dcmDataStructureEntry77

Siblings (29)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.9.6.1 dcmLengthUnits00
1.3.6.1.4.1.1206.4.2.9.6.2 dcmSpeedUnits00
1.3.6.1.4.1.1206.4.2.9.6.3 dcmWeightUnits00
1.3.6.1.4.1.1206.4.2.9.6.4 dcmMaxNumHeadings00
1.3.6.1.4.1.1206.4.2.9.6.5 dcmMaxNumBins00
1.3.6.1.4.1.1206.4.2.9.6.6 dcmBFDTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.6.7 dcmBFDTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.6.8 dcmBinnedFilterDefTable18
1.3.6.1.4.1.1206.4.2.9.6.9 dcmBSCTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.6.10 dcmBSCTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.6.11 dcmBinSCTable16
1.3.6.1.4.1.1206.4.2.9.6.12 dcmPSCTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.6.13 dcmPSCTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.6.14 dcmPvrStudyConfigTable15
1.3.6.1.4.1.1206.4.2.9.6.15 dcmESCTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.6.16 dcmESCTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.6.17 dcmEventStudyConfigTable15
1.3.6.1.4.1.1206.4.2.9.6.18 dcmELIMTMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.6.19 dcmELIMTCurNumRows00
1.3.6.1.4.1.1206.4.2.9.6.20 dcmEventConfigTable19
1.3.6.1.4.1.1206.4.2.9.6.21 dcmDRETMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.6.22 dcmDRETCurNumRows00
1.3.6.1.4.1.1206.4.2.9.6.23 dcmDRETable14
1.3.6.1.4.1.1206.4.2.9.6.24 dcmMETMaxNumRows00
1.3.6.1.4.1.1206.4.2.9.6.25 dcmMETCurNumRows00
1.3.6.1.4.1.1206.4.2.9.6.26 dcmMETable18
1.3.6.1.4.1.1206.4.2.9.6.27 dcmAPCTable16
1.3.6.1.4.1.1206.4.2.9.6.28 dcmIOPCRecTable15
1.3.6.1.4.1.1206.4.2.9.6.29 dcmLDRecTable13