Data Distribution System --> Other Data Distribution Systems:
data publication

This triple is bi-directional. See also Other Data Distribution Systems --> Data Distribution System: data publication

Definitions

data publication (Information Flow): Data publication includes those dialogs necessary to satisfy the publication portion of a data distribution architecture. The information content varies widely based on available content and the subscription, but it generally includes information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.

Data Distribution System (Source Physical Object): The 'Data Distribution System' collects, processes, and distributes ITS data, connecting data producers with data consumers and facilitating data exchange.

Other Data Distribution Systems (Destination Physical Object): Representing another Data Distribution System, 'Other Data Distribution Systems' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) data distribution systems. It supports modeling of projects or regions that include multiple interconnected data distribution systems that together manage data distribution in the connected vehicle environment.

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) - Apache Kafka

Solution Description

This solution is used within the U.S.. It combines standards associated with Data for Distribution (TBD) with those for Apache Kafka. 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 Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.

Mgmt

Apache Zookeeper
Facilities
Mind the gapMind the gap

Apache Kafka
Apache Zookeeper
Security

IETF RFC 8446
TransNet

IP Alternatives
IETF RFC 9293
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 Recent
Spatial Context Regional
Acknowledgement False
Cardinality Multicast
Initiator Source
Authenticable True
Encrypt True


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 High High Moderate
Basis This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE or LOW confidentiality requirement, then this could be MODERATE or LOW, as appropriate. This value is derived from the specific flows satisfied by this super-flow. HIGH is set because some flows may require it. If the implementation includes flows with only a MODERATE integrity requirement, then this could be MODERATE. This value is derived from the specific flows are satisfied by this super-flow. MODERATE is set because some flows may require it. If the implementation includes flows with only a LOW availability requirement, then this could be LOW. HIGH is not considered; any flow requiring HIGH availability will not use DDS.


Security Characteristics Value
Authenticable True
Encrypt True