<-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
Process is an instance of a Program running on the Information and Communication Technology (ICT) platform underpinning an M-Instance or on a device connected to it. A Process may perform an MPAI-specified Process Action or request other Processes to perform Process Actions using the MMM-TEC Protocols. If the Items received have incompatible Qualifiers, a Process may request a Conversion Service to convert the Item so that its has a Qualifier compatible with the Process.
Four types of Processes are specified in the following: App, Device, Service, and User. This characterisation has the scope of facilitating the reading of this Technical Specification as all types of Processes are simply Processes. A Process may be defined as performing all the Functions listed in the following.
Processes Perform Actions. The Functional Requirements of some Actions are specified, while others are Process-specific.
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 a given 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. |
Services may be M-Instance-specific. Table 1 names and defines the role of Services that are specified by MPAI (in bold) and some Services of general use referenced by the Verification Use Cases. MMM-TEC, however, does not mandate that services be implemented as described in Table 1, as the Capabilities of a Process are indicated in its P-Capabilities.
Table 1 – A list of Services referenced in the Verification Use Cases
| Service | Description |
| Activity | Keeps track of Processes starting a session. |
| Authenticate | Support User requests for Item Authentication |
| Author | Enables Users to acquire or develop Items. |
| Communicate | Enables communication between Processes. |
| Convert | Converts Data of Items to a different format based on provided Qualifier. |
| Discover | Supports Users looking for Items of Processes with given characteristics. |
| Execute | Executes a Program. |
| Export-Import | Manages input from and output to the Universe. |
| Identify | Identifies Data and Metadata as Items. |
| Inform | Supports Users looking for information about Items. |
| Interpret | Supports users requesting Interpretation of an Item. |
| Locate | Manages positioning and motion of Items. |
| Parcel | Offers Parcels of M-Instance land to Users. |
| Post | Posts Items on which a User holds Rights. |
| Register | Enables humans to Register with an M-Instance. |
| Rights | Manages the Rights of Processes. |
| Transact | Enables Users to perform Transactions. |
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 lists the Actions and specifies their Functional Requirements.
| – 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, Data, 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 intended discovery. |
| – 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 Processes, but to itself. |
| – Identify | The Action of a Process producing an Item from Data, Qualifier, and Model Rights. |
| – Inform | The Action of a Process providing an Information Response about an Item or Process Item. |
| – 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-Embedded 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 in a non-perceptible state. |
| – MM-Move | The Action of a Process moving an MM-Added Item from an M-Location to another M-Location 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 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 – 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 to 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. 2. Grant Rights based on Model Rights if a Transaction based on Model Transaction is performed. |
| – Property Change | The Action of a Process modifying the characteristics of an Item: 1. Resize the Item by Rx, Ry, Rz 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 Process1 (“sender”) 1. Assigning Rights on an Asset to Process2 (“receiver”). 2. Causing: 2.1. Wallet1 of Process1 to be increased by Value1. 2.2. Wallet2 of Process2 to be decreased by Value2. 2.3. Wallet3 of Process3 to be increased by Value3 (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 a Process 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/ |
<-Architecture and Operation Go to ToC Items->
