Represents the fixed route transit vehicles operated by University of Cincinnati.
| Functional Object | Description | User Defined |
|---|
| 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 in | 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 | 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 schedul | 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. | 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. | 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 det | 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 p | 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 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 | 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) ba | 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. |
|---|