ISO/TC 22/SC 31/WG 2 - Vehicle diagnostic protocols

This document specifies an application profile for the implementation of unified diagnostic services (UDS) local interconnect network (LIN) in road vehicles (UDSonLIN). UDSonLIN references ISO 14229‑1 and ISO 14229‑2 and specifies implementation requirements of the diagnostic services to be used for diagnostic communication on Local Interconnect Network. This document includes: — additional requirements specific to the implementation of UDS on local interconnect network; and — specific restrictions in the implementation of UDS on local interconnect network.

This document specifies an application profile for the implementation of unified diagnostic services (UDS) Internet Protocol (IP) in road vehicles (UDSonIP). UDSonIP references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the diagnostic services to be used for diagnostic communication on Internet Protocol. This document includes — additional requirements specific to the implementation of UDS on the Ethernet network, and — specific restrictions in the implementation of UDS on the Ethernet network.

This document specifies an application profile for the implementation of unified diagnostic services (UDS) on controller area network (CAN) in road vehicles. UDSonCAN references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the diagnostic services to be used for diagnostic communication on CAN. This document specifies — additional requirements specific to the implementation of UDS on the CAN network, and; — specific restrictions in the implementation of UDS on the CAN network.

This document specifies common session layer services and requirements to provide independence between unified diagnostic services (ISO 14229-1) and all transport protocols and network layer services (e.g. ISO 13400-2 DoIP, ISO 15765-2 DoCAN, ISO 10681-2 communication on FlexRay, ISO 14230-2 DoK-Line, and ISO 20794-3 CXPI). This document specifies a common service primitive interface between OSI layer 5 (session) and layer 4 (transport) via so-called service request/indication/confirmation primitives.

This document specifies the requirements related to the connection between the external test equipment externally connected to the diagnostic link connector and the in-vehicle CAN network to successfully establish, maintain and terminate communication.

This document specifies requirements for CAN-based communication systems between the in-vehicle network and the diagnostic link connector of the vehicle. This document does not specify any requirements related to the in-vehicle CAN network architecture. This document specifies the requirements to enable the in-vehicle CAN-based communication systems to establish, maintain, and terminate communication with the devices connected to the diagnostic link connector.

This document specifies the implementation of a common set of unified diagnostic services (UDS) on clock extension peripheral interface networks in road vehicles. The UDSonCXPI diagnostics defines methods to implement diagnostic data transfer between a client and the CXPI slave nodes via the CXPI master node. This document specifies support of three different diagnostic classes for CXPI slave nodes. This document references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the UDSonCXPI communication protocol for mainly HMI (Human Machine Interface), but not limited to, electric/electronic systems of road vehicles. UDSonCXPI defines how to implement the diagnostic data transfer between a client and CXPI slave nodes via CXPI master node. NOTE UDSonCXPI does not specify any requirement for the in-vehicle CXPI bus architecture. This document refers to information contained in ISO 14229-1, ISO 14229-2 and ISO 20794 (all parts). This document does not include any redundant information of the above-mentioned documents. It focuses on — additional requirements specific to the implementation of UDSonCXPI network, and — specific restrictions in the implementation of UDSonCXPI network.

This document specifies data link independent requirements of diagnostic services, which allow a diagnostic tester (client) to control diagnostic functions in an on-vehicle electronic control unit (ECU, server) such as an electronic fuel injection, automatic gearbox, anti-lock braking system, etc. connected to a serial data link embedded in a road vehicle. It specifies generic services, which allow the diagnostic tester (client) to stop or to resume non-diagnostic message transmission on the data link. This document does not apply to non-diagnostic message transmission on the vehicle's communication data link between two electronic control units. However, this document does not restrict an in-vehicle on-board tester (client) implementation in an ECU in order to utilize the diagnostic services on the vehicle's communication data link to perform bidirectional diagnostic data exchange. This document does not specify any implementation requirements.

This document specifies the requirements for secured and unsecured diagnostic communication between client DoIP entity and server(s) installed in the vehicle using Internet protocol (IP) as well as the transmission control protocol (TCP) and user datagram protocol (UDP). This includes the definition of vehicle gateway requirements (e.g. for integration into an existing computer network) and test equipment (client DoIP entity) requirements (e.g. to detect and establish communication with a vehicle). This document specifies features that are used to detect a vehicle in a network and enable communication with the vehicle gateway as well as with its sub-components during the various vehicle states. These features are separated into two types: mandatory and optional. This document specifies the following mandatory features: — vehicle network integration (IP address assignment); — vehicle announcement and vehicle discovery; — vehicle basic status information retrieval (e.g. diagnostic power mode); — connection establishment (e.g. concurrent communication attempts), connection maintenance and vehicle gateway control; — data routing to and from the vehicle's sub-components; — error handling (e.g. physical network disconnect). This document specifies the following optional features: — DoIP entity status monitoring; — transport layer security (TLS); — DoIP entity firewall capabilities.

