SAE J2945/B

Die Annotation des Normtextes SAE J2945/B :

When identifying the content of this report, one of the goals was that it supports a nationally interoperable method for connected vehicles (CVs) to make traffic signal priority and/or preemption (TSPP) requests of connected intersections (CIs) that support priority and/or preemption services. Given that, this report specifies the over-the-air (OTA) interface between CVs and CIs to support TSPP applications using updated revisions of the SAE J2735 Signal Request Message (SRM) and Signal Status Message (SSM) and the use of a Wireless Access in Vehicular Environments (WAVE) Service Advertisement (WSA) to advertise support for TSPP at a CI. Included are a concept of operations, requirements, design, and message structure definitions developed using a detailed systems engineering process.

NOTE 1: During the report development, the concept of the intelligence regarding the need for TSPP residing in the CV or the CI was discussed, e.g., a CV that can determine what it needs to support its current and/or future actions and can provide that information to the CI versus a CV that only provides information about its current actions and the CI determines what the CV needs. In general, the approach taken in this version of the report is of the latter where the CV just provides information to the CI about its current state and the CI makes all the preferential treatment decisions. When more information is available regarding a CV’s ability to know what it needs regarding TSPP and what the data requirements are to provide that information to the CI, future revisions of this report may be made available to provide this functionality.

NOTE 2: Given that this is the initial version of this report, the possibility exists that items will be uncovered by early adopters that necessitate changes. Should those changes require a break in backward compatibility with this version of the report, a versioning mechanism has been put in place whereby an application will know which version of this report a message is associated with. See 8.1 for the details on how this versioning mechanism is intended to work.

TYPE OF DOCUMENT: Ground Vehicle Standard