< < SU02 : SU03 : SU04 > >

SU03: Data Distribution

This service package manages the distribution of data from data providers to data consumers and protects those data from unauthorized access. It informs data providers of how to provide data, manages data subscriptions, and provides data forwarding capabilities. The service package also maintains a directory of System Users that want data and supports multiple distribution mechanisms including publish-subscribe and directly from data provider to data consumer. It allows data consumers to specify (and change the specification of) data they wish to receive.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Center Manager Center Manages
Center Owner Center Owns
Center Owner Center Manager Operations Agreement
Center Owner Data Distribution System Owner Information Exchange Agreement
Center Supplier Center Owner Warranty
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Owns
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Data Distribution System Owner Information Provision Agreement
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
Data Distribution System Manager Data Distribution System Manages
Data Distribution System Manager Data Distribution System Operator System Usage Agreement
Data Distribution System Operator Data Distribution System Operates
Data Distribution System Owner Center Owner Information Exchange Agreement
Data Distribution System Owner Data Distribution System Owns
Data Distribution System Owner Data Distribution System Manager Operations Agreement
Data Distribution System Owner Other Data Distribution Systems Owner Information Exchange Agreement
Data Distribution System Supplier Data Distribution System Owner Warranty
Other Data Distribution Systems Manager Other Data Distribution Systems Manages
Other Data Distribution Systems Owner Data Distribution System Owner Information Exchange Agreement
Other Data Distribution Systems Owner Other Data Distribution Systems Owns
Other Data Distribution Systems Owner Other Data Distribution Systems Manager Operations Agreement
Other Data Distribution Systems Supplier Other Data Distribution Systems Owner Warranty
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Owner Personal Information Device Owns
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Vehicle OBE Manager Vehicle OBE Manages
Vehicle OBE Owner Vehicle OBE Owns
Vehicle OBE Owner Vehicle OBE Manager Operations Agreement
Vehicle OBE Supplier Vehicle OBE Owner Warranty

Maintenance Stage Roles and Relationships

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Center Center This general physical object is used to model core capabilities that are common to any center.
Connected Vehicle Roadside Equipment Field 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Data Distribution System Support The 'Data Distribution System' collects, processes, and distributes ITS data, connecting data producers with data consumers and facilitating data exchange.
Data Distribution System Operator Support The 'Data Distribution System Operator' represents the person or people that monitor and manage the data services provided by the Data Distribution System (DDS). These personnel manage and monitor the systems that support the publish/subscribe services of the DDS.
Other Data Distribution Systems Support 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.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment.
Vehicle OBE Vehicle 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.

Includes Functional Objects:

Functional Object Description Physical Object
Center Data Collection 'Center Data Collection' collects and stores information that is created in the course of center operations. This data can be used directly by operations personnel or it can be made available to other data users and archives in the region. Center
Center Data Subscription Management 'Center Data Subscription Management' manages data subscriptions for an end user. It provides access to a catalog of available data, manages the necessary user information and rules that govern the data subscriptions, supports communications with data providers to collect data per the subscription rules, and makes the data available to the end user. It provides the local user interface through which a user can specify and manage subscriptions. It supports different mechanisms for collecting subscribed data for the end-user including one-time query-response as well as publish-subscribe services. Center
DDS Data Access Management 'DDS Data Access Management' defines the access mechanisms, structures and restrictions for inbound (from providers) and outbound (to consumers) data. Data Distribution System
DDS Data Collection and Aggregation 'DDS Data Collection and Aggregation' collects data 'deposits' from producers including meta data such as the generation location and time. It authenticates and validates the data deposits and logs all associated meta data. Authenticated, valid data is bundled based on information type and location and made available as data products to consumers who are interested in the data. It establishes delivery parameters for data consumers that subscribe based on parameters including content type and geographic region of interest and delivers data to consumers based on these parameters. Data Distribution System
Personal Data Subscription Management 'Personal Data Subscription Management' manages data subscriptions for an end user. It provides access to a catalog of available data, manages the necessary user information and rules that govern the data subscriptions, supports communications with data providers to collect data per the subscription rules, and makes the data available to the end user. It provides the local user interface through which a user can specify and manage subscriptions. It supports different mechanisms for collecting data for the end-user including one-time query-response as well as publish-subscribe services. Personal Information Device
RSE Data Subscription Management 'RSE Data Subscription Management' manages data subscriptions for an RSE. It provides access to a catalog of available data, manages the necessary identification information and rules that govern the data subscriptions, supports communications with data providers to collect data per the subscription rules, and makes the data available to other RSE applications. It supports different mechanisms for collecting data including one-time query-response as well as publish-subscribe services. Connected Vehicle Roadside Equipment
Vehicle Data Subscription Management 'Vehicle Data Subscription Management' manages data subscriptions for an end user. It provides access to a catalog of available data, manages the necessary user information and rules that govern the data subscriptions, supports communications with data providers to collect data per the subscription rules, and makes the data available to the end user. It provides the local user interface through which a user can specify and manage subscriptions. It supports different mechanisms for collecting data for the end-user including one-time query-response as well as publish-subscribe services. Vehicle OBE

