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 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 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 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 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 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 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 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 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 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 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 describes tests which verify on-board unit (OBU) conformance of functions and data
structures implementations, as defined in the implementation conformance statement (ICS) based on
ISO 14906 for EFC applications.
This document defines tests for assessing OBU conformance in terms of :
— basic dedicated short-range communication (DSRC) L7 functionality,
— EFC application functions,
— EFC attributes (i.e. EFC application information),
— the addressing procedures of EFC attributes and (hardware) components,
— the EFC transaction model, which defines the common elements and steps of any EFC transaction, and
— the behaviour of the interface so as to support interoperability on an EFC-DSRC application
interface level.
After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing a
complete EFC transaction (C.3). Although this document defines examples of test cases for DSRC
and EFC functionality (see Annex C), it does not intend to specify a complete test suite for a certain
implementation. To compose a test suite for a specific EFC implementation, the test cases can be
modified and new test cases can be defined and added in order for the conformance test suite to be
complete. It can be useful to consider the following when defining a complete test suite:
— small range: “exhaustive testing” of critical interoperability/compatibility features,
— large range: testing of boundaries and random values, and
— composite types: testing of individual items in sequence or parallel.
This document does not define tests which assess:
— performance,
— robustness, and
— reliability of an implementation.
NOTE 1 ISO 14907-1 defines test procedures that are aimed at assessing performance, robustness and
reliability of EFC equipment and systems.
NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and
related devices that can be relevant for OBUs which support such cards.
Annex D provides an informative overview of Japanese on-board equipment (OBE) conformance tests
which are based on the ISO 14907 series, in order to illustrate how these can be applied in practice.

  • Standard
    85 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides formal procedures and two, alternative, methods (users are advised to choose whichever of the two suits their individual requirements) for determining the priority of on-board messages presented to drivers of road vehicles by transport information and control systems (TICS) and other systems. It is applicable to the whole range of TICS in-vehicle messages, including traveller information, navigation, travel and traffic advisories, "yellow pages" information, warnings, systems status, emergency calling system information, and electronic toll/fee collection, as well as to messages from non-TICS sources such as telephone, warnings and telltales. Although applicable to systems that allow the free generation of messages, it neither provides guidance on how to use the messages deriving from its procedures nor is it applicable to mandatory or legally required messages.

  • Technical specification
    31 pages
    English language
    sale 15% off
  • Draft
    31 pages
    English language
    sale 15% off

This document describes tests which verify on-board unit (OBU) conformance of functions and data structures implementations, as defined in the implementation conformance statement (ICS) based on ISO 14906 for EFC applications. This document defines tests for assessing OBU conformance in terms of : — basic dedicated short-range communication (DSRC) L7 functionality, — EFC application functions, — EFC attributes (i.e. EFC application information), — the addressing procedures of EFC attributes and (hardware) components, — the EFC transaction model, which defines the common elements and steps of any EFC transaction, and — the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface level. After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing a complete EFC transaction (C.3). Although this document defines examples of test cases for DSRC and EFC functionality (see Annex C), it does not intend to specify a complete test suite for a certain implementation. To compose a test suite for a specific EFC implementation, the test cases can be modified and new test cases can be defined and added in order for the conformance test suite to be complete. It can be useful to consider the following when defining a complete test suite: — small range: "exhaustive testing" of critical interoperability/compatibility features, — large range: testing of boundaries and random values, and — composite types: testing of individual items in sequence or parallel. This document does not define tests which assess: — performance, — robustness, and — reliability of an implementation. NOTE 1 ISO 14907‑1 defines test procedures that are aimed at assessing performance, robustness and reliability of EFC equipment and systems. NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and related devices that can be relevant for OBUs which support such cards. Annex D provides an informative overview of Japanese on-board equipment (OBE) conformance tests which are based on the ISO 14907 series, in order to illustrate how these can be applied in practice.

  • Standard
    77 pages
    English language
    sale 15% off
  • Standard
    76 pages
    French language
    sale 15% off
  • Draft
    78 pages
    English language
    sale 15% off
  • Draft
    75 pages
    French language
    sale 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, locationbased
