Refine Your Search

Search Results

Viewing 1 to 9 of 9
Standard

Requirements for Road Weather Applications

2021-08-10
WIP
J2945/3

Inclement weather can have a significant impact on surface transportation systems. It can result in hazardous conditions for travelers due to poor visibility, or wet or icy roadways. Weather applications have the potential to provide additional data to surface transportation infrastructure owners and operators, allowing them to better assess the impacts of the weather environment on or around the roadway and to better manage the surface transportation system. Such weather applications can:

  • Collect road weather data from connected vehicles and mobile devices, increasing the number of data sources available.
  • Provide road weather related traveler information to travelers via connected vehicles and devices, such as when and where a hazardous condition exists.
  • Provide the ability to manage road weather response on specific roadways.
Standard

Infrastructure Applications Testing for Interoperability

2020-09-17
WIP
J3238
Interoperability is a key metric for success of ITS standards. To achieve interoperability, testing of V2X infrastructure applications requires a common methodology for verification and validation of these applications. The Infrastructure Applications Technical Committee (IATC) has recommended that certification of applications be performed based on specifications vetted through a consensus-based process. This project will develop a recommended practice test methodology for the different type of interface configurations supported by various IATC application specifications. Those 3 interface configurations are: * broadcast interface (SAE messages broadcast using WSMP), * localized data exchange interface (SAE data exchanges using WSMP or IP), and * cloud based data exchange interface (SAE data exchanges using IP).
Standard

Requirements for Road Weather Applications™ ASN File

2020-04-23
CURRENT
J2945/3ASN_202004
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.
Standard

Requirements for Road Weather Applications™ Set

2020-04-23
CURRENT
J2945/3SET_202004
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.
Standard

Requirements for Road Weather Applications

2020-03-24
CURRENT
J2945/3_202003
Inclement weather can have a significant impact on surface transportation systems. It can result in hazardous conditions for travelers due to poor visibility, or wet or icy roadways. Weather applications have the potential to provide additional data to surface transportation infrastructure owners and operators, allowing them to better assess the impacts of the weather environment on or around the roadway and to better manage the surface transportation system. Such weather applications can: Collect road weather data from connected vehicles and mobile devices, increasing the number of data sources available. Provide road weather related traveler information to travelers via connected vehicles and devices, such as when and where a hazardous condition exists. Provide the ability to manage road weather response on specific roadways.
Standard

Standard for Lane-Level and Road Furniture Mapping for Infrastructure-based V2X Applications

2019-08-21
WIP
J2945/A
V2X applications related to vehicles and/or infrastructure enhance safety, mobility, and the environment. These applications utilize mapping, positioning, and communication technology for their operations. V2X stakeholders have identified a wide range of potential infrastructure-based applications that have different needs for map, location-based information (attributes) and accuracy. The current MAP message defined in J2735 is tailored toward intersections, and the corresponding road furniture/attributes are embedded in the MAP message. It is very difficult to apply the existing message to many emerging V2X applications. The new standard will provide a generalized 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.
Standard

Recommended Practices for Signalized Intersection Applications

2019-08-21
WIP
J2945/B
This document outlines how to use SAE J2735 and other related information for signalized intersection applications. The document focuses on how to use SPaT and MAP messages to support signalized-intersection applications. In general, implementation guidance is necessary to achieve interoperability by addressing the requirements for the options for both over the air dialogs and message contents, and to support larger intersection maps This document also addresses using Signal Request & Signal Status messages corresponding to vehicle functionality and approaches to traffic signal priority/pre-emption (TSP), including three different methods for implementing TSP over the air. The project is complementary to the connected intersections project being performed by ITE.
Standard

Traffic Probe Use and Operation

2019-08-21
WIP
J2945/C
This recommended practice will provide guidance on Traffic Probe Use data to manufacturers that are either Transportation System Management (TSM) core or aligned entities. The recommended practice originates from prior work of the Society of Automotive Engineers (SAE) Dedicated Short Range Communication (DSRC) Technical Committee, as well as existing practices implemented by industry, academia and government. The recommended practice informs manufacturers and practitioners of message use and operation within an automated collection system involved in the orchestration of safe, efficient, and reliable movement of people and goods. The recommended practice for Traffic Probe Use and Operation will support practitioners through the definition of message structure, on-board processing and storage requirements, the operational preservation of vehicle anonymity, and message event management criteria.
Standard

Road Safety Applications

2016-09-30
WIP
J2945/4
This standard will serve to re-work and extend the existing SAE J2735 message elements in order to include additional travel and roadway information from the infrastructure to enhance safety awareness and promote the exchange and transfer of such messages types between vehicles and the infrastructure (V2I). Fundamentally this document will outline the needs and detail the system requirements to support a variety of use cases linking to the J2735 effort as other J2945/x documents do. The initial scope will be to revise the structure of the existing “TIM” message to reflect the lessons learned from the various deployment activities such as the BIM developed by an automotive OEM consortium. The objective is to improve the general functionality of the message set in key areas such as message linking, content segmentation, message forwarding within a security framework, and new application areas beyond what is enabled by the TIM.
X