OID reference

dcmEventConfigTable

1.3.6.1.4.1.1206.4.2.9.6.20

Description

This table maps logical IO’s to a unique event number within a particular study. The parameters allow defining the structure of each event data that is to be recorded. An event is defined as a specific state of a logical IO and given a unique event # for a particular study. The parameters are related to a particular s…

Full description and source information

Identification

Identifier and names

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

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

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

SNMP properties

Value type
SEQUENCE OF DcmEventConfigEntry
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.

dcmEventConfigTable OBJECT-TYPE
 SYNTAX   SEQUENCE OF DcmEventConfigEntry
 ACCESS   not-accessible
 STATUS   optional
 DESCRIPTION
 "This table maps logical IO’s to a unique event number within a particular
study. The parameters allow defining the structure of each event data that is
to be recorded. An event is defined as a specific state of a logical IO and
given a unique event # for a particular study. The parameters are related to
a particular study number to allow for multiple structures for the same input.
An IO event record as stored in the data portion of an event data packet would
consist of an Event # (dcmEventNum), Event Value (# of bits specified by
dcmEventValueSize), Timestamp (# of bits specified by dcmTimestampSize). The
size of the IO event would be the sum of the Event # Size
(dcmEventNumberSize), Event Value Size (dcmEventValueSize) and the
Timestampsize (dcmTimestampSize).
Therefore to decipher the bitstream in an event record, the       first x bits
(dcmEventNumberSize) of each data element would identify the Event Number and
this table would define how many bits follow for the event value and event
timestamp.
This is a single-indexed table. The index is assigned sequentially and the
table requires row administration. There shall be one row in this table for
each event # mapped to an event study.
The table can be managed thru the dcmEventConfigRowAdmin object.”
::= {dcmStudyDataSetup 20}

Meaning

Descriptions

1 unique

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

This table maps logical IO’s to a unique event number within a particular study. The parameters allow defining the structure of each event data that is to be recorded. An event is defined as a specific state of a logical IO and given a unique event # for a particular study. The parameters are related to a particular study number to allow for multiple structures for the same input. An IO event record as stored in the data portion of an event data packet would consist of an Event # (dcmEventNum), Event Value (# of bits specified by dcmEventValueSize), Timestamp (# of bits specified by dcmTimestampSize). The size of the IO event would be the sum of the Event # Size (dcmEventNumberSize), Event Value Size (dcmEventValueSize) and the Timestampsize (dcmTimestampSize). Therefore to decipher the bitstream in an event record, the first x bits (dcmEventNumberSize) of each data element would identify the Event Number and this table would define how many bits follow for the event value and event timestamp. This is a single-indexed table. The index is assigned sequentially and the table requires row administration. There shall be one row in this table for each event # mapped to an event study. The table can be managed thru the dcmEventConfigRowAdmin object.

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

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

Status in source: optional.

Names: dcmEventConfigTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dcmEventConfigTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "DcmEventConfigEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"",
    "This",
    "table",
    "maps",
    "logical",
    "IO",
    "’",
    "s",
    "to",
    "a",
    "unique",
    "event",
    "number",
    "within",
    "a",
    "particular",
    "study",
    ".",
    "The",
    "parameters",
    "allow",
    "defining",
    "the",
    "structure",
    "of",
    "each",
    "event",
    "data",
    "that",
    "is",
    "to",
    "be",
    "recorded",
    ".",
    "An",
    "event",
    "is",
    "defined",
    "as",
    "a",
    "specific",
    "state",
    "of",
    "a",
    "logical",
    "IO",
    "and",
    "given",
    "a",
    "unique",
    "event",
    "#",
    "for",
    "a",
    "particular",
    "study",
    ".",
    "The",
    "parameters",
    "are",
    "related",
    "to",
    "a",
    "particular",
    "study",
    "number",
    "to",
    "allow",
    "for",
    "multiple",
    "structures",
    "for",
    "the",
    "same",
    "input",
    ".",
    "An",
    "IO",
    "event",
    "record",
    "as",
    "stored",
    "in",
    "the",
    "data",
    "portion",
    "of",
    "an",
    "event",
    "data",
    "packet",
    "would",
    "consist",
    "of",
    "an",
    "Event",
    "#",
    "(",
    "dcmEventNum",
    ")",
    ",",
    "Event",
    "Value",
    "(",
    "#",
    "of",
    "bits",
    "specified",
    "by",
    "dcmEventValueSize",
    ")",
    ",",
    "Timestamp",
    "(",
    "#",
    "of",
    "bits",
    "specified",
    "by",
    "dcmTimestampSize",
    ")",
    ".",
    "The",
    "size",
    "of",
    "the",
    "IO",
    "event",
    "would",
    "be",
    "the",
    "sum",
    "of",
    "the",
    "Event",
    "#",
    "Size",
    "(",
    "dcmEventNumberSize",
    ")",
    ",",
    "Event",
    "Value",
    "Size",
    "(",
    "dcmEventValueSize",
    ")",
    "and",
    "the",
    "Timestampsize",
    "(",
    "dcmTimestampSize",
    ")",
    ".",
    "Therefore",
    "to",
    "decipher",
    "the",
    "bitstream",
    "in",
    "an",
    "event",
    "record",
    ",",
    "the",
    "first",
    "x",
    "bits",
    "(",
    "dcmEventNumberSize",
    ")",
    "of",
    "each",
    "data",
    "element",
    "would",
    "identify",
    "the",
    "Event",
    "Number",
    "and",
    "this",
    "table",
    "would",
    "define",
    "how",
    "many",
    "bits",
    "follow",
    "for",
    "the",
    "event",
    "value",
    "and",
    "event",
    "timestamp",
    ".",
    "This",
    "is",
    "a",
    "single-indexed",
    "table",
    ".",
    "The",
    "index",
    "is",
    "assigned",
    "sequentially",
    "and",
    "the",
    "table",
    "requires",
    "row",
    "administration",
    ".",
    "There",
    "shall",
    "be",
    "one",
    "row",
    "in",
    "this",
    "table",
    "for",
    "each",
    "event",
    "#",
    "mapped",
    "to",
    "an",
    "event",
    "study",
    ".",
    "The",
    "table",
    "can",
    "be",
    "managed",
    "thru",
    "the",
    "dcmEventConfigRowAdmin",
    "object",
    ".",
    "”",
    "::=",
    "{",
    "dcmStudyDataSetup",
    "20",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "DcmEventConfigEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "This table maps logical IO’s to a unique event number within a particular study. The parameters allow defining the structure of each event data that is to be recorded. An event is defined as a specific state of a logical IO and given a unique event # for a particular study. The parameters are related to a particular study number to allow for multiple structures for the same input. An IO event record as stored in the data portion of an event data packet would consist of an Event # (dcmEventNum), Event Value (# of bits specified by dcmEventValueSize), Timestamp (# of bits specified by dcmTimestampSize). The size of the IO event would be the sum of the Event # Size (dcmEventNumberSize), Event Value Size (dcmEventValueSize) and the Timestampsize (dcmTimestampSize). Therefore to decipher the bitstream in an event record, the first x bits (dcmEventNumberSize) of each data element would identify the Event Number and this table would define how many bits follow for the event value and event timestamp. This is a single-indexed table. The index is assigned sequentially and the table requires row administration. There shall be one row in this table for each event # mapped to an event study. The table can be managed thru the dcmEventConfigRowAdmin object."
    ],
    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.20.1 dcmEventConfigEntry88

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.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
1.3.6.1.4.1.1206.4.2.9.6.30 dcmDataStructureTable18