Browse Topic: Vehicle networking

Items (291)
Find
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
LIN Network for Vehicle ApplicationsJ2602-1_202510 (Current)10/1/2025
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
Data Dictionary for Quantities Used in Cyber Physical Systems (Enhanced License)AS6969_DA (Current)7/29/2024
Enhanced License for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) allowing for greater usage as outlined in the terms of the Enhanced License. Terms can be reviewed prior to purchase once item is added to the cart. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) This data dictionary provides a mathematically coherent set of definitions for quantity types used in data models for unmanned systems. In this data dictionary, a quantity is defined as a property of a phenomenon, substance, or body whose value has magnitude.
AS-4UCS Unmanned Systems Control Segment Architecture
J1939 Digital AnnexJ1939DA_202110 (Historical)10/21/2021
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
J1939 Digital AnnexJ1939DA_202108 (Historical)8/5/2021
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
J1939 Digital AnnexJ1939DA_202103 (Historical)3/29/2021
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
J1939 Digital AnnexJ1939DA_202012 (Historical)12/30/2020
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
Network End-to-End Data Link Evaluation System Transceiver Health MonitoringAIR6552/3 (Current)12/22/2020
This document establishes methods to obtain, store, and access data about the health of a fiber optic network using commercial sensors located in or near the transceiver. This document is intended for: Managers, Engineers, Contracting Officers, Third Party Maintenance Agencies, and Quality Assurance.
AS-3 Fiber Optics and Applied Photonics Committee
J1939 Digital AnnexJ1939DA_202010 (Historical)10/30/2020
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
J1939 Digital AnnexJ1939DA_202007 (Historical)7/15/2020
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
ROADMAP FOR IPV6 TRANSITION IN AVIATIONARINC686 (Current)6/19/2020
ARINC Report 686 represents the consensus of industry to prepare a roadmap migration from IPv4 to IPv6. This document describes airline objectives (air and ground side when possible) towards the development and introduction of IPv6. There are three distinct elements considered: 1) the applications for addressing aspects 2) the communication network(s) over which the applications are running for the IP protocol level itself and associated features, and 3) the physical link(s) the network(s) interface.
Airlines Electronic Engineering Committee
Application Layer - DiagnosticsJ1939/73_202006 (Historical)6/9/2020
SAE J1939-73 defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc. California-, EPA-, or EU-regulated OBD requirements are satisfied with a subset of the specified connector and the defined messages.
Truck Bus Control and Communications Network Committee
SAE J1939 Functional Safety Communications ProtocolJ1939-76_202004 (Current)4/29/2020
This document provides the technical requirements for implementing the SAE J1939 Functional Safety Communication Protocol in a manner determined suitable for meeting industry applicable functional safety standards.
Truck Bus Control and Communications Network Committee
J1939 Digital AnnexJ1939DA_202003 (Historical)3/31/2020
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
Permanently or Semi-Permanently Installed Diagnostic Communication Devices, Security GuidelinesJ3005-2_202003 (Current)3/4/2020
The scope of the document is to define the cyber-security best practices to reduce interference with normal vehicle operation, or to minimize risk as to unauthorized access of the vehicle's control, diagnostic, or data storage system; access by equipment (i.e., permanently or semi-permanently installed diagnostic communication device, also known as dongle, etc.) which is either permanently or semi-permanently connected to the vehicle's OBD diagnostic connector, either SAE J1939-13, SAE J1962, or other future protocol; or hardwired directly to the in-vehicle network. This document only specifies requirements and guidance for those diagnostic communication devices and not for the vehicle. Refer to SAE J3138 for requirements for the vehicle side.
Vehicle E E System Diagnostic Standards Committee
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
Cellular-key solution augments commercial-vehicle security20TOFHP02_082/1/2020
Connectivity's many benefits are matched by security concerns, which has prompted a number of security specialists from many fields to focus their attention on commercial vehicles. Irdeto, which provides security tools and services to disparate industries, is addressing commercial vehicles with cell phone-based keyless entry technology and cybersecurity services. The company, founded in 1969, lists diverse firms like Charter Communications, Comcast, 20th Century Fox and Alibaba Cloud as customers. As OEMs ramped up their connectivity offerings, Irdeto established its Connected Transport division in 2016. That division addresses overall cybersecurity while also offering a keyless entry system, Keystone, that uses cell phones to give users more control over vehicle access.
Costlow, Terry
J1939 Digital AnnexJ1939DA_202001 (Historical)1/31/2020
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
COMMUNICATIONS MANAGEMENT UNIT (CMU) MARK 2ARINC758-4 (Current)11/26/2019
This ARINC Standard specifies the ARINC 758 Mark 2 Communications Management Unit (CMU) as an on-board message router capable of managing various datalink networks and services available to the aircraft. Supplement 4 adds Ethernet interfaces, per ARINC Specification 664 Part 2. This will allow the CMU to communicate with IP based radio transceivers (e.g., L-Band Satellite Communication Systems (Inmarsat SwiftBroadband (SBB) and Iridium Certus), ACARS over IP, AeroMACS, etc.).
Airlines Electronic Engineering Committee
J1939 Digital AnnexJ1939DA_201910 (Historical)10/29/2019
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
Cyberattacks and Countermeasures for Intelligent and Connected Vehicles07-12-01-000510/14/2019
ICVs are expected to make the transportation safer, cleaner, and more comfortable in the near future. However, the trend of connectivity has greatly increased the attack surfaces of vehicles, which makes in-vehicle networks more vulnerable to cyberattacks which then causes serious security and safety issues. In this article, we therefore systematically analyzed cyberattacks and corresponding countermeasures for in-vehicle networks of intelligent and connected vehicles (ICVs). Firstly, we analyzed the security risk of ICVs and proposed an in-vehicle network model from a hierarchical point of view. Then, we discussed possible cyberattacks at each layer of proposed network model. After that, we provided an overview of the state of the art of the potential countermeasures against cyberattacks, such as secure hardware architecture, encryption and authentication, network firewall, intrusion detection system, and secure Firmware over the air (FOTA), and then a reasonable defense mechanism is proposed. At last, some challenges and future works related to cyberattacks against ICVs were discussed. This article aims to review the cyberattacks for ICVs and suggest comprehensive security countermeasures.
Luo, Feng, Hou, Shuo
Handling of Data from Heterogeneity of Vehicular Devices through Inter-Networking2019-28-015610/11/2019
Collection of various data from sensed data or raw availability of data from transcript or interdependency of data from various sources is a tedious task in a real time scenario like an Indian context is considered. Planning to find a solution to collect the data from various vehicular devices about the information related to the pollution becomes a cumbersome job. The need of the data, under what time duration data has to be transmitted, how they are interconnected and whether data needs to be stored or how they are processed is a major question that arise when dealing with collecting data and internetworking with various vehicular devices. A study of two different types of approaches for internetworking between the devices is discussed. One related to real time setup of mobile application and other with the dynamic cluster approach when the nodes are moving in a region was considered. Eliminating the speed of the vehicle with the movement of human formation of cluster with the mobile application to identify the various devices in the vicinity was identified and handoff between the clusters was also taken care in the first approach and in the second one performance metrics while establishing the multi-layer cluster was discussed.
Anuradha, Gnanaprakasam, Ramesh Babu, Kalivaradhan, Naiju, Chooriyaparambil Damodaran
Data Security ServicesJ1760_201910 (Current)10/9/2019
The scope of this SAE Recommended Practice is to require the use of the same Security Services as defined by the International Standard ISO/CD 15764, modified by the Class of Security as determined by the resource provider and referenced in Table 1, Extended Data Link Security References.
Motor Vehicle Council
Inline Optical Power Monitoring, Network End-to-End Data Link Evaluation SystemAIR6552/1 (Current)10/2/2019
This document establishes methods to obtain, store, and access data about the health of a fiber optic network using commercially available inline optical power monitoring sensors. This document is intended for: Managers Engineers Technicians Contracting officers Third party maintenance agencies Quality assurance
AS-3 Fiber Optics and Applied Photonics Committee
Rugged Network File ServersTBMG-351179/1/2019
Ampex Data Systems Hayward, CA 650-367-2011
J1939 Digital AnnexJ1939DA_201907 (Historical)7/22/2019
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
Communication Transceivers Qualification Requirements - CANJ2962/2_201907 (Current)7/18/2019
This document covers the requirements for transceiver qualification. Requirements stated in this document will provide a minimum standard level of performance for the CAN transceiver in the IC to which all compatible transceivers shall be designed. No other features in the IC are tested or qualified as part of this recommended practice. This will assure robust serial data communication among all connected devices, regardless of supplier. The goal of SAE J2962-2 is to commonize approval processes of CAN transceivers across OEMs. The intended audience includes, but is not limited to, CAN transceiver suppliers, component release engineers, and vehicle system engineers.
Vehicle Architecture For Data Communications Standards
Communication Transceivers Qualification Requirements - LINJ2962/1_201907 (Current)7/18/2019
This document covers the requirements for transceiver qualification. Requirements stated in this document will provide a minimum standard level of performance for the LIN transceiver block in the IC to which all compatible transceivers shall be designed. No other features in the IC are tested or qualified as part of this recommended practice. This will assure robust serial data communication among all connected devices regardless of supplier. The goal of SAE J2962-1 is to commonize approval processes of LIN transceivers across OEMs. The intended audience includes, but is not limited to, LIN transceiver suppliers, component release engineers, and vehicle system engineers.
Vehicle Architecture For Data Communications Standards
Autonomous Vehicle Engineering: May 201919AVEP055/2/2019
Editorial AVs, data and 'surveillance capitalism' SAE AV Activities SAE launches Office of Automation The Navigator Lessons from the 737 Max-8 debacle Scorecard Waymo, GM and Ford pegged as autonomous leaders Designs to Dye for: Autonomy's New-Materials Revolution From pineapples to bacteria, Envisage's research is focused on new-mobility's 'inside' story. Dining on Data Processing, in real-time, the enormous data stream that's flowing through AVs is increasingly the job of NVIDIA's mighty GPUs. Danny Shapiro relishes the feast. New Performance Metrics for Lidar Frame-rate measurement is so yesterday. Object-revisit rate and instantaneous resolution are more relevant metrics, and indicative of what a lidar system can and should do, argues a revolutionary in the artificial-perception space. 5G Cellular May Be Transformational for Automakers, Suppliers Long-awaited 5G cellular technology will be a foundational base for expanding vehicle connectivity and autonomy, enabling far more data capacity and lower latency. First Smile, Last Smile May Mobility is building a unique business model around AV shuttle services, explains COO and co-founder Alisyn Malek. 'Road Race' for AV Testing May Be Slowing To optimize safety, as well as cost- and time-efficiency, experts espouse increased virtual testing of autonomous vehicles as preferable to the industry's rush to test on public roads. The famous "Trolley Problem" might not really be the problem automat-ed-vehicle ethics have to solve. AV 'Goiters' Be Gone! Magneti Marelli's 'Smart Corner' technology aims to reduce cost, complexity and mass by integrating key vehicle sensors seamlessly into a vehicle's lighting modules. Supersonic Spy Drone To light off its ramjet engine, the 2,300-mph D-21 needed a blindingly-fast launch platform. Enter Lockheed's A-12-the precursor to the SR-71 Blackbird.
Verification Methods for AS5653 Network TerminalAS6088 (Current)4/24/2019
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Terminal (NT) complies with the NT requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
AS-1A Avionic Networks Committee
J1939 Digital AnnexJ1939DA_201904 (Historical)4/22/2019
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
Vehicle E/E Architecture and Its Adaptation to New Technical Trends2019-01-08624/2/2019
With the ever-increasing requirements on vehicle performance, as well as the trend of vehicle becoming an integral part of a much bigger ecosystem involving automated driving, intelligent transportation and smart city, more and more electrical/electronic (E/E) systems are integrated in vehicles. Vehicle E/E architecture being the fundamental organization of E/E components, the relationship among the components and with the environment, as well as the principles guiding the design and evolution, has essential influences on vehicle E/E system functions and performance. This paper gives the definition of vehicle E/E architecture and provides different views. The guidelines, contents and process of E/E architecture design are discussed. The evolution of E/E architecture, influence of the latest technical trends including electrification, automated driving, and connectivity functions on E/E architecture, and how vehicle E/E architecture adapts to the technical trends are studied.
Jiang, Shugang
A GPU Accelerated Particle Filter Based Localization Using 3D Evidential Voxel Maps2019-01-04914/2/2019
An evidential theory is widely used for 2D grid-based localization in a robotics field because the theory has benefits to consider additional states such as 'unknown' and 'conflict'. However, there are some problems such as computational limitation and excessive resource share when the localization system is expanded from 2D grid to 3D voxel. In order to overcome the problems, this paper proposes the parallelized particle filter based localization system using 3D evidential voxel maps. A many-core processor based parallel computing framework with optimization techniques is applied to accelerate the computing power. Experiments were performed to evaluate the performance of the localization system in a complex environment, and to compare the computational time and resources between various types of processing units. The experimental results show that the proposed parallel particle filter is much more efficient than particle filter without parallel computing regarding computational cost.
Cho, Sungjin, Kim, Chansoo, Jo, Kichun, Sunwoo, Myoungho
A Closed Loop Method for Vehicle Instrument Cluster Test Automation2019-01-12504/2/2019
Instrument Panel Cluster (IPC), is a key ECU in vehicles. As IPC is a visual product, testing the software features of IPC is highly manual effort. Software Testing constitutes for approx. 35% of the total Software Development Life Cycle (SDLC). High focus on quick to market, shorter SDLC coupled with manual validation environment poses a challenge of increasing testing efficiency and improving software quality. This challenge drove the need to investigate a solution to automate the testing process and cut down the huge manual effort that goes into validating an Instrument Panel Cluster (IPC) software. The proposed intrusive and non-intrusive approaches to automate the testing process of IPC software employs a Frame Grabbing technique for the former approach and a Camera based technique for the latter. Both the approaches are robust, reliable, and scalable and covers the major portion of Vehicle Instrument cluster test scenarios. The paper captures the results, advantages and the constraints in the implementation of both the approaches. The comprehensive evaluation of the proposed techniques will help in identifying the right approach for the need, satisfying necessary criteria for automation. The paper aims to provide a best possible solution to optimize the tedious efforts which goes into validating an Instrument Panel Cluster (IPC) software and in turn enables a flawless software delivery within the stipulated timeline.
G, Gayatri Sindhu, Ramu, Arunkumar, Shastry, Raghuram
Security Mechanisms Design of Automotive Gateway Firewall2019-01-04814/2/2019
Automotive security has become one of important topics in recent years under new automotive Electronic and Electrical Architecture (EEA). With the development of Intelligent Connected Vehicle (ICV), it has become possible to hack an automotive through in-vehicle networks. The introduction of Information Communications Technology (ICT) brings more risk threats to automotive. Researchers have shown that an attacker can easily tamper with many automotive functions via On-Board Diagnostic II (OBD-II) or In-Vehicle Infotainment (IVI). In order to protect automotive against malicious attacks, automotive security risks were analyzed and then security mechanisms based on network firewall were designed in this paper. Automotive network firewall is a security system that monitors and controls incoming and outgoing network traffics of automotive based on predetermined security rules. The main functions of network firewall include packet filter, anti-DoS and access control. Because of deferent security requirements of in-vehicle networks, CAN/FD and Ethernet were divided into two domains respectively. Packet filter mechanisms were designed to monitor CAN/FD, in which security level and time delay were considered. Ethernet firewall mechanisms were designed based on Stateful Packet Filter (SPF) technology. Beside packet filter mechanisms, anti-DoS and access control mechanisms were also designed. Security Real Time Operating System (SRTOS) was introduced to ensure lower layer security. Considering the ECU constraint, Hardware Security Module (HSM) is chosen to implement cryptography function. At last, proposed automotive network firewall were implemented base on a multicore MCU with HSM. The system is evaluated in several aspects such as packet throughput, time delay, anti-attack and memory usage. The evaluation results show that the automotive network firewall is effective and efficient.
Luo, Feng, Hou, Shuo
Continental's new CTO to lead retooled R&D pillar19AUTP03_143/1/2019
At a recent media roundtable with its executives, Continental introduced its new CTO, Dirk Abendroth, who took on that role on January 1, 2019. Abendroth, 43, will serve as chief technology officer of Continental's upcoming Automotive Group and report to Continental CEO Elmar Degenhart. Abendroth joins the global supplier from EV start-up Byton, where he led Powertrain and Autonomous Driving development since July 2016. The Hamburg native was previously at BMW in Munich in EV development, including work on the BMW i3 and i8. Note the term “upcoming,” as perhaps equally significant with its new CTO is a foundational change in Continental's corporate structure, along with a large shift in engineering expertise. The change in corporate structure is adapting to overall growth, and the company also plans to shift thousands of engineers to help it adapt to the rapidly evolving automotive landscape. Under its new Automotive Group, Continental will pool its R&D resources to instill faster creation of next-gen autonomous and connected mobility tech.
Seredynski, Paul
Still Unsettled on Vehicle Connectivity Standard19AVEP03_103/1/2019
As data and data-sharing become more crucial to the transportation evolution, the auto sector has yet to gain consensus on the best connectivity format. As autonomous vehicles inch closer to reality, a diverse range of companies and public entities are exploring ways to maximize their positive impact on traffic flows and congestion. Communication at all levels, both between vehicles and between public and private interest groups, will be an important element for improving efficiency.
Costlow, Terry
J1939 Digital AnnexJ1939DA_201902 (Historical)2/28/2019
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
OBD Traceability MatrixJ1939-90_201902 (Historical)2/5/2019
This Information Report is intended to supplement the J1939 documents by offering the application of SAE RP J1939 to OBD data communications in a form that can be sorted and searched for easier use. It is NOT intended as a substitute for the actual regulations and standards documents, and any discrepancies between this document and the published documents must be resolved in favor of the published documents. This spreadsheet outlines elements in ARB OBD II and HD OBD requirements and identifies which J1939 SPNs and messages may be used to satisfy the datastream, readiness, in-use ratio, and test results requirements.
Truck Bus Control and Communications Network Committee
Optional Pass-Thru FeaturesJ2534/2_201901 (Current)1/16/2019
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 an SAE J2534-1 specification. It is not required for an interface to be fully compliant with 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
Securing the Secret Key2019-01-00971/16/2019
Recent advances in automotive technologies have paved way to a new era of connectivity. Advanced Driver Assistance Systems are getting deployed in automobiles; many companies are developing driverless cars; connected cars are no more a work of mere research. [1] Vehicle manufacturers are developing ways to interface mobile devices with vehicles. However, all these advances in technology has introduced security risks. Unlike traditional computing systems, the security risk of an automobile can be fatal and can result in loss of lives [2]. The in-vehicle network of an automobile was originally designed to operate in a closed environment and hence network security was not considered during its design [3]. Several studies have already shown that an in-vehicle network can be easily compromised and an intruder can take full control of the vehicle. Researchers are working on various ways to solve this problem. Securing the in-vehicle communication by encrypting the messages is one such way. This depends on the strength of the secret key used to encrypt the messages. In an automobile, these secret keys will be inside the automobile itself. If the in-vehicle network is compromised, then the secret keys will get exposed to intruders. There should be mechanisms to secure the secret keys. In this paper, we propose a way of securing the secret key for automotive network.
SS, Narendra Kumar
Agricultural and Forestry Off-Road Machinery Control and Communication NetworkJ1939/2_201901 (Current)1/14/2019
SAE J1939-2 specifies the requirements for application of SAE J1939 in agricultural and forestry equipment. This document specifies the series of documents within the set of SAE J1939 documents that are applicable to agricultural and forestry equipment and provides further requirements for this industry. The SAE and ISO groups have cooperated to define agricultural and forestry networks in a manner to allow compatibility of ECUs and messaging protocols between the A&F and the T&B networks.
Truck Bus Control and Communications Network Committee
Comparative Analysis of Large Data Transfer in Automotive Applications Using Ethernet Switched Networks2019-26-00221/9/2019
Automotive radars and cameras form the backbone of self-driving cars, Active safety and Advanced Driver Assistant Systems (ADASs). Streaming sensor, camera and audio data between sensors and Electronic control units(ECUs) requires huge data exchange. Ethernet with its large bandwidth capability is typically used as physical medium to communicate large data in automotive in-vehicle networks. Large data generally deals with payload size greater than single Ethernet Maximum Transmission Unit(MTU) size i.e.1522 Bytes that shall be sent via the transport protocol of the underlying bus. The purpose of the paper is to compare four different methods for transferring large data for current automotive Ethernet requirements. The methods Udp/Ip Fragmentation, Application fragmentation, Tcp/Ip Fragmentation and IEEE1722 transport protocol are evaluated. Bench evaluation of these methods are performed using Vector/Elektrobit software. The optimal approach is evaluated based on network performance with End to End latency metric.
Chaudhari, Nayana, Ananthoju, Kalyan Chakravarthy, Isac, Sinu
THE NAVIGATOR19AUTP01_081/1/2019
There is no such thing as a free lunch, as the old truism goes. For more than a century, the auto industry business model has been to sell it and forget it. Once you drove off the lot in that shiny new machine, you were on your own, aside from warranty repairs for defects or compliance recalls. If you wanted to upgrade the functionality of your vehicle or even put fuel in to operate it, you paid out of pocket. Then Tesla seemed to turn that model on its head with free battery charging via its Supercharger network, and over-the-air (OTA) software updates.
Abuelsamid, Sam
Cybersecurity Considerations for Heavy Vehicle Event Data Recorders11-01-02-000612/14/2018
Trust in the digital data from heavy vehicle event data recorders (HVEDRs) is paramount to using the data in legal contests. Ensuring the trust in the HVEDR data requires an examination of the ways the digital information can be attacked, both purposefully and inadvertently. The goal or objective of an attack on HVEDR data will be to have the data omitted in a case. To this end, we developed an attack tree and establish a model for violating the trust needed for HVEDR data. The attack tree provides context for mitigations and also for functional requirements. A trust model is introduced as well as a discussion on what constitutes forensically sound data. The main contribution of this article is an attack tree-based model of both malicious and accidental events contributing to compromised event data recorder (EDR) data. A comprehensive list of mitigations for HVEDR systems results from this analysis.
Daily, Jeremy, Gardiner, Ben
Physical Layer, 250 Kbps, Un-Shielded Twisted Pair (UTP)J1939/15_201812 (Current)12/14/2018
This document describes a physical layer utilizing Unshielded Twisted Pair (UTP) cable with extended stub lengths for flexibility in ECU placement and network topology. Also, connectors are not specified. CAN controllers used on SAE J1939-15 networks must be restricted to use only Classical Frames as defined in ISO 11898- 1. A network which may have legacy controllers cannot tolerate FD Frames. These SAE Recommended Practices are intended for light- and heavy-duty vehicles on- or off-road as well as appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include, but are not limited to: on- and off-highway trucks and their trailers; construction equipment; and agricultural equipment and implements.
Truck Bus Control and Communications Network Committee
J1939 Digital AnnexJ1939DA_201810 (Historical)10/31/2018
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
Keeping Data Fresh for Wireless NetworksTBMG-328689/1/2018
For wireless networks that share time-sensitive information on the fly, it's not enough to transmit data quickly: that data also needs to be fresh. Consider the many sensors in your car. While it may take less than a second for most sensors to transmit a data packet to a central processor, the age of that data may vary depending on how frequently a sensor is relaying readings. In an ideal network, these sensors should be able to transmit updates constantly, providing the freshest, most current status for every measurable feature, from tire pressure to the proximity of obstacles. But there's only so much data that a wireless channel can transmit without completely overwhelming the network.
Verification Methods for AS5653 Network Controller, Network Terminal, and Switch Physical LayerAS6260 (Current)8/13/2018
This document was prepared by the SAE AS-1A2 Committee to establish techniques for verifying that Network Controllers (NCs), Network Terminals (NTs), switches, cables, and connectors comply with the physical layer requirements specified in AS5653B. Note that this verification document only verifies the specific requirements from AS5653B and does not verify all of the requirements invoked by documents that are referenced by AS5653B. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653B and in this verification document.
AS-1A Avionic Networks Committee
J1939 Digital AnnexJ1939DA_201808 (Historical)8/2/2018
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
Truck Bus Control and Communications Network Committee
Items per page:
1 – 50 of 291