services, re-routing. The information in the containers is organized in sub-structures called data
frames and data elements, which are described in terms of its content and its 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 specification
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 defines requirements on the compliance check communication (CCC) interface level, but
not for the RSE or OBE internal functional behaviour. Consequently, tests regarding OBE and/or RSE
functional behaviour remain outside the scope of this document.

  • Standard
    78 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 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 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 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 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
    41 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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 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, re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of its content and its 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 specification
    48 pages
    English language
    sale 15% off
  • Draft
    48 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 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 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 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 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 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 part of IEC 63005 describes test methods on evaluating performance of basic
functionalities of EVDR described in IEC 63005-1.

  • Standard
    19 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the test procedures of electronic fee collection (EFC) roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically.
The scope of this document is restricted to systems operating within the radio emission, electromagnetic
compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated.
This document identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters:
— functionality;
— quality;
— referenced pre-tests.
An overview of the tests and parameters provided by this document is given in 5.1 and 5.2.
This document describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken.
It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this document provide instructions to evaluate the test results.
This document defines only the tests and test procedures, not the benchmark figures that these are to be measured against. The test procedures defined in this document can be used as input, e.g. by scheme owners, for prototype testing, type approvals, tests of installations and periodic inspections.
Related to a conceptual model of an EFC system, this document relates only to the equipment of the user and the service provider. Any other entities are outside the scope of document.
EFC systems for dedicated short-range communication (DSRC) consist, in principle, of a group of technical components, which in combination fulfil the functions required for the collection of fees by electronic automatic means. These components comprise all, or most, of the following:
— OBE within a vehicle;
— OBE containing the communications and computing sub-functions;
— optional integrated circuit card which may carry electronic money, service rights, and other secured information;
— communication between OBE and RSE based on DSRC;
— equipment for the fee collection at the RSE containing the communications and computing subfunctions;
— equipment for the enforcement at the roadside;
— central equipment for the administration and operation of the system.
The scope of this document relates solely to OBE and RSE and the DSRC interface between OBE and RSE including its functions to perform the fee collection. All the equipment used for enforcement (e.g. detection, classification, localization, and registration) and central equipment are outside the scope of this document.

  • Standard
    96 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines key terms and parameters applied in the analysis of driver visual behaviour focused on glance and glance-related measures. It provides guidelines and minimum requirements on equipment and procedures for analysing driver visual behaviour including assessment of TICS to: — plan evaluation trials; — specify (and install) data capture equipment; and — validate, analyse, interpret and report visual-behaviour metrics (standards of measurement). The parameters and definitions described below provide a common source of reference for driver visual behaviour data. It is applicable to on-road trials (e.g. field operational tests or naturalistic studies), and laboratory-based driving studies. The procedures described in this document can also apply to more general assessments of driver visual behaviour. Data collected and analysed according to this document will allow comparisons to be performed across different TICS applications and experimental scenarios.

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

This document specifies OCC (Optical Camera Communication) as an access technology for localized communications applicable in ITS stations conforming with ISO 21217. OCC access technology is specified for the implementation context of ISO 21218. This document provides specifications of a communication interface (CI) named "ITS-OCC". This document specifies the additions to and deviations from IEEE 802.15.7:2018 which are required in order to make ITS-OCC CIs compatible with: — the ITS station and communication architecture specified in ISO 21217, and — the hybrid communications support specified in ISO 21218. This document specifies: — an OCC profile of IEEE 802.15.7:2018 for usage in C-ITS; — details of CAL (ISO 21218); and — details of MAE (ISO 21218, ISO 24102-3). NOTE Considering safety-related services involving communications between a vehicle and a roadside station being performed on the basis of OCC, it is noted that, due to shadowing, communications can be interrupted or blocked for a significantly long time.

  • Standard
    25 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

The CEN 13149 series of products concerns on-board data communication systems on public transport vehicles. This series provides for data services that enable open and managed sharing of relevant information.
This document, being Part 10 of the series, specifies a location publication, enabling all on-vehicle services to share a common understanding of the location and orientation of the vehicle, based on inputs taken from global navigational satellite systems (GNSS) such as GPS and Galileo. It covers:
-   the functional scope, i.e. which data the service provides, why, when and how often;
-   the transport protocol, i.e. how the data are transmitted;
-   the service publication, i.e. how the service can be found by other modules or applications;
-   the structure of the data, i.e. how the data are structured and how the data elements are named.
This document implements the service framework described in FprCEN/TS 13149-7.

  • Technical specification
    13 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The CEN 13149 series of products concerns on-board data communication systems on public transport vehicles. This series provides for data services that enable open and managed sharing of relevant information.
