OTIC Public Service Vehicles

Status: Existing

Description

Public service vehicles owned by the OTIC. Some of these vehicles are equipped with connected vehicle technology.

Stakeholders

StakeholderRoleRole Status
Ohio Turnpike and Infrastructure Commission (OTIC)OwnsExisting

Physical Objects

Vehicle OBE
Emergency Vehicle OBE
Basic Emergency Vehicle

Functional Objects

Functional ObjectDescriptionUser Defined
EV Barrier System Control'EV Barrier System Control' provides local control of automatic or remotely controlled gates and other barrier systems from an emergency vehicle. Using this capability, emergency personnel can open and close barriers without leaving the vehicle, using V2I Communications to control the barriers.False
EV On–Board En Route Support'EV On–Board En Route Support' provides communications functions to responding emergency vehicles that reduce response times and improve safety of responding public safety personnel and the general public. It supports traffic signal preemption via short range communication directly with signal control equipment and sends alert messages to surrounding vehicles.False
EV On–Board Incident Management Communication'EV On–board Incident Management Communication' provides communications support to first responders. Information about the incident, information on dispatched resources, and ancillary information such as road and weather conditions are provided to emergency personnel. Emergency personnel transmit information about the incident such as identification of vehicles and people involved, the extent of injuries, hazardous material, resources on site, site management strategies in effect, and current clearance status. Emergency personnel may also send in–vehicle signing messages to approaching traffic using short range communications.False
ITS Communications Support'ITS Communications Support' provides means to send and receive messages to and from other ITS Objects. It provides mechanisms for scheduling and prioritizing communications traffic. It may also provide relay functions.False
ITS Management Support'ITS Management Support' provides management of the ITS Object. This includes management of regulatory information and policies, management of application processes, management of communication system configuration and update management, communications interfaces, protocol–specific techniques to ensure interoperability such as service advertisements, communications congestion management and interference management, local device states and communications information, billing management, fault management, service level and performance monitoring.False
ITS Security Support'ITS Security Support' provides communications and system security functions to the ITS Object, including privacy protection functions. It may include firewall, intrusion management, authentication, authorization, profile management, identity management, cryptographic key management. It may include a hardware security module and security management information base.False
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.False
Vehicle Control Automation'Vehicle Control Automation' provides lateral and/or longitudinal control of a vehicle to allow 'hands off' and/or 'feet off' driving, automating the steering, accelerator, and brake control functions. It builds on the sensors included in 'Vehicle Safety Monitoring' and 'Vehicle Control Warning' and uses the information about the area surrounding the vehicle to safely control the vehicle. It covers the range of incremental control capabilities from driver assistance systems that take over steering or acceleration/deceleration in limited scenarios with direct monitoring by the driver to full automation where all aspects of driving are automated under all roadway and environmental conditions.False
Vehicle Control Warning'Vehicle Control Warning' monitors areas around the vehicle and provides warnings to a driver so the driver can take action to recover and maintain safe control of the vehicle. It includes lateral warning systems that warn of lane departures and obstacles or vehicles to the sides of the vehicle and longitudinal warning systems that monitor areas in the vehicle path and provide warnings when headways are insufficient or obstacles are detected in front of or behind the vehicle. It includes on–board sensors, including radars and imaging systems, and the driver information system that provides the visual, audible, and/or haptic warnings to the driver.False
Vehicle Data Subscription Management'Vehicle Data Subscription Management' manages data subscriptions for an end user. It provides access to a catalog of available data, manages the necessary user information and rules that govern the data subscriptions, supports communications with data providers to collect data per the subscription rules, and makes the data available to the end user. It provides the local user interface through which a user can specify and manage subscriptions. It supports different mechanisms for collecting data for the end–user including one–time query–response as well as publish–subscribe services.False
Vehicle Location Determination'Vehicle Location Determination' receives current location of the vehicle and provides this information to vehicle applications that use the location information to provide ITS services.False
Vehicle Map Management'Vehicle Map Management' supports map updates and makes current map and geometry data available to other applications. It manages map data on–board and provides map data to end–user applications that provide location–based services.False
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.False
Vehicle Secure Area Access System'Vehicle Secure Area Access System' provides access to secure areas such as shipping yards, warehouses, airports, transit–only ramps, parking gates and other areas. It accepts inputs from the vehicle driver that include the necessary identity information and uses this information to generate the request to activate a barrier to gain access to the area.False
Vehicle Situation Data Monitoring'Vehicle Situation Data Monitoring' is the highest–level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this functional object supports collection of data for areas remote from RSEs or other communications infrastructure.False
Vehicle Speed Management Assist'Vehicle Speed Management Assist' assists the driver in operating the vehicle within the current speed limit. It monitors current vehicle speed and communicates with the infrastructure to receive current speed limits and associated road configuration change notifications. Driver warnings are issued when unsafe or excessive speeds are detected based on the provided speed limits and current conditions.False
Vehicle System Executive'Vehicle System Executive' provides the operating system kernel and executive functions that manage the software configuration and operation and support computer resource management, security, and software installation and upgrade.False
Vehicle System Monitoring and Diagnostics'Vehicle System Monitoring and Diagnostics' includes on–board sensors and integrated self test software that monitors the condition of each of the vehicle systems and diagnostics that can be used to support vehicle maintenance. The status of the vehicle and ancillary equipment and diagnostic information is provided to the driver and service center.False

Physical Standards

Document NumberTitleDescription
ISO 21217Intelligent transport systems –– Communications access for land mobiles (CALM) –– ArchitectureISO 21217 describes the communications reference architecture of nodes called "ITS station units" designed for deployment in ITS communication networks. While it describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. It also describes the various communication modes for peer–to–peer communications over various networks between ITS communication nodes. These nodes may be ITS station units as described in the document or any other reachable nodes. ISO 21217 specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain.
NIST FIPS PUB 140–2Security Requirements for Cryptographic ModulesThis Federal Information Processing Standard (140–2) specifies the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self–tests; design assurance; and mitigation of other attacks.

Interfaces To

(View Context Diagram)

Commercial Vehicles
Connected/Automated Vehicles
Drivers
Ohio Certification System
Ohio Cooperative ITS Credentials Management System
Ohio Object Registration and Discovery System
OTIC Central Dispatch
OTIC Connected Vehicles Roadside Equipment
OTIC CV Service Monitoring System
OTIC Equipment and Fleet Service Facilities
OTIC Maintenance and Construction Vehicles
OTIC Website
Private Companies Map Update Systems