ISO/TC 22/SC 31 - Data communication

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 communication interface between motion sensor and recording equipment. This includes the mechanical, electrical and logical 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 communication between the electric vehicle (EV), including battery electric vehicle (BEV) and plug-in hybrid electric vehicle (PHEV), and the electric vehicle supply equipment (EVSE). The application layer messages defined in this document are designed to support the electricity power transfer between an EV and an EVSE. This document defines the communication messages and sequence requirements for bidirectional power transfer. This document furthermore defines requirements of wireless communication for both conductive charging and wireless charging as well as communication requirements for automatic connection device and information services about charging and control status. The purpose of this document is to detail the communication between an electric vehicle communication controller (EVCC) and a supply equipment communication controller (SECC). Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between the EVCC and the SECC.

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 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 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 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 in-vehicle Ethernet application layer, presentation layer, and session layer conformance test plans (CTP) for electronic control units (ECUs). This document is a collection of all conformance test cases which are recommended to be considered for automotive use and should be referred by car manufacturers within their quality control processes. The document specifies the scalable Service-Oriented MiddlewarE over Internet Protocol (SOME/IP) and Dynamic Host Configuration Protocol (DHCP) version 4 conformance test cases.

This document defines how to access resources on a web-services interface of an offering party using the Hypertext Transfer Protocol Secure (HTTPS). Resources can be accessed through request/reply and/or requested to be pushed. The Representational State Transfer (REST) architectural pattern is chosen as a common way to format resource paths both for request/reply and push. Some specific extensions to this pattern are defined to allow for asynchronous resource requests, such as, for example, forcing readouts of data from a connected vehicle.

This document states the minimum requirements, recommendations, permissions and possibilities for ensuring interoperable web services from an accessing party’s perspective. The document: — states requirements on the structure and format of resources; — defines the concept of resource identifiers (direct and correlated); — provides different resource categories (e.g. anonymous, pseudonymized, technical, and personal resources); — provides different approaches on how to bundle shareable resources (e.g. resource group or container); — contains guidelines on how to define the unique resources of an individual application; — defines the entities and roles, necessary for granting an accessing party access to resource owner’s resources; — states requirements on how an accessing party accesses resources, including requirements on how to use the defined and referenced technologies, see Table 1. See Annex A for additional information about roles and responsibilities covered by ISO 20078 series.

This document defines how to authenticate users and accessing parties on a web-services interface. It also defines how a resource owner can delegate access to its resources to an accessing party. Within this context, this document also defines the necessary roles and required separation of duties between these in order to fulfil requirements stated on security, data privacy and data protection. All conditions and dependencies of the roles are defined towards a reference implementation using OAuth 2.0 compatible framework and OpenID Connect 1.0 compatible framework.

This document specifies advanced features of an ISO/IEC/IEEE 8802-3 automotive Ethernet PHY (often also called transceiver), e.g. for diagnostic purposes for automotive Ethernet PHYs. This document specifies: — advanced PHY features; — wake-up and sleep features; — PHY test suite; — PHY control IUT requirements and conformance test plan; — PCS test suite; — PCS IUT requirements and conformance test plan; — PMA test suite; and — PMA IUT requirements and conformance test plan.

This document specifies in-vehicle Ethernet transport layer and network layer conformance test plans (CTP) for electronic control units (ECUs). This document is a collection of all conformance test cases which are recommended to be considered for automotive use and should be referred by car manufacturers within their quality control processes. The document includes conformance test plans for the address resolution protocol, Internet control message protocol version 4, Internet protocol version 4, Internet protocol version 4 auto configuration, user datagram protocol, transport control protocol, and dynamic host configuration protocol version 4.

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 ePTI-relevant system identifiers, data identifiers, routine identifiers, input/output control identifiers, data types, CompuMethods (computations), and units. This document describes ePTI systems' data definitions and associated technical requirements. The technical requirements of data definitions of emissions-related systems are specified in other standards, e.g. the ISO 15031 series[4], the ISO 27145 series[5], and SAE J1979DA. The ePTI system list defined in this document summarizes ePTI-relevant systems and specifies a defined name (system), a unique identifier (ePTI system identifier) and a description for each ePTI-relevant system. This document does not specify any type of test method or pass/fail criteria of the ePTI-relevant system during a PTI.

This document describes the processes of an offering party’s implementation to provide (ISO 20078‑2) access-controlled (ISO 20078-3) resources (ISO 20078‑1) to accessing parties. The processes are summarized as: registration of different stakeholder as well as granting, denying and revoking of access to resources. Those processes are held as examples of combining ISO 20078‑1, ISO 20078‑2 and ISO 20078‑3 and can vary depending on the actual implementation of the offering party.

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 a conformance test for a vehicle manufacturer assessment of self-conformance of the VM RMI system. The conformance test cases follow the use case definition of ISO 18541‑1 and the requirements stated in ISO 18541‑2 and ISO 18541‑3. The primary, but not exclusive, purpose of this document is to provide information to the VM RMI system provider to build and test the VM RMI system against the conformance test cases. This final step in the development process of the VM RMI system is an enabler for all providers that their VM RMI system meets a high degree of functional requirements expected by the end user. Furthermore, this document defines in Annex A conformance test cases for the use cases and requirements versions that apply for granting access to security-related RMI following the SERMI scheme. This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [9].

