< < MC10 : PM01 : PM02 > >

PM01: Parking Space Management

This service package monitors and manages parking spaces in lots, garages, and other parking areas and facilities. It assists in the management of parking operations by monitoring parking lot ingress and egress, parking space occupancy and availability. Infrastructure-based detectors and/or connected vehicles may be used to monitor parking occupancy. The service package shares collected parking information with local drivers and information providers for broader distribution.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Owns
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Parking Management Center Owner Information Exchange Agreement
Connected Vehicle Roadside Equipment Owner Vehicle OBE Owner Expectation of Information Provision
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
Parking Area Equipment Manager Parking Area Equipment Manages
Parking Area Equipment Manager Parking Operator System Usage Agreement
Parking Area Equipment Owner Connected Vehicle Roadside Equipment Owner Information Exchange and Action Agreement
Parking Area Equipment Owner Parking Area Equipment Owns
Parking Area Equipment Owner Parking Area Equipment Manager Operations Agreement
Parking Area Equipment Owner Parking Management Center Owner Information Exchange Agreement
Parking Area Equipment Supplier Parking Area Equipment Owner Warranty
Parking Management Center Manager Parking Management Center Manages
Parking Management Center Manager Parking Manager System Usage Agreement
Parking Management Center Owner Connected Vehicle Roadside Equipment Owner Information Exchange Agreement
Parking Management Center Owner Parking Area Equipment Owner Information Exchange Agreement
Parking Management Center Owner Parking Management Center Owns
Parking Management Center Owner Parking Management Center Manager Operations Agreement
Parking Management Center Owner Traffic Management Center Owner Information Provision Agreement
Parking Management Center Owner Transportation Information Center Owner Information Provision Agreement
Parking Management Center Supplier Parking Management Center Owner Warranty
Parking Manager Parking Management Center Operates
Parking Operator Parking Area Equipment Operates
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Owner Personal Information Device Owns
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Owner Traffic Management Center Owns
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Personal Information Device Owner Information Exchange Agreement
Transportation Information Center Owner Transportation Information Center Owns
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Owner Vehicle OBE Owner Information Exchange Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Vehicle OBE Manager Vehicle OBE Manages
Vehicle OBE Owner Transportation Information Center Owner Information Exchange Agreement
Vehicle OBE Owner Vehicle OBE Owns
Vehicle OBE Owner Vehicle OBE Manager Operations Agreement
Vehicle OBE Supplier Vehicle OBE Owner Warranty