ISO 13400-3:2016 specifies the vehicle communication interface and test equipment requirements for a physical and data link layer based on IEEE 802.3 100BASE-TX. This interface serves as the physical basis for IP-based communication between the vehicle and test equipment. This document specifies the following aspects: - requirements for signal and wiring schematics in order to ensure physical layer compatibility of the vehicle interface and Ethernet networks and test equipment communication interfaces; - discovery/identification of the in-vehicle diagnostic Ethernet interface; - activation and deactivation of the in-vehicle diagnostic Ethernet interface; - mechanical and electrical diagnostic connector requirements; - this edition has been modified to include the identification of two Ethernet pin assignments.

ISO 14230-2:2016 specifies data link layer services tailored to meet the requirements of UART-based vehicle communication systems on K-Line as specified in ISO 14230‑1. It has been defined in accordance with the diagnostic services established in ISO 14229‑1 and ISO 15031‑5, but is not limited to use with them and is also compatible with most other communication needs for in-vehicle networks. The protocol specifies an unconfirmed communication. The diagnostic communication over K-Line (DoK-Line) protocol supports the standardized service primitive interface as specified in ISO 14229‑2. ISO 14230-2:2016 provides the data link layer services to support different application layer implementations like the following: - enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics); - emissions-related OBD as specified in ISO 15031, SAE J1979-DA and SAE J2012-DA; - in addition, ISO 14230-2:2016 clarifies the differences in initialization for K-line protocols defined in ISO 9141 and ISO 14230. This is important since a server supports only one of the protocols mentioned above and the client has to handle the coexistence of all protocols during the protocol determination procedure.

ISO 15765-2:2016 specifies a transport protocol and network layer services tailored to meet the requirements of CAN‑based vehicle network systems on controller area networks as specified in ISO 11898‑1. It has been defined in accordance with the diagnostic services established in ISO 14229‑1 and ISO 15031‑5 but is not limited to use with them and is also compatible with most other communication needs for in‑vehicle networks. ISO 11898‑1 specifies variable length CAN frames with a maximum payload size dependent on the protocol device used. A CLASSICAL CAN protocol device can transmit/receive frames with payload sizes ranging from 0 bytes to 8 bytes per frame. A CAN FD (flexible data rate) protocol device can transmit/receive frames with payload sizes from 0 bytes to 64 bytes. A CAN FD protocol device is also capable of transmitting/receiving CLASSICAL CAN frames. The diagnostic communication over controller area network (DoCAN) protocol supports the standardized service primitive interface as specified in ISO 14229‑2 (UDS). ISO 15765-2:2016 provides the transport protocol and network layer services to support different application-layer implementations such as - enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics), - emissions-related on-board diagnostics (OBD) as specified in ISO 15031, - world-wide harmonized on-board diagnostics (WWH-OBD) as specified in ISO 27145, and - end of life activation on on-board pyrotechnic devices (ISO 26021). The transport protocol specifies an unconfirmed communication. NOTE This part of ISO 15765 does not determine whether CLASSICAL CAN, CAN FD or both are recommended or required to be implemented by other standards referencing this part of ISO 15765.

ISO 27145-4:2016 defines the requirements to successfully establish, maintain and terminate communication with a vehicle that implements the requirements of the WWH-OBD GTR (Global technical regulation No. 5; see Reference [16]). This requires plug and play communication capabilities for the vehicle, as well as for any test equipment that intends to establish communication with a vehicle. This part of ISO 27145 details all the OSI layer requirements to achieve this goal. ISO 27145-4:2016 is intended to become the single communication standard for access to information relating to vehicle on-board diagnostics (VOBD). To allow for a smooth migration from the existing communication standards to this future world-wide standardized communication standard, the communication concept as specified in this part of ISO 27145 is based on two different data links: - diagnostic communication over Controller Area Network (DoCAN), ISO 15765‑4; - diagnostic communication over Internet Protocol (DoIP), ISO 13400 (all parts). NOTE It is intended that this part of ISO 27145 will be extended as necessary upon introduction of additional communication media. IMPORTANT ? Use cases deriving from country-specific implementation of GTR No. 5 into local legislation are not included in this part of ISO 27145.