This document includes technical requirements which are related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators. This document specifies the minimum set of technical requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1. Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme. This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [15].

This document includes functional user interface requirements related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators. This document specifies all functional user interface requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1.

This document provides a general overview and structure of each part of the ISO 18541 series. This document also describes the use cases applicable to the standardized access to automotive RMI. The use cases address real world scenarios (e.g. servicing vehicles) regarding the information access necessary to perform vehicle roadside assistance, inspection, diagnosis, repair and maintenance, including the updating and replacement of electronic control units (ECU). Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme. The RMI systems used by personnel to perform the services consist of: — a web-based system, which provides access to RMI needed to perform the service(s); — contact information for specific RMI; — a security framework to protect access to security-related RMI (vehicle theft protection measures). This document is applicable to light passenger vehicles and light commercial vehicles.

This document, as the first document in the ISO 23239 series, provides a basic definition of vehicle domain service and supplementary information on detailed concepts, as well as definitions of the typical and supplementary use cases being used to define the specification of applications. Detailed specifications of communications and applications are provided in other documents in the ISO 23239 series, and they are not provided in this document. NOTE The remote processes by the tools connected to the on-board diagnosis (OBD) connector in a vehicle, such as repair and maintenance, prognostics, monitoring, configuration and reprogramming of vehicle are out of the scope of this document.

This document specifies the 150-Mbit/s coaxial physical layer for MOST (MOST150 cPHY), a synchronous time-division-multiplexing network. This document specifies the applicable constraints and defines interfaces and parameters, suitable for the development of products based on MOST150 cPHY. Such products include coaxial links, coaxial receivers, coaxial transmitters, electrical to coaxial converters, and coaxial to electrical converters. This document also establishes basic measurement techniques and actual parameter values for MOST150 cPHY.

This document specifies the conformance test plan for the 150-Mbit/s coaxial physical layer for MOST (MOST150 cPHY), a synchronous time-division-multiplexing network. This document specifies the basic conformance test measurement methods, relevant for verifying compatibility of networks, nodes, and MOST components with the requirements specified in ISO 21806‑10.

This document specifies the conformance test plan for the 50-Mbit/s balanced media physical layer for MOST (MOST50 bPHY), a synchronous time-division-multiplexing network. This document specifies the basic conformance test measurement methods, relevant for verifying compatibility of networks, nodes, and MOST components with the requirements specified in ISO 21806-12.

This document specifies the 50-Mbit/s balanced media physical layer for MOST (MOST50 bPHY), a synchronous time-division-multiplexing network. This document specifies the applicable constraints and defines interfaces and parameters, suitable for the development of products based on MOST50 bPHY. Such products include electrical interconnects, integrated receivers, transmitters, electrical to balanced media converters, and balanced media to electrical converters. This document also establishes basic measurement techniques and actual parameter values for MOST50 bPHY.

This document specifies the conformance test plan (CTP) for the lean application layer for MOST, a synchronous time-division-multiplexing network, as specified in ISO 21806-14. This document specifies conformance test cases (CTCs) for root nodes and remote nodes in the following categories: — network startup; — network shutdown; — network events; — node discovery; — connection management. Interoperability testing is not in the scope of this document.

This document specifies the technical requirements for the lean application layer for MOST, a synchronous time-division-multiplexing network. The lean application layer includes a specification of the services available to control the configuration and behaviour of the network management. The lean application layer covers the definition of: — node kinds, — node addressing, — data transport, — network configuration, — lean network services interface, — network management, including connection management, — diagnosis, and — timing definitions.

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available. This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

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 defines the Open Test sequence eXchange (OTX) additional extension requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in Clause 4. The data model specification aims at an exhaustive definition of all features of the OTX extensions which have been implemented to satisfy the requirements. This document establishes rules for the syntactical entities of each extension. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents containing extension features are to be interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions.

