Browse Topic: Communication protocols

Items (553)
J1939 Digital AnnexJ1939DA_201402 (Current)12/8/2025
The J1939 Digital Annex The J1939 Digital Annex, introduced in August 2013, offers key J1939 technical data in an Electronic Spreadsheet that can be easily searched, sorted, and adapted to other formats. J1939DA contains all of the SPNs (parameters), PGNs (messages), and other J1939 data previously published in the SAE J1939 top level document. J1939DA also contains all of the SLOTs, Manufacturer ID Codes, NAME Functions, and Preferred Addresses previously published in the SAE J1939 top level and the J1939-71 document. J1939DA contains the complete technical details for all of the SPNs and PGNs previously published in the SAE J1939-71 document. For all other SPNs and PGNs which are published in a document other than SAE J1939-71, J1939DA lists only basic details along with a reference to the document that contains the complete technical details. J1939DA replaces, and expands upon, the 1939 Companion Spreadsheet (CS1939), which was last published through November 2012. The data fields included in J1939DA for PGNs are: PGN Parameter Group Label Acronyn EDP DP PF PGN Length PS PGN Description Multipacket Transmission Rate PGN Data Length Default Priority PGN Reference PGN Document The data fields included in J1939DA for SPNs are: SPN SPN Name SPN Description SPN Length Resolution Offset Data Range Operational Range Units SLOT Identifier SPN Type SPN Reference SPN Document The J1939 Digital Annex is current through Fourth Quarter 2013 and can be purchased separately or as part of the SAE J1939 Standards Collection on the Web.
Truck Bus Control and Communications Network Committee
This document applies to safety observers or spotters involved with the use of outdoor laser systems. It may be used in conjunction with SAE Aerospace Standard (AS4970) “Human Factors Considerations for Outdoor Laser Operations in the Navigable Airspace.” Additional control measures may be applicable and are listed in ANSI Z136.6.
G10T Laser Safety Hazards Committee
This document covers the requirements for SAE implementations based on ISO 17987:2016. Requirements stated in this document will provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This will assure full serial data communication among all connected devices regardless of supplier.The goal of SAE J2602-1 is to improve the interoperability and interchangeability of LIN devices within a network by adding additional requirements that are not present in ISO 17987:2016 (e.g., fault tolerant operation, network topology, etc.).The intended audience includes, but is not limited to, ECU suppliers, LIN controller suppliers, LIN transceiver suppliers, component release engineers, and vehicle system engineers.The term “master” has been replaced by “commander” and term “slave” with “responder” in the following sections.
Vehicle Architecture For Data Communications Standards
SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year, as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to API version 04.04 of the SAE J2534-1 specification. It is not required for an interface to be fully compliant with API version 04.04 of the SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the vehicle OEMs and scan tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.
Vehicle E E System Diagnostic Standards Committee
This SAE Aerospace Information Report (AIR) reviews technical, operational, and maintenance data being exchanged between key stakeholders in aerospace asset lifecycle and data standards available for such exchanges. It identifies gaps and non-availability of data standards in certain areas. The scope of the current document is limited to aircraft operations, maintenance and disposal stages post-build phase, and does not include the detailed interactions during the aircraft build phase.
G-31 Electronic Transactions for Aerospace Committee
The security of connected health technology is often assumed to exist when it does not, or considered to be prohibitively expensive or complex, or, worst of all, relegated to an afterthought. This is dangerous thinking, especially as the industry increasingly moves to a smartphone-based command-and-control model for these safety-critical applications.
V2X Communications Message Set Dictionary™ SetJ2735SET_202007 (Historical)7/23/2020
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made, and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style. The J2735 Standard specifies a message set, and its data frames and data elements, specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced simply as "DSRC") communications systems. The ASN.1 integrates software for validation of telecommunications and networking. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and encoding and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards. You may also be interested in: V2X Communications Message Set Dictionary™ the J2735 PDF V2X Communications Message Set Dictionary™ J2735 ASN file includes the ASN file (ZIP format) - download purchase only Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ the J2945/2 PDF Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ J2945/2 ASN file that includes the ASN file (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ Set includes the J2945/2 ASN file and the J2945/2 PDF (ZIP format) - download purchase only. Requirements for Road Weather Applications™ the J2945/3 PDF Requirements for Road Weather Applications™ J2945/3 ASN file that includes the ASN file (ZIP format) - download purchase only. Requirements for Road Weather Applications™ Set includes the J2945/3 ASN file and the J2945/3 PDF (ZIP format) - download purchase only.
V2X Core Technical Committee
V2X Communications Message Set Dictionary™ ASN fileJ2735ASN_202007 (Historical)7/23/2020
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made, and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style. The J2735 Standard specifies a message set, and its data frames and data elements, specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced simply as "DSRC") communications systems. The ASN.1 integrates software for validation of telecommunications and networking. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and encoding and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards. You may also be interested in: V2X Communications Message Set Dictionary™ the J2735 PDF V2X Communications Message Set Dictionary™ Set includes the J2735 ASN file and the J2735 PDF (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ the J2945/2 PDF Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ J2945/2 ASN file that includes the ASN file (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ Set includes the J2945/2 ASN file and the J2945/2 PDF (ZIP format) - download purchase only. Requirements for Road Weather Applications™ the J2945/3 PDF Requirements for Road Weather Applications™ J2945/3 ASN file that includes the ASN file (ZIP format) - download purchase only. Requirements for Road Weather Applications™ Set includes the J2945/3 ASN file and the J2945/3 PDF (ZIP format) - download purchase only.
V2X Core Technical Committee
Requirements for Road Weather Applications™ ASN FileJ2945/3ASN_202004 (Historical)4/23/2020
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. SAE J2945/3 specifies interface requirements for weather data collection and distribution using V2X communications, including detailed systems engineering documentation (needs and requirements mapped to appropriate data exchanges). The weather data can be used for traffic management, vehicle safety and other roadway applications that are represented within the National ITS Architecture. You may also be interested in: Requirements for Road Weather Applications™ the J2945/3 PDF Requirements for Road Weather Applications™ Set includes the J2945/3 ASN file and the J2945/3 PDF (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ the J2945/2 PDF Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ J2945/2 ASN file that includes the ASN file (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ Set includes the J2945/2 ASN file and the J2945/2 PDF (ZIP format) - download purchase only. V2X Communications Message Set Dictionary™ the J2735 PDF V2X Communications Message Set Dictionary™ J2735 ASN file includes the ASN file (ZIP format) - download purchase only V2X Communications Message Set Dictionary™ Set includes the J2735 ASN file and the J2735 PDF (ZIP format) - download purchase only.
Infrastructure Applications Technical Committee
Requirements for Road Weather Applications™ SetJ2945/3SET_202004 (Historical)4/23/2020
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. SAE J2945/3 specifies interface requirements for weather data collection and distribution using V2X communications, including detailed systems engineering documentation (needs and requirements mapped to appropriate data exchanges). The weather data can be used for traffic management, vehicle safety and other roadway applications that are represented within the National ITS Architecture. You may also be interested in: Requirements for Road Weather Applications™ the J2945/3 PDF Requirements for Road Weather Applications™ J2945/3 ASN file that includes the ASN file (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ the J2945/2 PDF Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ J2945/2 ASN file that includes the ASN file (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness™ Set includes the J2945/2 ASN file and the J2945/2 PDF (ZIP format) - download purchase only. Dedicated Short Range Communications (DSRC) Message Set Dictionary™ the J2735 PDF Dedicated Short Range Communications (DSRC) Message Set Dictionary™ J2735 ASN file includes the ASN file (ZIP format) - download purchase only Dedicated Short Range Communications (DSRC) Message Set Dictionary™ Set includes the J2735 ASN file and the J2735 PDF (ZIP format) - download purchase only.
Infrastructure Applications Technical Committee
Selftrust - A Practical Approach for Trust Establishment2020-01-07204/14/2020
In recent years, with increase in external connectivity (V2X, telematics, mobile projection, BYOD) the automobile is becoming a target of cyberattacks and intrusions. Any such intrusion reduces customer trust in connected cars and negatively impacts brand image (like the recent Jeep Cherokee hack). To protect against intrusion, several mechanisms are available. These range from a simple secure CAN to a specialized symbiote defense software. A few systems (e.g. V2X) implement detection of an intrusion (defined as a misbehaving entity). However, most of the mechanisms require a system-wide change which adds to the cost and negatively impacts the performance. In this paper, we are proposing a practical and scalable approach to intrusion detection. Some benefits of our approach include use of existing security mechanisms such as TrustZone® and watermarking with little or no impact on cost and performance. In addition, our approach is scalable and does not require any system-wide changes. To detect intrusions, we propose a combination of TrustZone® secure space approach along with a mechanism of static and dynamic watermarks. The current scope of research is restricted to architectures which provide a secure space to execute software. The research is an enhancement over the current TrustZone® implementation for device control post intrusion. In conclusion, the proposed approach is a simple and scalable mechanism for detection and control of intrusion.
Abhyankar, Ranjit VinayakA, Sreenath
Effects of a Probability-Based Green Light Optimized Speed Advisory on Dilemma Zone Exposure2020-01-01164/14/2020
Green Light Optimized Speed Advisory (GLOSA) systems have the objective of providing a recommended speed to arrive at a traffic signal during the green phase of the cycle. GLOSA has been shown to decrease travel time, fuel consumption, and carbon emissions; simultaneously, it has been demonstrated to increase driver and passenger comfort. Few studies have been conducted using historical cycle-by-cycle phase probabilities to assess the performance of a speed advisory capable of recommending a speed for various traffic signal operating modes (fixed-time, semi-actuated, and fully-actuated). In this study, a GLOSA system based on phase probability is proposed. The probability is calculated prior to each trip from a previous week’s, same time-of-day (TOD) and day-of-week (DOW) period, traffic signal controller high-resolution event data. By utilizing this advisory method, real-time communications from the vehicle to infrastructure (V2I) become unnecessary, eliminating data-loss related issues. The effects of three different advice approaches (conservative, balanced, and aggressive) on dilemma zone exposure are analyzed. Proof of concept is carried out by simulating drives through a test-route composed of an arterial that had historical high-resolution traffic signal event logs for a series of actuated-coordinated traffic signals during different TOD and DOW. A comparison was performed between unadvised and GLOSA advised trips obtained from approximately 486,000 simulated trajectories. Results were obtained by analyzing the vehicle’s probability of stopping from utilizing Traffic Engineering dilemma zone theory. Reductions of 93% in the amount of hard brakings and 96% in the number of crossings through red light were observed with the proposed system. This data suggests the feasibility of a probability-based advisory, as well as the viability of utilizing the proposed GLOSA system to minimize dilemma zone exposure.
Saldivar-Carranza, EnriqueLi, HowellKim, WoosungMathew, JijoBullock, DarcySturdevant, James
Hardware-in-the-Loop and Road Testing of RLVW and GLOSA Connected Vehicle Applications2020-01-13794/14/2020
This paper presents an evaluation of two different Vehicle to Infrastructure (V2I) applications, namely Red Light Violation Warning (RLVW) and Green Light Optimized Speed Advisory (GLOSA). The evaluation method is to first develop and use Hardware-in-the-Loop (HIL) simulator testing, followed by extension of the HIL testing to road testing using an experimental connected vehicle. The HIL simulator used in the testing is a state-of-the-art simulator that consists of the same hardware like the road side unit and traffic cabinet as is used in real intersections and allows testing of numerous different traffic and intersection geometry and timing scenarios realistically. First, the RLVW V2I algorithm is tested in the HIL simulator and then implemented in an On-Board-Unit (OBU) in our experimental vehicle and tested at real world intersections. This same approach of HIL testing followed by testing in real intersections using our experimental vehicle is later extended to the GLOSA application. The GLOSA application that is tested in this paper has both an optimal speed advisory for passing at the green light and also includes a red light violation warning system. The paper presents the HIL and experimental vehicle evaluation systems, information about RLVW and GLOSA and HIL simulation and road testing results and their interpretations.
Gelbal, Sukru YarenCantas, Mustafa RidvanAksun Guvenc, BilinGuvenc, LeventSurnilla, GopichandraZhang, HaoShulman, MichaelKatriniok, AlexanderParikh, Jayendra
Data-Driven Confidence Model for ADAS Object Detection2020-01-06954/14/2020
The majority of road accident is due to human error. Advanced Driver Assistance System (ADAS) has the potential to reduce human error and improve driving safety. Customers have shown a growing acceptance for ADAS technology. With the rising demand for safety and comfortable driving experience, the global market for ADAS is expected to grow to $67 billion by 2025. A reliable ADAS system requires an accurate and robust object-detection system. There is often a trade-off in tuning the system. On one hand, miss-detection can cause accidents; on the other hand, false-detection can result in ghost-braking and harm the driving experience. The ADAS system can access various information from different sources. However, a unified confidence model, which combines different indicators, has not been much studied in the literature. In this paper, we propose a data-driven method, which utilizes the features from radar, camera and the tracking system to produce a high-level confidence model. In addition, different regions regarding the ego vehicle usually have different emphases for detection error based on the system design requirements. And therefore, we can tune towards the design requirements by change the threshold of the classifier based on the region of interest. The proposed method was validated with real-world driving data and shown a better performance based on the design requirement of the Adaptive Cruise Control (ACC) and Autonomous Emergency Braking (AEB) functions.
Yang, HangZhang, DaruiWang, DaihanZhou, Jianguang
Vehicle Safe-Mode, Concept to Practice Limp-Mode in the Service of Cybersecurity11-02-02-00062/27/2020
This article describes both a concept and an implementation of vehicle safe-mode (VSM) - a mechanism that may help reduce the damage of an identified cyberattack to the vehicle, its driver, the passengers, and its surroundings. Unlike other defense mechanisms that try to block the attack or simply notify of its existence, the VSM mechanism responds to a detected intrusion by limiting the vehicle’s functionality to safe operations and optionally activating additional security countermeasures. This is done by adopting ideas from the existing mechanism of Limp-mode that was originally designed to limit the damage of a mechanical, or an electrical, malfunction and let the vehicle “limp back home” in safety. Like Limp-mode, the purpose of safe-mode is to limit the vehicle from performing certain functions when conditions arise that could render full operation dangerous: Detecting a malfunction in the Limp-mode case is analogous to detecting an active cybersecurity breach in the safe-mode case, and the reactions should be analogous as well. We demonstrate that the VSM can be implemented, possibly even as an aftermarket add-on: to do so we developed a proof-of-concept (PoC) system and actively tested it in real time on an operating vehicle. Once activated, our VSM system restricts the vehicle to Limp-mode behavior by guiding it to remain in low gear, taking into account the vehicle’s speed and the driver’s actions. Our system does not require any changes to the electronic control units (ECUs), or to any other part of the vehicle, beyond connecting the safe-mode manager (SMManager) to the correct bus. We note that our system can rely upon any deployed anomaly-detection system to identify the potential attack. We point out that restricting the vehicle to Limp-mode-like behavior by an aftermarket system is just an example. If a car manufacturer would integrate such a system into a vehicle, they would have many more options, and the resulting system would probably be safer and with a better human-machine interface.
Dagan, TsvikaMontvelisky, YuvalMarchetti, MircoStabili, DarioColajanni, MicheleWool, Avishai
Vehicle Application LayerJ1939/71_202002 (Historical)2/11/2020
The SAE J1939 communications network is developed for use in heavy-duty environments and suitable for horizontally integrated vehicle industries. The SAE J1939 communications network is applicable for light-duty, medium-duty, and heavy- duty vehicles used on-road or off-road, and for appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include, but are not limited to, on-highway and off-highway trucks and their trailers, construction equipment, and agricultural equipment and implements. SAE J1939-71 is the SAE J1939 reference document for the conventions and notations that specify parameter placement in PGN data fields, the conventions for ASCII parameters, and conventions for PGN transmission rates. This document previously contained the majority of the SAE J1939 data parameters and messages for information exchange between the ECU applications connected to the SAE J1939 communications network. It also contained reference figures and reference information. The data parameters (SPNs), messages (PGNs), reference figures, and information previously published within this document are now published in SAE J1939DA. There are several SAE J1939-7X documents that collectively define all of the SAE J1939 application layer data parameters and messages. Diagnostic services and some industry-specific data parameters and messages are documented within other SAE J1939-7X application layer documents. An ECU may simultaneously use and support data parameters and messages from multiple SAE J1939-7X application layer documents.
Truck Bus Control and Communications Network Committee
This standard specifies the communications hardware and software requirements for fueling hydrogen surface vehicles (HSV), such as fuel cell vehicles, but may also be used where appropriate, with heavy-duty vehicles (e.g., busses) and industrial trucks (e.g., forklifts) with compressed hydrogen storage. It contains a description of the communications hardware and communications protocol that may be used to refuel the HSV. The intent of this standard is to enable harmonized development and implementation of the hydrogen fueling interfaces. This standard is intended to be used in conjunction with the hydrogen fueling protocols in SAE J2601 and nozzles and receptacles conforming with SAE J2600.
Fuel Cell Standards Committee
Security Mechanism and Verification of Vehicle Network Based on Message Authentication2019-01-502811/4/2019
In view of the relatively bare network environment of the current car controller area network (CAN) and the high-performance requirements of most existing security mechanisms for electronic control units (ECUs), based on a new and faster network transmission protocol, a lightweight car bus authentication method using Message Authentication Code (MAC) is proposed. In this case, the vehicle network is modularized in dependence on the different functional requirements of each part of the bus, calculation tasks are processed by the gateway of the corresponding network segment, the confidentiality and correctness of the vehicle network can be guaranteed by synchronizing the message authentication tables in all nodes, and the transmission rate gets obvious improvement under CAN FD (flexible data-rate) protocol as well. In this paper, the security and real-time performance of the vehicle network are verified by hardware experiments, and the impact of the encryption method on the performance in the network is verified by software simulation. The CAN FD bus is formally designed in the MATLAB environment with finite state machine. The state machine model can dynamically display the communication behavior of the bus system during simulation, and is suitable for building an optimized simulation platform for the CAN FD bus network. Therefore, simulations on this platform are conducted, and comparisons between different performance parameters of CAN and CAN FD network are carried out.
Wang, BenxiongPi, DaweiXie, BoyuanWang, HongliangWang, Xianhui
A “STEP” Forward for Product Lifecycle Management19AERP10_0210/1/2019
The existence of countless proprietary file formats and the exchange of 3D CAD data has been a significant problem since the beginning of 3D CAD modeling. CAD applications and methods using digital data are constantly changing, which predicates the need for a solution to share validated and accurately translated data. Thus the birth of STEP242. Companies who are adopting model-based processes and tools within their organizations are using ISO 10303 STEP Application Protocols AP242 and AP239 for both exchanging data as well as maintaining data for archival and retrieval. Long Term Data Archival and Retrieval (LOTAR) (http://www.lotar-international.org) is an International project sponsored by multiple consortiums for the standardization of the archival and retrieval of digital product and technical data. This project is ISO compliant and works across multi-CAD environments enabling stake holders to share 3D data within a Model-Based Environment (MBE) or a digital enterprise. To ensure the preservation of design intent, validation properties that include geometric shape representation, assembly features, saved views, user-defined attributes, color, visibility, and Product & Manufacturing Information (PMI) 3D data need to be verified and validated for compliance. The culmination of these standards is allowing companies around the globe to manage interoperability with fewer challenges.
Items per page:
1 – 50 of 553