24315-1 METR ConOps
T: Terminology

legal power to issue societal rules of behaviour for a defined area

territory for which a jurisdictional entity (3.1.6) has the power to define societal rules of behaviour

Note 1 to entry: A jurisdictional area might include non-contiguous locations.

jurisdictional area (3.1.4) whose jurisdictional entity (3.1.6) is a governmental entity, and the facility (3.x.x) is part of the jurisdictional entity's transport system (ISO 14812:2021, 3.1.2.2)

EXAMPLE         A subway station is a governmental area

private campus

jurisdictional area (3.1.4) whose jurisdictional entity (3.1.6) is the owner of the area, except for government-owned, transport-related areas

Note 1 to entry: A campus is a site typified by a school, hospital, store, or some other set of one or more buildings and might include parking or other transport facilities where the owner of the campus has the jurisdictional authority to establish its own rules. The rules can be in lieu of or in addition to rules established by the representative governmental entities.

EXAMPLE         A government-owned university is a campus

<METR> area entirely within a jurisdictional area (3.x.x) that has a consistent level of support for METR data (3.x.x) throughout

Note 1 to entry: A sub-area can be a jurisdictional area, which can have its own sub-areas.

<METR> jurisdictional area or sub-area

territorial limit associated with a jurisdictional area (3.1.4)

 Note 1 to entry:           A geofence can be used to electronically represent a jurisdictional boundary.

person (ISO 14812, 3.1.1.6) or organization who has jurisdiction (3.1.3)

EXAMPLE               A city government

Note 1 to entry:   In the case of a geopolitical jurisdiction, the jurisdictional entity is typically the recognized government for the territory; in the case of a campus, the jurisdictional entity is typically the landowner. 

Note 2 to entry: A jurisdictional entity assigns its authority to one or more rule-makers, which may be itself (e.g., the individual owner or a campus) or other divisions of the entity (e.g., police department, traffic department).

authorised categories and defined areas

re-interpretable representation of information in a formalized manner suitable for communication, interpretation or processing

[SOURCE ISO 2382-1:2015, 2121272, Notes removed]

<METR> set of specified characteristics used to group data (3.2.1.1)

EXAMPLE         Speed limit rules for motor vehicles within a specified jurisdictional area  

Note 1 to entry: The data category represents the set of characteristics; the term "rule set" is used to describe the rules that currently meet the specified characteristics. 

all rules (3.x.x) within a specified data category (3.2.1.2)

<METR> applicable to the METR user (3.x.x) within the circumstances

regulation, advisory, or guidance established by a rule-maker (3.x.x) for its jurisdictional area (3.x.x)

Note 1 to entry: The jurisdictional area can be a campus.

Note 2 to entry: The primary focus of METR is to provide rules that are likely to impact the dynamic driving task (DDT, ISO 14812:2021, 3.7.3.1). The exact boundary of which rules are a part of METR is left to those deploying METR distribution systems.

trustworthy (3.x.x) rules(s) (3.x.x) from a jurisdictional entity (3.x.x)

representation of a rule as recorded in official records of the jurisdictional entity

representation of a rule as presented within METR

representation of a rule as presented in the field

EXAMPLE         traffic control device

<METR> data (3.x.x) that is not a rule (3.x.x) but affects the meaning or active status of rules

Note 1 to entry: Supplemental data includes data provided by on-board equipment, roadside devices, map providers, and other sources.

Note 2 to entry: Supplemental data is often dynamic (i.e., changing more frequently than the validity periods of rule sets).

supplemental data (3.x.x) that is provided by on-board equipment

EXAMPLE: current time, windshield wiper status

<METR> rule (3.x.x) that does not have any expectation of a termination (3.x.x)

Note 1 to entry: A variable rule, such as a variable speed limit, often consists of a persistent rule (e.g., a variable speed limit applies to a specified stretch of a road) that is supplemented with supplemental data that identifies the current speed limit in effect.

<METR> rule (3.x.x) that has or is expected to have a specified termination (3.x.x)

<METR> rule that is publicized for a period longer than the expiration period for its containing rule set before it becomes active

Note 1 to entry: Pre-announced rules do not require low-latency communications because they are distributed well enough in advance so that all users with up-to-date rule sets will have a copy of the rule.

<METR> rule that becomes active prior to the expiration of a relevant, valid rule set

EXAMPLE   Police officer imposing a road closure

Note 1 to entry:   Ad-hoc rules are typically made in response to current conditions and typically require low-latency to ensure that METR users are notified in time to allow for operational decisions.

Note 2 to entry:   Ad-hoc rules are typically temporary.

<METR> disseminated in digital form such that a receiver can parse the digital information to readily extract data

Note 1 to entry: Digitized images do not meet this definition of electronic.

<METR> containing a parameter whose value is dependent upon supplemental data (3.x.x) issued by the rule-maker (3.x.x) who issued the rule (3.x.x)

Note 1 to entry: The supplemental data can be generated by an automated system under the authority of the rule-maker.

EXAMPLE         A speed limit that changes based on rule-maker decisions 

EXAMPLE         A traffic signal, which changes states as determined by a traffic signal controller

being active based on explicitly stated conditions

EXAMPLE         “when workers present”, “dusk”, “in winter”, "08:00 - 12:00"

Note 1 to entry: Condition-based rules can be based on multiple conditions.

Note 2 to entry: Time-based rules (e.g., a parking rule that is only in effect during certain hours) are one type of condition-based rules.

publicized (3.x.x) to the those affected using traffic control devices (3.x.x)

being announced to the public

not publicized (3.x.x) to those affected through traffic control devices (3.x.x)

Note 1 to entry:   Unposted regulations are often part of the legal codes of a jurisdiction that travellers are expected to know without posted regulations.

posted (3.x.x) and able to be perceived by those affected

posted (3.x.x) but not able to be perceived by a significant portion of those affected

Note 1 to entry:   Unobservable official notices have been posted but might not be perceived properly due to any number of reasons, such as damage, fading, snow accumulation, obstructions, graffiti, removal, etc.

<METR> epoch at which a rule (3.x.x) was approved

EXAMPLE               A rule can be approved through legislation, the completion of a traffic warrant, a traffic response plan, or other means. A rule can remain inactive for a prolonged period after its inception, as in the case of rules associated with an evacuation plan.

<METR> epoch at which a rule (3.x.x) is expected to be or was withdrawn

EXAMPLE               A daily parking restriction that is intended to be in effect daily from 07:00 to 19:00 and ending 31 July would require a termination time of no earlier than 19:00 on 31 July.

having an inception (3.x.x) in the past and a termination (3.x.x) either undefined or in the future

Note 1 to entry:   A current rule can be active, inactive, or overridden.

current (3.2.6.1) and presently in effect

Note 1 to entry:   A rule can be active during certain hours of the day or upon other defined conditions.

Note 2 to entry:   Regulations are only enforced when active.

current (3.2.6.1) but not presently in effect

Note 1 to entry:   A rule might not be in effect during certain hours of the day.

Note 2 to entry:   A regulation cannot be enforced while it is inactive.

Note 3 to entry:   Guidance information that is not applicable at certain times (e.g., detour that is in effect during certain hours) can be designated as "inactive" during those times.

current (3.2.6.1) but temporarily nullified and replaced

Note 1 to entry: It is expected that an override will eventually terminate, even if the expected termination epoch is unknown.

Note 2 to entry:   The item that is temporarily nullified is termed to be “overridden” and the item that it is replaced with is termed to be “overriding”.

Note 3 to entry:   The replacement can be null.

having a termination (3.x.x) in the past

epoch at which data (3.x.x) is considered to lose its trustworthiness (3.x.x) 

Note 1 to entry: Receivers can refresh their data prior to their expiration to avoid untrustworthy data.

having a future expiration (3.2.7.1)

EXAMPLE               A rule set that is downloaded can be designated as being valid for one week. The data would be considered untrustworthy after the one-week period.

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for issuing rules (3.x.x) for a jurisdictional area (3.x.x) for a specified scope

Note 1 to entry: A jurisdictional entity can divide its rule-making responsibilities among multiple rule-makers. For example, the one department can be responsible for setting speed limits while another department can be responsible for setting parking rules.

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for posting rules (3.x.x) for a jurisdictional area (3.x.x) using traffic control devices (3.x.x)

Note 1 to entry: The role includes posting signs and markings to publicize the rules established by the rule-maker. 

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for translating rules (3.x.x) defined by rule-makers (3.3.1.3) into an electronic format for METR

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for gathering rules (3.x.x) from one or more translators (3.3.1.4) and providing them to one or more disseminators (3.3.1.7)

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for providing trustworthy data (3.x.x) to METR users (3.3.1.15)

Note 1 to entry: The required degree of trustworthiness can vary based on the intended use of the data as well as applicable legal requirements (e.g., certification requirements). 

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for distributing rules (3.x.x) to METR users (3.3.1.15) via receivers (3.x.x) and interpreters (3.x.x)

<METR> disseminator (3.3.1.6) that is responsible for distributing all pre-announced rules (3.x.x) requested by a METR user (3.3.1.15) and within the publicized data categories (3.x.x) supported by the disseminator

Note 1 to entry: The pre-announced rule disseminator role is primarily envisioned to be fulfilled by a central system, but can be fulfilled by a mobile unit dispatched to a location without internet connectivity.

Note 2 to entry: A pre-announced rule disseminator can also distribute ad-hoc rules but does not bear the responsibility for doing so.

<METR> disseminator (3.3.1.7) that is responsible for distributing ad-hoc rules (3.x.x) 

Note 1 to entry: Ad-hoc rule disseminators are primarily envisioned to be broadcast sites with a short transmission range. As such, the rules distributed are envisioned to be the ad-hoc rules that are applicable to the broadcast area, which is likely a subset of all ad-hoc rules within a METR network coverage area.

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for distributing rules (3.x.x) in manners that do not conform to METR

EXAMPLE         distribution system that provides rules using protocols that do not meet METR security requirements

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for distributing supplemental data (3.x.x) to METR users (3.x.x) via interpreters (3.x.x)

Note 1 to entry: Supplemental data providers include on-board data providers and external data providers.

<METR> supplemental data provider (3.3.1.10) that is external to the material entity (ISO 14812:2021, 3.1.1.3) hosting the receiver (3.3.1.14)

Note 1 to entry: The material entity hosting the receiver is typically a vehicle, but can be a personal information device, such as a smartphone.

<METR> supplemental data provider (3.3.1.10) that is on-board the user's material entity (ISO 14812:2021, 3.1.1.3) hosting the receiver (3.3.1.14) and produces and provides supplemental data

Note 1 to entry: The material entity hosting the receiver is typically a vehicle, but can be a personal information device, such as a smartphone.

Note 2 to entry: On-board data providers can produce supplemental data that is derived from external data sources, for example by using sensors, clocks, GNSS receivers, and/or other devices with its own algorithms.

EXAMPLE         GNSS positioning data (i.e., GNSS positioning data is determined by an on-board algorithm that analyses multiple GNSS signals to produce an estimate of a geographic position).

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for retrieving, receiving, processing and maintaining a local store of METR data (3.x.x) 

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for interpreting data provided by the receiver (3.x.x) and supplemental data providers (3.x.x) into a format that the METR user (3.x.x) can support

Note 1 to entry: The interpretation can be to another electronic format (e.g., translation among different electronic interface standards) or to a human-machine interface format, as might be performed by a driver support system.

Note 2 to entry: The interpreter can also provide discrepancies to a discrepancy reporter

user

role (ISO 14812:2021, 3.1.6.7) that is responsible for using interpreted rules to fulfil a need

Note 1 to entry: METR users include transport users (ISO 14812:2021, 3.5.2.3) and ancillary users.

Note 2 to entry: The need being fulfilled is often the performance of the dynamic driving task or similar action (e.g., the task of walking in a safe manner that complies with local rules) but can also be trip planning, rule verification, etc.

<METR> METR user (3.3.1.10) that is either a transport user (ISO 14812:2021, 3.5.2.3), a driver (ISO 14812:2021, 3.6.2.3), a driving automation system (ISO 14812:2021, 3.7.3.6), or a driver information system

<METR> METR user (3.3.1.10) that is not a transport-related user (3.3.1.11)

Note 1 to entry: Ancillary users typically provide verification of the system or support transport users in their transport needs.

EXAMPLE         insurance company, lawyer, police officer

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for reporting rule information detected in the field using on-board sensors

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for reporting variances between rule information detected using on-board sensors and the rules that it had previously received via METR

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for receiving reports from discovery reporters (3.3.1.11) and discrepancy reporters (3.3.1.12) and passing the information to a rule verifier in an aggregate and anonymous form

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for verifying the contents of reports from discovery reporters (3.3.1.11) and discrepancy reporters (3.3.1.12)

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for compelling compliance with a rule (3.x.x)

Note 1 to entry:   An enforcer can be authorized to enforce rules for multiple jurisdictional entities. For example, a police officer can be authorized to enforce national laws.

Note 2 to entry:   An enforcer can be from an independent organization. For example, a campus can contract with a private enforcement agency or have its own enforcement agency.

<METR> role (ISO 14812:2021, 3.1.6.7) that is responsible for making formal judgements on disputed matters related to rules (3.x.x)

management of electronic transport regulations

collection of ITS services (ISO 14812:2021, 3.5.3.1) that provide for the distribution of rules (3.x.x) in an electronic format for the surface transport system (ISO 14812:2021, 3.1.2.3)

service to find resources, entities or services based on a specification of the desired target

[ISO/IEC 20924:2021, 3.1.16]

aggregation of at least one METR distribution system with at least one METR user

ITS component (ISO 14812:2021, 3.1.8.2) that fulfils one or more of the METR roles

set of one or more ITS components that jointly fulfil the translator (3.x.x), collector (3.x.x), and disseminator (3.x.x) roles

aggregation of the METR network and supplemental data providers

<METR> service where one or more METR receivers assist in verifying and/or enhancing the accuracy of the METR distribution system by providing data obtained in the field

