US: SAE J3067 (J2735 SE) - Local Unicast Wireless (1609.2)
Description
This solution is used within the U.S.. It combines standards associated with US: SAE J3067 (J2735 SE) with those for V–X: Local Unicast Wireless (1609.2). 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 V–X: Local Unicast Wireless (1609.2) standards include lower–layer standards that support local–area unicast wireless solutions applicable to North America, such as WAVE DSRC, LTE–V2X, LTE, Wi–Fi, etc.
Includes Standards
| Level | DocNum | FullName | Description |
|---|
| Mgmt | Addressed Elsewhere | Addressed Elsewhere in Stack | The services related to this portion of the stack are defined in the other standards listed for this solution. |
|---|
| Security | IEEE 1609.2 | IEEE Standard for Wireless Access in Vehicular Environments – Security Services for Applications and Management Messages | This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions. |
|---|
| Security | IEEE 1609.2a | IEEE 1609.2a–2017 – IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 1 | This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions. |
|---|
| Security | IEEE 1609.2b | IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 2––PDU Functional Types and Encryption Key Management | This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions. |
|---|
| 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 | IEEE 1609.3 | IEEE Standard for Wireless Access in Vehicular Environments (WAVE) – Networking Services | This standard defines the network and transport layer options for the WAVE environment. The standard defines three options: a bandwidth efficient single–hop solution known as WSMP, UDP/IP, and TCP/IP. It has been harmonized with ISO FNTP and FSAP – a common message format specified in ISO 16460. |
|---|
| Access | IEEE 802.11 | IEEE Draft Standard for Information technology––Telecommunications and information exchange between systems Local and metropolitan area networks––Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specificatio | This standard defines the physical and data link layers for wireless Ethernet, including WiFi and DSRC. |
|---|
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 |
|---|
| 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) |
|---|
| Uncertainty about trust revocation mechanism | Medium | The mechanisms used to prevent bad actors from sending authorized messages is unproven. | Bundle: IEEE 1609.2 | (All) |
|---|
| Data may not be fully defined (low) | Low | The information flow is unclear as to what precisely is needed; the standard may not fully support the needs of the information flow, depending on how it is interpreted. | (None) | ND Commercial Vehicles=>safety inspection record=>ND CVO Devices |
|---|
| Data may not be fully defined (low) | Low | The information flow is unclear as to what precisely is needed; the standard may not fully support the needs of the information flow, depending on how it is interpreted. | (None) | ND Commercial Vehicles=>safety inspection record=>NDDOT WIM |
|---|
| Data may not be fully defined (low) | Low | The information flow is unclear as to what precisely is needed; the standard may not fully support the needs of the information flow, depending on how it is interpreted. | (None) | ND CVO Devices=>safety inspection record=>ND Commercial Vehicles |
|---|
| Data may not be fully defined (low) | Low | The information flow is unclear as to what precisely is needed; the standard may not fully support the needs of the information flow, depending on how it is interpreted. | (None) | NDDOT WIM=>safety inspection record=>ND Commercial Vehicles |
|---|
Supports Interfaces
| Source | Destination | Flow |
|---|
| ND Commercial Vehicles | ND CVO Devices | on–board safety data |
|---|
| ND Commercial Vehicles | ND CVO Devices | safety inspection record |
|---|
| ND Commercial Vehicles | ND CVO Devices | screening event record |
|---|
| ND Commercial Vehicles | NDDOT WIM | safety inspection record |
|---|
| ND Commercial Vehicles | NDDOT WIM | screening event record |
|---|
| ND CVO Devices | ND Commercial Vehicles | electronic screening request |
|---|
| ND CVO Devices | ND Commercial Vehicles | safety inspection record |
|---|
| ND CVO Devices | ND Commercial Vehicles | safety inspection request |
|---|
| ND CVO Devices | ND Commercial Vehicles | screening event record |
|---|
| NDDOT WIM | ND Commercial Vehicles | electronic screening request |
|---|
| NDDOT WIM | ND Commercial Vehicles | safety inspection record |
|---|
| NDDOT WIM | ND Commercial Vehicles | safety inspection request |
|---|
| NDDOT WIM | ND Commercial Vehicles | screening event record |
|---|