kSIST-TS FprCEN ISO/TS 24315-4:2026
(Main)Intelligent transport systems - Management of electronic traffic regulations (METR) - Part 4: System-level requirements (SysR) (ISO/DTS 24315-4:2026)
- Abstract
The management of electronic traffic regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document defines the requirements for each of the component systems that make up the METR system of systems (SoS), including the METR regulation system, METR distribution system, METR consumer system, and METR discrepancy handling system
- Status
- Not Published
- Public Enquiry End Date
- 09-Nov-2026
- Technical Committee
- ITC - Information technology
- Current Stage
- 5520 - Unique Acceptance Procedure (UAP) (Adopted Project)
- Start Date
- 17-Sep-2026
- Due Date
- 04-Feb-2027
- Completion Date
- 07-Oct-2026
kSIST-TS FprCEN ISO/TS 24315-4:2026 is SIST’s draft technical specification for intelligent transport systems and management of electronic traffic regulations (METR). It specifies system-level requirements for the METR system of systems, covering the METR regulation system (MRS), METR distribution system (MDS), METR consumer system (MCS), and METR discrepancy handling system (MDHS). In practice, it is the document for authorities, system developers, operators, and integrators who need the METR component systems to exchange and process electronic traffic regulations in a consistent way.
What does kSIST-TS FprCEN ISO/TS 24315-4:2026 specify?
kSIST-TS FprCEN ISO/TS 24315-4:2026 specifies the requirements for the METR system of systems at system level. The scope is the component systems that make up METR, and the document is organized to support implementation, interface design, security, and operational handling.
The document is arranged into scope, normative references, terms and definitions, symbols and abbreviated terms, overview, information flow requirements, functional object requirements, and external dependencies. Annex A gives deployment scenarios and MRS types, which helps readers see how the requirements map to different operational setups.
| Annex | What it covers |
|---|---|
| Annex A | Deployment scenarios and MRS types, including centre-based regulation systems for pre-announced rules, centre-based regulation systems for emergent rules, and localized regulation systems |
Clause 5 explains the METR framework, traceability conventions, and how the requirements are presented. Clause 6 sets out the information flows, and clause 7 sets out the functional object requirements for the METR component systems and related common behavior. Clause 8 covers external dependencies and the roles around the METR system.
What are the key requirements of kSIST-TS FprCEN ISO/TS 24315-4:2026?
kSIST-TS FprCEN ISO/TS 24315-4:2026 turns METR into a set of traceable system requirements rather than a general concept. The most important requirements are grouped around information exchange, verification, security, and the responsibilities of each component system.
System-level structure and traceability
Clause 5.3 says the document uses traceability conventions from CEN ISO/TS 24315-3:2025. In practice, that means managed items such as needs, requirements, and design elements should be linked to their reasons and to the related METR requirements, which is important for change control and audits.
Clause 5.5 explains that many requirements are written as information flows, with a definition, content, source, destination, and any constraints. That structure matters because implementers can use it directly to define interfaces and test whether data arrives from the right place and in the right form.
Information flows between METR systems
Clause 6 covers a long list of METR flows, including consolidated discrepancy report, discrepancy report details, discrepancy suppression information, local METR information for consumers, METR application information, METR information, METR information for consumers, METR information signature request, METR management information, signed METR information, system-generated discrepancy report, TCD discrepancy, TCD discrepancy status, TCD status, unverified METR information, and verified METR information.
Each flow is defined in the same way - purpose, content, source, destination, and security. That consistency matters in practice because the same structure can be reused for message design, interface specifications, and security review across different METR implementations.
Common system-level behavior
Clause 7.1 groups the common METR requirements. It includes METR collection and verification, logging detected inconsistencies, notifications, and ITS-S unit requirements such as access control, auditing, limited use of data, identification and authentication policies, incident reporting, personally identifiable information, data minimization, confidentiality, and system monitoring.
Clause 7.1 also includes general requirements for open specification, backwards compatibility, forward compatibility, and language neutrality. For a buyer or engineer, that means the solution should be interoperable, manageable over time, and usable across different national or regional implementations.
MRS, MDS, MCS, and MDHS responsibilities
Clause 7.2 adds MRS requirements such as independent verification, discrepancy management, information approval, packaging and provisioning, and translation. This is the part that turns source rules into approved METR information ready for distribution.
Clause 7.3 covers MDS requirements, including emergent information distribution, repackaging and distribution, radio frequency regulations, and ITS management support. In practice, MDS has to send the right rule to the right users or vehicles, and it has to handle urgent changes as well as planned rule updates.
Clause 7.4 covers MCS requirements such as discrepancy reporting, METR reception, verification, availability, latency, preferred communications, local storage of rules, and terms of service. This is the consumer side of METR, so implementers need to verify received rules and make sure the system can use them reliably at the point of use.
Clause 7.5 covers MDHS requirements for discrepancy report management, grouping, consolidated discrepancy reports, notifying responsible systems, forwarding details requests, and suppression management. That matters because field observations, duplicates, and repeated reports need controlled handling rather than ad hoc escalation.
External dependencies and operational roles
Clause 8 lists the actors and dependencies around METR, including discrepancy handling system operators, the maintenance and construction management centre, map providers, the METR auditor, the METR operator, the METR user, the rule maker, rule translation and signing agents, the rule verification agent, supporting data providers, and vehicles. In practice, METR deployment is not just a software task - it also depends on governance, operational roles, and field data.
What terms does kSIST-TS FprCEN ISO/TS 24315-4:2026 define?
kSIST-TS FprCEN ISO/TS 24315-4:2026 defines the core METR architecture and several key roles.
- METR - management of electronic traffic regulations, meaning trustworthy, machine-interpretable transport-related rules for road use.
- MRS - METR regulation system, the part that handles rule creation, verification, approval, packaging, and provisioning.
- MDS - METR distribution system, the part that repackages and distributes METR information to users and vehicles.
- MCS - METR consumer system, the part that receives, verifies, and uses METR information.
- MDHS - METR discrepancy handling system, the part that manages discrepancy reports and consolidation.
- first-tier MDHS - an MDHS that provides discrepancy information to another MDHS.
- second-tier MDHS - an MDHS that receives discrepancy information from another MDHS.
Who uses kSIST-TS FprCEN ISO/TS 24315-4:2026?
kSIST-TS FprCEN ISO/TS 24315-4:2026 is used by road authorities, ITS engineers, system integrators, operators, and vendors building METR services. It is also relevant to rule makers, rule translation agents, rule signing agents, rule verification agents, and METR auditors because clause 8 assigns responsibilities to those roles.
The document also matters to maintenance and construction management centres, discrepancy handling system operators, supporting data providers, and vehicle system developers. In practice, these groups use it to define how rules are entered, signed, distributed, verified, reported, and corrected in road transport operations.
Which standards are used with kSIST-TS FprCEN ISO/TS 24315-4:2026?
| Standard | What it contributes |
|---|---|
| ISO/TS 14812 | ITS vocabulary used for general intelligent transport systems terminology |
| ISO/TS 24315-1 | METR vocabulary |
| ISO/IEC/IEEE 24765 | Systems and software engineering vocabulary used for defined terms |
| CEN ISO/TS 24315-3:2025 | METR system of systems requirements and architecture, including traceability conventions and flow context |
| NIST 800-53, Rev 5 | Security and privacy controls relevant to access control, auditing, monitoring, and related safeguards |
| ISO 24315-2 | The METR concept of operations, referenced for operational understanding |
| ISO/IEC/IEEE 29148 | Guidance for the system requirements document style used in this specification |
What does the kSIST-TS FprCEN ISO/TS 24315-4:2026 document contain?
The document starts with a METR system overview, including purpose, information flow, graphical overview, rule distribution, and framework adaptation. It also includes figures such as the METR streetscape and the METR three-tier framework, which help readers understand how roadside communication units, user systems, and network infrastructure fit together.
Clause 6 is a structured catalogue of information flows, and each flow is described through purpose, content, source, destination, and security. Clause 7 groups the functional requirements for the shared METR functions and for each component system, while clause 8 describes contextual functional objects and actors.
Annex A provides deployment scenarios and MRS types, which is useful when mapping the requirements to a centre-based or localized implementation. The overall document is written to support design, integration, verification, and operational use of METR systems.
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
Great Wall Tianjin Quality Assurance Center
Established 1993, first batch to receive national accreditation with IAF recognition.
Hong Kong Quality Assurance Agency (HKQAA)
Hong Kong's leading certification body.
Sponsored listings
Frequently Asked Questions
kSIST-TS FprCEN ISO/TS 24315-4:2026 is a draft published by the Slovenian Institute for Standardization (SIST). Its full title is "Intelligent transport systems - Management of electronic traffic regulations (METR) - Part 4: System-level requirements (SysR) (ISO/DTS 24315-4:2026)". This standard covers: The management of electronic traffic regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document defines the requirements for each of the component systems that make up the METR system of systems (SoS), including the METR regulation system, METR distribution system, METR consumer system, and METR discrepancy handling system
The management of electronic traffic regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document defines the requirements for each of the component systems that make up the METR system of systems (SoS), including the METR regulation system, METR distribution system, METR consumer system, and METR discrepancy handling system
kSIST-TS FprCEN ISO/TS 24315-4:2026 is classified under the following ICS (International Classification for Standards) categories: 03.220.20 - Road transport; 35.240.60 - IT applications in transport. The ICS classification helps identify the subject area and facilitates finding related standards.
kSIST-TS FprCEN ISO/TS 24315-4:2026 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2026
Inteligentni transportni sistemi - Vodenje elektronskih prometnih predpisov
(METR) - 4. del: Sistemsko-nivojske zahteve (SysR) (ISO/DTS 24315-4:2026)
Intelligent transport systems - Management of electronic traffic regulations (METR) - Part
4: System-level requirements (SysR) (ISO/DTS 24315-4:2026)
Intelligente Verkehrssysteme - Management von elektronischen Verkehrsregularien
(METR) - Teil 4: Anforderungen an die Systemebene (SysR) (ISO/DTS 24315-4:2026)
Systèmes de transport intelligents - Gestion des règles de circulation sous forme
électronique - Partie 4: Exigences au niveau système (ISO/DTS 24315-4:2026)
Ta slovenski standard je istoveten z: FprCEN ISO/TS 24315-4
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
FINAL DRAFT
Technical
Specification
ISO/DTS 24315-4
ISO/TC 204
Intelligent transport systems —
Secretariat: ANSI
Management of electronic traffic
Voting begins on:
regulations (METR) —
2026-08-26
Part 4:
Voting terminates on:
2026-11-18
System-level requirements (SysR)
Systèmes de transport intelligents — Gestion des règles de
circulation sous forme électronique —
Partie 4: Exigences au niveau système
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 SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/CEN PARALLEL PROCESSING LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/DTS 24315-4:2026(en) © ISO 2026
FINAL DRAFT
ISO/DTS 24315-4:2026(en)
Technical
Specification
ISO/DTS 24315-4
ISO/TC 204
Intelligent transport systems —
Secretariat: ANSI
Management of electronic traffic
Voting begins on:
regulations (METR) —
Part 4:
Voting terminates on:
System-level requirements (SysR)
Systèmes de transport intelligents — Gestion des règles de
circulation sous forme électronique —
Partie 4: Exigences au niveau système
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 SUPPOR TING DOCUMENTATION.
© ISO 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/CEN PARALLEL PROCESSING
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland Reference number
ISO/DTS 24315-4:2026(en) © ISO 2026
ii
ISO/DTS 24315-4:2026(en)
Contents Page
Foreword .vii
Introduction .viii
0.1 System overview .viii
0.1.1 General .viii
0.1.2 Purpose .viii
0.1.3 Flow of information .viii
0.1.4 Graphical overview . ix
0.1.5 Rule distribution .x
0.2 Framework adaptation . . xi
0.3 Document overview .xii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms. 2
5 Overview . 3
5.1 General .3
5.2 Assumptions and dependencies .3
5.2.1 Customizing requirements .3
5.2.2 Internet-based communications .4
5.2.3 Vehicle communications .4
5.2.4 Geo-positioning rules .4
5.2.5 Leverage existing standards.4
5.2.6 Efficient data exchange.4
5.2.7 Additional requirements .4
5.3 Traceability conventions.4
5.4 External responsibilities .4
5.5 Presentation of requirements .4
5.6 Physical view .5
5.6.1 General .5
5.6.2 Physical view diagrams .6
6 Information flow requirements.13
6.1 Information flow: consolidated discrepancy report . 13
6.1.1 Purpose of consolidated discrepancy report . 13
6.1.2 Content of consolidated discrepancy report . 13
6.1.3 Source of consolidated discrepancy report . 13
6.1.4 Destination of consolidated discrepancy report .14
6.1.5 Security for consolidated discrepancy report .14
6.1.6 Instances of consolidated discrepancy report .14
6.2 Information flow: discrepancy report details .14
6.2.1 Purpose of discrepancy report details .14
6.2.2 Content of discrepancy report details .14
6.2.3 Source of discrepancy report details . 15
6.2.4 Destination of discrepancy report details . 15
6.2.5 Security for discrepancy report details. 15
6.3 Information flow: discrepancy suppression information . 15
6.3.1 Purpose of discrepancy suppression information . 15
6.3.2 Content of discrepancy suppression information .16
6.3.3 Source of discrepancy suppression information .16
6.3.4 Destination of discrepancy suppression information .16
6.3.5 Security for discrepancy suppression information.16
6.4 Information flow: local METR information for consumers .16
6.4.1 Purpose of local METR information for consumers .16
6.4.2 Content of local METR information for consumers .16
iii
ISO/DTS 24315-4:2026(en)
6.4.3 Source of local METR information for consumers.17
6.4.4 Destination of local METR information for consumers .17
6.4.5 Security for local METR information for consumers .17
6.5 Information flow: METR application information .17
6.5.1 Purpose of METR application information .17
6.5.2 Content of METR application information .17
6.5.3 Source of METR application information .17
6.5.4 Destination of METR application information .17
6.5.5 Security for METR application information .18
6.6 Information flow: METR application status .18
6.6.1 Purpose of METR application status .18
6.6.2 Content of METR application status .18
6.6.3 Source of METR application status .18
6.6.4 Destination of METR application status .18
6.6.5 Security for METR application status . .18
6.7 Information flow: METR coordination .19
6.7.1 Purpose of METR coordination .19
6.7.2 Content of METR coordination .19
6.7.3 Source of METR coordination .19
6.7.4 Destination of METR coordination .19
6.7.5 Security for METR coordination .19
6.8 Information flow: METR device status . 20
6.8.1 Purpose of METR device status . 20
6.8.2 Content of METR device status . 20
6.8.3 Source of METR device status . 20
6.8.4 Destination of METR device status . 20
6.8.5 Security for METR device status . 20
6.9 Information flow: METR discrepancy report . . 20
6.9.1 Purpose of METR discrepancy report . 20
6.9.2 Content of METR discrepancy report . 20
6.9.3 Source of METR discrepancy report .21
6.9.4 Destination of METR discrepancy report .21
6.9.5 Security for METR discrepancy report .21
6.10 Information flow: METR emergent rule input .21
6.10.1 Purpose of METR emergent rule input .21
6.10.2 Content of METR emergent rule input.21
6.10.3 Source of METR emergent rule input . 22
6.10.4 Destination of METR emergent rule input. 22
6.10.5 Security for METR emergent rule input . 22
6.11 Information flow: METR feedback . 22
6.11.1 Purpose of METR feedback . 22
6.11.2 Content of METR feedback . . . 22
6.11.3 Source of METR feedback . 22
6.11.4 Destination of METR feedback . 22
6.11.5 Security for METR feedback . 23
6.12 Information flow: METR information . 23
6.12.1 Purpose of METR information . 23
6.12.2 Content of METR information . 23
6.12.3 Source of METR information . 23
6.12.4 Destination of METR information . 23
6.12.5 Security for METR information . 23
6.13 Information flow: METR information for consumers .24
6.13.1 Purpose of METR information for consumers .24
6.13.2 Content of METR information for consumers.24
6.13.3 Source of METR information for consumers .24
6.13.4 Destination of METR information for consumers .24
6.13.5 Security for METR information for consumers .24
6.14 Information flow: METR information signature request .24
6.14.1 Purpose of METR information signature request .24
iv
ISO/DTS 24315-4:2026(en)
6.14.2 Contents of METR information signature request .24
6.14.3 Source of METR information signature request .24
6.14.4 Destination of METR information signature request . 25
6.14.5 Security for METR information signature request . 25
6.15 Information flow: METR input . 25
6.15.1 Purpose of METR input . 25
6.15.2 Content of METR input . 25
6.15.3 Source of METR input . 25
6.15.4 Destination of METR input . 25
6.15.5 Security for METR input . 25
6.16 Information flow: METR management information . 25
6.16.1 Purpose of METR management information . 25
6.16.2 Content of METR management information . 26
6.16.3 Source of METR management information . . 26
6.16.4 Destination of METR management information . 26
6.16.5 Security for METR management information . 26
6.17 Information flow: signed METR information . 26
6.17.1 Purpose of signed METR information . 26
6.17.2 Content of signed METR information . 26
6.17.3 Source of signed METR information . 26
6.17.4 Destination of signed METR information . 26
6.17.5 Security for signed METR information .27
6.18 Information flow: system-generated discrepancy report .27
6.18.1 Purpose of system-generated discrepancy report.27
6.18.2 Content of system-generated discrepancy report .27
6.18.3 Source of system-generated discrepancy report .27
6.18.4 Destination of system-generated discrepancy report .27
6.18.5 Security for system-generated discrepancy report .27
6.19 Information flow: TCD discrepancy . 28
6.19.1 Purpose of TCD discrepancy . 28
6.19.2 Content of TCD discrepancy . 28
6.19.3 Source of TCD discrepancy. 28
6.19.4 Destination of TCD discrepancy . 28
6.19.5 Security for TCD discrepancy . 28
6.20 Information flow: TCD discrepancy status . 28
6.20.1 Purpose of TCD discrepancy status . 28
6.20.2 Content of TCD discrepancy status . 28
6.20.3 Source of TCD discrepancy status . 29
6.20.4 Destination of TCD discrepancy status . 29
6.20.5 Security for TCD discrepancy status . 29
6.21 Information flow: TCD status . 29
6.21.1 Purpose of TCD status . 29
6.21.2 Content of TCD status . 29
6.21.3 Source of TCD status . 30
6.21.4 Destination of TCD status . 30
6.21.5 Security for TCD status . 30
6.22 Information flow: unverified METR information . 30
6.22.1 Purpose of unverified METR information . 30
6.22.2 Content of unverified METR information . 30
6.22.3 Source of unverified METR information . 30
6.22.4 Destination of unverified METR information . 30
6.22.5 Security for unverified METR information. 30
6.23 Information flow: verified METR information .31
6.23.1 Purpose of verified METR information .31
6.23.2 Content of verified METR information .31
6.23.3 Source of verified METR information .31
6.23.4 Destination of verified METR information .31
6.23.5 Security for verified METR information .31
v
ISO/DTS 24315-4:2026(en)
7 Functional object requirements .31
7.1 Common system-level METR requirements .31
7.1.1 METR Collection & Verification . .31
7.1.2 METR information verification .32
7.1.3 Coordination METR activities . 33
7.1.4 ITS-S unit requirements . 33
7.1.5 General requirements . 34
7.2 Additional MRS requirements . 34
7.2.1 Independent METR verification . 34
7.2.2 METR discovered rule management . 35
7.2.3 METR discrepancy management . 35
7.2.4 METR information approval .37
7.2.5 METR packaging and provisioning .37
7.2.6 METR translation . 39
7.3 Additional MDS requirements .41
7.3.1 METR emergent information distribution .41
7.3.2 METR repackaging and distribution .42
7.3.3 Radio frequency regulations .43
7.3.4 ITS management support .43
7.4 Additional MCS requirements .43
7.4.1 ITS management support .43
7.4.2 METR discrepancy reporting .43
7.4.3 METR reception . . . 44
7.4.4 METR verification .45
7.4.5 Other MCS requirements . .45
7.5 Additional MDHS requirements . 46
7.5.1 ITS management support . 46
7.5.2 METR discrepancy handling . 46
7.5.3 Consolidate discrepancy reports . 46
8 External dependencies . 47
8.1 Contextual functional objects .47
8.1.1 Data collection and provisioning .47
8.1.2 METR information adaptation .47
8.1.3 User device functions . 48
8.2 Actors . 48
8.2.1 Discrepancy handling system operators . 48
8.2.2 Maintenance and construction management centre . 49
8.2.3 Map providers . 49
8.2.4 METR auditor . 49
8.2.5 METR operator . 49
8.2.6 METR user . 50
8.2.7 Non-METR distribution centre . 50
8.2.8 Rule maker . 50
8.2.9 Rule implementation agent . 50
8.2.10 Rule signing agent . 50
8.2.11 Rule translation agent .51
8.2.12 Rule verification agent .52
8.2.13 Supporting data providers .52
8.2.14 Vehicles . 53
Annex A (informative) Deployment scenarios .54
Bibliography .57
vi
ISO/DTS 24315-4:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible
...