Parent Service Package: SU07
< < SU06.1 : SU07.1 : SU08.1 > >

SU07.1: ITS Communications Implementation

This 'implementation' is a holistic view of the SU07 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.

Relevant Regions:

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
ITS Communications Equipment MaintainerITS Communications Equipment Maintains
ITS Communications Equipment ManagerITS Communications Equipment Manages
ITS Communications Equipment ManagerITS Communications Equipment Operator System Usage Agreement
ITS Communications Equipment OperatorITS Communications Equipment Operates
ITS Communications Equipment OwnerITS Communications Equipment Maintainer System Maintenance Agreement
ITS Communications Equipment OwnerITS Communications Equipment Manager Operations Agreement
ITS Communications Equipment OwnerITS Object Maintainer Maintenance Data Exchange Agreement
ITS Communications Equipment OwnerITS Object User Service Usage Agreement
ITS Communications Equipment OwnerOther ITS Objects Maintainer Maintenance Data Exchange Agreement
ITS Communications Equipment OwnerOther ITS Objects User Service Usage Agreement
ITS Communications Equipment SupplierITS Communications Equipment Owner Warranty
ITS Object MaintainerITS Object Maintains
ITS Object ManagerITS Object Manages
ITS Object OwnerITS Communications Equipment Maintainer Maintenance Data Exchange Agreement
ITS Object OwnerITS Communications Equipment Operator Application Usage Agreement
ITS Object OwnerITS Communications Equipment Owner Expectation of Information Provision
ITS Object OwnerITS Communications Equipment User Service Usage Agreement
ITS Object OwnerITS Object Maintainer System Maintenance Agreement
ITS Object OwnerITS Object Manager Operations Agreement
ITS Object OwnerOther ITS Objects Maintainer Maintenance Data Exchange Agreement
ITS Object OwnerOther ITS Objects User Service Usage Agreement
ITS Object OwnerPathway Communications Unit Maintainer Maintenance Data Exchange Agreement
ITS Object OwnerPathway Communications Unit Operator Application Usage Agreement
ITS Object OwnerPathway Communications Unit User Service Usage Agreement
ITS Object OwnerRoadside Communications Unit Maintainer Maintenance Data Exchange Agreement
ITS Object OwnerRoadside Communications Unit Operator Application Usage Agreement
ITS Object OwnerRoadside Communications Unit User Service Usage Agreement
ITS Object OwnerWide Area Information Disseminator System Maintainer Maintenance Data Exchange Agreement
ITS Object OwnerWide Area Information Disseminator System Operator Application Usage Agreement
ITS Object OwnerWide Area Information Disseminator System Owner Expectation of Information Provision
ITS Object OwnerWide Area Information Disseminator System User Service Usage Agreement
ITS Object SupplierITS Object Owner Warranty
Other ITS Objects MaintainerOther ITS Objects Maintains
Other ITS Objects ManagerOther ITS Objects Manages
Other ITS Objects OwnerITS Communications Equipment Maintainer Maintenance Data Exchange Agreement
Other ITS Objects OwnerITS Communications Equipment Operator Application Usage Agreement
Other ITS Objects OwnerITS Communications Equipment Owner Expectation of Information Provision
Other ITS Objects OwnerITS Communications Equipment User Service Usage Agreement
Other ITS Objects OwnerITS Object Maintainer Maintenance Data Exchange Agreement
Other ITS Objects OwnerITS Object User Service Usage Agreement
Other ITS Objects OwnerOther ITS Objects Maintainer System Maintenance Agreement
Other ITS Objects OwnerOther ITS Objects Manager Operations Agreement
Other ITS Objects OwnerPathway Communications Unit Maintainer Maintenance Data Exchange Agreement
Other ITS Objects OwnerPathway Communications Unit Operator Application Usage Agreement
Other ITS Objects OwnerPathway Communications Unit User Service Usage Agreement
Other ITS Objects OwnerRoadside Communications Unit Maintainer Maintenance Data Exchange Agreement
Other ITS Objects OwnerRoadside Communications Unit Operator Application Usage Agreement
Other ITS Objects OwnerRoadside Communications Unit User Service Usage Agreement
Other ITS Objects SupplierOther ITS Objects Owner Warranty
Pathway Communications Unit MaintainerPathway Communications Unit Maintains
Pathway Communications Unit ManagerPathway Communications Unit Manages
Pathway Communications Unit ManagerPathway Communications Unit Operator System Usage Agreement
Pathway Communications Unit OperatorPathway Communications Unit Operates
Pathway Communications Unit OwnerITS Object Maintainer Maintenance Data Exchange Agreement
Pathway Communications Unit OwnerITS Object User Service Usage Agreement
Pathway Communications Unit OwnerOther ITS Objects Maintainer Maintenance Data Exchange Agreement
Pathway Communications Unit OwnerOther ITS Objects User Service Usage Agreement
Pathway Communications Unit OwnerPathway Communications Unit Maintainer System Maintenance Agreement
Pathway Communications Unit OwnerPathway Communications Unit Manager Operations Agreement
Pathway Communications Unit SupplierPathway Communications Unit Owner Warranty
Roadside Communications Unit MaintainerRoadside Communications Unit Maintains
Roadside Communications Unit ManagerRoadside Communications Unit Manages
Roadside Communications Unit ManagerRoadside Communications Unit Operator System Usage Agreement
Roadside Communications Unit OperatorRoadside Communications Unit Operates
Roadside Communications Unit OwnerITS Object Maintainer Maintenance Data Exchange Agreement
Roadside Communications Unit OwnerITS Object User Service Usage Agreement
Roadside Communications Unit OwnerOther ITS Objects Maintainer Maintenance Data Exchange Agreement
Roadside Communications Unit OwnerOther ITS Objects User Service Usage Agreement
Roadside Communications Unit OwnerRoadside Communications Unit Maintainer System Maintenance Agreement
Roadside Communications Unit OwnerRoadside Communications Unit Manager Operations Agreement
Roadside Communications Unit SupplierRoadside Communications Unit Owner Warranty
Wide Area Information Disseminator System MaintainerWide Area Information Disseminator System Maintains
Wide Area Information Disseminator System ManagerWide Area Information Disseminator System Manages
Wide Area Information Disseminator System ManagerWide Area Information Disseminator System Operator System Usage Agreement
Wide Area Information Disseminator System OperatorWide Area Information Disseminator System Operates
Wide Area Information Disseminator System OwnerOther ITS Objects Maintainer Maintenance Data Exchange Agreement
Wide Area Information Disseminator System OwnerOther ITS Objects User Service Usage Agreement
Wide Area Information Disseminator System OwnerWide Area Information Disseminator System Maintainer System Maintenance Agreement
Wide Area Information Disseminator System OwnerWide Area Information Disseminator System Manager Operations Agreement
Wide Area Information Disseminator System SupplierWide Area Information Disseminator System Owner Warranty

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
ITS Communications Equipment Support 'ITS Communications Equipment' includes the communications hardware and software that supports secure, reliable communications. It provides the layered protocols and communications services and includes the physical network plant and network hardware that supports ITS communications. It also encompasses security services that protect communications and the management services that support network management. This physical object allows transportation stakeholders that are implementing their own communications solution to represent this implementation in their ITS architecture. The communications capabilities provided by this physical object are frequently purchased from a third party provider. When communications is a purchased service, the hardware and software included in this physical object are largely transparent to transportation stakeholders and may be transparent to the ITS architecture.
ITS Object ITS The general 'ITS Object' includes core capabilities common to any class of object.
Other ITS Objects ITS Representing other ITS Objects, 'Other ITS Objects' provides a source and destination for information exchange between ITS Objects.
Pathway Communications Unit Field The 'Pathway Communications Unit' provides wireless communications between the pathway infrastructure (either indoor or outdoor) and nearby mobile devices; Communications with adjacent field equipment (including other PCUs) and back-office centers that monitor and control the PCU are also supported. The PCU provides basic radio communications supporting the lower layers of the OSI stack (TransNet and SubNet layers of the ARC-IT communications model). Importantly, it can also serve as a reference for mobile devices to determine their position more accurately (e.g., through triangulation or other means).
Roadside Communications Unit Field The 'Roadside Communications Unit' provides wireless communications between roadside infrastructure and nearby equipped vehicles. Communications with adjacent field equipment (including other RCUs) and back office centers that monitor and control the RCU are also supported. It provides basic radio communications supporting the lower layers of the OSI stack (TransNet and SubNet layers of the ARC-IT communications model). See also 'Connected Vehicle Roadside Equipment' that extends the basic RCU radio communications functionality with a full communications stack and support for locally installed ITS Applications
Wide Area Information Disseminator System Support The 'Wide Area Information Disseminator System' represents the center based systems and communications equipment that is used to send messages to equipped vehicles using wide-area wireless communications such as satellite radio, terrestrial FM broadcast subcarrier, or cellular data networks.

