ST09: Connected Eco-Driving
The Connected Eco-Driving service package provides customized real-time driving advice to drivers so that they can adjust their driving behavior to save fuel and reduce emissions. Eco-driving advice includes recommended driving speeds, optimal acceleration, and optimal deceleration profiles based on prevailing traffic conditions, interactions with nearby vehicles, and upcoming road grades. The service package also provides feedback to drivers on their driving behavior to encourage drivers to drive in a more environmentally efficient manner. Finally, the service package may include vehicle-assisted strategies where the vehicle automatically implements the eco-driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco-friendly manner).
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
- Implementations
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|---|---|
| Connected Vehicle Roadside Equipment Maintainer | Connected Vehicle Roadside Equipment | Maintains |
| Connected Vehicle Roadside Equipment Manager | Connected Vehicle Roadside Equipment | Manages |
| Connected Vehicle Roadside Equipment Manager | Connected Vehicle Roadside Equipment Operator | System Usage Agreement |
| Connected Vehicle Roadside Equipment Operator | Connected Vehicle Roadside Equipment | Operates |
| Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Maintainer | System Maintenance Agreement |
| Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Manager | Operations Agreement |
| Connected Vehicle Roadside Equipment Owner | Driver | Application Usage Agreement |
| Connected Vehicle Roadside Equipment Owner | TIC Operator | Application Usage Agreement |
| Connected Vehicle Roadside Equipment Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
| Connected Vehicle Roadside Equipment Owner | Transportation Information Center Owner | Information Exchange Agreement |
| Connected Vehicle Roadside Equipment Owner | Transportation Information Center User | Service Usage Agreement |
| Connected Vehicle Roadside Equipment Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
| Connected Vehicle Roadside Equipment Owner | Vehicle Owner | Expectation of Information Provision |
| Connected Vehicle Roadside Equipment Owner | Vehicle User | Service Usage Agreement |
| Connected Vehicle Roadside Equipment Supplier | Connected Vehicle Roadside Equipment Owner | Warranty |
| Driver | Vehicle | Operates |
| Multi-Access Edge Computing Manager | Multi-Access Edge Computing Operator | System Usage Agreement |
| Multi-Access Edge Computing Owner | Driver | Application Usage Agreement |
| Multi-Access Edge Computing Owner | TIC Operator | Application Usage Agreement |
| Multi-Access Edge Computing Owner | Vehicle Owner | Expectation of Information Provision |
| Other Vehicle OBEs Operator | Other Vehicles | Operates |
| Other Vehicles Maintainer | Other Vehicles | Maintains |
| Other Vehicles Manager | Other Vehicle OBEs Operator | System Usage Agreement |
| Other Vehicles Manager | Other Vehicles | Manages |
| Other Vehicles Owner | Driver | Application Usage Agreement |
| Other Vehicles Owner | Driver | Vehicle Operating Agreement |
| Other Vehicles Owner | Other Vehicles Maintainer | System Maintenance Agreement |
| Other Vehicles Owner | Other Vehicles Manager | Operations Agreement |
| Other Vehicles Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
| Other Vehicles Owner | Vehicle Owner | Expectation of Data Provision |
| Other Vehicles Owner | Vehicle User | Service Usage Agreement |
| Other Vehicles Supplier | Other Vehicles Owner | Warranty |
| TIC Operator | Transportation Information Center | Operates |
| Transportation Information Center Maintainer | Transportation Information Center | Maintains |
| Transportation Information Center Manager | TIC Operator | System Usage Agreement |
| Transportation Information Center Manager | Transportation Information Center | Manages |
| Transportation Information Center Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
| Transportation Information Center Owner | Connected Vehicle Roadside Equipment Operator | Application Usage Agreement |
| Transportation Information Center Owner | Connected Vehicle Roadside Equipment Owner | Information Exchange Agreement |
| Transportation Information Center Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
| Transportation Information Center Owner | Driver | Application Usage Agreement |
| Transportation Information Center Owner | Multi-Access Edge Computing Operator | Application Usage Agreement |
| Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
| Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
| Transportation Information Center Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
| Transportation Information Center Owner | Vehicle Owner | Information Exchange Agreement |
| Transportation Information Center Owner | Vehicle User | Service Usage Agreement |
| Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
| Vehicle Maintainer | Vehicle | Maintains |
| Vehicle Manager | Driver | System Usage Agreement |
| Vehicle Manager | Vehicle | Manages |
| Vehicle Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
| Vehicle Owner | Connected Vehicle Roadside Equipment Operator | Application Usage Agreement |
| Vehicle Owner | Connected Vehicle Roadside Equipment Owner | Expectation of Data Provision |
| Vehicle Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
| Vehicle Owner | Multi-Access Edge Computing Operator | Application Usage Agreement |
| Vehicle Owner | Multi-Access Edge Computing Owner | Expectation of Data Provision |
| Vehicle Owner | Other Vehicle OBEs Operator | Application Usage Agreement |
| Vehicle Owner | Other Vehicle OBEs Operator | Vehicle Operating Agreement |
| Vehicle Owner | Other Vehicles Maintainer | Maintenance Data Exchange Agreement |
| Vehicle Owner | Other Vehicles Owner | Expectation of Data Provision |
| Vehicle Owner | Other Vehicles User | Service Usage Agreement |
| Vehicle Owner | TIC Operator | Application Usage Agreement |
| Vehicle Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
| Vehicle Owner | Transportation Information Center Owner | Information Exchange Agreement |
| Vehicle Owner | Transportation Information Center User | Service Usage Agreement |
| Vehicle Owner | Vehicle Maintainer | System Maintenance Agreement |
| Vehicle Owner | Vehicle Manager | Operations Agreement |
| Vehicle Supplier | Vehicle Owner | Warranty |
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 |
|---|---|---|
| Connected Vehicle Roadside Equipment | Field | 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. 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. |
| 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. |
| Other Vehicles | Vehicle | 'Other Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. This object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Other Vehicle OBEs to model all connected vehicle V2V communications in ARC-IT. |
| 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. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| RSE Traffic Monitoring | 'RSE Traffic Monitoring' monitors the basic safety messages that are shared between connected vehicles, correlates multiple messages received from connected vehicles, and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident. | Connected Vehicle Roadside Equipment |
| RSE Traveler Information Communications | 'RSE Traveler Information Communications' includes field elements that distribute information to vehicles for in-vehicle display. The information may be provided by a center (e.g., variable information on traffic and road conditions in the vicinity of the field equipment) or it may be determined and output locally (e.g., static sign information and signal phase and timing information). This includes the interface to the center or field equipment that controls the information distribution and the short range communications equipment that provides information to passing vehicles. | Connected Vehicle Roadside Equipment |
| TIC Connected Vehicle Traveler Info Distribution | In support of connected vehicle applications, 'TIC Connected Vehicle Traveler Info Distribution' disseminates traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. Location-specific or situation-relevant traveler information is sent to short range communications transceivers at the roadside. | Transportation Information Center |
| TIC Situation Data Management | 'TIC Situation Data Management' manages connected vehicle situation data collection, quality controls, filtering, aggregation, and storage. Through this process, raw data reported by connected vehicles are transformed into information products that can be accessed and used to support transportation operations and traveler information. | Transportation Information Center |
| TIC Traveler Information Broadcast | 'TIC Traveler Information Broadcast' disseminates traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. The same information is broadcast to all equipped traveler interface systems and vehicles. | Transportation Information Center |
| Vehicle Basic Safety Communication | 'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity and the infrastructure, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. This object can also support broadcasting other vehicle information required for passing through a specific roadway segment such as variables that describe vehicle's characteristics and parameters, driver's preferences in terms of vehicle motion and behavior, etc. | Vehicle |
| Vehicle Eco-Driving Assist | 'Vehicle Eco-Driving Assist' provides customized real-time driving advice to drivers, allowing them to adjust behaviors to save fuel and reduce emissions. This advice includes recommended driving speeds, optimal acceleration and deceleration profiles based on prevailing traffic conditions, and local interactions with nearby vehicles, i.e., processing Basic Safety Messages (BSMs) to determine position and speed of vehicles that are between the host vehicle and the intersection. When approaching and departing signalized intersections, it uses intersection geometry information, the relative position and speed of vehicles ahead of it, and signal phase movement information to provide speed advice to the driver so that the driver can adapt the vehicle’s speed to pass the next traffic signal on green, decelerate to a stop in the most eco-friendly manner, or manage acceleration as the vehicle departs from a signalized intersection. It also provides feedback to drivers on their driving behavior to encourage them to drive in a more environmentally efficient manner. It may also support vehicle-assisted strategies, where the vehicle automatically implements the eco-driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco-friendly manner as the vehicle approaches a traffic signal or queue). | Vehicle |
| Vehicle Situation Data Monitoring | 'Vehicle Situation Data Monitoring' is the highest-level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this functional object supports collection of data for areas remote from RSEs or other communications infrastructure. | Vehicle |
| 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 |
|---|---|
| broadcast traveler information | General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, vehicle requirements, work zones, transit service information, weather information, parking information, and other related traveler information. This information is typically location-specific to the destination, includes a specification of the relevant geo-fence boundary, and time effectivity of the included information. |
| 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. |
| local traveler information | Traveler information including traffic, road, and weather conditions for a particular locality. This flow includes the location-specific traveler information and time effectivity of the information. |
| traffic situation data | Current, aggregate traffic data collected from connected vehicles. It includes raw and/or processed reported vehicle speeds, counts, and other derived measures. Raw and/or filtered vehicle control events may also be included to support incident detection. This flow represents information collected from a single probe data collection point in the road network (e.g., a CVRSE or a MEC). |
| traveler information application info | Traveler information and associated parameters, filters, and thresholds that control the RSE's distribution of the traveler information to passing vehicles. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. |
| traveler information application status | Application status reported by the RSE. This includes current operational state and status of the RSE and a record of traveler information distribution. |
| vehicle location and motion | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. |
| vehicle location and motion for surveillance | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications. |
| vehicle situation data | This flow represents vehicle snapshots that may be provided by the vehicle to support traffic and environmental conditions monitoring. Snapshots are collected by the vehicle for specific events (e.g., when a sensor exceeds a threshold) or periodically and reported based on control parameters when communications is available. Traffic-related data includes snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control events. Environmental data may include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. |
| vehicle situation data parameters | A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval. |
Goals and Objectives
Associated Planning Factors and Goals
| Planning Factor | Goal |
|---|---|
| E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; | Protect/Enhance the Environment |
Associated Objective Categories 
| Objective Category |
|---|
| Environment: Clean Air |
| System Efficiency: Energy Consumption |
Associated Objectives and Performance Measures
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 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. | RSE Traffic Monitoring | 01 | The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions. |
| 02 | The field element shall aggregate and forward collected probe information to the center. | |||
| RSE Traveler Information Communications | 01 | The field element shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control. | ||
| 04 | The field element shall return system operational status to the controlling center. | |||
| 11 | The field element shall provide real-time driving advice to connected vehicles so that they can adjust their driving behavior to save fuel and reduce emissions. | |||
| TIC Connected Vehicle Traveler Info Distribution | 04 | The center shall send eco-driving recommendations to connected vehicles so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions. | ||
| TIC Situation Data Management | 01 | The center shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment. | ||
| 02 | The center shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from appropriately equipped vehicles and short range communications equipment. | |||
| 05 | The center shall aggregate collected traffic probe data, calculate route segment travel times, route segment speeds, route usage, and road weather information for dissemination to other centers. | |||
| TIC Traveler Information Broadcast | 01 | The center shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | ||
| 02 | The center shall disseminate maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities. | |||
| 03 | The center shall disseminate transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers. | |||
| 04 | The center shall disseminate parking information to travelers, including location, availability, and fees. | |||
| 06 | The center shall disseminate weather information to travelers. | |||
| 07 | The center shall disseminate event information to travelers. | |||
| 08 | The center shall disseminate air quality information to travelers. | |||
| 10 | The center shall provide the capability for a system operator to control the type and update frequency of broadcast traveler information. | |||
| Vehicle Basic Safety Communication | 07 | The vehicle shall receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices. | ||
| Vehicle Eco-Driving Assist | 04 | The vehicle shall provide advisory speed to driver so that they can adjust their driving behavior to save fuel and reduce emissions. | ||
| 11 | The vehicle shall provide eco-driving recommendations to the driver. | |||
| Vehicle Situation Data Monitoring | 02 | The Vehicle shall collect data collection parameters from Centers. | ||
| 05 | The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment. | |||
| Vehicle Traveler Information Reception | 10 | The vehicle shall receive customized real-time driving advice so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions. | ||
| 22 | The vehicle shall receive formatted traffic information from a center and present it to the driver. | |||
| 02 | The connected vehicle needs to be able to automatically perform actions to implement eco-driving strategies. | TIC Connected Vehicle Traveler Info Distribution | 04 | The center shall send eco-driving recommendations to connected vehicles so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions. |
| Vehicle Basic Safety Communication | 06 | The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles. | ||
| Vehicle Eco-Driving Assist | 05 | The vehicle shall automatically adjust its operating parameters to implement the eco-driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco-friendly manner). | ||
Related Sources
| Document Name | Version | Publication Date |
|---|---|---|
| Dynamic Eco-Lanes: Operational Concept | Final v1.1 | 8/1/2012 |
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 |
| Connected Vehicle Roadside Equipment | Moderate | Moderate | Moderate | Class 2 |
| Other Vehicles | Not Applicable | High | Moderate | Class 3 |
| Transportation Information Center | Moderate | Moderate | Moderate | Class 2 |
| Vehicle | Moderate | High | Moderate | Class 3 |
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 | |||
| Connected Vehicle Roadside Equipment | Transportation Information Center | traffic situation data | Moderate | Moderate | Moderate |
| Aggregated messages may have more privacy implications than individual ones, especially if an attacker can attack more than one RSE-to-TMC connection at once. | This information is used to help with incident detection. It should be verified to ensure that it is not incorrectly influencing this.THEA: only limited adverse effect if raw/processed connected vehicle data is bad/compromised; could be LOW for ISIG | This information is used as supplemental information. It should operate correctly if not every single message is received. | |||
| Connected Vehicle Roadside Equipment | Transportation Information Center | traveler information application status | Moderate | Moderate | Low |
| This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. | If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. | A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered. | |||
| Connected Vehicle Roadside Equipment | Vehicle | local traveler information | Not Applicable | Moderate | Low |
| This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. Flaws in this information will have a minimal effect on systems receiving it. All of the information can be verified through other means, and in a worst case scenario will only cause slightly increased traffic in the general proximity of the RSE. DISC: Original V2I analysis classified this as LOW. | All of the information provided through this flow will be available from other sources and no systems will directly rely upon it. | |||
| 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. | |||
| Other Vehicles | Vehicle | vehicle location and motion | Not Applicable | High | Moderate |
| This data is intentionally transmitted to everyone via a broadcast. Much of its information content can also be determined via other visual indicators | BSM info needs to be accurate and should not be tampered with | BSM must be broadcast regularly to make data available for other vehicle OBEs, but availability cannot be guaranteed over a wireless medium | |||
| Transportation Information Center | Connected Vehicle Roadside Equipment | traveler information application info | Moderate | Moderate | Low |
| This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. | If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. | A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered. | |||
| Transportation Information Center | Vehicle | broadcast traveler information | Not Applicable | Moderate | Moderate |
| 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. DISC: WYO suggests this is LOW. | |||
| Transportation Information Center | Vehicle | vehicle situation data parameters | Low | Moderate | Moderate |
| This isn't exactly a control flow, more like a 'suggestion flow', as the vehicle will always decide what to send. Probably no need for obfuscation. | Info should be accurate and should not be tampered so that the vehicle only discloses the correctly requested data | Parameters should be timely and readily available, but would not have severe/catastrophic consequences if not | |||
| Vehicle | Connected Vehicle Roadside Equipment | vehicle location and motion for surveillance | Not Applicable | Moderate | Moderate |
| This is directly observable data; DISC: WYO believes this to be MODERATE | Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH | This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW | |||
| 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 | Other Vehicles | vehicle location and motion | Not Applicable | High | Moderate |
| This data is intentionally transmitted to everyone via a broadcast. Much of its information content can also be determined via other visual indicators | BSM info needs to be accurate and should not be tampered with | BSM must be broadcast regularly to make data available for other vehicle OBEs, but availability cannot be guaranteed over a wireless medium | |||
| Vehicle | Transportation Information Center | vehicle situation data | Moderate | Moderate | Low |
| Might be able to link multiple snapshots together and compromise some element of driver/traveler privacy. | Event driven data can be used for various mobility monitoring applications, and as operational decisions may be made based on mobility conditions, this data's accuracy should be preserved or decisions may not align with real situations. | While desireable, in most application contexts the provision of a single vehicle's data through this flow is not critical. | |||
Standards
The diagram here shows the primary standards associated with the physical objects and information flows in this service package. Click on the standard # to go to the page explaining that standard in more detail. The tables that follow the diagram list the standards associated with the information flows in this service package that should drive development decisions. Click on the standard name for more information from the Communications View about a particular standard, including the solutions and information flow triples associated with the standard and any gaps or overlaps. This table is based primarily on standards used in North America. For information concerning standards and communications solutions in other regions consult the Communications View.
This material should be considered 'draft for review' and may change separately from ARC-IT version revisions. The date on the diagram relates to the date of the physical service package diagram on which this is based; standards-related information should be considered up-to-date as of the 'last updated' date on this page.
Communication Standards: Standards associated with data, message or dialog definitions, communications protocols and management and security of data exchanges. All standards here are also illustrated in information flow triple communications view diagrams.
| Name | Title |
|---|---|
| ITS Application Entity | |
| ISO 14819-2 RDS-TMC Codes | Intelligent transport systems -- Traffic and travel information messages via traffic message coding -- Part 2: Event and information codes for Radio Data System -- Traffic Message Channel (RDS-TMC) using ALERT-C |
| ISO 14819-3 RDS-TMC Location Ref | Intelligent transport systems -- Traffic and travel information messages via traffic message coding -- Part 3: Location referencing for Radio Data System -- Traffic Message Channel (RDS-TMC) using ALERT-C |
| ISO 21219-15 TPEG2 - Traffic Event | Intelligent transport systems -- Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) -- Part 15: Traffic event compact (TPEG2-TEC) |
| NTCIP 1209 Transportation Sensor Objects | NTCIP Object Definitions for Transportation Sensor Systems (TSS) |
| SAE J2735 DSRC Message Set | V2X Communications Message Set Dictionary |
| SAE J2945/4 Road Safety Applications | Road Safety Applications |
| SAE J3161/1 Requirements for LTE-V2X Safety Communications | On-Board System Requirements for LTE-V2X V2V Safety Communications |
| Facilities Layer | |
| Bundle: ISO 15784-2 | Intelligent transport systems (ITS) -- Data exchange involving roadside modules communication -- Part 2: Centre to field device communications using SNMP |
| ISO 14819-1 RDS-TMC Protocol | Intelligent transport systems -- Traffic and travel information messages via traffic message coding -- Part 1: Coding protocol for Radio Data System -- Traffic Message Channel (RDS-TMC) using ALERT-C |
| Not Needed | No Standard Needed |
| SAE J2945 DSRC Common Design Elements | Dedicated Short Range Communication (DSRC) Systems Engineering Process Guidance for J2945/x Documents and Common Design Concepts |
| Security Entity | |
| Bundle: IEEE 1609.2 | IEEE 1609.2 Security Bundle |
| IETF RFC 6353 TLS for SNMP | Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) |
| IETF RFC 9456 TLS Updates for SNMP | Updates to the TLS Transport Model for SNMP |
| ISO 14819-6 RDS-TMC Encryption | Traffic and Traveller Information (TTI) -- TTI messages via traffic message coding -- Part 6: Encryption and conditional access for the Radio Data System -- Traffic Message Channel ALERT C coding |
| ISO 21219-24 TPEG2 - Light Encryption | Intelligent transport systems - Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) -- Part 24: Light encryption (TPEG2-LTE) |
| Proprietary | Proprietary |
| Secure Session Alternatives | Secure Session Alternatives |
| Management Entity | |
| 3GPP: E-UTRA - Radio Resource Control | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification |
| 3GPP: NAS protocol for EPS | 3rd Generation Partnership Project;Technical Specification Group Radio Access Network; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 |
| Bundle: SNMPv3 MIB | SNMPv3 & Networking MIBs |
| ISO 21219-6 TPEG2 - Message Mgmt | Intelligent transport systems - Traffic and travel information via transport protocol experts group, generation 2(TPEG2) -- Part 6: Message management container (TPEG2-MMC) |
| NTCIP 1201 Global Objects | NTCIP Global Object (GO) Definitions |
| SAE J3161 LTE-V2X Deployment Profiles | LTE Vehicle-to-Everything (LTE-V2X) Deployment Profiles and Radio Parameters for Single Radio Channel Multi-Service Coexistence |
| Networking and Transport Layer | |
| IEEE 1609.3 WAVE - Networking Services | IEEE Standard for Wireless Access in Vehicular Environments (WAVE) - Networking Services |
| Internet Transport Alternatives | Internet Transport Alternatives |
| IP Alternatives | Internet Protocol Alternative Set |
| Access Layer | |
| 3GPP LTE-V2X (PC5) | 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Release 14 Description; Summary of Rel-14 Work Items (Release 14) |
| Field SubNet Alternatives | Field SubNet Alternatives |
| Internet Subnet Alternatives | Internet Subnet Alternatives |
| WAW Broadcast Alternatives | Wide-Area Wireless Broadcast Alternatives |
| Wireless Internet Alternatives (NA) | Wireless Internet Alternatives according to North American standards |
Physical Standards: Standards associated with device physical, environmental or performance requirements.
The following table lists the standards associated with physical objects in this service package. Click on the standard name for more information about a particular standard.
| Name | Title |
|---|---|
| CTI 4001 RSU | Roadside Unit (RSU) Standard |
| ISO 15623 Fwd Collision Performance | Intelligent transport systems -- Forward vehicle collision warning systems -- Performance requirements and test procedures |
| ISO 24100 Probe Vehicle Data Protection | Intelligent transport systems -- Basic principles for personal data protection in probe vehicle information services |
| SAE J3361 Antenna requirements | V2X Antenna Coverage and Test Requirements for US FHWA Class 1 and Class 3-13 Class Vehicles |
| SAE J5001 OBU Standard | Onboard Unit Standard for Connected Vehicles |
Service-Level Standards: Standards associated service package structure, messaging patterns, user needs, requirements or similar systems-engineering content that describe one or more use cases satisfied by the service package.
No service-level standards have been identified for this service package.
System Requirements
| System Requirement | Need | ||
|---|---|---|---|
| 001 | The system shall send eco-driving recommendations to connected vehicles so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 02 | The connected vehicle needs to be able to automatically perform actions to implement eco-driving strategies. | ||
| 002 | The system shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 003 | The system shall collect environmental probe data (air temperature, exterior light status, wiper status, traction control status, etc.) from appropriately equipped vehicles and short range communications equipment. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 004 | The system shall aggregate collected traffic probe data, calculate route segment travel times, route segment speeds, route usage, and road weather information for dissemination to other centers. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 005 | The system shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 006 | The system shall disseminate maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 007 | The system shall disseminate transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 008 | The system shall disseminate parking information to travelers, including location, availability, and fees. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 009 | The system shall disseminate weather information to travelers. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 010 | The system shall disseminate event information to travelers. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 011 | The system shall disseminate air quality information to travelers. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 012 | The system shall provide the capability for a system operator to control the type and update frequency of broadcast traveler information. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 013 | The system shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 014 | The system shall aggregate and forward collected probe information to the center. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 015 | The system shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 016 | The system shall return system operational status to the controlling center. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 017 | The system shall provide real-time driving advice to connected vehicles so that they can adjust their driving behavior to save fuel and reduce emissions. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 018 | The system shall exchange location and motion information with roadside equipment and nearby vehicles. | 02 | The connected vehicle needs to be able to automatically perform actions to implement eco-driving strategies. |
| 019 | The system shall receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 020 | The system shall provide advisory speed to driver so that they can adjust their driving behavior to save fuel and reduce emissions. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 021 | The system shall automatically adjust its operating parameters to implement the eco-driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco-friendly manner). | 02 | The connected vehicle needs to be able to automatically perform actions to implement eco-driving strategies. |
| 022 | The system shall receive customized real-time driving advice so that the vehicle or the driver can adjust their driving behavior to save fuel and reduce emissions. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 023 | The system shall receive formatted traffic information from a center and present it to the driver. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 024 | The system shall collect data collection parameters from Centers. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 025 | The system shall provide eco-driving recommendations to the driver. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
| 026 | The system shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment. | 01 | The vehicle driver needs to be able to receive customized real-time driving advice so that they can adjust their driving behavior to save fuel and reduce emissions. |
