ISO/TC 22/SC 31/WG 4 - Network applications

This document specifies diagnostic application requirements and OSI-layer related communication profiles to ensure the interchange of digital information between towing and towed vehicles with a maximum authorized total mass greater than 3 500 kg. The conformance and interoperability test plans are not part of this document.

This document specifies the SAE J1939-based application layer, the payload of messages, and parameter groups for electronically controlled braking systems, including anti-lock braking systems (ABS), vehicle dynamics control systems (VDC), and running gears equipment, to ensure the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including communication between towed vehicles. Conformance and interoperability test plans are not part of this document.

This document specifies the communication interface between motion sensor and recording equipment. This includes the mechanical, electrical and logical requirements.

This document specifies all end-of-life activation of in-vehicle pyrotechnical devices identifiers, data identifiers, routine identifiers, data types, computations, and units. This document is based on: — new safety-relevant system technology designed into the vehicles, — new or more effective end-of-life activation of in-vehicle pyrotechnical devices, which requires additional test data, and routine controls. This document describes the end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements. This document specifies: — identifiers for end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements, — data identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements, — routine identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data definitions and associated technical requirements.

This document specifies the parameters used on the service interface of the recording equipment. Some of them are specified in detail in this document, while others are given in the ISO 14299 series.

This document specifies the CAN-based and the K-Line communication between the recording equipment and service tools for software download and calibrating purposes. The provided requirements and recommendations cover physical, data link, network, session, and application layers according to the OSI reference model as well as the unified diagnostics services.

This document specifies the electrical interfaces of the data and the service interfaces. The electrical interfaces to the CAN-based in-vehicle networks are not in the scope of this document.

This document specifies the mechanical dimensions of mandatory connectors and optional connectors used by the recording equipment for the data and the service interfaces. This includes, in particular, the connection to the CAN-based in-vehicle networks.

This document specifies the CAN-based data communication between the display unit and other devices connected to an SAE J1939-based in-vehicle network. The provided requirements and recommendations cover physical, data link, network, and application layers according to the OSI reference model. Additionally, it specifies the parameter groups, which are supported.

This document is applicable to road vehicles, where the electronic vehicle interface of the diagnostic link connector (DLC) is used to perform an end-of-life (EoL) activation of in-vehicle pyrotechnic devices. Apart from actual removal, this is the method to assure that no pyrotechnic substances are left in an EoL vehicle. On-board activation is an effective and safe method. This document describes use cases and specifies technical requirements in order to support the end-of-life activation of in-vehicle pyrotechnic devices via the electronic communication interface. This document references the ISO 14229 series unified diagnostic services implemented on diagnostic communication over controller area network (DoCAN) and Internet Protocol (DoIP) along with the required provision of data definitions. This document comprises: — terminology definitions; — definition of end-of-life activation of in-vehicle pyrotechnic devices relevant use cases; — requirements for the establishment of communication between the pyrotechnic device deployment tool (PDT) and the vehicle's pyrotechnic control unit(s) (PCU(s)); — requirements for the optional usage of a credentials-based authentication and authorisation mechanism between the PDT and the vehicle; — requirements for the protection against tampering of the defined end-of-life activation of in-vehicle pyrotechnic devices; — PCU-relevant technical requirements. PDT-relevant requirements are specified in a test equipment-specific standard with PDT-specific requirements.

This document specifies the standardized camera messages and data types used by a VCIC camera (OSI layer 7). Applications hosted on ECUs want to communicate with one or more cameras (e.g. “Ask camera for parameters.”). If the applications can use standardized services supported by the cameras (API layer 7), the development of a vision application is independent on the camera used. The services can be implemented by general libraries. The definition of streaming data is not an issue of this API.

This document specifies the application layer, the payload of messages, and parameter groups for equipment other than brakes and running gears, to ensure the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including communication between towed vehicles. This document supports the parameters and message sets for object detection (OD). The installation of the object detection (OD) device compliant to this document in the towed vehicle is identified by a dedicated message. Additionally, some lighting parameters and messages are specified. The conformance and interoperability test plans are not part of this document.

