< < TM16.3 : TM17.1 : TM17.2 > >
TM17.1: Wide Area Wireless Implementation
Wide area wireless (e.g., cellular) is used to communicate speed warning information to the vehicle.
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
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| Driver | Vehicle | The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects. |
| Enforcement Center | Center | The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc. |
| ITS Roadway Equipment | Field | 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included. |
| Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
| Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
| Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
| Vehicle | Vehicle | This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle 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. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. 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. |
| Vehicle Characteristics | Vehicle | 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles, occupants, emissions) of individual vehicles that can be sensed and measured or classified. This physical object represents the physical properties of vehicles that can be sensed by vehicle-based or infrastructure-based sensors to support vehicle automation and traffic sensor systems. The analog properties provided by this terminator represent the sensor inputs that are used to detect and assess vehicle(s) within the sensor's range to support safe AV operation and/or responsive and safe traffic management. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| MCM Reduced Speed Zone Warning | 'MCM Reduced Speed Zone Warning' supports remote control and monitoring of reduced speed zone warning roadside equipment. It provides posted speed limits and associated schedules and information about associated road configuration changes including lane merges and shifts. It monitors field equipment operation and reports current status to the operator. | Maint and Constr Management Center |
| Roadway Speed Monitoring and Warning | 'Roadway Speed Monitoring and Warning' includes the field elements that monitor vehicle speeds. If the speed is determined to be excessive, an advisory or warning is displayed. Current environmental conditions and other factors that may reduce safe operating speeds may also be taken into account. The operational status (state of the device, configuration, and fault data) is provided to the center. This application can also provide an enforcement function, reporting speed violations to an enforcement agency. | ITS Roadway Equipment |
| TIC Traffic Control Dissemination | 'TIC Traffic Control Dissemination' serves as intermediary between transportation operations centers (e.g., TMC, Transit MC) and transportation users (e.g., vehicles, personal devices). It collects and disseminates intersection status, lane control information, special vehicle alerts, and other traffic control related information that is real-time or near real-time in nature and relevant to vehicles in a relatively local area on the road network. It collects traffic control information from Traffic Management and other Center(s) and disseminates the relevant information to vehicles and other mobile devices. | Transportation Information Center |
| TMC Speed Warning | 'TMC Speed Warning' supports remote control and monitoring of reduced speed zone warning roadside equipment. It provides the location and extent of the reduced speed zone, the posted speed limit(s) with information about the applicability of the speed limit(s) (e.g., time of day, day of week, seasonality, relevant vehicle types) and information about associated road configuration changes including lane merges and shifts. It monitors field equipment operation and reports current status to the operator. | Traffic Management Center |
| Vehicle Traveler Information Reception | 'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. | Vehicle |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| automated enforcement parameters | Includes setup information that identifies rules to be enforced, identification of violators, vehicle/user clearance lists, and other information that supports automated enforcement using roadside systems. |
| driver information | Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. |
| driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. |
| driver updates | Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. |
| request for enforcement | Request for traffic enforcement of speed limits, lane controls, etc. on a roadway including in a work zone or other special situations. |
| roadway dynamic signage data | Information used to initialize, configure, and control dynamic message signs. This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these devices. |
| roadway dynamic signage status | Current operating status of dynamic message signs. |
| speed monitoring control | Information used to configure and control automated speed monitoring, speed warning, and speed enforcement systems. |
| speed monitoring information | System status including current operational state and logged information including measured speeds, warning messages displayed, and violation records. |
| speed warning information | Current speed limit, measured speed of the vehicle, and supplementary warning information. The flow may also identify whether the target speed is a posted advisory speed or enforceable speed limit. |
| vehicle characteristics | The physical or visible characteristics of individual vehicles that can be used to detect, classify, and monitor vehicles and imaged to uniquely identify vehicles and characterize their performance (e.g., speed, occupants, emissions). |
| violation notification | Notification to enforcement agency of detected traffic violations. This notification identifies the vehicle and documents the infraction date, time, and location, the violation, and associated information that documents the violation. For example, for a speed violation, this flow includes the measured speed and current posted speed limit. |
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 | ||
|---|---|---|---|---|
| 01 | Traffic Operations need to be able to monitor vehicle speeds to determine when vehicle speed is excessive. | MCM Reduced Speed Zone Warning | 01 | The center shall be capable of remotely control and monitor reduced speed zone warning roadside equipment operations. |
| Roadway Speed Monitoring and Warning | 01 | The field element shall include sensors to detect vehicle speeds, under traffic or maintenance center control. | ||
| 06 | The field element shall return operational status for the vehicle speed sensors to the controlling traffic or maintenance center; including measured speeds, warning messages displayed, and violation records. | |||
| TMC Speed Warning | 02 | The center shall province the capability to control automated speed monitoring and speed warning systems. | ||
| 02 | Traffic Operations need to be able to warn drivers when their speed is excessive. | MCM Reduced Speed Zone Warning | 02 | The center shall provide reduced speed zone posted speed limits and associated schedules and information about associated road configuration changes including lane merges and shifts for display on roadside devices. |
| Roadway Speed Monitoring and Warning | 03 | If the speed detected by vehicle speed sensors is determined to be excessive, the field element shall provide a safe speed advisory to passing drivers via a driver information system (such as portable messages signs, field to vehicle communications to in-vehicle signing systems, etc.). | ||
| Vehicle Traveler Information Reception | 01 | The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, border crossing information, and weather information. | ||
| 02 | The vehicle shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, border crossing advisories, and other special information. | |||
| 03 | The vehicle shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local conditions warnings identified by local environmental sensors). | |||
| 04 | The vehicle shall store a translation table for road sign and message templates used for in-vehicle display. | |||
| 05 | The vehicle shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. | |||
| 06 | The vehicle shall present to the driver a visual display of static sign information or dynamic roadway conditions information | |||
| 07 | The vehicle shall be capable of providing to the driver an audible presentation of static sign information or dynamic roadway conditions information | |||
| 03 | Traffic Operations need to be able to notify an enforcement agency that vehicles are traveling at excessive speed and to be able to request that the enforcement agency respond to the excessive speed. | TMC Speed Warning | 01 | The center shall provide the capability to notify an enforcement agency when vehicle speeds in the work zone are in excess of the posted speed limit or are creating an unsafe condition based upon the current environmental or traffic conditions. |
| 04 | Enforcement agencies need to be able to monitor vehicle speeds as measured by field equipment to determine when vehicle speed is excessive. | Roadway Speed Monitoring and Warning | 02 | The field element shall include sensors to detect vehicle speeds, under enforcement agency control. |
| 05 | The field element shall monitor notify an enforcement agency when a speed violation is detected. | |||
| 07 | The field element shall return operational status for the vehicle speed sensors to the enforcement agency. | |||
| 08 | The field element shall return fault data for the vehicle speed sensors to the controlling center for repair. | |||
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 |
| Enforcement Center | Moderate | High | Moderate | Class 3 |
| ITS Roadway Equipment | Moderate | Moderate | Moderate | Class 2 |
| Maint and Constr Management Center | Moderate | High | Moderate | Class 3 |
| Traffic Management Center | Moderate | High | Moderate | Class 3 |
| Transportation Information Center | Moderate | Moderate | Moderate | Class 2 |
| Vehicle | Low | Low | Low | Class 1 |
| Vehicle Characteristics | ||||
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 | |||
| Driver | Vehicle | driver input | Moderate | High | High |
| Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. | Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner | Commands must always be able to be given or the driver has no control. | |||
| Enforcement Center | ITS Roadway Equipment | automated enforcement parameters | Low | Moderate | Low |
| Should cause no harm if this information were public. | Corruption or manipulation of this flow could cause inaccurate violations, which would be a significant inconvenience (if set to generate more violations that it should). | If this flow cannot function then automated enforcement may in the worst case pause, which has little negative effect on roadway operation. | |||
| Enforcement Center | ITS Roadway Equipment | speed monitoring control | Moderate | High | Low |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
| ITS Roadway Equipment | Driver | driver information | Not Applicable | High | Moderate |
| This data is sent to all drivers and is also directly observable, by design. | This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it’s wrong, accidents could happen. | If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a cascading effect due to lack of coordination with other intersections. | |||
| ITS Roadway Equipment | Enforcement Center | speed monitoring information | Moderate | Moderate | Moderate |
| Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. | Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. | Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. | |||
| ITS Roadway Equipment | Enforcement Center | violation notification | Moderate | Moderate | Moderate |
| Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual. | Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. | More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies. | |||
| ITS Roadway Equipment | Maint and Constr Management Center | roadway dynamic signage status | Moderate | Moderate | Moderate |
| Device status information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Failure of this flow affects traveler information dissemination, the importance of which varies with the data contained in the flow and the scenario. Could be LOW in many instances. | |||
| ITS Roadway Equipment | Maint and Constr Management Center | speed monitoring information | Moderate | Moderate | Moderate |
| Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. | Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. | Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. | |||
| ITS Roadway Equipment | Traffic Management Center | roadway dynamic signage status | Moderate | Moderate | Moderate |
| Device status information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Failure of this flow affects traveler information dissemination, the importance of which varies with the data contained in the flow and the scenario. Could be LOW in many instances. | |||
| ITS Roadway Equipment | Traffic Management Center | speed monitoring information | Moderate | Moderate | Moderate |
| Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. | info that should not be tampered with, especially violation records and operational state but the rest is aggregate info | want updates but outdated information will not be catastrophic; would want to know about the speeds, warnings, etc. to be able to reconfigure speed warning info as necessary | |||
| Maint and Constr Management Center | Enforcement Center | request for enforcement | Moderate | Moderate | Low |
| If this request were intercepted by a third party, that party may learn where enforcement assets would be and so could use that information to avoid such assets in the commission of a crime. | Inaccurate or corrupted information here could lead to enforcement in areas not requested, and/or no enforcement in the area that was requested. Given that the request is possibly safety-based, this can negatively impact safety and/or mobility in that area. | The setup of enforcement in a given area will likely be given and granted at low frequency; that is on the order of instances/week, not a real time request, so this flow does not need to be continuously available. | |||
| Maint and Constr Management Center | ITS Roadway Equipment | roadway dynamic signage data | Moderate | Moderate | Moderate |
| Device control information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Occasional outages of this flow will delay dissemination of the data to travelers (the eventual end user) which could have significant impacts on travel, both safety and mobility impacts. | |||
| Maint and Constr Management Center | ITS Roadway Equipment | speed monitoring control | Moderate | High | Low |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. | |||
| Maint and Constr Management Center | Transportation Information Center | speed monitoring information | Moderate | Moderate | Moderate |
| Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. | info that should not be tampered with, especially violation records and operational state but the rest is aggregate info | want updates but outdated information will not be catastrophic; would want to know about the speeds, warnings, etc. to be able to reconfigure speed warning info as necessary | |||
| Traffic Management Center | Enforcement Center | request for enforcement | Moderate | Moderate | Low |
| If this request were intercepted by a third party, that party may learn where enforcement assets would be and so could use that information to avoid such assets in the commission of a crime. | Inaccurate or corrupted information here could lead to enforcement in areas not requested, and/or no enforcement in the area that was requested. Given that the request is possibly safety-based, this can negatively impact safety and/or mobility in that area. | The setup of enforcement in a given area will likely be given and granted at low frequency; that is on the order of instances/week, not a real time request, so this flow does not need to be continuously available. | |||
| Traffic Management Center | ITS Roadway Equipment | roadway dynamic signage data | Moderate | Moderate | Moderate |
| Device control information should not be available, as those with criminal intent may use this information toward their own ends. | Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. | Occasional outages of this flow will delay dissemination of the data to travelers (the eventual end user) which could have significant impacts on travel, both safety and mobility impacts. | |||
| Traffic Management Center | ITS Roadway Equipment | speed monitoring control | Moderate | High | Moderate |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. From THEA: encrypted, authenticated, proprietary but shouldn’t cause substantial risk but does control speed enforcement systems | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. From THEA: proprietary info that should not be tampered with; could directly affect safety if compromised posting unsafe speed limits, etc. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH. From THEA: want updates but outdated information will not be catastrophic; should be able to use previous/default config | |||
| Traffic Management Center | Transportation Information Center | speed monitoring information | Moderate | Moderate | Moderate |
| Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. | info that should not be tampered with, especially violation records and operational state but the rest is aggregate info | want updates but outdated information will not be catastrophic; would want to know about the speeds, warnings, etc. to be able to reconfigure speed warning info as necessary | |||
| Transportation Information Center | Vehicle | speed warning information | Low | Moderate | Low |
| Some of the information here is intended for all parties, but since this might include vehicle measured speed, remote observation of this information could be used against the vehicle operator by a third party, so there is some potential impact. | Regulatory information and other data that may be used to influence driver behavior should be correct or the vehicle opreator may take incorrect action. | This information should all be available through a variety of mechanisms. | |||
| Vehicle | Driver | driver updates | Not Applicable | Moderate | Moderate |
| This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. | This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. | If this information is not made available to the driver, then the system has not operated correctly. | |||
| Vehicle Characteristics | ITS Roadway Equipment | vehicle characteristics | |||
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.
| Name | Title | Physical Object |
|---|---|---|
| ISO 24100 Probe Vehicle Data Protection | Intelligent transport systems -- Basic principles for personal data protection in probe vehicle information services | Traffic Management Center |
| Transportation Information Center | ||
| ITE 5301 ATC ITS Cabinet | Intelligent Transportation System Standard Specification for Roadside Cabinets | ITS Roadway Equipment |
| NEMA TS 8 Cyber and Physical Security | Cyber and Physical Security for Intelligent Transportation Systems | ITS Roadway Equipment |
| Maint and Constr Management Center | ||
| Traffic Management Center | ||
| NEMA TS4 Hardware Standards for DMS | Hardware Standards for Dynamic Message Signs (DMS) With NTCIP Requirements | ITS Roadway Equipment |
| SAE J3361 Antenna requirements | V2X Antenna Coverage and Test Requirements for US FHWA Class 1 and Class 3-13 Class Vehicles | Vehicle |
| SAE J5001 OBU Standard | Onboard Unit Standard for Connected Vehicles | Vehicle |
System Requirements
| No System Requirements |