MMM-TEC V2.1 Processes

<-Architecture and Operation Go to ToC Items->

1. General
2. Process types	2.1 App	3. Device	4. Service	5. User
3. Actions

1 General

A Process is a Program Object instance running on the Information and Communication Technology (ICT) platform underpinning an M-Instance or on a device connected to it.

A Process may perform one of more MPAI-specified Process Actioms depending on its Capabilities describing the Actions, and the Items it is able to process, and Metadata describing the Process characteristics.

A Process unable to perform a Process Action, may request a destination Process to perform Process Actions by using the MMM-TEC Inter-Process Protocols.

If the destination Process is unable to process an Item because it does not support the Item’s Qualifiers with its Capabilities, it may request a Conversion Service to Convert the Item to a new Item with appropriate Sub-Types, Formats and Attributes. Likewise, the Requesting Process may request Conversion of Items received from the destination Process.

MMM-TEC defines four varieties of Processes: App, Device, Service, and User and uses the different varieties of Process to describe their operation. However, it should be borne in mind that all Process varieties are simply Processes with different Capabilities.

Section 2 specifies the four varieties of Process. Section 3 specifies the Functional Requirements of the Action “verbs” of Process Actions.

2 Process Types

2.1 App

Functions	An instance of an application-specific Program executed on a Device.
Functional Requirements	An App may need to be Certified in order to be allowed to operate in an M-Instance.

2.2 Device

Functions	A Device may: 1. UM-Capture Data from a U-Location. 2. Additionally, UM-Send Data and Metadata to a User. and/or 1. MU-Actuate an Item at a U-Location. 2. The Device may MU-Actuate after a User has MM-Sent an Item at an M-Location to the Device.
Functional Requirements	To connect and interoperate with an M-Instance, a Device may need to expose its Process Capabilities to the M-Instance.

2.3 Service

Purpose	A Process that provides specific Functionalities to other Processes.
Functional Requirements	A Service may be: 1. One of the native MMM-TEC Services (in bold in Table 1). 2. Hosted by the M-Instance but provided by a third party.

Table 1 names and defines the role of Services that are part of the Process Action specification.

Table 1 – A list of Services referenced in the Verification Use Cases

Service	Acronym	Description
Authenticate	ATSrvc	Support User requests for Item Authentication
Author	AUSrvc	Enables Users to acquire or develop Items.
Communicate	COSrvc	Enables communication between Processes.
Convert	CVSrvc	Converts Data of Items to a different format based on provided Qualifier.
Discover	DSSrvc	Supports Users looking for Items of Processes with given characteristics.
Execute	EXSrvc	Executes a Program.
Export-Import	EISrvc	Manages input from and output to the Universe.
Identify	IDSrvc	Identifies Data and Metadata as Items.
Inform	IFSrvc	Supports Users looking for information about Items.
Interpret	ITSrvc	Supports users requesting Interpretation of an Item.
Locate	LCSrvc	Manages positioning and motion of Items.
Post	PTSrvc	Posts Items on which a User holds Rights.
Register	RESrvc	Enables humans to Register with an M-Instance.
RightsMng	RMSrvc	Manages the Rights of Processes and Items.
Transact	TRSrvc	Enables Users to perform Transactions.

Some Verification Use Cases reference other Services of general use. Services needed by an implementation are implemented with Process Actions. Future MMM-TEC Versions may add functionalities to existing Process Actions or add new Process Actions.

For instance, Some Verification Use Cases use the following:

Service	Acronym	Description
Parcel	PCSrvc	Offers Parcels of M-Instance land to Users.
Presence	PRSrvc	Keeps track of Processes starting a session.

2.4 User

Functions

A Process representing a Registered human.

Functional Requirements

