Transit vehicles operated by Bowling Green State University Shuttle.
| Functional Object | Description | User Defined |
|---|
| 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 |
|---|
| Transit Vehicle On–Board Connection Protection | 'Transit Vehicle On–Board Connection Protection' monitors vehicle schedule performance and provides it to the transit center for connection protection processing. It receives operator instructions relating to managing connection protection and recognizes individual travelers who have arranged for connection protection and provides connection protection information to the transit center. | False |
|---|
| Transit Vehicle On–Board Maintenance | 'Transit Vehicle On–Board Maintenance' collects and processes transit vehicle maintenance data on–board the vehicle, including mileage and vehicle operating conditions. This maintenance information is provided to the management center and used to schedule future vehicle maintenance and repair. | False |
|---|
| Transit Vehicle On–Board Trip Monitoring | 'Transit Vehicle On–Board Trip Monitoring' tracks vehicle location, monitors fuel usage, collects operational status (doors opened/closed, running times, etc.) and sends the collected, time stamped data to the Transit Management Center. | False |
|---|
| Transit Vehicle Pedestrian Safety | 'Transit Vehicle Pedestrian Safety' exchanges current location and motion information with pedestrian–carried devices in the vicinity and uses that information to warn the driver of pedestrians in the vehicle's path. Information from on–board sensors (e.g., radars and image processing) are used to augment the short range communications, if available. In addition to notifying the driver, control information can also be provided to support automated control functions that can avoid the collision. | False |
|---|
| 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. | False |
|---|
| Transit Vehicle V2V Safety | 'Transit Vehicle V2V Safety' exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to predict vehicle paths, and notifies the driver when the potential for an impending collision is detected. Information from on–board sensors (e.g., radars and image processing) are used to augment the V2V communications, if available. In addition to notifying the driver, control information can also be provided to support automated control functions that can avoid the collision. This object is similar to the 'Vehicle Basic V2V Safety', but it accounts for crash scenarios that are unique to transit vehicles (e.g., Vehicle Turning Right in Front of Bus). It is also stop–aware since stop locations pose specific crash threats for transit vehicles. Finally, the detection and control algorithms, filters, and timing account for bus performance and risk profiles associated with remote vehicles that are unique to transit. | 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 Eco–Driving Assist | 'Vehicle Eco–Driving Assist' provides customized real–time driving advice to drivers, allowing them to adjust behaviors to save fuel and reduce emissions. This advice includes recommended driving speeds, optimal acceleration and deceleration profiles based on prevailing traffic conditions, and local interactions with nearby vehicles, i.e., processing Basic Safety Messages (BSMs) to determine position and speed of vehicles that are between the host vehicle and the intersection. When approaching and departing signalized intersections, it uses intersection geometry information, the relative position and speed of vehicles ahead of it, and signal phase movement information to provide speed advice to the driver so that the driver can adapt the vehicle's speed to pass the next traffic signal on green, decelerate to a stop in the most eco–friendly manner, or manage acceleration as the vehicle departs from a signalized intersection. It also provides feedback to drivers on their driving behavior to encourage them to drive in a more environmentally efficient manner. It may also support vehicle–assisted strategies, where the vehicle automatically implements the eco–driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco–friendly manner as the vehicle approaches a traffic signal or queue). | 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 Trip Planning and Route Guidance | 'Vehicle Trip Planning and Route Guidance' includes the in–vehicle system that coordinates with a traveler information center to provide a personalized trip plan to the driver. The trip plan is calculated by the Transportation Information Center (TIC) based on preferences and constraints supplied by the driver and provided to the driver for confirmation. Reservations and advanced payment may also be processed to confirm the trip plan. Coordination with the TIC may continue during the trip so that the route plan can be modified to account for new information. Many equipment configurations are possible including in–vehicle systems that provide a basic trip plan to the driver as well as more sophisticated systems that can provide turn by turn guidance to the driver along the route. | False |
|---|
| Document Number | Title | Description |
|---|
| ISO 21217 | Intelligent transport systems –– Communications access for land mobiles (CALM) –– Architecture | ISO 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–2 | Security Requirements for Cryptographic Modules | This 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. |
|---|