Includes Information Flows:

Information Flow Description
data provision Data provision provides the source material for a publish-subscribe or query-retrieval data distribution scheme. This is the 1 of the 1:N data distribution architecture. This flow is a super-flow; it does not define data elements but is inclusive of any flow implemented using publish-subscribe or query-retrieval methods.
data publication 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 query Data query includes those dialogs necessary to determine what data is available for and also submit a query for near-term response.
data query publication Data query publication includes those dialogs necessary to satisfy the response portion of a query-response action using the data distribution architecture. The information content varies widely based on available content and the query, 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 subscription 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.
DDS operations information presentation Presentation of information to the DDS Operator including current operational status of the Data Distribution System.
DDS operator input User input from the DDS operator including requests to monitor current system operation and inputs to affect system operation.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
C. Increase the security of the transportation system for motorized and nonmotorized users; Improve the security of the transportation system

Associated Objective Categories

Objective Category
Security: Crime
Security: Terrorism, Natural Disasters, and Hazardous Material Incidents
Traveler Information: Data Collection and Sharing on Travel Conditions

Associated Objectives and Performance Measures

Objective Performance Measure
Enhance tracking and monitoring of sensitive Hazmat shipments Number of Hazmat shipments tracked in real-time
Reduce exposure due to Hazmat & homeland security incidents Homeland security incident response time
Reduce exposure due to Hazmat & homeland security incidents Number of Hazmat incidents
Reduce exposure due to Hazmat & homeland security incidents Number of homeland security incidents
Reduce security risks to motorists and travelers Number of critical sites with security surveillance
Reduce security risks to motorists and travelers Number of security incidents on roadways
Reduce security risks to transit passengers and transit vehicle operators Number of security incidents at transit facilities
Reduce security risks to transit passengers and transit vehicle operators Number of security incidents on transit vehicles
Reduce security risks to transit passengers and transit vehicle operators Number of transit facilities and vehicles under security surveillance
Reduce security risks to transportation infrastructure Number of critical sites with hardened security enhancements
Reduce security risks to transportation infrastructure Number of critical sites with security surveillance
Reduce security risks to transportation infrastructure Number of security incidents on transportation infrastructure


 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers. Center Data Subscription Management 02 The center shall allow users to sign up for a data subscription service to access data held by the center.
03 The center shall be able to send data to users based upon a set of rules governing the data subscription service.
04 The center shall allow center personnel to manage the subscription service.
05 The center shall be capable of collecting data from other centers to be used as part of the data subscription service.
06 The center shall maintain a catalog of available data that can be accessed by users of the data subscription service.
07 The center shall support peer-to-peer communications with other regional centers to support operational data sharing. 
08 The center shall support a data subscription service that manages the necessary user information and rules that govern the data subscriptions.
DDS Data Access Management 06 The data support center shall provide metadata parameters (geographic area, data content type, time) as filters for subscription.
07 The data support center shall provide data consumers with a mechanism for throttling (or reducing) the data they receive as part of subscriptions.
08 The data support center shall provide data consumers with a mechanism for subscribing to data received by the Center.
09 The data support center shall provide a mechanism for the operator to modify data subscriptions.
DDS Data Collection and Aggregation 01 The data support center shall collect data from Vehicles.
02 The data support center shall provide data collection parameters to Vehicles.
03 The data support center shall collect data from Connected Vehicle Roadside Equipment.
04 The data support center shall provide data collection parameters to Connected Vehicle Roadside Equipment.
06 The data support center shall collect data from other Personal Devices.
Personal Data Subscription Management 01 The personal device shall be able to subscribe to a data subscription service.
02 The personal device shall be able to send a data query to a data subscription service.
03 The personal device shall be able to receive published data from a data subscription service.
04 The personal device shall be able to present data from a data subscription service to the traveler.
RSE Data Subscription Management 01 The field element shall be capable of providing a data subscription service to end user devices.
02 The field element shall support the ability for end user devices to sign up for a data subscription service.
03 The field element shall be capable of sending subscription data to the end user device based upon a set of rules governing the data subscription service.
04 The field element shall be capable of accepting a query for subscription data from end user devices and forwarding that query to the center responsible for the data subscription service.
Vehicle Data Subscription Management 01 The vehicle shall be able to subscribe to a data subscription service.
02 The vehicle shall be able to send a data query to a data subscription service.
03 The vehicle shall be able to receive published data from a data subscription service.
04 The vehicle shall be able to present data from a data subscription service to the driver.
02 System Operators need to be able to provide data to a geographically selected area. Center Data Subscription Management 03 The center shall be able to send data to users based upon a set of rules governing the data subscription service.
DDS Data Access Management 01 The data support center shall distribute to personal devices data which has been validated, aggregated, integrated, and sanitized.
02 The data support center shall distribute to Vehicles data which has been validated, aggregated, integrated, and sanitized.
04 The data support center shall distribute to Vehicles broadcast data which has been validated, aggregated, integrated, and sanitized.
05 The data support center shall distribute to Connected Vehicle Roadside Equipment data which has been validated, aggregated, integrated, and sanitized.
03 Data Distribution Operators need to be able to exchange data with other data distribution systems. Center Data Collection 05 The Center shall collect operational data from other Centers.
Center Data Subscription Management 01 The center shall support peer-to-peer communications with other regional centers to support operational data sharing.
DDS Data Collection and Aggregation 05 The data support center shall collect data from other Centers.
04 Data Distribution Operators need to be able to establish and maintain data processing algorithms, rules and related metadata, including all those processes related to Validation, Integration, Sanitization, and Aggregation. DDS Data Access Management 03 The data support center shall distribute to other Centers data which has been validated, aggregated, integrated, and sanitized.
DDS Data Collection and Aggregation 07 The data support center shall perform 'VISA' functions on incoming data (VISA = Validation, Integration, Sanitization, Aggregation).
08 The data support center shall provide a mechanism for the operator to control data collection parameters.
09 The data support center shall provide a mechanism for the operator to modify VISA functions.

