ISO 13185-4:2020

Intelligent transport systems - Vehicle interface for provisioning and support of ITS Services - Part 4: Unified vehicle interface protocol (UVIP) conformance test specification

This document specifies a conformance test for a UVIP server and client system developer assessment of self-conformance of the supplier's UVIP server and client system. The conformance test cases follow the use cases definition of ISO 13185-1 and the requirements stated in ISO 13185-2 and ISO 13185-3. The purpose of this document is to provide information to the UVIP server and client system provider to build and test the UVIP server and client system against the conformance test cases.

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)

General Information

• Status: Published
• Publication Date: 10-May-2020
• ICS: 03.220.01 - Transport in general
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 17 - Nomadic Devices in ITS Systems
• Current Stage: 9060 - Close of review
• Completion Date: 02-Dec-2030

Relations

• Consolidated By: ISO 128-2:2022 - Technical product documentation (TPD) - General principles of representation - Part 2: Basic conventions for lines
• Effective Date: 06-Jun-2022

Overview

ISO 13185-4:2020 defines the conformance test specification for the Unified Vehicle Interface Protocol (UVIP) used in Intelligent Transport Systems (ITS). The document provides a structured Conformance Test Plan (CTP) and detailed Conformance Test Cases (CTCs) that enable UVIP server and client system developers and suppliers to perform self-assessment of their implementations. The tests map to the use cases in ISO 13185-1 and the requirements in ISO 13185-2 and ISO 13185-3.

Key topics and technical requirements

• Conformance Test Plan (CTP) principles: guidance on how CTCs are defined, clustered and executed, including test structure and result criteria.
• CTC structure and lifecycle: each test case includes configuration, preamble (setup state), test execution, postamble, and clear result criteria.
• CTC clustering: tests are organized into functional clusters that reflect UVIP use cases:
  • Cluster 1 - Browsing vehicle ITS service groups (V‑ITS‑SG), ECUs and supported data IDs
  • Cluster 2 - Requesting vehicle and ECU data values (single and repeated use, data type/text queries)
  • Cluster 3 - Diagnostic Trouble Codes (DTCs): request, additional data, clearing, SendOnChange reporting
  • Cluster 4 - Unsolicited V‑ITS‑SG messages (SendOnEvent scenarios for emergency, critical/safety/warning situations)
  • Cluster 5 - Real‑time data transmission (real‑time data ID measurement and DTC reporting)
  • Cluster 6 - Controlling/adjusting vehicle equipment and customer profile settings
• Traceability to ISO 13185 parts 1–3: CTCs align with the use cases and normative requirements from other parts of the ISO 13185 series.
• Test system setup and clustering rules: instructions for system under test topology and how tests are grouped for efficient validation.

Practical applications and who uses this standard

• Vehicle OEMs and Tier‑1 suppliers: validate UVIP server/client implementations before integration into production vehicles.
• ITS service providers and integrators: verify interoperability of ITS services that rely on vehicle interfaces.
• Test laboratories and QA teams: develop conformance test rigs and run standardized CTCs for certification preparation.
• Regulators and certification bodies: reference a common, traceable conformance specification for compliance assessment.
• Software developers building telematics, remote diagnostics, real‑time data streaming, and vehicle control applications that depend on UVIP.

Related standards and keywords

• Related: ISO 13185-1, ISO 13185-2, ISO 13185-3 (use cases and protocol requirements)
• SEO keywords: ISO 13185-4, UVIP, Unified Vehicle Interface Protocol, conformance test specification, Intelligent Transport Systems, vehicle interface, V-ITS-SG, DTC, ECU, data ID, real-time vehicle data, ITS interoperability.

Standards Content (Sample)

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: [phone]
Fax: [phone]
Email: [e-mail]
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) .15
8.3 CTC_UC 3.3 – Clearing DTCs .15
8.3.1 Overview .15
8.3.2 Test purpose .15
8.3.3 Configuration .16
8.3.4 Preamble (setup state) .16
8.3.5 Test execution .16
8.3.6 Postamble (setup state) .16
8.4 CTC_UC 3.4 – SendOnChange – Provide DTC and status .17
8.4.1 Overview .17
9 CT cluster 4 – Unsolicited V-ITS-SG messages.17
9.1 CTC_UC 4.1 – SendOnEvent — Emergency situation .17
9.1.1 Overview .17
9.2 CTC_UC 4.2 – SendOnEvent — Critical driving situation .17
9.2.1 Overview .17
9.3 CTC_UC 4.3 – SendOnEvent — Safety situation .17
9.3.1 Overview .17
9.4 CTC_UC 4.4 – SendOnEvent — Warning situation .17
9.4.1 Overview .17
9.5 CTC_UC 4.5 – SendOnEvent — Data ID value matches threshold .18
9.5.1 Overview .18
10 CT cluster 5 – Real-time data transmission .18
10.1 CTC_UC 5.1 – Real-time data ID value measurement .18
10.1.1 Overview .18
10.2 CTC_UC 5.2 – Real-time DTC reporting .18
10.2.1 Overview .18
11 CT cluster 6 – Controlling /adjusting various equipment of the vehicle .18
11.1 CTC_UC 6.1 – Learn settings of customer profile .18
11.1.1 Overview .18
11.1.2 Test purpose .19
11.1.3 Configuration .19
11.1.4 Preamble (setup state) .19
11.1.5 Test execution .19
11.1.6 Postamble (setup state) .20
iv © ISO 2020 – All rights reserved

11.2 CTC_UC 6.2 – Control convenience system .20
11.2.1 Overview .20
11.2.2 Test purpose .20
11.2.3 Configuration .20
11.2.4 Preamble (setup state) .20
11.2.5 Test execution .20
11.2.6 Postamble (setup state) .21
11.3 CTC_UC 6.3 – Control charging for EV .21
11.3.1 Overview .21
11.3.2 Test purpose .21
11.3.3 Configuration .21
11.3.4 Preamble (setup state) .21
11.3.5 Test execution .22
11.3.6 Postamble (setup state) .22
12 CT cluster 7 – Writing short- and long-term data to V-ITS-SG .22
12.1 CTC_UC 7.1 – Write data to V-ITS-SG’s memory .22
12.1.1 Overview .22
12.1.2 Test purpose .22
12.1.3 Configuration .23
12.1.4 Preamble (setup state) .23
12.1.5 Test execution .23
12.1.6 Postamble (setup state) .23
12.2 CTC_UC 7.2 – Write vehicle profile to V-ITS-SG’s memory .23
12.2.1 Overview .23
12.3 CTC_UC 7.3 – Enable/disable functional system related data IDs .24
12.3.1 Overview .24
12.4 CTC_UC 7.4 – Write data ID thresholds to V-ITS-SG’s memory .24
12.4.1 Overview .24
13 CT cluster 8 – V-ITS-SG accessibility restrictions and firewall protection cluster .24
13.1 CTC_UC 8.1 – Secure access to V-ITS-SG .24
13.1.1 Overview .24
13.1.2 Test purpose .24
13.1.3 Configuration .24
13.1.4 Preamble (setup state) .24
13.1.5 Test execution .24
13.1.6 Postamble (setup state) .25
13.2 CTC_UC 8.2 – Request V-ITS-SG firewall status .25
13.2.1 Overview .25
13.3 CTC_UC 8.3 – Configuration of V-ITS-SG firewall .25
13.3.1 Overview .25
13.3.2 Test purpose .25
13.3.3 Configuration .25
13.3.4 Preamble (setup state) .26
13.3.5 Test execution .26
13.3.6 Postamble (setup state) .26
14 CT cluster 9 – V-ITS-SG special features .26
14.1 CTC_UC 9.1 – General data exchange .26
14.1.1 Overview .26
14.2 CTC_UC 9.2 – V-ITS-SG activation mode .27
14.2.1 Overview .27
14.3 CTC_UC 9.3 – Upload EventLogFile from V-ITS-SG .27
14.3.1 Overview .27
14.3.2 Test purpose .27
14.3.3 Configuration .27
14.3.4 Preamble (setup state) .27
14.3.5 Test execution .27
14.3.6 Postamble (setup state) .28
15 CT cluster 10 – Vehicle diagnostics .28
15.1 CTC_UC 10.1 – Perform functional group OBD .28
15.1.1 Overview .28
15.1.2 Test purpose .28
15.1.3 Configuration .28
15.1.4 Preamble (setup state) .28
15.1.5 Test execution .28
15.1.6 Postamble (setup state) .29
15.2 CTC_UC 10.2 – Perform enhanced OBD .29
15.2.1 Overview .29
15.2.2 Test purpose .29
15.2.3 Configuration .29
15.2.4 Preamble (setup state) .29
15.2.5 Test execution .29
15.2.6 Postamble (setup state) .30
15.3 CTC_UC 10.3 – Upload VSOCLogFile from V-ITS-SG .30
15.3.1 Overview .30
15.3.2 Test purpose .30
15.3.3 Configuration .30
15.3.4 Preamble (setup state) .30
15.3.5 Test execution .30
15.3.6 Postamble (setup state) .31
16 CT cluster 11 – Electric vehicle system status .31
16.1 CTC_UC 11.1 – Monitor battery charge status . .31
16.1.1 Overview .31
16.1.2 Test purpose .31
16.1.3 Configuration .31
16.1.4 Preamble (setup state) .31
16.1.5 Test execution .31
16.1.6 Postamble (setup state) .32
16.2 CTC_UC 11.2 – Monitor connection between charging station and EV .32
16.2.1 Overview .32
16.2.2 Test purpose .32
16.2.3 Configuration .32
16.2.4 Preamble (setup state) .32
16.2.5 Test execution .32
16.2.6 Postamble (setup state) .33
16.3 CTC_UC 11.3 – Battery charge start/stop notification .33
16.3.1 Overview .33
17 CT cluster 12 – V-ITS-SG maintenance .33
17.1 CTC_UC 12.1 – Update core software of V-ITS-SG .33
17.1.1 Overview .33
17.1.2 Test purpose .33
17.1.3 Configuration .34
17.1.4 Preamble (setup state) .34
17.1.5 Test execution .34
17.1.6 Postamble (setup state) .34
17.2 CTC_UC 12.2 – Perform a Reset in V-ITS-SG .34
17.2.1 Overview .34
17.2.2 Test purpose .34
17.2.3 Configuration .35
17.2.4 Preamble (setup state) .35
17.2.5 Test execution .35
17.2.6 Postamble (setup state) .35
17.3 CTC_UC 12.3 – Perform a reset in V-ITS-SG .35
17.3.1 Overview .35
17.3.2 Test purpose .35
vi © ISO 2020 – All rights reserved

17.3.3 Configuration .35
17.3.4 Preamble (setup state) .35
17.3.5 Test execution .36
17.3.6 Postamble (setup state) .36
17.4 CTC_UC 12.4 – Upload V-ITS-SG configuration file .36
17.4.1 Overview .36
17.4.2 Test purpose .36
17.4.3 Configuration .36
17.4.4 Preamble (setup state) .36
17.4.5 Test execution .36
17.4.6 Postamble (setup state) .37
17.5 CTC_UC 12.5 – Download V-ITS-SG configuration file .37
17.5.1 Overview .37
17.5.2 Test purpose .37
17.5.3 Configuration .37
17.5.4 Preamble (setup state) .37
17.5.5 Test execution .37
17.5.6 Postamble (setup state) .38
Bibliography .39
Foreword
ISO (the International O
...