Other Transportation Information Centers --> Transportation Information Center:
incident information for public

This triple is bi-directional. See also Transportation Information Center --> Other Transportation Information Centers: incident information for public

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

incident information for public (Information Flow): Report of current desensitized incident information prepared for public dissemination.

Other Transportation Information Centers (Source Physical Object): Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant.

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:

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

fotic-incident_data

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

(None-Data) - OASIS MQTT

Solution Description

This solution is used within Australia, Canada and the U.S.. It combines standards associated with (None-Data) with those for OASIS MQTT. The (None-Data) standards include an unspecified set of standards at the upper layers. 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 Development needed 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	True
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	Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption.	Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result.	Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Other Transportation Information Centers --> Transportation Information Center:incident information for public