Link Type: Wide Area Wireless

Vehicle OBE --> Data Distribution System:
data subscription

Definitions

data subscription (Information Flow): Data subscription includes those dialogs necessary to determine what data is available for subscription/query, and also the dialogs necessary to create or modify data subscriptions/queries.

Vehicle OBE (Source Physical Object): The Vehicle On-Board Equipment (OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The Vehicle OBE includes general capabilities that apply to passenger cars, trucks, and motorcycles. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

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

Included In

This Triple is in the following Service Packages:

This Triple is in 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 over Wireless

Solution Description

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

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

IETF RFC 793
IP Alternatives
Access
Mind the gapMind the gapMind the gap
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 True
Cardinality Unicast
Initiator Source
Authenticable True
Encrypt True


Interoperability Description
National This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union).

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 or LOW integrity requirement, then this could be MODERATE or LOW, as appropriate. 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