ISO 20730-1:2021

INTERNATIONAL ISO
STANDARD 20730-1
First edition
2021-04
Road vehicles — Vehicle interface
for electronic Periodic Technical
Inspection (ePTI) —
Part 1:
Application and communication
requirements
Véhicules routiers — Interface de véhicule pour contrôle technique
périodique électronique (ePTI) —
Partie 1: Exigences d’application et de communication
Reference number
©
ISO 2021
© ISO 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2021 – All rights reserved

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