Related Sources

Document Name Version Publication Date
Core System Concept of Operations (ConOps) Final revE 10/24/2011
ITS User Services Document 1/1/2005
SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods 8/15/2014


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Center High High Moderate Class 4
Connected Vehicle Roadside Equipment High High Moderate Class 4
Data Distribution System High High Moderate Class 4
Other Data Distribution Systems High High Moderate Class 4
Personal Information Device High High Moderate Class 4
Vehicle OBE High High Moderate Class 4



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Center Data Distribution System data provision High High Moderate
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.
Center Data Distribution System data query High Moderate Moderate
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. 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.
Center Data Distribution System data subscription High High Moderate
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.
Connected Vehicle Roadside Equipment Data Distribution System data provision High High Moderate
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.
Connected Vehicle Roadside Equipment Data Distribution System data query High Moderate Moderate
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. 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.
Connected Vehicle Roadside Equipment Data Distribution System data subscription High High Moderate
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.
Data Distribution System Center data publication High High Moderate
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.
Data Distribution System Center data query publication High High Moderate
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. 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.
Data Distribution System Connected Vehicle Roadside Equipment data publication High High Moderate
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.
Data Distribution System Connected Vehicle Roadside Equipment data query publication High High Moderate
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. 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.
Data Distribution System Data Distribution System Operator DDS operations information presentation Moderate High High
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Data Distribution System Other Data Distribution Systems data provision High High Moderate
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.
Data Distribution System Other Data Distribution Systems data publication High High Moderate
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.
Data Distribution System Other Data Distribution Systems data query High Moderate Moderate
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.
Data Distribution System Other Data Distribution Systems data query publication High High Moderate
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. 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.
Data Distribution System Other Data Distribution Systems data subscription High High Moderate
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.
Data Distribution System Personal Information Device data publication High High Moderate
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.
Data Distribution System Personal Information Device data query publication High High Moderate
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. 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.
Data Distribution System Vehicle OBE data publication High High Moderate
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.
Data Distribution System Vehicle OBE data query publication High High Moderate
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. 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.
Data Distribution System Operator Data Distribution System DDS operator input Moderate High High
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Other Data Distribution Systems Data Distribution System data provision High High Moderate
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.
Other Data Distribution Systems Data Distribution System data publication High High Moderate
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.
Other Data Distribution Systems Data Distribution System data query High Moderate Moderate
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. 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.
Other Data Distribution Systems Data Distribution System data query publication High High Moderate
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. 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.
Other Data Distribution Systems Data Distribution System data subscription High High Moderate
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.
Personal Information Device Data Distribution System data provision High High Moderate
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.
Personal Information Device Data Distribution System data query High Moderate Moderate
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. 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.
Personal Information Device Data Distribution System data subscription High High Moderate
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.
Vehicle OBE Data Distribution System data provision High High Moderate
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.
Vehicle OBE Data Distribution System data query High Moderate Moderate
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. 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.
Vehicle OBE Data Distribution System data subscription High High Moderate
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.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
USDOT RSU Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment