US: SAE J3067 (J2735 SE) - Secure Wireless Internet (ITS)

Description

This solution is used within the U.S.. It combines standards associated with US: SAE J3067 (J2735 SE) with those for I–M: Secure Wireless Internet (ITS). 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 I–M: Secure Wireless Internet (ITS) standards include lower–layer standards that support secure communications 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.

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 J3067Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary [SAE J2735] Using Systems Engineering MethodsThis 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.
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.
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.
Access3GPP Network3GPP Cellular Communications NetworkThis proxy standard represents a variety of 3GPP releases and underlying standards and technologies that rely upon cellular base stations for connectivity, including 3G, 4G, and the emerging 5G technologies.

Readiness: Moderate

Readiness Description

Two significant or one significant and several 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. 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.

Issues

IssueSeverityDescriptionAssociated StandardAssociated Triple
Application specification not definedHighThe logic, performance, and application security rules are not defined for this information flow.(None)ODOT OHGO Traveler Information System=>parking availability=>Commercial Vehicles
Application specification not definedHighThe logic, performance, and application security rules are not defined for this information flow.(None)ODOT OHGO Traveler Information System=>parking availability=>Personal Information Device
Not a standard (severe)HighAlthough 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)
Secure data access not providedMediumThe solution does not define rules on how the application entity authenticates requests to accept or provide data.(None)(All)
Data may not be fully defined (low)LowThe 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)PUCO Commercial Vehicle Registration System=>safety inspection record=>Commercial Vehicles
Data may not be fully defined (low)LowThe 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)Fleet and Freight Management Systems=>safety inspection record=>Commercial Vehicles

Supports Interfaces

SourceDestinationFlow
Commercial VehiclesFleet and Freight Management Systemsdriver log
Commercial VehiclesFleet and Freight Management Systemson–board safety data
Commercial VehiclesPUCO Commercial Vehicle Registration Systemdriver log
Commercial VehiclesPUCO Commercial Vehicle Registration Systemon–board safety data
Fleet and Freight Management SystemsCommercial Vehiclesdriver log
Fleet and Freight Management SystemsCommercial Vehiclessafety inspection record
ODOT OHGO Traveler Information SystemCommercial Vehiclesparking availability
ODOT OHGO Traveler Information SystemPersonal Information Deviceparking availability
PUCO Commercial Vehicle Registration SystemCommercial Vehiclessafety inspection record