ITS Roadway Equipment --> Archived Data System:
roadside archive data

Definitions

roadside archive data (Information Flow): A broad set of data derived from roadside sensors that includes current traffic conditions, environmental conditions, and any other data that can be directly collected by roadside sensors. This data also indicates the status of the sensors and reports of any identified sensor faults.

ITS Roadway Equipment (Source Physical Object): 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.

Archived Data System (Destination Physical Object): The 'Archived Data System' collects, archives, manages, and distributes data generated from ITS sources for use in transportation administration, policy evaluation, safety, planning, performance monitoring, program assessment, operations, and research applications. The data received is formatted and tagged with attributes that define the data source, conditions under which it was collected, data transformations, and other information (i.e. meta data) necessary to interpret the data. The archive can fuse ITS generated data with data from non-ITS sources and other archives to generate information products utilizing data from multiple functional areas, modes, and jurisdictions. The archive prepares data products that can serve as inputs to federal, state, and local data reporting systems. The 'Archived Data System' may reside within an operational center and provide focused access to a particular agency's data archives. Alternatively, it may operate as a distinct center that collects data from multiple agencies and sources and provides a general data warehouse service.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

None

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

US: NTCIP Data Collection - SNMPv1/TLS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: NTCIP Data Collection with those for I-F: SNMPv1/TLS. The US: NTCIP Data Collection standards include upper-layer standards required to implement center-to-field communications for data collection and monitoring of traffic characteristics (e.g., non-real-time data). The I-F: SNMPv1/TLS standards include lower-layer standards that define one way to retrofit basic security into SNMPv1 implementations (mainly in the US); however, this only secures the communications link and does not provide end-application security and is not recommended for new deployments.

ITS Application Entity
Mind the gap

NTCIP 1206
NTCIP 1209
Click gap icons for more info.
Mgmt

NTCIP 1201
Bundle: SNMPv1 MIB
Facilities

NTCIP 1206
NTCIP 1209
NTCIP 2301
Security
Mind the gapMind the gap

IETF RFC 8446
TransNet

IP Alternatives
IETF RFC 9293
Access
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Characteristic Value
Time Context Recent
Spatial Context Local
Acknowledgement True
Cardinality Unicast
Initiator Source
Authenticable True
Encrypt True


Interoperability Description
Local In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Moderate Moderate Low
Basis While this flow should not include any PII, as any PII in the underlying data should be stripped prior to being sent to an archive, this is not guaranteed. Even if PII is all removed prior, this flow is very large in scope and its compromise to unintended recipients may enable large scale data analysis that compromises personal information through circumstantial, aggregative or other combinatorial analysis. May include performance information that needs to be timely and correct so that errors may be identified and corrected. Large in scope so any errors effects may be magnified. Not a real time service, so intermittent availability should suffice.


Security Characteristics Value
Authenticable True
Encrypt True