< < 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
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Center Developer	Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Center Developer	Data Distribution System Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Connected Vehicle Roadside Equipment Developer	Connected Vehicle Roadside Equipment	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Connected Vehicle Roadside Equipment Developer	Data Distribution System Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Data Distribution System Developer	Center Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Data Distribution System Developer	Connected Vehicle Roadside Equipment Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Data Distribution System Developer	Data Distribution System	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Data Distribution System Developer	Other Data Distribution Systems Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Data Distribution System Developer	Personal Information Device Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Data Distribution System Developer	Vehicle OBE Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Other Data Distribution Systems Developer	Data Distribution System Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Other Data Distribution Systems Developer	Other Data Distribution Systems	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Personal Information Device Developer	Data Distribution System Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Personal Information Device Developer	Personal Information Device	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Vehicle OBE Developer	Data Distribution System Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Vehicle OBE Developer	Vehicle OBE	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Center Installer	Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Center Owner	Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Center Owner	Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Connected Vehicle Roadside Equipment Installer	Connected Vehicle Roadside Equipment	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Data Distribution System Installer	Data Distribution System	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Data Distribution System Owner	Data Distribution System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Data Distribution System Owner	Data Distribution System Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Other Data Distribution Systems Installer	Other Data Distribution Systems	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Other Data Distribution Systems Owner	Other Data Distribution Systems Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Other Data Distribution Systems Owner	Other Data Distribution Systems Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Personal Information Device Installer	Personal Information Device	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Personal Information Device Owner	Personal Information Device Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Personal Information Device Owner	Personal Information Device Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Vehicle OBE Installer	Vehicle OBE	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Vehicle OBE Owner	Vehicle OBE Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Vehicle OBE Owner	Vehicle OBE Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Center Maintainer	Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the �maintains� role typically is delegated authority by the entity with the �Owns� or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Center Manager	Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Center Owner	Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Center Owner	Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Center Owner	Data Distribution System Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Center Supplier	Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Connected Vehicle Roadside Equipment Maintainer	Connected Vehicle Roadside Equipment	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the �maintains� role typically is delegated authority by the entity with the �Owns� or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Connected Vehicle Roadside Equipment Manager	Connected Vehicle Roadside Equipment	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Connected Vehicle Roadside Equipment Owner	Data Distribution System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Connected Vehicle Roadside Equipment Supplier	Connected Vehicle Roadside Equipment Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Data Distribution System Maintainer	Data Distribution System	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the �maintains� role typically is delegated authority by the entity with the �Owns� or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Data Distribution System Manager	Data Distribution System	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Data Distribution System Manager	Data Distribution System Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Data Distribution System Operator	Data Distribution System	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Data Distribution System Owner	Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Data Distribution System Owner	Connected Vehicle Roadside Equipment Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Data Distribution System Owner	Data Distribution System Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Data Distribution System Owner	Data Distribution System Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Data Distribution System Owner	Other Data Distribution Systems Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Data Distribution System Owner	Personal Information Device Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Data Distribution System Owner	Vehicle OBE Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Data Distribution System Supplier	Data Distribution System Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Other Data Distribution Systems Maintainer	Other Data Distribution Systems	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the �maintains� role typically is delegated authority by the entity with the �Owns� or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Other Data Distribution Systems Manager	Other Data Distribution Systems	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Other Data Distribution Systems Owner	Data Distribution System Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Other Data Distribution Systems Owner	Other Data Distribution Systems Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Other Data Distribution Systems Owner	Other Data Distribution Systems Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Other Data Distribution Systems Supplier	Other Data Distribution Systems Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Personal Information Device Maintainer	Personal Information Device	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the �maintains� role typically is delegated authority by the entity with the �Owns� or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Personal Information Device Manager	Personal Information Device	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Personal Information Device Owner	Data Distribution System Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Personal Information Device Owner	Personal Information Device Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Personal Information Device Owner	Personal Information Device Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Personal Information Device Supplier	Personal Information Device Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Vehicle OBE Maintainer	Vehicle OBE	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the �maintains� role typically is delegated authority by the entity with the �Owns� or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Vehicle OBE Manager	Vehicle OBE	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Vehicle OBE Owner	Data Distribution System Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Vehicle OBE Owner	Vehicle OBE Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Vehicle OBE Owner	Vehicle OBE Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Vehicle OBE Supplier	Vehicle OBE Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Center	Center Data Collection	10.6.1.2	Manage Center Archive Data
Center	Center Data Subscription Management	10.6.1.1	Provide Transportation Center Data Sharing Services
Connected Vehicle Roadside Equipment	RSE Data Subscription Management	10.6.2.2	Provide Field Data Sharing Services
Data Distribution System	DDS Data Access Management	10.2.1	Manage Data Access Services
		10.2.3	Support Data Distribution Services
		10.2.4	Provide Data Distribution System Operator Interface
	DDS Data Collection and Aggregation	10.2.2	Provide Data Collection and Aggregation
		10.2.3	Support Data Distribution Services
		10.2.4	Provide Data Distribution System Operator Interface