ISO 13400-4:2016 specifies a minimum set of diagnostic Ethernet connector requirements which are based on ISO 15031‑3. The ISO 15031‑3 diagnostic connector is referenced by legislation in many countries. The diagnostic connection specified in this part of ISO 13400 consists of two mating connectors: the vehicle connector and the external test equipment connector as specified in ISO 15031‑3. ISO 13400-4:2016 specifies: - the functional requirements for the vehicle connector. These functional requirements are separated into two principal areas: connector contact allocation and electrical requirements for connector and related electrical circuits; - the functional requirements for the external test equipment connector. These functional requirements are separated into two principal areas: connector contact allocation and electrical requirements for connector and related electrical circuits. Two (2) different connector layouts and pin-outs are specified in this part of ISO 13400: a) Ethernet pin assignment option 1 (see Annex A); b) Ethernet pin assignment option 2 (see Annex B). Historically, option 1 is specified to meet Ethernet pin assignment of road vehicles already launched onto the market and may be used to resolve conflicts with vehicle manufacturer-specific usage of discretionary pins, e.g. pins 1 and 9. Option 2 is specified to meet the Ethernet pin assignment of road vehicles to resolve conflicts with vehicle manufacturer-specific usage of discretionary pins, e.g. pins 3 and 11. A discovery/identification and activation method of the vehicle's Ethernet via the "Ethernet Activation Line" is specified in ISO 13400‑3.

ISO 15031-5:2015 is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe and any other region that may adopt similar requirements in the future. It specifies: message formats for request and response messages, timing requirements between request messages from external test equipment and response messages from vehicles and between those messages and subsequent request messages, behaviour of both the vehicle and external test equipment if data are not available, and a set of diagnostic services, with corresponding content of request and response messages, to satisfy OBD regulations. ISO 15031-5:2015 includes capabilities required to satisfy OBD requirements for multiple regions, model years, engine types, and vehicle types. Those regulations are not yet final for some regions and are expected to change in the future. ISO 15031-5:2015 makes no attempt to interpret the regulations and does not include applicability of the included diagnostic services and data parameters for various vehicle applications. The user of ISO 15031-5:2015 is responsible for verifying the applicability of each clause of this part of ISO 15031 for a specific vehicle, engine, model year, and region. ISO 15031-5:2015 specifies diagnostic services and functionally addressed request/response messages required to be supported by motor vehicles and external test equipment for diagnostic purposes which pertain to motor vehicle emission-related data. Any external test equipment meeting the requirements of ISO 15031‑4 use these messages to retrieve emissions-related information from the vehicle. Each clause in ISO 15031-5:2015 which specifies additional details to existing clauses of ISO 9141‑2, ISO 14230‑4, SAE J1850, and ISO 15765‑4 supersede those specifications. ISO 15031-5:2015 references SAE J1979-DA (Digital Annex), which includes all definitions of PIDs, OBDMIDs, TIDs, and INFOTYPEs. ISO 15031-5:2015 provides the mechanism to satisfy the requirements included in the country-specific regulations and not all capabilities included in ISO 15031-5:2015 are required by the country-specific regulations. ISO 15031-5:2015 is not considered a final authority for interpretation of the regulations. Therefore, readers should determine the applicability of capabilities defined in ISO 15031-5:2015 for their own specific needs.

ISO 15031-6:2015 provides uniformity for standardized diagnostic trouble codes (DTC) that electrical/electronic On-Board Diagnostic (OBD) systems of motor vehicles are required to report when malfunctions are detected. It further provides guidance for uniform messages (text descriptor) associated with these codes. ISO 15031-6:2015 specifies the rules and guidelines for the definition of the following: a) the diagnostic trouble code format, which consists of addressing format, structure and messages; b) a description of the standardized set of diagnostic trouble codes and descriptions contained in SAE J2012-DA. The two most significant bytes of a DTC may be decoded according to two different lists in two formats: DTC Format Identifier 0016 and 0416; and c) a description of the standardized set of diagnostic trouble codes subtypes known as failure types contained in SAE J2012-DA (applies only when 3-byte DTCs are used). ISO 15031-6:2015 specifies all general rules and guidelines to define new diagnostic trouble codes. It references SAE J2012-DA (Digital Annex), which includes all standardized DTCs (number and text descriptor) as well as all diagnostic trouble codes subtypes known as failure types.