Note 1 to entry: The data can be sent through and summarized by an intermediary, such as an OEM.

Note 2 to entry: The data can be used as the initial source for data.

Note 3 to entry: The data can be used to update METR data to reflect real-time changes such as due to natural disasters.

physical mechanism used to convey information to travellers

<transport> physical structure or installation, including related site works, serving one or more transport-related purposes

<transport> system of facilities, equipment and services needed for the operation of a transport network

area of transport infrastructure with notifications that alert travellers to construction, maintenance, or utility work activities

transport using moderately low-speed (ISO 14812, 3.7.5.3), lightweight, limited sized vehicles

EXAMPLE               SAE 3194:2019 associates this with a curb weight of less than 500 pounds and a top speed of 30 mph or less

EXAMPLE               e-scooter

Note 1 to entry:   Local rules for the exact speed, weight, and size constraints vary.

Ground-based automated micromobility systems (missing “low speed”)

Personal delivery device (PDD)

Sidewalk robot

Delivery bot

Delivery robot

Sidewalk drone

Ground-based drone

Ground-based delivery vehicle / robot / drone

ADS-equipped vehicle designed to operate safely within a pedestrian environment

property that ensures that the actions of an entity can be traced uniquely to the entity

Note 1 to entry:   Accountability allows an entity to be held responsible for its actions and potentially be required to explain them to others.

[SOURCE: ISO 7498-2:1989, note added]

property that identifies the extent to which the recorded data reflect the actual underlying information

property that an entity is what it claims to be

[SOURCE: ISO/IEC 27000:2018, 3.5]

property of being accessible and usable on demand by an authorized entity

[SOURCE: ISO/IEC 27000:2018, 3.7]

degree to which an IT service supports all the specified goals, objectives and data specified by the user

property that information is not made available or disclosed to unauthorized individuals, entities, or processes (3.54)

[SOURCE: ISO/IEC 27000:2018, 3.10]

privacy 

property that information is not collected, retained, or disposed of in an unauthorized manner

Note 1 to entry: Information collection includes aggregating and fusing data to create new data.

Note 2 to entry: When the information relates to a person, the person that the data describes is responsible for granting authorization

Note 3 to entry: When the information relates to a vehicle, the person that owns the vehicle is responsible for granting authorization

security 

preservation of confidentiality (3.10), integrity (3.36) and availability (3.7) of information

[SOURCE: ISO/IEC 27000:2018, 3.28, modified to allow the use of “security” within this document]

property of accuracy and completeness

[SOURCE: ISO/IEC 27000:2018, 3.36]

degree to which actions or events can be proven to have taken place, so that the events or actions cannot be repudiated later

[SOURCE: ISO/IEC 25010]

property of satisfying stated and implied needs for a product, service, system, component, or process

property of consistent intended behaviour and results

[SOURCE: ISO/IEC 27000:2018, 3.55, modified to include “intended”]

property of a system to plan for, adapt to, resist or quickly recover from a potentially disruptive event, whether natural or man-made

[SOURCE: ISO 15392:2019, 3.21, modified to include planning]

expectation that a system does not, under defined conditions, lead to a state in which human life, health, property, or the environment is endangered –

[SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.48]

degree to which an IT service delivers outcomes within time limits to meet user needs

Note 1 to entry: In some cases, service timeliness is affected by a combination of multiple services provided by different service providers. For example, the service of providing traffic signal status is expected to provide not only timely traffic signal status from the traffic signal controller to the RSU, but also timely delivery of the RSU to the vehicle OBU so that the driver or ADS is able to react and safely navigate the intersection.

[SOURCE: ISO/IEC TS 25011:2017, 3.2.6.1, added "to meet user needs" and contextualized note to ITS]

open, comprehensive and understandable presentation of information

[ISO 14040:2006, 3.7]

degree to which a user or other stakeholder has confidence that a product or system will behave as intended

[SOURCE: ISO/IEC 25010:2011, 4.1.3.2]

ability to meet users' expectations in a verifiable way

Note 1 to entry: Depending on the context or sector, and also on the specific product or service, data (3.x.x) and technology used, different characteristics apply and require verification to ensure stakeholders' expectations are met.

Note 2 to entry: Characteristics of trustworthiness include, for instance, reliability, availability, resilience, security, privacy, safety, accountability, transparency, integrity, authenticity, quality, usability and accuracy.

Note 3 to entry: Trustworthiness is an attribute that can be applied to services, products, technology, data and information as well as, in the context of governance, to organizations.

Note 4 to entry:   The Figure shows the relationships among the characteristics of trustworthiness that are defined within this document:

[SOURCE: ISO/IEC 30145-2:2020, 3.9, note 4 added]

property that a system can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use

[SOURCE: ISO 9241-210:2019, 3.13, notes removed, text revised to start with “property that a system”]