MPAI-MMM Functionalities

This Chapter collects the Functionalities of an M-Instance supported by this Technical Specification. Terms beginning with a small letter have the common meaning, Terms beginning with a capital letter are defined.

1 M-Instance	5.1 General Rights	6 Personae
2 Processes	5.2 Perception Rights	7 Locations
3 Rules	5.3 Interaction Rights	8 Objects and Scenes
4 Registration	5.4 Service access Rights	9 Identifiers
5 Rights	5.5 Acquisition of Rights

1       M-Instance

An M-Instance

1. Is characterised as a set of Processes providing some or all the following functions:
2. Sensing data from U-Locations using Devices.
3. Processing the sensed data and producing Items.
4. Producing one or more M-Environments populated by Items either imported or internally generated.
5. Processing Objects from the M-Instance or potentially from other M-Instances to affect U- and/or M-Environments in ways that are:
   • Consistent with the goals set for the M-Instance.
   • Effected within the capabilities of the M-Instance.
   • In compliance with the Rules set for the M-Instance and the applicable laws.
6. May operate in a centralised or decentralised way.
7. May be subdivided in administratively separated M-Environments.
8. Monitors:
   • The Rights held by Processes on Processes to Act on Items at M-Locations.
   • The Entities placed at M-Locations with a Spatial Attitude.
9. Should be secure, e.g., to prevent malicious Users from:
   • Accessing the Account of a human who is not the human represented by the User.
   • Taking control of a Process.
   • Acting on Items for which it does not have Rights.
10. Should withstand denial of service attacks.

2       Processes

1. Process types
   • Devices: they connect U-Locations with M-Locations and vice-versa.
   • Users: they represent humans and are humans’ agents in the M-Instance or on Devices.
   • Apps: they run on Devices. A User may be an App running on a Device.
   • Services: they are generic Processes providing Functionalities.
2. Certification
   • Processes may be connected or imported to an M-Instance if they have passed Certification.
   • Contracts may be imported to an M-Instance if they have passed a Certification Process.

3       Rules

An M-Instance may be governed by Rules that may include:

1. The Personal Data retention, processing, and access policy.
2. The Rights and Obligations, e.g., ethical behaviour of Users.
3. The permission-based or permission-less access policy to M-Environments.
4. The trusted or trust-less relationship between Users and M-Instance.
5. The subset of required for each Account type.
6. The sanctions applied to a User whose Actions do not comply with the Rules.

4       Registration

1. A human, possibly on behalf of a legal entity, may Register with an M-Instance.
2. The M-Instance may
   • Request:
     • A subset of the human’s Personal Profile.
     • WalletIDs
     • Users
     • Personae
   • Create an Account with AccountID including:
     • The subset of the human’s Personal Profile.
     • WalletIDs
     • Users
     • Personae
     • Rights and Obligations

3. Personal Profile may have a scalable representation to enable an easy creation of a subset.

5       Rights

5.1      General Rights

Rights may include:

1. The maximum number of:
   • Users a human can deploy.
   • Personae a User can be rendered as.
   • Concurrent Users and Objects an M-Location can support.
2. The ability to:
   • Create persistent (as opposed to ephemeral) Scenes at M-Locations.
   • Store, search, and retrieve Experiences.
   • Develop economic activities.
   • Book M-Locations for a duration.
   • Support persistent storage.
   • Connect with or import Processes to an M-Instance.
   • Make Transactions to acquire Rights.

5.2      Perception Rights

A User may, depending on the Rights it holds:

1. Perceive scenes at U-Locations as captured by Devices endowed with audio, visual, haptic, and BCI capabilities, and the spatial attitudes of their objects.
2. Receive Messages from a U-Location as a result of an event there.
3. Import audio, speech, visual, and haptic models.
4. Perceive Entities.
5. Render perceived Entities at a U-Location with spatial attitudes.
6. Import Data and Metadata from and export Items to an Address.

5.3      Interaction Rights

A User may, depending on the Rights it holds:

1. Interrogate a Process about its Functionalities.
2. Interact with Entities.
3. Send public or private Speech, Visual, and Haptic Messages to Users.
4. Send selected Entities to a User.
5. Place Entities with Spatial Attitudes.
6. Animates Models.

5.4      Service access Rights

A User may, depending on the Rights it holds, perform or request a Process to perform:

1. Author an Item.
2. Authenticate an Item.
3. Change the Rights of a Process.
4. Discover Objects, Processes, Events, or Experiences.
5. Find the Transactions involving an Asset under specified conditions.
6. Obtain an interpretation of an Item, e.g.:

Request	From	To
Extract	Text	Personal Status
Extract	Speech	Text
Translate	Text or Speech	Text or Speech
Extract	Face and/or Gesture	Personal Status

7. Obtain Conversion of an Item from a Format to another Format.
8. Obtain information about a Process or an Item.
9. Obtain a recommendation of Processes or Items.
10. Record all the Actions made by a User (Activity Data) at an M-Location during a time.
11. Create a representation of a User’s network of connections with Items, M-Locations, and Processes (Social Graph).
12. Posts an Item that can be Transacted (Asset) to a marketplace.
13. Retrieve Objects, Events, or Experiences.
14. Store Objects, Events, or Experiences.
15. Formulate:
    • The information it intends to obtain from a Service.
    • The Rights it intends to acquire on the response of the Service.
    • How the response should be rendered.

5.5      Acquisition of Rights

A User may acquire, or have as part of its Account the Rights to:

1. Perform or request another User to perform Actions on Items.
2. Develop an economic activity in an M-Environment.
3. Make an Asset out of an Item.
4. Make a Transaction on an Asset specifying which Rights to the Asset it grants to the buyer.
5. Make an agreement with another user, e.g., via a Contract.
6. Copy or Modify, i.e., change Data (e.g., by editing it) and/or Metadata of an Item.
7. Change the settings and attributes of Entities of an M-Locations (e.g., SFX during a concert).
8. Set the Point of View from which it perceives a Scene.
9. Make inaccessible to any User an Item for which it has Rights.
10. Make or request a Process to make Actions in its own or another M-Instance.
11. Be rendered as one of the Personae uploaded at registration time.

6       Personae

A Persona may:

1. Faithfully reproduce the visual appearance of the human.
2. Have their visual appearance altered, compared to that of the human.
3. Have an unrelated visual appearance.
4. Display a presumptive Personal Status in speech, face, and gesture.
5. Be driven by
   • The movements of the human.
   • A Process.

7       Locations

1. An M-Location may be:
   • Private, i.e., only a User or a group of Users have Rights to it.
   • Public, i.e., a Metaverse Operator or a User grant anybody the Rights to enter, move in, and perceive the M-Location.
   • Persistent
   • Ephemeral
2. A U-Location
   • May require that a User hold Rights to Capture a scene, Render a Scene, or store Data at an Address.

8       Objects and Scenes

1. An Object may:
   • Be Virtual, i.e., Authored in an M-Instance.
   • Be Digitised, i.e., Digital Twins of objects.
   • Be Autonomous, i.e., Animated by a Process.
   • Have Audio, Visual, or Haptic attributes, or combinations of these attributes.
2. A Scene may be composed of:
   • Only Virtual Objects.
   • Only Digitised Objects.
   • Partly Virtual and partly Digitised Object.

9       Identifiers

1. All Items have an Identifier.
2. An Identifier:
   • Uniquely references an Item or a Process.
   • May be issued by a central, distributed, or no authority.
   • May have a Format accepted by more than one M-Instance.
   • May enable to trace the Identifier of an Item back to the Item that spawned the Asset.
   • May enable to trace the Identifier of a Modified Item back to the Item that spawned the Modified Item.