Traffic Management Center --> Transportation Information Center:
traffic image meta data

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

traffic image meta data (Information Flow): Meta data that describes traffic images. Traffic images (video) are in another flow.

Traffic Management Center (Source Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.

Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

None

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

traffic_image_meta_data_to_centers

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
Depends On	ITS Roadway Equipment	Traffic Management Center	traffic image meta data

Communication Solutions

EU: DATEX - DATEX Messaging (3)
US: TMDD - NTCIP Messaging (13)
(None-Data) - Secure Internet (ITS) (43)
Data for Distribution (TBD) - Apache Kafka (44)
Data for Distribution (TBD) - OMG DDS (44)
(None-Data) - OASIS MQTT (50)
Data for Distribution (TBD) - OASIS MQTT (50)
Data for Distribution (TBD) - OASIS AMQP (61)

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

Selected Solution

Data for Distribution (TBD) - OASIS MQTT

Solution Description

This solution is used within Australia, Canada and the U.S.. It combines standards associated with Data for Distribution (TBD) with those for OASIS MQTT. The Data for Distribution (TBD) standards include a placeholder for upper-layer standards necessary to define the data (elements and structures) necessary to complete a solution for the information flow based on data distribution technologies. The data standard will need to include a specific customization for the desired data distribution technology used (e.g., Kafka, DDS, etc.).. The OASIS MQTT standards include lower-layer standards that support data distribution of specific types of data.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt OASIS MQTT DMP	Facilities OASIS MQTT	Security IP Security Alternatives OASIS MQTT
	TransNet IP Alternatives Internet Transport Alternatives
	Access Internet Subnet Alternatives

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	Regional
Acknowledgement	False
Cardinality	Unicast
Initiator	Destination
Authenticable	True
Encrypt	False

Interoperability	Description
Regional	Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture).

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Low	Moderate	Moderate
Basis	Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW.	While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally.	While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Traffic Management Center --> Transportation Information Center:traffic image meta data