This document describes the data link layer (DLL) and physical layer (PHY) for the two CAN-based network interfaces specified in the 11992-series. The DLL sub-clauses are composed of: — DLL protocol entity requirements; — DLL device interface requirements; and — DLL network system requirements. Normally, the physical signalling sub-layer is implemented in the CAN protocol controller. The physical medium attachment sub-layer is normally implemented in the CAN transceiver or the System Base Chip (SBC). Optionally, it can comprise also additional protection circuitry. The media-dependent sub-layer comprises the connectors and the cabling. The physical signalling (PS) sub-clauses are composed of: — PS entity requirements; — PS device interface requirements; and — PS network system requirements. The physical medium attachment (PMA) sub-clauses are composed of: — PMA protocol entity requirements; and — PMA device interface requirements. The physical medium dependent (PMD) sub-clauses are composed of: — PMD entity requirements; — PMD device interface requirements; and — PMD network system requirements.

ISO 17215-2:2014 specifies how services can be discovered and controlled. This functionality is located mainly in layer 5 of the OSI model. Both discovery and control are implemented using the scalable service oriented middlewire over IP (SOME/IP). The general terminology defined in ISO 17215‑1 is also used in ISO 17215-2:2014.

ISO 17215-1:2014 describes the general use cases and communication scenarios, for a video communication interface for cameras used in video-based driver assistant systems. ISO 17215-1:2014 gives an overview of the structure and the partitioning of the ISO 17215 series and shows the relation between the different parts. ISO 17215-1:2014 serves as communication infrastructure for driver assistant applications that could be presenting video images to the driver, presenting warnings to the driver (e.g. using an HMI), or interacting with the vehicle (e.g. emergency breaking). The terminology defined in ISO 17215-1:2014 is common for all video communication interfaces for cameras communication systems and is used throughout all parts of the ISO 17215 series.

ISO 17215-4:2014 specifies the communication requirements for video camera interfaces. It is concerned mainly with layers 1 through 4 of the ISO/OSI basic reference model. These layers are the physical layer, the link layer, the network layer, and the transport layer. The general terminology defined in ISO 17215-1 is also used in ISO 17215-4:2014.

ISO 16844-7:2014 specifies the parameters used in the interchange of digital information between a road vehicle's tachograph system and vehicle units or a diagnostic tester, or within the tachograph system itself. The parameters are applicable for normal communication and/or diagnostic services. Parameters included in this part of ISO 16844 rely in particular on regulations stated in References [2] and [3].

ISO 16844-4:2015 specifies the controller area network (CAN) interface for the interchange of digital information between a road vehicle's tachograph system and vehicle units, and within the tachograph system itself. It specifies parameters of, and requirements for, the application of physical and data link layers of the electrical connection used in the electronic systems.

ISO 16844-6:2014 defines diagnostic communication and services for tachograph systems of road vehicles. The communication is specified both for CAN communication mode and K-line communication mode. The diagnostic services based on ISO 14229-1 and most services are common for the two communication interfaces. Interface specific implementations are specified in the respective sections.

ISO 17215-3:2014 specifies the standardized camera messages and data types used by a VCIC camera (OSI Layer 7). Applications hosted on ECUs want to communicate with one or more cameras (e.g. "Ask camera for parameters."). If the applications can use standardized services supported by the cameras (API layer 7), the development of a vision application should be independent of the camera used. The services can be implemented by general libraries. The definition of streaming data are not an issue of this API. The general terminology defined in ISO 17215-1 is also used in ISO 17215-3:2014.

ISO 11992-2:2014 specifies the parameters and messages for electronically controlled braking systems, including anti-lock braking systems (ABS) and vehicle dynamics control systems (VDC), as well as for running gear equipment (i.e. systems for steering, suspension, and tyres), to ensure that the data communication interchange of information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including the communication between (several) towed vehicles, on a dedicated network. It does not include any other communication on that network that is not related to the communication between those vehicles.

ISO 11992-4:2014 specifies the diagnostic communication over a CAN between the towing and towed vehicle(s) of a commercial vehicle and its trailer(s), according to ISO 11992-2 or ISO 11992-3, which allows a diagnostic tester (client) to control diagnostic functions in an on-vehicle ECU (server) embedded in a road vehicle using the communication gateways between the vehicles. It defines the data link layer's specific implementation of the unified diagnostic communication requirements, mainly given in the ISO 14229 and ISO 15765 document series by additional requirements and restrictions specific to the implementation of UDS on an ISO 11992 network. ISO 11992-4:2014 does not apply to any non-diagnostic message transmission use of the communication data link between two ECUs.

ISO 16844-1:2013 gives the dimensions and tests and requirements for the performance of electrical connectors needed for ensuring the interchangeability of different components of the tachograph systems used for road vehicles in accordance with Council Regulation (EEC) No. 3821/85 on recording equipment in road transport. In particular, ISO 16844-1:2013 specifies the connectors used to connect the recording unit of the tachograph to the vehicle electrical wiring harness.

