1   Definition

A Message sent by the Autonomous Motion Subsystem (AMS) to:

  1. Respond to a previous HCI-AMS Message.
  2. Informs the Human-CAV Interaction.

2   Functional Requirements

An AMS can send the HCI:

  1. A message in response to an HCI-AMS message containing:
    • List of Route options.
  2. Information, such as:
    • Destination reached.
    • Delay compared to plan and amount.
    • Road State.
    • Equipment failure and type.

The message set is obviously extensible.

3   Syntax

https://schemas.mpai.community/CAV2/V1.0/data/FailureID.json

https://schemas.mpai.community/OSD/V1.1/data/Time.json

https://schemas.mpai.community/CAE2/V1.0/data/AMSMessageID.json

 

4   Semantics

Label Size Description
Header N1 Bytes
·         Standard 8 Bytes The characters “CAV-AHM”
·         Version N2 Bytes Major version – 1 or 2 Bytes
·         Dot-separator 1 Byte The character “.”
·         Subversion N3 Bytes Minor version – 1 or 2 Bytes
AMSHCIMessageID N4 Bytes Identifier of AMS-HCI Message.
AMSHCIMessageData N5 Bytes Data in AMS-HCI Message.
·         RouteList N6 Bytes Endpoint of the Route.
·         Messages N7 Bytes Set of possible messages
o  Delay N8 Bytes Delay in travel and amount in seconds.
o  FailureID N9 Bytes CAV FailureID
o  AMSMessageID N10 Bytes One of AMSMessages.
DescrMetadata N11 Bytes Descriptive Metadata

5   Data Formats and Attributes

No Formats required,

6   To Respondents

Respondents are requested to propose Messages and their Semantics.