Search Results

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

SAE J2945/A and this Abstract Syntax Notation (ASN.1) file precisely define the structure of the data used to implement applications conformant to the Recommended Practice. Using the ASN.1 specification, a compiler tool can be used to produce encodings using encoding rules identified in J2945/A. Both this ASN.1 file and the SAE J2735 ASN.1 files are necessary to collectively implement the data structures described in the J2945/A. The combined library can be used by any receiving application (along with the additional logic of the application). SAE J2945/A also provides recommendations for the interface for sending and receiving Road Geometry and Attributes (RGA) messages. It provides the information necessary to build interoperable applications that rely on RGA messages.

This report specifies the minimum requirements for the Road Geometry and Attributes (RGA) data set (DS) to support road geometry related motor vehicle safety applications. Contained in this report are a concept of operations, requirements, and design, developed using a detailed systems engineering process. Utilizing the requirements, the RGA DS is defined, which includes the DS Abstract Syntax Notation One (ASN.1) format, data frames, and data element definitions. The requirements are intended to enable the exchange of the messages and their DS information to provide the desired interoperability and data integrity to support the applications considered within this report, as well as other applications which may be able to utilize the DS information. System requirements beyond this are outside the scope of this report.

This SAE Aerospace Information Report (AIR) describes the Architecture Framework for Unmanned Systems (AFUS). AFUS comprises a Conceptual View, a Capabilities View, and an Interoperability View. The Conceptual View provides definitions and background for key terms and concepts used in the unmanned systems domain. The Capabilities View uses terms and concepts from the Conceptual View to describe capabilities of unmanned systems and of other entities in the unmanned systems domain. The Interoperability View provides guidance on how to design and develop systems in a way that supports interoperability.

This SAE Information Report describes a concept of operations (CONOPS) for a Cooperative Driving Automation (CDA) Feature for infrastructure-based prescriptive cooperative merge. This work focuses on a Class D (Prescriptive; refer to J3216) CDA infrastructure-based cooperative merge Feature, supported by Class A (Status-Sharing) or Class C (Agreement-Seeking) messages among the merging cooperative automated driving system-operated vehicles (C-ADS-equipped vehicles). This document also provides a test procedure to evaluate this CDA Feature, which is suitable for proof-of-concept testing in both virtual and test track settings.

This SAE Information Report describes the deployment profile and radio parameters for a 10 MHz channel (i.e., LTE band 47 using EARFCN 54990 with a 10 MHz channel width, also known as Channel 180) based on LTE-V2X PC5 Sidelink (Mode 4) that can be used to support truck platooning applications. The content provided in this document is complementary to the content provided in SAE J3161 (which defines deployment profile and radio parameters for a 20 MHz channel).

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.

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.

This SAE Recommended Practice covers the requirements for ethernet physical layer (PHY) qualification (and as applicable to other high-speed networks [i.e., Audio Bus, LVDS, Ser-Des, etc.]). Requirements stated in this document provide a minimum standard level of performance for the PHY in the IC to which all compatible ethernet communications PHY shall be designed. When the communications chipset is an ethernet switch with an integrated automotive PHY (xBASE-T1), then the testing shall include performance for all switch PHY ports as well as each controller interface. No other features in the IC are tested or qualified as part of this SAE Recommended Practice. This assures robust serial data communication among all connected devices regardless of supplier. The goal of SAE J2962-3 is to commonize approval processes of ethernet PHYs across OEMs. The intended audience includes, but is not limited to, ethernet PHY suppliers, component release engineers, and vehicle system engineers.

This User Guide describes the content of the Rational Software Architect (RSA) version of the UCS Architectural Model and how to use this model within the RSA modeling tool environment. The purpose of the RSA version of the UCS Architectural Interface ICD model is to provide a model for Rational Software Architect (RSA) users, derived from the Enterprise Architect (EA) ICD model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6516 RSA Model, have been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces all UCS ICD messages all UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service and Non-Functional Properties Models

Governance of the Unmanned Aircraft System (UAS) Control Segment (UCS) Architecture was transferred from the United States Office of the Secretary of Defense (OSD) to SAE International in April 2015. Consequently, a subset of the UCS Architecture Library Release 3.4(PR) has been published under SAE as the Unmanned Systems (UxS) Control Segment (UCS) Architecture, AS6512. This Version Description Document (VDD) describes the correspondence and differences between the two architecture libraries.

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

This Abstract Syntax Notation (ASN.1) file precisely specifies the structure of the data used to support implementation of SAE International Standard J3217/R. Using the ASN.1 specification, a compiler tool can be used to produce encodings as required by the encoding rules identified in the standard (SAE J3217/R messages are encoded with UPER encoding). Both this file and the SAE J2735 ASN.1 files are necessary to collectively implement the data exchanges described in SAE J3217/R. The combined library can be used by any application (along with the additional logic of that application) to exchange the data using interfaces conformant to J3217/R. SAE J3217/R specifies interface requirements and message exchanges for configuration and reporting in road use charging systems.

The scope of this document is the concept of operations including reference system architecture, the user needs, the system functional and performance requirements, the messages, the corresponding data frames and elements, and other related functionality to enable road user charging.

This Abstract Syntax Notation (ASN.1) file precisely specifies the structure of the data used to support implementation of SAE International Standard J3217/R. Using the ASN.1 specification, a compiler tool can be used to produce encodings as required by the encoding rules identified in the standard (SAE J3217/R messages are encoded with UPER encoding). Both this file and the SAE J2735 ASN.1 files are necessary to collectively implement the data exchanges described in SAE J3217/R. The combined library can be used by any application (along with the additional logic of that application) to exchange the data using interfaces conformant to J3217/R. SAE J3217/R specifies interface requirements and message exchanges for configuration and reporting in road use charging systems.

The Use Case Trace (UCTRACE) is SAE publication AIR6519 of the Department of Defense Unmanned Control Segment (UCS) Architecture. This document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Use Case Trace (UCTRACE) Version 3.4(PR) approved for Distribution A public release 15.S-1859. This information is produced from a script run against the System Use Case Model contained in the UCS Architecture Model AS6518-MODEL.eap configuration item. The System Use Case Model includes, at its lowest level of elaboration, use cases Level 2/3 (L2/L3) that describe specific scenarios of message exchanges between Actors and internal system Participants via ServiceInterfaces. These message exchanges provide a way to create detailed traces that answer the question: “What UCS service interfaces must my components implement to satisfy functional requirements represented by a given Level 2/3 UCS use case?”

This platform specific Interface Control Document (ICD) provides an example mapping to the Object Management Group’s (OMG) Data Distribution Service (DDS) infrastructure middleware. The mapping is based on the Unmanned Systems (UxS) Control Segment (UCS) Architecture: Model, AS6518. A series of non-normative implementation choices have been made that are specific to this ICD. These implementation choices may not be appropriate for different system implementations. The machine readable ICD and result of this mapping and implementation choices are provided with AIR6521. Use and understanding of this document assumes a working knowledge of the UCS Architecture, the model structure and its contents.

This revision of AS6513 concerns conformance to the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Revision B, designated AS6512B (or later). The superseded AS6513A concerned conformance to the previous UCS Architecture, designated AS6512A. This document is the authoritative specification within the UCS Architecture for establishing conformance requirements for UCS products. The conformance of UCS products is determined by assessing the conformance of the UCS Product Description to the UCS Architecture. The UCS Product Description includes test artifacts.

This interface control document (ICD) specifies all software services in the Unmanned Systems (UxS) Control Segment Architecture, including interfaces, messages, and data model.

The UCS Architecture Model is the authoritative UML model of the UCS Architecture as defined in AS6512B