National foreword

This British Standard is the UK implementation of ISO 13209‑4:2024. It supersedes BS ISO 13209‑4:2021, which is withdrawn.

The UK participation in its preparation was entrusted to Technical Committee AUE/16, Data Communication (Road Vehicles).

A list of organizations represented on this committee can be obtained on request to its committee manager.

Contractual and legal considerations

This publication has been prepared in good faith, however no representation, warranty, assurance or undertaking (express or implied) is or will be made, and no responsibility or liability is or will be accepted by BSI in relation to the adequacy, accuracy, completeness or reasonableness of this publication. All and any such responsibility and liability is expressly disclaimed to the full extent permitted by the law.

This publication is provided as is, and is to be used at the recipient’s own risk.

The recipient is advised to consider seeking professional guidance with respect to its use of this publication.

This publication is not intended to constitute a contract. Users are responsible for its correct application.

Compliance with a British Standard cannot confer immunity from legal obligations.

This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 November 2024.

Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of ISO document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

ISO draws attention to the possibility that the implementation of this document may involve the use of (a) patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a) patent(s) which may be required to implement this document. However, implementers are cautioned that this may not represent the latest information, which may be obtained from the patent database available at www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.

This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31, Data communication.

This second edition cancels and replaces the first edition (ISO 13209‑4:2021), which has been technically revised.

The main changes are as follows:

ComInterface extension: added ability to select interfaces and control security access for DoIP, harmonized order of the ConnectionStates enumeration;
DataType extension: added initialization of Structures, StructureLiterals and addition of MIME types for Resource Locations;
DiagComPlus extension: added terms to access timestamps for Requests and Responses, and support of Inline-Mapping outside of diagnostic services. Harmonized order of the ComChannelState enumeration;
DiagDataBrowsingPlus extension: IsDiagTroubleCodeParameter term added;
EcuConfiguration extension: completely re-designed for a more generic approach to accessing configuration data;
FlashPlus extension: new action TransferSegment added;
Util extension: new term EscapeToRegularExpression added;
StateVariable extension: state variables modified from Write-only to No-reading across documents. The whole extension is DEPRECATED!
XML extension: New Action ValidateXMLFromByteField added;
Correction and clarification of the documentation text in all extensions.

This edition is not backward compatible with the previous one, because terms are deleted and term parameters are modified.

The incompatible changes are as follows:

ExternalServiceProvider extension: parameter providerType added to GetServiceProviderFromEvent, to ensure type safety.

Additionally the following new extensions are introduced:

Range;
EcuStateChart.

A list of all parts in the ISO 13209 series can be found on the ISO website.

Any feedback or questions on this document should be directed to the user’s national standards body. A complete listing of these bodies can be found at www.iso.org/members.html.

Introduction

Diagnostic test sequences are utilized whenever automotive components or functions with diagnostic abilities are being diagnosed, tested, reprogrammed or initialized by off-board test equipment. Test sequences define the succession of interactions between the user (i.e. workshop or assembly line staff), the diagnostic application (the test equipment) and the vehicle communication interface as well as any calculations and decisions that have to be carried out. Test sequences provide a means to define interactive, guided diagnostics or similar test logic.

Today, the automotive industry mainly relies on paper documentation and/or proprietary authoring environmments to document and to implement such test sequences for a specific test application. An author who is setting up engineering, assembly line or service diagnostic test applications implements the required test sequences manually, supported by non-uniform test sequence documentation, most likely using different authoring applications and formats for each specific test application. This redundant effort can be greatly reduced if processes and tools support the OTX concept.

The ISO 13209 series proposes an open and standardized format for the human- and machine-readable description of diagnostic test sequences. The format supports the requirements of transferring diagnostic test sequence logic uniformly between electronic system suppliers, vehicle manufacturers and service dealerships/repair shops.

This document extends the core of the ISO 13209 series with a set of additional, generally usable OTX extensions which are not part of ISO 13209‑3, using the extension mechanism rules described in ISO 13209‑2.

Figure 1 gives an overview of the additional extensions (marked in black) related to the existing extensions in ISO 13209‑3 (marked in white).

The main goals are:

enlargement of the field of application,
ensuring exchangeability between different tools and suppliers,
improvement of OTX code quality,
improvement of standard acceptance.

The following common requirements are covered:

general read-write access to files,
XML processing,
declare data, whose internal properties are unknown,
deep change monitoring in lists or maps,
store arbitrary information on the current runtime,
handling of user-defined data types: structure and enumeration,
ensure correct implementation of OTX test sequences,
support of DoIP,
configuration tasks,
browsing of ODX database,
extend OTX to functionality that is encapsulated in external services, part of a system, a device, a database or a simple library,
functional access to ECUs,
capturing, evaluating and persisting results of test sequences,
transport status information from inside a sequence to the environment,
advanced convenience functionality,
collection of communication data at runtime,
select and modify project and vehicle information's for MVCI systems,
support of variant coding,
enable late bound flashing of ECUs,
access to SQL databases,
evaluating test sequence results in a structured way,
access to information about vehicle network architecture,
state machine,
compressed data exchange.

1 Scope

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

2 Normative references

3 Terms, definitions and abbreviated terms

3.1 Terms and definitions

3.2 Abbreviated terms

4 Requirements

4.1 Basic principles for requirements definition

4.2 Requirement listing

5 Extension overview

5.1 General

5.2 Dependencies

5.3 OTX packaging (PTX)

6 OTX Assertion extension

6.1 Assertion – General

6.2 Assertion – Exceptions

6.3 Assertion – Actions

7 OTX BlackBox extension

7.1 BlackBox – General

7.2 BlackBox – Datatypes

7.3 BlackBox – Variable access

7.4 BlackBox – Terms

8 OTX BusMonitoring extension

8.1 BusMonitoring – General

8.2 BusMonitoring – Datatypes

8.3 BusMonitoring – Enumerations

8.4 BusMonitoring – Exceptions

8.5 BusMonitoring – Variable access

8.6 BusMonitoring – Actions

8.7 BusMonitoring – Terms

9 OTX ComInterface extension

9.1 ComInterface – General

9.2 ComInterface – Datatypes

9.3 ComInterface – Enumerations

9.4 ComInterface – Exceptions

9.5 ComInterface – Variable access

9.6 ComInterface – Actions

9.7 ComInterface – Terms

10 OTX CommonDialogs extension

10.1 CommonDialogs – General

10.2 CommonDialogs – Exceptions

10.3 CommonDialogs – Actions

11 OTX DataType extension

11.1 DataType – General

11.2 DataType – Datatypes

11.3 DataType – Exceptions

11.4 DataType – Variable access

11.5 DataType – Declaration and arguments

11.6 DataType – Signatures

11.7 DataType – Terms

12 OTX DiagComPlus extension

12.1 DiagComPlus – General

12.2 DiagComPlus – Datatypes

12.3 DiagComPlus – Enumerations

12.4 DiagComPlus – Exceptions

12.5 DiagComPlus – Variable access

12.6 DiagComPlus – Actions

12.7 DiagComPlus – Terms

13 OTX DiagConfiguration extension

13.1 DiagConfiguration – General

13.2 DiagConfiguration – Exceptions

13.3 DiagConfiguration – Actions

13.4 DiagConfiguration – Terms

14 OTX DiagDataBrowsingPlus extension

14.1 DiagDataBrowsingPlus – General

14.2 DiagDataBrowsingPlus – Datatypes

14.3 DiagDataBrowsingPlus – Enumerations

14.4 DiagDataBrowsingPlus – Exceptions

14.5 DiagDataBrowsingPlus – Variable access

14.6 DiagDataBrowsingPlus – Terms

15 OTX EcuConfiguration extension

15.1 EcuConfiguration – General

15.2 EcuConfiguration – Datatypes

15.3 EcuConfiguration – Exceptions

15.4 EcuConfiguration – Variable access

15.5 EcuConfiguration – Actions

15.6 EcuConfiguration – Terms

16 OTX EcuStateChart extension

16.1 EcuStateChart – General

16.2 EcuStateChart – Datatypes

16.3 EcuStateChart – Exceptions

16.4 EcuStateChart – Variable access

16.5 EcuStateChart – Terms

17 OTX EventPlus extension

17.1 EventPlus – General

17.2 EventPlus – Exceptions

17.3 EventPlus – Terms

18 OTX ExternalServiceProvider extension

18.1 ExternalServiceProvider – General

18.2 ExternalServiceProvider – Datatypes

18.3 ExternalServiceProvider – Enumerations

18.4 ExternalServiceProvider – Exceptions

18.5 ExternalServiceProvider – Variable access

18.6 ExternalServiceProvider – Declaration and arguments

18.7 ExternalServiceProvider – Signatures

18.8 ExternalServiceProvider – Actions

18.9 ExternalServiceProvider – Terms

19 OTX File extension

19.1 File – General

19.2 File – Datatypes

19.3 File – Exceptions

19.4 File – Variable access

19.5 File – Actions

19.6 File – Terms

20 OTX FlashPlus extension

20.1 FlashPlus – General

20.2 FlashPlus – Exceptions

20.3 FlashPlus – Actions

20.4 FlashPlus – Terms

21 OTX Persistence extension

21.1 Persistence – General

21.2 Persistence – Exceptions

21.3 Persistence – Actions

22 OTX Range extension

22.1 Range – General

22.2 Range – Datatypes

22.3 Range – Enumerations

22.4 Range – Exceptions

22.5 Range – Variable access

22.6 Range – Actions

22.7 Range – Terms

23 OTX SQL extension

23.1 SQL – General

23.2 SQL – Datatypes

23.3 SQL – Exceptions

23.4 SQL – Variable access

23.5 SQL – Actions

23.6 SQL – Terms

24 OTX StateMachineProcedure extension

24.1 StateMachineProcedure – General

24.2 StateMachineProcedure – Datatypes

24.3 StateMachineProcedure – Procedures

25 OTX StateVariable extension

25.1 StateVariable – General

25.2 StateVariable – Declaration and arguments

26 OTX TestResultHandling extension

26.1 TestResultHandling – General

26.2 TestResultHandling – Datatypes

26.3 TestResultHandling – Enumerations

26.4 TestResultHandling – Exceptions

26.5 TestResultHandling – Variable access

26.6 TestResultHandling – Declaration and arguments

26.7 TestResultHandling – Actions

26.8 TestResultHandling – Terms

27 OTX Util extension

27.1 Util – General

27.2 Util – Exceptions

27.3 Util – Terms

28 OTX VehicleInfo extension

28.1 VehicleInfo – General

28.2 VehicleInfo – Datatypes

28.3 VehicleInfo – Enumerations

28.4 VehicleInfo – Exceptions

28.5 VehicleInfo – Variable access

28.6 VehicleInfo – Terms

29 OTX XML extension

29.1 XML – General

29.2 XML – Datatypes

29.3 XML – Exceptions

29.4 XML – Variable access

29.5 XML – Actions

29.6 XML – Terms

30 OTX ZipHandling extension

30.1 ZipHandling – General

30.2 ZipHandling – Exceptions

30.3 ZipHandling – Actions

Bibliography

BS ISO 13209-4:2024

Road vehicles. Open Test sequence eXchange format (OTX) - Expanded extensions interface definition

Current

Published:

30 Nov 2024