🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS ISO 20730-1:2021

BS ISO 20730-1:2021

$198.66

Road vehicles. Vehicle interface for electronic Periodic Technical Inspection (ePTI) – Application and communication requirements

Published By Publication Date Number of Pages
BSI 2021 54
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This document is applicable to road vehicles, where the electronic vehicle interface is used to perform a test method that is part of a periodic technical inspection (ePTI).

This document describes use cases and specifies technical requirements in order to support the ePTI-relevant vehicle safety system(s) checks during the periodic technical inspection via the electronic interface. This document references the ISO 14229 series, the unified diagnostic services implemented on diagnostic communication over controller area network (DoCAN) and the Internet protocol (DoIP) along with the required provision of data definitions.

The technical requirements of diagnostic services and data definitions of emissions-related systems are specified in other International Standards, for example, ISO 15031 and ISO 27145. Other environmental systems’ ePTI use cases and technical requirements can be considered in the future.

This document defines:

  • all requirements describing the vehicle-communication functionality via the diagnostic link connector related to ePTI, for example:

    1. discovery of the ePTI data link;

    2. discovery of the ePTI-relevant systems;

    3. query of ePTI-relevant systems’ information, including software identification, software integrity, current and/or stored values;

    4. query of ePTI-relevant systems’ error information;

    5. activation of ePTI-relevant systems’ actuators or routines;

  • the use cases about the individual vehicle communication functionality, for example, query identification information, command functional test method.

This document does not directly specify any type of test method or pass/fail criteria of the ePTI-relevant system during a PTI, but provides data, which may support PTI test methods.

The document specifies:

  • terminology;

  • communication establishment between the ePTI external test equipment and the vehicle’s ePTI-relevant systems;

  • usage of a credentials-based authentication and authorisation mechanism between the ePTI external test equipment and the vehicle;

  • protection against tampering of the defined ePTI methods;

  • definition of ePTI-relevant use cases:

    • ePTI external test equipment discovers available data identifier as specified in ISO 20730-3 ;

    • ePTI external test equipment queries the ePTI-relevant system’s information, including software numbers, software integrity information, current and/or stored values, self-test completion status, system status, and error information (e.g. DTC and/or DID information);

    • ePTI external test equipment activates the ePTI-relevant system’s actuators or routines;

  • definition of ePTI-relevant technical requirements;

  • ePTI external test equipment minimum requirements.

This document excludes:

  • process definitions for performing the PTI check;

  • process and data definitions for off-board data provision;

  • standardised data exchange formats;

  • validation and verification of vehicle safety systems according to vehicle manufacturer specifications.

PDF Catalog

