Wireless Communications Provider System --> Transportation Information Center:
comm-derived travel performance data

Definitions

comm-derived travel performance data (Information Flow): Data that can be used to derive travel time data and other transportation performance measures. Data provided may be raw IDs, locations, and timestamps, derived link travel times, speeds, or other data that has been collected and derived by a communications provider from its mobile customers.

Wireless Communications Provider System (Source Physical Object): The 'Wireless Communications Provider System' represents the systems used by wireless communications providers to provide data and voice services that collectively serve billions of mobile users around the world. As they serve their customers, these providers collect location information from their mobile customers as they use communications services while they traverse the transportation network. This information may be shared with transportation providers, in aggregate and without personal information, to provide a rich data source that may be used in conjunction with other data to monitor transportation network use and performance.

Use this physical object where the relationship with the communications provider is limited to use of service provider-derived transportation network performance data. Where wireless communications services are purchased and used to support wireless interfaces included in an ITS architecture, see 'ITS Communications Equipment', which can represent use of purchased communications services as part of an overall ITS communications network.

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:

This Triple has the following triple relationships:

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

Data for Distribution (TBD) - OASIS AMQP

Solution Description

This solution is used within Canada, the E.U. and the U.S.. It combines standards associated with Data for Distribution (TBD) with those for OASIS AMQP. 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 AMQP standards include lower-layer standards that support data distribution of specific types of data.

ITS Application Entity
Mind the gapMind the gap

Development needed
Click gap icons for more info.

Mgmt
Mind the gapMind the gap

Development needed
Facilities
Mind the gapMind the gap

OASIS AMQP
Security
Mind the gapMind the gap
TransNet
Access

Internet Subnet Alternatives
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 Now
Spatial Context Regional
Acknowledgement False
Cardinality Unicast
Initiator Source
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 Not Applicable Moderate Low
Basis This data is intended for public use and is presumed to already be sanitized. Data should be correct and available, but this is one of many sources of travel-time data. Installations not relying on this source as their primary means for acquiring travel time data could lower this to LOW. Data should be correct and available, but this is one of many sources of travel-time data. Installations relying on this source as their primary means for acquiring travel time data should elevate this to MODERATE.


Security Characteristics Value
Authenticable True
Encrypt False