Search Results

This Abstract Syntax Notation (ASN.1) file precisely specifies the structure of the data used to support implementation of SAE International Standard J2945/3. As part of an international treaty, data defined in US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the data entities or "ASN specifications". Using the ASN.1 specification, a compiler tool can be used used to produce encodings as required by the encoding rules identified in the standard (SAE J2945/3 messages are encoded with UPER or JER encoding). Both this file and the SAE J2735 ASN.1 files are necessary to collectively implement the data exchanges described in the J2945/3. The combined library can be used by any application (along with the additional logic of that application) to exchange the data over interfaces conformant to J2945/3.

This Abstract Syntax Notation (ASN.1) file precisely specifies the structure of the data used to support implementation of SAE International Standard J2945/3. As part of an international treaty, data defined in US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the data entities or "ASN specifications". Using the ASN.1 specification, a compiler tool can be used used to produce encodings as required by the encoding rules identified in the standard (SAE J2945/3 messages are encoded with UPER or JER encoding). Both this file and the SAE J2735 ASN.1 files are necessary to collectively implement the data exchanges described in the J2945/3. The combined library can be used by any application (along with the additional logic of that application) to exchange the data over interfaces conformant to J2945/3.

This Abstract Syntax Notation (ASN.1) file precisely specifies the structure of the data used to support implementation of SAE International Standard J2945/3. As part of an international treaty, data defined in US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the data entities or "ASN specifications". Using the ASN.1 specification, a compiler tool can be used used to produce encodings as required by the encoding rules identified in the standard (SAE J2945/3 messages are encoded with UPER or JER encoding). Both this file and the SAE J2735 ASN.1 files are necessary to collectively implement the data exchanges described in the J2945/3. The combined library can be used by any application (along with the additional logic of that application) to exchange the data over interfaces conformant to J2945/3.

This Abstract Syntax Notation (ASN.1) file precisely specifies the structure of the data used to support implementation of SAE International Standard J2945/3. As part of an international treaty, data defined in US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the data entities or "ASN specifications". Using the ASN.1 specification, a compiler tool can be used used to produce encodings as required by the encoding rules identified in the standard (SAE J2945/3 messages are encoded with UPER or JER encoding). Both this file and the SAE J2735 ASN.1 files are necessary to collectively implement the data exchanges described in the J2945/3. The combined library can be used by any application (along with the additional logic of that application) to exchange the data over interfaces conformant to J2945/3.

Connected vehicles can provide data from multiple sensors that monitor both the vehicle and the environment through which the vehicle is passing. The data, when shared, can be used to enhance and optimize transportation operations and management—specifically, traffic flow and infrastructure maintenance. This document describes an interface between vehicle and infrastructure for collecting vehicle/probe data. That data may represent a single point in time or may be accumulated over defined periods of time or distance, or may be triggered based on circumstance. The purpose of this document is to define an interoperable means of collecting the vehicle/probe data in support of the use cases defined herein. There are many additional use cases that may be realized based on the interface defined in this document. Note that vehicle diagnostics are not included within the scope of this document, but diagnostics-related features may be added to probe data in a future supplemental document.