43.040.15 - Car informatics. On board computer systems
ICS 43.040.15 Details
Car informatics. On board computer systems
Kfz-Informatik. Bordcomputer
Informatique automobile. Systemes informatiques embarqués
Avtomobilska informatika. Vgrajeni računalniški sistemi
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 43.040.15 - Car informatics. On board computer systems
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
The purpose of this document is to provide background information on driver state monitoring (DSM) in the context of partial driving automation (SAE L2). It describes existing DSM implementations (including system interventions), the underlying design guidelines and provisions by relevant stakeholders in the field, as well as considerations on how to validate the effectiveness of driver state-related system interventions. Moreover, the document introduces a conceptual framework for “driver readiness and intervention management” for the purpose of providing a comprehensive view of relevant aspects of driver readiness and harmonizing terms and definitions in this field. It is believed that this framework can be helpful when comparing different approaches for driver state assessment. The document does not contain any specific technical requirements for current or future system implementations of driver state monitoring.
- Technical specification37 pagesEnglish languagesale 15% off
This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under test (SUT) that implements an electric-vehicle communication controller (EVCC) or a supply-equipment communication controller (SECC) for all common requirements specified in ISO 15118-20 that are independent of a particular charging type (AC, DC, ACD, WPT charging). These conformance tests specify the testing of capabilities and behaviours of an SUT, as well as checking what is observed against the conformance requirements specified in ISO 15118-20 and against what the implementer states the SUT implementation's capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements specified in ISO 15118-20. The behaviour tests of the ATS examine an implementation as thoroughly as practical over the full range of dynamic conformance requirements specified in ISO 15118-20 and within the capabilities of the SUT.
A test architecture is described in correspondence to the ATS. The abstract test cases in this document are described leveraging this test architecture and are specified in descriptive tabular format covering the ISO/OSI layer 3 to 7 (network to application layers).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118-20. This document additionally refers to specific tests for requirements on referenced standards (e.g. IETF RFCs, W3C Recommendation, etc.) if they are relevant in terms of conformance for implementations according to ISO 15118-20. However, it is explicitly not intended to widen the scope of this conformance specification to such external standards, if it is not technically necessary for the purpose of conformance testing for ISO 15118-20. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, or the environment of the protocol implementation. Furthermore, the abstract test cases specified in this document only consider the communication protocol and the system's behaviour specified in ISO 15118-20. Power flow between the EVSE and the EV is no prerequisite for the test cases specified in this document.
- Standard331 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements and recommendations regarding performance criteria for display systems in vehicles as a guideline for suppliers and manufacturers under normal operating conditions. This document applies to in-vehicle display systems designed to provide vital information to the driver and passenger. This document applies to the system as a whole as well as its relevant components, such as cover lenses, coatings, and properties of the device itself. This document covers display systems in passenger vehicles (including sport utility vehicles and light trucks) and commercial vehicles (including heavy trucks and buses). NOTE Static and dynamic laboratory testing and dynamic field operational assessment to measure display and cover glass attributes are also included, where available, in the scope of this document. This document is not applicable for: — technology and type of display device (e.g. LED, LCD, OLED); — manufacturing and handling of components in production; — electrical setup and integration into the vehicle; — EMC requirements for electrical subassemblies; — head-up display (HUD) and e-mirror displays [e.g. camera monitoring system (CMS)]; — behaviour in accidents besides the regulatory head impact test (HIT).
- Technical specification34 pagesEnglish languagesale 15% off
This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 13141.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment to support interoperability between different equipment supplied by different manufacturers.
ISO 13141 specifies requirements for the localization augmentation communication (LAC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard46 pagesEnglish languagesale 10% offe-Library read for1 day
This part 8 specifies the physical layer of an onboard data transmission bus between the different equipment for service operations and monitoring of the fleet. This applies to equipment installed on board vehicles that are operating as part of a public transport network, i.e. in operation under public service contracts. This equipment includes operation aid systems, automatic passenger information systems, fare collection systems, etc.
The use of IEEE 802.11 Wireless LAN communications is excluded from the scope of this Technical Specification; its use is not recommended for the service-based approach of CEN/TS 13149.
Equipment directly related to the safety-related functioning of the vehicle (propulsion management, brake systems, door opening systems, etc.) are excluded from the scope of this Technical Specification and are dealt with in other standardization bodies. Interfaces to such equipment or safety-critical networks can be provided through dedicated gateways.
This document covers the following:
— The link between equipment inside vehicles consisting of one carriage only, e.g. buses and trolleybuses, as well as a set of carriages, e.g. trams and trains;
— The Physical Layer for IP-communication networks onboard PT vehicles;
— The cables, connectors and other equipment including pin assignment and environmental requirements.
This document specifies wired communication networks onboard PT vehicles which are based on the Ethernet specification ISO/IEC/IEEE 8802-3-10 Base T, 100 Base Tx and 1000 Base T.
- Technical specification19 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical specification20 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the LIN protocol including the signal management, frame transfer, schedule table handling, task behaviour, status management, and commander and responder node. It contains also OSI layer 5 properties according to ISO 14229-7 UDSonLIN-based node configuration and identification services (SID: B016 to B816) belonging to the core protocol specification. A node (normally a commander node) that is connected to more than one LIN network is handled by higher layers (i.e. the application) not within the scope of this document.
- Standard74 pagesEnglish languagesale 15% off
This document outlines methodologies for creating and evaluating AACN algorithms, using suitable parameters, to predict the level of injury sustained by road users in a collision. The injury prediction is used to facilitate emergency response after a collision occurs. The methodology is based on onboard vehicle data and occupant-related information and applies to vehicle occupants and vulnerable road users. This document is applicable to road vehicles having provisions for measuring and communicating crash related data. This document provides neither a particular AACN injury level prediction algorithm, nor information on how to use the estimated probability of injury to decide on further suitable actions (rescue, medical, etc.). Data format for sending vehicle information and communication protocol between the vehicle and the public service answering point (PSAP) is outside the scope of this document.
- Technical specification42 pagesEnglish languagesale 15% off
This document describes use cases and activities for updating software in vehicles over the air using mobile cellular network. This document provides a case study on the use of International Standards in preparing software update packages, managing infrastructure and operation within the vehicles. This document includes descriptions of a reference model for software update operations and metadata which can be used during the software update operations.
- Technical report44 pagesEnglish languagesale 15% off
This part 8 specifies the physical layer of an onboard data transmission bus between the different equipment for service operations and monitoring of the fleet. This applies to equipment installed on board vehicles that are operating as part of a public transport network, i.e. in operation under public service contracts. This equipment includes operation aid systems, automatic passenger information systems, fare collection systems, etc.
The use of IEEE 802.11 Wireless LAN communications is excluded from the scope of this Technical Specification; its use is not recommended for the service-based approach of CEN/TS 13149.
Equipment directly related to the safety-related functioning of the vehicle (propulsion management, brake systems, door opening systems, etc.) are excluded from the scope of this Technical Specification and are dealt with in other standardization bodies. Interfaces to such equipment or safety-critical networks can be provided through dedicated gateways.
This document covers the following:
— The link between equipment inside vehicles consisting of one carriage only, e.g. buses and trolleybuses, as well as a set of carriages, e.g. trams and trains;
— The Physical Layer for IP-communication networks onboard PT vehicles;
— The cables, connectors and other equipment including pin assignment and environmental requirements.
This document specifies wired communication networks onboard PT vehicles which are based on the Ethernet specification ISO/IEC/IEEE 8802-3-10 Base T, 100 Base Tx and 1000 Base T.
- Technical specification19 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical specification20 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluation of on-board equipment (OBE) and roadside equipment (RSE) to EN 15509.
Normative Annex A presents the test purposes for the OBE.
Normative Annex B presents the test purposes for the RSE.
Normative Annex C provides the protocol conformance test report (PCTR) proforma for OBE.
Normative Annex D provides the PCTR proforma for RSE.
- Standard121 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a transport protocol and network layer services tailored to meet the requirements of LIN‑based vehicle network systems on local interconnect networks. The protocol specifies an unconfirmed communication. The LIN protocol supports the standardized service primitive interface as specified in ISO 14229-2. This document provides the transport protocol and network layer services to support different application layer implementations such as: — normal communication messages, and — diagnostic communication messages. The transport layer defines transportation of data that is contained in one or more frames. The transport layer messages are transported by diagnostic frames. A standardized API is specified for the transport layer. Use of the transport layer is targeting systems where diagnostics are performed on the backbone bus (e.g. CAN) and where the system builder wants to use the same diagnostic capabilities on the LIN sub-bus clusters. The messages are in fact identical to ones in ISO 15765-2 and the PDUs carrying the messages are very similar. The goals of the transport layer are: — to have low load on commander node, — to provide full (or a subset thereof) diagnostics directly on the responder nodes, and — to target clusters built with powerful LIN nodes (not the mainstream low cost).
- Standard75 pagesEnglish languagesale 15% off
This document specifies the 12 V and 24 V electrical physical layers (EPL) of the LIN communications system. The electrical physical layer for LIN is designed for low-cost networks with bit rates up to 20 kbit/s to connect automotive electronic control units (ECUs). The medium that is used is a single wire for each receiver and transmitter with reference to ground. Annex A provides recommendations on the LIN physical layer peripheral interface design of type UART and frame controller for commander and responder nodes. This document includes the definition of electrical characteristics of the transmission itself and also the documentation of basic functionality for bus driver devices. This document also provides the physical layer definitions for nodes with LIN AA capabilities according to one of the procedures C, D and E. All parameters in this document are defined for the ambient temperature range from −40 °C to 125 °C.
- Standard43 pagesEnglish languagesale 15% off
This document specifies the conformance test for the electrical physical layer (EPL) of the LIN communications system. The purpose of this document is to provide a standardised way to verify whether a LIN bus driver conforms to ISO 17987-4. The primary motivation is to ensure a level of interoperability of LIN bus drivers from different sources in a system environment. This document provides all the necessary technical information to ensure that test results are consistent even on different test systems, provided that the particular test suite and the test system are conformant to the content of this document.
- Standard195 pagesEnglish languagesale 15% off
This document specifies test methods to evaluate the behaviour of a vehicle equipped with an acceleration control pedal error (ACPE) system according to ISO/PAS 19486. Those forward and reverse accidents occur during a straight-line acceleration when the vehicle under test (VUT) accelerates due to driver misapplication of accelerator pedal instead of intended brake pedal. This document is limited to ACPE systems of light vehicles only classified in UN-ECE (TRANS/WP.29/1045) Vehicle: “Category 1-1 vehicle” and does not apply to such devices installed in vehicles of other categories, such as heavy vehicles or motorcycles. This document focuses on an important part of the vehicle behaviour during these collision scenarios, which is the capacity to avoid or mitigate the collision especially to the other vehicle.
- Technical specification13 pagesEnglish languagesale 15% off
This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and RSE to support interoperability between different equipment supplied by different manufacturers.
ISO 12813 specifies requirements for the compliance check communication (CCC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard91 pagesEnglish languagesale 10% offe-Library read for1 day
In respect of operating requirements specified in EN 16072, this document specifies adaptations to enable the provision of eCall for powered two-wheel vehicles.
As with the existing provisions for eCall for category M1/N1 vehicles, these are specified within the paradigm of being OEM-fit equipment supplied with new vehicles.
This document includes only the requirements for category L1 and L3 P2WV (vehicle based) with the exception of L1e-A (powered cycle), although other documents can subject other ‘L’ subcategories to use this document. Other documents can be prepared for other UNECE category ‘L’ variants.
The requirements herein relate only to the provision of pan-European eCall and does not provide requirements for third party service provision of eCall. Other than in the 112-eCall using IMS over packet switched networks paradigm, which involves a direct call from the vehicle to the most appropriate PSAP, third party service provision involves the support of an intermediary third-party service provider before the call is forwarded to the PSAP.
The provision of eCall for vehicles via the aftermarket (post sales and registration), and the operational requirements for any such aftermarket solution, will be the subject of other work.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the LIN protocol conformance test. This test verifies the conformance of LIN communication controllers with respect to ISO 17987-2 and ISO 17987-3. This document provides all necessary technical information to ensure that test results are identical even on different test systems, provided that the particular test suite and the test system are compliant to the content of this document. Annex A, Annex B and Annex C specify the protocol conformance test plans for responder nodes supporting auto addressing procedures according procedure C, procedure D or procedure E, see ISO 17987-3:2025, Annex C.
- Standard104 pagesEnglish languagesale 15% off
This document gives an overview of the structure and the partitioning of the ISO 17987 series. In addition, it outlines the use cases where the ISO 17987 series is used. The terminology defined in this document is common for all LIN communication systems and is used throughout the ISO 17987 series. This document has been established to define the use cases for LIN.
- Standard8 pagesEnglish languagesale 15% off
This document defines a data format to exchange data that is relevant for exchanging and using measurement equipment between calibration service providers, laboratories and requestors in vehicle safety testing. Additional content found on https://standards.iso.org/iso/ts/23520/ed-1/en defines standard exchange for equipment grouping and metadata definitions for test documentation. Related electronic documents are available for detailed reference based on examples. This document is applicable for all equipment manufacturers, calibration service providers, laboratories and their customers. This document excludes the exchange of test results or test documentation itself which is extensively defined in ISO/TS 13499.
- Technical specification7 pagesEnglish languagesale 15% off
This document specifies the functional requirements and test procedures for an acceleration control for pedal error (ACPE) system. This document applies to the systems installed in light vehicles (category M1 and N1)[2] and it does not apply to those installed in large vehicles or motorcycles.
- Technical specification13 pagesEnglish languagesale 15% off
This document specifies the physical and data link layer of high-level communication (HLC) between electric vehicles (EV) and electric vehicle supply equipment (EVSE) based on single-pair Ethernet communication. Single-pair Ethernet communication uses differential twisted pair wires that are dedicated and balanced. This document applies to 10BASE-T1S only.
This document covers the overall information exchange between all actors involved in electrical energy exchange. The ISO 15118 series applies to charging between EV and EVSE.
- Standard22 pagesEnglish languagesale 10% offe-Library read for1 day
The scope of this document encompasses design parameters of external visual communication used by single mode L4/L5 automated driving system-dedicated vehicles (ADS-DVs), as defined in SAE J3016. Guidance is given for passenger cars (including sport utility vehicles and light trucks) and commercial vehicles (including heavy trucks and buses), as well as derivatives of them that carry or do not carry compartments for occupants (i.e. driver or passengers). These vehicles can be operated in different domains, covering several alternative scenarios and use cases (e.g. open roads, motorways, urban environments, confined areas, geo-fenced areas with dedicated lanes, ports, terminals, pits). It is assumed that the design of ADS-DVs will be unique, thus making it readily apparent that the vehicle is an ADS-DV (see also Annex A for descriptions of use cases concerning the need for communication). The wide range of domains makes it important to consider users with different experiences and abilities, e.g. experienced and inexperienced drivers, elderly, people with disabilities and children.
- Technical specification58 pagesEnglish languagesale 15% off
The present document specifies technical requirements, limits and test methods for equipment employing UWB for
vehicular access devices installed in motor and railway vehicles in the frequency ranges 3,8 GHz to 4,2 GHz and
6,0 GHz to 8,5 GHz.
These equipment types are intended to be utilized for vehicle access, vehicle immobilization and extended vehicle
access control functionalities (like closing windows or remotely starting the car).
Further details of the covered EUT can be found in clause 4.2.
NOTE: The relationship between the present document and essential requirements of article 3.2 of
Directive 2014/53/EU [i.1] is given in annex A.
- Standard39 pagesEnglish languagesale 15% off
- Standard45 pagesEnglish languagesale 15% off
- Standard45 pagesEnglish languagesale 15% off
- Standard45 pagesEnglish languagesale 15% off
- Standard45 pagesEnglish languagesale 10% offe-Library read for1 day
This document applies to safety-related systems that include one or more electrical and/or electronic (E/E) systems that use AI technology and that is installed in series production road vehicles, excluding mopeds. It does not address unique E/E systems in special vehicles, such as E/E systems designed for drivers with disabilities. This document addresses the risk of undesired safety-related behaviour at the vehicle level due to output insufficiencies, systematic errors and random hardware errors of AI elements within the vehicle. This includes interactions with AI elements that are not part of the vehicle itself but that can have a direct or indirect impact on vehicle safety. EXAMPLE 1 Examples of AI elements within the vehicle include the trained AI model and AI system. EXAMPLE 2 Direct impact on safety can be due to object detection by elements external to the vehicle. EXAMPLE 3 Indirect impact on safety can be due to field monitoring by elements external to the vehicle. The development of AI elements that are not part of the vehicle is not within the scope of this document. These elements can conform to domain-specific safety guidance. This document can be used as a reference where such domain-specific guidance does not exist. This document describes safety-related properties of AI systems that can be used to construct a convincing safety assurance claim for the absence of unreasonable risk. This document does not provide specific guidelines for software tools that use AI methods. This document focuses primarily on a subclass of AI methods defined as machine learning (ML). Although it covers the principles of established and well-understood classes of ML, it does not focus on the details of any specific AI methods e.g. deep neural networks.
- Technical specification172 pagesEnglish languagesale 15% off
This document provides a taxonomy to classify the type of adaptivity within vehicle systems. The taxonomy includes five types ranging from no adaptation (type 0) to adaptations based on interpreted user characteristics and context data (type 4). This document provides definitions of the five types of adaptation and explains adaptation in a consistent and coherent manner. By offering definitions and descriptions of the five types, this document can be used to classify the adaptivity within vehicle systems according to the types. This document is intended to be applied to all components of vehicle systems that the driver and/or other occupants interact with either while driving or while parked. This includes vehicle information systems, communication systems, for example, navigation systems or mobile devices connected to the vehicle infrastructure, traffic and travel information (TTI) systems, as well as vehicle comfort systems, for example, climate control, massage, or ambient lighting. The taxonomy is also applicable to third-party software provided by third-party suppliers that is displayed and/or operated in the vehicle. The taxonomy can also be applied to interactive exterior elements, like windscreen wipers or pedestrian communication devices and non-driving-related functions that are novel to future vehicles in the context of automated driving, such as playing a video. The information and communication vehicle systems described in this document exclude driving-operation or driving-assistance systems. Consequently, safety-related functions governed by Automotive Safety Integrity Level (ASIL) specifications (ISO 26262) are not addressed. Implementation and validation of data collection/detection are also beyond the scope. Additionally, priority handling, as well as varying legal regulations across countries, are not covered in the taxonomy.
- Technical specification17 pagesEnglish languagesale 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 interpreted. The syntax rules are provided by UML[2] class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions.
- Standard457 pagesEnglish languagesale 15% off
This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services and re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of their content and syntax.
The data structures are specified as communications-agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.
- Technical specification58 pagesEnglish languagesale 10% offe-Library read for1 day
This document proposes a standard test procedure to assess the efficiency of cleaning systems for sensors. It addresses the following conditions: — dust/mud — frost/snow — mist/rain This document does not propose a preferred cleaning system. This document is intended to be technologically neutral and performance-oriented. Its focus is on the cleaning system, not on sensor detection. The assessment method specified in this document is therefore fully independent from sensor technology and from the data generated by the sensor when in use. This document is entirely focussed on the cleanliness of the front surface of the sensor. This document does not address continuous contamination, such as continuous rain. This is because in these circumstances, the efficiency of the cleaning system can only be assessed from inside the sensor. For non-continuous contamination, this document includes intermittent cleaning, which is considered a succession of cleaning cycles that are launched periodically, as defined in 3.2. The test does not include specific day time/night time conditions. This is because these conditions have no impact on the results and the average clean remains similar. However, more efficient cleaning can be done at night. This document does not cover contamination with insects due to the challenges of ensuring homogeneous application. This document does not provide indicators for sensor performance. This document is limited to the evaluation of the removal of contamination from surfaces. This document does not include evaluation on preventive measures taken in the installation design. The aerodynamic design affects how mud sprayed from a moving vehicle or rain droplets can reach and build-up on the sensor's frontal protection layer. Countermeasure design is beyond the scope of this document.
- Standard21 pagesEnglish languagesale 15% off
- Standard1 pageEnglish languagesale 15% off
This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services and re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of their content and syntax.
The data structures are specified as communications-agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.
- Technical specification58 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services and re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of their content and syntax. The data structures are specified as communications-agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.
- Technical specification49 pagesEnglish languagesale 15% off
This document specifies a graphic data dictionary (GDD), a system of standardized codes for existing road traffic signs and pictograms used to deliver traffic and traveller information (TTI). The coding system can be used in the formation of messages within intelligent transport systems (ITS).
- Standard81 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the controller area network (CAN) data link layer (DLL) and the physical coding sub-layer (PCS). The CAN DLL features data fields of up to 2048 byte when the CAN extended data field length (XL) frame format is used. This document divides the CAN DLL into the logical link control (LLC) and the medium access control (MAC) sub-layers. The DLL’s service data unit (SDU), which interfaces the LLC and the MAC, is implemented by means of the LLC frame. The LLC frame also features the service data unit type (SDT) and the virtual CAN channel identifier (VCID), which provide higher-layer protocol configuration and identification information. How the higher-layer functions are handled is not specified in this document. There are five implementation options: 1) support of the CAN classic frame format only, not tolerating the CAN flexible data rate (FD) frame format; 2) support of the CAN classic frame format and tolerating the CAN FD frame format; 3) support of the CAN classic frame format and the CAN FD frame format; 4) support of the CAN classic frame format, the CAN FD frame format and the CAN XL frame format; 5) support of the CAN FD frame format for CAN FD light responders (Annex A). NOTE Nodes of the first option can communicate with nodes of the third and fourth option when only the CAN classic frame format is used. Nodes of the first option cannot communicate with nodes of the fifth option: any attempt at communication generates error frames. Therefore, new designs implementing the fourth option can communicate with all other nodes.
- Standard82 pagesEnglish languagesale 15% off
This document specifies a graphic data dictionary (GDD), a system of standardized codes for existing road traffic signs and pictograms used to deliver traffic and traveller information (TTI). The coding system can be used in the formation of messages within intelligent transport systems (ITS).
- Standard81 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a graphic data dictionary (GDD), a system of standardized codes for existing road traffic signs and pictograms used to deliver traffic and traveller information (TTI). The coding system can be used in the formation of messages within intelligent transport systems (ITS).
- Standard73 pagesEnglish languagesale 15% off
This document specifies a transport and network layer protocol with transport 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. The diagnostic communication over controller area network (DoCAN) protocol supports the standardized abstract service primitive interface as specified in ISO 14229-2 (UDS). This document supports different application layer protocols 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 the ISO 15031 series and SAE J1979 series; — world-wide harmonized on-board diagnostics (WWH-OBD) as specified in the ISO 27145 series; and — end of life activation of on-board pyrotechnic devices (the ISO 26021 series). The transport protocol specifies an unconfirmed communication. NOTE This document does not determine whether CAN CC, CAN FD or both are recommended or required to be implemented by other standards referencing this document.
- Standard47 pagesEnglish languagesale 15% off
This document specifies physical medium attachment (PMA) sublayers for the controller area network (CAN). This includes the high-speed (HS) PMA without and with low-power mode capability, without and with selective wake-up functionality. Additionally, this document specifies PMAs supporting the signal improvement capability (SIC) mode and the FAST mode in Annex A. The physical medium dependent (PMD) sublayer is not in the scope of this document.
- Standard64 pagesEnglish languagesale 15% off
This document defines the extraction of vehicle trip data via nomadic devices to measure CO2 emissions in relation to driving behaviours. The extracted data can then be analysed and provided to drivers to serve as eco-friendly driving guidance. In this document the following items are defined: — use cases for different events (speeding, long speeding, sudden start and stop, sudden acceleration and deceleration, idling, fuel-cut, economical driving); — functional requirements for collecting data for driving behaviour pattern analysis; — data sets for each use case for measuring vehicle emissions (CO2) and for being provided to drivers via nomadic devices. Vehicle types such as passenger cars, vans, utility vehicles, etc. are concerned in this document
- Standard15 pagesEnglish languagesale 15% off
This document describes a framework for functional safety to enable the use of pre-existing software architectural elements not originally developed in accordance with the ISO 26262:2018 series, but intended to be integrated into safety-related embedded software conformant with the ISO 26262:2018 series by: — determining relevant criteria when using the pre-existing software architectural element as a safety-related element of safety-related embedded software; — determining relevant criteria inherent to the pre-existing software architectural element, e.g. needs for external safety mechanisms to detect and control failures caused by the pre-existing software architectural element; — providing suitable evidence and arguments for use of the pre-existing software architectural element that can include applicable procedures, techniques and safety measures; — supporting the fulfilment of software safety requirements when using the pre-existing software architectural element as a safety-related element of safety-related embedded software; — supporting the integration of the pre-existing software architectural element as a safety-related element of safety-related embedded software.
- Technical specification19 pagesEnglish languagesale 15% off
This European Standard defines the key actors in the eCall chain of service provision as:
1) In-Vehicle System (IVS)/vehicle,
2) Mobile network Operator (MNO),
3) Public safety assistance point [provider](PSAP),
in some circumstances may also involve:
4) Third Party Service Provider (TPSP),
and to provide conformance tests for actor groups 1) - 4).
NOTE Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service.
This European Standard covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
- Standard264 pagesEnglish languagesale 10% offe-Library read for1 day
IEC TR 63479-1:2023 describes general considerations and system model for infotainment services for public vehicles (PVIS), with the relevant service examples.
- Technical report22 pagesEnglish languagesale 15% off
This document specifies the OSI layers 4 to 1 (transport layer, network layer, data link layer and physical layer) 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 and maintain communication utilizing the communication parameters (communication profile) specified in (application-type) standards referencing this document. The SIC (signal improvement capability) transceiver options, as specified in ISO 11898-2, are out of scope in this document.
- Standard18 pagesEnglish languagesale 15% off
This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under test (SUT) implementing an electric-vehicle or supply-equipment communication controller (EVCC or SECC) with support for WLAN-based high-level communication (HLC) according to ISO 15118‑8 and against the background of ISO 15118-1. These conformance tests specify the testing of capabilities and behaviours of an SUT, as well as checking what is observed against the conformance requirements specified in ISO 15118‑8 and against what the implementer states the SUT implementation's capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements defined in ISO 15118‑8. The behaviour tests of the ATS examine an implementation as thoroughly as practical over the full range of dynamic conformance requirements defined in ISO 15118‑8 and within the capabilities of the SUT (see NOTE below).
A test architecture is described in correspondence to the ATS. The abstract test cases in this document are described leveraging this test architecture and are specified in descriptive tabular format for the ISO/OSI physical and data link layers (layers 1 and 2).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118‑8. This document can additionally refer to specific tests for requirements on referenced standards (e.g. IEEE, or industry consortia standards, like WiFi Alliance) as long as they are relevant in terms of conformance for implementations according to ISO 15118‑8. However, it is explicitly not intended to widen the scope of this conformance specification to such external standards, if it is not technically necessary for the purpose of conformance testing for ISO 15118‑8. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, nor the environment of the protocol implementation. Furthermore, the abstract test cases defined in this document only consider the communication protocol and the system's behaviour defined ISO 15118‑8. The power flow between the EVSE and the EV is not considered.
NOTE Practical limitations make it impossible to define an exhaustive test suite, and economic considerations can restrict testing even further. Hence, the purpose of this document is to increase the probability that different implementations are able to interwork. This is achieved by verifying them by means of a protocol test suite, thereby increasing the confidence that each implementation conforms to the protocol specification. However, the specified protocol test suite cannot guarantee conformance to the specification since it detects errors rather than their absence. Thus, conformance to a test suite alone cannot guarantee interworking. Instead, it gives confidence that an implementation has the required capabilities and that its behaviour conforms consistently in representative instances of communication.
- Standard80 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides a common framework of definitions and measurement methods for the design, and ergonomics testing of automotive head-up displays (HUDs) independent of technologies except where noted. Applications in both passenger cars (including sport utility vehicles and light trucks) and commercial vehicles (including heavy trucks and buses) are covered. This document does not include helmet-mounted HUDs or other head carried gear such as glasses. Areas covered in this document include: — guidance on how to establish reference points and representative viewing conditions based on vehicle coordinates and ranges of driver's/passenger's eye points; — descriptions of the HUD image geometry and optical properties measurements; — definitions of the HUD virtual image and driver vision measurements; — static and dynamic laboratory tests, and dynamic field operational assessments that include suggested vehicle setup procedures in order to measure HUD image attributes.
- Technical specification76 pagesEnglish languagesale 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.
- Standard344 pagesEnglish languagesale 15% off
This document addresses light-duty vehicles, such as passenger cars, pick-up trucks, light vans and sport utility vehicles (motorcycles excluded) equipped with Manoeuvring Aids for Low Speed Operation (MALSO) systems. It specifies the minimum functionality requirements which the driver can generally expect of the device, i.e. detection of and information on the presence of relevant obstacles within a defined (short) detection range. It defines minimum requirements for failure indication as well as performance test procedures; it includes rules for the general information strategy but does not restrict the kind of information or display system. MALSO systems use object-detection devices (sensors) for ranging in order to provide the driver with information based on the distance to obstacles. Although sensing technology is not addressed in this document, technology does affect the performance-test procedures set up in Clause 7. The current test objects are defined based on systems using ultrasonic sensors, which reflect the most commonly used technology at the time of publication. For other sensing technologies which will potentially emerge in the future, these test objects shall be checked and changed if required. Visibility-enhancement systems like video-camera aids without distance ranging and warning are not covered by this document. Reversing aids and obstacle-detection devices on heavy commercial vehicles are not addressed by this document.
- Standard21 pagesEnglish languagesale 15% off
This document specifies diagnostic application requirements and OSI-layer related communication profiles to ensure the interchange of digital information between towing and towed vehicles with a maximum authorized total mass greater than 3 500 kg. The conformance and interoperability test plans are not part of this document.
- Standard30 pagesEnglish languagesale 15% off
This document specifies the SAE J1939-based application layer, the payload of messages, and parameter groups for electronically controlled braking systems, including anti-lock braking systems (ABS), vehicle dynamics control systems (VDC), and running gears equipment, to ensure the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including communication between towed vehicles. Conformance and interoperability test plans are not part of this document.
- Standard103 pagesEnglish languagesale 15% off
This document specifies requirements and recommendations for software update engineering for road vehicles on both the organizational and the project level. This document is applicable to road vehicles whose software can be updated. The requirements and recommendations in this document apply to vehicles, vehicle systems, ECUs, infrastructure, and the assembly and deployment of software update packages after the initial development. This document is applicable to organizations involved in software update engineering for road vehicles. Such organizations can include vehicle manufacturers, suppliers, and their subsidiaries or partners. This document establishes a common understanding for communicating and managing activities and responsibilities among organizations and related parties. The development of software for vehicle functions, except for software update engineering, is outside the scope of this document. Finally, this document does not prescribe specific technologies or solutions for software update engineering.
- Standard24 pagesEnglish languagesale 15% off
- Standard24 pagesEnglish languagesale 15% off
- Standard24 pagesEnglish languagesale 15% off
IEC 63005-2:2019 describes test methods on evaluating performance of basic functionalities of EVDR described in IEC 63005-1.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day