1. Definition
Audio Data entering an AIW or AIM.
2 Functional Requirements
Input Audio shall have a Qualifier for use in different application domains.
In the Connected Autonomous Vehicle domain, Microphone Array is used to:
- Provide the location of sound sources.
- Enable extraction of speech addressed to CAV by humans
- Incorporate outdoor Audio information into the Basic Environment Representation.
- Remove unwanted noise from the passenger cabin.
3 Syntax
https://schemas.mpai.community/CAE1/V2.2/data/InputAudio.json
4 Semantics
Label | Size | Description |
Header | N1 Bytes | Input Audio Header |
– Standard | 9 Bytes | The characters “CAE-IAU-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. |
InputAudioID | N5 Bytes | ID of Input Audio. |
AudioSensorID | N6 Bytes | ID of Audio Sensor. |
InputAudioData | Ny Bytes | Set of Input Audio Data |
– InputAudioQualifier | N12 Bytes | The Qualifier of Input Audio |
– InputAudioPayload | N13 Bytes | The Payload of Input Audio |
– InputAudioDataLength | N14 Bytes | The Length of Input Audio Data in Bytes |
– InputAudioDataURI | N15 Bytes | URI of Input Audio Data |
DescrMetadata | N16 Bytes | Descriptive Metadata |
5 Data Formats
Audio Qualifiers (Sub-Types, Formats, and Attributes) are required.
6 To Respondents
Respondents are invited to propose Sub-Types, Formats, and Attributes.