1 Definition
Message exchanged between the Ego CAV’s and the Human-CAV Interaction Subsystems (HCI) of another CAV or CAV-Aware entity (e.g., Roadside Unit, a Store and Forward entity) “Remote HCI”.
2 Functional Requirements
Ego HCI may:
- Exchange messages with a Remote HCI.
- At a passenger’s prompt, request a Remote HCI to send the digital representation (M-Location) of the audio-visual scene of a specific U-Location.
- Respond or not to the request from a Remote HCI to send the digital representation (M-Location) of the audio-visual scene of a specific U-Location by selecting the Level of Detail for transmitting the requested M-Location with the available bandwidth.
- Respond to a request to move the CAV to a specified Wai Point and stop assuming a specified Point of View.
3 Syntax
https://schemas.mpai.community/CAV2/V1.0/data/EgoRemoteHCIMessage.json
4 Semantics
Label | Size | Description |
Header | N1 Bytes | Ego-Remote HCI Message Header |
– Standard – EgoRemoteHCIMessage | 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 |
EgoRemoteHCIMessageID | N4 Bytes | Identifier of Ego-Remote HCI Message. |
EgoRemoteHCIMessageData | N5 Bytes | Data of Ego-Remote-HCI Message. |
– Request | N6 Bytes | Data sent on Ego CAV’s initiative. |
– MLocationRequest | N7 Bytes | M-Location corresponding to a U-Location. |
– GenericMessage | N8 Bytes | Any message. |
– Response | N9 Bytes | Data sent in response to a request or message. |
– FullEvironmentDescriptors | N10 Bytes | Full Environment Descriptors. |
– ResponseToMessage | N11 Bytes | Response to Message. |
DescrMetadata | N12 Bytes | Descriptive Metadata. |