Personal Information Device	Personal Data Subscription Management	10.6.3.3	Provide Personal Data Sharing Services
Vehicle OBE	Vehicle Data Subscription Management	10.6.3.2	Provide Vehicle Data Sharing Services

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 security
D. Increase the accessibility and mobility of people and for freight;	Reduce congestion
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight;	Enhance integration and connectivity
J. Enhance travel and tourism.	Support travel and tourism

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
Increase the percent of transportation facilities whose owners share their traveler information with other agencies in the region to X percent by Y year.	Percent of transportation facilities whose owners share their traveler information with other agencies in the region.
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 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 subscribe to a data subscription service.
			02	The personal device shall send a data query to a data subscription service.
			03	The personal device shall receive published data from a data subscription service.
			04	The personal device shall 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 subscribe to a data subscription service.
			02	The vehicle shall send a data query to a data subscription service.
			03	The vehicle shall receive published data from a data subscription service.
			04	The vehicle shall 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 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
Source	Destination	Information Flow	Basis	Basis	Basis
Center	Data Distribution System	data provision	High	High	Moderate
Center	Data Distribution System	data provision	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
Center	Data Distribution System	data query	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 availability; if the flow is not satisfied the user may be become frustrated and seek a solution other than DDS. Thus MODERATE.
Center	Data Distribution System	data subscription	High	High	Moderate
Center	Data Distribution System	data subscription	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
Connected Vehicle Roadside Equipment	Data Distribution System	data provision	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
Connected Vehicle Roadside Equipment	Data Distribution System	data query	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 availability; if the flow is not satisfied 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
Connected Vehicle Roadside Equipment	Data Distribution System	data subscription	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
Data Distribution System	Center	data publication	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
Data Distribution System	Center	data query publication	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 availability; if the flow is not satisfied 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
Data Distribution System	Connected Vehicle Roadside Equipment	data publication	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
Data Distribution System	Connected Vehicle Roadside Equipment	data query publication	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 availability; if the flow is not satisfied 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
Data Distribution System	Data Distribution System Operator	DDS operations information presentation	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
Data Distribution System	Other Data Distribution Systems	data provision	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
Data Distribution System	Other Data Distribution Systems	data publication	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
Data Distribution System	Other Data Distribution Systems	data query	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 availability; if the flow is not satisfied 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
Data Distribution System	Other Data Distribution Systems	data query publication	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 availability; if the flow is not satisfied 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
Data Distribution System	Other Data Distribution Systems	data subscription	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
Data Distribution System	Personal Information Device	data publication	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
Data Distribution System	Personal Information Device	data query publication	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 availability; if the flow is not satisfied 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
Data Distribution System	Vehicle OBE	data publication	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
Data Distribution System	Vehicle OBE	data query publication	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 availability; if the flow is not satisfied 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
Data Distribution System Operator	Data Distribution System	DDS operator input	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
Other Data Distribution Systems	Data Distribution System	data provision	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
Other Data Distribution Systems	Data Distribution System	data publication	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
Other Data Distribution Systems	Data Distribution System	data query	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 availability; if the flow is not satisfied 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
Other Data Distribution Systems	Data Distribution System	data query publication	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 availability; if the flow is not satisfied 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
Other Data Distribution Systems	Data Distribution System	data subscription	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
Personal Information Device	Data Distribution System	data provision	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
Personal Information Device	Data Distribution System	data query	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 availability; if the flow is not satisfied 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
Personal Information Device	Data Distribution System	data subscription	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
Vehicle OBE	Data Distribution System	data provision	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
Vehicle OBE	Data Distribution System	data query	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 availability; if the flow is not satisfied 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
Vehicle OBE	Data Distribution System	data subscription	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
CTI 4001 RSU	Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589)	Connected Vehicle Roadside Equipment

