EN ISO 18541-2:2014

SLOVENSKI STANDARD
01-januar-2015
&HVWQDYR]LOD6WDQGDUGL]LUDQGRVWRSGRLQIRUPDFLMRSRSUDYLOLKLQY]GUåHYDQMX
DYWRPRELORY50,GHO7HKQLþQH]DKWHYH,62
Road vehicles - Standardized access to automotive repair and maintenance information
(RMI) - Part 2: Technical requirements (ISO 18541-2:2014)
Straßenfahrzeuge - Standardisierter Zugang zur Reparatur und Wartung (RMI) - Teil 2:
Technische Anforderungen (ISO 18541-2:2014)
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)
Ta slovenski standard je istoveten z: EN ISO 18541-2:2014
ICS:
43.040.15 $YWRPRELOVNDLQIRUPDWLND Car informatics. On board
9JUDMHQLUDþXQDOQLãNLVLVWHPL computer systems
43.180 'LDJQRVWLþQDYGUåHYDOQDLQ Diagnostic, maintenance and
SUHVNXVQDRSUHPD test equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN ISO 18541-2
NORME EUROPÉENNE
EUROPÄISCHE NORM
September 2014
ICS 43.040.15; 43.180
English Version
Road vehicles - Standardized access to automotive repair and
maintenance information (RMI) - Part 2: Technical requirements
(ISO 18541-2:2014)
Véhicules routiers - Normalisation de l'accès aux Straßenfahrzeuge - Standardisierter Zugang zur Reparatur
informations relatives à la réparation et à la maintenance und Wartung (RMI) - Teil 2: Technische Anforderungen
pour l'automobile (RMI) - Partie 2: Exigences techniques (ISO 18541-2:2014)
(ISO 18541-2:2014)
This European Standard was approved by CEN on 13 March 2014.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same
status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United
Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2014 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 18541-2:2014 E
worldwide for CEN national Members.

Contents Page
Foreword .3
Foreword
This document (EN ISO 18541-2:2014) has been prepared by Technical Committee ISO/TC 22 “Road
vehicles” in collaboration with Technical Committee CEN/TC 301 “Road vehicles” the secretariat of which is
held by AFNOR.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by March 2015, and conflicting national standards shall be withdrawn at
the latest by March 2015.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech
Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece,
Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.
Endorsement notice
The text of ISO 18541-2:2014 has been approved by CEN as EN ISO 18541-2:2014 without any modification.

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
ISO 18541-2:2014(E)
© 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

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

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

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

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

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

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

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 shall be administered by the VM:
tion
— User Id;
— Log on and off times;
— Period of non-use.
Classification Mandatory.
6.5 [TREQ-6] Administration of access event data to security-related RMI by the VM
Table 7 defines the requirements for the administration of access event data to security-related RMI by
the VM.
ISO 18541-2:2014(E)
Table 7 — [TREQ-6] Administration of access event data to security-related RMI by the VM
REQ # TREQ-6
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 enquir-
definition ies in case of liability issues.
Brief descrip- The following access event data shall be administered by the VM:
tion
— User Id;
— Log on and off times;
— Type of security-related RMI accessed,
— VIN of the related vehicle,
— Affected ECU (if possible).
Classification Mandatory.
7 Requirements cluster 2 — IT architecture
7.1 [TREQ-7] Conceptual architecture
Table 8 defines the requirements for the conceptual architecture.
Table 8 — [TREQ-7] Conceptual architecture
REQ # TREQ-7
Main title Requirements for the conceptual architecture
Requirement The implementation of the RMI system shall be according to a standardized conceptual archi-
definition tecture.
Brief descrip- The standardized conceptual architecture is described in Figure 2.
tion
The IO is responsible for the provision of client hardware (PC, Laptop, etc.) and a VCI according
to the detailed requirements in clause 8.
The VM is responsible for the availability of the RMI system and the authorized/purchased
software and data components.
The VM shall facilitate the successful download to the IO client, once the IO has registered,
logged-in and prompted the download.
Classification Mandatory.
Figure 2 shows all IT systems potentially involved in the execution of the repair and maintenance use
cases defined in ISO 18541-1.
— The RMI applications will be implemented as distributed software on a client device at the location of
the independent operator (Independent Operator System) and a server in the VM premises (Vehicle
Manufacturer/RMI system). The software distribution may follow different patterns depending on
the overall design decision taken by the application builders to achieve an optimum performance
(see 7.2).
— Client and server communicate via internet.
— The RMI application may communicate with other applications for the execution of single use cases.
— The user is offered access to repair and maintenance information via the client device with standard
navigation, communication and display facilities.
— The vehicle acts as an IT system communicating with the other systems for use cases like updating
and replacing modules or integrated diagnostics.
10 © ISO 2014 – All rights reserved

ISO 18541-2:2014(E)
— For the communication with the VM RMI applications, for the purposes of diagnostics and
reprogramming, two alternatives are possible:
— Alternative ‘1’: the vehicle is connected via a pluggable, standardized, non-proprietary vehicle
communication interface;
— Alternative ‘2’: the vehicle is connected via an in-build wireless, standardized, non-proprietary
vehicle communication interface.
— Both alternatives shall either support the ISO 22900-2 or SAE J2534 (or both) standards.
— For access to security-related RMI, additional hardware for the management of a user certificate on
the IO client is required. A secure connection to the Trust Centre is required by both, the IO client
and the VM RMI system.
ISO 18541-2:2014(E)
Key
1 wired/wireless connection between “vehicle” and “Independent Operator System” with VCI Protocol Module
2 alternative means of connection as defined in TREQ-8 between “vehicle” and “Independent Operator
System” without VCI Protocol Module
Figure 2 — Conceptual architecture for access to vehicle RMI
7.2 [TREQ-8] Implementation principles
Table 9 defines the requirements for the implementation principles.
12 © ISO 2014 – All rights reserved

ISO 18541-2:2014(E)
Table 9 — [TREQ-8] Implementation principles
REQ # TREQ-8
Main title Requirements for implementation principles
Requirement The implementation of the VM RMI architecture may vary as long as it remains within the
definition conceptual architecture.
Brief descrip- The VM will decide on the option for implementation to follow:
tion
— ‘thin’ client;
— ‘thick’ client, or
— any other implementation strategies following state-of-the-art software technology.
There are minimum requirements for the software infrastructure to be supported by the
implemented application. See requirements cluster 4 clause 9 for detailed specification.
Figure 3 shows an example for ‘thick’ client architecture.
Figure 4 shows an example for ‘thin’ client architecture.
Classification Mandatory.
Figure 3 illustrates an example for the implementation of a VM RMI application following a so-called
“thick client” software distribution pattern. Substantial parts of the application software is downloaded
to the client system and executed there. Some use cases are executed completely in the client system;
others are executed in cooperation between the client and the server application software parts.
ISO 18541-2:2014(E)
Key
1 wired/wireless connection between “vehicle” and “Independent Operator System” with VCI Protocol Module
2 alternative means of connection as defined in TREQ-8 between “vehicle” and “Independent Operator
System” without VCI Protocol Module
Figure 3 — Example for thick client architecture
Figure 4 illustrates an example for the implementation of a VM RMI application following a so-called
“thin client” software distribution pattern. The application software resides only on the server and
is not downloaded to the client. In the client system only modules for web-based navigation, display
and communication with the server, the vehicle, the certificate hardware and the trust centre are
implemented. All use cases are executed using the server application software.
14 © ISO 2014 – All rights reserved

ISO 18541-2:2014(E)
Key
1 wired/wireless connection between “vehicle” and “Independent Operator System” with VCI Protocol Module
2 alternative means of connection as defined in TREQ-8 between “vehicle” and “Independent Operator
System” without VCI Protocol Module
Figure 4 — Example for thin client architecture
8 Requirements cluster 3 — External interfaces
8.1 [TREQ-9] Vehicle communication interface (VCI)
Table 10 defines the requirements for the vehicle communication interface.
ISO 18541-2:2014(E)
Table 10 — [TREQ-9] Vehicle communication interface (VCI)
REQ # TREQ-9
Main title Requirements for the vehicle communication interface (VCI)
Requirement The vehicle shall be connected to the diagnostics or programming application via a vehi-
definition cle communication interface (VCI) either compliant to the Modular Vehicle Communication
Interface (MVCI) according to ISO 22900-2 (D-PDU API), or SAE J2534 Pass-Thru according to
SAE J2534–1 and SAE J2534–2 for diagnosis according to use case 6.3 and updating and replac-
ing modules according to use cases in cluster 7 of ISO 18541-1:2014.
The diagnostic and programming application may be integrated in the RMI system or run
separately.
Brief descrip- The VM RMI website shall inform the user about the VCI standards supported under the rel-
tion evant use cases.
When the VM RMI system supports the ISO 22900-2 standard then the VM RMI system will
support the D-PDU API as specified in the ISO 22900-2 standard (D-PDU API), so that different
MVCI providers can communicate via this API with the VM RMI system application for updat-
ing and replacing modules and integrated diagnostics. A software driver for the specific MVCI
shall be provided by the MVCI tool manufacturer and shall be installed in the IO PC in addition
to the VM RMI system software. Figure 5 illustrates the ISO 22900-2 structure, components
and interfaces.
When the VM RMI system supports the SAE J2534 Pass-Thru standard then the VM RMI sys-
tem will support the Pass-Thru API as specified in the SAE J2534–1 and SAE J2534–2 recom-
mended practice, so that different Pass-Thru VCI providers can communicate via this API with
the VM RMI system application for updating and replacing modules and integrated diagnos-
tics. A software driver for the specific SAE J2534 Pass-Thru VCI shall be provided by the Pass-
Thru device tool manufacturer and shall be installed in the IO PC in addition to the VM RMI
system software. Figure 6 illustrates the SAE J2534 structure, compone
...