24315 METR
SoSR: System of Systems Requirements and Architecture


Last modified on 2024-06-28 16:57
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
SoSR-35

1 Scope

The management of electronic transport r…
SoSR-36

2 Normative references

The following documents are referred to …
SoSR-174
ISO/TS 14812:2022, Intelligent transport…
SoSR-175
ISO/TS 24315-1:2024 , Intelligent transp…
SoSR-906
ISO/IEC/IEEE 24765:2017, Systems and sof…
SoSR-9

3 Terms and definitions

For the purposes of this document, the t…
SoSR-1819

3.1 distribution system rule set signer

entity associated with the distribution …
SoSR-1824 NOTE: The distribution system rule set signer …
SoSR-1825 NOTE: The distribution system rule set signer …
SoSR-1820

3.2 regulation system rule set signer

entity associated with the regulation sy…
SoSR-1821 NOTE: Metadata includes useful information (e.…
SoSR-10

4 Symbols and abbreviated terms

SoSR-987

4.1 ADS

Automated Driving System
SoSR-988

4.2 ARC-IT

Architecture Reference for Cooperative a…
SoSR-989

4.3 CCMS

cooperative ITS credentials management s…
SoSR-990

4.4 CV

connected vehicle
SoSR-991

4.5 FM

frequency modulation
SoSR-992

4.6 GNSS

global navigation satellite system
SoSR-993

4.7 HTML

hypertext markup language
SoSR-994

4.8 IEC

International Electrotechnical Commissio…
SoSR-995

4.9 IEEE

Institute of Electrical and Electronics …
SoSR-996

4.10 ISO

Organization for International Standardi…
SoSR-997

4.11 ITS

intelligent transport systems
SoSR-998

4.12 MCMC

maintenance and construction management …
SoSR-999

4.13 METR

management of electronic traffic regulat…
SoSR-1000

4.14 OBE

on-board equipment
SoSR-1001

4.15 OEM

original equipment manufacturer
SoSR-1002

4.16 PID

personal information device
SoSR-1003

4.17 PMR

public mobile robot
SoSR-1004

4.18 RSE

roadside equipment
SoSR-1012

4.19 SoS

system of systems
SoSR-1005

4.20 SoSR

system of systems requirements
SoSR-1006

4.21 SRADS

service registration and discovery servi…
SoSR-1007

4.22 TCD

traffic control device
SoSR-1008

4.23 TS

technical specification
SoSR-1009

4.24 UN

user need
SoSR-1010

4.25 VRU

vulnerable road user
SoSR-1011

4.26 WAIDS

wide-area information disseminator syste…
SoSR-1

5 Overview

SoSR-2

5.1 METR purpose

The ISO 24315 series intends to provide …
SoSR-3

5.2 METR scope

The METR SoS is designed to provide elec…
SoSR-4

5.3 METR overview

SoSR-176

5.3.1 Functional view

Figure 1 summarizes the functional view …
SoSR-1444

5.3.2 Physical view

SoSR-177

5.3.2.1 Overview

Figure 2 provides a corresponding physic…
SoSR-1445

5.3.2.2 Information flows with the METR SoS

The physical view includes the following…
SoSR-812
  • Discrepancy Contact Centre <—> METR SoS:…
SoSR-814
  • MCMC —> METR SoS: TCD status (as defined…
SoSR-818
  • METR adapter system —> METR SoS: METR di…
SoSR-1013
  • METR SoS —> MCMC: METR information (as d…
SoSR-1446
  • METR SoS —> METR auditor: METR audit inf…
SoSR-816
  • METR SoS —> METR adapter system: METR in…
SoSR-1407
  • METR SoS —> Non-METR Distribution System…
SoSR-817
  • Rule maker —> METR SoS: legal rules (as …
SoSR-1447

5.3.2.3 Other relevant information flows

In addition to the information flows ide…
SoSR-1449
  • METR adapter system —> METR user: user u…
SoSR-1448
  • METR user —> METR adapter system: suppor…
SoSR-1450
  • Supporting data provider —> METR adapter…
SoSR-1451

5.3.2.4 Physical objects

The top-level physical view includes the…
SoSR-1452
Physical object Description Assigned pro…
SoSR-1453

5.3.2.5 Component systems within the METR SoS

Clause 8 further analyses the internals …
SoSR-8

5.4 Assumptions and dependencies

SoSR-183

5.4.1 Assumptions

SoSR-188

5.4.1.1 Internet-based communications

It is assumed that the METR SoS will lik…
SoSR-899

5.4.1.2 Leverage existing standards

METR is one ITS service among many exist…
SoSR-952

5.4.1.3 Supporting data

It is assumed that supporting data provi…
SoSR-953 NOTE: Being able to provide evidence that accu…
SoSR-903

5.4.1.4 Avoiding vehicle inoperability

It is assumed that vehicles will not bec…
SoSR-904 NOTE: This can be achieved by allowing the veh…
SoSR-184

5.4.2 Dependencies

SoSR-189
The requirements defined in this documen…
SoSR-919
  • publicly available communication technol…
SoSR-920
  • inputs from supporting data providers as…
SoSR-1247
  • availability of both maps and map update…
SoSR-1248
  • being able to align the map quickly and …
SoSR-378

5.5 Traceability conventions

Within the systems engineering process, …
SoSR-1455
From the perspective of the developers o…
SoSR-951
Table 1 indicates the rules for each tra…
SoSR-921
Source Type Destination Each functional …
SoSR-1454
[1] High-level requirements are used whe…
SoSR-11

6 System of systems requirements

SoSR-922

6.1 General

The SoS requirements are presented in th…
SoSR-923
  • Function: identifies the purpose of the …
SoSR-924
  • Content: identifies the data that is con…
SoSR-925
  • Source or Destination: identifies the in…
SoSR-926
  • Causality: if the flow is initiated by t…
SoSR-927
  • Constraints: identifies any constraints …
SoSR-928
  • Resulting action: identifies the action …
SoSR-462

6.2 Input Requirements

SoSR-487

6.2.1 Information flow: legal rules

SoSR-830

6.2.1.1 Function

The METR SoS accepts legal rules [SOURCE…
SoSR-509

6.2.1.2 Content

The METR input shall include:
SoSR-510
  • METR information, as defined in 6.6.3;
SoSR-518
  • METR information content, as defined in …
SoSR-519
  • METR information meta-data, as defined i…
SoSR-520
  • observable transport rule attributes, as…
SoSR-822
  • additional transport rule attributes, as…
SoSR-522

6.2.1.3 Source

The METR SoS shall obtain the legal rule…
SoSR-523 NOTE: The legal rules are preferably obtained …
SoSR-524

6.2.1.4 Causality

Ideally, the legal rule flow is initiate…
SoSR-525

6.2.1.5 Constraints

No constraints are defined for this info…
SoSR-526

6.2.1.6 Resulting action

Upon receipt of the legal rule flow, the…
SoSR-491

6.2.2 Information flow: METR coordination

SoSR-831

6.2.2.1 Function

The METR SoS shall enable METR operation…
SoSR-555

6.2.2.2 Content

The METR coordination flow can include:
SoSR-832
  • METR information, as defined in 6.6.3;
SoSR-833
  • METR information content, as defined in …
SoSR-834
  • METR information meta-data, as defined i…
SoSR-835
  • observable transport rule attributes, as…
SoSR-836
  • additional transport rule attributes, as…
SoSR-565
  • free text that allows operational person…
SoSR-556

6.2.2.3 Source

The METR SoS shall obtain the METR coord…
SoSR-557

6.2.2.4 Causality

The METR coordination flow is initiated …
SoSR-558

6.2.2.5 Constraints

No constraints are defined for this inpu…
SoSR-559

6.2.2.6 Resulting action

Upon initiation of the METR coordination…
SoSR-496

6.2.3 Information flow: METR discrepancy information

SoSR-867

6.2.3.1 Function

The METR SoS shall accept all METR discr…
SoSR-607

6.2.3.2 Content

The METR discrepancy information flow sh…
SoSR-629
  • METR information identifier, if known, a…
SoSR-632
  • location of the discrepancy;
SoSR-868
  • time at which the discrepancy was detect…
SoSR-630
  • type of discrepancy identified, such as:
SoSR-356
  • electronic discrepancies; and
SoSR-355
  • physical discrepancies;
SoSR-635
  • meta-data about the METR adapter system …
SoSR-631
  • image of the site;
SoSR-633
  • associated sensor readings; and
SoSR-634
  • free form notes.
SoSR-606

6.2.3.3 Source

The METR SoS shall obtain the METR discr…
SoSR-608

6.2.3.4 Causality

The METR discrepancy information flow is…
SoSR-609

6.2.3.5 Constraints

No constraints are defined for this inpu…
SoSR-610

6.2.3.6 Resulting action

After receipt of sufficient METR discrep…
SoSR-493

6.2.4 Information flow: TCD status

SoSR-843

6.2.4.1 Function

The METR SoS shall maintain its awarenes…
SoSR-574

6.2.4.2 Content

The TCD status information flow shall in…
SoSR-579
  • type(s) of TCD implemented (or removed);
SoSR-580
  • associated METR information content, if …
SoSR-581
  • observable transport rule attributes, as…
SoSR-595
  • status of any requested discrepancy corr…
SoSR-583
  • free form notes.
SoSR-575

6.2.4.3 Source

The METR SoS shall obtain the TCD status…
SoSR-576

6.2.4.4 Causality

The TCD status information flow is typic…
SoSR-585 NOTE: It is the responsibility of the MCMC to …
SoSR-577

6.2.4.5 Constraints

SoSR-885
6.2.4.5.1 Change notifications
The MCMC is responsible for providing th…
SoSR-592
6.2.4.5.2 Query
A request for the TCD status flow shall …
SoSR-598
  • the identifier for the TCD of interest;
SoSR-597
  • any reported discrepancy associated with…
SoSR-849
  • the METR information identification for …
SoSR-850
  • free form notes.
SoSR-886
6.2.4.5.3 Query response
The MCMC is responsible for providing th…
SoSR-578

6.2.4.6 Resulting action

Upon receipt of the TCD status informati…
SoSR-586 EXAMPLE: In the case of implementing a stop sign,…
SoSR-981 EXAMPLE: In the case of a resolved discrepancy [S…
SoSR-587 NOTE: The resulting action can be different ba…
SoSR-463

6.3 Output requirements

SoSR-1443

6.3.1 Information flow: METR audit information

SoSR-1456

6.3.1.1 Function

The METR SoS shall enable METR auditors …
SoSR-1457 NOTE: Audits are especially useful to establis…
SoSR-1458

6.3.1.2 Content

The METR audit information can include:
SoSR-1459
  • Information transmitted or received;
SoSR-1460
  • Date and time of transmission or recepti…
SoSR-1461
  • Identification of the destination or ori…
SoSR-1462
  • Authentication information identifying t…
SoSR-1463
  • Auditing attributes as defined in 6.6.8.
SoSR-1464

6.3.1.3 Destination

The METR SoS shall provide the METR audi…
SoSR-1465

6.3.1.4 Causality

The METR audit information flow is initi…
SoSR-1466

6.3.1.5 Constraints

The METR auditor can specify filtering c…
SoSR-1467

6.3.1.6 Resulting action

It is the responsibility of the auditor …
SoSR-499

6.3.2 Information flow: METR coordination

SoSR-858

6.3.2.1 Function

The METR SoS shall enable METR operation…
SoSR-663

6.3.2.2 Content

The METR coordination flow can include:
SoSR-860
  • METR information, as defined in 6.6.3;
SoSR-861
  • METR information content, as defined in …
SoSR-862
  • METR information meta-data, as defined i…
SoSR-863
  • observable transport rule attributes, as…
SoSR-864
  • additional transport rule attributes, as…
SoSR-859
  • free text that allows operational person…
SoSR-670

6.3.2.3 Destination

The METR SoS shall provide the METR coor…
SoSR-671

6.3.2.4 Causality

The METR SoS shall enable METR operation…
SoSR-674

6.3.2.5 Constraints

No constraints are defined for this outp…
SoSR-675

6.3.2.6 Resulting action

It is the responsibility of the operatio…
SoSR-1372

6.3.3 Information flow: METR information

SoSR-1373

6.3.3.1 Function

The METR SoS shall provide authorized re…
SoSR-1374

6.3.3.2 Content

The METR information flow shall include …
SoSR-1375
  • feature catalogue, as defined in 6.6.2;
SoSR-1376
  • METR information, as defined in 6.6.3;
SoSR-1377
  • METR information content, as defined in …
SoSR-1378
  • METR information meta-data, as defined i…
SoSR-1379
  • observable transport rule attributes, as…
SoSR-1380
  • additional transport rule attributes, as…
SoSR-1381

6.3.3.3 Destination

The METR SoS shall provide METR informat…
SoSR-1382

6.3.3.4 Causality

The METR SoS shall provide METR informat…
SoSR-1384

6.3.3.5 Constraints

SoSR-1385
6.3.3.5.1 Location constraint
The METR SoS may allow subscribed system…
SoSR-1386
  • proximity from a point location;
SoSR-1387
  • proximity along a route; or
SoSR-1388
  • user-defined area.
SoSR-1389 NOTE: The mobile user can vary its location co…
SoSR-1390
6.3.3.5.2 Content constraint
The METR SoS may allow subscribed system…
SoSR-1398
6.3.3.5.3 Response time
The METR SoS shall begin providing the M…
SoSR-1399
6.3.3.5.4 Data quality
The METR SoS shall only distribute METR …
SoSR-1403
6.3.3.5.5 Emerging rule availability
The METR SoS shall provide authorized sy…
SoSR-1405

6.3.3.6 Resulting action

The requesting system is responsible for…
SoSR-464

6.3.4 Information flow: METR information for adaptation

SoSR-855

6.3.4.1 Function

The METR SoS shall provide METR adapter …
SoSR-465

6.3.4.2 Content

METR information for adaptation flow sha…
SoSR-467
  • feature catalogue, as defined in 6.6.2;
SoSR-468
  • METR information, as defined in 6.6.3;
SoSR-469
  • METR information content, as defined in …
SoSR-655
  • METR information meta-data, as defined i…
SoSR-656
  • observable transport rule attributes, as…
SoSR-657
  • additional transport rule attributes, as…
SoSR-466

6.3.4.3 Destination

The METR SoS shall provide METR informat…
SoSR-470

6.3.4.4 Causality

The METR SoS shall provide the METR info…
SoSR-676 NOTE: Within the context of this document, the…
SoSR-856

6.3.4.5 Constraints

SoSR-471
6.3.4.5.1 Location constraint
The METR SoS shall provide METR informat…
SoSR-472
  • proximity from a point location;
SoSR-473
  • proximity along a route; and
SoSR-474
  • user-defined area.
SoSR-661 NOTE: The mobile user can vary its location co…
SoSR-475
6.3.4.5.2 Content constraint
The METR SoS shall provide the METR info…
SoSR-476
  • manually reported characteristics (i.e.,…
SoSR-1818
  • authenticated permits (e.g., permissions…
SoSR-477
  • detectable characteristics;
SoSR-478
  • static characteristics; and
SoSR-662
  • METR information type (e.g., rule catalo…
2022-12-30: Kenneth Vaughn

Needed so that users can identify areas that support rule categories without asking for all rules (e.g., for routing I first want to exclude areas that do not support types of data)

SoSR-865 NOTE: This division of characteristics is inte…
SoSR-220
6.3.4.5.3 Provide rules in priority order
The METR SoS shall deliver METR informat…
SoSR-409 NOTE: This requirement can assist in fulfillin…
SoSR-480
6.3.4.5.4 Response time
The METR SoS shall begin providing the M…
SoSR-979
6.3.4.5.5 Verified information
The METR distributor shall only distribu…
SoSR-207
6.3.4.5.6 Information delivery
The METR SoS shall ensure that each METR…
SoSR-410 EXAMPLE: A jurisdiction uses a wide-area informat…
SoSR-411 NOTE: The probability that a user system can a…
SoSR-74
6.3.4.5.7 METR information availability
The METR SoS shall ensure the continued …
SoSR-408 NOTE: Mobile users are responsible for determi…
SoSR-680 EXAMPLE: Users can refresh rules often enough to …
SoSR-1411 EXAMPLE: Use a guaranteed delivery, subscription-…
SoSR-1412 EXAMPLE: Local beacons that notify approaching ve…
SoSR-1413 EXAMPLE: Local signs that notify approaching vehi…
SoSR-1414 EXAMPLE: Obtain access to low frequency spectrum …
SoSR-339
6.3.4.5.8 Emerging rule availability
The METR SoS shall provide users with re…
SoSR-162
6.3.4.5.9 Remote emergent rules
Upon direction from a rule maker, the ME…
SoSR-483

6.3.4.6 Resulting action

The requesting user is responsible for d…
SoSR-500

6.4 Functional requirements

SoSR-503

6.4.1 Verification of METR rules

SoSR-167

6.4.1.1 Verify locations associated with rules

The METR SoS shall verify that the locat…
SoSR-159

6.4.1.2 Maintain awareness of rule makers

The METR SoS shall be cognizant of the a…
SoSR-62

6.4.1.3 Verify rule consistency

The METR SoS shall identify inconsistenc…
SoSR-677

6.4.1.4 Ensure data quality

All information shall be verified and si…
SoSR-1468 NOTE: The extent of verification can be establ…
SoSR-1813

6.4.1.5 Ensure data resiliency

The METR SoS shall provide a local data …
SoSR-501

6.4.2 METR information storage requirements

SoSR-678

6.4.2.1 Availability

The METR SoS shall maintain the availabi…
SoSR-679

6.4.2.2 Integrity

The METR SoS shall maintain the integrit…
SoSR-105

6.4.2.3 Access control for data

The METR SoS shall only grant access to …
SoSR-103

6.4.2.4 Ensure confidentiality of stored information

The METR SoS shall maintain the confiden…
SoSR-965

6.4.2.5 Limited data storage

The METR SoS shall only store data that …
SoSR-107

6.4.2.6 Ensure data privacy

The METR SoS shall only use data for pur…
2022-05-03: Kenneth Vaughn

Any suggestions on how to be more specific and yet still appropriate?

SoSR-964 NOTE: Some jurisdictions have legal requiremen…
SoSR-344

6.5 Applicable ITS station unit requirements

SoSR-851

6.5.1 Support services

SoSR-852

6.5.1.1 Service registration and discovery

SoSR-876
6.5.1.1.1 Service registration
The METR SoS shall register the followin…
SoSR-878
  • distribution service; and
SoSR-879
  • discrepancy handling service.
SoSR-877
6.5.1.1.2 Service discovery
The METR SoS shall use the service regis…
SoSR-880
  • distribution service; and
SoSR-881
  • discrepancy handling service.
SoSR-218

6.5.1.2 ITS system management

SoSR-217
6.5.1.2.1 Use preferred communications
The METR SoS shall use the communication…
SoSR-900 NOTE: Communication technologies with limited …
SoSR-210
6.5.1.2.2 METR updates and patches
The METR SoS shall manage the installati…
SoSR-228
6.5.1.2.3 METR device management
The METR SoS shall manage each METR infr…
SoSR-55
6.5.1.2.4 Manage services
The METR SoS shall manage the services r…
SoSR-209
6.5.1.2.5 Resource management
The METR SoS shall manage the resources …
SoSR-56
6.5.1.2.6 Radio frequency regulations
The METR SoS shall comply with local reg…
SoSR-967
6.5.1.2.7 System resiliency
The METR SoS shall recover from any serv…
SoSR-968
6.5.1.2.8 System availability
The METR SoS shall be available to provi…
SoSR-1814
6.5.1.2.9 Connectivity awareness
The METR SoS shall allow the METR user t…
SoSR-47

6.5.1.3 ITS security support

SoSR-48
6.5.1.3.1 Obtain policies
The METR SoS shall obtain relevant polic…
SoSR-50
6.5.1.3.2 Implement enrolment policies
The METR SoS shall implement the relevan…
SoSR-45
6.5.1.3.3 Implement authorization policies
The METR SoS shall implement the relevan…
SoSR-52
6.5.1.3.4 Implement misbehaviour reporting policies
The METR SoS shall implement relevant mi…
SoSR-51
6.5.1.3.5 Implement revocation policies
The METR SoS shall implement relevant re…
2022-04-27: Kenneth Vaughn

This sounds like the METR system is revoking certificates; is there a better way to phrase this to clarify that METR is honouring the revocation lists?

SoSR-49
6.5.1.3.6 Ensure authenticated communications
The METR SoS shall ensure that all commu…
SoSR-104
6.5.1.3.7 Confidential communications
The METR SoS shall encrypt any data that…
SoSR-887
6.5.1.3.8 Access control for operations
The METR SoS shall only grant access to …
SoSR-106
6.5.1.3.9 Maintain change log
Within the required data privacy limits,…
SoSR-108
6.5.1.3.10 Terms of service
The METR SoS shall provide the terms of …
SoSR-345
6.5.1.3.11 Disclose use of information
When requested, the METR SoS shall discl…
SoSR-150
6.5.1.3.12 Maintain security certificates
The METR SoS shall maintain its security…
SoSR-869

6.5.2 Timeliness

SoSR-1811

6.5.2.1 Pre-announced rule completeness

The METR SoS shall allow the METR user t…
SoSR-870

6.5.2.2 Time to refresh

The METR SoS shall provide an efficient …
SoSR-97

6.5.2.3 Emergent rule availability

The METR SoS shall distribute any active…
SoSR-1812
Within this context, a relevant rule set…
SoSR-872 NOTE: When immediately enacting a new, long-te…
SoSR-149

6.5.3 Efficient exchange

The METR SoS shall deliver METR informat…
SoSR-929

6.5.4 Filtering

The METR SoS shall deliver METR informat…
SoSR-100

6.5.5 Open specification

For all interfaces between physical obje…
SoSR-898

6.5.6 Backwards compatibility

The METR SoS shall support interoperabil…
SoSR-901

6.5.7 Forward compatibility

The METR SoS shall provide interfaces th…
SoSR-902 EXAMPLE: Support for rules related to low-altitud…
SoSR-101

6.5.8 Language neutral

The METR SoS shall provide all rules and…
SoSR-360

6.6 METR information requirements

SoSR-79

6.6.1 General

The METR SoS shall require rules to be d…
SoSR-102

6.6.2 Feature catalogue

The METR SoS shall provide a catalogue o…
SoSR-512

6.6.3 METR information

SoSR-60

6.6.3.1 Jurisdictional vocabulary

The METR SoS shall be aware of relevant …
SoSR-129
  • vehicle terms (e.g., what vehicles quali…
SoSR-128
  • facility terms (e.g., if there is a defa…
SoSR-168
  • weather terms (e.g., if a different spee…
2022-05-09: Kenneth Vaughn

Should we treat environmental (and other) conditions this way? In other words, if a lower speed limit applies when it is raining, how does a vehicle know when it is precipitating:

a. The rule does not provide any guidance

b. The rule defines an explicit rate of precipitation

c. The rule refers to a environmental classification of "precipitation" that defines a specific rate

SoSR-954
  • air quality and emission terms (e.g., wh…
SoSR-147
  • restriction terms (e.g., what qualifies …
SoSR-404
  • user terms (e.g., class of driver licens…
SoSR-405
  • usage terms (e.g., delivery for hire).
SoSR-807

6.6.3.2 Defined area catalogue

The METR SoS shall maintain a catalogue …
SoSR-221
  • the geographical boundaries of the defin…
SoSR-337
  • the jurisdictional entity with authority…
SoSR-354
  • whether the defined area is believed to …
SoSR-1239 NOTE: Boundaries for defined areas can be defi…
SoSR-1240 NOTE: A translation agent can also define seco…
SoSR-1241 EXAMPLE: A translation agent for a nation can est…
SoSR-808

6.6.3.3 Facility catalogue

The METR SoS shall maintain a catalogue …
SoSR-803
  • the location of the transport facility […
SoSR-169
  • the jurisdictional entity with authority…
SoSR-65

6.6.3.4 Rule catalogue

The METR SoS shall indicate rule categor…
SoSR-1238 NOTE: In order to claim that all rules are sup…
SoSR-802

6.6.3.5 Supporting data provider catalogue

The METR SoS shall maintain a catalogue …
SoSR-75
  • availability of each data provider [SOUR…
SoSR-92
  • cyber location [SOURCE: ISO 24315-1:2024…
SoSR-962
  • information required to authenticate the…
SoSR-963
  • an indication of the data that the data …
SoSR-796

6.6.3.6 Transport rules

The METR SoS shall be aware of all trans…
SoSR-85

6.6.4 METR information content

SoSR-957

6.6.4.1 General

All METR information content shall be pr…
SoSR-69

6.6.4.2 METR information identifier

For each item of METR information, the M…
SoSR-70

6.6.4.3 METR information type

For each item of METR information, the M…
SoSR-1816

6.6.4.4 Verification level

For each item of METR information, the M…
SoSR-86

6.6.5 METR information meta-data

SoSR-958

6.6.5.1 General

While all data shall be exchanged in a s…
SoSR-67

6.6.5.2 Provenance of information

For each item of METR information, the M…
SoSR-798 NOTE: The provenance can indicate the entity t…
SoSR-80

6.6.5.3 Freshness period

For each item of METR information, the M…
SoSR-403 NOTE: Rules, even emergent rules, can be overr…
SoSR-1815 NOTE: For efficiency, a default freshness peri…
SoSR-961

6.6.5.4 Confidence Metrics

For each category of METR information an…
SoSR-975

6.6.5.5 Known conflicts

For each item of METR information with a…
SoSR-977
  • indicate the confirmed discrepancy;
SoSR-978
  • indicate whether continued discrepancy r…
SoSR-976
  • provide guidance as to how the discrepan…
SoSR-87

6.6.6 Observable transport rule attributes

SoSR-959

6.6.6.1 General

Observable transport rule attributes sha…
SoSR-797

6.6.6.2 Transport rule type

For each transport rule, the METR SoS sh…
SoSR-114

6.6.6.3 Transport rule location

For each transport rule, the METR SoS sh…
SoSR-123

6.6.6.4 Transport rule temporal characteristics

For each transport rule, the METR SoS sh…
SoSR-122

6.6.6.5 Transport rule applicability characteristics

For each transport rule, the METR SoS sh…
SoSR-205

6.6.6.6 Transport rule status

For each transport rule, the METR SoS sh…
SoSR-844

6.6.6.7 Transport rule expected implementation date

If the status of the transport rule is n…
SoSR-821

6.6.7 Additional transport rule attributes

SoSR-960

6.6.7.1 General

Additional rule attributes shall not be …
SoSR-121

6.6.7.2 Transport rule enforceability

For each transport rule, the METR SoS sh…
SoSR-148

6.6.7.3 Transport rule precedence

For each transport rule, the METR SoS sh…
SoSR-90

6.6.7.4 Transport rule priority

For each transport rule, the METR SoS sh…
SoSR-161

6.6.7.5 Transport rule signing organization

For each transport rule, the METR SoS sh…
2023-08-21: Kenneth Vaughn

Should be rule-maker rather than translator

SoSR-91

6.6.7.6 Associated supporting data

For each piece of supporting data requir…
SoSR-94
  • the supporting data to be provided; and
SoSR-420
  • each supporting data provider authorized…
SoSR-1469

6.6.8 Auditing attributes

SoSR-1470

6.6.8.1 Transport rule translation agent

For each transport rule, the METR SoS sh…
SoSR-1471

6.6.8.2 Transport rule verification agent

For each transport rule, the METR SoS sh…
SoSR-1472

6.6.8.3 Transport rule signing agent

For each transport rule, the METR SoS sh…
SoSR-506

7 Actor responsibilities

SoSR-932

7.1 Rule maker responsibilities

SoSR-64

7.1.1 Maintain rules

The rule maker is responsible for creati…
SoSR-234

7.1.2 Define location accurately

It is the responsibility of the METR rul…
SoSR-412 EXAMPLE: A parking rule is likely to require grea…
SoSR-930

7.2 METR user responsibilities

SoSR-873

7.2.1 Acquire rules before travelling

A METR user is responsible for being awa…
SoSR-874 NOTE: A user can obtain transport rules throug…
SoSR-507

7.2.2 Identify necessary rule criteria

The METR user is responsible for notifyi…
SoSR-1817

7.2.3 Obtain necessary supporting data

The METR user is responsible for obtaini…
SoSR-508

7.2.4 Process rules

The METR user is responsible for combini…
SoSR-934

7.2.5 Identify discrepancies

Any inconsistencies detected among METR …
SoSR-353

7.2.6 Mapping

It is the responsibility of users of MET…
SoSR-171

7.2.7 Determine user's location

It is the responsibility of the METR use…
SoSR-173

7.2.8 Determine environmental conditions

It is the responsibility of METR users t…
SoSR-1415

7.3 Implementer responsibilities

The implementer is responsible for ensur…
SoSR-1473

7.4 Auditor responsibilities

The auditor is responsible for investiga…
SoSR-325

8 System-level reference architecture

SoSR-376

8.1 Overview

2022-12-02: Kenneth Vaughn

This text should be reviewed by Tom, especially the way we reference ARC-IT (i.e., is this a part of ARC-IT, derived from ARC-IT, etc.)

SoSR-1014
This system reference architecture for M…
SoSR-1249
This document defines architectural elem…
SoSR-1474

8.2 Physical view

SoSR-1475

8.2.1 Mapping to functional view

Figure 4 depicts the assignment of the p…
SoSR-1476
The primary responsibilities of these sy…
SoSR-1477
  • service registration and discovery (8.2.…
SoSR-1478
  • security and credentials management (8.2…
SoSR-1479
  • device certification and enrolment (8.2.…
SoSR-1480
  • core authorization (8.2.8); and
SoSR-1481
  • system monitoring (8.2.9).
SoSR-1482 NOTE: For brevity, the (1) security and creden…
SoSR-1483 NOTE: Support flows that are defined in ARC-IT…
SoSR-1484

8.2.2 Centralized METR information distribution service package

SoSR-1485

8.2.2.1 Overview

The physical view for the centralized ME…
SoSR-1486

8.2.2.2 Physical objects

The centralized METR information distrib…
SoSR-1487
  • maintenance and construction management …
SoSR-1488
  • METR consumer system [SOURCE: ISO 24315-…
SoSR-1489
  • METR discrepancy handling system [SOURCE…
SoSR-1490
  • METR distribution system [SOURCE: ISO 24…
SoSR-1491
  • METR regulation system [SOURCE: ISO 2431…
SoSR-1492
  • METR user, as defined in 5.3.2.4 and 7.1…
SoSR-1493
  • METR adapter [SOURCE: ISO 24315-1:2024, …
SoSR-1494
  • non-METR distribution centre;
SoSR-1495
  • other METR distribution centre;
SoSR-1496
  • other METR regulation centre;
SoSR-1497
  • rule implementation agent;
SoSR-1498
  • rule signing agent;
SoSR-1499
  • rule translation agent;
SoSR-1500
  • rule verification agent; and
SoSR-1501
  • supporting data provider.
SoSR-1502

8.2.2.3 Information flows

The centralized METR information distrib…
SoSR-1503
  • METR coordination;
SoSR-1504
  • METR emergent rule input;
SoSR-1505
  • METR feedback;
SoSR-1506
  • METR information;
SoSR-1507
  • METR information for consumers;
SoSR-1508
  • METR information signature request;
SoSR-1509
  • METR input;
SoSR-1510
  • signed METR information;
SoSR-1511
  • supporting data;
SoSR-1512
  • TCD implementation status;
SoSR-1513
  • TCD status;
SoSR-1514
  • unverified METR information;
SoSR-1515
  • user updates; and
SoSR-1516
  • verified METR information.
SoSR-1517

8.2.2.4 Description

SoSR-1518
8.2.2.4.1 Information input
The rule translation agent enters releva…
SoSR-1519
8.2.2.4.2 Information verification
Local policies may encourage or require …
SoSR-1520
8.2.2.4.3 Information signing
Once a legal rule has been translated in…
SoSR-1521
8.2.2.4.4 Physical and METR rule synchronicity
When new legal rules are approved, the p…
SoSR-1522 NOTE: The implementation of the TCD and the cr…
SoSR-1523 NOTE: A METR rule can be associated with multi…
SoSR-1524
8.2.2.4.5 Internal information distribution
METR information that is signed can be s…
SoSR-1525
METR information is also forwarded to ot…
SoSR-1526
If supported, METR information can be fo…
SoSR-1527
8.2.2.4.6 Information distribution to users
As the METR distribution system receives…
SoSR-1528
  • there is a large volume of information t…
SoSR-1529
  • most of this information is relatively s…
SoSR-1530
  • any of the information can potentially c…
SoSR-1531
  • the information that needs to be distrib…
SoSR-1532
  • individual METR users connect and discon…
SoSR-1533
  • because METR consumer systems are typica…
SoSR-1534
As a result of these challenges, it is e…
SoSR-1535

8.2.3 Localized METR information distribution

SoSR-1536

8.2.3.1 Overview

The physical view for the localized METR…
SoSR-1537

8.2.3.2 Physical objects

The localized METR information distribut…
SoSR-1538
  • ITS roadway equipment;
SoSR-1539
  • METR consumer system within a METR user …
SoSR-1540
  • METR discrepancy handling system/centre;
SoSR-1541
  • METR distribution system within connecte…
SoSR-1542
  • METR distribution system/centre;
SoSR-1543
  • METR regulation system within a METR inp…
SoSR-1544
  • METR regulation system/centre;
SoSR-1545
  • METR user;
SoSR-1546
  • METR adapter system within a METR user d…
SoSR-1547
  • METR verification centre;
SoSR-1548
  • non-METR distribution system;
SoSR-1549
  • other METR regulation system;
SoSR-1550
  • rule signing agent;
SoSR-1551
  • rule translation agent;
SoSR-1552
  • supporting data provider; and
SoSR-1553
  • specialized vehicle (SV) on-board equipm…
SoSR-1554

8.2.3.3 Information flows

The localized METR information distribut…
SoSR-1555
  • field equipment status;
SoSR-1556
  • local METR information for consumers;
SoSR-1557
  • METR application information;
SoSR-1558
  • METR application status;
SoSR-1559
  • METR device status;
SoSR-1560
  • METR emergent rule input;
SoSR-1561
  • METR feedback;
SoSR-1562
  • METR information;
SoSR-1563
  • METR information for consumers;
SoSR-1564
  • METR information signature request;
SoSR-1565
  • METR management information;
SoSR-1566
  • signed METR information;
SoSR-1567
  • supporting data; and
SoSR-1568
  • user update.
SoSR-1569

8.2.3.4 Description

SoSR-1570
8.2.3.4.1 Information input
The service package logically starts wit…
SoSR-1571
8.2.3.4.2 Information internal distribution
METR information can also be sent to oth…
SoSR-1572
If supported, METR information can be fo…
SoSR-1573
8.2.3.4.3 Establishing localized distribution
Localized rules can be disseminated thro…
SoSR-1574
8.2.3.4.4 Monitoring and managing localized distribution
The METR input device should inform its …
SoSR-1575
8.2.3.4.5 Information distribution to users
Localized rules can be locally distribut…
SoSR-1576

8.2.4 Discrepancy management

SoSR-1577

8.2.4.1 Overview

The physical view for the discrepancy ma…
SoSR-1578

8.2.4.2 Physical objects

The discrepancy management service packa…
SoSR-1579
  • discrepancy contact centre;
SoSR-1580
  • maintenance and construction management …
SoSR-1581
  • METR discrepancy handling system/centre;
SoSR-1582
  • METR distribution system/centre;
SoSR-1583
  • METR consumer system within the METR use…
SoSR-1584
  • METR regulation system/centre;
SoSR-1585
  • METR user;
SoSR-1586
  • METR adapter system within the METR user…
SoSR-1587
  • non-METR distribution centre;
SoSR-1588
  • other METR discrepancy handing centre;
SoSR-1589
  • other METR distribution centre;
SoSR-1590
  • other METR regulation centre;
SoSR-1591
  • rule implementation agent;
SoSR-1592
  • rule signing agent;
SoSR-1593
  • rule verification agent; and
SoSR-1594
  • rule translation agent.
SoSR-1595

8.2.4.3 Information flows

The discrepancy management service packa…
SoSR-1596
  • consolidated discrepancy report;
SoSR-1597
  • discrepancy report details;
SoSR-1598
  • discrepancy suppression info;
SoSR-1599
  • METR coordination;
SoSR-1600
  • METR discrepancy report;
SoSR-1601
  • METR emergent rule input;
SoSR-1602
  • METR feedback;
SoSR-1603
  • METR information signature request;
SoSR-1604
  • METR input;
SoSR-1605
  • signed METR information;
SoSR-1606
  • system-generated discrepancy report;
SoSR-1607
  • TCD discrepancy status;
SoSR-1608
  • TCD implementation status;
SoSR-1609
  • unverified METR information;
SoSR-1610
  • user updates; and
SoSR-1611
  • verified METR information.
SoSR-1612

8.2.4.4 Description

SoSR-1613
8.2.4.4.1 User reports of discrepancies
When the METR information adaption funct…
SoSR-1614
8.2.4.4.2 Discrepancy report consolidation
The METR discrepancy handling system wil…
SoSR-1615
METR regulation systems can also learn o…
SoSR-1616
8.2.4.4.3 Discrepancy disposition
When the METR regulation system becomes …
SoSR-1617
Fully resolving a discrepancy might requ…
SoSR-1618
8.2.4.4.4 Supression of confirmed discrepancies
Once a METR regulation system has been a…
SoSR-1619
Alternatively, the regulation system can…
SoSR-1620
Furthermore, the regulation system may w…
SoSR-1622

8.2.5 METR auditing service package

SoSR-1623

8.2.5.1 Overview

The physical view for the METR auditing …
SoSR-1624

8.2.5.2 Physical objects

The auditing service package uses the fo…
SoSR-1627
  • METR auditor;
SoSR-1632
  • METR consumer system within a METR user …
SoSR-1629
  • METR discrepancy handling centre/system;
SoSR-1630
  • METR distribution centre/system;
SoSR-1628
  • METR distribution system within a CV RSE…
SoSR-1631
  • METR distribution system within a SV OBE…
SoSR-1633
  • METR regulation centre/system; and
SoSR-1634
  • METR regulation system within a METR inp…
SoSR-1625

8.2.5.3 Information flows

The discrepancy management service packa…
SoSR-1626

8.2.5.4 Description

The METR auditor queries METR component …
SoSR-1621

8.2.6 Service registration and discovery

METR relies upon the service registratio…
SoSR-1635
  • Centre --> Object registration and disco…
SoSR-1636
  • Object registration and discovery system…
SoSR-1637 NOTE: ISO 23708 is expected to standardize the…
SoSR-386

8.2.7 Security enrolment and credentials management

METR relies upon the "device certificati…
SoSR-786
  • CCMS --> ITS object: enrolment credentia…
SoSR-787
  • CCMS --> ITS object: security credential…
SoSR-789
  • CCMS --> ITS object: security credential…
SoSR-784
  • CCMS --> ITS object: security policy and…
SoSR-785
  • ITS object --> CCMS: device enrolment in…
SoSR-788
  • ITS object --> CCMS: misbehaviour report…
SoSR-1639 NOTE: ISO 23708 is expected to standardize the…
SoSR-388

8.2.8 Core authorization

METR relies upon the core authorization …
SoSR-793
  • Authorizing centre --> CCMS: user permis…
SoSR-792
  • Authorizing centre --> Centre: permissio…
SoSR-790
  • Centre --> Authorizing centre: permissio…
SoSR-791
  • Centre --> Authorizing centre: permissio…
SoSR-1640 NOTE: ISO 23708 is expected to standardize the…
SoSR-795

8.2.9 System monitoring

METR relies upon the core authorization …
2023-01-11: Kenneth Vaughn

Do we need to show this or is this already covered within the emergent rule SP?

SoSR-892
  • CVRSE --> METR Centre: RSE application s…
SoSR-896
  • CVRSE --> Service Monitor System: RSE st…
SoSR-889
  • METR Centre --> CVRSE: equipment control…
SoSR-890
  • METR Centre --> CVRSE: RSE application i…
SoSR-888
  • METR Centre --> CVRSE: RSE application i…
SoSR-891
  • METR Centre --> MCMC: equipment maintena…
SoSR-893
  • METR Centre --> Service Monitor System: …
SoSR-894
  • MCMC --> METR Centre: equipment maintena…
SoSR-895
  • Service Monitor System --> Centre: RSE f…
SoSR-1641 NOTE: ISO 23708 is expected to standardize the…
SoSR-1028

8.2.10 Physical objects

SoSR-1655

8.2.10.1 Overview

The physical objects used in the system-…
SoSR-1029

8.2.10.2 Connected vehicle (CV) roadside equipment (RSE)

The CV RSE represents the roadside devic…
SoSR-1045 NOTE: CV RSEs typically use wireless technolog…
SoSR-1207

8.2.10.3 ITS roadway equipment (IRE)

The IRE represents roadside devices that…
SoSR-1035

8.2.10.4 METR consumer system

The METR consumer system receives guidan…
SoSR-1032

8.2.10.5 METR discrepancy handling centre

A "METR discrepancy handling centre" is …
SoSR-1648

8.2.10.6 METR discrepancy handling system

A METR discrepancy handling system accep…
SoSR-1250 NOTE: The discrepancy handling system can inco…
SoSR-1033

8.2.10.7 METR distribution centre

A "METR distribution centre" is a centre…
SoSR-1649

8.2.10.8 METR distribution system

A METR distribution system collects METR…
SoSR-1038

8.2.10.9 METR distribution vehicle

The METR distribution vehicle is typical…
SoSR-1034

8.2.10.10 METR input device

The METR input device represents any dev…
SoSR-1650

8.2.10.11 METR regulation centre

A "METR regulation centre" is a centre-b…
SoSR-1036

8.2.10.12 METR regulation system

A METR regulation system enables the cre…
SoSR-1652

8.2.10.13 METR user device

A "METR user device" represents any devi…
SoSR-1046

8.2.10.14 Other METR discrepancy handling centre

Depending on deployments scenarios, a di…
SoSR-1653

8.2.10.15 Other METR distribution centre

A METR distribution centre can exchange …
SoSR-1044

8.2.10.16 Other METR regulation centre

A METR regulation centre can exchange ME…
SoSR-1654

8.2.10.17 Rule implementation agent

The rule implementation agent represents…
SoSR-1656

8.2.10.18 Rule signing agent

The rule signing agent represents the pe…
SoSR-1658

8.2.10.19 Rule translation agent

The rule translation agent represents th…
SoSR-1657

8.2.10.20 Rule verification agent

The rule verification agent represents t…
SoSR-1047

8.2.11 Information flows

SoSR-1048

8.2.11.1 consolidated discrepancy report

The "consolidated discrepancy report" fl…
SoSR-1068
  • METR discrepancy handling system --> MET…
SoSR-1069
  • METR discrepancy handling system --> Oth…
SoSR-1049

8.2.11.2 discrepancy report details

While investigating a consolidated discr…
SoSR-1070
  • METR discrepancy handling system --> MET…
SoSR-1071
  • Other METR discrepancy handling system <…
SoSR-1050

8.2.11.3 discrepancy suppression info

Once a METR regulation system has been a…
SoSR-1072
  • METR regulation system --> METR discrepa…
SoSR-1073
  • METR discrepancy handling system <-> Oth…
SoSR-1051

8.2.11.4 field equipment status

The ‘field equipment status” information…
SoSR-1074
  • ITS roadway equipment --> Connected vehi…
SoSR-1097

8.2.11.5 local METR information for consumers

The “local METR information for consumer…
SoSR-1094
  • METR distribution system [RSE] --> METR …
SoSR-1095
  • METR distribution system [SV OBE] --> ME…
SoSR-1053

8.2.11.6 METR application information

The “METR application information flow” …
SoSR-1076
  • METR regulation system --> METR distribu…
SoSR-1054

8.2.11.7 METR application status

The “METR application status” informatio…
SoSR-1077
  • METR distribution system [RSE] --> METR …
SoSR-1642

8.2.11.8 METR audit information

The “METR audit information” information…
SoSR-1716
  • METR consumer system --> METR auditor;
SoSR-1717
  • METR discrepancy handling system --> MET…
SoSR-1718
  • METR distribution system --> METR audito…
SoSR-1719
  • METR regulation system --> METR auditor;
SoSR-1055

8.2.11.9 METR coordination

The “METR coordination” information flow…
SoSR-1078
  • METR regulation system <-> Discrepancy c…
SoSR-1079
  • METR regulation system <-> Maintenance &…
SoSR-1080
  • METR regulation system <-> Rule verifica…
SoSR-1081
  • METR regulation system <-> Other METR re…
SoSR-1082
  • Rule verification centre <-> Maintenance…
SoSR-1056

8.2.11.10 METR device status

The “METR device status” information flo…
SoSR-1083
  • METR regulation system --> METR distribu…
SoSR-1057

8.2.11.11 METR discrepancy report

The “METR discrepancy report” informatio…
SoSR-1084
  • METR consumer system --> METR discrepanc…
SoSR-1099
  • METR consumer system --> METR regulation…
SoSR-1643

8.2.11.12 METR emergent rule input

The "METR emergent rule input" informati…
SoSR-1720
  • Rule translation agent --> METR regulati…
SoSR-1058

8.2.11.13 METR feedback

The “METR feedback” information flow sup…
SoSR-1085
  • METR regulation system --> Rule translat…
SoSR-1059

8.2.11.14 METR information

The “METR information” information flow …
SoSR-1087
  • METR regulation system --> maintenance a…
SoSR-1088
  • METR regulation system --> METR discrepa…
SoSR-1089
  • METR regulation system --> METR distribu…
SoSR-1090
  • METR regulation system --> non-METR dist…
SoSR-1091
  • METR regulation system <-> other METR re…
SoSR-1086

8.2.11.15 METR information for consumers

The “METR information for consumers” inf…
SoSR-1093
  • METR distribution system [MDC] --> METR …
SoSR-1242

8.2.11.16 METR information signature request

The "METR information signature request"…
SoSR-1243
This information flow occurs between:
SoSR-1244
  • METR regulation system --> Rule-maker
SoSR-1061

8.2.11.17 METR input

The “METR input” information flow suppor…
SoSR-1096
  • Rule translator agent --> METR regulatio…
SoSR-1062

8.2.11.18 METR management information

If the rule is to be distributed through…
SoSR-1098
  • METR regulation system --> METR distribu…
SoSR-1060

8.2.11.19 signed METR information

The “signed METR information” informatio…
SoSR-1092
  • Rule-maker --> METR regulation system
SoSR-1064

8.2.11.20 supporting data

The "supporting data" information flow i…
SoSR-1101
  • centre --> METR user system (e.g., infra…
SoSR-1102
  • RSE --> METR user system (e.g., infrastr…
SoSR-1103
  • SV OBE --> METR user system (e.g., peer-…
SoSR-1105
  • OBE --> METR user system (e.g., peer-sou…
SoSR-1104
  • METR user --> METR user system (e.g., us…
SoSR-1100 NOTE: Vehicle-sourced supporting data does not…
SoSR-1065

8.2.11.21 system-generated discrepancy report

METR regulation systems can learn of dis…
SoSR-1106
  • METR distribution system --> METR regula…
SoSR-1107
  • Non-METR distribution system --> METR re…
SoSR-1108
  • Other METR regulation system --> METR re…
SoSR-1066

8.2.11.22 TCD discrepancy status

The "TCD discrepancy status" information…
SoSR-1109
  • Maintenance & construction management ce…
SoSR-1067

8.2.11.23 TCD implementation status

The “TCD implementation status” informat…
SoSR-1646
  • Implementer --> Maintenance and construc…
SoSR-1644

8.2.11.24 TCD status

The “TCD status” information flow suppor…
SoSR-1645
  • Maintenance and construction management …
SoSR-1245

8.2.11.25 unverified METR information

The “unverified METR information” inform…
SoSR-1369
  • METR Regulation System --> METR Verifica…
SoSR-1210

8.2.11.26 user updates

The "user updates" information flow prov…
SoSR-1211
  • METR user system --> METR user
SoSR-1246

8.2.11.27 verified METR information

The “verified METR information” flow sup…
SoSR-1370
  • Rule verification centre --> METR regula…
SoSR-1826

8.2.12 Cybersecurity overview

METR includes multiple features to promo…
SoSR-1827
Rules are established by rule makers. Ho…
SoSR-1828
  • send an entire rule set as defined by th…
SoSR-1829
  • repackage the rules as appropriate to al…
SoSR-1830
In either case, the information is trans…
SoSR-1659

8.3 Enterprise view

SoSR-1660

8.3.1 Overview

While the physical view reflects how the…
SoSR-1661
Figure 15 focuses on how each of the ent…
SoSR-1662
Key 4 - METR regulation system 5 - METR …
SoSR-1663

8.3.2 Enterprise objects

SoSR-1749

8.3.2.1 Adapter system developer

SoSR-1750
The developer of the adapter is responsi…
SoSR-1751
  • on-board GNSS feed that provides the loc…
SoSR-1752
  • on-board status of the windshield wipers…
SoSR-1753
  • on-board sensors that might report detec…
SoSR-1754
  • external data source that identifies the…
SoSR-1755
  • external data sources that might provide…
SoSR-1756
The adapter considers all these data sou…
SoSR-1757 NOTE: The algorithm is likely to consider othe…
SoSR-1758
The adapter makes the current active rul…
SoSR-1664

8.3.2.2 Auditor

The auditor is responsible for determini…
SoSR-1747

8.3.2.3 Consumer system developer

SoSR-1748
The consumer system developer [SOURCE: I…
SoSR-1666

8.3.2.4 Device manufacturer

The manufacturer is responsible for deve…
SoSR-1677

8.3.2.5 Device owner

The device owner is responsible for purc…
SoSR-1667

8.3.2.6 Discrepancy contact

The discrepancy contact typically repres…
SoSR-1668

8.3.2.7 Discrepancy handler

SoSR-1795
The primary responsibilities of the disc…
SoSR-1796 NOTE: Jurisdictions will likely need to establ…
SoSR-1669

8.3.2.8 Distributor

The distributor is responsible for colle…
SoSR-1738
For each defined area that it covers, a …
SoSR-1740
  • the categories of pre-announced rules th…
SoSR-1741
  • the categories of emergent rules that th…
SoSR-1742
METR receivers need this information to …
SoSR-1739
An emergent rule distributor [SOURCE: IS…
SoSR-1743
All distributors package rules into one …
SoSR-1671

8.3.2.9 METR user

SoSR-1773
8.3.2.9.1 Overview
Within the existing system, transport us…
SoSR-1774
8.3.2.9.2 Transport-related user
A transport-related user is a METR user …
SoSR-1775
  • drivers;
SoSR-1776
  • micromobility users (including those ope…
SoSR-1777
  • ride sourcing users;
SoSR-1778
  • pedestrians;
SoSR-1779
  • individuals that are sending or receivin…
SoSR-1780
  • fleet managers;
SoSR-1781
  • driving automation systems; and
SoSR-1782
  • PMRs.
SoSR-1783
A transport-related user does not have a…
SoSR-1784
8.3.2.9.3 Ancillary user
An ancillary user is a METR user that is…
SoSR-1785
  • lawyers;
SoSR-1786
  • enforcement personnel;
SoSR-1787
  • insurance companies;
SoSR-1788
  • academic institutions;
SoSR-1789
  • automotive repair facilities;
SoSR-1790
  • traffic managers;
SoSR-1791
  • rule makers; and
SoSR-1792
  • policy makers.
SoSR-1793
An ancillary user does not have any addi…
SoSR-1794 NOTE: Some ancillary users can be authorized t…
SoSR-1672

8.3.2.10 METR adapter system developer

The METR adaptor system developer is res…
SoSR-1744

8.3.2.11 Non-METR distributor

SoSR-1745
A non-METR distributor [SOURCE: ISO 2431…
SoSR-1746 NOTE: A non-METR distributor strips the rule-s…
SoSR-1670

8.3.2.12 Rule implementer

SoSR-1721
8.3.2.12.1 General
The rule implementer [SOURCE: ISO 24315-…
SoSR-1722
8.3.2.12.2 Announcing the implementation
Distributing updates of pre-announced ru…
SoSR-1723
  • providing supporting data that implement…
SoSR-1724
  • creating a temporary emergent rule to re…
SoSR-1725
8.3.2.12.3 Avoiding rule duplication
In either case, the information would ne…
SoSR-1726
  • Step 1 - A new stop sign is installed, a…
SoSR-1727
  • Step 2 - The pre-announced rule distribu…
SoSR-1728
  • Step 3 - The freshness period for prior …
SoSR-1729
During Step 2, some METR user systems wi…
SoSR-1730
8.3.2.12.4 Updating the pre-announced rule
Once the TCD is implemented and the rele…
SoSR-1731
  • The implementer notifying the translator…
SoSR-1732
  • The implementer notifying the rule verif…
SoSR-1733
  • The implementer notifying both the trans…
SoSR-1673

8.3.2.13 Rule maker

The rule maker is responsible for making…
SoSR-1678

8.3.2.14 Rule signer

The rule signer is responsible for signi…
SoSR-1674

8.3.2.15 Rule verifier

The rule verifier is responsible for ver…
SoSR-1675

8.3.2.16 Supporting data provider

SoSR-1759
8.3.2.16.1 General
Although supporting data providers are a…
SoSR-1760
8.3.2.16.2 External data providers
External data providers are supporting d…
SoSR-1761
  • peer-sourced data providers, which is pr…
SoSR-1762
  • infrastructure data providers (e.g., sig…
SoSR-1763
8.3.2.16.3 Vehicle-sourced data providers
A vehicle-sourced data provider is a sto…
SoSR-1764
  • static vehicular characteristics (e.g., …
SoSR-1765
  • on-board sensors reporting dynamic vehic…
SoSR-1766
  • on-board sensors reporting external cond…
SoSR-1767
8.3.2.16.4 User-sourced data providers
A user-sourced data provider is a stored…
SoSR-1768
  • Touchscreen displays (e.g., for manual i…
SoSR-1769
  • Bluetooth connections (e.g., for electro…
SoSR-1770
  • QR code, chip readers, and similar devic…
SoSR-1772
Due to the varied degree of trustworthin…
SoSR-1771
8.3.2.16.5 Other classification schemes
Data can also be classified as either cr…
SoSR-1676

8.3.2.17 Translator

The translator is responsible for conver…
SoSR-1734
A translator can use an entirely manuall…
SoSR-1735
  • deploy one or more specially authorized …
SoSR-1736
  • coordinate with other translators to obt…
SoSR-1737
Regardless of the process used, the tran…
SoSR-1679

8.3.3 Agreements and expectation definitions

SoSR-1700

8.3.3.1 General

It is expected that agreements that requ…
SoSR-1701
  • require the client (e.g., distributor) t…
SoSR-1702
  • require the provider (e.g., translator) …
SoSR-1703
Ideally all conflicts and inconsistencie…
SoSR-1680

8.3.3.2 Current rule or provisioning agreement

An agreement that the provider (e.g., co…
SoSR-1681

8.3.3.3 Discrepancy reporting agreement

An agreement that the provider (e.g., di…
SoSR-1682

8.3.3.4 Expectation of audit information

An expectation that the provider (i.e., …
SoSR-1683

8.3.3.5 Expectation of coordination

An expectation that the provider and cli…
SoSR-1684

8.3.3.6 Expectation of discrepancy issue

An expectation that the provider (i.e., …
SoSR-1685

8.3.3.7 Expectation of discrepancy reports

An expectation that the provider (e.g., …
SoSR-1686

8.3.3.8 Expectation of relevant rules

An expectation that the provider (e.g., …
SoSR-1687

8.3.3.9 Expectation of rules

An expectation that the provider will ma…
SoSR-1688

8.3.3.10 Expectation of supporting data

An expectation that the provider (e.g., …
SoSR-1689

8.3.3.11 Expectation of TCD maintenance

An expectation that the provider (i.e., …
SoSR-1690

8.3.3.12 Relevant rule provisioning agreement

An agreement that the provider (e.g., ad…
SoSR-1691

8.3.3.13 Rule distribution agreement

An agreement stating that the provider (…
SoSR-1692

8.3.3.14 Rule provisioning agreement

An agreement that the provider (i.e., tr…
SoSR-1693

8.3.3.15 Rule publication agreement

An agreement that the provider (i.e., ru…
SoSR-1694

8.3.3.16 Rule sharing agreement

An agreement that the provider (e.g., di…
SoSR-1695

8.3.3.17 Rule signing agreement

An agreement that the provider (e.g., ru…
SoSR-1696

8.3.3.18 Rule verification agreement

An agreement stating that the provider (…
SoSR-1697

8.3.3.19 System provisioning agreement

An agreement that the provider (i.e., ma…
SoSR-1698

8.3.3.20 TCD status provisioning agreement

An agreement that the provider (i.e., im…
SoSR-1699

8.3.3.21 Vehicle usage agreement

An agreement that the provider (e.g., ve…
SoSR-1704

8.3.4 Role definitions

The role types referenced in this docume…
SoSR-1705
Role Description Monitors The enterprise…
SoSR-1797

8.3.5 Resources

SoSR-1809

8.3.5.1 General

This clause describes the resources cont…
SoSR-1801

8.3.5.2 Environment

No changes are envisioned for the enviro…
SoSR-1800

8.3.5.3 Public record

No changes are envisioned for the public…
SoSR-1798

8.3.5.4 Rules

The rules discussed in ISO 24315-2:2024,…
SoSR-1799

8.3.5.5 Traffic control devices

The TCDs discussed in ISO 24315-2:2024, …
SoSR-1806

8.3.5.6 Wide area information dissemination system

A wide area information dissemination sy…
SoSR-389

9 Variables

SoSR-390

9.1 General

Variables allow customization of perform…
SoSR-396

9.2 catalogueUpdateInterval

The catalogueUpdateInterval is the allow…
SoSR-397

9.3 criteriaLatencyTime

The criteriaLatencyTime is the allowable…
SoSR-393

9.4 distributionResponseTime

The distributionResponseTime is the maxi…
SoSR-972

9.5 informationRefreshDuration

The informationRefreshDuration is the mi…
SoSR-970

9.6 metrRecoveryTime

The metrRecoveryTime is the maximum allo…
SoSR-857

9.7 metrResponseTime

The metrResponseTime is the maximum allo…
SoSR-660 NOTE: The metrResponseTime does not consider t…
SoSR-866

9.8 metrUpdateCycle

The amount of time that retrieved METR i…
SoSR-969

9.9 metrUpTimePercent

The metrUpTimePercent is the minimum per…
SoSR-391

9.10 provisionLatency

The provisionLatency is the allowable ti…
SoSR-392

9.11 subscriptionRefreshTime

The subscriptionRefreshTime is the allow…
SoSR-394

9.12 translationUpdateInterval

The translationUpdateInterval is the all…
SoSR-982

10 Conformance

SoSR-985

10.1 General

This annex provides a concise conformanc…
SoSR-909

10.2 Symbols indicating requirement status

Table 1 defines the codes used to specif…
SoSR-910
Abbreviated term Description M Mandatory…
SoSR-911
The O.# (range) notation is used to show…
SoSR-912

10.3 Conditional status notation

The predicate notations in Table 2 may b…
SoSR-913
Notation Description This no…
SoSR-914
The notation means that the …
SoSR-915
The predicates used in the concise confo…
SoSR-916
Predicate Subclause serviceDiscovery Con…
SoSR-984

10.4 Concise conformance table

Table 4 provides the concise conformance…
SoSR-983
Clause Title Conformance 6.2.2 Informati…
SoSR-986 NOTE: For example, item 6.5.1.1.2.b in the las…
SoSR-905

11 Traceability

SoSR-908

11.1 General

Each requirement in this document traces…
SoSR-955

11.2 Column Explanation

Each user need, constraint, and requirem…
SoSR-1416

12 Diagram conventions

SoSR-1706

12.1 Physical view conventions

The physical viewpoint represents physic…
SoSR-1707
Each physical view diagram includes phys…
SoSR-1708
SoSR-1709
Major categories of physical objects inc…
SoSR-1710
  • Centre: An entity that provides applicat…
SoSR-1711
  • Field: An entity located near or along t…
SoSR-1712
  • Support: An entity, typically from a fix…
SoSR-1713
  • Traveller: Equipment used by travellers …
SoSR-1714
  • Vehicle: Vehicle related elements onboar…
SoSR-1417

12.2 Enterprise view conventions

SoSR-1715

12.2.1 Overview

The data expectation diagrams contained …
SoSR-1418

12.2.2 Enterprise objects

Each box with a heavy border in the figu…
SoSR-1419

12.2.3 Resources

Each box with a lightly dashed border re…
SoSR-1420

12.2.4 Relationships

SoSR-1421

12.2.4.1 Agreements

While agreements are often established w…
SoSR-1422
  • authentication requirements for each par…
SoSR-1423
  • non-repudiation requirements, including …
SoSR-1424
  • access control [SOURCE: ISO 24315-1:2024…
SoSR-1425
  • confidentiality requirements; and
SoSR-1426
  • data privacy requirements.
SoSR-1427
If formal agreements cannot be establish…
SoSR-1428

12.2.4.2 Expectations

All expectations include expectations th…
SoSR-1429
  • all data exchanges are authenticated;
SoSR-1430
  • non-repudiation records are maintained f…
SoSR-1431
  • all data exchanges are subject to the in…
SoSR-1432
Any expectation can be formalized into a…
SoSR-1433

12.2.4.3 Roles

Relationships between enterprise objects…
SoSR-1434

12.2.5 Naming conventions

Enterprise view relationships use initia…
SoSR-1435

12.2.6 Relationship status

The status of relationships are depicted…
SoSR-1436

12.2.7 Colour coding of elements

Enterprise objects and resources are col…
SoSR-1437

12.3 Diagrams provide limited context

Reference architectures are typically ve…
SoSR-1251

13 Possible deployments of role-based architecture

SoSR-1252

13.1 Overview

The METR SoS is a complex system of syst…
SoSR-1253

13.2 Physical grouping of functionality

SoSR-1254
Regardless of the amount of area covered…
SoSR-1311 NOTE: Many of the physical objects identified …
SoSR-1255
  • The entry, approval and management of ru…
SoSR-1313
  • The entry, approval and management of ru…
SoSR-1256
  • Localized rule entry: In addition to loc…
SoSR-1371 NOTE: Campuses include any private grounds.
SoSR-1314
  • Centralized rule distribution: Users nee…
SoSR-1315
  • The collection of rules from multiple re…
SoSR-1257
  • The consumer system is separated from th…
SoSR-1316
  • The ISO 24315 series of documents assume…
SoSR-1258
  • The METR discrepancy handling system is …
SoSR-1317
  • The METR discrepancy handling system gro…
SoSR-1318
  • The METR regulation system is separated …
SoSR-1319
The ISO 24315 series documents assume th…
SoSR-1260

13.3 Regulation system inputs

SoSR-1261

13.3.1 Overview

The complexity of a METR regulation syst…
SoSR-1262

13.3.2 Isolated regulation system

If the jurisdictional environment for a …
SoSR-1263

13.3.3 Hierarchical regulation systems

In most cases, it is envisioned that reg…
SoSR-1264

13.3.4 Composite regulation systems

While eventually most regulation systems…
SoSR-1326

13.3.5 Regulation system evolution

Systems evolve over time and early syste…
SoSR-1265

13.3.6 Importance of coordination

Prior to deploying a METR regulation sys…
SoSR-1266

13.4 Populating METR information

SoSR-1267

13.4.1 Overview

One of the challenges of deploying the M…
SoSR-1268

13.4.2 Select rule categories to populate

One useful way to organize the entry of …
SoSR-1331

13.4.3 Pre-announced information

SoSR-1328

13.4.3.1 Define sub-jurisdictions

It is envisioned that most regulation sy…
SoSR-1269

13.4.3.2 Define jurisdictional sub-areas

Large jurisdictional entities (e.g., a l…
SoSR-1329

13.4.3.3 Define key terms

Jurisdictional entities need to ensure t…
SoSR-1270

13.4.3.4 Coordinate entry of pre-announced rules

Ideally, pre-announced rules should be e…
SoSR-1330

13.4.4 Plan for emergent rules

When developing a regulation system, it …
SoSR-1334

13.4.5 Identify supporting data providers

Some rules will require supporting data …
SoSR-1335

13.4.6 Commercial involvement

SoSR-1336

13.4.6.1 Commercial off-the-shelf software

The standardization of interfaces is exp…
SoSR-1337

13.4.6.2 Commercial data entry

In addition to developing commercial off…
SoSR-1272

13.4.6.3 Commercial regulation system

A private company can also enter rules. …
SoSR-1339

13.5 Pre-announced METR information distribution

SoSR-1344

13.5.1 Overview

Due to the volume of information coupled…
SoSR-1325

13.5.2 Distribution of rules

The primary purpose of the pre-announced…
SoSR-1347

13.5.3 Scope of distribution system

SoSR-1348

13.5.3.1 Geographic coverage of rules

It is expected that most distribution sy…
SoSR-1349

13.5.3.2 Rule category coverage

Likewise, distribution systems can have …
SoSR-1350

13.5.3.3 Communications reach

It is expected that most pre-announced d…
SoSR-1340

13.5.4 Number of distribution systems

SoSR-1342

13.5.4.1 Single distribution system

The design of the regulation system need…
SoSR-1343

13.5.4.2 Multiple distribution systems

If the regulation system is expected to …
SoSR-1345

13.5.5 Number of regulation systems

SoSR-1346

13.5.5.1 Single regulation system

If there is a one-to-one relationship be…
SoSR-1323

13.5.5.2 Multiple regulation systems

It is envisioned that, in most deploymen…
SoSR-1324

13.5.6 Maintenance of rules

Distribution systems need to be aware of…
SoSR-1355

13.5.7 Boundary considerations

Another factor to consider when deployin…
SoSR-1273

13.6 Emergent rule distribution

SoSR-1351

13.6.1 Overview

The distribution of emergent rules is mu…
SoSR-1357

13.6.2 Scope of distribution system

It is envisioned that emergent rule dist…
SoSR-1353

13.6.3 Distribution mechanisms

Emergent rules can be distributed throug…
SoSR-1356

13.6.4 Migrating emergent rules to pre-announced rules

Deployments also need to consider how em…
SoSR-1358

13.7 Consumer system deployments

It is expected that consumer systems wil…
SoSR-1359

13.8 Discrepancy handling system deployments

SoSR-1360

13.8.1 Policies for pre-processing reports

SoSR-1362

13.8.1.1 Overview

Discrepancy handling systems are respons…
SoSR-1363

13.8.1.2 Public reports

It is expected that most reports will be…
SoSR-1364

13.8.1.3 Certified reports

In addition to crowd-sourced data [SOURC…
SoSR-1361

13.8.2 Scope of discrepancy handling system

SoSR-1365

13.8.2.1 Geographic coverage area

Deployers of discrepancy handling system…
SoSR-1366

13.8.2.2 Sources of discrepancy reports

Discrepancy reports originate from consu…
SoSR-1367

13.8.2.3 Destination of reports

The discrepancy handling systems also ne…