System Requirements

System Requirement		Need
001	The system shall collect operational data from other Centers.	03	Data Distribution Operators need to be able to exchange data with other data distribution systems.
002	The system shall support peer-to-peer communications with other regional centers to support operational data sharing.	03	Data Distribution Operators need to be able to exchange data with other data distribution systems.
003	The system shall allow users to sign up for a data subscription service to access data held by the center.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
004	The system shall send data to users based upon a set of rules governing the data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
004		02	System Operators need to be able to provide data to a geographically selected area.
005	The system shall allow center personnel to manage the subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
006	The system shall collect data from other centers to be used as part of the data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
007	The system shall maintain a catalog of available data that can be accessed by users of the data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
008	The system shall support peer-to-peer communications with other regional centers to support operational data sharing.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
009	The system shall support a data subscription service that manages the necessary user information and rules that govern the data subscriptions.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
010	The system shall provide a data subscription service to end user devices.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
011	The system shall support the ability for end user devices to sign up for a data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
012	The system shall send subscription data to the end user device based upon a set of rules governing the data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
013	The system shall accept a query for subscription data from end user devices and forwarding that query to the center responsible for the data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
014	The system shall distribute to personal devices data which has been validated, aggregated, integrated, and sanitized.	02	System Operators need to be able to provide data to a geographically selected area.
015	The system shall distribute to Vehicles data which has been validated, aggregated, integrated, and sanitized.	02	System Operators need to be able to provide data to a geographically selected area.
016	The system shall distribute to other Centers data which has been validated, aggregated, integrated, and sanitized.	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.
017	The system shall distribute to Vehicles broadcast data which has been validated, aggregated, integrated, and sanitized.	02	System Operators need to be able to provide data to a geographically selected area.
018	The system shall distribute to Connected Vehicle Roadside Equipment data which has been validated, aggregated, integrated, and sanitized.	02	System Operators need to be able to provide data to a geographically selected area.
019	The system shall provide metadata parameters (geographic area, data content type, time) as filters for subscription.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
020	The system shall provide data consumers with a mechanism for throttling (or reducing) the data they receive as part of subscriptions.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
021	The system shall provide data consumers with a mechanism for subscribing to data received by the Center.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
022	The system shall provide a mechanism for the operator to modify data subscriptions.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
023	The system shall collect data from Vehicles.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
024	The system shall provide data collection parameters to Vehicles.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
025	The system shall collect data from Connected Vehicle Roadside Equipment.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
026	The system shall provide data collection parameters to Connected Vehicle Roadside Equipment.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
027	The system shall collect data from other Centers.	03	Data Distribution Operators need to be able to exchange data with other data distribution systems.
028	The system shall collect data from other Personal Devices.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
029	The system shall perform 'VISA' functions on incoming data (VISA = Validation, Integration, Sanitization, Aggregation).	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.
030	The system shall provide a mechanism for the operator to control data collection parameters.	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.
031	The system shall provide a mechanism for the operator to modify VISA functions.	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.
032	The system shall subscribe to a data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
033	The system shall send a data query to a data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
034	The system shall receive published data from a data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
035	The system shall present data from a data subscription service to the traveler.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
036	The system shall receive published data from a data subscription service.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.
037	The system shall present data from a data subscription service to the driver.	01	System Operators, Vehicle Operators, and PID Operators need to be able to request and receive information without establishing formal relationships with data providers.