ISO 16844-2:2011 specifies the electrical connection between the recording unit, and the vehicle network and the motion sensor, in tachograph systems used in road vehicles.

ISO 26021-5:2008 defines the requirements of redundancy hardware or software systems independent from the CAN line which are activated by the ACL hardware line. It also describes the additional sequences of the deployment process, and the technical details for the direct hardware connection between pyrotechnic device tool (PDT) and pyrotechnic control unit (PCU).

ISO 26021-3:2009 specifies the technical requirements to realize tool requirements for end-of-life activation of on-board pyrotechnic devices. It defines a test tool for ISO 26021 disposal functionality as well as the requirement for the final pyrotechnical device deployment tool (PDT). The focus is the definition of the human interface and the interfaces to the vehicle. It also defines general requirements for tests to validate the disposal functionality of the pyrotechnic control unit (PCU). It specifies two tool use-cases. Tool use-case 1 – deployment test tool (DTT): a development tool used to test and validate the PCU; the target users of this tool are the engineers of the PCU suppliers and the original equipment manufacturers (OEMs); the use case defines the human interface, the interfaces to the vehicle (CAN & ACL) and concrete test sequences. Tool use-case 2 – pyrotechnic device deployment tool (PDT): the final tool that is used to dispose pyrotechnical devices in vehicles; the target users of this tool are dismantlers; the use case defines the human interface, the interfaces to the vehicle (CAN & ACL), the environmental conditions and the deployment sequences.

ISO 26021-4:2009 defines the requirements of redundancy hardware or software systems independent from the controller area network (CAN) line, which are activated by the additional communication line (ACL hardware line). It describes the additional sequences of the deployment process, and the technical details for the direct hardware connection between the pyrotechnic device deployment tool (PDT) and the pyrotechnic control unit (PCU).

ISO 26021-2:2008 defines the deployment process, the system architecture, CAN-based communication methods and system preconditions which have to be implemented to fulfil the use cases defined in ISO 26021‑1. Additionally, the relationship to and use with other existing standards are defined. It also describes the technical details of the on-board deployment method. The way in which the pyrotechnic devices contained in the vehicle function in conjunction with the PDT is the primary focus of the document. Under the provisions of the document, the design of the PDT or PCU can be implemented in accordance with specific functionality and hardware requirements. This part of ISO 26021 specifies the access to the PCU. This includes communication as well as the logic sequences which are involved during the activation process.

ISO 26021-1:2008 gives an overview of the structure of ISO 26021 and the way it has been divided into parts, as well as showing the relationship between the parts. In addition, it outlines the use case scenarios in which the ISO 26021 document set will be used. It also defines terminology that is used throughout the ISO 26021 document set.

ISO 16844-3:2004 specifies the physical and data link layers of the electrical interface connecting a motion sensor to a vehicle unit, used in tachograph systems in road vehicles to perform speed signal transmission and data interchange.

ISO 16844-4:2004 specifies the CAN (controller area network) interface for the interchange -- performed in accordance ISO 16844-6 -- of digital information between a road vehicle's tachograph system and vehicle units, and within the tachograph system itself. It specifies parameters of, and requirements for, the physical and data link layers of the electrical connection used in the electronic systems.

ISO 16844-7:2004 specifies the parameters used in the interchange of digital information between a road vehicle's tachograph system and vehicle units or a diagnostic tester, or within the tachograph system itself. The parameters are applicable for real time communication and/or diagnostic services.

ISO 16844-6:2004 specifies diagnostic communication and services in tachograph systems used in road vehicles, for both the CAN and K-line communication modes. It is also applicable for programming purposes.

ISO 16844-5:2004 specifies the secured interchange of digital information between a road vehicle's tachograph system and vehicle units, and within the tachograph system itself. This type of interchange will be used for CAN communication or diagnostic services on CAN (controller area network), where there is need to protect interchanged parameters against fraud.

ISO 11992-3:2002 specifies the parameters and messages for electronically controlled braking systems other than systems for braking and running gear (i.e. steering, suspension and tyres), to ensure the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including communication between towed vehicles.

ISO 11992-1:2003 specifies the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg, and towed vehicles, including communication between towed vehicles in terms of parameters and requirements of the physical and data link layer of the electrical connection used to connect the electrical and electronic systems. It also includes conformance tests of the physical layer.