US: SAE J3067 (J2735 SE) - Guaranteed Secure Wireless Internet (ITS)
Description
This solution is used within the U.S.. It combines standards associated with US: SAE J3067 (J2735 SE) with those for I–M: Guaranteed Secure Wireless Internet (ITS). The US: SAE J3067 (J2735 SE) standards include a proposed solution for the upper–layers to implement V2X information flows that do not yet have fully standardized messages, functionality or performance characteristics. The I–M: Guaranteed Secure Wireless Internet (ITS) standards include lower–layer standards that support secure communications with guaranteed delivery 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 | SAE J3067 | Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary [SAE J2735] Using Systems Engineering Methods | This informational report formalized a deliverable received from the USDOT as suggested improvements to SAE J2735:2009. Many of these suggestions have been incorporated into later revisions of SAE J2735 and SAE J2945/x; additional suggestions may be incorporated as the documents are extended to address additional applications. |
|---|
| Facilities | SAE J2945 | Dedicated Short Range Communication (DSRC) Systems Engineering Process Guidance for J2945/x Documents and Common Design Concepts | This standard defines cross–cutting material which applies to the J2945/x series including generic DSRC interface requirements and guidance on Systems Engineering (SE) content. |
|---|
| TransNet | IETF RFC 793 | Transmission Control Protocol | This standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks. |
|---|
Readiness: Moderate
Readiness Description
Two significant or one significant and several minor issues. For existing deployments, the chosen solution is likely deficient in security or management capabilities and the issues should be reviewed and upgrades developed as needed. For new deployments, the solution may be viable for pilots when applied to the triples it supports; such pilot deployments should consider a path to addressing these issues as a part of their design activities. The solution does not provide sufficient interoperability, management, and security to enable proper, full–scale deployment without additional work.
Issues
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | Fleet and Freight Management Systems=>hazmat information=>Commercial Vehicles and Barges |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | Riverfront Terminals and Operations Centers=>hazmat information=>Commercial Vehicles and Barges |
|---|
| Not a standard (severe) | High | Although the document is publicly available, it has not been the subject of a rigorous industry review and is only provided as informal guidance. It is expected that details will change significantly prior to adoption as a standard. | SAE J3067 DSRC Prop Mods to 2735 | (All) |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Commercial Vehicles and Barges=>hazmat notification=>Fleet and Freight Management Systems |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Commercial Vehicles and Barges=>hazmat notification=>Riverfront Terminals and Operations Centers |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Commercial Vehicles and Barges=>hazmat notification=>Regional Public Safety Dispatch Centers |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Commercial Vehicles and Barges=>hazmat notification=>Regional 911 Call Centers |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Commercial Vehicles and Barges=>hazmat notification=>Regional Operations Center |
|---|
| 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 |
|---|
| Commercial Vehicles and Barges | Fleet and Freight Management Systems | hazmat notification |
|---|
| Commercial Vehicles and Barges | Regional 911 Call Centers | hazmat notification |
|---|
| Commercial Vehicles and Barges | Regional Operations Center | hazmat notification |
|---|
| Commercial Vehicles and Barges | Regional Public Safety Dispatch Centers | hazmat notification |
|---|
| Commercial Vehicles and Barges | Riverfront Terminals and Operations Centers | hazmat notification |
|---|
| Fleet and Freight Management Systems | Commercial Vehicles and Barges | hazmat information |
|---|
| Riverfront Terminals and Operations Centers | Commercial Vehicles and Barges | hazmat information |
|---|