Definition
Functional Requirements
Syntax
Semantics
Conformance
Performance
1 Definition
A Message exchanged between the Human-CAV Interaction (HCI) subsystem and the Autonomous Motion Subsystem (AMS) of the same CAV. The same Data Type serves both directions: HCI sends it as a Request, the AMS answers with it as a Response.
2 Functional Requirements
The Request – the HCI Message – is sent by HCI to request:
- The Routes to a Destination: the place the passenger asks for, as a Way Point of the Offline Map, possibly with intermediate Way Points and desired Times.
- The Route selected by the passenger among those proposed.
- A Route Command: Execute, Suspend, Resume, Change or Stop the Route.
- The stream of the M-Location corresponding to a U-Location the passenger names, via a Point of View.
The Response – the AMS Message – is sent by the AMS to provide:
- The Routes to the Destination, each segment with the time the CAV is expected at its end; none where the Destination cannot be reached.
- The Route Status: the state of the Route the CAV was commanded to drive – Executing, Suspended, Stopped or Arrived – in answer to each Route Command and on arrival.
- The identifier of a CAV equipment failure condition, the Road State and the CAV State.
The message set is extensible.
3 Syntax
https://schemas.mpai.community/CAV2/V2.0/data/AMSHCIMessage.json
4 Semantics
Table 1 specifies the semantics of the AMS-HCI Message Data Type.
| Label | Type | Req. | Description |
|---|---|---|---|
| Header | string (CAV-AHM-V2.0) | Yes | AMS-HCI Message Header – Standard CAV-AHM-Vx.y |
| MInstanceID | string | Identifier of the M-Instance (Virtual Space) associated with this AMS-HCI Message. | |
| UEnvironmentID | string | Identifier of the U-Environment (Real Space) associated with this AMS-HCI Message. | |
| AMSHCIMessageID | string | Yes | Unique identifier of this AMS-HCI Message instance. |
| AMSHCIMessageTime | Simple Time | Time this AMS-HCI Message was produced. | |
| AMSHCIMessageSpaceTime | Simple Time | Time this AMS-HCI Message was sent. | |
| HCIMessage | object | Data in message from HCI to AMS. | |
| HCIMessage. |
object [] | List of requested Routes with Stops. | |
| HCIMessage. |
Route | A requested Route. | |
| HCIMessage. |
string | Identifier of the reference Offline Map. | |
| HCIMessage. |
string | Identifier of the Route selected by the passenger. | |
| HCIMessage. |
string | Command to apply to the current Route. One of: Execute, Suspend, Resume, Change, Stop. | |
| HCIMessage. |
object | Request to stream the M-Location corresponding to a human-specified U-Location via Point of View. | |
| HCIMessage. |
string | U-Location from which the passenger wishes to observe the environment. | |
| AMSMessage | object | Data in message from AMS to HCI. | |
| AMSMessage. |
Route [] | List of candidate Routes provided in response to an HCI request. | |
| AMSMessage. |
object | State of the Route the CAV was commanded to drive: in answer to a Route Command, and on arrival. | |
| AMSMessage. |
string | Yes | Identifier of the Route this state refers to. |
| AMSMessage. |
string | Yes | Executing: the CAV drives the Route; Suspended: halted, to be resumed; Stopped: halted, the Route abandoned; Arrived: stopped at the Route’s destination. One of: Executing, Suspended, Stopped, Arrived. |
| AMSMessage. |
string | Identifier of a CAV equipment failure condition (e.g. battery low, mechanical failure). | |
| AMSMessage. |
CAV State | Current CAV State. | |
| AMSMessage. |
Road State | Current Road State. | |
| DataXMData | Data Exchange Metadata | MPAI-PTF Data Exchange Metadata providing provenance, authorisation, legal, security, and confidence information associated with this AMS-HCI Message in a trusted data exchange context. | |
| DescrMetadata | string | Human-readable descriptive metadata of the AMS-HCI Message (plain text, max 2048 characters). |
5 Conformance Testing
Data conform to the AMS-HCI Message Data Type when they validate against its schema. If the schema references other schemas, data referencing a secondary schema shall also validate against that schema, if present, and conform with the Qualifier, if present.