This document is applicable to road vehicles, where the electronic vehicle interface is used to perform a test method that is part of a periodic technical inspection (ePTI). This document describes use cases and specifies technical requirements in order to support the ePTI-relevant vehicle safety system(s) checks during the periodic technical inspection via the electronic interface. This document references the ISO 14229 series, the unified diagnostic services implemented on diagnostic communication over controller area network (DoCAN) and the Internet protocol (DoIP) along with the required provision of data definitions. The technical requirements of diagnostic services and data definitions of emissions-related systems are specified in other International Standards, for example, ISO 15031 and ISO 27145. Other environmental systems' ePTI use cases and technical requirements can be considered in the future. This document defines: — all requirements describing the vehicle-communication functionality via the diagnostic link connector related to ePTI, for example: 1) discovery of the ePTI data link; 2) discovery of the ePTI-relevant systems; 3) query of ePTI-relevant systems’ information, including software identification, software integrity, current and/or stored values; 4) query of ePTI-relevant systems’ error information; 5) activation of ePTI-relevant systems’ actuators or routines; — the use cases about the individual vehicle communication functionality, for example, query identification information, command functional test method. This document does not directly specify any type of test method or pass/fail criteria of the ePTI-relevant system during a PTI, but provides data, which may support PTI test methods. The document specifies: — terminology; — communication establishment between the ePTI external test equipment and the vehicle's ePTI-relevant systems; — usage of a credentials-based authentication and authorisation mechanism between the ePTI external test equipment and the vehicle; — protection against tampering of the defined ePTI methods; — definition of ePTI-relevant use cases: — ePTI external test equipment discovers available data identifier as specified in ISO 20730-3; — ePTI external test equipment queries the ePTI-relevant system’s information, including software numbers, software integrity information, current and/or stored values, self-test completion status, system status, and error information (e.g. DTC and/or DID information); — ePTI external test equipment activates the ePTI-relevant system’s actuators or routines; — definition of ePTI-relevant technical requirements; — ePTI external test equipment minimum requirements. This document excludes: — process definitions for performing the PTI check; — process and data definitions for off-board data provision; — standardised data exchange formats; — validation and verification of vehicle safety systems according to vehicle manufacturer specifications.

This document specifies the conformance test plan for ISO 20794-2:2020 implementations. It specifies conformance test cases related to: — concept of operation; — network management; — transfer management; and — error management.

This document specifies the conformance test plans for the CXPI data link layer and the CXPI physical layer. It also specifies the conformance test plan for error detection. Additionally, this document describes the concept of conformance test plan operation.

This document specifies the following items to complement ISO/IEC /IEEE 8802‑3: — interface between reconciliation sublayer and physical entity including reduced gigabit media independent interface (RGMII); — common physical entity wake-up and synchronised link sleep functionalities independent from physical media and transmission bit rate. The optical and electrical component requirements and test methods for optical and electrical transmission of in-vehicle Ethernet are not in the scope of this document.

This document specifies the 150-Mbit/s optical physical layer for MOST (MOST150 oPHY), a synchronous time-division-multiplexing network. This document specifies the applicable constraints and defines interfaces and parameters, suitable for the development of products based on MOST150 oPHY. Such products include fibre optical links and connectors, fibre optic receivers, fibre optic transmitters, electrical to optical converters, and optical to electrical converters. This document also establishes basic measurement techniques and actual parameter values for MOST150 oPHY.

This document defines the terms which are used in the ISO 21111 series and provides an overview of the standards for in-vehicle Ethernet including the complementary relations to ISO/IEC/IEEE 8802‑3:2017[7] and its amendments, the document structure in accordance with OSI reference model specified in ISO/IEC 7498‑1[1] and ISO/IEC 10731:1994,[2] type of physical entities, in-vehicle Ethernet specific functionalities, and so on.

This document specifies the conformance test plan for the 150-Mbit/s optical physical layer for MOST (MOST150 oPHY), a synchronous time-division-multiplexing network. This document specifies the basic conformance test measurement methods, relevant for verifying compatibility of networks, nodes, and MOST components with the requirements specified in ISO 21806-8[eXtyles1] . [eXtyles1]ISO 21806-8: current stage is 50.00

This document specifies the conformance test plan (CTP) for the application layer for MOST, a synchronous time-division-multiplexing network, as specified in ISO 21806-2. This document specifies conformance test cases (CTCs) in the following categories: — device model; — data and basic data types; — registry management; — connection management; — error management; — diagnosis. Interoperability testing is not in the scope of this document.

This document specifies the transport and network layer conformance test plan, which tests the transportation of diagnostic communication, node configuration data and network layer services using the service interface parameters reported by the lower OSI layers and submitted to the higher OSI layers. The transport layer and network layer conformance test plan contain the following descriptions: — concept of operation conformance test plan; — transport layer protocol conformance test plan; — network layer services conformance test plan; and — error detection conformance test plan.

This document specifies the requirements of the physical and data link layer of a wireless High Level Communication (HLC) between Electric Vehicles (EV) and the Electric Vehicle Supply Equipment (EVSE). The wireless communication technology is used as an alternative to the wired communication technology as defined in ISO 15118‑3. It covers the overall information exchange between all actors involved in the electrical energy exchange. ISO 15118 (all parts) are applicable for conductive charging as well as Wireless Power Transfer (WPT). For conductive charging, only EVSEs compliant with "IEC 61851‑1 modes 3 and 4" and supporting HLC are covered by this document. For WPT, charging sites according to IEC 61980 (all parts) and vehicles according to ISO 19363 are covered by this document.

This document specifies the conformance test plan (CTP) for the data link layer for MOST, a synchronous time-division-multiplexing network, as specified in ISO 21806-6. This document specifies conformance test cases (CTCs) in the following categories: — network frames; — allocation channel; — protected system channel; — timestamp channel; — flow control; — cyclic redundancy check; — arbitration; — default packet channel. Interoperability testing is not in the scope of this document.