PDF Pages PDF Title
2 undefined
8 Foreword
9 Introduction
11 1 Scope
12 2 Normative references
13 3 Terms and definitions
15 4 Symbols and abbreviated terms
5 How to read this document
5.1 Layout of the document
16 5.2 Use case structure explanation
5.3 Requirements statement structure
17 5.4 ePTI application example
18 6 ePTI inspection modules and use cases overview and principles
6.1 Basic principles
19 6.2 ePTI inspection modules
7 IM-1 – Discover ePTI data link and ePTI-relevant system(s)
7.1 UC 1.1 – Discover ePTI data link
20 7.2 UC 1.2 – Discover ePTI-relevant system(s)
8 IM-2 – Authentication, authorisation
8.1 UC 2.1 – ePTI external test equipment authentication
21 8.2 UC 2.2 – Vehicle ECU authentication
9 IM-3 – Query available ePTI identifier(s)
9.1 UC 3.1 – Query supported data identifier(s)
22 9.2 UC 3.2 – Query supported routine identifier(s)
9.3 UC 3.3 – Query supported input/output control identifier(s)
23 10 IM-4 – Query ePTI system information
10.1 UC 4.1 – Query vehicle identification number
10.2 UC 4.2 – Query vehicle odometer value
10.3 UC 4.3 – Query system’s software number
24 10.4 UC 4.4 – Identify installed system’s software integrity information
10.5 UC 4.5 – Query information from system
25 11 IM-5 – Query system’s self-test completion and error information
11.1 UC 5.1 – Query system’s self-test completion status
11.2 UC 5.2 – Query system status and error information
26 12 IM-6 – Activate system’s routines, input/output control(s)
12.1 UC 6.1 – Activate system’s routine(s)
12.2 UC 6.2 – Activate system’s input/output control(s)
27 13 Overview of vehicle system requirements
13.1 ePTI external test equipment and vehicle message exchange sequence
13.2 Technical requirements and use case coverage
28 14 Application (APP)
14.1 Setup vehicle’s DoCAN data link framework
30 14.2 Setup vehicle’s DoIP data link framework
32 14.3 Choice of DoCAN and DoIP data link in the vehicle
15 Application layer (AL)
15.1 Applicable ISO 14229-1 UDS functionality
33 15.2 Authentication
15.2.1 Requirements definition — ePTI external test equipment authentication
34 15.2.2 Requirements definition — ECU authentication
15.3 ReadDataByIdentifier — Report ePTI-relevant system(s)
15.3.1 Requirements definition — Report ePTI-relevant system(s)
15.3.2 Message sequence implementation requirements — Report ePTI-relevant system(s)
35 15.3.3 Example of the message sequence — Report ePTI-relevant system(s)
36 15.4 ReadDataByIdentifier — Report ECU supported data identifier(s)
15.4.1 Requirements definition — Report ECU supported data identifier(s)
37 15.4.2 Message sequence implementation requirements — Report ECU supported data identifier(s)
15.4.3 Example of the message sequence — Report ECU supported data identifier(s)
38 15.5 ReadDataByIdentifier — Report ECU supported routine identifier(s)
15.5.1 Requirements definition — Report ECU supported routine identifier(s)
15.5.2 Message sequence implementation requirements — Report ECU supported routine identifier(s)
39 15.5.3 Example of the message sequence — Report ECU supported routine identifier(s)
15.6 ReadDataByIdentifier — Report ECU supported input/output control identifier(s)
15.6.1 Requirements definition — Report ECU supported input/output control identifier(s)
40 15.6.2 Message sequence implementation requirements — Report ECU supported input/output control identifier(s)
15.6.3 Example of the message sequence — Report ECU supported input/output control identifier(s)
15.7 ReadDataByIdentifier — Report VIN from ECU
15.7.1 Requirements definition — Report VIN from ECU
41 15.7.2 Message sequence implementation requirements — Report VIN from ECU
15.7.3 Example of the message sequence — Report VIN from ECU
42 15.8 ReadDataByIdentifier — Report vehicle odometer value
15.8.1 Requirements definition — Report vehicle odometer value
15.8.2 Message sequence implementation requirements — Report vehicle odometer value
43 15.8.3 Example of the message sequence — Report vehicle odometer value
15.9 ReadDataByIdentifier — Report vehicle’s system software number(s)
15.9.1 Requirements definition — Report vehicle’s system software number(s)
44 15.9.2 Message sequence implementation requirements — Report vehicle’s system software number(s)
15.10 ReadDataByIdentifier — Report information from system
15.10.1 Requirements definition — Report information from system
45 15.10.2 Message sequence implementation requirements — Report information from system
15.10.3 Example of the message sequence — Report information from system
15.11 ReadDataByIdentifier — Report vehicle’s ePTI system self-test completion and system status
15.11.1 Requirements definition — Report vehicle’s ePTI system self-test completion and system status
46 15.11.2 Message sequence implementation requirements — Report vehicle’s ePTI system self-test completion and system status
47 15.11.3 Example of the message sequence — Report vehicle’s ePTI system self-test completion and system status
15.12 RoutineControl — Activate system’s routines
15.12.1 Requirements definition — Activate system’s routines
49 15.12.2 Message sequence implementation requirements — Activate system’s routines
15.12.3 Example of the message sequence — Activate system’s routines exterior lights
15.13 InputOutputControlByIdentifier — Activate system’s input/output controls
15.13.1 Requirements definition — Activate system’s input/output controls
51 15.13.2 Message sequence implementation requirements — Activate system’s input/output controls
15.13.3 Example of the message sequence — Activate system’s input/output controls
16 Session layer (SL)
52 Bibliography

Related products

BS ISO 20730-1:2021
$198.66