1 Definition
Information exchanged between the HCI of the Ego CAV and a peer HCI of a Remote CAV.
2 Functional Requirements
- Messages from Remote to Ego HCI have the same payload.
- The Ego HCI may
- Exchange messages to a Remote HCI
- Request a Remote HCI or a CAV-Aware entity (e.g., Roadside Unit, a Store and Forward entity), because a passenger has requested it to send a particular M-Location.
- Respond or not to the request from emote HCI or a CAV-Aware entity.
- Respond to a request and select the Level of Detail for transmitting the requested M-Location Data appropriate for the available bandwidth.
3 Syntax
https://schemas.mpai.community/CAV2/V1.0/data/EgoRemoteHCI.json
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:
- Comment or elaborate on the functional requirements identified E-HCI to R-HCI message above.
- Propose Data Formats of U-Location and Generic Message.