1   Definition

Information exchanged between the HCI of the Ego CAV and a peer HCI of a Remote CAV.

2   Functional Requirements

  1. Messages from Remote to Ego HCI have the same payload.
  2. The Ego HCI may:
    • Send messages to a Remote HCI.
    • Request a Remote HCI or a CAV-Aware entity (e.g., Roadside Unit, a Store and Forward entity) to send a particular M-Location.
    • Select the appropriate Level of Detail for transmission of requested M-Location Data.

3   Syntax


4   Semantics

Label Size Description
Header N1 Bytes
– Standard 9 Bytes The characters “MMM-ERH-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
EgoRemoteHCIID N4 Bytes Identifier of EgoRemoteHCIMessage.
EgoRemoteHCIData N5 Bytes Data of Ego-Remote-HCI Message.
– MLocationRequest N6 Bytes ULocation
– FullEvironmentRepresentation N7 Bytes AV Scene Descriptors with semantics.
– GenericMessage N8 Bytes
DescrMetadata N9 Bytes Descriptive Metadata.

5   Data Formats

MPAI has defined U-Location as a spatial volume in the Universe.

The payload of a Generic Message may have other formats.

6   To Respondents

Respondents are invited to:

  1. Comment or elaborate on the functional requirements identified E-HCI to R-HCI message above.
  2. Propose Data Formats of U-Location and Generic Message.