1.       A User may perform the following functions:
1.1. Act as the interface of the human with the M-Instance.
1.2.      Render the User as a Persona UM-Animated by a Stream or by an autonomous agent.
2.       Animation results from an MM-/UM-Animate Action and enabled by a Program run by the User.
3.       The Animation Program may be part of the Processes registered by a human or provided by the M-Instance.
4. An M-Instance may not require Registration.

3. Actions

Table 2 specifies the Functional Requirements of the Actions that a Process may use when performing a Process Action.

Authenticate	The Action of a Process producing an Authentication Response Item confirming or not that an Item or Process is what it claims to be.
Author	The Action of a Process producing an Item based on provided Items and their Data and Qualifiers.
Convert	The Action of a Process changing the Data of an Item according to a given Qualifier
Discover	The Action of a Process providing a Discovery Response Item relevant to the Items or Processes that are intended to be discovered.
Execute	The Action of a Process executing a Program and producing Items.
Hide	The Action of a Process making the ID of an Item unavailable to all other Processes.
Identify	The Action of a Process producing and labelling an Item from Data, its Qualifier, and Model Rights.
Inform	The Action of a Process providing an Information Response Item about an Item or Process.
Interpret	The Action of a Process providing an Interpretation Response Item about an Item or Process.
MM-Animate	The Action of a Process animating an MM-Added Item with a Stream or Command Item.
MM-Add	The Action of a Process placing an Item at an M-Location with a Spatial Attitude with a specified perceptible or imperceptible state.
MM-Move	The Action of a Process moving an MM-Added Item from an M-Location to another M-Location along a Trajectory, preserving any change that may have been effected on the Item since it was MM-Added.
MM-Send	The Action of a Process sending a Message to other Processes.
Modify	The Action of a Process producing a new Item starting from an existing Item using new Data and possibly with a new Qualifier.
MU-Actuate	The Action of a Process rendering an MM-Added Item as an R-Item at a U-Location with a Spatial Attitude.
MU-Add	The Action of a Process placing an R-Item at a U-Location with a Spatial Attitude.
MU-Animate	The Action of a Process animating an MU-Added R-Item with – A stream Item equivalent to the one used to animate the Persona of which the R-Item is an Analogue Twin, or – A specific command applied to an Item that is reflected in the R-Item that is its Analogue Twin.
MU-Move	The Action of a Process moving an MU-Added R-Item from a U-Location to another U-Location via a Trajectory giving it an assigned Spatial Attitude when the R-Item is at the new U-Location.
MU-Send	The Action of a Process in an M-Instance sending a Message to Processes in the Universe.
Post	The Action of a Process adding an Asset to its repository and making it perceptible.
Property Change	The Action of a Process modifying the characteristics of an Item: 1. Resize the Item by R_x, R_y, R_z along the Item’s axes. 2. Display a specific Personal Status (if a Persona). 3. Change the attributes of 3.1 A Light Source: SourceType, ColourInfo, Intensity 3.2 An Audio Source: SourceType 3.3 A Basic Visual or 3D Object: Mass, Gravity Property, Texture 4. Make an Item perceptible if not already in that state.
Register	The Action of a human opening an Account based on the human’s Personal Data.
Resolve	The Action of a Process setting up a multi-M-Instance Session that involves two/more than two Processes in two/more than two M-Instances.
Rights Change	The Action of a Process modifying the Rights of a Process or an Item.
Transact	The Action of a Process₁ (“sender”) 1. Assigning Rights for an Asset to Process₂ (“receiver”). 2. Causing: 2.1. Wallet₁ of Process₁ to be increased by Value₁. 2.2. Wallet₂ of Process₂ to be decreased by Value₂. 2.3. Wallet₃ of Process₃ to be increased by Value₃ (optionally).
UM-Capture	The Action of a Process capturing a scene at a U-Location as Data with a Qualifier.
UM-Send	The Action of a Process in the Universe sending a Message to Processes in an M-Instance.
Validate	The Action of a Process producing a Validation Response Item that confirms or not that an Item or Process has the Rights it claims to have.