ISO 15031-4:2014 specifies a set of standard diagnostic services to be provided by vehicles (OBD services). ISO 15031-4:2014 specifies a complementary set of facilities, to be provided by external test equipment, which will include scan tool facilities. These facilities provide complete, efficient, and safe access to all of the public OBD (on-board diagnosis) services on any vehicle, which is compliant with ISO 15031-4:2014. ISO 15031-4:2014 specifies - a means of establishing communications between an OBD-equipped vehicle and external test equipment, and - a set of diagnostic services to be provided by the external test equipment in order to exercise the services defined in ISO 15031‑5. ISO 15031-4:2014 does not preclude the inclusion of additional capabilities or functions in external test equipment. However, it is the responsibility of the external test equipment designer to ensure that no such capability or function can adversely affect either an OBD-equipped vehicle, which may be connected to the external test equipment or the external test equipment itself.

ISO 15031-7:2013 gives guidelines for the protection of road vehicle modules from unauthorized intrusion through a vehicle diagnostic data link. These security measures offer vehicle manufacturers the flexibility to tailor their security to their own specific needs and do not exclude other, additional measures. ISO 15031-7:2013 applies to vehicle modules whose solid-state memory contents are able to be altered from outside the electronic module through a diagnostic data communication link. Such alteration could potentially damage a vehicle's electronics or other components, placing at risk its compliance with government legislation or the vehicle manufacturer's interests in respect of security.

ISO 14229-6:2013 specifies the implementation of a common set of unified diagnostic services (UDS) on K-Line (UART based) in road vehicles (UDSonK-Line). UDSonK-Line references ISO 14229 1 and ISO 14229 2, and specifies implementation requirements of the diagnostic services to be used for diagnostic communication over K-Line, the server memory programming for all in-vehicle servers connected to a K-Line network with external test equipment. UDSonK-Line does not specify any requirement for the in-vehicle K-Line bus architecture. ISO 14229-6:2013 makes reference to information contained in ISO 14229 1, ISO 14229 2, ISO 14230 1, and ISO 14230 2. ISO 14229-6:2013 does not include any redundant information of the above-mentioned documents. It focuses on additional requirements specific to the implementation of UDSonK-Line network, and specific restrictions in the implementation of UDSonK-Line network.

ISO 14229-4:2012 specifies the implementation of a common set of unified diagnostic services (UDS) on FlexRay networks (FR) in road vehicles (UDSonFR). UDSonFR references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the diagnostic services to be used for diagnostic communication over FlexRay. UDSonFR does not specify any requirements of the in-vehicle FlexRay architecture. ISO 14229-4:2012 focuses on additional requirements specific to the implementation of UDS on the FlexRay network, and specific restrictions in the implementation of UDS on the FlexRay network.

ISO 27145-3:2012 defines the implementation of a subset of unified diagnostic services (UDS) specified in ISO 14229-1. The diagnostic services are used to communicate the diagnostic data defined in ISO 27145-2. The subset of unified diagnostic services derives from the requirements stated in the World-Wide Harmonized On-Board Diagnostic Global Technical Regulations (WWH-OBD GTR). The common message set defined in ISO 27145-3:2012 is independent of the underlying transport, network, data link and physical layer. ISO 27145-3:2012 does not specify any requirements for the in-vehicle network architecture. ISO 27145-3:2012 is compatible with ISO 14229-1 and includes provisions to support the data set of SAE J1979-DA and SAE J2012-DA WWH-OBD. ISO 27145-3:2012 is intended for use with ISO 27145-4, which is the entry point for the protocol initialization and is based on two different data links: · Diagnostic communication over Controller Area Network (DoCAN), ISO 15765‑1, ISO 15765‑2, ISO 15765‑4; · Diagnostic communication over Internet Protocol (DoIP), ISO 13400 (all parts). ISO 27145-3:2012 includes capabilities required to satisfy OBD regulations for multiple regions, vehicle types, model years, and engine types. Those regulations are not yet final for some regions and are expected to change in the future. ISO 27145-3:2012 does not attempt to interpret the regulations and does not include applicability of the included diagnostic services and data parameters for various vehicle applications. It is intended that users of ISO 27145-3:2012 verify the applicability of each of its clauses for a specific vehicle, engine, model year and region.

ISO 27145-2:2012 defines all regulatory data elements of the ISO 27145 series. The data elements are used to provide the external test equipment with the diagnostic status of the vehicle on-board diagnostics (VOBD) system in the vehicle. All data elements are communicated with the unified diagnostic services as defined in ISO 27145-3. The data elements are diagnostic trouble codes (DTCs), data identifiers (DIDs) and routine identifiers (RIDs). The mapping from parameter identifiers (PIDs), monitor identifiers (MIDs) and info type identifiers (ITIDs) is described in ISO 27145-2:2012. If new legislated WWH-OBD GTR modules are established, it is intended that ISO 27145 be applicable with possible extensions, which can be included in ISO 27145-2:2012, can be specified as enhancements of the SAE Digital Annexes or can even be part of other referenced documents which are intended to include the applicable data definitions. ISO 27145 is intended to become the single communication standard for access to OBD-related information (VOBD). To allow for a smooth migration from the existing communication standards to this future world-wide communication standard, the communication concept as specified in ISO 27145-4 is based on two different data links: ISO 15765-4 and ISO 13400 (all parts).