This document, being Part 9 of the series, specifies a time publication, enabling all on-vehicle services to share a common understanding of current time, based on a suitable agreed master network clock. It covers:
-   the functional scope, i.e. which data the service provides, why, when and how often.
-   the transport protocol, i.e. how the data are transmitted.
-   the service publication, i.e. how the service can be found by other modules or applications
-   the structure of the data, i.e. how the data are structured and how the data elements are named.
This document implements the service framework described in FprCEN/TS 13149-7.

  • Technical specification
    9 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The CEN 13149 series of products concerns on-board data communication systems on public transport vehicles. This series provides for data services that enable open and managed sharing of relevant information.
This document, being Part 11 of the series, specifies a publication service for data provided by the vehicle platform, enabling all on-vehicle services to share a common understanding of the operational activity of the vehicle, based on inputs taken from chassis systems such as the J1939 CAN bus. It covers:
-   the functional scope, i.e. which data the service provides, why, when and how often.
-   the transport protocol, i.e. how the data are transmitted.
-   the service publication, i.e. how the service can be found by other modules or applications
-   the structure of the data, i.e. how the data are structured and how the data elements are named.
This document implements the service framework described in FprCEN/TS 13149-7.

  • Technical specification
    14 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the test procedures of electronic fee collection (EFC) roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically. The scope of this document is restricted to systems operating within the radio emission, electromagnetic compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated. This document identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters: — functionality; — quality; — referenced pre-tests. An overview of the tests and parameters provided by this document is given in 5.1 and 5.2. This document describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this document provide instructions to evaluate the test results. This document defines only the tests and test procedures, not the benchmark figures that these are to be measured against. The test procedures defined in this document can be used as input, e.g. by scheme owners, for prototype testing, type approvals, tests of installations and periodic inspections. Related to a conceptual model of an EFC system, this document relates only to the equipment of the user and the service provider. Any other entities are outside the scope of document. EFC systems for dedicated short-range communication (DSRC) consist, in principle, of a group of technical components, which in combination fulfil the functions required for the collection of fees by electronic automatic means. These components comprise all, or most, of the following: — OBE within a vehicle; — OBE containing the communications and computing sub-functions; — optional integrated circuit card which may carry electronic money, service rights, and other secured information; — communication between OBE and RSE based on DSRC; — equipment for the fee collection at the RSE containing the communications and computing sub-functions; — equipment for the enforcement at the roadside; — central equipment for the administration and operation of the system. The scope of this document relates solely to OBE and RSE and the DSRC interface between OBE and RSE including its functions to perform the fee collection. All the equipment used for enforcement (e.g. detection, classification, localization, and registration) and central equipment are outside the scope of this document.

  • Standard
    87 pages
    English language
    sale 15% off
  • Standard
    92 pages
    French language
    sale 15% off

This document specifies the general rules for an on-board data communication system between the different systems that may be used within public transport vehicles, based on the Internet Protocol (IPv4, [3] and IPv6, [4]). This includes operational support systems, passenger information systems, fare collection systems, etc.
This document describes:
-   the requirements for an on board IP network;
-   the overview architecture and components for an IP based on-board network;
-   the modular structure of the network architecture;
-   the Service Oriented Architecture (SOA) approach, and approach to defining services.
Systems directly related to the safe operation of the vehicle (including propulsion management, brake systems, door opening systems) are excluded from the scope of this document and are dealt with in other standardization bodies. However, the architecture described in this document may be used for support services such as safety information messages. Interfaces to safety-critical systems should be provided through dedicated gateways with appropriate security provisions; for the purposes of this document, these are regarded as simply external information sources.
This document is designed primarily for vehicles with a fixed primary structure, where networks can be installed on a permanent basis and the system configuration task consists largely of the integration, adjustment or removal of the functional end systems that produce and/or consume data. Public transport vehicles consisting of units linked temporarily for operational purposes (specifically, trains in which individual engines, cars or consists are routinely connected and disconnected) require additional mechanisms to enable the communications network itself to reconfigure. Such mechanisms are provided through other standards, notably the IEC 61375 series [5].

  • Technical specification
    26 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 63005-2:2019 describes test methods on evaluating performance of basic functionalities of EVDR described in IEC 63005-1.

  • Standard
    19 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the general rules for an on-board data communication system between the different systems that may be used within public transport vehicles, based on the Internet Protocol (IPv4, [3] and IPv6, [4]). This includes operational support systems, passenger information systems, fare collection systems, etc.
