US: SAE Signal Control Messages - Local Unicast Wireless (1609.2)
Description:
This solution is used within the U.S.. It combines standards associated with US: SAE Signal Control Messages with those for V-X: Local Unicast Wireless (1609.2). The US: SAE Signal Control Messages standards include upper-layer standards required to implement signal control information flows. 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.Relevant Regions:
- United States
Comm Profile: V-X: Local Unicast Wireless (1609.2)
Comm Class: LAN - Local Area Network
Standards in Profile:
Level | Standard |
---|---|
Access | Bundle: Local Unicast Wireless SubNet (US) |
Security | Bundle: IEEE 1609.2 |
TransNet | IEEE 1609.3 WAVE - Networking Services |
Data Profile: US: SAE Signal Control Messages
Standards in Profile:
Level | Standard |
---|---|
Facilities | SAE J2735 DSRC Message Set |
Facilities | SAE J2945/0 DSRC Common Design Elements |
ITS Application Entity | CTI 4501 CI Implementation Guide |
ITS Application Entity | ISO 19091 V2I for signalized intersections |
ITS Application Entity | SAE J2735 DSRC Message Set |
ITS Application Entity | SAE J2945/B Signal Intersection Applications |
Solution Issues Severity: 9
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
Default | Severity | Name | Type | Description |
---|---|---|---|---|
True | Low | Data not defined in standard format | ITS Info Gap | The definition of data concepts should conform to ISO 14817-1 to promote reuse among ITS. |
True | Low | Guidance document under development | Standardization Gap | This recommended practice on how to use the related standards is still under development but is not seen as strictly necessary to begin deployment of equipment. |
True | Low | Not a standard (minor) | Standardization Gap | The document is publicly available and widely used but it is not currently a formal standard. |
True | Medium | Not a standard | Standardization Gap | The document may be publicly available but it is not currently available as a formal standard and details may change prior to adoption as a standard. |
True | Medium | Uncertainty about trust revocation mechanism | Security Gap | The mechanisms used to prevent bad actors from sending authorized messages is unproven. |
False | Low | Relatively new technology | Standardization Gap | The standard is finalized but has not been widely deployed. Deployment experience may result in further revisions in the technology, although it is expected that the standards group will make reasonable efforts to make any changes backwards compatible. |
False | Medium | Overlap of standards | Overlap | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. |
False | Medium | Regulatory Permission Needed | Standardization Gap | Deployment of this standard requires regulatory approval, which is currently subject to significant delays. |
False | High | Regulatory Issue | Standardization Gap | Deployment of this standard is subject to regulatory approval, which is not currently expected to be granted for deployments in the near-term. |
Solution to Triples
This solution is used on the following information flow triples: