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].

  • Standard
    76 pages
    English language
    sale 15% off
  • Standard
    78 pages
    French language
    sale 15% off
  • Draft
    75 pages
    English language
    sale 15% off
  • Draft
    79 pages
    French language
    sale 15% off

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].

  • Standard
    32 pages
    English language
    sale 15% off
  • Standard
    36 pages
    French language
    sale 15% off
  • Draft
    32 pages
    English language
    sale 15% off
  • Draft
    36 pages
    French language
    sale 15% off

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.

  • Standard
    13 pages
    English language
    sale 15% off
  • Standard
    13 pages
    French language
    sale 15% off
  • Draft
    13 pages
    English language
    sale 15% off
  • Draft
    13 pages
    French language
    sale 15% off

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.

  • Standard
    40 pages
    English language
    sale 15% off
  • Standard
    44 pages
    French language
    sale 15% off
  • Draft
    41 pages
    English language
    sale 15% off
  • Draft
    45 pages
    French language
    sale 15% off

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.

  • Standard
    54 pages
    English language
    sale 15% off
  • Draft
    54 pages
    English language
    sale 15% off

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.

  • Standard
    84 pages
    English language
    sale 15% off
  • Draft
    84 pages
    English language
    sale 15% off

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.

  • Standard
    49 pages
    English language
    sale 15% off
  • Draft
    49 pages
    English language
    sale 15% off

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.

  • Standard
    57 pages
    English language
    sale 15% off
  • Draft
    58 pages
    English language
    sale 15% off

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.

  • Standard
    34 pages
    English language
    sale 15% off
  • Draft
    34 pages
    English language
    sale 15% off

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.

  • Standard
    19 pages
    English language
    sale 15% off
  • Draft
    19 pages
    English language
    sale 15% off

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.

  • Standard
    227 pages
    English language
    sale 15% off
  • Draft
    226 pages
    English language
    sale 15% off

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.

  • Standard
    55 pages
    English language
    sale 15% off
  • Draft
    55 pages
    English language
    sale 15% off

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.

  • Standard
    49 pages
    English language
    sale 15% off
  • Draft
    49 pages
    English language
    sale 15% off

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.

  • Standard
    379 pages
    English language
    sale 15% off
  • Draft
    379 pages
    English language
    sale 15% off

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.

  • Standard
    133 pages
    English language
    sale 15% off
  • Draft
    133 pages
    English language
    sale 15% off

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.

  • Standard
    42 pages
    English language
    sale 15% off

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.

  • Standard
    132 pages
    English language
    sale 15% off
  • Draft
    132 pages
    English language
    sale 15% off

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.

  • Standard
    51 pages
    English language
    sale 15% off
  • Draft
    51 pages
    English language
    sale 15% off

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

  • Standard
    68 pages
    English language
    sale 15% off
  • Draft
    68 pages
    English language
    sale 15% off

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.

  • Standard
    28 pages
    English language
    sale 15% off
  • Draft
    28 pages
    English language
    sale 15% off

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.

  • Standard
    47 pages
    English language
    sale 15% off
  • Draft
    46 pages
    English language
    sale 15% off

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.

  • Standard
    8 pages
    English language
    sale 15% off
  • Draft
    8 pages
    English language
    sale 15% off

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.

  • Standard
    96 pages
    English language
    sale 15% off
  • Draft
    96 pages
    English language
    sale 15% off

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.

  • Standard
    30 pages
    English language
    sale 15% off

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.

  • Standard
    33 pages
    English language
    sale 15% off
  • Standard
    35 pages
    French language
    sale 15% off
  • Draft
    33 pages
    English language
    sale 15% off

This document specifies a part of the application, the application layer, and the presentation layer. The application covers the — device model, — registry management, — connection management for streaming data, — diagnosis, and — error handling. The application layer covers the structure of MOST messages consisting of — addressing, — function block identifiers, — instance identifiers, — function identifiers, — operation types, and — timing definitions. The presentation layer covers the definition of data, basic data types and function classes.

  • Standard
    136 pages
    English language
    sale 15% off

This document specifies technical requirements related to the MOST transport layer and network layer functionality: — the service interface to application layer; — the network layer services; — the data transport mechanism; — the dynamic behaviour of a node; — the network error management.

  • Standard
    56 pages
    English language
    sale 15% off

This document specifies technical requirements related to the MOST data link layer functionality. A MOST network is comprised of two or more nodes connected through a physical layer. The data link layer functionality is provided by each node. On each network, all nodes are synchronised and one node provides the system clock. This node is the TimingMaster, while all other nodes are TimingSlaves. The timing configuration of the node (TimingMaster or TimingSlave) determines the tasks that need to be performed on the data link layer. The data link layer specifies the following subjects: — the service interface to the network layer; — the network frame, its areas and indicators; — the different network channels; — the different flow control mechanisms; — the load-adaptive arbitration and the round-robin arbitration; — the different addressing options; — the different cyclic redundancy checks, their usage and the CRC acknowledge; — the frame indicators.

  • Standard
    68 pages
    English language
    sale 15% off

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.

  • Standard
    23 pages
    English language
    sale 15% off

This document specifies the conformance test plan (CTP) for the transport layer and network layer for MOST, a synchronous time-division-multiplexing network, as specified in ISO 21806-4. This document specifies conformance test cases (CTCs) in the following categories: — network layer services; — data transport mechanism; — dynamic behaviour of a node. Interoperability testing is not in the scope of this document.

  • Standard
    31 pages
    English language
    sale 15% off

This document provides general information and definitions for Media Oriented Systems Transport (MOST), a synchronous time-division-multiplexing network. This document describes the access to MOST specifications, which are referenced by the ISO 21806 series.

  • Standard
    23 pages
    English language
    sale 15% off

This document defines the classification methodology of time-constrained situations and their requirements, that are to be addressed by the "ExVe time critical interfaces" described in ISO 20077‑1. Time-constrained situations include safety-critical situations. It is important for the design of the vehicle to have priority management of "ExVe time critical interface" resources in order to comply with time constrained situations requirements. The methodology provides a classification, which determines application priorities for optimal vehicle resource allocation.

  • Standard
    23 pages
    English language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 15% off

This document specifies: — requirements on the physical layer at system level, — requirements on the interoperability test set-ups, — interoperability test plan that checks the requirements for the physical layer at system level, — requirements on the device-level physical layer conformance test set-ups, and — device-level physical layer conformance test plan that checks a set of requirements for the OSI physical layer that are relevant for device vendors. The interoperability test plan checks the physical layer system requirements specified in this document and in ISO/IEC/IEEE 8802-3:2017/Amd 9. This test plan is structured in four different test groups, attending to the kind of system requirements that covers: — link status, that includes the tests that check the status of the link by using the content of the available registers and its accuracy with the real status of the link, — link-up, that includes the tests that check the time that the IUT reaches a reliable link status from certain state, — channel quality, that includes the tests that check the quality of the optical channel by using the content of the available registers and its accuracy with the real quality of the optical channel, and — wake-up and sleep, that include tests that check that the transmission and reception of the wake-up and sleep events. The device-level conformance test plan checks the device-level requirements specified in the ISO 21111 series and in ISO/IEC/IEEE 8802-3:2017/Amd 9. This test plan is structured in four different test groups, attending to the test set-up required: — high-attenuation channel, — low-attenuation channel, — optical IUT transmitter measurements, and — wake-up and synchronised link sleep.

  • Standard
    73 pages
    English language
    sale 15% off
  • Draft
    73 pages
    English language
    sale 15% off

This document provides supplemental specifications to a physical layer capable of transmitting 1 Gbit/s over plastic optical fibre compliant with ISO/IEC/IEEE 8802-3:2017/Amd 9:2018, with specific application to communications inside road vehicles. Additionally, there is a test plan specified for conformance testing. The test plan includes test cases to assure compliance of an IUT with the functionality specified in this document. ISO/IEC/IEEE 8802-3:2017/Amd 9:2018 is considered indispensable for the application of this document. The supplemental specifications include wake-up and synchronised link sleep functionality. The specification includes the sublayers, service interfaces, and state diagrams that support the functionality. The supplemental specifications are collected in protocol implementation conformance statement (PICS). The requirements specified in ISO/IEC/IEEE 8802-3:2017/Amd 9:2018 and in this document constitute the complete PICS that specifies the GEPOF physical entity functionality. The optical component requirements and test methods for optical 1-Gbit/s transmission of in-vehicle Ethernet are not within the scope of this document.

  • Standard
    186 pages
    English language
    sale 15% off
  • Draft
    186 pages
    English language
    sale 15% off

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.

  • Standard
    43 pages
    English language
    sale 15% off

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.

  • Standard
    466 pages
    English language
    sale 15% off

This document describes the application layer protocol including the application measurement and control data management, message transfer and fault management. The application and application layer contain the following descriptions: — message structure; — communication method; — network management (optional); — measurement and control data; and — error handling. This document also specifies: — the service interface; and — the service interface parameters.

  • Standard
    37 pages
    English language
    sale 15% off

This document specifies the OSI transport layer and network layer by means of services and protocols. They can be used by different applications. The transport layer: — transforms a message into a single packet; — adds protocol control information for diagnostic and node configuration into each packet; — adds packet identifier for diagnostic and node configuration into each packet; and — performs transport protocol error detection. The transport layer protocol is not used for normal communication except to map the service interface parameters between lower and upper OSI layers. The network layer: — adds a node address for diagnostic and node configuration into each segment; and — observes timing for diagnostic and node configuration of each segment. The network layer is not used for normal communication except to map the service interface parameters between lower and upper OSI layers.

  • Standard
    23 pages
    English language
    sale 15% off

This document specifies the CXPI data link layer and the CXPI physical layer. The DLL is based on: — priority-based CXPI network access; — non-destructive content-based arbitration; — broadcast frame transfer and acceptance filtering; and — node related error detection and error signalling. The CXPI physical layer (PHY) requirements comprise of: — physical signalling (PS) sub-layer, which specifies the requirements of the clock generation function, the encoding and decoding of CXPI frames, and bit-wise collision resolution logic; — physical media attachment (PMA) sub-layer, which specifies the requirements of the signal shaping waveform logic; — physical media dependent (PMD) sub-layer, which specifies the requirements of the CXPI network termination, electrostatic discharge protection, etc., and device connector requirements; and — physical media (PM), which specifies the requirements of the CXPI network cable/wiring harness.

  • Standard
    56 pages
    English language
    sale 15% off

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.

  • Standard
    78 pages
    English language
    sale 15% off

This document identifies criteria that can be considered for assessing the risks related to solutions for remote access to road vehicles, including extended vehicles (ExVe) and their implementation. Internal communication within the vehicle or the ExVe is out of the scope of this document. Cybersecurity risks related to the VM infrastructure (except the elements that are part of the extended vehicle) and the road-side equipment are out of the scope of this document. The criteria identified in this document are also applicable in the case of a risk assessment related to the specification of remote communication solutions, for example a technical standard. The list of criteria that is provided can be considered as sufficiently comprehensive but not exhaustive, from a global point of view, to allow coherent risk mitigation, if such mitigation is necessary. This document does not suggest nor specify any methodology for performing a risk assessment. It does not aim at replacing any methodology, technical specification or standard relative to one or other specific type of risks (for example cyber security risks).

  • Technical report
    12 pages
    English language
    sale 15% off

This document specifies an additional electrical physical layer (EPL) for the Local Interconnect Network (LIN) of the ISO 17987 series. It specifies the transmission over DC powerline without affecting the LIN higher layers, hereafter named DC-LIN. The DC-LIN EPL uses a high-frequency modulated carrier to propagate UART bytes (byte-oriented) over the DC powerline. This document specifies the electrical characteristics, the modulation method of the transmission, and how to impose the carrier signal on the DC powerlines. The DC-LIN EPL supports bit rates of 9 615 bit/s, 10 417 bit/s, and 19 230 bit/s. The DC-LIN EPL is applicable for a wide range of DC powerlines including 12-V and 24-V operations, allowing communicating between different DC powerlines via a coupling capacitor. A DC-LIN EPL interface to powerline example is described in Annex A.

  • Standard
    56 pages
    English language
    sale 15% off

This document presents the assessment of the safety, security, competition, responsibilities, and data protection risks that can originate from the ISO 20078 series. In particular, the following risks are outside the scope of this assessment, because they relate to elements that are excluded from the scope of the ISO 20078 series: — the risks associated with the implementation of the ISO 20078 series; — the risks associated with the process that the accessing parties or any other parties would later on use to communicate the information they obtained; — the risks associated with the process used by the resource owner to provide, modify, or revoke their authorization to pass information; — the risks associated with the mitigation of the risks, should such a mitigation be necessary.

  • Technical report
    39 pages
    English language
    sale 15% off

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.

  • Standard
    22 pages
    English language
    sale 15% off

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.

  • Standard
    17 pages
    English language
    sale 15% off

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.

  • Technical report
    16 pages
    English language
    sale 15% off

This document, as a basis for the other parts of the ISO 15118 series, specifies terms and definitions, general requirements and use cases for conductive and wireless HLC between the EVCC and the SECC. This document is applicable to HLC involved in conductive and wireless power transfer technologies in the context of manual or automatic connection devices. This document is also applicable to energy transfer either from EV supply equipment to charge the EV battery or from EV battery to EV supply equipment in order to supply energy to home, to loads or to the grid. This document provides a general overview and a common understanding of aspects influencing identification, association, charge or discharge control and optimisation, payment, load levelling, cybersecurity and privacy. It offers an interoperable EV-EV supply equipment interface to all e-mobility actors beyond SECC. The ISO 15118 series does not specify the vehicle internal communication between battery and other internal equipment (beside some dedicated message elements related to the energy transfer). NOTE 1 Electric road vehicles specifically are vehicles in categories M (used for carriage of passengers) and N (used for carriage of goods) (compare ECE/TR ANS/WP.29/78 ev.2). This does not prevent vehicles in other categories from adopting the ISO 15118 series as well. NOTE 2 This document is destined to orientate the message set of ISO 15118‑2 and ISO 15118‑20[1]. The absence of any particular use case in this document does not imply that it will not be put into practice, with the required messages. NOTE 3 This document, ISO 15118‑2 and ISO 15118‑20 are designed to work independent of data transfer medium used. However, the ISO 15118 series is made for fitting the specified data link layers in the corresponding documents in this series. [1] Under preparation. Stage at the time on publication: ISO/DIS 15118-20:2019.

  • Standard
    117 pages
    English language
    sale 15% off
  • Standard
    131 pages
    French language
    sale 15% off

This document specifies general requirements and constraints applicable to a remote diagnostic process, the use cases and scenarios to support the implementation of a remote diagnostic process using a standardized interface of the ExVe. It concerns: — the road vehicles with four or more wheels designed and constructed primarily for the carriage of persons that are defined as Category 1 vehicles in the United Nations Special Resolution No.1 in TRANS/WP.29/1045, as last amended on 19 June 2012, and — the road vehicle with four or more wheels designed and constructed primarily for the carriage of goods that are defined as Category 2 vehicles in the United Nations Special Resolution No.1 in TRANS/WP.29/1045, as last amended on 19 June 2012, where these road vehicles are still in accordance with the specifications of the vehicle manufacturer. This document does not define the interfaces provided by the ExVe nor the internal implementation inside the ExVe. Processes like repair, prognostics, monitoring, configuration, re-programming and variant coding are not part of this document. The prerequisites (e.g. authentication and authorization) for all use cases are not covered within this document. A possible specification of the required content for the implementation of a remote diagnostic application using the web interface of the ExVe according to ISO 20078 is given in Annex A.

  • Standard
    61 pages
    English language
    sale 15% off

This document defines how to access Resources on a Web services interface of an Offering Party using the Hypertext Transfer Protocol Secure (HTTPS). For such an access, the Representational State Transfer (REST) architectural pattern is chosen as a common way to format Resource paths. 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.

  • Standard
    20 pages
    English language
    sale 15% off

This document defines the different concepts, entities and roles involved in implementing and delivering ExVe web services. In addition, it also gives an overview of the necessary activities that should be executed by the different roles involved and a logical order for those activities. This document defines the concept of identifiers (direct and correlated), different Resource categories (e.g. personal, vehicle related, pseudonymized and anonymized Resources) and different approaches on how to bundle sharable Resources (e.g. Resource Group or Container).

  • Standard
    17 pages
    English language
    sale 15% off