VIS - Secure Wireless Internet (ITS)
Description
This solution is used within Canada and the U.S.. It combines standards associated with VIS with those for I–M: Secure Wireless Internet (ITS). The VIS standards include upper–layer standards required to exchange vehicle diagnostic and detailed information. The I–M: Secure Wireless Internet (ITS) standards include lower–layer standards that support secure communications between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 or IEEE 1609.2 certificates. A non–mobile (if any) endpoint may connect to the service provider using any Internet connection method.
Includes Standards
| Level | DocNum | FullName | Description |
|---|
| ITS Application Entity | VSS | Vehicle Signal Specification | This specification provides a vendor–independent domain taxonomy for vehicle signals. It can be used as standard in automotive applications to communicate semantically well–defined information around the vehicle. |
|---|
| Facilities | IETF RFC 6455 | The WebSocket Protocol | The WebSocket Protocol enables two–way communication between a client running untrusted code in a controlled environment to a remote host that has opted–in to communications from that code. The security model used for this is the origin–based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser–based applications that need two–way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling). |
|---|
| Facilities | VISS | Vehicle Information Service Specification | This specification defines a WebSocket based API for a Vehicle Information Service (VIS) to enable client applications to get, set, subscribe and unsubscribe to vehicle signals and data attributes. |
|---|
Readiness: High–Moderate
Readiness Description
One significant or possibly a couple minor issues. For existing deployments, the chosen solution likely has identified security or management issues not addressed by the communications solution. Deployers should consider additional security measures, such as communications link and physical security as part of these solutions. They should also review the management issues to see if they are relevant to their deployment and would require mitigation. For new deployments, the deployment efforts should consider a path to addressing these issues as a part of their design activities. The solution does not by itself provide a fully secure implementation without additional work.
Issues
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | (All) |
|---|
| Secure data access not provided | Medium | The solution does not define rules on how the application entity authenticates requests to accept or provide data. | (None) | (All) |
|---|
Supports Interfaces
| Source | Destination | Flow |
|---|
| BCRTA Transit Vehicles | BCRTA Equipment and Fleet Service Facilities | vehicle diagnostic data |
|---|
| Cincinnati Fire/EMS Vehicles | Cincinnati Maintenance Garage | vehicle diagnostic data |
|---|
| Cincinnati Maintenance Vehicles | Cincinnati Maintenance Garage | vehicle diagnostic data |
|---|
| Cincinnati Streetcar Rail Vehicles | Cincinnati Maintenance Garage | vehicle diagnostic data |
|---|
| City and County Fire/EMS Vehicles | Municipal/County Equipment Repair Facility | vehicle diagnostic data |
|---|
| City and County Police/Sheriffs Vehicles | Municipal/County Equipment Repair Facility | vehicle diagnostic data |
|---|
| Hamilton County Fire/EMS Vehicles | Municipal/County Equipment Repair Facility | vehicle diagnostic data |
|---|
| Hamilton County Maintenance Vehicle | Municipal/County Equipment Repair Facility | vehicle diagnostic data |
|---|
| Hamilton County Sheriffs Vehicles | Municipal/County Equipment Repair Facility | vehicle diagnostic data |
|---|
| Hoosier Helper Safety Service Patrol | INDOT Seymour District Maintenance Garages | vehicle diagnostic data |
|---|
| INDOT Maintenance Vehicles | INDOT Seymour District Maintenance Garages | vehicle diagnostic data |
|---|
| KYTC District 6 Maintenance Vehicles | KYTC District 6 Maintenance Garages | vehicle diagnostic data |
|---|
| Local Transit Vehicles | Local Transit Equipment and Fleet Service Facilities | vehicle diagnostic data |
|---|
| ODOT Freeway Safety Patrol | ODOT District 8 Maintenance Garages | vehicle diagnostic data |
|---|
| ODOT Maintenance Vehicles | ODOT District 8 Maintenance Garages | vehicle diagnostic data |
|---|
| Other City and County Maintenance Vehicles | Municipal/County Equipment Repair Facility | vehicle diagnostic data |
|---|
| Other Public Safety Vehicles | Municipal/County Equipment Repair Facility | vehicle diagnostic data |
|---|
| RAMP Transit Vehicles | TANK Equipment and Fleet Service Facilities | vehicle diagnostic data |
|---|
| SORTA ACCESS Vehicles | SORTA Equipment and Fleet Service Facilities | vehicle diagnostic data |
|---|
| SORTA Fixed Route Vehicles | SORTA Equipment and Fleet Service Facilities | vehicle diagnostic data |
|---|
| TANK Transit Vehicles | TANK Equipment and Fleet Service Facilities | vehicle diagnostic data |
|---|
| TRIMARC Freeway Service Patrol (KYTC) | KYTC District 6 Maintenance Garages | vehicle diagnostic data |
|---|