PT10: Intermittent Bus Lanes
This service package provides dedicated bus lanes during peak demand times to enhance transit operations mobility. An intermittent bus lane is a lane that can change its status from regular lane (accessible for all vehicles) to bus lane, for the time strictly necessary for a bus or set of buses to pass. The status of the IBL is communicated to drivers using roadside message signs and through in-vehicle signage. The creation and removal of dedicated bus lanes is managed through coordination between traffic and transit centers.
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 |
---|---|---|
Basic Vehicle Maintainer | Basic Vehicle | Maintains |
Basic Vehicle Manager | Basic Vehicle | Manages |
Basic Vehicle Manager | Driver | System Usage Agreement |
Basic Vehicle Owner | Basic Vehicle Maintainer | System Maintenance Agreement |
Basic Vehicle Owner | Basic Vehicle Manager | Operations Agreement |
Basic Vehicle Owner | Driver | Application Usage Agreement |
Basic Vehicle Owner | Driver | Vehicle Operating Agreement |
Basic Vehicle Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
Basic Vehicle Owner | Vehicle Owner | Expectation of Data Provision |
Basic Vehicle Owner | Vehicle User | Service Usage Agreement |
Basic Vehicle Supplier | Basic Vehicle Owner | Warranty |
Connected Vehicle Roadside Equipment Maintainer | Connected Vehicle Roadside Equipment | Maintains |
Connected Vehicle Roadside Equipment Manager | Connected Vehicle Roadside Equipment | Manages |
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 | Enforcement Center Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Enforcement Center Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | Enforcement Center User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Owner | ITS Roadway Equipment Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | ITS Roadway Equipment Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | ITS Roadway Equipment User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Traffic Management Center Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | Traffic Management Center User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Transit Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Transit Vehicle OBE Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | Transit Vehicle OBE User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Transit Vehicle Operator | Application Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Vehicle Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | Vehicle User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Supplier | Connected Vehicle Roadside Equipment Owner | Warranty |
Driver | Basic Vehicle | Operates |
Driver | Vehicle | Operates |
Enforcement Center Maintainer | Enforcement Center | Maintains |
Enforcement Center Manager | Enforcement Center | Manages |
Enforcement Center Owner | Enforcement Center Maintainer | System Maintenance Agreement |
Enforcement Center Owner | Enforcement Center Manager | Operations Agreement |
Enforcement Center Supplier | Enforcement Center Owner | Warranty |
ITS Roadway Equipment Maintainer | ITS Roadway Equipment | Maintains |
ITS Roadway Equipment Manager | ITS Roadway Equipment | Manages |
ITS Roadway Equipment Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
ITS Roadway Equipment Owner | Connected Vehicle Roadside Equipment Owner | Information Exchange and Action Agreement |
ITS Roadway Equipment Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
ITS Roadway Equipment Owner | ITS Roadway Equipment Maintainer | System Maintenance Agreement |
ITS Roadway Equipment Owner | ITS Roadway Equipment Manager | Operations Agreement |
ITS Roadway Equipment Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
ITS Roadway Equipment Owner | Traffic Management Center Owner | Information Exchange and Action Agreement |
ITS Roadway Equipment Owner | Traffic Management Center User | Service Usage Agreement |
ITS Roadway Equipment Supplier | ITS Roadway Equipment Owner | Warranty |
TIC Operator | Transportation Information Center | Operates |
Traffic Management Center Maintainer | Traffic Management Center | Maintains |
Traffic Management Center Manager | Traffic Management Center | Manages |
Traffic Management Center Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Connected Vehicle Roadside Equipment Owner | Information Provision Agreement |
Traffic Management Center Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
Traffic Management Center Owner | Enforcement Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Enforcement Center Owner | Information Provision Agreement |
Traffic Management Center Owner | Enforcement Center User | Service Usage Agreement |
Traffic Management Center Owner | ITS Roadway Equipment Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | ITS Roadway Equipment Owner | Information Provision Agreement |
Traffic Management Center Owner | ITS Roadway Equipment User | Service Usage Agreement |
Traffic Management Center Owner | TIC Operator | Application Usage Agreement |
Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
Traffic Management Center Owner | Transit Management Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Transit Management Center Owner | Information Exchange Agreement |
Traffic Management Center Owner | Transit Management Center User | Service Usage Agreement |
Traffic Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Traffic Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
Transit Management Center Maintainer | Transit Management Center | Maintains |
Transit Management Center Manager | Transit Management Center | Manages |
Transit Management Center Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
Transit Management Center Owner | Traffic Management Center Owner | Information Exchange Agreement |
Transit Management Center Owner | Traffic Management Center User | Service Usage Agreement |
Transit Management Center Owner | Transit Management Center Maintainer | System Maintenance Agreement |
Transit Management Center Owner | Transit Management Center Manager | Operations Agreement |
Transit Management Center Owner | Transit Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Transit Management Center Owner | Transit Vehicle OBE Owner | Information Provision Agreement |
Transit Management Center Owner | Transit Vehicle OBE User | Service Usage Agreement |
Transit Management Center Owner | Transit Vehicle Operator | Application Usage Agreement |
Transit Management Center Supplier | Transit Management Center Owner | Warranty |
Transit Vehicle OBE Maintainer | Transit Vehicle OBE | Maintains |
Transit Vehicle OBE Manager | Transit Vehicle OBE | Manages |
Transit Vehicle OBE Manager | Transit Vehicle Operator | System Usage Agreement |
Transit Vehicle OBE Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
Transit Vehicle OBE Owner | Connected Vehicle Roadside Equipment Owner | Expectation of Data Provision |
Transit Vehicle OBE Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
Transit Vehicle OBE Owner | Transit Management Center Maintainer | Maintenance Data Exchange Agreement |
Transit Vehicle OBE Owner | Transit Management Center Owner | Expectation of Data Provision |
Transit Vehicle OBE Owner | Transit Management Center User | Service Usage Agreement |
Transit Vehicle OBE Owner | Transit Vehicle OBE Maintainer | System Maintenance Agreement |
Transit Vehicle OBE Owner | Transit Vehicle OBE Manager | Operations Agreement |
Transit Vehicle OBE Supplier | Transit Vehicle OBE Owner | Warranty |
Transit Vehicle Operator | Transit Vehicle OBE | 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 | Driver | Application Usage Agreement |
Transportation Information Center Owner | Transit Vehicle OBE Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Transit Vehicle OBE Owner | Information Provision Agreement |
Transportation Information Center Owner | Transit Vehicle OBE User | Service Usage Agreement |
Transportation Information Center Owner | Transit Vehicle 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 Provision Agreement |
Transportation Information Center Owner | Vehicle User | Service Usage Agreement |
Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
Vehicle Characteristics Maintainer | Vehicle Characteristics | Maintains |
Vehicle Characteristics Manager | Vehicle Characteristics | Manages |
Vehicle Characteristics Owner | Vehicle Characteristics Maintainer | System Maintenance Agreement |
Vehicle Characteristics Owner | Vehicle Characteristics Manager | Operations Agreement |
Vehicle Characteristics Supplier | Vehicle Characteristics Owner | Warranty |
Vehicle Maintainer | Vehicle | Maintains |
Vehicle Manager | Driver | System Usage Agreement |
Vehicle Manager | Vehicle | Manages |
Vehicle Owner | Basic Vehicle Maintainer | Maintenance Data Exchange Agreement |
Vehicle Owner | Basic Vehicle Owner | Expectation of Data Provision |
Vehicle Owner | Basic Vehicle User | Service Usage Agreement |
Vehicle Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
Vehicle Owner | Connected Vehicle Roadside Equipment Owner | Expectation of Data Provision |
Vehicle Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
Vehicle Owner | Driver | Application Usage Agreement |
Vehicle Owner | Driver | Vehicle Operating 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 |
---|---|---|
Basic Vehicle | Vehicle | 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles. |
Connected Vehicle Roadside Equipment | Field | 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
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. |
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. |
Transit Management Center | Center | The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems. |
Transit Vehicle OBE | Vehicle | The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles. |
Transit Vehicle Operator | Vehicle | The 'Transit Vehicle Operator' represents the person that receives and provides additional information that is specific to operating the ITS functions in all types of transit vehicles. The information received by the operator would include status of on-board systems. Additional information received depends upon the type of transit vehicle. In the case of fixed route transit vehicles, the Transit Vehicle Operator would receive operator instructions that might include actions to take to correct schedule deviations. In the case of flexible fixed routes and demand response routes the information would also include dynamic routing or passenger pickup information. |
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, 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) 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 |
---|---|---|
Roadway Basic Surveillance | 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. | ITS Roadway Equipment |
Roadway Dynamic Lane Management and Shoulder Use | 'Roadway Dynamic Lane Management and Shoulder Use' includes the field equipment, physical overhead lane signs and associated control electronics that are used to manage and control specific lanes and/or the shoulders. This equipment can be centrally controlled by a Traffic Management Center or it can be autonomous and monitor traffic conditions and demand along the roadway and determine how to change the lane controls to respond to current conditions. Lane controls can be used to change the lane configuration of the roadway, reconfigure intersections and/or interchanges, allow use of shoulders as temporary travel lanes, designate lanes for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), vehicles attending a special event, etc. and/or prohibit or restrict types of vehicles from using particular lanes. Guidance and information for drivers can be posted on dynamic message signs. | ITS Roadway Equipment |
Roadway Traffic Information Dissemination | 'Roadway Traffic Information Dissemination' includes field elements that provide information to drivers, including dynamic message signs and highway advisory radios. | ITS Roadway Equipment |
RSE Restricted Lanes Application | The 'RSE Restricted Lanes Application' uses short range communications to monitor and manage dynamic and static restricted lanes. It collects vehicle profile information from vehicles entering the lanes and monitors vehicles within the lanes, providing aggregate data to the back office center. It provides lane restriction information and signage data to the vehicles and optionally identifies vehicles that violate the current lane restrictions. These functions are performed based on operating parameters provided by the back office managing center(s). | 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 Traffic Control Dissemination | 'TIC Traffic Control Dissemination' disseminates intersection status, lane control information, 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 Center(s) and disseminates the relevant information to vehicles and other mobile devices. | Transportation Information Center |
TMC Basic Surveillance | 'TMC Basic Surveillance' remotely monitors and controls traffic sensor systems and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. | Traffic Management Center |
TMC Dynamic Lane Management and Shoulder Use | 'TMC Dynamic Lane Management and Shoulder Use' remotely monitors and controls the system that is used to dynamically manage travel lanes, including temporary use of shoulders as travel lanes. It monitors traffic conditions and demand measured in the field and determines when the lane configuration of the roadway should be changed, when intersections and/or interchanges should be reconfigured, when the shoulders should be used for travel (as a lane), when lanes should be designated for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), vehicles attending a special event, etc. and/or when types of vehicles should be prohibited or restricted from using particular lanes. It controls the field equipment used to manage and control specific lanes and the shoulders. It also can automatically notify the enforcement agency of lane control violations. | Traffic Management Center |
TMC In-Vehicle Signing Management | 'TMC In-Vehicle Signing Management' controls and monitors RSEs that support in-vehicle signing. Sign information that may include static regulatory, service, and directional sign information as well as variable information such as traffic and road conditions can be provided to the RSE, which uses short range communications to send the information to in-vehicle equipment. Information that is currently being communicated to passing vehicles and the operational status of the field equipment is monitored by this application. The operational status of the field equipment is reported to operations personnel. | Traffic Management Center |
TMC Restricted Lanes CV Application | 'TMC Restricted Lanes CV Application' manages dynamic lanes for connected vehicles. The application provides the back office functions and supports the TMC operator in establishing and managing dynamic lanes using communications to manage lane use for connected vehicles. | Traffic Management Center |
TMC Traffic Information Dissemination | 'TMC Traffic Information Dissemination' disseminates traffic and road conditions, closure and detour information, incident information, driver advisories, and other traffic-related data to other centers, the media, and driver information systems. It monitors and controls driver information system field equipment including dynamic message signs and highway advisory radio, managing dissemination of driver information through these systems. | Traffic Management Center |
Transit Center Priority Management | 'Transit Center Priority Management' monitors transit schedule performance and generates requests for transit priority on routes and at certain intersections. It may coordinate with the Traffic Management Center to provide transit priority along the selected route, including allocation of dynamic lanes and granting signal priority. It also coordinates with the Transit Vehicle OBE to monitor and manage local transit signal priority requests at individual intersections. | Transit Management Center |
Transit Vehicle Schedule Management | 'Transit Vehicle Schedule Management' monitors schedule performance and identifies corrective actions when a deviation is detected. It provides two-way communication between the transit vehicle and center, enabling the center to communicate with the vehicle operator and monitor on-board systems. | Transit Vehicle OBE |
Vehicle Basic Safety Communication | 'Vehicle Basic Safety Communication' exchanges current vehicle location and motion information with other vehicles in the vicinity, 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. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. 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 may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. | Vehicle |
Vehicle Basic Safety Communication | 'Vehicle Basic Safety Communication' exchanges current vehicle location and motion information with other vehicles in the vicinity, 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. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. 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 may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. | Vehicle |
Vehicle Restricted Lanes Application | The 'Vehicle Restricted Lanes Application' monitors and reports its own operating parameters and communicates with roadside equipment to safely enter, operate within, and exit restricted lanes that are relevant to all types of vehicles. | Vehicle |
Vehicle Restricted Lanes Application | The 'Vehicle Restricted Lanes Application' monitors and reports its own operating parameters and communicates with roadside equipment to safely enter, operate within, and exit restricted lanes that are relevant to all types of vehicles. | Vehicle |
Includes Information Flows:
Information Flow | Description |
---|---|
access violation notification | Notification that an individual vehicle or user has committed an access violation. The flow identifies the nature of the violation and the time and location where the violation was recorded. |
current lane restrictions | Information provided to an enforcement agency that defines the current enforceable lane restrictions. It defines the location, duration, and restrictions for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, and speed limits. |
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 input information | Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment. |
driver update information | Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback. |
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. |
dynamic bus lane request | Request for a restricted bus lane. May also describe affected services and include schedules with specific vehicle arrival times. |
dynamic bus lane status | Status of dynamic lane request, identifying if the request can be met, and the specific lane, start, end location, and time period where priority or exclusive access is to be granted. |
host vehicle status | Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment. |
lane management control | Information used to configure and control dynamic lane management systems. |
lane management information | System status of managed lanes including current operational state, violations, and logged information. This includes lane usage information including both traditional traffic flow measures and special information associated with managed lanes such as measured passenger occupancies. It also includes the operational status of the lane management equipment. |
lane violation notification | Notification to enforcement agency of detected lane entry violations, lane speed violations, or other dynamic lane violations. Lane entry violations may be issued for restricted vehicle types or vehicles that do not meet required emissions or passenger occupancy standards that enter a managed lane. This notification identifies the vehicle and documents the lane parameter that was violated. |
restricted lanes application info | Restricted lane application configuration data and messaging parameters. This flow defines the location, duration, and operating parameters for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It may also identify additional vehicles that may be allowed in the lanes as exceptions, though they don't meet specified criteria. It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, speed limits and platooning parameters. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. |
restricted lanes application status | Current RSE application status that is monitored by the back office center including the operational state of the RSE, current configuration parameters, and a log of lane use (aggregate profiles of vehicles that checked in to the lane and reported vehicle speeds in the lanes) and RSE communications activity. |
restricted lanes information | This flow defines the location, duration, and operating parameters for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, speed limits and platooning parameters. |
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. |
traffic detector control | Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. |
traffic detector data | Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. |
traffic images | High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. |
transit schedule information | Current and projected transit schedule information used to initialize the transit vehicle with a vehicle assignment, monitor schedule performance, and develop corrective actions on-board. |
transit vehicle operator display | Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services. |
transit vehicle operator input | Transit vehicle operator inputs to on-board ITS equipment, including tactile and verbal inputs. Includes authentication information, on-board system control, emergency requests, and fare transaction data. |
transit vehicle schedule performance | Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle. |
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. |
vehicle location and motion | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. |
vehicle profile | Information about a vehicle such as vehicle make and model, fuel type, engine type, size and weight, vehicle performance and level of control automation, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions or participation in cooperative vehicle control applications. |
vehicle signage application info | In-vehicle signing application configuration data and messaging parameters. This flow provides a list of regulatory, warning, and information messages to be displayed and parameters that support scheduling and prioritizing messages to be issued to passing vehicles. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. |
vehicle signage application status | In-vehicle signing application status reported by the RSE. This includes current operational state and status of the RSE and a log of messages sent to passing vehicles. |
vehicle signage data | In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., local traffic and road conditions, restrictions, vehicle requirements, work zones, detours, closures, advisories, and warnings). |
vehicle signage local data | Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data. |
video surveillance control | Information used to configure and control video surveillance systems. |
Goals and Objectives
Associated Planning Factors and Goals
Planning Factor | Goal |
---|---|
D. Increase the accessibility and mobility of people and for freight; | Reduce congestion |
G. Promote efficient system management and operation; | Improve efficiency |
Associated Objective Categories
Objective Category |
---|
Transit Operations and Management: Line-Haul Transit |
Associated Objectives and Performance Measures
Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. | TMC Basic Surveillance | 06 | The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each). |
TMC Dynamic Lane Management and Shoulder Use | 01 | The center shall remotely monitor and control dynamically managed travel lanes. | ||
02 | The center shall monitor traffic conditions and demand measured per lane. | |||
08 | The center shall support temporary use of shoulders as travel lanes. | |||
10 | The center shall identify lane use restrictions, prohibiting specific types of vehicles (e.g., commercial vehicles) from specific lanes. | |||
11 | The center shall designate lanes for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), or vehicles attending a special event. | |||
14 | The center shall reconfigure intersections and interchanges for compatibility with the current lane configuration. | |||
17 | The center shall accept requests for dedicated bus lanes from the transit center. | |||
TMC Restricted Lanes CV Application | 03 | The Center shall notify a Transit Center of the status of a dynamic transit lane. | ||
09 | The center shall provide current lane access requirements and restrictions to roadside equipment to provide to connected vehicles. | |||
Transit Center Priority Management | 05 | The center shall identify if the request for specific lane can be met, and the specific lane, start, end location, and time period where priority or exclusive access is to be granted. | ||
Transit Vehicle Schedule Management | 02 | The transit vehicle shall use the route information and its current location to determine the deviation from the predetermined schedule. | ||
03 | The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops. | |||
04 | The transit vehicle shall determine scenarios to correct the schedule deviation. | |||
06 | The transit vehicle shall send the schedule deviation and estimated arrival time information to the center. | |||
Vehicle Basic Safety Communication | 06 | The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles. | ||
02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. | Roadway Traffic Information Dissemination | 01 | The field element shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close). |
03 | The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center. | |||
RSE Restricted Lanes Application | 02 | The field device shall provide lane restriction information and signage data to vehicles. | ||
RSE Traveler Information Communications | 04 | The field element shall return system operational status to the controlling center. | ||
12 | The field element shall provide data about bus lanes to vehicles. | |||
TIC Traffic Control Dissemination | 01 | The center shall provide intersection status, lane control information, and other real time traffic control related information to vehicles. | ||
TMC Basic Surveillance | 06 | The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each). | ||
TMC Dynamic Lane Management and Shoulder Use | 09 | The center shall activate lane management field equipment that is used to dynamically manage specific lanes and shoulders. | ||
18 | The center shall notify the transit center of dedicated bus lane status. | |||
TMC In-Vehicle Signing Management | 04 | The center shall receive system operational status from field equipment that supports in-vehicle signage communications. | ||
06 | The center shall format and output restricted lane information to field equipment that supports in-vehicle signage communications. | |||
TMC Restricted Lanes CV Application | 01 | The Center shall notify drivers and vehicles when a travel lane is a dedicated bus lane. | ||
02 | The Center shall notify drivers and vehicles when a dedicated bus lane becomes an open travel lane. | |||
09 | The center shall provide current lane access requirements and restrictions to roadside equipment to provide to connected vehicles. | |||
TMC Traffic Information Dissemination | 02 | The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers. | ||
03 | The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.). | |||
04 | The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair. | |||
09 | The center shall collect current lane configurations status for the driver information systems equipment (DMS, HAR, etc.). | |||
Transit Vehicle Schedule Management | 01 | The transit vehicle shall receive a vehicle assignment including transit route information, transit service instructions, traffic information, road conditions, and other information for the operator. | ||
04 | The transit vehicle shall determine scenarios to correct the schedule deviation. | |||
05 | The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle operator if the deviation is small, or the transit vehicle is operating in an urban area. | |||
03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. | Roadway Basic Surveillance | 01 | The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control. |
04 | The field element shall return sensor and CCTV system operational status to the controlling center. | |||
Roadway Dynamic Lane Management and Shoulder Use | 06 | The field element shall collect vehicle profile information from individual vehicles using field-vehicle communications. | ||
07 | The field element shall monitor current lane usage to determine if vehicles are complying with current lane use restrictions. | |||
08 | The field element shall capture vehicle information, including vehicle image(s) of vehicles violating current lane usage restrictions and report violations to the controlling center. | |||
RSE Restricted Lanes Application | 01 | The field device shall collect vehicle profile information from vehicles entering the lanes and monitors vehicles within the lanes. | ||
TMC Basic Surveillance | 01 | The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center. | ||
02 | The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center. | |||
05 | The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution. | |||
07 | The center shall remotely control devices to detect traffic. | |||
TMC Dynamic Lane Management and Shoulder Use | 15 | The center shall notify the enforcement agency of violators of the lane controls. | ||
TMC Restricted Lanes CV Application | 04 | The center shall notify enforcement when a violation of the dynamic transit lane usage is detected. | ||
Vehicle Restricted Lanes Application | 01 | The vehicle shall provide operating parameters to the roadside in order to identify that it qualifies for use of a restricted lane. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
CO-UMP Flexible Infrastructure | 5/31/2021 | |
ConOps for Transit Connected Vehicle | Draft | 3/31/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 |
Basic Vehicle | ||||
Connected Vehicle Roadside Equipment | Moderate | High | Moderate | Class 3 |
Enforcement Center | Moderate | Moderate | Moderate | Class 2 |
ITS Roadway Equipment | Moderate | Moderate | Moderate | Class 2 |
Traffic Management Center | Moderate | High | Moderate | Class 3 |
Transit Management Center | Moderate | Moderate | Moderate | Class 2 |
Transit Vehicle OBE | Low | Moderate | Moderate | Class 1 |
Transportation Information Center | Not Applicable | Moderate | Moderate | Class 1 |
Vehicle | Moderate | High | Moderate | Class 3 |
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 | |||
Basic Vehicle | Vehicle | driver input information | Moderate | High | High |
Internal vehicle flow that if reverse engineered could enable third party vehicle control. Largely a competitive question, could be set LOW if manufacturer and operator are not concerned with this type of compromise. | Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation. | Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation. | |||
Basic Vehicle | Vehicle | host vehicle status | Low | Moderate | High |
Unlikely that this includes any information that could be used against the originator. | This can be MODERATE or HIGH, depending on the application: This is used later on to determine whether a vehicle is likely going to violate a red light or infringe a work zone. This needs to be correct in order for the application to work correctly. | Since this monitors the health and safety of the vehicle and that information is eventually reported to the driver, it should be available at all times as it directly affects vehicle and operator safety. | |||
Connected Vehicle Roadside Equipment | Enforcement Center | lane 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. | 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. Must be correct to avoid false accusations. | More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies. | |||
Connected Vehicle Roadside Equipment | ITS Roadway Equipment | restricted lanes 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 | Traffic Management Center | restricted lanes 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 | Traffic Management Center | vehicle signage 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. DISC: WYO believes this to be LOW | 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 | access violation notification | Moderate | High | Moderate |
May contain PII of a black listed user account, and/or vehicle identification. | Given the potential for PII to be involved, this needs to be correct and unalterable to avoid confusion or malfeasance. | Availability is at least MODERATE since the information has potential legal (or at least traffic law) implications that would otherwise involve a far less prompt and possibly manpower intensive interaction. | |||
Connected Vehicle Roadside Equipment | Vehicle | restricted lanes information | Not Applicable | Moderate | Moderate |
Broadcast and intended for public consumption. | Should be correct or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. In areas with a noted significant safety impact due to illegitimate use of the limited access facility, this may be HIGH. | Should be timely or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. | |||
Connected Vehicle Roadside Equipment | Vehicle | vehicle signage data | Low | Moderate | Moderate |
This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone. | These signs are meant to augment other visual cues to the driver. They should be accurate, but any inaccuracies should be corrected for by other means. | These notifications are helpful to a driver, but if the driver does not receive this notification immediately, there should still be other visual cues. | |||
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. | |||
ITS Roadway Equipment | Connected Vehicle Roadside Equipment | vehicle signage local data | Low | Moderate | Moderate |
This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone. | This information impacts the vehicle signage data sent to neighboring ASDs and should be trusted to avoid sending wrong information. DISC: WYO believes this to be HIGH. | The system should know if these messages are not received. | |||
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 | Traffic Management Center | lane management information | Moderate | Moderate | Moderate |
May contain PII, may contain source data describing device control and sensed status that if captured could be used in the commission of a crime or breaking of traffic laws or regulations. | Information related to violations must be correct so that incorrect accusations are not made. Information related to device status and control must be correct to avoid wasted maintenance efforts. | More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies. | |||
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 | traffic detector data | Low | Moderate | Moderate |
No impact if someone sees the data | Some minimal guarantee of data integrity is necessary for all C-ITS flows. THEA believes this to be LOW.only limited adverse effect if raw/processed traffic detector data is bad/compromised; DISC: WYO believes this to be HIGH | Only limited adverse effect of info is not timely/readily available, however without this information it will be difficult to perform traffic management activities, thus MODERATE. If not used for management, may be LOW. | |||
ITS Roadway Equipment | Traffic Management Center | traffic image meta data | Low | Moderate | Moderate |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
ITS Roadway Equipment | Traffic Management Center | traffic images | Low | Moderate | Low |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
ITS Roadway Equipment | Transit Vehicle Operator | 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 will happen. | If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a knock-on effect due to lack of coordination with other intersections. | |||
Traffic Management Center | Connected Vehicle Roadside Equipment | restricted lanes application info | Low | Moderate | Moderate |
Broadcast and intended for public consumtion. | Should be correct or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. In areas with a noted significant safety impact due to illegitimate use of the limited access facility, this may be HIGH. | Should be timely or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. | |||
Traffic Management Center | Connected Vehicle Roadside Equipment | vehicle signage application info | Moderate | Moderate | 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. | If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, or not properly communicate areas where maintenance workers are operating for example. Not HIGH because regardless of the application, this flow alone does not directly drive injury or damage. DISC: WYO believes this to be HIGH. | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. This data should be received in a timely manner after it is sent. This will determine which lanes are blocked off for emergency vehicle use in incident management applications. 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. | |||
Traffic Management Center | Enforcement Center | current lane restrictions | Low | High | Moderate |
Public policies about enforcement conditions are by definition public and should not be hidden. | Given that punishments may result from applying the information contained within to individual violations, the data must be correct or incorrect accusations may be made. | More or less important depending on the context. Given that decision making is taken based on this information, probably should not drop below MODERATE however. | |||
Traffic Management Center | Enforcement Center | lane 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. | 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. Must be correct to avoid false accusations. | More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies. | |||
Traffic Management Center | ITS Roadway Equipment | lane management 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. | 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. | |||
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 | traffic detector control | Moderate | Moderate | 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. DISC: THEA, WYO believe this to be LOW: encrypted, authenticated, proprietary; but should not cause severe damage if seen | 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: should be accurate and not be tampered with; could enable outside control of traffic sensors but should not cause severe harm, but could cause issues with traffic sensor data received and be detrimental to operations | 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 delayed information will not be severe; should be able to operate from a previous/default control/config. DISC: WYO believes this to be MODERATE | |||
Traffic Management Center | ITS Roadway Equipment | video surveillance control | Moderate | Moderate | 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. | 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. | |||
Traffic Management Center | Transit Management Center | dynamic bus lane status | Moderate | Moderate | Moderate |
Should probably not be observable to prevent third party knowledge of which transit vehicles have priority. Vehicles with priority could be targeted to 'follow the wave' which can have a negative effect on safety and overall mobility. | This information is important for the system to function correctly. If it is incorrect, it could lead to the transit system designing routes that do not take advantage of the optimizations. | This information is necessary for the system to operate properly. There should be an acknowledgement of the message being received. | |||
Traffic Management Center | Transportation Information Center | restricted lanes information | Not Applicable | Moderate | Moderate |
Broadcast and intended for public consumption. | Should be correct or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. In areas with a noted significant safety impact due to illegitimate use of the limited access facility, this may be HIGH. | Should be timely or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. | |||
Transit Management Center | Traffic Management Center | dynamic bus lane request | Moderate | Moderate | Moderate |
Contains bus location, predictive data and other information that could be used by an attacker to determine how the roadway network is being managed and leverage that information in the commission of a crime. | Needs to be correct and available so that the bus lane request is accomodated if practical. If this information becomes corrupted then bus lane assignment may not function and transit performance will suffer. | Needs to be correct and available so that the bus lane request is accomodated if practical. If this information becomes corrupted then bus lane assignment may not function and transit performance will suffer. | |||
Transit Management Center | Transit Vehicle OBE | transit schedule information | Low | Moderate | Moderate |
This information is not sensitive. It is generally made public, to support transit system functionality. | This data contains the vehicle assignment. It should be accurate, and not easily modified. However, the bus drivers will have some knowledge about what a reasonable configuration is, and should be able to notice any unusual configurations, such as all busses being a #27. | This information is necessary for the TSP to work correctly. A few missed messages will not have a large impact. The Transit Management Center needs to know if the TV OBE does not receive the message, so it can resend it. | |||
Transit Vehicle OBE | Transit Management Center | transit vehicle schedule performance | Low | Moderate | Low |
This information is directly observable, and in most instances it is made publically available. | This information may be used to influence the decision about whether or not to make a traffic control priority request on behalf of the transit vehicle. If it is incorrect it may cause the transit management center to send out incorrect traffic control priority requests, which may delay traffic. | There should not be any catastrophic failures caused if this data is occasionally missing. | |||
Transit Vehicle OBE | Transit Vehicle Operator | transit vehicle operator display | Low | Moderate | Low |
This should not include any sensitive information. It would be possible for a person standing behind the driver to observe the information transmitted. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. This entire application should not directly affect the drivers driving habits. The operator should still be slowing and stopping at yellow or red lights, along with observing all other driving regulations. DISC: Original V2I analysis classified this as LOW. | Even if the operator is not made aware of the signal preemption, the system should still operate correctly. The operator should be using the traffic lights to influence their decision about whether or not to stop, not the display. | |||
Transit Vehicle Operator | Transit Vehicle OBE | transit vehicle operator input | Low | Moderate | Low |
This information is transmitted through systems on board the Transit Vehicle. Even if the vehicle were compromised and these communications monitored, most of this information is directly observable. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. If this is compromised, it could result in an incorrect signal priority request, which has minimal impact. DISC: Original V2I analysis classified this as LOW. | A delay in reporting this may result in a signal priority request not going through, which has minimal impact. | |||
Transportation Information Center | Vehicle | restricted lanes information | Not Applicable | Moderate | Moderate |
Broadcast and intended for public consumption. | Should be correct or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. In areas with a noted significant safety impact due to illegitimate use of the limited access facility, this may be HIGH. | Should be timely or receiving vehicles may not take advantage of (if licensed) or violate (if not) limited access lanes. While there could be a safety impact, this is generally not the case. | |||
Vehicle | Basic Vehicle | driver update information | Low | Moderate | Moderate |
This information is all presented to the vehicle operator. Encrypting this information may make it harder to reverse engineer vehicle systems, and may defeat criminal tracking tools when the vehicle has already been compromised. Unless those scenarios are of concern to the operator or manufacturer, this can safely be set LOW. | Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. | Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. | |||
Vehicle | Connected Vehicle Roadside Equipment | 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 | Incorrect information could lead to the system not operating properly. If the system does not properly know where the vehicle is, it cannot make an accurate decision about whether there is going to be a pedestrian in the crosswalk that the vehicle is approaching. This can have a safety impact.; DISC: NYC believes this to be MODERATE | This data is required for the system to operate properly. If this data is not available, the system cannot give accurate warning information. | |||
Vehicle | Connected Vehicle Roadside Equipment | vehicle profile | Low | Moderate | Moderate |
Includes no PII and probably includes information that could be observed, so no need for obfuscation. | As this information will be used to determine the vehicle's ability to access services or be charged usage fees, it must be correct and not easily forgeable. | This flow enables various services; if the flow is not available the vehicle may not be able to use those services, and also may be charged incorrectly. | |||
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. |
Standards
The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.
Name | Title | Physical Object |
---|---|---|
CTI 4001 RSU | Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) | Connected Vehicle Roadside Equipment |
ITE ATC | Advanced Transportation Controller | ITS Roadway Equipment |
ITE ATC API | Application Programming Interface Standard for the Advanced Transportation Controller | ITS Roadway Equipment |
ITE ATC ITS Cabinet | Intelligent Transportation System Standard Specification for Roadside Cabinets | ITS Roadway Equipment |
ITE ATC Model 2070 | Model 2070 Controller Standard | ITS Roadway Equipment |
NEMA TS 8 Cyber and Physical Security | Cyber and Physical Security for Intelligent Transportation Systems | ITS Roadway Equipment |
Traffic Management Center | ||
NEMA TS2 Traffic Controller Assemblies | Traffic Controller Assemblies with NTCIP Requirements | ITS Roadway Equipment |
NEMA TS4 Hardware Standards for DMS | Hardware Standards for Dynamic Message Signs (DMS) With NTCIP Requirements | ITS Roadway Equipment |
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall provide intersection status, lane control information, and other real time traffic control related information to vehicles. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
002 | The system shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
003 | The system shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
004 | The system shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
005 | The system shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each). | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. | ||
006 | The system shall remotely control devices to detect traffic. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
007 | The system shall remotely monitor and control dynamically managed travel lanes. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
008 | The system shall monitor traffic conditions and demand measured per lane. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
009 | The system shall support temporary use of shoulders as travel lanes. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
010 | The system shall activate lane management field equipment that is used to dynamically manage specific lanes and shoulders. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
011 | The system shall identify lane use restrictions, prohibiting specific types of vehicles (e.g., commercial vehicles) from specific lanes. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
012 | The system shall designate lanes for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), or vehicles attending a special event. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
013 | The system shall reconfigure intersections and interchanges for compatibility with the current lane configuration. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
014 | The system shall notify the enforcement agency of violators of the lane controls. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
015 | The system shall accept requests for dedicated bus lanes from the transit center. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
016 | The system shall notify the transit center of dedicated bus lane status. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
017 | The system shall receive system operational status from field equipment that supports in-vehicle signage communications. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
018 | The system shall format and output restricted lane information to field equipment that supports in-vehicle signage communications. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
019 | The system shall notify drivers and vehicles when a travel lane is a dedicated bus lane. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
020 | The system shall notify drivers and vehicles when a dedicated bus lane becomes an open travel lane. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
021 | The system shall notify a Transit Center of the status of a dynamic transit lane. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
022 | The system shall notify enforcement when a violation of the dynamic transit lane usage is detected. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
023 | The system shall provide current lane access requirements and restrictions to roadside equipment to provide to connected vehicles. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. | ||
024 | The system shall remotely control driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
025 | The system shall collect operational status for the driver information systems equipment (DMS, HAR, etc.). | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
026 | The system shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
027 | The system shall collect current lane configurations status for the driver information systems equipment (DMS, HAR, etc.). | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
028 | The system shall identify if the request for specific lane can be met, and the specific lane, start, end location, and time period where priority or exclusive access is to be granted. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
029 | The system shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
030 | The system shall return sensor and CCTV system operational status to the controlling center. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
031 | The system shall collect vehicle profile information from individual vehicles using field-vehicle communications. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
032 | The system shall monitor current lane usage to determine if vehicles are complying with current lane use restrictions. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
033 | The system shall capture vehicle information, including vehicle image(s) of vehicles violating current lane usage restrictions and report violations to the controlling center. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
034 | The system shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle r | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
035 | The system shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
036 | The system shall collect vehicle profile information from vehicles entering the lanes and monitors vehicles within the lanes. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
037 | The system shall provide lane restriction information and signage data to vehicles. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
038 | The system shall return system operational status to the controlling center. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
039 | The system shall provide data about bus lanes to vehicles. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
040 | The system shall receive a vehicle assignment including transit route information, transit service instructions, traffic information, road conditions, and other information for the operator. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
041 | The system shall use the route information and its current location to determine the deviation from the predetermined schedule. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
042 | The system shall calculate the estimated times of arrival (ETA) at transit stops. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
043 | The system shall determine scenarios to correct the schedule deviation. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. | ||
044 | The system shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle operator if the deviation is small, or the transit vehicle is operating in an urban area. | 02 | Traffic Operations needs to be able to notify drivers regarding the status of the intermittent bus lane. |
045 | The system shall send the schedule deviation and estimated arrival time information to the center. | 01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
046 | The system shall provide operating parameters to the roadside in order to identify that it qualifies for use of a restricted lane. | 03 | Traffic Operations needs to be able to notify enforcement of vehicle violations in the bus lanes. |
01 | Traffic Operations needs to be able to open and close intermittent bus lanes based on fixed times or based on request from Transit Operations in order to improve the efficiency of transit operations. |
Implementations
PT10.1 Wide-Area Wireless Implementation
Intermittent bus lanes are negotiated between Traffic and Transit Management Centers and wide-area wireless communications are used to communicate current lane status information to transit vehicles and other vehicles in the area. Dynamic message signs are used to communicate intermittent lane status to unequipped vehicles.
Wide-Area Wireless Implementation Flows
Information Flow | Description | Inclusion Status |
---|---|---|
current lane restrictions | Information provided to an enforcement agency that defines the current enforceable lane restrictions. It defines the location, duration, and restrictions for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, and speed limits. | Optional |
driver information | Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. | Fundamental |
driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. | Optional |
driver input information | Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment. | Optional |
driver update information | Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback. | Optional |
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. | Optional |
dynamic bus lane request | Request for a restricted bus lane. May also describe affected services and include schedules with specific vehicle arrival times. | Fundamental |
dynamic bus lane status | Status of dynamic lane request, identifying if the request can be met, and the specific lane, start, end location, and time period where priority or exclusive access is to be granted. | Fundamental |
host vehicle status | Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment. | Optional |
lane management control | Information used to configure and control dynamic lane management systems. | Fundamental |
lane management information | System status of managed lanes including current operational state, violations, and logged information. This includes lane usage information including both traditional traffic flow measures and special information associated with managed lanes such as measured passenger occupancies. It also includes the operational status of the lane management equipment. | Fundamental |
lane violation notification | Notification to enforcement agency of detected lane entry violations, lane speed violations, or other dynamic lane violations. Lane entry violations may be issued for restricted vehicle types or vehicles that do not meet required emissions or passenger occupancy standards that enter a managed lane. This notification identifies the vehicle and documents the lane parameter that was violated. | Optional |
restricted lanes information | This flow defines the location, duration, and operating parameters for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, speed limits and platooning parameters. | Fundamental |
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. | Optional |
roadway dynamic signage status | Current operating status of dynamic message signs. | Optional |
traffic detector control | Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. | Optional |
traffic detector data | Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors | Optional |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. | Optional |
traffic images | High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. | Optional |
transit schedule information | Current and projected transit schedule information used to initialize the transit vehicle with a vehicle assignment, monitor schedule performance, and develop corrective actions on-board. | Optional |
transit vehicle operator display | Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services. | Optional |
transit vehicle operator input | Transit vehicle operator inputs to on-board ITS equipment, including tactile and verbal inputs. Includes authentication information, on-board system control, emergency requests, and fare transaction data. | Optional |
transit vehicle schedule performance | Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle. | Optional |
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. | Optional |
video surveillance control | Information used to configure and control video surveillance systems. | Optional |
Wide-Area Wireless Implementation Functional Objects
Back to Implementation List
PT10.2 Short Range Communications Implementation
Intermittent bus lanes are negotiated between Traffic and Transit Management Centers and short range wireless communications are used to communicate current lane status information to vehicles approaching the intermittent lanes area. This implementation also includes use of dynamic message signs to support unequipped vehicles.
Short Range Communications Implementation Flows
Information Flow | Description | Inclusion Status |
---|---|---|
access violation notification | Notification that an individual vehicle or user has committed an access violation. The flow identifies the nature of the violation and the time and location where the violation was recorded. | Optional |
current lane restrictions | Information provided to an enforcement agency that defines the current enforceable lane restrictions. It defines the location, duration, and restrictions for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, and speed limits. | Optional |
driver information | Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. | Fundamental |
driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. | Optional |
driver input information | Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment. | Optional |
driver update information | Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback. | Optional |
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. | Optional |
dynamic bus lane request | Request for a restricted bus lane. May also describe affected services and include schedules with specific vehicle arrival times. | Fundamental |
dynamic bus lane status | Status of dynamic lane request, identifying if the request can be met, and the specific lane, start, end location, and time period where priority or exclusive access is to be granted. | Fundamental |
host vehicle status | Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment. | Optional |
lane management control | Information used to configure and control dynamic lane management systems. | Fundamental |
lane management information | System status of managed lanes including current operational state, violations, and logged information. This includes lane usage information including both traditional traffic flow measures and special information associated with managed lanes such as measured passenger occupancies. It also includes the operational status of the lane management equipment. | Fundamental |
lane violation notification | Notification to enforcement agency of detected lane entry violations, lane speed violations, or other dynamic lane violations. Lane entry violations may be issued for restricted vehicle types or vehicles that do not meet required emissions or passenger occupancy standards that enter a managed lane. This notification identifies the vehicle and documents the lane parameter that was violated. | Optional |
restricted lanes application info | Restricted lane application configuration data and messaging parameters. This flow defines the location, duration, and operating parameters for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It may also identify additional vehicles that may be allowed in the lanes as exceptions, though they don't meet specified criteria. It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, speed limits and platooning parameters. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. | Fundamental |
restricted lanes application status | Current RSE application status that is monitored by the back office center including the operational state of the RSE, current configuration parameters, and a log of lane use (aggregate profiles of vehicles that checked in to the lane and reported vehicle speeds in the lanes) and RSE communications activity. | Fundamental |
restricted lanes application status | Current RSE application status that is monitored by the back office center including the operational state of the RSE, current configuration parameters, and a log of lane use (aggregate profiles of vehicles that checked in to the lane and reported vehicle speeds in the lanes) and RSE communications activity. | Optional |
restricted lanes information | This flow defines the location, duration, and operating parameters for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, speed limits and platooning parameters. | Optional |
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. | Optional |
roadway dynamic signage status | Current operating status of dynamic message signs. | Optional |
traffic detector control | Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. | Optional |
traffic detector data | Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors | Optional |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. | Optional |
traffic images | High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. | Optional |
transit schedule information | Current and projected transit schedule information used to initialize the transit vehicle with a vehicle assignment, monitor schedule performance, and develop corrective actions on-board. | Optional |
transit vehicle operator display | Visual, audible, and tactile outputs to the transit vehicle operator including vehicle surveillance information, alarm information, vehicle system status, information from the operations center, and information indicating the status of all other on-board ITS services. | Optional |
transit vehicle operator input | Transit vehicle operator inputs to on-board ITS equipment, including tactile and verbal inputs. Includes authentication information, on-board system control, emergency requests, and fare transaction data. | Optional |
transit vehicle schedule performance | Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle. | Optional |
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. | Optional |
vehicle location and motion | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. | Optional |
vehicle location and motion | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. | Fundamental |
vehicle profile | Information about a vehicle such as vehicle make and model, fuel type, engine type, size and weight, vehicle performance and level of control automation, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions or participation in cooperative vehicle control applications. | Optional |
vehicle profile | Information about a vehicle such as vehicle make and model, fuel type, engine type, size and weight, vehicle performance and level of control automation, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions or participation in cooperative vehicle control applications. | Fundamental |
vehicle signage application info | In-vehicle signing application configuration data and messaging parameters. This flow provides a list of regulatory, warning, and information messages to be displayed and parameters that support scheduling and prioritizing messages to be issued to passing vehicles. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. | Optional |
vehicle signage application status | In-vehicle signing application status reported by the RSE. This includes current operational state and status of the RSE and a log of messages sent to passing vehicles. | Optional |
vehicle signage data | In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., local traffic and road conditions, restrictions, vehicle requirements, work zones, detours, closures, advisories, and warnings). | Optional |
vehicle signage local data | Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data. | Optional |
video surveillance control | Information used to configure and control video surveillance systems. | Optional |
Short Range Communications Implementation Functional Objects
Back to Implementation List