This part of ISO 27145 provides an overview of the structure and the partitioning of the different parts of ISO 27145 and shows the relationship between the parts. In addition, it outlines the use case scenarios where the ISO 27145 series is used. All terminology that is common throughout the ISO 27145 series is also outlined. ISO 27145 is intended to become the single communication standard for access to OBD-related information. To allow for a smooth migration from the existing communication standards to this future world-wide communication standard, the initial communication concept is based on the ISO 15765 series, i.e. Diagnostic communication over Control Area Network (DoCAN). The intention is for the future communication concept to be based on the ISO 13400 series, i.e. Diagnostic communication over Internet Protocol (DoIP) utilizing Ethernet. In view of the usage of standard network layer protocols, future extensions to optional physical layers (e.g. wireless) are possible. ISO 27145 has been extended to define the world-wide harmonized On-Board Diagnostics (OBD) communication standard. Based on the results of the initialization, the external test equipment determines which protocol and diagnostic services are supported by the vehicle's emissions-related system, i.e. — legislated OBD: ISO 15031 series (based on DoCAN), and — legislated WWH-OBD: ISO 27145 series (based on DoCAN and DoIP). IMPORTANT — Use cases deriving from country-specific implementation of Global

ISO 14230-1:2012 specifies the physical layer, based on ISO 9141, on which the diagnostic services will be implemented. It is based on the physical layer described in ISO 9141-2, but expanded to allow for road vehicles with either 12 V d.c. or 24 V d.c. voltage supply.

ISO 15031-1:2010 gives an overview of the structure and the partitioning of ISO 15031 (Road vehicles — Communication between vehicle and external test equipment for emissions-related diagnostics), and shows the relation between the different parts. It also defines the corresponding SAE recommended practices and reference to the SAE Digital Annexes. The terminology defined in ISO 15031-1:2010 is common for all parts of ISO 15031. ISO 15031-1:2010 also describes the use cases applicable to the communication between vehicle and external test equipment for emissions-related diagnostics.

ISO 15031-2:2010 provides guidance on the usage of terms, definitions, abbreviations and acronyms used in emissions-related diagnostics, with respect to the communication between road vehicles and external equipment used in that field. It also specifies a procedure for constructing new terms. As it gives recommended usage of diagnostic terms applicable to electrical/electronic systems, it also makes reference to related mechanical terms, definitions, abbreviations and acronyms. ISO 15031-2:2010 is applicable to all light-duty gasoline and diesel passenger vehicles and trucks, and to heavy-duty gasoline vehicles. Specific applications of this document include diagnostic, service and repair manuals, bulletins and updates, training manuals, repair databases, underhood emission labels and emission certification applications. ISO 15031-2:2010 is intended to help industry provide standard terms, definitions, abbreviations and acronyms with a view to establishing a common terminology for diagnostic tools and publications.

This part of ISO 14230 specifies the requirements for the Keyword Protocol 2000 (KWP 2000) data link and connected vehicle and scan tool when used to comply with on-board diagnostic (OBD) requirements for emission-related test data. This part of ISO 14230 only specifies requirements relative to the Keyword Protocol 2000 for OBD purposes. Complete specification can be found in ISO 14230 parts 1 to 3 and in ISO 14229. ISO 14230-1, ISO 14230-2 and ISO 14230-3 are applicable for OBD purposes only as explicitly referenced in this part of ISO 14230.

This part of ISO 14230 specifies the requirements for the Keyword Protocol 2000 data link on which one or several on-vehicle Electronic Control Units are connected to an off-board tester in order to perform diagnostic functions. This part of ISO 14230 specifies the requirements of the implementation of the Diagnostic Services specified in ISO 14229, including - byte-encoding and hexadecimal values for the service identifiers; - byte-encoding for the parameters of the diagnostic service requests and responses; - hexadecimal values for the standard parameters. The vehicle environment to which this part of ISO 14230 applies may consist of a single tester that may be temporarily connected to the on-vehicle diagnostic data link and several on-vehicle Electronic Control Units connected directly or indirectly.

