(None-Data) - WAVE WSMP
Description
This solution is used within the U.S.. It combines standards associated with (None–Data) with those for V–X: WAVE WSMP. The (None–Data) standards include an unspecified set of standards at the upper layers. 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.
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 | | Standard(s) need to be developed | One or more standards need to be developed for this subject matter before this is considered a complete solution. |
|---|
| Facilities | | Standard(s) need to be developed | One or more standards need to be developed for this subject matter before this is considered a complete solution. |
|---|
| 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). |
|---|
Readiness: Lowest
Readiness Description
Many serious issues. This category includes solutions that have not been standardized, or do not have a basic level of interoperability or security. Consider selecting a different communications solution or if this is not possible (eg. a pilot of a new application that has not been standardized), take additional measures to provide an acceptable level of security or interoperability.
Issues
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|
| Data profile not defined | Ultra | Performance, functionality, and the upper–layers of the OSI stack have not been defined for this information flow. | (None) | (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) |
|---|
| Uncertainty about trust revocation mechanism | Medium | The mechanisms used to prevent bad actors from sending authorized messages is unproven. | Bundle: IEEE 1609.2 | (All) |
|---|
Supports Interfaces
| Source | Destination | Flow |
|---|
| Des Moines Area Vehicles | Des Moines Connected Vehicle Roadside Equipment | automated vehicle control status |
|---|
| Des Moines Area Vehicles | Des Moines Connected Vehicle Roadside Equipment | vehicle platoon coordination |
|---|
| Des Moines Connected Vehicle Roadside Equipment | Des Moines Area Vehicles | automated vehicle control parameters |
|---|