This solution is used within the U.S.. It combines standards associated with US: SAE J3067 (J2735 SE) with those for V–X: WAVE WSMP. 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: WAVE WSMP standards include lower–layer standards that support connectionless, near constant, ultra–low latency vehicle–to–any communications within ~300m using the WAVE Short Messaging Protocol (WSMP) over IEEE WAVE in the 5.9GHz spectrum. The broadcast mode is interoperable with M5 FNTP.
| 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 1609.4 | IEEE Draft Standard for Wireless Access in Vehicular Environments – Multi–Channel Operation | This standard primarily defines the data link layer of the WAVE communications stack. |
|---|
| 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. |
|---|
| Access | ISO/IEC 8802–2 | IEEE Standard for Information technology –– Telecommunications and information exchange between systems––Local and metropolitan area networks –– Specific requirements –– Part 2: Logical Link Control | ISO/IEC 8802–2 describes the logical link control (LLC) sublayer, which constitutes the top sublayer in the data link layer of the ISO 8802 Local Area Network Protocol (also known as IEEE 802.2). |
|---|
Multiple significant and 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. Some solutions in this category may also be becoming obsolete from an interoperability perspective and if this is the case, then upgrades should be planned as soon as possible. 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.
| 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) | ODOT Connected Vehicles Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | OTIC Connected Vehicles Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | Akron–Canton Airport Connected Vehicle Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | Akron–Canton Airport Connected Vehicle Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | County and City Connected Vehicles Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | ODOT Connected Vehicles Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | OTIC Connected Vehicles Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Application specification not defined | High | The logic, performance, and application security rules are not defined for this information flow. | (None) | County and City Connected Vehicles Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| 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) |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | Bundle: WAVE – Subnet | (All) |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | County and City Connected Vehicles Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | Akron–Canton Airport Connected Vehicle Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | County and City Connected Vehicles Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | OTIC Connected Vehicles Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | ODOT Connected Vehicles Roadside Equipment=>parking availability=>Connected/Automated Vehicles |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | ODOT Connected Vehicles Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | OTIC Connected Vehicles Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | Akron–Canton Airport Connected Vehicle Roadside Equipment=>parking availability=>Commercial Vehicles |
|---|
| 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) | City of Kent Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | Commercial Vehicles=>vehicle profile=>OTIC Connected Vehicles Roadside Equipment |
|---|
| 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) | City of Akron Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | City of Cuyahoga Falls Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | City of Green Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | City of Stow Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | OSHP Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | OTIC Public Service Vehicles=>vehicle profile=>OTIC Connected Vehicles Roadside Equipment |
|---|
| 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) | Other Municipalities Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | Summit County Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | City of Hudson Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | City of Twinsburg Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | City of Barberton Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | University of Akron Roo Express Shuttle Service Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | Connected/Automated Vehicles=>vehicle profile=>OTIC Connected Vehicles Roadside Equipment |
|---|
| 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) | Connected/Automated Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| 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) | Connected/Automated Vehicles=>vehicle profile=>County and City Connected Vehicles Roadside Equipment |
|---|
| 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) | Portage County Emergency Vehicles=>vehicle profile=>ODOT Connected Vehicles Roadside Equipment |
|---|
| Source | Destination | Flow |
|---|
| Akron–Canton Airport Connected Vehicle Roadside Equipment | Commercial Vehicles | parking availability |
|---|
| Akron–Canton Airport Connected Vehicle Roadside Equipment | Connected/Automated Vehicles | parking availability |
|---|
| City of Akron Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| City of Barberton Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| City of Cuyahoga Falls Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| City of Green Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| City of Hudson Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| City of Kent Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| City of Stow Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| City of Twinsburg Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| Commercial Vehicles | Connected/Automated Vehicles | vehicle profile |
|---|
| Commercial Vehicles | OTIC Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| Connected/Automated Vehicles | Commercial Vehicles | vehicle profile |
|---|
| Connected/Automated Vehicles | County and City Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| Connected/Automated Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| Connected/Automated Vehicles | OTIC Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| County and City Connected Vehicles Roadside Equipment | Commercial Vehicles | parking availability |
|---|
| County and City Connected Vehicles Roadside Equipment | Connected/Automated Vehicles | parking availability |
|---|
| ODOT Connected Vehicles Roadside Equipment | Commercial Vehicles | parking availability |
|---|
| ODOT Connected Vehicles Roadside Equipment | Connected/Automated Vehicles | parking availability |
|---|
| OSHP Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| Other Municipalities Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| OTIC Connected Vehicles Roadside Equipment | Commercial Vehicles | parking availability |
|---|
| OTIC Connected Vehicles Roadside Equipment | Connected/Automated Vehicles | parking availability |
|---|
| OTIC Public Service Vehicles | OTIC Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| Portage County Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| Summit County Emergency Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|
| University of Akron Roo Express Shuttle Service Vehicles | ODOT Connected Vehicles Roadside Equipment | vehicle profile |
|---|