Maintenance Stage Roles and Relationships

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Parking Management 1.1.6 Collect Vehicle Traffic Surveillance Data
1.2.5.8 Manage Roadside Parking Facility Communications
Parking Area Equipment Parking Area Management 1.2.5.13 Manage Commercial Vehicle Parking
1.2.5.3 Provide Parking Lot Operator Interface
1.2.5.6 Detect Vehicles in Parking Lot
1.2.5.7 Output Parking Lot Information to Drivers
Parking Management Center Parking Coordination 1.2.5.1 Provide Parking Lot Static Data
1.2.5.11 Provide Parking Manager Interface
1.2.5.12 Manage Loading Zone Use
1.2.5.2 Coordinate Other Parking Data
1.2.5.4 Determine Dynamic Parking Lot State
7.2.1.9 Manage Parking Lot Reservations
Parking Management 1.2.5.1 Provide Parking Lot Static Data
1.2.5.4 Determine Dynamic Parking Lot State
Personal Information Device Personal Interactive Traveler Information 6.8.1.1.1 Determine Personal Portable Device Guidance Method
6.8.1.1.2 Provide Personal Portable Device Dynamic Guidance
6.8.3.1 Get Traveler Personal Request
6.8.3.2 Provide Traveler with Personal Travel Information
6.8.3.3 Provide Traveler Personal Interface
6.8.3.4 Update Traveler Personal Display Map Data
6.8.3.5 Provide Traveler Transit Services Interface
6.8.3.6 Provide Personal Safety Messages
6.8.3.7 Manage Traveler Personal Social Media Interface
7.5.3 Provide Personal Payment Device Interface
7.6.6.3 Provide Road Use Charging Services Personal Interface
Transportation Information Center TIC Data Collection 6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.2.3 Collect Transit Operations Data
6.2.4 Collect Multimodal Data
6.2.5 Collect Situation and Sensor Data From Vehicles
6.2.6 Collect Emergency Traveler Data
6.5.4 Process Travel Services Provider Data
6.6.2.3 Provide Route Segment Data for Other Areas
7.4.2 Collect Price Data for Traveler Information Use
TIC Interactive Traveler Information 6.10 Manage Traveler Profiles
6.2.1 Collect Misc Traveler Information
6.5.2 Provide Interactive Data Interface
7.4.1.2 Process Travel Services Provider Payments
7.4.1.3 Process Driver Map Update Payments
7.4.1.4 Process Traveler Map Update Payments
7.4.1.6 Process Traveler Trip and Other Services Payments
7.4.1.7 Process Traveler Rideshare Payments
Vehicle OBE Vehicle Basic Safety Communication 3.1.1 Produce Collision and Crash Avoidance Data
3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs
3.2.3.2 Manage Platoon Following
3.2.3.3 Process Data for Vehicle Actuators
3.2.3.5 Process Vehicle Sensor Data
3.2.4 Process Sensor Data for Automatic Vehicle Operations
6.7.1.2 Provide Driver Guidance Interface
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.3 Provide Driver Information Interface
Vehicle Interactive Traveler Information 3.1.3 Process Vehicle On-board Data
3.3.1 Provide Communications Function
6.7.1.2 Provide Driver Guidance Interface
6.7.3.1 Get Driver Personal Request
6.7.3.2 Provide Driver with Personal Travel Information
6.7.3.3 Provide Driver Information Interface
6.7.3.4 Update Driver Display Map Data
7.2.3 Provide Driver Parking Lot Payment Interface
7.2.4 Distribute Advanced Tolls and Fares
7.2.5 Provide Payment Device Interface for Parking
7.5.1 Provide Vehicle Payment Device Interface
Vehicle Roadside Information Reception 3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.2.3.3 Process Data for Vehicle Actuators
6.7.1.2 Provide Driver Guidance Interface
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Get Driver Personal Request
6.7.3.2 Provide Driver with Personal Travel Information
6.7.3.3 Provide Driver Information Interface
7.1.4 Provide Driver Toll Payment Interface

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
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.
Parking Area Equipment Field 'Parking Area Equipment' provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. The two primary approaches to monitoring parking area usage are sensing vehicles within parking spots or counting vehicles as they come in and as they leave the area. This portion of the functionality must be located in the parking area where it can monitor, classify, and share information with customers and their vehicles. See also the separate 'Parking Management Center' physical object that may be located in a back office, remote from the parking area, which interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region.
Parking Management Center Center The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.
Parking Manager Center 'Parking Manager' is the human operator that supports back office operations for one or more parking areas.
Parking Operator Field 'Parking Operator' is the human attendant that may be physically present at the parking lot facility to monitor the operational status of the facility.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Transportation Information Center Center The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Vehicle OBE Vehicle The Vehicle On-Board Equipment (OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The Vehicle OBE includes general capabilities that apply to passenger cars, trucks, and motorcycles. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object Description Physical Object
Parking Area Management 'Parking Area Management' detects and classifies vehicles at parking facility entrances, exits, and other designated locations within the facility. Current parking availability is monitored and used to inform drivers through dynamic message signs/displays so that vehicles are efficiently routed to available spaces. Parking facility information, including current parking rates and directions to entrances and available exits, is also provided to drivers. Parking Area Equipment
Parking Coordination 'Parking Coordination' supports communication and coordination between equipped parking facilities and also supports regional coordination between parking facilities and traffic management systems. Coordination with traffic management supports local traffic control coordination in and around the parking facility and broader regional coordination. It also shares information with transit management systems and information providers to support multimodal travel planning, including parking reservations capabilities. Information including current parking availability, system status, and operating strategies are shared to enable local parking facility management that supports regional transportation strategies. Parking Management Center
Parking Management 'Parking Management' monitors parking area operations for one or more parking areas, monitoring current operational status including current parking occupancy and rates supporting back office operations. Parking Management Center
Personal Interactive Traveler Information 'Personal Interactive Traveler Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones. Personal Information Device
RSE Parking Management 'RSE Parking Management' monitors the basic safety messages generated by connected vehicles to detect vehicles parking and maintain and report spaces that are occupied by connected vehicles. It also uses short range communications to provide parking information to vehicles. Connected Vehicle Roadside Equipment
TIC Data Collection 'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. Transportation Information Center
TIC Interactive Traveler Information 'TIC Interactive Traveler Information' disseminates personalized traveler information including traffic and road conditions, transit information, parking information, maintenance and construction information, multimodal information, event information, and weather information. Tailored information is provided based on the traveler's request in this interactive service. Transportation Information Center
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 OBE
Vehicle Interactive Traveler Information 'Vehicle Interactive Traveler Information' provides drivers with personalized traveler information including traffic and road conditions, transit information, maintenance and construction information, multimodal information, event information, and weather information. The provided information is tailored based on driver requests. Both one-time requests for information and on-going information streams based on a submitted traveler profile and preferences are supported. Vehicle OBE
Vehicle Roadside Information Reception 'Vehicle Roadside Information Reception' receives advisories, vehicle signage data, and other driver information and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. Vehicle OBE

Includes Information Flows:

Information Flow Description
driver parking information Presentation of general parking information to drivers including lot status, parking availability, and directions to available spaces, entrances, and exits.
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.
interactive traveler information Traveler information provided in response to a traveler request. The provided information includes traffic and road conditions, advisories, incidents, restrictions, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations.
parking area information Current status for the parking area. This includes information on general parking area status (operating hours, open entrances and exits, entrance queue status, parking operator information, current parking occupancy and availability).
parking area management information Parameters that support management of a parking area. Hours of operation, parking rules and regulations, parking operator (attendant) information, etc.
parking area status Presentation of information to the parking operator including operational status and transaction reports.
parking availability Information on available parking. This flow identifies available spaces with associated information about parking restrictions and location for each available space. Specifically includes information on parking for commercial vehicles, coaches/buses, and cars - and likely also motorcycles, electric vehicle plugins, etc.
parking information General parking information and status, including current parking availability, parking pricing, and parking space availability information.
parking management application info Parking management application information including parking lot configuration and status and associated parameters and thresholds that control the algorithms that monitor parking occupancy and the parking information that is delivered. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
parking management application status Parking management application status reported by the RSE. This includes current operational state and status of the RSE and current, aggregate parking data collected from connected vehicles that can be used to monitor parking space usage and availability.
parking manager input Input from the parking manager to query current status and control back office operations for a parking management system.
parking operator input User input from the parking operator to query current status and control the operation of the parking management system.
parking status Presentation of information to the parking manager including operational status and transaction reports. This includes aggregated status for parking areas as well as status for back office operations.
traveler request A request for traveler information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences.
vehicle location and motion for surveillance Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
vehicle 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, lane restrictions, 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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
D. Increase the accessibility and mobility of people and for freight; Achieve a significant reduction in congestion
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance the integration and connectivity of the transportation system
G. Promote efficient system management and operation; Improve the efficiency of the surface transportation system

Associated Objective Categories

Objective Category
Special Event Management: Parking Management
Transit Operations and Management: Park-and-Ride Support

Associated Objectives and Performance Measures

Objective Performance Measure
Decrease the time spent clearing special event venue parking lots of vehicles by X percent in Y years following each event. Percent decrease in time to clear parking lots.
Enhance parking facility services and management Number of parking facilities with advanced parking information to customers
Enhance parking facility services and management Number of parking facilities with automated occupancy counting and space management
Enhance parking facility services and management Number of parking facilities with coordinated availability information
Enhance parking facility services and management Number of parking facilities with coordinated electronic payment systems
Enhance parking facility services and management Number of parking facilities with electronic fee collection
Enhance parking facility services and management Number parking facilities with electronic fee collection
Increase the number of special events that use shared parking facilities (e.g., parking lots of nearby businesses or organizations) by X percent in Y years. Number of special events that use shared parking facilities.
Increase the use of flexible pricing mechanisms near special event locations on X percent of parking spaces in Y years. Percent of parking spaces near special event locations that use flexible pricing mechanisms.
Increase traveler awareness of park-and-ride lots by X percent within Y years. Number of users aware of park-and-ride lots in their region.


 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Parking operators need to be able to collect information from Infrastructure-based detectors and/or connected vehicles in order to monitor parking lot ingress and egress, and availability in lots, garages, and other parking areas and facilities. Parking Area Management 01 The parking element shall maintain static parking lot information including hours of operation, rates, location, entrance locations, capacity, type, and constraints.
06 The parking element shall provide the capability to detect, count, and classify vehicles at entrances, exits, and designated locations within a parking facility.
Parking Management 01 The center shall monitor parking area current operational status including current parking occupancy and rates.
RSE Parking Management 01 The field element shall collect vehicle location information messages generated by connected vehicles to detect vehicles parking space and maintain and report spaces that are occupied by connected vehicles.
TIC Data Collection 05 The transportation information center shall collect, process, and store parking information, including location, availability, and fees.
02 Parking operators need to be able to determine availability of parking spaces. Parking Area Management 03 The parking element shall determine and maintain the number and availability of parking spaces.
03 Parking operators need to be able to share the collected parking information with local drivers and other centers for broader distribution. Parking Area Management 02 The parking element shall maintain dynamic parking lot information including current state of the lot, occupancy, arrival rates, and departure rates.
04 The parking element shall share information with a traffic management center to identify queues at entrances, exits that should be used, and other information that supports coordinated local traffic control in and around the parking facility.
05 The parking element shall manage local dynamic message signs that display messages to travelers such as the parking lot state, number of spaces available, location of entrances, and current charges.
Parking Coordination 03 The parking element shall distribute parking lot information to traffic management centers upon request to support integrated regional traffic control and parking management. This could include information on facility hours of operation and current parking availability.
05 The parking element shall distribute parking lot information upon request to traveler information providers to support travel planning.
Personal Interactive Traveler Information 17 The personal traveler interface shall receive traveler information including traffic and road conditions, advisories, incidents, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations.
RSE Parking Management 02 The field equipment shall provide real-time status of parking spaces to travelers.
03 The field element shall provide drivers the parking information and status, including current parking availability.
TIC Interactive Traveler Information 04 The center shall disseminate customized parking information to travelers, including location, availability, and fees upon request.
12 The center shall accept requests for parking space information from travelers.
Vehicle Basic Safety Communication 05 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
06 The vehicle shall be able to receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices.
Vehicle Interactive Traveler Information 15 The vehicle shall receive information on available parking including available spaces with associated information about parking restrictions and location for each available space.
Vehicle Roadside Information Reception 01 The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005
Smart Roadside Initiative ConOps 5/21/2012


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
Parking Area Equipment Moderate Moderate Moderate Class 2
Parking Management Center Moderate Moderate Moderate Class 2
Personal Information Device Moderate Moderate Moderate Class 2
Traffic Management Center Moderate Moderate Moderate Class 2
Transportation Information Center Moderate Moderate Moderate Class 2
Vehicle OBE Moderate Moderate Moderate Class 2



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Connected Vehicle Roadside Equipment Parking Management Center parking management application status Moderate Moderate Low
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. 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.
Connected Vehicle Roadside Equipment Vehicle OBE parking availability Not Applicable Moderate Moderate
Intended for local public use, no need to obfuscate. This data is used for trip planning for all types of vehicles. Failure to receive this information, or incorrect or fraudelent information, will negatively impact the trip for recipients of such data. This data is used for trip planning for all types of vehicles. Failure to receive this information, or incorrect or fraudelent information, will negatively impact the trip for recipients of such data.
Connected Vehicle Roadside Equipment Vehicle OBE 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.
Parking Area 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. 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.
Parking Area Equipment Driver driver parking information Low Moderate Moderate
This information is presented visually to the driver, essentially broadcast in a limited area. This information deserves some degree of confidence in its accuracy, as if it were compromised could be used to direct drivers to unsafe or inappropriate locations. Without direction information, could be LOW. Depending on the size of the parking infrastructure this might be LOW. For larger facilities, directions and locations of available spaces and exits will not be as readily observable, so this is more useful.
Parking Area Equipment Parking Management Center parking area information Moderate Moderate Low
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. 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.
Parking Area Equipment Parking Operator parking area status Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Parking Management Center Connected Vehicle Roadside Equipment parking management application info Moderate Moderate Low
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Parking Management Center Parking Area Equipment parking area management information 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.
Parking Management Center Parking Manager parking status Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Parking Management Center Traffic Management Center parking information Moderate Moderate Moderate
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise.
Parking Management Center Transportation Information Center parking information Moderate Moderate Moderate
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise.
Parking Manager Parking Management Center parking manager input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Parking Operator Parking Area Equipment parking operator input Moderate High High
Field operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Field operations flows should generally be correct and available as these are the primary interface between operators and system. Field operations flows should generally be correct and available as these are the primary interface between maintenance personnel and the system.
Personal Information Device Transportation Information Center traveler request Moderate Moderate Moderate
This is likely to include the traveler location and may include traveler identity as well. This PII could be used by an attacker to the detriment of the traveler. Request needs to be correct, or the wrong data may be sent. Interface needs to be available or users will find other sources that are reliable.
Transportation Information Center Personal Information Device interactive traveler information Moderate Moderate Low
Personalized traveler information implies location, intent and/or future location, which if compromised could enable an attacker with leverage over the traveler. Traveler information needs to be correct, as the traveler is using this to make transport-related decisions. Travelers will rely on this data for transportation-related decisions. Depending on the number of options, possible choices and impacts, this may be MODERATE.
Transportation Information Center Vehicle OBE interactive traveler information Moderate Moderate Low
Personalized traveler information implies location, intent and/or future location, which if compromised could enable an attacker with leverage over the traveler. Traveler information needs to be correct, as the traveler is using this to make transport-related decisions. Travelers will rely on this data for transportation-related decisions. Depending on the number of options, possible choices and impacts, this may be MODERATE.
Vehicle OBE Connected Vehicle Roadside Equipment vehicle location and motion for surveillance Not Applicable Moderate Moderate
This is directly observable data; DISC: WYO believes this to be MODERATE Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW
Vehicle OBE Driver driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.
Vehicle OBE Transportation Information Center traveler request Moderate Moderate Moderate
This is likely to include the traveler location and may include traveler identity as well. This PII could be used by an attacker to the detriment of the traveler. Request needs to be correct, or the wrong data may be sent. Interface needs to be available or users will find other sources that are reliable.

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
USDOT RSU Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment