Road vehicles — Standardized access to automotive repair and maintenance information (RMI) — Part 2: Technical requirements

ISO 18541-2:2014 includes technical requirements which are related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators. ISO 18541-2:2014 specifies the minimum set of technical requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1.

Véhicules routiers — Normalisation de l'accès aux informations relatives à la réparation et à la maintenance pour l'automobile (RMI) — Partie 2: Exigences techniques

ISO 18541-2:2014 comprend les « exigences techniques » liées aux systèmes d'informations relatives à la réparation et à la maintenance pour l'automobile (RMI) dans le but de normaliser l'accès des opérateurs indépendants aux RMI. La présente partie de la norme spécifie l'ensemble minimal d'exigences techniques concernant le système RMI d'un constructeur de véhicules. Ces exigences reflèteront les besoins qui découlent des cas d'utilisation spécifiés dans l'ISO 18541-1.

General Information

Status
Withdrawn
Publication Date
17-Sep-2014
Withdrawal Date
17-Sep-2014
Current Stage
9599 - Withdrawal of International Standard
Start Date
16-Jun-2021
Completion Date
16-Jun-2021
Ref Project

RELATIONS

Buy Standard

Standard
ISO 18541-2:2014 - Road vehicles -- Standardized access to automotive repair and maintenance information (RMI)
English language
30 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO 18541-2:2014 - Road vehicles -- Standardized access to automotive repair and maintenance information (RMI)
English language
30 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO 18541-2:2014 - Véhicules routiers -- Normalisation de l'acces aux informations relatives a la réparation et a la maintenance pour l'automobile (RMI)
French language
37 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO
STANDARD 18541-2
First edition
2014-09-15
Road vehicles — Standardized access
to automotive repair and maintenance
information (RMI) —
Part 2:
Technical requirements
Véhicules routiers — Normalisation de l’accès aux informations
relatives à la réparation et à la maintenance pour l’automobile
(RMI) —
Partie 2: Exigences techniques
Reference number
ISO 18541-2:2014(E)
ISO 2014
---------------------- Page: 1 ----------------------
ISO 18541-2:2014(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2014

All rights reserved. Unless otherwise specified, 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
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2014 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 18541-2:2014(E)
Contents Page

Foreword ..........................................................................................................................................................................................................................................v

Introduction ................................................................................................................................................................................................................................vi

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms, definitions, symbols and abbreviated terms ....................................................................................................... 1

3.1 Terms and definitions ....................................................................................................................................................................... 1

3.2 Abbreviated terms ............................................................................................................................................................................... 2

4 Conventions ............................................................................................................................................................................................................... 3

5 Requirements overview and principles ....................................................................................................................................... 3

5.1 Basic principles for requirements definition ................................................................................................................ 3

5.2 Requirements clustering ................................................................................................................................................................ 3

6 Requirements cluster 1 — Access-related data administration .........................................................................7

6.1 [TREQ-1] General access-related data administration ......................................................................................... 7

6.2 [TREQ-2], [TREQ-3] Administration of IO and IO employee data by the VM .................................... 7

6.3 [TREQ-4] Administration of payment data by the VM .......................................................................................... 8

6.4 [TREQ-5] Administration of access event data by the VM ................................................................................ 9

6.5 [TREQ-6] Administration of access event data to security-related RMI by the VM..................... 9

7 Requirements cluster 2 — IT architecture .............................................................................................................................10

7.1 [TREQ-7] Conceptual architecture ......................................................................................................................................10

7.2 [TREQ-8] Implementation principles ...............................................................................................................................12

8 Requirements cluster 3 — External interfaces ..................................................................................................................15

8.1 [TREQ-9] Vehicle communication interface (VCI) .................................................................................................15

8.2 [TREQ-10] Trust centre (certificate management) ..............................................................................................19

8.3 [TREQ-11] Parts ordering for security-related features ..................................................................................19

8.4 [TREQ-12] Partnered accessory provider systems ..............................................................................................19

9 Requirements cluster 4 — Technical infrastructure ...................................................................................................20

9.1 [TREQ-13] Type of device...........................................................................................................................................................20

9.2 [TREQ-14] Hardware features ................................................................................................................................................20

9.3 [TREQ-15] Operating systems ................................................................................................................................................20

9.4 [TREQ-16] Web browsers ...........................................................................................................................................................20

9.5 [TREQ-17] Presentation formats for information packages ........................................................................21

9.6 [TREQ-18] Internet connection .............................................................................................................................................21

9.7 [TREQ-19] Performance of the VM RMI system ......................................................................................................21

10 Requirements cluster 5 — Co-existence of VM software on IO client .........................................................22

10.1 [TREQ-20] Requirements for installing VM-specific software on the IO client ...........................22

10.2 [TREQ-21] Requirements for updating of installed VM data and applications on the

IO client ......................................................................................................................................................................................................23

10.3 [TREQ-22] Requirements for the operation of VM-specific software on the IO client ..........23

10.4 [TREQ-23] Requirements for the uninstalling of VM-specific software on the IO client .....24

10.5 [TREQ-24] Requirements for restoring in case of an abnormal termination of the VM-

specific software on the IO client .........................................................................................................................................24

11 Requirements cluster 6 — Operations .......................................................................................................................................25

11.1 [TREQ-25] VM RMI system availability time..............................................................................................................25

11.2 [TREQ-26] Support for the usage of the VM RMI system ................................................................................25

11.3 [TREQ-27] Operation of the IO PC.......................................................................................................................................26

12 Requirements cluster 7 — Functional user interface .................................................................................................26

12.1 [TREQ-28] Functional user interface ................................................................................................................................26

Annex A (informative) PC specification ..........................................................................................................................................................28

© ISO 2014 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 18541-2:2014(E)

Bibliography .............................................................................................................................................................................................................................29

iv © ISO 2014 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 18541-2:2014(E)
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 documents 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).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www.iso.org/patents).

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

constitute an endorsement.

For an explanation on the meaning of ISO specific terms and expressions related to conformity

assessment, as well as information about ISO’s adherence to the WTO principles in the Technical Barriers

to Trade (TBT) see the following URL: Foreword - Supplementary information

ISO 18541-2:2013 was prepared by the European Committee for Standardization (CEN) Technical

Committee CEN/TC 301, Road vehicles, in collaboration with ISO Technical Committee ISO/TC 22, Road

vehicles, Subcommittee SC 3, Electrical and electronic equipment, in accordance with the agreement on

technical cooperation between ISO and CEN (Vienna Agreement).

ISO 18541 consists of the following parts, under the general title Road vehicles — Standardized access to

automotive repair and maintenance information (RMI):
— Part 1: General information and use case definition
— Part 2: Technical requirements
— Part 3: Functional user interface requirements
— Part 4: Conformance test
© ISO 2014 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 18541-2:2014(E)
Introduction

This set of standards includes the requirements to be fulfilled by Repair and Maintenance Information

(RMI) systems as applied by the European Commission — Enterprise and Industry Directorate-General,

[[5]]

Consumer goods — Automotive industry EC mandate M/421, dated Brussels, 21 January 2008.

This mandate relates to the EC type-approval system for vehicles falling into the scopes of Directives

[8] [6] [7]

70/156/EEC (replaced by 2007/46/EC ), 2002/24/EC and 2003/37/EC and, in particular, to

requirements for access to vehicle repair and maintenance information by independent operators.

This International Standard only covers access to automotive repair and maintenance information for

light passenger and commercial vehicles (see NOTE 1) and heavy duty vehicles (see NOTE 2) based on

[8]
Directive 70/156/EEC (replaced by 2007/46/EC ).

The purpose of the EC Mandate M/421 is to develop a standard or set of standards which specify the

requirements to provide standardized access to automotive repair and maintenance information (RMI)

for independent operators.

The information included in this part of ISO 18541 derives from the legislative requirements on European

level in the field of RMI and related security requirements and can be referenced by legislation in other

countries.

NOTE 1 Regulation (EC) No 715/2007 of the european parliament and of the council of 20 June 2007 on

type-approval of motor vehicles with respect to emissions from light passenger and commercial vehicles

(Euro 5 and Euro 6) and on access to vehicle repair and maintenance information and Commission Regulation

(EC) No 692/2008 of 18 July 2008 implementing and amending Regulation (EC) No 715/2007 of the European

Parliament and of the Council on type-approval of motor vehicles with respect to emissions from light passenger

and commercial vehicles (Euro 5 and Euro 6) and on access to vehicle repair and maintenance information and

amending Commission Regulation (EU) No 566/2011 of 8 June 2011 amending Regulation (EC) No 715/2007 of

the European Parliament and of the Council and Commission Regulation (EC) No 692/2008 as regards access to

vehicle repair and maintenance information.

NOTE 2 Regulation (EC) No 595/2009 of the european parliament and of the council of 18 June 2009 on type-

approval of motor vehicles with respect to emissions from heavy duty vehicles (Euro VI) and on access to vehicle

repair and maintenance information, Commission Regulation (EU) No 582/2011 of 25 May 2011 implementing

and amending Regulation (EC) No 595/2009 of the European Parliament and of the Council with respect to

emissions from heavy duty vehicles (Euro VI), and Commission Regulation (EU) No 64/2012 of 23 January 2012

amending Regulation (EU) No 582/2011 2011 implementing and amending Regulation (EC) No 595/2009 of the

European Parliament and of the Council with respect to emissions from heavy duty vehicles (Euro VI).

vi © ISO 2014 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 18541-2:2014(E)
Road vehicles — Standardized access to automotive repair
and maintenance information (RMI) —
Part 2:
Technical requirements
1 Scope

This part of ISO 18541 includes technical requirements which are related to automotive repair and

maintenance information (RMI) systems in order to standardize access to RMI for independent operators.

This part of ISO 18541 specifies the minimum set of technical requirements related to a vehicle

manufacturer’s RMI system. These requirements will reflect the deriving needs from the use cases as

specified in ISO 18541-1.
2 Normative references

The following documents, in whole or in part, are normatively referenced in this document and are

indispensable for its application. For dated references, only the edition cited applies. For undated

references, the latest edition of the referenced document (including any amendments) applies.

ISO 18541-1:2014, Road vehicles — Standardized access to automotive RMI — Part 1: General information

and use case definition

ISO 18541-3, Road vehicles — Standardized access to automotive repair and maintenance information

(RMI) — Part 3: Functional user interface requirements

ISO 22900-2, Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: Diagnostic

protocol data unit application programming interface (D-PDU API)
SAE J2534-1, Recommended Practice for Pass-Thru Vehicle Programming
SAE J2534-2, Optional Pass-Thru Features
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 18541-1 apply.

© ISO 2014 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO 18541-2:2014(E)
3.2 Abbreviated terms
API application programming interface
CSP certificate status protocol
DB database
DLC data link cable
DLL dynamic link library
D-PDU diagnostic – protocol data unit
DVD optical disc storage media format
ECU electronic control unit
FAQ frequently asked questions
GB giga-byte
GHz giga-hertz
GMT Greenwich mean time
IO independent operator
IT information technology
LAN local area network
MVCI modular vehicle communication interface
NAT network address translation
OBD on-board diagnostics
OCSP online certificate status protocol
PC personal computer
PKCS public key certificate status
RMI repair and maintenance information
RS232 recommended standard 232
SERMI security-related repair and maintenance information
TREQ- technical requirement
TC trust centre
USB universal serial bus
VAT No. value added tax number
VM vehicle manufacturer
WWH-OBD world-wide harmonized on-board diagnostics
2 © ISO 2014 – All rights reserved
---------------------- Page: 8 ----------------------
ISO 18541-2:2014(E)
4 Conventions

This part of ISO 18541 is based on the conventions discussed in the OSI Service Conventions

(ISO/IEC 10731).
5 Requirements overview and principles
5.1 Basic principles for requirements definition

Basic principles have been established as a guideline to define the requirements.

— BP1: The requirements stated in this part of ISO 18541 shall not specify any implementation details.

— BP2: Requirements shall be expressed in terms of performance rather than design or descriptive

characteristics. This approach leaves maximum freedom to technical development.

— BP3: A requirement is identified by a TREQ-xx, where ‘xx’ is the requirement number. Each

requirement consists of a “Main title”, “Requirement definition”, “Requirement description”,

“Explanatory / Example” and “Classification”.

— BP4: The requirements in clusters 4 and 5 in this part of ISO 18541 have been formulated with the

aim of minimizing the number of IO clients (PC, Laptop, etc.) required to access different VM RMI

systems.
5.2 Requirements clustering

Figure 1 illustrates the technical requirements clusters. Figure 1 shall provide an overview about all

technical requirements clusters and the specific technical requirements. Each technical requirement

is identified by the mnemonic “TREQ-” and an alpha-numeric number. The name of the technical

requirement is descriptive for the area.
© ISO 2014 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO 18541-2:2014(E)
Figure 1 — Overview about the technical requirements clusters

Table 1 provides an overview of the main categories of standardized access to automotive RMI

requirements. A requirement category shall have at least one requirement.
4 © ISO 2014 – All rights reserved
---------------------- Page: 10 ----------------------
ISO 18541-2:2014(E)
Table 1 — Main requirements clusters
# - Main title Brief description Technical requirements
of cluster [TREQ] reference

1 – Access- Describes the main data types to be administered by the VM [TREQ-1] General access-

related data RMI System and the requirements for the appropriate manage- related data administration

administration ment procedures in order to comply with the standardized
[TREQ-2] Administration of
access to RMI.
IO data by the VM
RMI requirements related to cluster access-related data admin-
[TREQ-3] Administration of
istration are
IO employee data by the VM
— requirements for the administration of IO data by the
[TREQ-4] Administration of
VM,
payment data by the VM
— requirements for the administration IO employee data
[TREQ-5] Administration of
by the VM,
access event data by the VM
— requirements for the administration of payment data
[TREQ-6] Administration of
by the VM;
access event data to security-
— requirements for the administration of access event related RMI by the VM
data by the VM;
— requirements for the administration of access event
data to security-related RMI by the VM.

2 – IT Describes requirements for the main IT components and inter- [TREQ-7] Conceptual archi-

architecture faces at the different IT architectural levels. tecture
RMI requirements related to cluster IT architecture are [TREQ-8] Implementation
principles
— requirements for the conceptual architecture;
— requirements for the implementation principles.

3 – External Describes the requirements for communication interfaces [TREQ-9] Vehicle communi-

interfaces other than the user interface. cation interface (VCI)

RMI requirements related to cluster external interfaces are [TREQ-10] Trust centre (cer-

tificate management)
— requirements for the vehicle communication interface
(VCI); [TREQ-11] Parts ordering for
security-related features
— requirements for the trust centre (certificate manage-
ment); [TREQ-12] Partnered acces-
sory provider systems
— requirements for the parts ordering for security-
related features;
— requirements for the partnered accessory provider
systems.
© ISO 2014 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO 18541-2:2014(E)
Table 1 (continued)
# - Main title Brief description Technical requirements
of cluster [TREQ] reference

4 – Technical Compatibility conditions, minimum requirements for compo- [TREQ-13] Type of device

infrastructure nents and Internet connection parameters to give an accept-
[TREQ-14] Hardware fea-
able performance. This cluster intends to define minimal
tures
development guiding rules that shall be followed by the VM in

order to ensure compatibility between VM RMI systems. Com- [TREQ-15] Operating sys-

patibility issues that may occur shall be managed by the Forum tems
SERMI.
[TREQ-16] Web browsers
This requirements cluster specifies the technical infrastruc-
[TREQ-17] Presentation
ture recommendations which are:
formats for information
— requirements related to type of device; packages
— requirements related to hardware features; [TREQ-18] Internet connec-
tion
— requirements related to operating systems, runtime
languages, libraries;
[TREQ-19] Performance of
the VM RMI system
— requirements related to Web browsers;
— requirements related to presentation formats for
information packages;
— requirements related to internet connection;
— requirements related to performance of the VM RMI
system.

5 – Co-exist- This requirements cluster specifies the co-existence of VM [TREQ-20] Requirements for

ence of VM software on the IO client. installing VM-specific soft-
software on IO ware on the IO client
— requirements for installing VM-specific software on
client
the IO client; [TREQ-21] Requirements for
updating of installed VM data
— Requirements for updating VM-specific software on
and applications on the IO
the IO client;
client
— Requirements for the operation of VM-specific soft-
[TREQ-22] Requirements for
ware on the IO client;
the operation of VM-specific

— Requirements for the uninstalling of VM-specific soft- software on the IO client

ware on the IO client;
[TREQ-23] Requirements for
the uninstalling of VM-spe-
— Requirements for restoring in case of an abnormal
cific software on the IO client
termination of the VM-specific software on the IO client.
The VM software shall be developed according to acknowl- [TREQ-24] Requirements

edged quality criteria for the co-existence of VM applications for restoring in case of an

installed on the client side. abnormal termination of the
VM-specific software on the
IO client

6 – Operations This requirements cluster specifies the RMI requirements [TREQ-25] VM RMI system

related to the cluster operations are: availability time
— requirements related to the VM RMI system availabil- [TREQ-26] Support for the
ity time; usage of the VM RMI system

— requirements related to the support for the usage of [TREQ-27] Operation of the

the VM RMI system; IO PC
— requirements related to the operation of the IO PC.

7 – Functional This requirement cluster includes the reference to the [TREQ-28] Requirements

user interface ISO 18541-3 functional user interface of the VM RMI system. cluster 7 – Functional user

interface
6 © ISO 2014 – All rights reserved
---------------------- Page: 12 ----------------------
ISO 18541-2:2014(E)
6 Requirements cluster 1 — Access-related data administration
6.1 [TREQ-1] General access-related data administration

Table 2 defines the requirements for the general access-related data administration.

Table 2 — [TREQ-1] General access-related data administration
REQ # TREQ-1
Main title General access-related data administration

Requirement The VM allows access to the RMI system depending on the storage of some data

definition
— for user registration,
— agreement to terms and conditions,
— any other data required by local legislation,
— for user login and access data recovery,
— for invoicing,
— for physical delivery of material if needed,
[14]
— for logging of any access to security-related RMI see SERMI,

— for logging of any access to ECU replacing/update (in case of liability issues),

— to be able to disable a user see ISO 18541-1 use case UC 1.5 Request to de-register IO

employee;

The administration of this data shall be according to data and privacy protection legislation.

Brief descrip- The VM has to administer data on users, on payment, on access events to security-related RMI

tion and on access events to general RMI content.
Classification Mandatory.
6.2 [TREQ-2], [TREQ-3] Administration of IO and IO employee data by the VM
6.2.1 [TREQ-2] Administration of IO data by the VM
Table 3 defines the requirements for the administration of IO data by the VM.
© ISO 2014 – All rights reserved 7
---------------------- Page: 13 ----------------------
ISO 18541-2:2014(E)
Table 3 — [TREQ-2] Administration of IO data by the VM
REQ # TREQ-2
Main title Requirements for the administration of IO data by the VM

Requirement IO data shall be administered by the VM to enable user access, access data reset and to facili-

definition tate written communication with the IO.
Brief descrip- The following list of IO data shall be administered by the VM:
tion
— IO name,
— IO postal address,
— country,
— postal address for invoicing if different from IO postal address,
— inter-community VAT No.,
— first name, family name of the IO legal representative,

— e-mail address for communication with the IO legal representative in all aspects of the

VM RMI system usage,
— preferred language,

— User ID and password of the IO legal representative (the User ID must be unique in the

VM system),

— optionally a confirmation of the IO approval according to the SERMI scheme if the IO

wants to request access to security-related RMI.
Classification Mandatory.
6.2.2 [TREQ-3] Administration of IO employee data by the VM

Table 4 defines the requirements for the administration of IO employee data by the VM.

Table 4 — [TREQ-3] Administration of IO employee data by the VM
REQ # TREQ-3
Main title Requirements for the administration of IO employee data by the VM

Requirement IO employee data shall be administered by the VM to enable user access, access data reset and

definition to facilitate written communication with the IO employee.
Brief descrip- The following list of user data shall be administered by the VM:
tion
— IO name (see ISO 18541-1:2014, 3.1.14)

— e-mail address for communication with the employee in all aspects of the VM RMI

system usage,
— preferred language,

— User ID and password of the IO employee (the User ID must be unique in the VM sys-

tem),

— optionally a digital certificate ID according to the SERMI scheme if the IO employee

wants to request access to security-related RMI,
— optionally the access level granted for security-related RMI.
Classification Mandatory.
6.3 [TREQ-4] Administration of payment data by the VM

Table 5 defines the requirements for the administration of payment data by the VM.

8 © ISO 2014 – All rights reserved
---------------------- Page: 14 ----------------------
ISO 18541-2:2014(E)
Table 5 — [TREQ-4] Administration of payment data by the VM
REQ # TREQ-4
Main title Requirements for the administration of payment data by the VM

Requirement User data shall be administered by the VM to allow the VM to invoice the user.

definition

Brief descrip- The following user data shall be administered by the VM for the purposes of invoicing for use

tion of the VM MI system.
— Type of subscription;
— Method of payment;
— Subscription period;
— Invoicing address;
— Inter-community VAT No.
Classification Mandatory.
6.4 [TREQ-5] Administration of access event data by the VM

Table 6 defines the requirements for the administration of access event data by the VM.

Table 6 — [TREQ-5] Administration of access event data by the VM
REQ # TREQ-5
Main title Requirements for the administration of access event data by the VM

Requirement Access event data shall be administered by the VM to monitor use of the VM RMI system and

definition take appropriate action if necessary.
Brief descrip- The following access event data shal
...

DRAFT INTERNATIONAL STANDARD ISO/DIS 18541-2
ISO/TC 22/SC 3 Secretariat: DIN
Voting begins on Voting terminates on
2012-07-26 2012-12-26

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION  МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ  ORGANISATION INTERNATIONALE DE NORMALISATION

Road vehicles — Standardized access to automotive repair and
maintenance information (RMI) —
Part 2:
Technical requirements

Véhicules routiers — Normalisation de l'accès aux informations relatives à la réparation et à la maintenance

pour l'automobile (RMI) —
Partie 2: Exigences techniques
ICS 43.040.15; 43.180
ISO/CEN PARALLEL PROCESSING

This draft has been developed within the European Committee for Standardization (CEN), and

processed under the CEN-lead mode of collaboration as defined in the Vienna Agreement.

This draft is hereby submitted to the ISO member bodies and to the CEN member bodies for a parallel

five-month enquiry.

Should this draft be accepted, a final draft, established on the basis of comments received, will be

submitted to a parallel two-month approval vote in ISO and formal vote in CEN.

To expedite distribution, this document is circulated as received from the committee

secretariat. ISO Central Secretariat work of editing and text composition will be undertaken at

publication stage.

Pour accélérer la distribution, le présent document est distribué tel qu'il est parvenu du

secrétariat du comité. Le travail de rédaction et de composition de texte sera effectué au

Secrétariat central de l'ISO au stade de publication.

THIS DOCUMENT IS A DRAFT CIRCULATED FOR COMMENT AND APPROVAL. IT IS THEREFORE SUBJECT TO CHANGE AND MAY NOT BE

REFERRED TO AS AN INTERNATIONAL STANDARD UNTIL PUBLISHED AS SUCH.

IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNOLOGICAL, COMMERCIAL AND USER PURPOSES,

DRAFT INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME

STANDARDS TO WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS.

RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT, WITH THEIR COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF WHICH

THEY ARE AWARE AND TO PROVIDE SUPPORTING DOCUMENTATION.
© International Organization for Standardization, 2012
---------------------- Page: 1 ----------------------
ISO/DIS 18541-2
Copyright notice

This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted

under the applicable laws of the user’s country, neither this ISO draft nor any extract from it may be

reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic,

photocopying, recording or otherwise, without prior written permission being secured.

Requests for permission to reproduce should be addressed to either ISO at the address below or ISO’s

member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO 2012 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/DIS 18541-2
Contents Page

Foreword ............................................................................................................................................................. v

1  Scope ...................................................................................................................................................... 1

2  Normative references ............................................................................................................................ 1

3  Terms, definitions, symbols and abbreviated terms ......................................................................... 2

3.1  Terms and definitions ........................................................................................................................... 2

3.2  Abbreviated terms ................................................................................................................................. 2

4  Conventions ........................................................................................................................................... 3

5  Requirements overview and principles ............................................................................................... 3

5.1  Basic principles for requirements definition ...................................................................................... 3

5.2  Requirements clustering ...................................................................................................................... 4

6  Requirements cluster "access-related data administration" ............................................................ 6

6.1  General ................................................................................................................................................... 6

6.2  Administration of user data by the VM ................................................................................................ 7

6.3  Administration of payment data by the VM ........................................................................................ 7

6.4  Administration of access event data by the VM ................................................................................. 8

6.5  Administration of access event data to security-related RMI by the VM ......................................... 8

6.6  Administration of downloaded VM data and applications at the IO site ......................................... 9

7  Requirements cluster "IT architecture" .............................................................................................. 9

7.1  Conceptual architecture ....................................................................................................................... 9

7.2  Implementation principles .................................................................................................................. 12

8  Requirements cluster "external interfaces" ..................................................................................... 15

8.1  Vehicle communication interface (VCI) ............................................................................................. 15

8.2  Trust centre (certificate management) .............................................................................................. 20

8.3  Parts ordering for security-related features ..................................................................................... 20

8.4  Partnered accessory provider systems ............................................................................................ 21

9  Requirements cluster "technical infrastructure" ............................................................................. 21

9.1  Type of device ...................................................................................................................................... 21

9.2  Hardware features ............................................................................................................................... 21

9.3  Operating systems .............................................................................................................................. 22

9.4  Web browsers ...................................................................................................................................... 22

9.5  Presentation formats for information packages .............................................................................. 22

9.6  Internet connection ............................................................................................................................. 23

9.7  Performance of the VM RMI system .................................................................................................. 23

10  Requirements cluster "VM software installed on the IO client" ..................................................... 24

10.1  Requirements for installing VM-specific software on the IO client ................................................ 24

10.2  Requirements for the operation of VM-specific software on the IO client ................................... 25

10.3  Requirements for the uninstalling of VM-specific software on the IO client ................................ 25

10.4  Requirements for restoring in case of an abnormal termination of the VM-specific

software on the IO client ..................................................................................................................... 26

11  Requirements cluster "operations" ................................................................................................... 26

11.1  VM RMI system availability time ........................................................................................................ 26

11.2  Support for the usage of the VM RMI system ................................................................................... 27

11.3  Operation of the IO PC ........................................................................................................................ 27

12  Requirements cluster "functional user interface" ........................................................................... 28

Annex A (informative) “fit for purpose” commercially available minimum PC specification ................. 29

© ISO 2012 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/DIS 18541-2

Bibliography ...................................................................................................................................................... 30

iv © ISO 2012 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/DIS 18541-2
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.

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.

The main task of technical committees is to prepare International Standards. Draft International Standards

adopted by the technical committees are circulated to the member bodies for voting. Publication as an

International Standard requires approval by at least 75 % of the member bodies casting a vote.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent

rights. ISO shall not be held responsible for identifying any or all such patent rights.

ISO 18541-2 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, and by

Technical Committee CEN/CENELEC/TC 301, Road vehicles in collaboration.

ISO 18541 consists of the following parts, under the general title Road vehicles — Standardized access to

automotive repair and maintenance information (RMI):
 Part 1: General information and use case definition
 Part 2: Technical requirements
 Part 3: Functional user interface requirements
 Part 4: Conformance test
© ISO 2012 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/DIS 18541-2
Introduction

This set of standards includes the requirements to be fulfilled by Repair and Maintenance Information (RMI)

systems as applied by the

EUROPEAN COMMISSION - ENTERPRISE AND INDUSTRY DIRECTORATE-GENERAL, Consumer goods

- Automotive industry EC mandate M/421 [1]
"MANDATE TO THE EUROPEAN STANDARDIZATION ORGANISATIONS FOR STANDARDIZATION IN
THE FIELD OF VEHICLE OBD, REPAIR AND MAINTENANCE INFORMATION"
dated Brussels, 21 January 2008.

This mandate relates to the EC type-approval system for vehicles falling into the scopes of Directives

70/156/EEC [2], 2002/24/EC [3] and 2003/37/EC [4] and, in particular, to requirements for access to vehicle

repair and maintenance information by independent operators.

This standard only covers the access to automotive repair and maintenance information based on Directive

70/156/EEC [2]. The Directive 70/156/EEC [2] is replaced by 2007/46/EC [5].

The purpose of the EC Mandate M/421 [1] is to develop a standard or set of standards which specify the

requirements to provide "standardized access to automotive repair and maintenance information (RMI)" for

independent operators.

The information included in this part of the standard derives from the legislative requirements on European

level in the field of repair and maintenance information and related security requirements.

1) REGULATION (EC) No 715/2007 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of

20 June 2007 on type approval of motor vehicles with respect to emissions from light passenger and

commercial vehicles (Euro 5 and Euro 6) and on access to vehicle repair and maintenance information [6] and

COMMISSION REGULATION (EC) No 692/2008 of 18 July 2008 implementing and amending Regulation (EC)

No 715/2007 of the European Parliament and of the Council on type-approval of motor vehicles with respect to

emissions from light passenger and commercial vehicles (Euro 5 and Euro 6) and on access to vehicle repair and

maintenance information [7] and amending COMMISSION REGULATION (EU) No 566/2011 of 8 June 2011

amending Regulation (EC) No 715/2007 of the European Parliament and of the Council and Commission

Regulation (EC) No 692/2008 as regards access to vehicle repair and maintenance information.

vi © ISO 2012 – All rights reserved
---------------------- Page: 6 ----------------------
DRAFT INTERNATIONAL STANDARD ISO/DIS 18541-2
Road vehicles — Standardized access to automotive repair and
maintenance information (RMI) — Part 2: Technical
requirements
1 Scope

This part of the standard includes "technical requirements" which are related to automotive repair and

maintenance information (RMI) systems in order to standardize the access to RMI for independent operators.

This part of the standard specifies the minimum set of technical requirements related to a vehicle

manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as

specified in ISO 18541-1.
2 Normative references

The following referenced documents are indispensable for the application of this document. For dated

references, only the edition cited applies. For undated references, the latest edition of the referenced

document (including any amendments) applies.

ISO 18541-1, Road vehicles — Standardized access to automotive RMI — Part 1: General information and

use case definition

ISO 18541-3, Road vehicles — Standardized access to automotive RMI — Part 3: Functional user interface

requirements

ISO 18541-4, Road vehicles — Standardized access to automotive RMI — Part 4: Conformance test

ISO 18542 (all parts), Road vehicles — Standardized RMI terminology
ISO°20828, Road vehicles — Security certificate management

ISO 22900-2, Road vehicles — Modular vehicle communication interface (MVCI) — Part 2: D-PDU API

SAE°J2534-1, Recommended Practice for Pass-Thru Vehicle Programming
SAE°J2534-2, Optional Pass-Thru Features

EC Forum for Access to Vehicle RMI, Report on Access to security-related RMI, Version 1.1,

© ISO 2012 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO/DIS 18541-2
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions

For the purposes of this document, the terms and definitions of ISO 18541-1 apply.

3.1.1
SERMI

the de-facto association founded by IO and VM organisations to act as the owner for the process and scheme

defined in the EC Forum for Access to Vehicle RMI, Report on Access to security-related RMI, version 1.1.

3.1.2
accessories

supplementary features and components selected by a vehicle owner to enhance safety, performance,

comfort, etc. and whose fitting doesn´t require a change of the vehicle type approval or authorisation.

3.2 Abbreviated terms
API application programming interface
DLC data link cable
DLL dynamic link library
D-PDU diagnostic – protocol data unit
DVD optical disc storage media format
FAQ frequently asked questions
GB giga-byte
GHz giga-hertz
IO independent operator
LAN local area network
MVCI modular vehicle communication interface
NAT network address translation
OBD on-board diagnostics
PC personal computer
RS232 recommended standard 232
SERMI security-related repair and maintenance information
TREQ- technical requirement
TC trust centre
USB universal serial bus
VAT No. value added tax number
2 © ISO 2012 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/DIS 18541-2
VM vehicle manufacturer
WWH-OBD world-wide harmonized on-board diagnostics
4 Conventions

prEN ISO 18541-2:2012 is based on the conventions discussed in the OSI Service Conventions

(ISO/IEC 10731:1994).
5 Requirements overview and principles
5.1 Basic principles for requirements definition

Basic principles have been established as a guideline to define the requirements.

 The requirements stated in this part of the standard shall not specify any implementation details.

 Requirements shall be expressed in terms of performance rather than design or descriptive

characteristics. This approach leaves maximum freedom to technical development.

 The entire content of the definition/description of a requirement identified by a TREQ-xx, where ‘xx’ is the

requirement number, which consists of a “Main title”, Requirement definition”, “Brief description” and

“Classification”, shall be interpreted as part of the requirement except for descriptions which do not use

the term “shall” or “e.g.”.
© ISO 2012 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO/DIS 18541-2
5.2 Requirements clustering

Figure 1 illustrates the technical requirements clusters. The figure shall provide an overview about all technical

requirements clusters and the specific technical requirements. Each technical requirement is identified by the

mnemonic "TREQ-" and an alpha-numeric number. The name of the technical requirement is descriptive for

the area.
Overview about the technical requirements clusters and associated requirements

Cluster “access-related Cluster “IT- Cluster “technical Cluster “VM software Cluster “operations“

data administration“ architecture“ infrastructure“ installed on the IO
client“
TREQ-1: TREQ-6: TREQ-12: TREQ-19: TREQ-23:

Requirements for the Requirements for the Requirements for the Requirements for Requirements for the

administration of user conceptual architecture type of device Installing VM-specific VM RMI system

data by the VM software on the IO availability time
client
TREQ-13:
TREQ-2: TREQ-7: Requirements for the TREQ-24:
TREQ-20:
Requirements for the Requirements for hardware features Requirements for the
Requirements for the
administration of implementation support for the usage
operation of VM-
payment data by the principles of the VM RMI system
specific software on
TREQ-14:
the IO client
Requirements
concerning the
TREQ-3: TREQ-25:
operating systems
Requirements for the Requirements for the
TREQ-21:
administration of
operation of the IO PC
Requirements for the
Cluster “external
access event data by
uninstalling of VM-
TREQ-15:
interfaces“
the VM
specific software on
Requirements for Web
the IO client
TREQ-8:
browsers
TREQ-4:
Requirements for the
Requirements for the
vehicle communication
Cluster “functional user
administration of TREQ-22:
interface (VCI)
interface“
access event data to
Requirements for
TREQ-16:
security-related RMI by
restoring in case of an
Requirements for the
TREQ-26:
TREQ-9:
the VM
abnormal termination
presentation formats
Requirements for the
Requirements for the
of the VM-specific
for information
functional user
trust centre (certificate
TREQ-5: software on the IO
packages interface
management)
client
Requirements for the
administration of TREQ-17:
TREQ-10:
downloaded VM data Requirements for the
Requirements for the
and applications at the internet connection
parts ordering for
IO site
security-related
features
TREQ-18:
TREQ-11:
Requirements for
Requirements for the
performance of the VM
partnered accessory
RMI system
provider systems
Figure 1 — Overview about the technical requirements clusters
4 © ISO 2012 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/DIS 18541-2

Table 1 provides an overview of the main categories of standardized access to automotive RMI requirements.

A requirement category shall have at least one requirement.
Table 1 — Main requirements clusters
# Main title of cluster Brief description

1 Access-related data Describes the main data types to be administered by the VM RMI System and the

administration

requirements for the appropriate management procedures in order to comply with the

standardized access to RMI.
RMI requirements related to cluster access-related data administration are
 requirements for the type of data to be administered;
 requirements for the administration of user data by the VM;
 requirements for the administration of payment data by the VM;
 requirements for the administration of access event data by the VM;

 requirements for the administration of access event data to security-related RMI by

the VM;

 requirements for the administration of downloaded VM data and applications at the

IO site.

2 IT architecture Describes requirements for the main IT components and interfaces at the different IT

architectural levels.
RMI requirements related to cluster IT architecture are
 requirements for the conceptual architecture;
 requirements for the implementation principles.

3 External interfaces Describes the requirements for communication interfaces other than the user interface.

RMI requirements related to cluster external interfaces are
 requirements for the vehicle communication interface (VCI);
 requirements for the trust centre (certificate management);
 requirements for the parts ordering for security-related features;
 requirements for the partnered accessory provider systems.

4 Technical infrastructure Compatibility conditions, minimum requirements for components and Internet

connection parameters to give an acceptable performance. This cluster intends to

define minimal development guiding rules that shall be followed by the VM in order to

ensure compatibility between VM RMI systems. Compatibility issues that may occur
shall be managed by the Forum SERMI.

This requirements cluster specifies the technical infrastructure recommendations which

are:
 requirements related to type of device;
 requirements related to hardware features;
 requirements related to operating systems, runtime languages, libraries;
 requirements related to Web browsers;
 requirements related to presentation formats for information packages;
 requirements related to VM software;
 requirements related to internet connection;
 requirements related to performance of the VM RMI system.
© ISO 2012 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO/DIS 18541-2
Table 1 — (continued)
# Main title of cluster Brief description

5 Co-existence of VM This requirements cluster specifies the co-existence of VM software on IO client.

software on IO client

The VM Software shall be developed according to acknowledged quality criteria for the

co-existence of applications installed on the client side.

6 Operations This requirements cluster specifies the RMI requirements related to the cluster

operations are:
 requirements related to the VM RMI system availability time;
 requirements related to the support for the usage of the VM RMI system;
 requirements related to the operation of the IO PC.

7 Functional user This requirement cluster includes the reference to the ISO 18541-3 functional user

interface interface of the VM RMI system.
6 Requirements cluster "access-related data administration"
6.1 General

The VM has to administer data on users, on payment, on access events to security-related RMI and on

access events to general RMI content. Therefore, the VM allows access to the RMI system depending on the

storage of some data
 for user registration,
 agreement to terms and conditions,
 any other data required by local legislation,
 for user login and access data recovery,
 for invoicing,
 for physical delivery of material if needed,
 for logging of any access to security-related RMI see SERMI [9],

 for logging of any access to ECU replacing/update (in case of liability issues),

 to be able to disable a user see ISO 18541-1 use case 1.3 Disable user;

The administration of this data shall be according to data and privacy protection legislation. These data are

mandatory to fulfil the requirements in subclauses 6.2 - 6.6.
6 © ISO 2012 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/DIS 18541-2
6.2 Administration of user data by the VM
Table 2 defines the requirements for the administration of user data by the VM.
Table 2 — Administration of user data by the VM
REQ # TREQ-1
Main title Requirements for the administration of user data by the VM

Requirement User data shall be administered by the VM to enable user access, access data reset and to facilitate

definition written communication with the IO.
Brief The following list of user data shall be administered by the VM:
description
 first name, family name;
 email-address;
 company name;
 preferred language;
 user name and password;
 company postal address.
Classification mandatory
6.3 Administration of payment data by the VM

Table 3 defines the requirements for the administration of payment data by the VM.

Table 3 — Administration of payment data by the VM
REQ # TREQ-2
Main title Requirements for the administration of payment data by the VM

Requirement User data shall be administered by the VM to allow the VM to invoice the user.

definition

Brief The following user data shall be administered by the VM for the purposes of invoicing for use of the

description VM RMI system.
 Type of subscription;
 Method of payment;
 Subscription period;
 Invoicing address;
 Inter-community VAT No.
Classification mandatory
© ISO 2012 – All rights reserved 7
---------------------- Page: 13 ----------------------
ISO/DIS 18541-2
6.4 Administration of access event data by the VM

Table 4 defines the requirements for the administration of access event data by the VM.

Table 4 — Administration of access event data by the VM
REQ # TREQ-3
Main title Requirements for the administration of access event data by the VM

Requirement Access event data shall be administered by the VM to monitor use of the VM RMI system and take

definition appropriate action if necessary.
Brief The following access event data shall be administered by the VM:
description
 User name;
 Log on and off times;
 Period of non-use.
Classification mandatory
6.5 Administration of access event data to security-related RMI by the VM

Table 5 defines the requirements for the administration of access event data to security-related RMI by the

VM.
Table 5 — Administration of access event data to security-related RMI by the VM
REQ # TREQ-4

Main title Requirements for the administration of access event data to security-related RMI by the VM

Requirement Access event data to security-related RMI shall be administered by the VM to support enquiries in

definition case of liability issues.
Brief The following access event data shall be administered by the VM:
description
 User name;
 Log on and off times;
 Type of security-related RMI accessed,
 VIN of the related vehicle,
 Affected ECU (if possible).
Classification mandatory
8 © ISO 2012 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/DIS 18541-2
6.6 Administration of downloaded VM data and applications at the IO site

Table 6 defines the requirements for the administration of downloaded VM data and applications at the IO site.

Table 6 — Administration of downloaded VM data and applications at the IO site
REQ # TREQ-5

Main title Requirements for the administration of downloaded VM data and applications at the IO site

Requirement Downloaded VM data and applications at the IO site shall be administered by the VM to enable a

definition check on the validity of the data and applications and, where necessary, provide updates to the same.

In addition to the actual VM applications web browser plugins or further base software components

might be administered by the VM.

Brief The following downloaded VM data and applications and optionally also plugins and other base

description software components at the IO site shall be administered by the VM based on:

 Installed application version at the IO site;
 Current version information available;
 Downloaded data validity.
Classification mandatory
7 Requirements cluster "IT architecture"
7.1 Conceptual architecture
Table 7 defines the requirements for the concep
...

NORME ISO
INTERNATIONALE 18541-2
Première édition
2014-09-15
Véhicules routiers — Normalisation
de l’accès aux informations relatives à
la réparation et à la maintenance pour
l’automobile (RMI) —
Partie 2:
Exigences techniques
Road vehicles — Standardized access to automotive repair and
maintenance information (RMI) —
Part 2: Technical requirements
Numéro de référence
ISO 18541-2:2014(F)
ISO 2014
---------------------- Page: 1 ----------------------
ISO 18541-2:2014(F)
DOCUMENT PROTÉGÉ PAR COPYRIGHT
© ISO 2014

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni utilisée

sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie, l’affichage sur

l’internet ou sur un Intranet, sans autorisation écrite préalable. Les demandes d’autorisation peuvent être adressées à l’ISO à

l’adresse ci-après ou au comité membre de l’ISO dans le pays du demandeur.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Publié en Suisse
ii © ISO 2014 – Tous droits réservés
---------------------- Page: 2 ----------------------
ISO 18541-2:2014(F)
Sommaire Page

Avant‐propos ................................................................................................................................................................... v

Introduction ................................................................................................................................................................... vi

1 Domaine d'application ................................................................................................................................... 1

2 Références normatives .................................................................................................................................. 1

3 Termes, définitions, symboles et abréviations ..................................................................................... 1

3.1 Termes et définitions ..................................................................................................................................... 1

3.2 Abréviations ...................................................................................................................................................... 1

4 Conventions ....................................................................................................................................................... 3

5 Aperçu général et principes des exigences ............................................................................................ 3

5.1 Principes fondamentaux concernant la définition des exigences ................................................. 3

5.2 Groupage des exigences ................................................................................................................................ 3

6 Ensembles d'exigences 1 – Administration des données relatives à l'accès .............................. 8

6.1 [TREQ‐1] Administration générale des données relatives à l'accès .............................................. 8

6.2 Administration, par le CV, des données relatives à un employé de l'OI ....................................... 9

6.2.1 [TREQ‐2] Administration, par le VM, des données relatives à l'OI ................................................ 9

6.2.2 [TREQ‐3] Administration, par le CV, des données relatives à un employé de l'OI ................ 10

6.3 [TREQ‐4] Administration, par le CV, des données relatives au paiement ................................ 11

6.4 [TREQ‐5] Administration par le CV des données relatives aux événements d'accès ........... 11

6.5 [TREQ‐6] Administration, par le VM, des données relatives aux événements d'accès

aux RMI relatives à la sécurité ................................................................................................................. 12

7 Ensemble d'exigences 2 – Architecture TI ........................................................................................... 12

7.1 [TREQ‐7] Architecture conceptuelle ...................................................................................................... 12

7.2 [TREQ‐8] Principes de mise en œuvre .................................................................................................. 15

8 Ensemble d'exigences 3 – Interfaces externes ................................................................................... 20

8.1 [TREQ‐9] Interface de communication avec le véhicule (VCI) ..................................................... 20

8.2 [TREQ‐10] Site d'authentification (gestion des certificats) .......................................................... 24

8.3 [TREQ‐11] Passation de commande de pièces ayant des caractéristiques liées à la

sécurité ............................................................................................................................................................. 25

8.4 [TREQ‐12] Systèmes des partenaires fournisseurs d'accessoires .............................................. 25

9 Ensemble d'exigences 4 – Infrastructure technique ........................................................................ 26

9.1 [TREQ‐13] Type de dispositif ................................................................................................................... 26

9.2 [TREQ‐14] Caractéristiques du matériel .............................................................................................. 26

9.3 [TREQ‐15] Systèmes d'exploitation ....................................................................................................... 26

9.4 [TREQ‐16] Navigateurs web ...................................................................................................................... 27

9.5 [TREQ‐17] Formats de présentation des dossiers d'information ............................................... 27

9.6 [TREQ‐18] Connexion Internet ................................................................................................................ 28

9.7 [TREQ‐19] Performance du système RMI du CV ................................................................................ 28

10 Ensemble d'exigences 5 – Coexistence des logiciels des CV chez le client OI .......................... 29

10.1 [TREQ‐20] Exigences relatives à l'installation du logiciel du CV sur le système de

l'opérateur indépendant (OI) client ...................................................................................................... 29

10.2 [TREQ‐21] Exigences relatives à la mise à jour de données et d'applications du CV

installées sur le système de l'opérateur indépendant (OI) client ............................................... 30

© ISO 2014 – Tous droits réservés iii
---------------------- Page: 3 ----------------------
ISO 18541-2:2014(F)

10.3 [TREQ‐22] Exigences relatives au fonctionnement du logiciel du CV sur le système de

l'opérateur indépendant (OI) client. ..................................................................................................... 31

10.4 [TREQ‐23] Exigences relatives à la désinstallation du logiciel du CV installé sur le

système de l'opérateur indépendant (OI) client ............................................................................... 32

10.5 [TREQ‐24] Exigences relatives au rétablissement en cas de fin d'exécution anormale

du logiciel du CV sur le système de l'opérateur indépendant (OI) client ................................ 32

11 Ensemble d'exigences 6 – Opérations ................................................................................................... 33

11.1 [TREQ‐25] Temps de disponibilité du système RMI du CV ........................................................... 33

11.2 [TREQ‐26] Exigences relatives à l'assistance pour l'utilisation du système RMI du CV ..... 33

11.3 [TREQ‐27] Fonctionnement de l'ordinateur de l'opérateur indépendant (OI) ..................... 34

12 Ensemble d'exigences 7 – Interface utilisateur fonctionnelle ..................................................... 34

12.1 [TREQ‐28] Interface utilisateur fonctionnelle

Annexe A (informative) Spécification relative à l'ordinateur ..................................................................... 35

12.1 Spécification relative à l'ordinateur – Matériel ................................................................................ 35

12.2 Spécification relative à l'ordinateur – Logiciel .................................................................................. 35

Bibliographie ............................................................................................................................................................... 36

iv © ISO 2014 – Tous droits réservés
---------------------- Page: 4 ----------------------
ISO 18541-2:2014(F)
Avant‐propos

L'ISO (Organisation internationale de normalisation) est une fédération mondiale d'organismes

nationaux de normalisation (comités membres de l'ISO). L'élaboration des Normes internationales est

en général confiée aux comités techniques de l'ISO. Chaque comité membre intéressé par une étude a le

droit de faire partie du comité technique créé à cet effet. Les organisations internationales,

gouvernementales et non gouvernementales, en liaison avec l'ISO participent également aux travaux.

L'ISO collabore étroitement avec la Commission électrotechnique internationale (CEI) en ce qui

concerne la normalisation électrotechnique.

Les Normes internationales sont rédigées et maintenues conformément aux règles données dans les

Directives ISO/CEI, Partie 1. En particulier, il est à noter que les différents critères d'approbation

nécessaires pour la différents types de documents de l'ISO se font conformément aux règles des

directives ISO / CEI, Partie 2 (voir www.iso.org/directives).

Il est attiré l'attention sur le fait que certains des éléments du présent document peuvent faire l'objet de

droits de brevet. L'ISO ne saurait être tenue responsable d'identifier de tels droits de brevets. Les

détails des droits de brevet identifiés lors de l'élaboration du document seront dans l'introduction et /

ou sur la liste ISO des déclarations de brevets reçus (voir www.iso.org/patents).

Tout nom de marque utilisé dans ce document est fourni pour la commodité des utilisateurs et ne

constitue pas une approbation.

L'ISO 18541‐2 a été élaborée par le comité technique CEN/TC 301, Véhicules routiers, en collaboration

avec le comité technique ISO/TC 22, Véhicules routiers, sous‐comité SC 3, équipements électriques et

électroniques, selon l’accord de coopération technique entre le CEN et l’ISO (accord de Vienne).

L'ISO 18541 comprend les parties suivantes, présentées sous le titre général Véhicules routiers —

Normalisation de l'accès aux informations relatives à la réparation et à la maintenance pour l'automobile

(RMI):
 Partie 1 : Informations générales et définition de cas d'utilisation
 Partie 2 : Exigences techniques
 Partie 3 : Exigences fonctionnelles relatives à l’interface utilisateur
 Partie 4 : Test de conformité
© ISO 2014 – Tous droits réservés v
---------------------- Page: 5 ----------------------
ISO 18541-2:2014(F)
Introduction

La présente série de normes contient les exigences auxquelles doivent se conformer les systèmes

d'Information sur la Réparation et la Maintenance (RMI) en application du Mandat CE M/421 relatif à

l'industrie automobile donné par la Commission Européenne – Direction Générale Entreprise et

Industrie, Biens de consommation, fait à Bruxelles le 21 janvier 2008.

Ce mandat porte sur le système de réception CE des véhicules relevant des domaines d’application des

Directives 70/156/CEE (remplacée par 2007/46/CE [8]), 2002/24/CE [6] et 2003/37/CE [7] et, en

particulier, sur les exigences concernant l'accès aux informations relatives à la réparation et à la

maintenance des véhicules par des opérateurs indépendants.

La présente norme traite uniquement de l'accès aux informations sur la réparation et la maintenance

des véhicules particuliers et utilitaires légers (voir NOTE 1) et des véhicules utilitaires lourds (voir

NOTE 2) fondé sur la Directive 70/156/CEE (remplacée par 2007/46/CE [8]).

Le Mandat CE M/421 a pour objet l'élaboration d'une norme ou d'une série de normes spécifiant les

exigences pour fournir à des opérateurs indépendants un « accès normalisé aux informations relatives à

la réparation et à la maintenance (RMI) pour l'automobile ».

Les informations contenues dans la présente partie de la norme découlent des exigences législatives au

niveau européen dans le domaine des informations relatives à la réparation et à la maintenance et des

prescriptions de sécurité associées, et peuvent être citées en référence par la législation dans d’autres

pays.

NOTE 1 REGLEMENT (CE) n° 715/2007 DU PARLEMENT EUROPEEN ET DU CONSEIL du 20 juin 2007 relatif

à la réception des véhicules à moteur au regard des émissions des véhicules particuliers et utilitaires légers

(Euro 5 et Euro 6) et aux informations sur la réparation et l'entretien des véhicules [14] et REGLEMENT (CE)

n° 692/2008 DE LA COMMISSION du 18 juillet 2008 portant application et modification du Règlement (CE)

n° 715/2007 du Parlement européen et du Conseil relatif à la réception des véhicules à moteur au regard des

émissions des véhicules particuliers et utilitaires légers (Euro 5 et Euro 6) et aux informations sur la réparation et

l'entretien des véhicules [13] et REGLEMENT (UE) n° 566/2011 DE LA COMMISSION du 8 juin 2011 [10] portant

modification du Règlement (CE) n° 715/2007 du Parlement européen et du Conseil et du Règlement (CE)

n° 692/2008 de la Commission en ce qui concerne l’accès aux informations sur la réparation et l’entretien des

véhicules.

NOTE 2 REGLEMENT (CE) n° 595/2009 DU PARLEMENT EUROPEEN ET DU CONSEIL du 18 juin 2009 relatif

à la réception des véhicules à moteur et des moteurs au regard des émissions des véhicules utilitaires lourds

(Euro VI) et à l’accès aux informations sur la réparation et l’entretien des véhicules, REGLEMENT (UE)

n° 582/2011 de la COMMISSION du 25 mai 2011 portant modalités d'application et modification du

Règlement (CE) n° 595/2009 du Parlement européen et du Conseil au regard des émissions des véhicules

utilitaires lourds (Euro VI), et REGLEMENT (UE) n° 64/2012 de la COMMISSION du 23 janvier 2012 modifiant le

règlement (UE) n° 582/2011 portant modalités d’application et modification du règlement (CE) n° 595/2009 du

Parlement européen et du Conseil au regard des émissions des véhicules utilitaires lourds (Euro VI).

vi © ISO 2014 – Tous droits réservés
---------------------- Page: 6 ----------------------
ISO 18541-2:2014(F)
Véhicules routiers — Normalisation de l'accès aux informations
relatives à la réparation et à la maintenance pour l'automobile
(RMI) — Partie 2: Exigences techniques
1 Domaine d'application

La présente partie de la norme comprend les « exigences techniques » liées aux systèmes

d'informations relatives à la réparation et à la maintenance pour l'automobile (RMI) dans le but de

normaliser l'accès des opérateurs indépendants aux RMI.

La présente partie de la norme spécifie l'ensemble minimal d'exigences techniques concernant le

système RMI d'un constructeur de véhicules. Ces exigences reflèteront les besoins qui découlent des cas

d'utilisation spécifiés dans l'ISO 18541‐1.
2 Références normatives

Les documents suivants, en tout ou partie, sont référencés de façon normative dans le présent

document et sont indispensables à son application. Pour les références datées, seule l'édition citée

s'applique. Pour les références non datées, la dernière édition du document de référence s'applique (y

compris les éventuels amendements).

ISO 18541‐1:2014, Véhicules routiers — Normalisation de l'accès aux informations relatives à la

réparation et à la maintenance pour l'automobile (RMI) — Partie 1 : Informations générales et définition

de cas d'utilisation

ISO 18541‐3, Véhicules routiers — Normalisation de l'accès aux informations relatives à la réparation et à

la maintenance pour l'automobile (RMI) — Partie 3 : Exigences fonctionnelles relatives à l'interface

utilisateur

ISO 22900‐2, Véhicules routiers — Interface de communication modulaire du véhicule (MVCI) — Partie 2 :

Interface de programmation d'application d'unité de données du protocole de diagnostic (D‐PDU API)

SAE J2534‐1, Recommended Practice for Pass‐Thru Vehicle Programming
SAE J2534‐2, Optional Pass‐Thru Features
3 Termes, définitions, symboles et abréviations
3.1 Termes et définitions

Pour les besoins du présent document, les termes et définitions donnés dans ISO 18541‐1 s'appliquent.

3.2 Abréviations
API interface de programmation d'application
CSP protocole de statut des certificats
© ISO 2014 – Tous droits réservés
---------------------- Page: 7 ----------------------
ISO 18541-2:2014(F)
BD base de données
DLC câble de liaison de données
DLL bibliothèque de liens dynamiques
D‐PDU unité de données du protocole de diagnostic
DVD format de support de mémoire sur disque optique
UCE unité de contrôle électronique
FAQ questions posées fréquemment
GB giga‐octet
GHz gigahertz
GMT temps universel coordonné
OI opérateur indépendant
TI technologies de l'information
RLE réseau local d'entreprise
MVCI interface de communication modulaire du véhicule
NAT traduction d'adresse réseau
OBD système de diagnostic embarqué
OCSP protocole de statut des certificats en ligne
PC ordinateur personnel
PKCS statut d'un certificat de clé publique
RMI informations relatives à la réparation et à la maintenance
RS232 norme recommandée 232
SERMI informations sur la réparation et la maintenance relatives à la sécurité
TREQ exigence technique
TC site d'authentification
USB bus série universel
N° TVA numéro de taxe sur la valeur ajoutée
CV constructeur de véhicules
© ISO 2014 – Tous droits réservés
---------------------- Page: 8 ----------------------
ISO 18541-2:2014(F)
WWH‐OBD système mondial harmonisé de diagnostic embarqué
4 Conventions

Cette partie de l’EN EN ISO 18541‐2:2014 est fondé sur les conventions discutées dans le cadre des

conventions pour la définition des services OSI (ISO/CEI 10731:1994).
5 Aperçu général et principes des exigences
5.1 Principes fondamentaux concernant la définition des exigences

Les principes fondamentaux ont été établis sous forme de lignes directrices pour définir les exigences.

 PF1 : Les exigences mentionnées dans la présente partie de la norme ne doivent spécifier aucun

détail de mise en œuvre.

 PF2 : Les exigences doivent être exprimées en termes de performances plutôt qu'en termes de

conception ou de caractéristiques descriptives. Cette approche laisse une latitude maximale au

développement technique.

 PF3 : Une exigence est identifiée par TREQ‐xx, où « xx » est le numéro de l'exigence. Chaque

exigence comprend un « titre principal », une « définition de l'exigence », une « description de

l'exigence », une « explication/exemple » et une « classification ».

 PF4 : Les exigences des ensembles (clusters) 4 et 5 de la présente partie de la norme ont été

formulées dans le but de réduire au minimum le nombre d'OI clients (PC, ordinateur portable, etc.)

requis pour accéder aux différents systèmes de RMI de CV.
5.2 Groupage des exigences

La Figure 1 illustre les ensembles (clusters) d'exigences techniques. La figure doit fournir un aperçu

général de tous les ensembles d'exigences techniques et des exigences techniques spécifiques. Chaque

exigence technique est identifiée par le mnémonique « TREQ‐ » et par une séquence alphanumérique.

La désignation de l'exigence technique est descriptive du domaine.
© ISO 2014 – Tous droits réservés
---------------------- Page: 9 ----------------------
ISO 18541-2:2014(F)
Overview about the technical requirements clusters and associated requirements

Cluster “access-related Cluster “IT- Cluster “technical Cluster “VM software Cluster “operations“

data administration“ architecture“ infrastructure“ installed on the IO
client“
TREQ-1: TREQ-7: TREQ-13: TREQ-20: TREQ-25:

General access-related Requirements for the Requirements for the Requirements for Requirements for the

data administration conceptual architecture type of device installing VM-specific VM RMI system

software on the IO availability time
client
TREQ-14:
TREQ-2: TREQ-8: Requirements for the TREQ-26:
TREQ-21:
hardware features
Requirements for the Requirements for Requirements for the
Requirements for
administration of IO implementation support for the usage
updating VM-specific
data by the VM principles of the VM RMI system
software on the IO
TREQ-15:
client
Requirements
concerning the
TREQ-3: TREQ-27:
operating systems
Requirements for the TREQ-22: Requirements for the
administration of IO Requirements for the operation of the IO PC
Cluster “external
employee data by the operation of VM-
interfaces“ TREQ-16:
VM specific software on
Requirements for Web
the IO client
TREQ-9:
browsers
TREQ-4:
Requirements for the
Requirements for the
vehicle communication Cluster “functional user
TREQ-23:
administration of
interface (VCI)
interface“
Requirements for the
payment data by the TREQ-17:
uninstalling of VM-
VM Requirements for the TREQ-28:
TREQ-10:
specific software on
presentation formats Requirements for the
Requirements for the
the IO client
TREQ-5: for information functional user
trust centre (certificate
Requirements for the packages interface
management)
administration of
TREQ-24:
TREQ-18:
access event data by
TREQ-11:
Requirements for
Requirements for the
the VM
Requirements for the
restoring in case of an
internet connection
parts ordering for
abnormal termination
TREQ-6:
security-related
of the VM-specific
Requirements for the
features
software on the IO
administration of
client
TREQ-19:
TREQ-12:
access event data to
Requirements for
security-related RMI by Requirements for the
performance of the VM
partnered accessory
the VM
RMI system
provider systems

Overview about the technical requirements clusters and Aperçu général des ensembles (clusters)

associated requirements d’exigences techniques et exigences associées

Cluster "access-related" data administration Ensemble administration des données « relatives à

l'accès »
TREQ-1: TREQ-1 :

General access-related data administration Administration générale des données relatives à l’accès

TREQ-2: TREQ-2 :

Requirements for the administration of IO data by the VM Administration, par le CV, des données relatives à l’OI

TREQ-3: TREQ-3 :

Requirements for the administration of IO employee data by the Administration, par le CV, des données relatives à un

VM employé de l’OI
TREQ-4: TREQ-4 :

Requirements for the administration of payment data by the VM Administration par le CV, des données relatives au

paiement
TREQ-5: TREQ-5 :

Requirements for the administration of access event data by the Administration, par le CV, des données relatives aux

VM évènements d’accès
TREQ-6: TREQ-6 :

Requirements for the administration of access event data to Administration par le CV, des données relatives aux

security-related RMI by the VM évènements d’accès aux RMI relatives à la sécurité

Cluster "IT-architecture" Ensemble « architecture TI »
TREQ-7: TREQ-7 :

Requirements for the conceptual architecture Exigences relatives à l'architecture conceptuelle

TREQ-8: TREQ-8 :
© ISO 2014 – Tous droits réservés
---------------------- Page: 10 ----------------------
ISO 18541-2:2014(F)

Requirements for implementation principles Exigences relatives aux principes de mise en œuvre

Cluster "external interfaces" Ensemble « interfaces externes »
TREQ-9: TREQ-9 :

Requirements for the vehicle communication interface (VCI) Exigences relatives à l'interface de communication avec

le véhicule (VCI)
TREQ-10: TREQ-10 :

Requirements for the trust centre (certificate management) Exigences relatives au site d’authentification (gestion des

certificats)
TREQ-11: TREQ-11 :

Requirements for the parts ordering for security-related features Exigences relatives à la passation de commande de

pièces pour des caractéristiques liées à la sécurité
TREQ-12: TREQ-12 :

Requirements for the partnered accessory provider systems Exigences relatives aux systèmes des partenaires

fournisseurs d'accessoires
Cluster « technical infrastructure » Ensemble "infrastructure technique"
TREQ-13: TREQ-13 :
Requirements for the type of device Exigences relatives au type de dispositif
TREQ-14: TREQ-14 :

Requirements for the hardware features Exigences relatives aux caractéristiques du matériel

TREQ-15: TREQ-15 :

Requirements concerning the operating systems Exigences relatives aux systèmes d'exploitation

TREQ-16: TREQ-16 :
Requirements for Web browsers Exigences relatives aux navigateurs web
TREQ-17: TREQ-17 :

Requirements for the presentation formats for information Exigences relatives aux formats de présentation des

packages dossiers d'informations
TREQ-18: TREQ-18 :

Requirements for the internet connection Exigences relatives à la connexion internet

TREQ-19: TREQ-19 :

Requirements for performance of the VM RMI system Exigences relatives à la performance du système RMI du

Cluster "VM software installed on the IO client" Ensemble « Logiciel du VM installé sur le système de

l'OI client »
TREQ-20: TREQ-20 :

Requirements for Installing VM-specific software on the IO client Exigences relatives à l'installation du logiciel du CV sur le

système de l'OI client
TREQ-21: TREQ-21 : Exigences relatives à la mise à jour de

Requirements for updating VM-specific software on the IO client données et d’applications du CV installées sur le

système de l’OI client
TREQ-22: Requirements for the operation of VM-specific software TREQ-22 :
on the IO client Exigences relatives au fonctionnement du logiciel propre
au CV sur le système de l'OI client
TREQ-23: TREQ-23 :

Requirements for the uninstalling of VM-specific software on the IO Exigences relatives à la désinstallation du logiciel propre

client au CV installé sur le système de l'OI client
TREQ-24: TREQ-24 :

Requirements for restoring in case of an abnormal termination of Exigences relatives au rétablissement en cas de fin

the VM-specific software on the IO client d'exécution anormale du logiciel du CV sur le système de

l'OI client
Cluster "operations" Ensemble « opérations »
TREQ-25: TREQ-25 :

Requirements for the VM RMI system availability time Exigences relatives au temps de disponibilité du système

RMI du CV
TREQ-26: TREQ-26 :

Requirements for the support for the usage of the VM RMI system Exigences relatives à l'assistance pour l'utilisation du

système RMI du CV
TREQ-27: Requirements for the operation of the IO PC TREQ-27 :
Exigences relatives au fonctionnement de l'ordinateur de
© ISO 2014 – Tous droits réservés
---------------------- Page: 11 ----------------------
ISO 18541-2:2014(F)
l'OI

Cluster "functional user interface" Ensemble « interface utilisateur fonctionnelle »

TREQ-28: Requirements for the functional user interface TREQ-28 :
Exigences relatives à l'interface utilisateur fonctionnelle
Figure 1 — Aperçu général des ensembles (clusters) d'exigences techniques

Le Tableau 1 fournit un aperçu général des principales catégories de l'accès normalisé aux exigences

RMI pour l'automobile. Une catégorie d'exigences doit comprendre au moins une exigence.

Tableau 1 — Principaux ensembles (clusters) d'exigences
N° ‐ Titre Description succincte Référence aux exigences
principal de techniques [TREQ]
l’ensemble

1 – Décrit les principaux types de données devant être [TREQ‐1] Administration

Administration administrées par le système RMI du CV ainsi que les exigences générale des données

des données relatives aux procédures de gestion appropriées afin d'assurer relatives à l'accès

relatives à la conformité à l'accès normalisé au système RMI.
[TREQ‐2] Administration,
l'accès

Les exigences RMI, liées à l'administration des données de par le CV, des données

l'ensemble relatives à l'accès, sont les suivantes : relatives à l'OI
[TREQ‐3] Administration,
 les exigences concernant l'administration, par le CV, des
par le CV, des données
données relatives à l'OI ;
relatives à un employé de
 les exigences concernant l'administration, par le CV, des
l'OI
données relatives à un employé de l'OI ;
[TREQ‐4] Administration,
 les exigences concernant l'administration, par le CV, des
par le CV, des données
données relatives au paiement ;
relatives au paiement
 les exigences concernant l'administration, par le CV, des
[TREQ‐5] Administration
données d'accès ;
par le CV des données
 les exigences concernant l'administration, par le CV, des
relatives aux événements
données d'accès aux RMI relatives à la sécurité.
d'accès
[TREQ‐6] Administration,
par le CV, des données
relatives aux événements
d'accès aux RMI relatives à
la sécurité

2 – Décrit les exigences des principaux composants et des [TREQ‐7] Architecture

Architecture interfaces informatiques (TI) relatives aux différents niveaux conceptuelle

TI d'architecture TI.
[TREQ‐8] Principes de mise
Les exigences RMI liées à l'architecture TI de l'ensemble sont en œuvre
les suivantes :
 les exigences relatives à l'architecture conceptuelle ;
 les exigences relatives aux principes de mise en œuvre.

3 – Interfaces Décrit les exigences relatives aux interfaces de communication [TREQ‐9] Interface de

externes autre
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.