<- Profiles     Go to ToC

(Informative)

1    AIF Implementations.

1.1     Resource-constrained implementation

1.2     Non-resource-constrained implementation

2    Examples of types

3    Examples of Metadata

3.1     Metadata of Enhanced Audioconference Experience AIF

3.2     Metadata of Enhanced Audioconference Experience AIW

3.3     Metadata of CAE-EAE Analysis Transform AIM

3.4     Metadata of CAE-EAE Sound Field Description AIM

3.5     Metadata of CAE-EAE Speech Detection and Separation AIM

3.6     Metadata of CAE-EAE Noise Cancellation AIM

3.7     Metadata of CAE-EAE Synthesis Transform AIM

3.8     Metadata of CAE-EAE Packager AIM

1       AIF Implementations

This Chapter contains informative examples of high-level descriptions of possible AIF operations. This Chapter will continue to be developed in subsequent Version of this Technical Specification by adding more examples.

1.1      Resource-constrained implementation

  1. Controller is a single process that implements the AIW and operates based on interrupts call-backs.
  2. AIF is instantiated via a secure communication interface.
  3. AIMs can be local or has been instantiated through a secure communication interface.
  4. Controller initialises the AIF.
  5. AIF asks the AIMs to be instantiated.
  6. Controller manages the Events and Messages.
  7. User Agent can act on the AIWs at the request of the user.

1.2      Non-resource-constrained implementation

  1. Controller and AIW are two independent processes.
  2. Controller manages the Events and Messages.
  3. AIW contacts Controller on Communication and authenticates itself.
  4. Controller requests AIW configuration metadata.
  5. AIW sends Controller the configuration metadata.
  6. The implementation of the AIW can be local or can be downloaded from the MPAI Store.
  7. Controller authenticates itself with the MPAI Store and requests implementations for the needed AIMs listed in the metadata from the MPAI Store.
  8. The Store sends the requested AIM implementations and the configuration metadata.
  9. Controller:
    1. Instantiates the AIMs specified in the AIW metadata.
    2. Manages their communication and resources by sending Messages to AIMs.
  10. User Agent can gain control of AIWs running on the Controller via a specific Controller API, e.g., User Agent can test conformance of a AIW with an MPAI standard through a dedicated API call.

2       Examples of types

byte[] bitstream_t

An array of bytes, with variable length.

{int32 frameNumber; int16 x; int16 y; byte[] frame} frame_t

A struct_type with 4 members named frameNumber, x, y, and frame — they are an int32, an int16, an int16, and an array of bytes with variable length, respectively.

{int32 i32 | int64 i64} variant_t

A variant_type that can be either an int32 or an int64.

3       Examples of Metadata

This section contains the AIF, AIW and AIM Metadata of the Enhanced Audioconference Experience Use Case.

3.1      Metadata of Enhanced Audioconference Experience AIF

 

3.2      Metadata of Enhanced Audioconference Experience AIW

 

3.3      Metadata of CAE-EAE Analysis Transform AIM

 

3.4      Metadata of CAE-EAE Sound Field Description AIM

 

3.5      Metadata of CAE-EAE Speech Detection and Separation AIM

 

3.6      Metadata of CAE-EAE Noise Cancellation AIM

 

1.1.1      Metadata of CAE-EAE Synthesis Transform AIM

 

1.1.1      Metadata of CAE-EAE Packager AIM

 

 <- Profiles     Go to ToC