This document describes:
-   the requirements for an on board IP network;
-   the overview architecture and components for an IP based on-board network;
-   the modular structure of the network architecture;
-   the Service Oriented Architecture (SOA) approach, and approach to defining services.
Systems directly related to the safe operation of the vehicle (including propulsion management, brake systems, door opening systems) are excluded from the scope of this document and are dealt with in other standardization bodies. However, the architecture described in this document may be used for support services such as safety information messages. Interfaces to safety-critical systems should be provided through dedicated gateways with appropriate security provisions; for the purposes of this document, these are regarded as simply external information sources.
This document is designed primarily for vehicles with a fixed primary structure, where networks can be installed on a permanent basis and the system configuration task consists largely of the integration, adjustment or removal of the functional end systems that produce and/or consume data. Public transport vehicles consisting of units linked temporarily for operational purposes (specifically, trains in which individual engines, cars or consists are routinely connected and disconnected) require additional mechanisms to enable the communications network itself to reconfigure. Such mechanisms are provided through other standards, notably the IEC 61375 series [5].

  • Technical specification
    26 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This European Standard applies to controller device interfaces that provide defined interfaces between low voltage switchgear, controlgear, control circuit devices, switching elements and controlling devices (e.g. programmable controllers, personal computers, etc.). It may also be applied for the interfacing of other devices and elements to a controller device interface.
This standard specifies requirements for controllers and devices utilising these interfaces, including not only the communication protocol specification, but also associated relevant electrical and mechanical characteristics.  It also specifies the electrical and EMC tests required to verify the performance of each controller device interface when connected to the appropriate controllers and devices.
This part 1 establishes a consistent terminology and format for the subsequent interfaces.  It also harmonises requirements of a general nature in order to reduce the need for testing to different standards, increase understanding and facilitate comparisons of controller device interface standards.  Those requirements of the various controller device interface standards which can be considered as general have therefore been gathered in this part 1.
In addition to meeting the specific requirements stated in this part 1, the controller device interfaces included in this standard
   are documented in the English language in accordance with the requirements specified in this part 1,
   are already in use in commercial products and running in industrial plants,
   are available in quantity and at low price,
   are available from several sources and commercialised openly,
   to satisfy the tests specified, amongst others,  in EN 61000 4 2, EN 61000 4 3, EN 61000 4 4,
EN 61000 4 5, and EN 61000 4 6 against the test levels specified in EN 50082 2,
   have appropriate mechanisms for transmission error detection,
   are open, widely accepted, well documented, stable and support inter operability,
   are complete and describe the necessary interfaces in sufficient detail to enable error free implementation,
   are free of any restriction related to testing the implementation.
For each controller device interface only two documents are necessary to determine all requirements and tests:
   the general requirements of this standard, referred to as "part 1" in the relevant parts covering the various types of controller device interfaces;
   the relevant controller device interface standard hereinafter referred to as the "relevant controller device interface standard" or "controller device interface standard".
The solutions described in this standard have been used for many years by industry to solve application requirements involving low voltage switchgear and controlgear. They are characterised by:
   their ability to power connected devices directly from the network;
   their ability to operate in harsh environments typified by those encountered at the machine level by controls in industrial applications;
   usage of the sophisticated medium access rules of CAN which allows both organisation of traffic based on user assigned priorities and efficient resolution of occasional access conflict;
   a wide range of exchange services allowing precise tailoring of data exchange to the actual application needs as well as simultaneous distribution of data to a selected set of connected devices;
   their capability to simultaneously support data acquisition, diagnostics, messaging and
   programming/configuration as required, amongst others, for systems interfacing controllers to
low voltage switchgear and controlgear in industrial applications.
NOTE   The controller device interface standards currently part of this series are:
   EN 50325 2:  DeviceNet
   EN 50325 3:  Smart Distributed System (SDS)
   EN 50325-4: CANopen
   EN 50325-5 : Functional safety communication based on EN 50325-4

  • Standard
    14 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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