Location correction - Guaranteed Secure Wireless Internet (ITS)
Description:
This solution is used within the U.S.. It combines standards associated with Location correction with those for I-M: Guaranteed Secure Wireless Internet (ITS). The Location correction standards include uppoer-layer standards that enable the distribution of position corrections data. 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.Relevant Regions:
- Canada
- United States
Comm Profile: I-M: Guaranteed Secure Wireless Internet (ITS)
Comm Class: WAN - Wide Area Network
Standards in Profile:
| Level | Standard |
|---|---|
| Access | Wireless Internet Alternatives (NA) |
| Mgmt | Bundle: SNMPv3 MIB |
| Security | Secure Session Alternatives |
| TransNet | IETF RFC 9293 TCP |
| TransNet | IP Alternatives |
Data Profile: Location correction
Standards in Profile:
| Level | Standard |
|---|---|
| ITS Application Entity | CTI 4501 CI Implementation Guide |
| ITS Application Entity | SAE J2735 DSRC Message Set |
Solution Issues Severity: 4
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
| Default | Severity | Name | Type | Description |
|---|---|---|---|---|
| False | Low | Overlap of standards (Minor) | 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. However, as this information transfer is infrastructure-based, agencies can deploy a solution throughout their jurisdiction with minimal downside and can use gateways to connect to other technologies. |
| False | Low | Time synchronization | Performance / Applicability Gap | The standard requires a highly accurate time shared between participants. |
| 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 | Uncertainty about trust revocation mechanism | Security Gap | The mechanisms used to prevent bad actors from sending authorized messages is unproven. |
| False | Medium | Unvetted by community | Standardization Gap | The proposed solution uses a suite of standards that is accepted within some communities, but has not necessarily been accepted for use within the context of this information triple. |
| 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. |
| 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 | 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. |
Solution to Triples
This solution is used on the following information flow triples:
| Source | Flow | Destination |
|---|---|---|
| Multi-Access Edge Computing | location correction | Personal |
| Multi-Access Edge Computing | location correction | Vehicle |