This is the public page of Mixed-reality Collaborative Spaces (MPAI-MCS), an MPAI standard project supporting scenarios where geographically separated humans represented by avatars collaborate in virtual-reality spaces called Ambients. MCSs require that
- A service provider create an Ambient. The Ambient can be a naked space such as the walls of a room, but also a space populated by audio-visual objects.
- Multiple independent human participants populate the Ambient with Avatars which may be animated graphic characters or Avatars that are virtual twins of humans represented with as realistic as possible features: especially, face, head, arms, hands and speech. The body is obviously also an element of the virtual twin.
MPAI-MCS seeks to define standard formats for the Ambient and for the Avatar for a service provider to be able to create an MCS populated with avatars with the given features or for a participant client to create its own MCS using data generated by other environments. The standard format can be considered as an interchange format to which any other non-standard formats can be converted.
The standard is intended for an MPAI-specified execution environment called AI Framework (MPAI-AIF) running workflows called AI Workflows composed of processing elements called AI Modules (AIM). More information about the standard can be found here. The standard can be downloaded.
The Server-based Ambient Use Case is depicted and illustrated in the figures below. It requires
- the transmitting client (Figure 1)
- the server (Figure 2)
- the receiving part of the client (Figure 3).
Clients are used by participants, e.g., to attend a virtual conference, where all participants are represented by an avatar, e.g., sitting at a table. The Avatars faithfully represent the participants with their faces, heads and gestures and made more realistic by the emotion extracted from speech, face and gesture. Each participant can populate the Ambient with the avatars controlled by the participants and can select the viewpoint.
This is not the only possible functionality allocation between client and server. In another configuration, most of the functionalities are supported by the transmitting client and the client architecture is simplified. However, the receiving client need not change.
MPAI has developed MPAI-MCS Use Cases and Functional Requirements WD0.5. The goal is to issue a Call for Technologies after the internal process is completed. Anybody is allowed to respond. If a proposed technology is accepted, the proponent will be asked to join MPAI.
MPAI-MCSis at the level of Use Cases and Functional Requirements. If you wish to participate in this work you have the following options
- Join MPAI
- Participate until the MPAI-MCS Functional Requirements are approved (after that only MPAI members can participate) by sending an email to the MPAI Secretariat.
- Keep an eye on this page.
Return to the MPAI-MCS page