Data Distribution System --> Other Data Distribution Systems:
data query
This triple is bi-directional. See also
Other Data Distribution Systems --> Data Distribution System: data query
Definitions
data query (Information Flow): Data query includes those dialogs necessary to determine what data is available for and also submit a query for near-term response.
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:
None |
Communication Solutions
- Data for Distribution (TBD) - Apache Kafka (44)
- Data for Distribution (TBD) - OASIS MQTT (50)
- Data for Distribution (TBD) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
OASIS MQTT DMP |
Facilities
OASIS MQTT |
Security
|
|
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 | 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 | Moderate | Moderate | |
Basis | Query flows imply the interests of the source. Observation of this information betrays the privacy of the requestor. Depending on the type of requestor and type of Query flows imply the interests of the source. Observation of this information betrays the privacy of the requestor. Depending on the type of requestor and type of information requested, this could be MODERATE.information requested, this could be MODERATE. | Query flows create long term relationships between source and DDS, and dictate what information the source receives. Corruption of this flow could have a significant impact on data reception; however, re-query should be a fairly simply process, justifying MODERATE and not HIGH. | Query flows need some level of abailability; if the flow is not satisifed the user may be become frustrated and seek a solution other than DDS. Thus MODERATE. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |