1   Definition

The HCI-AMS Messages request that the Motion Actuation Subsystem (MAS) execute specified actions.

2   Functional Requirements

HCIs send Messages to the AMS based on messages from humans or a Remote-HCI to:

  1. Request possible Routes connecting the current place and the destination that may include:
    • Desired arrival time.
    • Stops in between place and destination.
  2. Request to
    • Execute a Route.
    • Suspend a Route.
    • Resume a Route.
    • Change a Route.
  3. Request to see/hear an M-Location corresponding to a U-Location from a Point of View.

3   Syntax

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

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

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

 

4   Semantics

Label Size Description
Header N1 Bytes
·         Standard 9 Bytes The characters “CAV-HAM-V”
·         Version N2 Bytes Major version – 1 or 2 Bytes
·         Dot-separator 1 Byte The character “.”
·         Subversion N3 Bytes Minor version – 1 or 2 Bytes
HCIAMSMessageID N4 Bytes Identifier of HCI-AMS Message.
HCIAMSMessageData N4 Bytes Data in HCI-AMS Message.
·         DestinationAndArrivalTime N5 Bytes Route Endpoint and arrival time.
·         IntermediateStops N6 Bytes Stops between origin and destination
·         SelectedRoute N7 Bytes ID of Route
·         RouteCommands N8 Bytes “Execute”, “Suspend”, “Resume”, “Change”
DescrMetadata N9 Bytes Descriptive Metadata

5   Data Formats

No Format required.

6   To Respondents

Respondents are invited to:

  1. Comment or elaborate on the Functional Requirements of the HCI-AMS Messages identified above.
  2. Extend the list of Functional Requirements.