1 Definition
A Data Type representing analogue signals generated by information captured by an ultrasonic sensor.
2 Functional Requirements
An active time-of-flight sensor typically operating in the 40 kHz to 250 kHz range.
The main features of Ultrasound are:
- Ability to monitor the immediate surroundings of the vehicle (≤ 10 m).
- Operation frequency above 30 kHz.
- Low-resolution images.
3 Syntax
https://schemas.mpai.community/CAV2/V1.0/data/InputUltrasound.json
4 Semantics
Label | Size | Description |
Header | N1 Bytes | Input Ultrasound Header |
– Standard | 9 Bytes | The characters “CAV-IUS-V” |
– Version | N2 Bytes | Major version – 1 or 2 characters |
– Dot-separator | 1 Byte | The character “.” |
– Subversion | N3 Byte | Minor version – 1 or 2 characters |
MInstanceID | N4 Bytes | ID of the Virtual Space. |
InputUltrasoundID | N5 Bytes | ID of Input Ultrasound. |
UltrasoundSensorID | N6 Bytes | ID of Ultrasound Sensor. |
InputUltrasoundData | Ny Bytes | Set of Input Ultrasound Data |
– InputUltrasoundQualifier | N12 Bytes | The Qualifier of Input Ultrasound |
– InputUltrasoundPayload | N13 Bytes | The Payload of Input Ultrasound |
– InputUltrasoundDataLength | N14 Bytes | The Length of Input Ultrasound Data in Bytes |
– InputUltrasoundDataURI | N15 Bytes | URI of Input Ultrasound Data |
DescrMetadata | N16 Bytes | Descriptive Metadata |
Label | Size | Description |
Header | N1 Bytes | Input Uktrasound Header |
– Standard | 9 Bytes | The characters “CAV-IUS-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. |
InputUltrasoundID | N4 Bytes | Identifier of Input Ultrasound Data. |
UltrasoundSensorID | N5 Bytes | Identifier of Ultrasound Sensor. |
InputUltrasoundSpaceTime | N6 Bytes | Total duration of Input Ultrasound Data. |
InputUltrasoundData | N7 Bytes | Set of Input Ultrasound Data |
– InputUltrasoundFormatID | N8 Bytes | Format ID of Input Ultrasound Data. |
– InputUltrasoundDataLength | N9 Bytes | Data Length of Input Ultrasound Data in Bytes. |
– InputUltrasoundDataURI | N10 Bytes | Location of Input Ultrasound Data. |
InputUltrasoundAttributes[] | N11 Bytes | Set of Input Ultrasound Data Attributes |
– InputUltrasoundAttributeID | N12 Bytes | ID of Attribute of Input Ultrasound Data |
– UltrasoundAttributeFormatID | N13 Bytes | ID of Attribute Format of Input Audio Data |
– InputUltrasoundAttributeLength | N14 Bytes | Number of Bytes in Input Ultrasound Data |
– InputUltrasoundAttributeDataURI | N15 Bytes | URI of Data of Input Ultrasound Data |
5 Data Formats
Ultrasound Data Formats are required.
6 To Respondents
- Comment or elaborate on the functional requirements of Ultrasound Sub-Types, Formats, and Attributes with the goal of achieving tracking and representation of objects for the Ultrasound Scene Description.
- Propose Sub-Types, Formats, and Attributes for use in the future Technical Specification: Data Types, Formats, and Attributes (MPAI-TFA).