US: SAE Lane-Level Mapping - Secure Internet (ITS)

Description

This solution is used within the U.S.. It combines standards associated with US: SAE Lane–Level Mapping with those for I–I: Secure Internet (ITS). The US: SAE Lane–Level Mapping standards include upper–layer standards required to implement lane–level and road furniture mapping information flows. The I–I: Secure Internet (ITS) standards include lower–layer standards that support secure communications between ITS equipment using X.509 or IEEE 1609.2 security certificates.

Includes Standards

LevelDocNumFullNameDescription
MgmtIETF RFC 3411An Architecture for Describing Simple Network Management Protocol (SNMP) Management FrameworksThis standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture.
MgmtIETF RFC 3412Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)This standard (RFC) contains a MIB that assists in managing the message processing and dispatching subsystem of an SNMP entity.
MgmtIETF RFC 3413Simple Network Management Protocol (SNMP) ApplicationsThis standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys.
MgmtIETF RFC 3414User–based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)This standard (RFC) contains a MIB that assists in configuring and managing the user–based security model.
MgmtIETF RFC 3415View–based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)This standard (RFC) contains a MIB that supports the configuration and management of the View–based access control model of SNMP.
MgmtIETF RFC 3416Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)This standard (RFC) defines the message structure and protocol operations used by SNMPv3.
MgmtIETF RFC 3418Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)This standard (RFC) defines the MIB to configure and manage an SNMP entity.
MgmtIETF RFC 4293Management Information Base for the Internet Protocol (IP)This standard (RFC) defines the MIB that manages an IP entity.
SecurityIETF RFC 5280Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileThis standard (RFC) defines how to use X.509 certificates for secure communications over the Internet.
SecurityIETF RFC 8446The Transport Layer Security (TLS) ProtocolThis standard (RFC) specifies Version 1.3 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.
ITS Application EntitySAE J2945/AStandard for Lane–Level and Road Furniture Mapping for Infrastructure–based V2X ApplicationsThe document provides a generalized mapping solution that can be applied to future infrastructure–based application standards using a layering approach, so that each new application standard at most needs to define a new layer of information that is unique to specific V2X application. It provides an ability to describe small, lane–level map descriptions that apply directly to V2X applications such as reduced speed zones (e.g. work zones) and curves (e.g. curve speed warning).
ITS Application EntitySAE J2735Dedicated Short Range Communications (DSRC) Message Set Dictionary (TM)This standard defines the data and messages for use in DSRC (i.e., V2V, V2I, and V2D) applications. The SAE J2945 series defines additional requirements on how to use these messages.
FacilitiesSAE J2945Dedicated Short Range Communication (DSRC) Systems Engineering Process Guidance for J2945/x Documents and Common Design ConceptsThis standard defines cross–cutting material which applies to the J2945/x series including generic DSRC interface requirements and guidance on Systems Engineering (SE) content.
FacilitiesSAE J2945/AStandard for Lane–Level and Road Furniture Mapping for Infrastructure–based V2X ApplicationsThe document provides a generalized mapping solution that can be applied to future infrastructure–based application standards using a layering approach, so that each new application standard at most needs to define a new layer of information that is unique to specific V2X application. It provides an ability to describe small, lane–level map descriptions that apply directly to V2X applications such as reduced speed zones (e.g. work zones) and curves (e.g. curve speed warning).
TransNetIETF RFC 2460Internet Protocol, Version 6 (IPv6) SpecificationThis standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng.
TransNetIETF RFC 4291IP Version 6 Addressing ArchitectureThis standard (RFC) defines the addressing architecture of the IP Version 6 (IPv6) protocol. It includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.
TransNetIETF RFC 4443Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationThis standard (RFC) defines the control messages to manage IPv6.
TransNetIETF RFC 793Transmission Control ProtocolThis standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks.
Access Internet Subnet AlternativesA set of alternative standards that includes any Subnet Layer method of connecting to the Internet.

Readiness: High–Moderate

Readiness Description

One significant or possibly a couple minor issues. For existing deployments, the chosen solution likely has identified security or management issues not addressed by the communications solution. Deployers should consider additional security measures, such as communications link and physical security as part of these solutions. They should also review the management issues to see if they are relevant to their deployment and would require mitigation. For new deployments, the deployment efforts should consider a path to addressing these issues as a part of their design activities. The solution does not by itself provide a fully secure implementation without additional work.

Issues

IssueSeverityDescriptionAssociated StandardAssociated Triple
Still under developmentMediumA draft of the standard has been developed by the working group, but it was still under development at the time this analysis was performed.SAE J2945/A Lane–Level & Road Furniture Mapping(All)
Data not defined in standard formatLowThe definition of data concepts should conform to ISO 14817–1 to promote reuse among ITS.SAE J2735 DSRC Message Set(All)

Supports Interfaces

SourceDestinationFlow
Private Companies Map Update SystemsAkron–Canton Airport Connected Vehicle Roadside Equipmentroadway geometry
Private Companies Map Update SystemsCounty and City Connected Vehicles Roadside Equipmentroadway geometry
Private Companies Map Update SystemsODOT Connected Vehicles Roadside Equipmentroadway geometry
Private Companies Map Update SystemsOTIC Connected Vehicles Roadside Equipmentroadway geometry