This part of ISO 9141 establishes recommended test methods, test procedures and specific test parameters in order to verify a vehicle or OBD II scan tool can communicate on a bus according to ISO 9141-2. It is not applicable as a test for a single module or for any subpart of an ISO 9141-2 network. The test described is not provided to verify any tool or vehicle requirement not described in ISO 9141-2. In particular it does not check any requirement described in SAE J1962, SAE J1978, ISO 15031-5 or the expanded diagnostic protocol for scan tool. The procedures and methods test a set of specific requirements applicable to all road vehicles and scan tools which make use of ISO 9141-2.

Contains minor amendments in three subclauses.

Is limited to vehicles with nominal 12 V supply voltage. Describes a subset of ISO 9141:1989. Specifies the requirements for setting-up the interchange of digital information between on-board emission-related electronic control units of road vehicles and the SAE OBD II scan tool as specified in SAE J1978. This communication is established to facilitate compliance with California Code of Regulation, Title 13, 1968.1.

Specifies the requirements for setting up the interchange of digital information between on-board Electronic Control Units (ECUs) of road vehicles and suitable diagnostic testers. This communication is established in order to facilitate inspection, test diagnosis and adjustment of vehicles, systems and ECUs. Does not apply when system-specific diagnostic test equipment is used.

ISO 15765-4:2016 specifies requirements for Controller Area Networks (CAN) where one or more controllers comply with on-board diagnostics (OBD) or world-wide harmonized on-board diagnostics (WWH‑OBD) regulations. The network presumes the use of an external test equipment for inspection and repair diagnostics, as defined by the regulations. The CAN network requirements for the vehicle and the external test equipment are based on the specifications of ISO 15765-2, ISO 11898-1 and ISO 11898-2. ISO 15765-4:2016 places restrictions on those International Standards for the fulfilment of the regulations. It does not specify in-vehicle CAN bus architecture, but seeks to ensure that the vehicle's regulated CAN communications comply with external test equipment requirements. ISO 15765-4:2016 defines the requirements to successfully establish, maintain and terminate communication with a vehicle that implements the requirements of the OBD/WWH-OBD regulations. Plug‑and-play communication capabilities among vehicles and test equipment are defined to assure the interoperation of external test equipment and vehicles. This part of ISO 15765 details all of the OSI layer requirements to achieve this goal. ISO 15765-4:2016 is the entry point for DoCAN (Diagnostic communication over Controller Area Network). Based on the results of the initialization, the external test equipment determines which protocol and diagnostic services are supported by the vehicle's emissions-related system: - legislated OBD: ISO 15031 (all parts); - legislated WWH-OBD: ISO 27145 (all parts).

ISO 15031-3:2016 references the latest publication of SAE J1962. On-board diagnostic (OBD) regulations require road vehicles to be equipped with a standardized connector for purposes of access to OBD information by ISO 15031‑4 compliant external test equipment. This part of ISO 15031 describes the requirements for the physical connection and associated pin usage to allow for standard access to the OBD data. The first edition of this part of ISO 15031 was based on SAE J1962 and was intended to meet European OBD requirements for 2000 and later model year vehicles, and added a modified connector type to accommodate vehicles with a 24 V system. This revised part of ISO 15031 is technically equivalent to SAE J1962 with the exception of the specific requirements identified in the document. ISO 15031-3:2016 specifies additional requirements related to right hand driven (RHD) vehicles. Annex A and Annex B are for information and not required to fulfil emissions-related OBD.

ISO 14229-7:2015 specifies the implementation of a common set of unified diagnostic services (UDS) on UART-based local interconnect networks in road vehicles. The UDSonLIN diagnostics defines methods to implement diagnostic data transfer between a client and the LIN slave nodes through the LIN master node. LIN slave nodes support three different diagnostic classes as defined in ISO 17987. UDSonLIN references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the following: - diagnostic services to be used for diagnostic communication over LIN, - server memory programming for in-vehicle LIN servers with an external test equipment, and - configuration of a LIN slave node as specified in ISO 17987.

ISO 14229-5:2013 references ISO 14229-1 and ISO 14229-2 and specifies the implementation requirements of a common set of unified diagnostic services (UDS) on Internet Protocol (UDSonIP). ISO 14229-5:2013 does not include any redundant information of the documents as listed in the introduction. It focuses on additional requirements specific to the implementation of UDSonIP, and specific restrictions in the implementation of UDSonIP.

