ISO/TR 24315-2:2025
(Main)Intelligent transport systems — Management of electronic traffic regulations (METR) — Part 2: Operational concepts (ConOps)
Intelligent transport systems — Management of electronic traffic regulations (METR) — Part 2: Operational concepts (ConOps)
The management of electronic transport regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document describes the operational concept (ConOps) for METR in a format that is consistent with ISO/IEC/IEEE 29148.
Systèmes de transport intelligents — Gestion des règles de circulation sous forme électronique — Partie 2: Concepts opérationnels
General Information
Relations
Standards Content (Sample)
Technical
Report
ISO/TR 24315-2
First edition
Intelligent transport systems —
2025-10
Management of electronic traffic
regulations (METR) —
Part 2:
Operational concepts (ConOps)
Systèmes de transport intelligents — Gestion des règles de
circulation sous forme électronique —
Partie 2: Concepts opérationnels
Reference number
© ISO 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms. 1
5 Current system or situation . 2
5.1 General .2
5.2 Background, objectives and scope .3
5.2.1 Background .3
5.2.2 Objectives .3
5.2.3 Scope of application .4
5.3 Operational policies and constraints .4
5.3.1 Policies .4
5.3.2 Constraints .5
5.4 Description of the current situation .5
5.4.1 General .5
5.4.2 Terminators .6
5.4.3 Processes .9
5.4.4 Data flows .10
5.4.5 Additional stakeholders .10
5.4.6 Data details . 12
5.5 Modes of operation for the current situation . 15
5.6 User classes and other involved personnel .16
5.6.1 General .16
5.6.2 Users subject to rules .16
5.6.3 Entities that establish rules.17
5.6.4 Third party entities .18
5.7 Support environment . . .18
5.7.1 General .18
5.7.2 Sources of support .19
6 Justification for and nature of changes . .20
6.1 General . 20
6.2 Justification of changes . 20
6.2.1 General . 20
6.2.2 Evolving transport environment . 20
6.2.3 Discrepancy reports .21
6.3 User need statements . 23
6.3.1 Trustworthiness needs. 23
6.3.2 User needs . 35
6.3.3 Rule maker needs . 44
6.3.4 Third party needs: auditing . 48
6.4 Priorities . 48
6.5 Deferred user needs . . 48
6.5.1 General . 48
6.5.2 User needs deferred to a future release . 49
6.5.3 User needs considered but not included . 49
6.6 Assumptions and constraints . 49
6.6.1 Assumptions . 49
6.6.2 Constraints .51
7 Concepts for the proposed system .52
7.1 General .52
iii
7.2 Background, objectives, and scope .52
7.3 Operational policies and constraints .52
7.3.1 Policies .52
7.3.2 Constraints .52
7.4 Description of the proposed system .52
7.4.1 Overview .52
7.4.2 Terminators . 54
7.4.3 Processes . 54
7.4.4 Data flows . 56
7.5 Modes of operation .57
7.5.1 General .57
7.5.2 Normal mode .57
7.5.3 Degraded mode . 58
7.5.4 Fallback mode . 58
7.6 User classes and other involved personnel . 58
7.7 Support environment . .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.