Wireless Communications Provider System --> Traffic Management 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.
Traffic Management Center (Destination 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.
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
- EU: DATEX - DATEX Messaging (3)
- (None-Data) - Secure Internet (ITS) (43)
- (None-Data) - Apache Kafka (44)
- (None-Data) - OMG DDS (44)
- (None-Data) - OASIS MQTT (50)
- (None-Data) - OASIS AMQP (61)
- Data for Distribution (TBD) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
|
Click gap icons for more info.
|
||
Mgmt
|
Facilities
No Standard Needed |
Security
IETF RFC 8446 |
|
TransNet
|
|||
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 | 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 |