Status in source: mandatory.
Names: dcmData
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcmData",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"This field contains the actual data that was recorded for this study. Although it is defined as an Octet String, it represents binary data. The type of data encoded in this column is identified in the configured study mapped to this row of this table (refer to Study Configuration Table). Binned data shall store a single octet value as the first byte in this field which indicates the number of octets used to store each bin count. The number and order of the bin counts stored are defined by the Binned Study Configuration Table (refer to Binned Data Bins Ordering C.3.1.8). Each recording interval is considered a binned data record. One or more binned data records may be stored in this field as specified by the number of records field in this row of this table. PVR data shall be stored as defined by the PVR Study Configuration Table. The PVR data (as defined in the PVR Study Configuration Table) associated with each vehicle is considered a vehicle record. One or more vehicle records may be stored in this field as specified by the number of records field in this row of this table. Event data shall be stored as defined by the Event Study Configuration Table. Each sensor event shall be considered an event record. One or more event records may be stored in this field as specified by the number of records field in this row of this table. ArrayParam data shall be stored as defined by the Array Parameter Change Record Table. It represents Array Parameters (refer to the Array Parameter Table) that have been changed in the dcm device either manually or automatically. One or more Array Parameter Change Records may be stored in this field as specified by the number of records field in this row. LogicalIOParam data shall be stored as defined by the Logical IO Parameter Change Record Table. It represents Logical IO Parameters (refer to the Logical IO Parameter Table) that have been changed in the dcm device either manually or automatically. One or more Logical IO Parameter Change Records may be stored in this field as specified by the number of records field in this row. LogData data shall be stored as defined by the Log Data Record Table. It represents information (as an octet string) with a time tag which the dcm device has written to the data file. One or more Log Records may be stored in this field as specified by the number of records field in this row. Refer to Annex C.3.1 for an example of Binned Record Data encoding, Annex C.3.2 for an example of PVR Record Data encoding and Annex C.3.3 for an example of Event Record Data encoding. This packet may contain data for one or more recording intervals. The length of the entire data section shall be encoded as the length field of this Octet String. If there is no data associated with the specified data packet (e.g. no vehicles traversed the sensor arrays during that time period), the number of records field shall be set to 0 and an ASN.1 NULL shall be placed in the data field.\"",
"::=",
"{",
"dcmDataStructureEntry",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"This field contains the actual data that was recorded for this study. Although it is defined as an Octet String, it represents binary data. The type of data encoded in this column is identified in the configured study mapped to this row of this table (refer to Study Configuration Table). Binned data shall store a single octet value as the first byte in this field which indicates the number of octets used to store each bin count. The number and order of the bin counts stored are defined by the Binned Study Configuration Table (refer to Binned Data Bins Ordering C.3.1.8). Each recording interval is considered a binned data record. One or more binned data records may be stored in this field as specified by the number of records field in this row of this table. PVR data shall be stored as defined by the PVR Study Configuration Table. The PVR data (as defined in the PVR Study Configuration Table) associated with each vehicle is considered a vehicle record. One or more vehicle records may be stored in this field as specified by the number of records field in this row of this table. Event data shall be stored as defined by the Event Study Configuration Table. Each sensor event shall be considered an event record. One or more event records may be stored in this field as specified by the number of records field in this row of this table. ArrayParam data shall be stored as defined by the Array Parameter Change Record Table. It represents Array Parameters (refer to the Array Parameter Table) that have been changed in the dcm device either manually or automatically. One or more Array Parameter Change Records may be stored in this field as specified by the number of records field in this row. LogicalIOParam data shall be stored as defined by the Logical IO Parameter Change Record Table. It represents Logical IO Parameters (refer to the Logical IO Parameter Table) that have been changed in the dcm device either manually or automatically. One or more Logical IO Parameter Change Records may be stored in this field as specified by the number of records field in this row. LogData data shall be stored as defined by the Log Data Record Table. It represents information (as an octet string) with a time tag which the dcm device has written to the data file. One or more Log Records may be stored in this field as specified by the number of records field in this row. Refer to Annex C.3.1 for an example of Binned Record Data encoding, Annex C.3.2 for an example of PVR Record Data encoding and Annex C.3.3 for an example of Event Record Data encoding. This packet may contain data for one or more recording intervals. The length of the entire data section shall be encoded as the length field of this Octet String. If there is no data associated with the specified data packet (e.g. no vehicles traversed the sensor arrays during that time period), the number of records field shall be set to 0 and an ASN.1 NULL shall be placed in the data field."
],
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)
Related source files and packages:
Show more related files and packages
- 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)
Related source files and packages: