24315 METR
ConOps: Operational Concept (ConOps)


Last modified on 2024-06-28 13:11
Submit Comment
Traceability Tables:
NOTE: The RSR, DSR, CSR, DHSR, MDR, and ITS-SUR are still in very preliminary draft form
ID Description Discussion Links
ConOps-2

1 Scope

The management of electronic transport r…
ConOps-51

2 Normative references

The following documents are referred to …
ConOps-636
ISO/TS 14812:2022, Intelligent transport…
ConOps-637
ISO/TS 24315-1: - , Intelligent transpor…
ConOps-638
ISO/IEC/IEEE 24765:2017, Systems and sof…
ConOps-52

3 Terms and definitions

For the purposes of this document, the t…
ConOps-402

4 Symbols and abbreviated terms

ConOps-969

4.1 3G

third-generation technology standard for…
ConOps-970

4.2 3GPP

3rd Generation Partnership Project
ConOps-971

4.3 4G

fourth-generation technology standard fo…
ConOps-972

4.4 5G

fifth-generation technology standard for…
ConOps-973

4.5 ADS

Automated Driving System
ConOps-974

4.6 ARC-IT

Architecture Reference for Cooperative a…
ConOps-975

4.7 C-ITS

cooperative intelligent transport system…
ConOps-976

4.8 CCMS

cooperative ITS credentials management s…
ConOps-977

4.9 DDT

dynamic driving task
ConOps-978

4.10 DSRC

dedicated short-range communications
ConOps-979

4.11 FM

frequency modulation
ConOps-980

4.12 GNSS

global navigation satellite system
ConOps-981

4.13 HMI

human-machine interface
ConOps-982

4.14 IEC

International Electrotechnical Commissio…
ConOps-983

4.15 IEEE

Institute of Electrical and Electronic E…
ConOps-984

4.16 ISO

International Organization for Standardi…
ConOps-985

4.17 ITS

intelligent transport systems
ConOps-986

4.18 LTE-V2X

long-term evolution vehicle-to-everythin…
ConOps-987

4.19 METR

management of electronic traffic regulat…
ConOps-988

4.20 MUTCD

Manual on Uniform Traffic Control Device…
ConOps-1061

4.21 OBE

on-board equipment
ConOps-989

4.22 OCR

optical character recognition
ConOps-990

4.23 ODD

operational design domain
ConOps-991

4.24 OEM

original equipment manufacturer
ConOps-992

4.25 PMR

public-area mobile robot
ConOps-993

4.26 QR

quick response
ConOps-994

4.27 RSU

roadside unit
ConOps-995

4.28 TC

technical committee
ConOps-996

4.29 TMDD

Traffic Management Data Dictionary
ConOps-997

4.30 TN-ITS

transport network - intelligent transpor…
ConOps-998

4.31 TPEG

transport protocol experts group
ConOps-999

4.32 UK

United Kingdom
ConOps-1000

4.33 UNECE

United Nations Economic Commission for E…
ConOps-1001

4.34 US

United States of America
ConOps-1002

4.35 USDOT

United States Department of Transportati…
ConOps-1003

4.36 UTC

universal coordinated time
ConOps-1004

4.37 Wi-Fi

wireless network protocols
ConOps-1005

4.38 WP

working party
ConOps-6

5 Current system or situation

ConOps-7

5.1 General

This clause describes the current situat…
ConOps-763
  • signage;
ConOps-764
  • markings (e.g., pavement markings);
ConOps-765
  • published information (e.g., local laws,…
ConOps-766
The description of the current system is…
ConOps-8

5.2 Background, objectives and scope

ConOps-163

5.2.1 Background

Even before Karl Friedrich Benz produced…
ConOps-164
ConOps-168
The sign reads: NOTICE TO OWNERS AND DRI…
ConOps-165
In fact, the world's first traffic signa…
ConOps-166

5.2.2 Objectives

Rules for the use of road transport are …
ConOps-683
  • safety (e.g., requirements for taillight…
ConOps-684
  • efficiency (e.g., traffic signal logic, …
ConOps-685
  • comfort (e.g., guidance information, inc…
ConOps-686
  • mobility (e.g., parking restricted to tr…
ConOps-687
  • sustainability (e.g., requirements for t…
ConOps-688
The objective of METR is to provide trav…
ConOps-167

5.2.3 Scope of application

Within the current situation, most estab…
ConOps-689
  • limitation on road use for pedestrians a…
ConOps-690
  • prohibition of certain forms of micromob…
ConOps-1068
  • pedestrian signals at intersections;
ConOps-691
  • guidance to pedestrians on which directi…
ConOps-692
  • sidewalk closures for construction activ…
ConOps-693
  • rules for the operation of PMRs.
ConOps-694
The scope of rules considered in the des…
ConOps-695
The METR design may also be applicable f…
ConOps-933 NOTE: The intent is that this document can sup…
ConOps-9

5.3 Operational policies and constraints

ConOps-169

5.3.1 Policies

The typical current system is assumed to…
ConOps-421
  • The set of rules that govern behaviour v…
ConOps-422
  • The set of rules that govern behaviour a…
ConOps-423
  • The set of rules that govern behaviour c…
ConOps-425
  • Rules are made publicly available prior …
ConOps-424
  • The set of rules that apply at any given…
ConOps-1065 NOTE: While the term "campus" is often used to…
ConOps-426
  • All vehicles and travellers need to be a…
ConOps-427
  • All vehicles and travellers need to have…
ConOps-414
  • Rules are to be conveyed in a manner tha…
ConOps-417
  • Jurisdictions make rules publicly availa…
ConOps-418
  • Jurisdictions have competing demands tha…
ConOps-640
  • available budget;
ConOps-641
  • sustainability concerns, such as a desir…
ConOps-642
  • access to locations (e.g., physical or l…
ConOps-170

5.3.2 Constraints

The typical system is assumed to have th…
ConOps-409
  • Only appointed rule makers [SOURCE: ISO …
ConOps-410
  • The applicable location for each rule ca…
ConOps-411
  • Rules issued by rule makers of overlappi…
ConOps-412
  • Rules are to clearly identify the times …
ConOps-413
  • Rules are to support multi-lingual envir…
ConOps-415
  • Approved rules [SOURCE: ISO 24315-1:2024…
ConOps-416
  • Jurisdictions are responsible for making…
ConOps-10

5.4 Description of the current situation

ConOps-403

5.4.1 General

Subclause 5.4 provides an overview of ho…
ConOps-1070

5.4.2 Processes

Table 1 provides a description of each p…
ConOps-1071
Process Description Responsible Stakehol…
ConOps-1072

5.4.3 Data flows

Table 2 describes the content of each da…
ConOps-1073
Output from Data flow Input to Descripti…
ConOps-1140

5.4.4 Responsible stakeholders

ConOps-182

5.4.4.1 Rule maker

A rule maker represents an entity with t…
ConOps-189
Most locations fall within a jurisdictio…
ConOps-696 EXAMPLE: Legislative bodies often establish unpos…
ConOps-697 EXAMPLE: Regional government transportation agenc…
ConOps-698 EXAMPLE: Local government transportation agencies…
ConOps-699 EXAMPLE: Separate government entities sometimes e…
ConOps-700 EXAMPLE: Maintenance agencies often establish tem…
ConOps-701 EXAMPLE: Emergency response agencies can establis…
ConOps-702 EXAMPLE: Private entities can establish rules for…
ConOps-706 NOTE: Rules established by any rule maker can …
ConOps-703
Rule makers are responsible for establis…
ConOps-704
Rule makers are ultimately responsible f…
ConOps-705
Rule makers also need to work with other…
ConOps-939

5.4.4.2 Implementer

ConOps-196
5.4.4.2.1 Publicizing rules
An implementer is responsible for perfor…
ConOps-707
  • maintaining the public record through dr…
ConOps-708
  • maintaining TCDs, which notify traveller…
ConOps-709
  • signs, including regulatory signs (e.g.,…
ConOps-710
  • pavement markings, such as lane markings…
ConOps-711
  • signals, such as traffic signals and fla…
ConOps-712
  • channelization devices, such as traffic …
ConOps-713
  • traffic calming measures, such as rumble…
ConOps-714
  • facility access control measures, such a…
ConOps-1076
Properly performing these actions can re…
ConOps-715
5.4.4.2.2 Challenges
These methods of publicizing rules are n…
ConOps-716
  • posted rules can become unobservable [SO…
ConOps-717
  • posted rules might not be understood by …
ConOps-718
  • unauthorized sources might attempt to po…
ConOps-719
  • transport users (especially those from f…
ConOps-720
In recent years, these problems have bec…
ConOps-721
5.4.4.2.3 Rule implementation
In most cases, an unposted rule will typ…
ConOps-722
By comparison, a posted rule is typicall…
ConOps-173

5.4.4.3 Supporting data provider

At times, the transport user may have to…
ConOps-783 EXAMPLE: A transport user can use in-vehicle cloc…
ConOps-784 EXAMPLE: A transport user can watch a traffic sig…
ConOps-785 EXAMPLE: A transport user can use a navigation sy…
ConOps-786 EXAMPLE: A transport user can use a navigation sy…
ConOps-787
Within the existing system, information …
ConOps-174

5.4.4.4 Transport user

ConOps-175
5.4.4.4.1 General
Each transport user has the primary resp…
ConOps-176
  • be aware of all relevant rules;
ConOps-177
  • be aware of the environment;
ConOps-178
  • be aware of their location;
ConOps-934
  • be aware of the precedent of each rule (…
ConOps-179
  • comply with the active rule environment.
ConOps-180
5.4.4.4.2 Awareness
Regardless of the complexities of the ju…
ConOps-723
  • jurisdictional boundaries;
ConOps-724
  • the location of each rule; and
ConOps-725
  • his or her location.
ConOps-726
5.4.4.4.3 Location accuracy
Within the existing system, a transport …
ConOps-727
5.4.4.4.4 Context
Determining the precise location of a ju…
ConOps-181
Unposted rules can also change by jurisd…
ConOps-728
  • the precedence of various rules, includi…
ConOps-729
  • the location-specific meaning of rules;
ConOps-730
  • the location-specific meaning of TCDs; a…
ConOps-731
  • the conditions under which rules become …
ConOps-936
5.4.4.4.5 Proper judgement
Transport users are also expected to exe…
ConOps-1077

5.4.5 Data Details

ConOps-404

5.4.5.1 Rules

ConOps-429
The rules established by a rule maker ne…
ConOps-215
5.4.5.1.1 Rule lifecycle
Rules change over time at varying rates.…
ConOps-405
Figure 3 indicates how rules can transit…
ConOps-430
A proposed rule [SOURCE: ISO 24315-1:202…
ConOps-771
  • active — the rule is currently in effect…
ConOps-772
  • inactive — the rule is not in effect due…
ConOps-773
  • overridden — the rule is not in effect d…
ConOps-774
A rule can transition between states mul…
ConOps-775 NOTE: When rules are defined with an expected …
ConOps-407
5.4.5.1.2 Rule characteristics
While the standards for TCDs cover typic…
ConOps-632 EXAMPLE: A lower speed limit applies at night on …
ConOps-633 EXAMPLE: A lower speed limit applies 1) at night,…
ConOps-634 EXAMPLE: A lower speed limit applies 1) at night …
ConOps-631
Including multiple conditions on a rule,…
ConOps-408
5.4.5.1.3 Rule precedence
Rules need to be unambiguous in their pr…
ConOps-197
5.4.5.1.4 Jurisdictional boundaries
Rules are limited by geographic boundari…
ConOps-198
5.4.5.1.5 Conclusion
Rules that apply to the transport enviro…
ConOps-1080

5.4.5.2 Traffic control devices

ConOps-406
5.4.5.2.1 General
TCDs are one way by which implementers c…
ConOps-776
  • publications of UNECE WP.1World Party on…
ConOps-777
  • publications of UNECE WP.29 World Forum …
ConOps-778
  • the Vienna Convention on Road Signs and …
ConOps-779
  • similar regional, national, and local pu…
ConOps-780
While these documents are informative an…
ConOps-781
As an example, within the United States,…
ConOps-1079
5.4.5.2.2 Maintenance
ConOps-1078
In addition, the infrastructure used to …
ConOps-767
  • become obscured;
ConOps-768
  • fade (e.g., see Figure 6);
ConOps-769
  • be damaged or vandalized.
ConOps-1081
ConOps-770
Legal requirements to maintain TCDs vary…
ConOps-1082
5.4.5.2.3 Public record
In addition to TCDs, the implementer can…
ConOps-1083
5.4.5.2.4 Environment
Most jurisdictions have rules requiring …
ConOps-1084
5.4.5.2.5 Vehicle or device
Within the context of the ISO 24315 seri…
ConOps-202

5.5 Modes of operation for the current situation

The current situation can be described b…
ConOps-732
  • Normal: The regulations that are in forc…
ConOps-733
  • Evacuation: Select TCDs are overridden b…
ConOps-734
  • Power failure: TCDs that require power t…
ConOps-735
  • Manual (traffic officer on the roadway) …
ConOps-736
  • Other conditional (i.e., regulations tha…
ConOps-737
  • Responding emergency vehicle: Many juris…
ConOps-738
  • Road works: Within areas with road works…
ConOps-739
  • Unmarked conditions (e.g., bridge out, f…
ConOps-11

5.6 User classes and other involved personnel

ConOps-203

5.6.1 General

Subclause 5.6 describes the major user c…
ConOps-204

5.6.2 Users subject to rules

Users that are subject to rules distribu…
ConOps-740
  • travellers, who need to be aware of rule…
ConOps-741
  • road vehicle operators (e.g., those for …
ConOps-742
  • special vehicle operators (including pol…
ConOps-743
  • passengers;
ConOps-744
  • pedestrians;
ConOps-745
  • micromobility users (e.g., bicycles, e-s…
ConOps-746
  • travellers with disabilities.
ConOps-747
  • delivery service users, who need to be a…
ConOps-748
  • goods senders and
ConOps-749
  • goods receivers.
ConOps-750
  • driving automation systems, which need t…
ConOps-751
  • road vehicles with Level 1 driving autom…
ConOps-752
  • PMRs
ConOps-753
  • vehicle/device owners, who need to be aw…
ConOps-754
  • road vehicle owners;
ConOps-755
  • special vehicle owners;
ConOps-756
  • micromobility vehicle owners;
ConOps-757
  • PMR owners;
ConOps-758
  • nomadic device owners; and
ConOps-815
  • vehicle keeper (e.g., someone renting or…
ConOps-759
  • transport service providers, who need to…
ConOps-760
  • private transport providers (e.g., deliv…
ConOps-761
  • private vehicle providers (e.g., rental …
ConOps-762
  • public transport providers.
ConOps-205

5.6.3 Entities that establish rules

Entities that establish rules, which inc…
ConOps-788
  • policymakers, who establish rules that a…
ConOps-789
  • lawmakers (e.g., politicians);
ConOps-790
  • municipal rule makers (e.g., city manage…
ConOps-791
  • transport rule makers (e.g., traffic eng…
ConOps-792
  • sustainability rule makers (e.g., enviro…
ConOps-793
  • campus rule makers (e.g., landowners, ai…
ConOps-794
  • vehicle fleet rule makers (e.g., car hir…
ConOps-795
  • judicial system (e.g., courts that inter…
ConOps-796
  • infrastructure operators, who might acti…
ConOps-797
  • transport operations personnel and
ConOps-798
  • facility operators (e.g., toll roads, pa…
ConOps-799
  • field personnel, who might activate real…
ConOps-800
  • highway service patrol personnel;
ConOps-801
  • emergency response field personnel;
ConOps-802
  • work crew field personnel; and
ConOps-803
  • implementers.
ConOps-816
  • driving automation system (Level 1-5) de…
ConOps-804
Infrastructure operators and field perso…
ConOps-206

5.6.4 Third party entities

Third parties include:
ConOps-805
  • verifiers, who verify that posted rules …
ConOps-806
  • enforcement parties, who are involved in…
ConOps-807
  • enforcement organizations [SOURCE: ISO 2…
ConOps-808
  • prosecutors;
ConOps-809
  • defence attorneys;
ConOps-817
  • tribunals; and
ConOps-810
  • judges.
ConOps-811
  • other parties, who might wish to monitor…
ConOps-812
  • insurance companies, who might monitor i…
ConOps-813
  • navigation services, who may wish to inc…
ConOps-814
  • analysts and advocates (e.g., automobile…
ConOps-1062
  • fleet managers (e.g., those for public t…
ConOps-207

5.7 Support environment

ConOps-208

5.7.1 General

Subclause 5.7 describes the support conc…
ConOps-209

5.7.2 Sources of support

ConOps-210

5.7.2.1 Travellers

ConOps-942
5.7.2.1.1 General
Travellers are supported in discovering …
ConOps-818
  • vehicle inspection and repair personnel,…
ConOps-819
  • navigation and other technology systems …
ConOps-824
  • general rules of the road publications (…
ConOps-1063
  • TCDs.
ConOps-820
5.7.2.1.2 Vehicle maintenance
Within the current environment, travelle…
ConOps-821
If a vehicle is disabled, it can be towe…
ConOps-822
5.7.2.1.3 Technology updates
Technology devices (e.g., smartphones, V…
ConOps-826
  • largely stand-alone applications with mi…
ConOps-827
  • applications that perform significant pr…
ConOps-828
  • applications that are front ends to soft…
ConOps-211

5.7.2.2 Delivery service users

Delivery service users are supported in …
ConOps-829
  • delivery service providers, who inform t…
ConOps-212

5.7.2.3 Driving automation systems

Driving automation systems are supported…
ConOps-830
  • perception and ranging sensor systems;
ConOps-831
  • on-board databases of rules;
ConOps-1064
  • wireless information updates; and
ConOps-832
  • artificial intelligence/machine learning…
ConOps-213

5.7.2.4 Vehicle/device owners

Vehicle/device owners are supported in d…
ConOps-833
  • vehicle registration applications;
ConOps-834
  • mail reminders of periodic inspection an…
ConOps-835
  • automotive insurance renewal reminders.
ConOps-214

5.7.2.5 Transport service providers

Transport service providers are supporte…
ConOps-836
  • governmental and/or campus agencies that…
ConOps-837
  • software systems that automatically ensu…
ConOps-838
  • transport service providers conveying ru…
ConOps-17

6 Justification for and nature of changes

ConOps-216

6.1 General

This clause describes the shortcomings o…
ConOps-217

6.2 Justification of changes

ConOps-682

6.2.1 General

This document specifies the operational …
ConOps-647

6.2.2 Evolving transport environment

We live in a transformative time with re…
ConOps-646

6.2.3 Discrepancy Reports

Part of the plan to ensure trustworthy i…
ConOps-649
A user can detect a discrepancy [SOURCE:…
ConOps-19

6.3 User need statements

ConOps-432

6.3.1 Trustworthiness Needs

ConOps-452

6.3.1.1 Trustworthiness — Reliability — Accuracy

A METR user [SOURCE: ISO 24315-1:2024, 3…
ConOps-433

6.3.1.2 Trustworthiness — Reliability — Availability — Connectivity

A METR user needs to be able to download…
ConOps-434

6.3.1.3 Trustworthiness — Reliability — Availability — Geographic boundaries

A METR user needs to be aware of the jur…
ConOps-435

6.3.1.4 Trustworthiness — Reliability — Availability — Rule coverage

A METR user needs to be aware of the ava…
ConOps-436

6.3.1.5 Trustworthiness — Reliability — Availability — Supporting data coverage

A METR user needs to be aware of the ava…
ConOps-456

6.3.1.6 Trustworthiness — Reliability — Availability — Interruptions

A METR user needs to be able to rely upo…
ConOps-437

6.3.1.7 Trustworthiness — Reliability — Availability — Degradation

A METR user needs to be aware of degrade…
ConOps-446

6.3.1.8 Trustworthiness — Reliability — Completeness

A METR user needs all relevant data for …
ConOps-438

6.3.1.9 Trustworthiness — Reliability — Quality — Clarity

A METR user needs rules to be unambiguou…
ConOps-439

6.3.1.10 Trustworthiness — Reliability — Quality — Expiration

A METR user needs to be aware when previ…
ConOps-440

6.3.1.11 Trustworthiness — Reliability — Quality — Legal status

A METR user needs to be aware of the enf…
ConOps-441

6.3.1.12 Trustworthiness — Reliability — Quality — Confidence metrics

A METR user needs to be aware of how muc…
ConOps-442

6.3.1.13 Trustworthiness — Reliability — Resilience

A METR user needs the METR environment t…
ConOps-443

6.3.1.14 Trustworthiness — Reliability — Timeliness — Rules

A METR user needs to be aware of each ru…
ConOps-444

6.3.1.15 Trustworthiness — Reliability — Timeliness — Supporting data

A METR user needs to be aware of the cur…
ConOps-445

6.3.1.16 Trustworthiness — Reliability — Transparency

A METR user needs data that are transpar…
ConOps-447

6.3.1.17 Trustworthiness — Reliability — Usability — Language neutrality

A METR user needs rules to be exchanged …
ConOps-448

6.3.1.18 Trustworthiness — Reliability — Usability — Features

A METR user needs to be aware of the cap…
ConOps-450

6.3.1.19 Trustworthiness — Security — Authority — Access control

A METR user needs to have confidence tha…
ConOps-455

6.3.1.20 Trustworthiness — Security — Authority — Data privacy

A METR user needs to have confidence tha…
ConOps-454

6.3.1.21 Trustworthiness — Security — Authority — Legitimacy

A METR user needs to be aware of the aut…
ConOps-449

6.3.1.22 Trustworthiness — Security — Confidentiality

A METR user needs to have confidence tha…
ConOps-451

6.3.1.23 Trustworthiness — Security — Integrity — Accountability

Within established data privacy [SOURCE:…
ConOps-453

6.3.1.24 Trustworthiness — Security — Integrity — Authenticity

A METR user needs to be able to authenti…
ConOps-457

6.3.2 User needs

ConOps-458

6.3.2.1 User — Distributor — Discovery

A METR user needs to discover the approp…
ConOps-459

6.3.2.2 User — Distributor — Terms of service

A METR user needs to be able to discover…
ConOps-460

6.3.2.3 User — Connectivity — Preferences

A METR user needs to be able to identify…
ConOps-461

6.3.2.4 User — Awareness — Jurisdictional classification schemes

A METR user needs to understand the clas…
ConOps-462

6.3.2.5 User — Awareness — Self-awareness

A METR user needs to be sufficiently awa…
ConOps-463

6.3.2.6 User — Awareness — Mapping

A METR user needs electronic map(s) for …
ConOps-464

6.3.2.7 User — Awareness — Geopositioning

A METR user needs to be able to determin…
2023-01-20: Kenneth Vaughn

Trace to a general ITS-SU requirement assumption that the interpreter (or other external component) is still part of the trust environment. Also applies to time and all supporting data

ConOps-465

6.3.2.8 User — Conflicts — Detected

A METR user needs to be aware of confirm…
ConOps-466

6.3.2.9 User — Facility — Defined area

A METR user needs to be aware of the rel…
ConOps-467

6.3.2.10 User — Jurisdiction — Sub-areas

A METR user needs to be aware of any def…
ConOps-468

6.3.2.11 User — Rule — Awareness

A METR user needs to be aware of all ava…
ConOps-469

6.3.2.12 User — Rule — Characteristics

A METR user needs to be aware of the rel…
ConOps-470

6.3.2.13 User — Rule — Definition

A METR user needs to be able to become a…
ConOps-471

6.3.2.14 User — Rule — Precedence

A METR user needs to be aware of the pre…
ConOps-472

6.3.2.15 User — Rule — Distribution — Prioritization

A METR user needs rules to be distribute…
ConOps-473

6.3.2.16 User — Rule — Distribution — Efficiency

A METR user needs to obtain relevant rul…
ConOps-474

6.3.2.17 User — Rule — Applicability — Permits

A METR user needs to be aware of the per…
2023-01-20: Kenneth Vaughn

Should this be removed from the UN or moved to a section that relates to roles outside of the defined METR boundary? (We previously decided that non-public rules are not in-scope.)

DT=> Keep as a UN and trace to a Consumer System assumption. Also explain that there should be a standard interface for consumer systems to read in permits, but this is also outside of our scope.

ConOps-475

6.3.2.18 User — Rule — Journey planning

A METR user needs to be able to obtain a…
ConOps-476

6.3.2.19 User — Rule — Obsolescence

A METR user needs to be able to operate …
ConOps-477

6.3.2.20 User — Status — Manual inputs

A METR user needs to be aware of vehicle…
2023-01-20: Kenneth Vaughn

Trace to assumption in Consumer system

ConOps-478

6.3.2.21 User — Status — Environmental awareness

A METR user needs to be able to determin…
2023-01-20: Kenneth Vaughn

Trace to assumption in Consumer system

ConOps-479

6.3.2.22 User — System — Upgrade

A METR user needs the METR network to pa…
ConOps-480

6.3.3 Rule maker needs

ConOps-481

6.3.3.1 Rule maker — Jurisdictions — Identification

Within a jurisdictional area, the rule m…
ConOps-482

6.3.3.2 Rule maker — Rule signer

A rule maker needs to identify those ind…
ConOps-483

6.3.3.3 Rule maker — Translation agent

A rule maker needs to identify those ind…
ConOps-484

6.3.3.4 Rule maker — Publicize — Rules at a distance

A rule maker might need to publicize eme…
ConOps-485

6.3.3.5 Rule maker — Rules — Non-electronic

The rule maker needs to be able to infor…
ConOps-486

6.3.3.6 Rule maker — Discrepancies — Primary

A rule maker needs to be informed when a…
ConOps-487

6.3.3.7 Rule maker — Discrepancies — Secondary

A rule maker needs to be informed when s…
ConOps-488

6.3.3.8 Rule maker — Rule discovery service

A rule maker needs to discover and valid…
ConOps-490

6.3.3.9 Rule maker — Independent verification

A rule maker needs to be able independen…
ConOps-965

6.3.4 Third party needs

ConOps-966

6.3.4.1 Third party — Auditing

Auditors need to be able to retrieve his…
ConOps-20

6.4 Priorities

ISO/IEC/IEEE 29148 indicates that an ope…
ConOps-218

6.5 Deferred user needs

ConOps-219

6.5.1 General

Subclause 6.5 identifies user needs cons…
ConOps-220

6.5.2 User needs deferred to a future release

ConOps-221

6.5.2.1 Precise legal meaning of rules

The initial version of METR does not att…
ConOps-943
  • The messaging structure to handle all kn…
ConOps-944
  • The laws might have ambiguities within i…
ConOps-945
  • The interpretation of the legal language…
ConOps-946
  • The effort to define a message format th…
ConOps-947
Future efforts can address areas of know…
ConOps-222

6.5.2.2 Aerial drones

The initial edition of METR does not att…
ConOps-223

6.5.2.3 Indoor pedestrian environments

Indoor pedestrian environments are poten…
ConOps-224

6.5.3 User needs considered but not included

ConOps-225
While the general design of METR might a…
ConOps-22

6.6 Assumptions and constraints

ConOps-226

6.6.1 Assumptions

ConOps-227

6.6.1.1 Users — Modes

The scope of METR is intended to include…
ConOps-228

6.6.1.2 Users — Variety

METR users include humans (e.g., drivers…
ConOps-229

6.6.1.3 Users — Mixed environment

Vehicles that support METR need to be ab…
ConOps-230

6.6.1.4 Users — Stationary users

Some METR receivers will not be mobile (…
ConOps-231

6.6.1.5 Communications — Stationary components — Sufficient bandwidth

Sufficient communication bandwidth will …
ConOps-232

6.6.1.6 Communications — Mobile users — Mobile wireless internet

All mobile METR receivers will support m…
ConOps-233

6.6.1.7 Communications — Mobile users — Instability of internet access

Mobile wireless internet connectivity ca…
ConOps-234

6.6.1.8 Communications — Mobile users — Areas without internet coverage

Mobile wireless internet can be unavaila…
ConOps-235

6.6.1.9 Communications — Mobile users — Short-range wireless

All motor vehicles that support METR wil…
ConOps-236

6.6.1.10 Communications — Delivery — Pre-announced rules

Pre-announced rules will be retrieved at…
ConOps-237

6.6.1.11 Communications — Delivery — Emergent rules

METR receivers will be notified of relev…
ConOps-967
  • broadcast within the vicinity of the une…
ConOps-968
  • published to all subscribed METR receive…
ConOps-247

6.6.1.12 Communications — Delivery — Supporting data

METR will rely upon existing data source…
ConOps-238

6.6.1.13 Communications — Delivery — Third party

This document assumes that there may be …
ConOps-239

6.6.1.14 Geopositioning — Accuracy

Vehicle sensors will be able to correspo…
ConOps-240

6.6.1.15 Safety — Rule makers

Rule makers are responsible for ensuring…
ConOps-241

6.6.1.16 Safety — Users

The DDT includes the responsibility to p…
ConOps-242

6.6.1.17 Safety — Reliance

For the foreseeable future, METR will be…
ConOps-243

6.6.2 Constraints

ConOps-244

6.6.2.1 Communications — Delivery — Efficiency

METR needs to be designed to enable effi…
ConOps-245

6.6.2.2 Forwards and backwards compatibility

Every version of METR needs to be backwa…
ConOps-246

6.6.2.3 Existing standards

The design of METR needs to rely upon ex…
ConOps-248

6.6.2.4 Limitations of short-range wireless communications

Short range wireless communication chann…
ConOps-431 NOTE: This might require the use of short-rang…
ConOps-249

6.6.2.5 Aerial drones

The design of METR needs to be flexible …
ConOps-428

6.6.2.6 Radio frequency regulations

METR needs to comply with local regulati…
ConOps-23

7 Concepts for the proposed system

ConOps-491

7.1 General

This clause describes all the key concep…
ConOps-492

7.2 Background, objectives, and scope

To address the issues raised in Subclaus…
ConOps-493

7.3 Operational policies and constraints

ConOps-494

7.3.1 Policies

All the policies defined in Subclause 5.…
ConOps-496

7.3.2 Constraints

All the constraints defined in Subclause…
ConOps-497

7.4 Description of the proposed system

ConOps-498

7.4.1 Overview

Subclause 7.4 provides a vision for the …
ConOps-499
ConOps-1141 NOTE: The information contained within this su…
ConOps-1069 NOTE: For simplicity, Figure 8 shows a single …
ConOps-1094

7.4.2 Processes

Table 3 provides a description of each p…
ConOps-1095
Process Description Responsible Stakehol…
ConOps-1142
In addition to the processes in Table 3,…
ConOps-1096

7.4.3 Data flows

Table 4 provides a complete list of data…
ConOps-1097
Output from Data flow Input to Data flow…
ConOps-615

7.5 Modes of operation

ConOps-616

7.5.1 General

Subclause 7.5 describes the various mode…
ConOps-617

7.5.2 Normal mode

In the normal mode, a METR receiver can …
ConOps-618

7.5.3 Degraded mode

In the degraded mode, the METR environme…
ConOps-894
  • one or more translators being offline;
ConOps-896
  • one or more distributors being offline;
ConOps-898
  • the consumer system being in an area wit…
ConOps-899
The degraded mode is only entered if the…
ConOps-619

7.5.4 Fallback mode

The fallback mode represents a condition…
ConOps-900
  • determine that the alternate distributor…
ConOps-901
  • periodically poll its primary distributo…
ConOps-621

7.6 User classes and other involved personnel

The proposed system does not change the …
ConOps-622

7.7 Support environment

ConOps-623

7.7.1 General

The support environment includes the fac…
ConOps-620

7.7.2 Rule discovery service

The rule discovery service [SOURCE: ISO …
ConOps-1066 NOTE: Within the METR design documents, the ru…
ConOps-624

7.7.3 Service registration and discovery service

The ITS service registration and discove…
ConOps-625

7.7.4 Security service

The Cooperative ITS Credential Managemen…
ConOps-626

7.7.5 Technology services

Technology services provide base informa…
ConOps-902
  • telecommunications; and
ConOps-903
  • cloud platforms.
ConOps-627

7.7.6 METR Certification

The METR Certification Manager is respon…
ConOps-628

7.7.7 Maintenance

Maintenance facilities will be responsib…
ConOps-629

7.7.8 Enforcement

An enforcer encourages compliance with t…
ConOps-630

7.7.9 Academic research and advocacy

Academic institutions and advocacy group…
ConOps-904
  • automated vehicle experts;
ConOps-905
  • location perception experts; and
ConOps-906
  • advocates (e.g., safety, environmental, …
ConOps-35

8 Summary of impacts

ConOps-36

8.1 Operational impacts

METR is expected to have the following i…
ConOps-907
  • Several new roles have been defined and …
ConOps-908
  • Areas will need to ensure that there is …
ConOps-909
  • CCMS services will need to be available.
ConOps-910
  • Jurisdictions will need to indicate whet…
ConOps-911
  • Field personnel will need to coordinate …
ConOps-912
  • Implementers will need to inform transla…
ConOps-913
  • The need to digitize rules might result …
ConOps-914
  • METR users will need to determine the le…
ConOps-915
  • The legal system will need to consider h…
ConOps-37

8.2 Organizational impacts

METR is expected to have the following i…
ConOps-930
  • Regions will need to develop a deploymen…
ConOps-931
  • Inspection and maintenance facilities wi…
ConOps-932
  • Longer term operations with full deploym…
ConOps-38

8.3 Impacts during development

METR is expected to have the following i…
ConOps-916
  • OEMs will need to consider how to implem…
ConOps-917
  • OEMs will need to ensure that their vehi…
ConOps-918
  • Translators might wish to work closely w…
ConOps-919
  • Jurisdictional entities will need to con…
ConOps-39

9 Analysis of the proposed system

ConOps-40

9.1 Benefits

METR is expected to provide the followin…
ConOps-920
  • The provision of rules in a trustworthy,…
ConOps-921
  • Forensic evidence of the rules in force …
ConOps-41

9.2 Disadvantages and limitations

METR is expected to present the followin…
ConOps-922
  • Electronic rules provide an additional p…
ConOps-923
  • Field personnel will need to coordinate …
ConOps-924
  • Legal systems will need to set precedent…
ConOps-925
  • METR-equipped vehicles with expired METR…
ConOps-42

9.3 Alternatives considered

The null alternative (i.e., not providin…
ConOps-34

10 Operational scenarios

ConOps-308

10.1 General

This annex is intended to provide an ove…
ConOps-256

10.2 Sandy the busy mother

ConOps-257

10.2.1 General

Our first operational scenario is Sandy,…
ConOps-258

10.2.2 Refresh rule set

When Sandy starts her minivan, component…
ConOps-259

10.2.3 Snowy conditions

Local ordinances in Sandy’s locale speci…
ConOps-260

10.2.4 Start of snowfall

Within this jurisdiction, a lower speed …
ConOps-261

10.2.5 Operation of a traffic signal

The "motor vehicle right-of-way" rule se…
ConOps-262

10.2.6 Locating appropriate parking

As Sandy reaches her destination to meet…
ConOps-263

10.3 Trip to grandma's house

ConOps-264

10.3.1 Overview

Little Red Riding Hood has decided to ta…
ConOps-265

10.3.2 Download rule set for long journey

Based on the information contained on he…
ConOps-266

10.3.3 Encountering road works

As the ADS leaves Ms. Hood's neighbourho…
ConOps-267

10.3.4 Encountering a new traffic control device

As the vehicle proceeds through the work…
ConOps-963 NOTE: The same process can be followed for the…
ConOps-268

10.3.5 Encountering a variable speed limit

As Ms. Hood's vehicle gets onto the moto…
ConOps-269

10.3.6 Snow chain requirements

As Ms. Hood begins to cross the mountain…
ConOps-270

10.3.7 Pit stop

As the trip continues, Ms. Hood realizes…
ConOps-271

10.3.8 ADS fallback based on METR information

As Ms. Hood nears her destination, the A…
ConOps-272

10.3.9 Starting outside of METR coverage

After an extended visit with her grandmo…
ConOps-949
  • Have someone bring an updated set of rul…
ConOps-950
  • Manually drive the vehicle to an area wi…
ConOps-951
Since Ms. Hood's vehicle supports manual…
ConOps-288

10.4 Klaus the truck operator

ConOps-289

10.4.1 Overview

Klaus drives a container-carrying commer…
ConOps-290

10.4.2 Download rules

While Klaus's truck is being loaded with…
ConOps-291

10.4.3 Hazardous goods

Today's trip includes the transport of h…
ConOps-292

10.4.4 Encountering rain

As Klaus begins his journey, he notices …
ConOps-293

10.4.5 Emergent rules due to emergency

As Klaus leaves the city, the METR recei…
ConOps-294

10.4.6 Downloading new rules en-route

The ADS decides that the publicized deto…
ConOps-295

10.4.7 Transition to manual control

The METR receiver notifies the ADS of th…
ConOps-296

10.4.8 Turn prohibited

As Klaus continues to follow the detour,…
ConOps-297

10.4.9 Crossing a major border

As Klaus continues along his route, he c…
ConOps-952
  • the speed limit is now conveyed in miles…
ConOps-953
  • the definition of a dangerous goods vehi…
ConOps-954
  • the distinction between urban and rural …
ConOps-955
  • the rules on when an ADS can operate a h…
ConOps-956
  • the ADS is required to be certified by t…
ConOps-957
  • stop signs require a 2-second full stop.
ConOps-958
From Klaus's perspective, when the ADS i…
ConOps-298

10.4.10 On-board management of rules

Over time, the on-board electronics accu…
ConOps-273

10.5 Bilo the jet-set professor

ConOps-274

10.5.1 Overview

Bilo is an international expert in his f…
ConOps-275

10.5.2 Configuring the car

As a part of Bilo's rental car account, …
ConOps-276

10.5.3 Rental car

In addition to the rules that all other …
ConOps-277

10.5.4 Campus rules

The first stop on Bilo's trip is the uni…
ConOps-278

10.5.5 Rule discrepancy

At some time, Bilo's ADS detects an inco…
ConOps-279

10.5.6 Permitted parking

The large university campus requires vis…
ConOps-280

10.5.7 Micromobility and VRUs

Once parked, Bilo exits his vehicle and …
ConOps-299

10.6 Partially blind Fiona

ConOps-300

10.6.1 Overview

Fiona just bought a new cup and saucer a…
ConOps-301

10.6.2 Navigation to meeting spot

The ride-sourced service notes that Fion…
ConOps-302

10.6.3 Kerbside pickup

As the driver approaches the passenger l…
ConOps-250

10.7 Rosie the delivery robot

ConOps-251

10.7.1 Overview

Rosie, along with eleven other sibling p…
ConOps-252

10.7.2 Parking the van

Rosie's parent van is a level 4 ADS-equi…
ConOps-253

10.7.3 Sidewalk closure

On the way to the parking spot, Rosie wa…
ConOps-254

10.7.4 Reporting unexpected conditions

As Rosie traverses the alternate path, d…
ConOps-255

10.7.5 Propagation of conditions

In the meantime, the report handler rece…
ConOps-281

10.8 Thibideaux on the Bayou

ConOps-282

10.8.1 Overview

Thibideaux is enjoying his delicious shr…
ConOps-283

10.8.2 Evacuation orders

Thibideaux attempts to engage his ADS on…
ConOps-284

10.8.3 Manual traffic directions

As Thibideaux creeps along in slow traff…
ConOps-285

10.8.4 Ignoring signs that are overridden

As Thibideaux enters the motorway, he ob…
ConOps-286

10.8.5 Reporting inconsistent data

While Thibideaux likes his relatives, he…
ConOps-959
  • Update the notice to indicate that the M…
ConOps-960
  • Replace the notice with a new temporary …
ConOps-961
  • Update the notice to advise METR users t…
ConOps-962
With this information adapters are bette…
ConOps-287

10.8.6 Encountering a disabled traffic signal

The METR receiver is aware of where traf…
ConOps-303

10.9 Larry the lawyer

ConOps-304

10.9.1 Overview

Larry is a lawyer who has been hired to …
ConOps-305

10.9.2 Defence

One of the main pieces of evidence that …
ConOps-306

10.9.3 Prosecution

The prosecutor points out that the lower…
ConOps-307

10.9.4 Rebuttal

Larry can demonstrate that several other…
ConOps-650

10.10 Tracy the Traffic Engineer

ConOps-651

10.10.1 Overview

Tracy is the traffic engineer responsibl…
ConOps-652

10.10.2 Investigation

After receiving the request, Tracy has h…
ConOps-653

10.10.3 Rule approval

The system notifies Tracy that her assis…
ConOps-655
  • rescinding the existing parking rule, wh…
ConOps-654
  • creating a new passenger loading zone ru…
ConOps-656
  • creating two new parking rules (one that…
ConOps-657
  • changing the signage to effect these cha…
ConOps-658
  • painting the kerb white along the passen…
ConOps-659
  • removing the on-street parking space pav…
ConOps-661
  • implementing corresponding changes to ME…
ConOps-660
Tracy reviews the request and approves i…
ConOps-662

10.10.4 Work orders

Once the rule changes are approved, the …
ConOps-663

10.10.5 METR pre-announced rules

As soon as the modified rules are approv…
ConOps-664

10.10.6 METR emergent rules and supporting data

However, in this case, the TCDs were imp…
ConOps-1093

11 Data flow diagram conventions

ConOps-1100

11.1 General

The data expectation diagrams contained …
ConOps-500
  • Process: Each circle within the diagram …
ConOps-1102
  • Data flow: Each line within the diagram …
ConOps-1116

11.2 Naming conventions

Functional view processes and data flows…
ConOps-1119

11.3 Diagrams provide limited context

Reference architectures are typically ve…
ConOps-44

12 Tentative categories for METR information

ConOps-677

12.1 General

This annex provides a tentative example …
ConOps-316

12.2 Vocabulary categories

Each jurisdiction will need to maintain …
ConOps-317
  • vehicle classifications;
ConOps-318
  • roadway classifications;
ConOps-319
  • user classifications;
ConOps-926
  • usage classifications; and
ConOps-320
  • road network classifications, for exampl…
ConOps-321
  • motor vehicle road network;
ConOps-322
  • micromobility road network; and
ConOps-323
  • pedestrian road network.
ConOps-324

12.3 Rule Categories

It is expected that during the early sta…
ConOps-325
  • right of way (i.e., 11.397-11.398, 11.42…
ConOps-326
  • general restrictions (i.e., 12.411-12.41…
ConOps-327
  • vehicle classification restrictions, wit…
ConOps-328
  • general vehicle classification restricti…
ConOps-329
  • light vehicle restrictions (i.e., 12.114…
ConOps-330
  • motorcycle restrictions (i.e., 12.114, 1…
ConOps-331
  • truck and goods vehicle restrictions (i.…
ConOps-332
  • trailer restrictions (i.e., 12.116, 12.1…
ConOps-333
  • bus restrictions (i.e., 12.128, 12.129, …
ConOps-334
  • micromobility restrictions (i.e., 12.128…
ConOps-335
  • moped restrictions (i.e., 12.419, 12.454…
ConOps-336
  • pedestrian restrictions (i.e., 12.423, 1…
ConOps-337
  • animal-related (drawn, ridden, accompani…
ConOps-338
  • hand cart restrictions (i.e., 12.425);
ConOps-339
  • agricultural vehicle restrictions (i.e.,…
ConOps-340
  • wheelchair restrictions (i.e., 12.454, 1…
ConOps-341
  • microcar restrictions (i.e., 12.455);
ConOps-342
  • weight restrictions (i.e., 12.133, 12.51…
ConOps-343
  • width restrictions (i.e., 12.499);
ConOps-344
  • height restrictions (i.e., 12.511);
ConOps-345
  • length restrictions (i.e., 12.514);
ConOps-346
  • vehicle usage restrictions (i.e., 12.134…
ConOps-347
  • turning restrictions (i.e., 12.155, 12.1…
ConOps-348
  • speed restrictions (i.e., 12.176, 12.177…
ConOps-349
  • cargo restrictions (i.e., 12.475, 12.476…
ConOps-350
  • overtaking restrictions (i.e., 12.542, 1…
ConOps-351
  • noise restrictions (i.e., 12.558);
ConOps-352
  • kerbside usage restrictions (i.e., 12.57…
ConOps-353
  • lane restrictions (i.e., 12.621, 13.611-…
ConOps-354
  • zonal regulations (i.e., 12.631-12.635);
ConOps-355
  • tolling (i.e., 13.681-13.685);
ConOps-356
  • border restrictions (i.e., 13.875);
ConOps-357
  • crossings (i.e., 11.236-11.248, 11.381-1…
ConOps-358
  • signal locations (i.e., 11.253);
ConOps-359
  • road works (i.e., 11.348, 11.425);
ConOps-360
  • gradients (i.e., 11.346-11.347);
ConOps-361
  • road weather, including road surface con…
ConOps-644
  • air quality and emissions;
ConOps-420

13 Change request process

ConOps-679

13.1 General

It is expected that over time this docum…
ConOps-680

13.2 Requesting changes

Stakeholders who would like to propose a…
ConOps-681

13.3 Impacts to the standards series

The deletion, modification, or addition …
ConOps-45

14 Bibliography