ISO 14230-2:2013 specifies data link layer services tailored to meet the requirements of UART-based vehicle communication systems on K-Line as specified in ISO 14230-1. It has been defined in accordance with the diagnostic services established in ISO 14229-1 and ISO 15031-5, but is not limited to use with them, and is also compatible with most other communication needs for in-vehicle networks. The protocol specifies an unconfirmed communication. The diagnostic communication over K-Line (DoK-Line) protocol supports the standardized service primitive interface as specified in ISO 14229-2. ISO 14230-2:2013 provides the data link layer services to support different application layer implementations like: enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics); emissions-related OBD as specified in ISO 15031, SAE J1979-DA, and SAE J2012-DA. In addition, ISO 14230-2:2013 clarifies the differences in initialization for K-line protocols defined in ISO 9141 and ISO 14230. This is important since a server supports only one of the protocols mentioned above and the client has to handle the coexistence of all protocols during the protocol-determination procedure.

ISO 14229-1:2013 specifies data link independent requirements of diagnostic services, which allow a diagnostic tester (client) to control diagnostic functions in an on-vehicle Electronic Control Unit (ECU, server) such as an electronic fuel injection, automatic gear box, anti-lock braking system, etc. connected to a serial data link embedded in a road vehicle. It specifies generic services, which allow the diagnostic tester (client) to stop or to resume non-diagnostic message transmission on the data link. ISO 14229-1:2013 does not apply to non-diagnostic message transmission on the vehicle's communication data link between two ECUs. However, it does not restrict an in-vehicle on-board tester (client) implementation in an ECU in order to utilize the diagnostic services on the vehicle's communication data link to perform bidirectional diagnostic data exchange. ISO 14229-1:2013 does not specify any implementation requirements.

ISO 14229-2:2013 specifies data link independent requirements of session layer services. ISO 14229-2:2013 specifies common session layer services to provide independence between unified diagnostic services (ISO 14229-1) and all transport protocols and network layer services (e.g. ISO 15765-2 DoCAN, ISO 10681-2 communication on FlexRay, ISO 13400 DoIP, ISO 14230-2 DoK-Line, etc.) ISO 14229-2:2013 specifies a common service primitive interface between OSI layer 4 (Transport) and layer 5 (Session) via so-called service request/confirmation/indication primitives. This interface allows seamless implementation of ISO 14229-1 unified diagnostic services (UDS) with any communication protocol titled "DoXYZ / CoXYZ" like ISO 15765 DoCAN - diagnostic communication over Controller Area Network, ISO 13400 DoIP, ISO 10681 communication over FlexRay, ISO 14230 DoK-Line. ISO 15031 (emissions-related OBD) and ISO 27145 (WWH-OBD) support the standardized service primitive interface.

ISO 14229-3:2012 specifies the implementation of a common set of unified diagnostic services (UDS) on controller area networks (CAN) in road vehicles (UDSonCAN). It references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the diagnostic services to be used for diagnostic communication over CAN. It does not specify any requirement for the in-vehicle CAN bus architecture.

ISO 27145-4:2012 defines the requirements to successfully establish, maintain and terminate communication with a vehicle that implements the requirements of the World-Wide Harmonized On-Board Diagnostic Global Technical Regulations (Global technical regulation No. 5). This requires plug and play communication capabilities for the vehicle as well as for any test equipment that intends to establish communication with a vehicle. ISO 27145-4:2012 details all the OSI layer requirements to achieve this goal. ISO 27145-4:2012 is intended to become the single communication standard for access to information relating to vehicle on‑board diagnostics (VOBD). To allow for a smooth migration from the existing communication standards to this future world-wide standardized communication standard, the communication concept as specified in ISO 27145-4:2012 is based on two different data links: · Diagnostic communication over Controller Area Network (DoCAN), ISO 15765-4; · Diagnostic communication over Internet Protocol (DoIP), ISO 13400 (all parts). Use cases deriving from country-specific implementation of Global Technical Regulation No. 5 into local legislation are not included in ISO 27145-4:2012.

ISO 13400-2:2012 specifies the requirements for diagnostic communication between external test equipment and vehicle electronic components using Internet Protocol (IP) as well as the transmission control protocol (TCP) and user datagram protocol (UDP). This includes the definition of vehicle gateway requirements (e.g. for integration into an existing computer network) and test equipment requirements (e.g. to detect and establish communication with a vehicle). ISO 13400-2:2012 specifies features that can be used to detect a vehicle in a network and enable communication with the vehicle gateway as well as with its sub-components during the various vehicle states. These features are separated into two types: mandatory and optional. ISO 13400-2:2012 specifies the following mandatory features: vehicle network integration (IP address assignment); vehicle announcement and vehicle discovery; vehicle basic status information retrieval (e.g. diagnostic power mode); connection establishment (e.g. concurrent communication attempts), connection maintenance and vehicle gateway control; data routing to and from the vehicle's sub-components; error handling (e.g. physical network disconnect). ISO 13400-2:2012 specifies the following optional features: DoIP entity status monitoring; DoIP entity firewall capabilities.

