Cincinnati Fire/EMS Vehicles
Status: Existing
Description
Represents the ITS equipment, such as mobile data terminals, in the City of Cincinnati's emergency fire and EMS vehicles.
Stakeholders
Physical Objects
Functional Objects
| Functional Object | Description | User Defined |
|---|
| 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 | 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 emerge | False |
|---|
| EV Service Patrol Vehicle Operations | 'EV Service Patrol Vehicle Operations' provides on–board processing and communications to service patrol vehicles that reduce response times and improve safety of responding personnel. It supports service patrol vehicle dispatch and provides incident inf | 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 in | 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, | 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 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 | False |
|---|
Physical Standards
| 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. |
|---|
Interfaces To
(View Context Diagram)