<– Metaverse Functionalities      Go to ToC       Functional Requirements of Processes–>

An M-Instance is an Information and Communication Technology platform with the following general functions:

  1. To sense data from U-Locations.
  2. To process the sensed data and produce Data.
  3. To produce one or more M-Environments populated by Objects that can be either digitised or virtual, the latter with or without autonomy.
  4. To process Objects from the M-Instance or potentially from other M-Instances.
  5. To affect U- and/or M-Environments using Objects in ways that are:
    • Consistent with the goals set for the M-Instance.
    • Within the Capabilities of the M-Instance.
    • According to the Rules of the M-Instance.
    • Respecting applicable laws and regulations.

and operating as and providing the Functionalities of this Technical Specification.

An M-Instance:

  1. May make its Capabilities known.
  2. May be administratively subdivided in M-Environments.
  3. May allow a human to Register with the M-Instance or an M-Environment.
  4. May request a Registering human to provide a subset of their Personal Profile.
  5. Is implemented as a set of Processes:
    • Providing Functionalities defined by this Technical Specification.
    • Composed of:
      • A Program having a Format supported by the M-Instance.
      • Metadata describing the Program and containing the following as a minimum:


Table 2 – Minimum Metadata of a Process

Metadata elements Details
ProcessID The ID of the Process.
UserID The ID of the User having Rights to Act on the Process.
InRightsID The ID of the User’s Rights to Act granted to the Process.
OutRightsID The ID of the Rights a User may acquire on the Process.
DescrMdata Any description of the Process.
  • Performing Actions on Items if they hold the Rights to do that.
  • Requesting other Processes to perform Actions by transmitting a standard Request-Action Item and responding to a Request-Action with a Response-Action:


Table 3 – Elements of Request-Action and Response-Action

Request-Action Response-Action Details
Request-Action ID Response-Action ID Unique ID
Emission Time Emission Time Tine of Issuance
Source Process ID Source Process ID Requesting Process ID
Destination Process ID Destination Process ID Requested Process ID
InItems OutItems In/Output Items required by the Action
InLocations Locations of InItems
OutLocations Locations of OutItems
OutRights Expected Rights on OutItems
  • Performing the Request if:
    • The requesting Process holds the Rights that are required to perform the request.
    • The requested Process holds Rights to perform the requested Action on the Item.
  1. May support four types of Processes:
    • The User Process represents and is under the control of a human who has Registered with the M-Instance. A User may run on the M-Instance or on a Device connected to the M-Instance.
    • Device is one or more Processes running on a physical device connecting M-Locations to U-Locations, specifically the Registered human, by:
      • Capturing scenes as Media and providing Media as Data/Metadata – U-Location to M-Location). Data/Metadata shall be Identified as an Item to enable Processes to perform Actions.
      • Receiving an Entity and rending it as Media with a Spatial Attitude (Position and Orientation) – M-Location to a U-Location.
    • Service provides specific functionalities.
    • App runs on a Device. A Device may run the User Process as an App.

Figure 1 – The human-device-user-persona chain

  1. Provides Functionalities through Processes performing Actions on Items containing:
    • Data whose Format is supported by the M-Instance.
    • Metadata describing the Item and containing the following as a minimum:


Table 4 – Minimum Metadata for Item

Metadata elements Details
ItemID The ID of the Item.
UserID The ID of the User having Rights to Act on the Item.
InRightsID The ID of the User’s Rights to Act granted to the Item.
OutRightsID The ID of the Rights a User may acquire on the Item.
DescrMdata Any description of the Item.
  1. Enables a Process:
    • To communicate to a Process in another M-Instance through an M-Instance’s Resolution Service.
    • To obtain conversion of the Format of an Item’s Data by calling a Conversion Service.
    • To specify their communication needs by:
      • Requesting the needed maximum and average bitrate value.
      • Reserving the needed bitrate for a time and a location.
      • Requesting that the same simultaneous Experience be provided to a specified number of Devices.
  1. Identifies Processes/Items with one Identifier and, optionally, with more than one Identifier. Each Identifier uniquely refers to one Process/Item.
  2. Creates Items by processing the sensed data and the autonomously produced data.
  3. Employs Data Types to represent entities such as Amount (of a Currency), length, area, and volume etc.
  4. Gives a Registered human the Rights to deploy one or more:
    • Users and Devices each with M-Instance-specific Rights.
    • Personae, i.e., human-like, or humanoid Models used by deployed Users to render themselves.
  5. Establishes Rules that the Users in the M-Instance shall comply with.

Figure 2 – Resolution and Conversion Services

  1. May penalise Users for lack of compliance with the Rules.
  2. May allow a Process to perform, or request another Process to perform, Actions on Items even in the absence of Rights.
  3. May require that Processes be certified for use in the M-Instance.


Future versions of this document may specify:

  1. Profiles of Actions and Items.
  2. Additional Actions and Items.


<– Metaverse Functionalities        Go to ToC       Functional Requirements of Processes–>