Go to CAV-TEC V1.1 Data Types

Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment

1      Definition

An Interaction is a message exchanged between functional components to request or convey Route, Path, or Trajectory information. It includes contextual identifiers and one element representing either a request or a response associated with routing operations.

2      Functional Requirements

An Interaction shall include one and only one of the following elements: RouteRequest, RouteResponse, PathRequest, PathResponse, TrajectoryRequest, or TrajectoryResponse.

If an Interaction contains:

  • a RouteRequest, PathRequest, or TrajectoryRequest, it represents a request;
  • a RouteResponse, PathResponse, or TrajectoryResponse, it represents a response.

An Interaction shall include a Header and may include identifiers, timestamps, an Offline Map identifier, data exchange metadata, and descriptive metadata.

3      Syntax

https://schemas.mpai.community/CAV2/V1.1/data/Interaction.json

4      Semantics

Table 1 – Semantics of the Interaction Data Type

Label
Description
Header Interaction Header – Standard “CAV‑INT‑Vx.y”.
MInstanceID Identifier of the M-Instance (Virtual Space) associated with this Interaction.
UEnvironmentID Identifier of the U-Environment (Real Space) associated with this Interaction.
InteractionID Unique identifier of this Interaction instance.
InteractionTime Time this Interaction was produced.
InteractionSpaceTime Space/Time where/when this Interaction applies.
RouteRequest Request trigger for a new Route.
RouteResponse Route provided in response to a Route Request.
PathRequest Request trigger for a new Path.
PathResponse Path provided in response to a Path Request.
TrajectoryRequest Request trigger for a new Trajectory.
TrajectoryResponse Trajectory provided in response to a Trajectory Request.
DataXMData MPAI-PTF Data Exchange Metadata providing provenance, authorisation, legal, security, and confidence information associated with this Interaction in a trusted data exchange context.
DescrMetadata Human-readable descriptive metadata of the Interaction (plain text, max 2048 characters).

5      Conformance Testing

A Data instance conforms with Interaction (CAV‑INT) if:

  1. The Data validates against the Interaction’s JSON Schema.
  2. All Data in the Interaction’s JSON Schema:
    1. Have the specified type.
    2. Validate against their JSON Schemas.
    3. Conform with their Data Qualifiers.

6      Performance Assessment

Not part of this specification.

Go to CAV-TEC V1.1 Data Types