Includes Functional Objects:

Functional Object Description Physical Object
ITS Communications Privacy Protection 'ITS Communications Privacy Protection' operates as a proxy, obscuring the originator's network address, and tagging the message so that it can return replies to the originator. ITS Communications Equipment
ITS Communications Services 'ITS Communications Services' supports secure, reliable data communications between connected devices. It includes the network devices as well as any required physical cabling and supporting hardware that represent the communications infrastructure that originate, route, and terminate data communications between a source and a destination. Applications specific protocols are layered over more general communications protocols to support the communications. Network management keeps the network configured and working reliably. Security services ensure the data received is correct and from an authentic source. ITS Communications Equipment
ITS Communications Support 'ITS Communications Support' provides means to send and receive messages to and from other ITS Objects. It provides mechanisms for scheduling and prioritizing communications traffic. It may also provide relay functions. ITS Object
ITS Security Support 'ITS Security Support' provides communications and system security functions to the ITS Object, including privacy protection functions. It may include firewall, intrusion management, authentication, authorization, profile management, identity management, cryptographic key management. It may include a hardware security module and security management information base. ITS Object
PCU Communications 'PCU Communications' provides basic radio communications between pathway infrastructure and nearby mobile devices. Communications with adjacent field equipment (including other PCUs) and back office centers that monitor and control the PCU are also supported. It supports the lower layers of the OSI stack, specifically the TransNet and SubNet layers of the ARC-IT communications model. Message relay capabilities are also included to improve radio communications range, reliability, and performance. Pathway Communications Unit
RCU Radio Communications 'RCU Radio Communications' provides basic radio communications between roadside infrastructure and nearby equipped vehicles and mobile devices. Communications with adjacent field equipment (including other RCUs) and back office centers that monitor and control the RCU are also supported. It supports the lower layers of the OSI stack, specifically the TransNet and SubNet layers of the ARC-IT communications model. Message relay capabilities are also included to improve radio communications range, reliability, and performance. Roadside Communications Unit
WAID Broadcast Services 'WAID Broadcast Services' provides wide-area digital broadcast of traveler information to transportation users across a region. It collects traveler information of interest to clientele (either subscribers or the general public) and distributes the traveler information using broadcast data services that are offered in context with entertainment and other data services. Wide Area Information Disseminator System

