Data Distribution System --> ITS Object:
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.

ITS Object (Destination Physical Object): The general 'ITS Object' includes core capabilities common to any class of object.

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:

  • None

This Triple has the following triple relationships:

None

Communication Solutions

No communications solutions identified.

Characteristics

Characteristic Value
Time Context Recent
Spatial Context Regional
Acknowledgement True
Cardinality Unicast
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