ISO 13185-4:2020

INTERNATIONAL ISO
STANDARD 13185-4
First edition
2020-05
Intelligent transport systems —
Vehicle interface for provisioning and
support of ITS Services —
Part 4:
Unified vehicle interface protocol
(UVIP) conformance test specification
Systèmes de transport intelligents - Interface véhicule pour la
fourniture et le support de services —
Partie 4: Spécification d'essai de conformité du protocole d'interface
véhicule unifié (PIVU)
Reference number
©
ISO 2020
© ISO 2020
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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved

Contents Page
Foreword .viii
Introduction .ix
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 1
4 Conventions . 2
5 Conformance test plan (CTP) basic principles and clustering . 2
5.1 Basic principles for CTC definition . 2
5.2 CTC structure . 3
5.2.1 CTC – General structure . 3
5.2.2 Result criteria . 4
5.3 CTC system setup . 4
5.4 CTC clustering . 5
5.4.1 General. 5
5.4.2 Main CTC clusters . 5
6 CT cluster 1 – Requesting V-ITS-SG and vehicle identification related information .6
6.1 CTC_UC 1.1 – Browsing available V-ITS-SGs . 6
6.1.1 Overview . 6
6.1.2 Test purpose . 6
6.1.3 Configuration . 7
6.1.4 Preamble (setup state) . 7
6.1.5 Test execution . 7
6.1.6 Postamble (setup state) . 8
6.2 CTC_UC 1.2 – Browsing supported ECUs . 8
6.2.1 Overview . 8
6.2.2 Test purpose . 8
6.2.3 Configuration . 9
6.2.4 Preamble (setup state) . 9
6.2.5 Test execution . 9
6.2.6 Postamble (setup state) . 9
6.3 CTC_UC 1.3 – Browsing supported data Ids . 9
6.3.1 Overview . 9
6.3.2 Test purpose . 9
6.3.3 Configuration . 9
6.3.4 Preamble (setup state) .10
6.3.5 Test execution .10
6.3.6 Postamble (setup state) .10
7 CT cluster 2 – Requesting vehicle and ECU data values .10
7.1 CTC_UC 2.1 – Requesting data ID values for single usage .10
7.1.1 Overview .10
7.1.2 Test purpose .10
7.1.3 Configuration .10
7.1.4 Preamble (setup state) .11
7.1.5 Test execution .11
7.1.6 Postamble (setup state) .11
7.2 CTC_UC 2.2 – Requesting data ID values for repeated usage .12
7.2.1 Overview .12
7.2.2 Test purpose .12
7.2.3 Configuration .12
7.2.4 Preamble (setup state) .12
7.2.5 Test execution .12
7.2.6 Postamble (setup state) .13
7.3 CTC_UC 2.3 – Requesting data ID text and data type information .13
7.3.1 Overview .13
7.4 CTC_UC 2.4 – Requesting data type definitions .13
7.4.1 Overview .13
7.5 CTC_UC 2.5 – Requesting all available text and data type information .13
7.5.1 Overview .13
8 CT cluster 3 – Requesting and clearing DTCs and related data .13
8.1 CTC_UC 3.1 – Requesting DTCs .13
8.1.1 Overview .13
8.1.2 Test purpose .13
8.1.3 Configuration .14
8.1.4 Preamble (setup state) .14
8.1.5 Test execution .14
8.1.6 Postamble (setup state) .14
8.2 CTC_UC 3.2 – Requesting additional DTC data .14
8.2.1 Overview .14
8.2.2 Test purpose .14
8.2.3 Configuration .15
8.2.4 Preamble (setup state) .15
8.2.5 Test execution .15
8.2.6 Postamble (setup state) .
...