ISO 13400-1:2011 describes the general use cases and communication scenarios which are covered by an Internet Protocol-based vehicle communication standard. Each use case drives specific communication capabilities of the vehicle communication interface, for instance in order to be interoperable in an existing computer network. The diagnostic communication over Internet Protocol (DoIP) protocol supports the standardized service primitive interface as specified in ISO 14229-2. The descriptions in ISO 13400-1:2011 cover different application layer implementations, such as: enhanced vehicle diagnostics (system diagnostics beyond legislated functionality, non-emissions-related system diagnostics); WWH-OBD (World-Wide Harmonized On-Board Diagnostics) as specified in ISO 27145-2 and ISO 27145-3.

ISO 15765-1:2011 gives an overview of the structure and the partitioning of ISO 15765, and shows the relationships between the different parts. It also defines the diagnostic network architecture. The terminology defined in this part is common for all diagnostic networks and is used throughout all parts of ISO 15765. The diagnostic communication over controller area network (DoCAN) protocol supports the standardized service primitive interface as specified in ISO 14229‑2.

ISO 15031-5:2011 is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future. ISO 15031-5:2011 specifies: - message formats for request and response messages, - timing requirements between request messages from external test equipment and response messages from vehicles, and between those messages and subsequent request messages, - behaviour of both the vehicle and external test equipment if data is not available, - a set of diagnostic services, with corresponding content of request and response messages, to satisfy OBD regulations. ISO 15031-5:2011 includes capabilities required to satisfy OBD requirements for multiple regions, model years, engine types, and vehicle types. Those regulations are not yet final for some regions, and are expected to change in the future. ISO 15031-5:2011 makes no attempt to interpret the regulations and does not include applicability of the included diagnostic services and data parameters for various vehicle applications. The user of ISO 15031-5:2011 is responsible for verifying the applicability of each clause of ISO 15031-5:2011 for a specific vehicle, engine, model year and region. ISO 15031-5:2011 specifies diagnostic services and functionally addressed request/response messages required to be supported by motor vehicles and external test equipment for diagnostic purposes which pertain to motor vehicle emission-related data. Any external test equipment meeting the requirements of ISO 15031-4 use these messages to retrieve emissions-related information from the vehicle. Each clause in ISO 15031-5:2011 which specifies additional details to existing sections of ISO 9141-2, ISO 14230-4, SAE J1850, and ISO 15765-4 supersede those specifications. ISO 15031-5:2011 references SAE J1979-DA (Digital Annex), which includes all definitions of PIDs, OBDMIDs, TIDs and INFOTYPES. ISO 15031-5:2011 provides the mechanism to satisfy the requirements included in the country-specific regulations and not all capabilities included in ISO 15031-5:2011 are required by the country-specific regulations. ISO 15031-5:2011 is not considered a final authority for interpretation of the regulations. Therefore readers should determine the applicability of capabilities defined in ISO 15031-5:2011 for their own specific needs.

ISO 15765-4:2011 specifies requirements for controller area networks (CAN) where one or more controllers comply with on-board diagnostics (OBD) or world-wide harmonized on-board diagnostics (WWH-OBD) regulations. The network presumes the use of an external test equipment for inspection and repair diagnostics, as defined by the regulations. The CAN network requirements for the vehicle and the external test equipment are based on the specifications of ISO 15765-2, ISO 11898-1 and ISO 11898-2. ISO 15765-4:2011 places restrictions on those International Standards for the fulfilment of the regulations. It does not specify in-vehicle CAN bus architecture, but seeks to ensure that the vehicle's regulated CAN communications comply with external test equipment requirements. ISO 15765-4:2011 defines the requirements to successfully establish, maintain and terminate communication with a vehicle that implements the requirements of the OBD/WWH-OBD regulations. Plug-and-play communication capabilities among vehicles and test equipment are defined to assure the interoperation of external test equipment and vehicles. ISO 15765-4:2011 details all of the OSI layer requirements to achieve this goal. ISO 15765-4:2011 is the entry point for DoCAN (Diagnostic communication over CAN). Based on the results of the initialization, the external test equipment determines which protocol and diagnostic services are supported by the vehicle's emissions-related system: legislated OBD: ISO 15031 (all parts), legislated WWH-OBD: ISO 27145 (all parts).