Go To CAE-AOR Data Types

1 Definition 2 Functional Requirements 3 Syntax 4 Semantics

1 Definition

Health Data is End User’s Data received by a Health Front End from a Health Device.

2 Functional Requirements

User Command shall support the following Functional Requirements:

Navigating the AudioScene e.g., changing the position/orientation of the end user by giving new Point of View
Remixing the audio content Level (LUFS measured as specified by ITU-R BS.1770) parameter specifying augmentation or reduction of the different waveform components (audio object data) of the Audio Object;

Removing or adding Objects

Re-positioning Audio Objects List of audio objects in the scene and their new points of view
Substituting Audio Objects e.g., changing the language: List of Audio Objects and their associated new Qualifiers.
Adding motion to the Audio Object List of Audio Objects and their associated Acoustic Profile and Spatial Attitude.
Modifying the acoustic environment List of Audio Objects and their associated Acoustic Profile.

3 Syntax

https://schemas.mpai.community/CAE3/V1.0/data/UserCommand.json

4 Semantics

Label Description
Header User Command Header, Standard “CAE-UCM-Vx.y”
MInstanceID Identifier of M-Instance.
UEnvironmentID
UserCommandID Identifier of Health Data.
UserCommandTime Time of Health Data.
UserCommandData Set of Health Data.
– AudioSceneNavigation
– AudioRemixing 
– AudioObjectRepositioning
– AudioObjectSubstitution
– AudioObjectMotion
– AcousticEnvironmentModification
DataXMData Information about this User Command.
DescrMetadata Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with Health Data (CAE-UCM) if:

  1.  Its JSON Object validates against its JSON Schema.
  2. Any included  JSON Object validates against its JSON Schema.
  3. All Data in the JSON Object:
    1. Have the specified Data Types.
    2. Conform with the Qualifiers signaled in their JSON Schemas.

6     Performance Assessment

Go To AIH-HSP Data Types