Includes Information Flows:

Information Flow Description
ITS information Information exchanged by ITS systems or devices. This flow is a super-flow; it does not define specific content since it represents any information flow exchange between physical objects defined in ARC-IT. This information flow represents any of those information flows and inherits the data content and attributes defined in the more detailed information flows.
local ITS information ITS information that is relevant to a particular location (e.g., a particular intersection) that is of interest to receivers near that location. This flow is a super-flow; it does not define specific content since it represents any information flow exchange using short range communications between physical objects defined in ARC-IT. This includes both broadcast communications to all receivers within range and unicast communications targeted for a specific receiver. This information flow represents any of those information flows and inherits the data content and attributes defined in the more detailed information flows.
local ITS information relay Local ITS information that is relayed to improve range, reliability, and/or performance. This flow is a super-flow; it does not define specific content since it represents any relay of 'local ITS information' using short range communications. See 'local ITS information' for more information.
proxied ITS information Information exchanged by ITS systems or devices where the sender is isolated from the receiver by an intermediary that acts as a proxy for the sender. This flow is a super-flow; it does not define specific content since it represents any information flow exchange between physical objects defined in ARC-IT. This information flow represents any of those information flows and inherits the data content and attributes defined in the more detailed information flows.
wide area broadcast ITS information ITS information of broad interest that is relevant over a wide area and suitable for broadcast distribution. This flow is a super-flow; it does not define specific content since it represents all wide-area broadcast information flows defined in ARC-IT. This information flow represents any of those broadcast information flows and inherits the data content and attributes defined in the more detailed information flows.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective Performance Measure


 
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

Related Sources

Document Name Version Publication Date
None


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
ITS Communications Equipment  
ITS Object  
Other ITS Objects  
Pathway Communications Unit  
Roadside Communications Unit  
Wide Area Information Disseminator System  



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
ITS Communications Equipment ITS Object ITS information High High High
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 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.
ITS Communications Equipment ITS Object proxied ITS information High High High
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 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.
ITS Communications Equipment Other ITS Objects ITS information High High High
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 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.
ITS Communications Equipment Other ITS Objects proxied ITS information High High High
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 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.
ITS Object ITS Communications Equipment ITS information High High High
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 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.
ITS Object Other ITS Objects ITS information High High High
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 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.
ITS Object Pathway Communications Unit local ITS information High High High
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 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.
ITS Object Roadside Communications Unit ITS information High High High
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 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.
ITS Object Wide Area Information Disseminator System ITS information High High High
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 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.
Other ITS Objects ITS Communications Equipment ITS information High High High
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 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.
Other ITS Objects ITS Object ITS information High High High
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 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.
Other ITS Objects Pathway Communications Unit local ITS information High High High
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 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.
Other ITS Objects Roadside Communications Unit local ITS information High High High
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 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.
Pathway Communications Unit ITS Object local ITS information High High High
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 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.
Pathway Communications Unit Other ITS Objects local ITS information High High High
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 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.
Roadside Communications Unit ITS Object ITS information High High High
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 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.
Roadside Communications Unit Other ITS Objects local ITS information High High High
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 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.
Roadside Communications Unit Other ITS Objects local ITS information relay High High High
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 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.
Wide Area Information Disseminator System Other ITS Objects wide area broadcast ITS information Not Applicable Moderate Low
By definition this is publicly broadcast data. The distribution of this data is intended to be very large, as such the impact of corrupted data will be significant. Probably not HIGH, as there are other distribution channels for this data. There are multiple channels for the delivery of this information, so if this one is not available, others will work. Could consider raising this to MODERATE if it is the sole mechanism able to reach certain areas.

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. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

NameTitlePhysical Object
CTI 4001 RSU Roadside Unit (RSU) Standard Roadside Communications Unit
FIPS 140-2 Security Requirements for Cryptographic Modules ITS Object
ISO 21217 Architecture Intelligent transport systems -- Communications access for land mobiles (CALM) -- Architecture ITS Object




System Requirements

No System Requirements