MMM-FPR V1.0 Use Cases

<- Data Types    Go to ToC    Functionality Profiles –>

Table of Contents of Chapter 8 – Use Cases

8.1    Introduction 8.2    Virtual Lecture 8.3    Virtual Meeting 8.4    Hybrid working

8.5    eSports Tournament 8.6    Virtual performance 8.7    AR Tourist Guide 8.8    Virtual Dance

8.9    Virtual Car Showroom 8.10  Drive a Connected Autonomous Vehicle

8.1        Introduction

This Chapter collects Metaverse Use Cases to facilitate the development of Functionality Profiles.

Use Cases are populated by Users that request to perform Actions on different types of Items. In a Use Case, Users are identified by one subscript and Items by the same subscript of the User performing an Action on the Item followed by a sequential number. For instance:

1. User_i MM-Embeds Persona_j at M-Location_i.k, etc.
2. User_i MU-Renders Entity_j at U-Location_i.k, etc.
3. User_i MM-Sends Object_j to User_k.

 

Note1	The following abbreviations will be used: A = Audio, AV = Audio-Visual, AVH = Audio-Visual-Haptic, SA=Spatial Attitude.
Note2	The Basic Actions of a Composite Action are not listed unless they are independently used by the Use Case.

8.2        Virtual Lecture

8.2.1        Description

A student attends a lecture held by a teacher in a classroom created by a school manager:

1. A School Manager
   • Authors and embeds a virtual classroom.
   • Pays the teacher.
2. A Teacher
   • Embeds its persona from home at the classroom’s desk.
   • Embeds and animates a 3D model.
   • Leaves the classroom.
3. A Student
   • When “at home” pays to attend and make a copy of their lecture Experience.
   • Then Embeds a persona in the classroom.
   • Goes close to the teacher’s desk to feel the 3D model with haptic gloves.
   • Stores their lecture Experience.
   • Leaves the classroom.

 

The detailed workflow is:

1. User₁ (Manager):
   • Authors Entity₁.
   • MM-Embeds Entity₁ at M-Location_1.1.
2. User₃ (Teacher):
   • Tracks Persona₁ (AV) at M-Location_3.1 with SA (establishes a connection between the human and the Persona).
   • MM-Embeds Persona₁ at M-Location_3.2 (desk in classroom).
   • MM-Disables Persona₁ at Location_3.1.
   • MM-Embeds Model₁ at M-Location_3.3 (close to M-Location_3.2).
   • MM-Animates Model₁.
3. User₂ (Student):
   • Tracks Persona₁ (AV) at M-Location_2.1 with SA.
   • Transacts Value₁.
   • MM-Embeds Persona₁ (AV) at M-Location_2.2 with SA.
   • MM-Disables Persona₁ at Location_2.1.
4. User₃ (Teacher):
   • MM-Embeds Model₁ (AVH) at M-Location_3.3 (close to M-Location_3.2).
   • MM-Animates Model₁.
5. User₂ (Student)
   • MM-Adds Persona₁ (AV) at M-Location_2.3 (close to the desk).
   • MU-Captures Model₁ (AVH).
   • MU-Exports Experience₁ at Address_2.1.
6. User₁ (Manager):
   • Transacts Value₁ to User₃ (Teacher).
7. User₃ (Teacher):
   • MM-Disables Persona₁ from M-Location_3.2
   • MM-Embeds Persona₁ at M-Location_3.1.
8. User₂ (Student)
   • MM-Disables Persona₁ from M-Location_2.2
   • MM-Embeds Persona₁ at M-Location_2.1.

8.2.2        Workflow and Actions

 

Table 10 – Virtual Lecture workflow and Actions.

User1 (Manager)	Authors	Entity1.1	(VClassroom).
	MM-Embeds	Entity1.1	M-Location1.1.
User3 (Teacher)	Tracks	Persona3.1 (AV)	M-Location3.1 w/ SA.
	MM-Embeds	Persona3.1	M-Location3.2 (desk).
	MM-Disables	Persona3.1	M-Location3.1
	MM-Embeds	Model3.1	M-Location3.3 (close to desk).
	MM-Animates	Model3.1.
User2 (Student)	Tracks	Persona2.1 (AV)	M-Location2.1 w/ SA.
	Transacts	Value2.1	(Lecture & Experience)
	MM-Embeds	Persona2.1 (AV)	Location2.2 with SA.
	MM-Disables	Persona2.1	M-Location2.1.
User3 (Teacher)	MM-Embeds	Model3.1 (AVH)	M-Location3.3 (close to desk).
	MM-Animates	Model3.1.
User2 (Student)	MM-Adds	Persona2.1 (AV)	M-Location2.3 (close to desk).
	MU-Captures	Model3.1 (AVH)
	MU-Exports	Experience2.1	Address2.1
User1 (Manager)	Transacts	Value1.1	User3 (Lecture fees).
User3 (Teacher)	MM-Disables	Persona3.1	M-Location3.2
	MM-Embeds	Persona3.1	M-Location3.1
User2 (Student)	MM-Disables	Persona2.1	M-Location2.2
	MM-Embeds	Persona2.1	M-Location2.1

8.2.3        Actions, Items, and Data Types

 

Table 11 – Virtual Lecture Actions, Items, and Data Types.

Actions	Items	Data Types
Authenticate	Service	Amount
Author	Entity	Coordinates
MM-Embed	M-Location	Currency
MM-Disable	U-Location	Spatial Attitude
MM-Animate	Value	Value
Register	User	Orientation
Track	Persona	Position
Transact	Experience
MU-Export

8.3        Virtual Meeting

8.3.1        Description

A participant attends a meeting in a room created by a meeting manager. The manager deploys a virtual secretary to produce a summary of the conversations, enriched by information about participants’ personal statuses. The participant gets a translation of sentences uttered in languages other than their own and makes a presentation using a 3D model.

 

This is the workflow of the use case:

1. User₁ (Meeting Manager)
   • MM-Embeds a virtual meeting room at an M-Location₁.
   • MM-Embeds Persona₁ (a Virtual Secretary, a Process MM-Animating a Persona of User₁ at M-Location_1.2).
   • MM-Animates the Virtual Secretary.
2. User₂ (a meeting participant):
   • Tracks Persona₁ at Location_2.1 (“its home”).
   • MM-Embeds Persona₁ (AV) at M-Location_2.2 (“the meeting room”. A Persona can be MM-Enabled as Audio only, Audio-Visual, or Audio-Visual-Haptic).
   • MM-Disables Persona₁ (A-V) from Location_2.1 (disappears from “home”).
   • Interprets (requests translation of speech) of Persona₁ of User₃ (2^nd meeting participant).
   • MM-Embeds Entity₁ (a 3D model) at M-Location_2.3 (“place in the meeting room”).
   • MM-Animates Entity₁ (to make the presentation controlling the 3D model).
3. Virtual Secretary:
   • Interprets Persona₁’s Personal Status (requests estimation of the internal state of Persona_3.1, possibly in addition to Persona_3.1’s Speech Objects translation).
   • Produces a text Summary of Persona₁’s Speech Object (with added graphical signs expressing Persona_3.1’s Personal Status).
   • MM-Embeds the Summary at an M-Location₃ (“meeting room” for participants to comment).

8.3.2        Workflow and Actions

 

Table 12 – Virtual Meeting workflow and actions.

Who	Does	What	Where/comment
User1 (Manager)	MM-Embeds	Entity1.1	(VMeeting room) M-Location1.1
	MM-Embeds	Persona1.1	(Virtual Secretary) M-Location1.2
	MM-Animates	Persona1.1	Operates Virtual Secretary.
User2 (Participant)	Tracks	Persona2.1 (AV)	M-Location2.1 w/ SA
	MM-Embeds	Persona2.1 (AV)	M-Location2.2 w/ SA
	MM-Disables	Persona2.1 (AV)	M-Location2.1
User3 (Participant)	Tracks	Persona3.1 (AV)	M-Location3.1 w/ SA
	MM-Embeds	Persona3.1 (AV)	M-Location3.2 w/ SA
	MM-Disables	User3	M-Location3.1
User2 (Participant)	Interprets	Persona3.1	(Requests translation)
	MM-Embeds	Model2.1	(3D presentation) M-Location2.2
	MM-Animates	Model2.1
Virtual Secretary	Interprets	Persona2.1	(Personal Status)
	Produces	Entity1.2	(Summary)
	MM-Embeds	Entity1.2	M-Location1.3 (VMeeting room)
	MM-Disables	Persona1.1	M-Location1.2
User2 (Participant)	MU-Exports	Event2.1	Address2.1
	MM-Embeds	Persona2.1 (AV)	M-Location2.1 (back home)
	MM-Disables	Persona2.1 (AV)	Location2.2
User3 (Participant)	MM-Embeds	Persona3.1 (AV)	M-Location2.1 (back home)
	MM-Disables	Persona3.1 (AV)	Location3.2 (back home)

8.3.3        Actions, Items, and Data Types

 

Table 13 – Virtual Meeting Actions, Items, and Data Types.

Actions	Items	Data Types
Authenticate	Entity	Coordinates
Call	Persona	Orientation
Interpret	Service	Position
MM-Animate	User	Spatial Attitude
MM-Capture
MM-Disable
MM-Embed
MU-Export
Register
Track

8.4        Hybrid working

8.4.1        Description

A company applies mixed in-presence and remote working policy.

1. Physical Workers attend Company physically.
2. All Workers
   • Are Authenticated.
   • Are present in the Virtual office.
   • Communicate by Sharing AV messages (except R-worker to R-worker).
   • Participate in Virtual meetings.

 

This is the detailed workflow:

1. User₁ (Manager):
   • Authors Entity₁ (Virtual office).
   • Embeds Entity₁ (Virtual office).
   • Embeds Entity₂ at Location_1.1 (Office gateway)
   • MM-Animates Persona₁ as “Virtual time clock”.
2. real worker:
   • Comes to real office.
3. User₂ (R-worker):
   • MM-Embeds Persona₁ at M-Location_2.1 (Virtual office).
4. User₃ (V-worker):
   • Tracks Persona₁ at M-Location_3.1
   • MM-Embeds Persona₁ at Location_3.2 (Virtual office).
5. User1 (“virtual time clock”) Authenticates:
   • User₂ (R-worker)
   • User₃ (V-worker).
6. User₃ (V-worker):
   • MM-Disables Persona₁ at Location_3.1
   • MM-Sends Object₁ (A) to User₂ (R-worker).
   • MM-Embeds Persona₁ at Location_3.3 (close to R-worker).
   • MM-Disables Persona₁ at Location_3.2
   • MM-Embeds Persona₁ at Location_3.4 (Vmeeting room).
   • MM-Disables Persona₁ at Location_3.3
7. User₂ (R-worker)
   • MM-Embeds Model₁ (VWiteboard) at M-Location_2.2 (Vmeeting room).
   • MM-Animates VWhiteboard
   • MM-Disables Persona₁ at Location_2.2 (Vmeeting room).
8. User₃ (V-worker):
   • MM-Embeds Persona₁ at Location_3.1 (Home).
   • MM-Disables Persona₁ at Location_3.1 (Vmeeting room).

8.4.2        Workflow and Actions

 

Table 14 – Hybrid Working workflow and actions.

Who	Does	What	Where/comment
User1 (Manager)	Authors	Entity1.1 (AV)	V-Office
	MM-Embeds	Entity1.1	M-Location1.1
	MM-Embed	Persona1.1 (AV)	M-Location1.2 (VTime clock)
	MM-Animates	Persona1.1 (AV)	M-Location1.2
User2 (R-Worker)	Tracks	Persona2.1 (AV)	M-Location2.1 (VOffice)
	Registers
	MM-Embeds	Persona2.1	M-Location12.1 (VOffice)
User3 (V-Worker)	Tracks	Persona3.1 (AV)	M-Location3.1 (home)
	MM-Embeds	Persona3.1	M-Location3.2 w/ SA (V-Desk)
User1 (VTime clock)	Authenticates	User2
	Authenticates	User3
User3 (V-Worker)	MM-Sends	Objects3.1 (A)	Persona2.1 (AV)
	MM-Embeds	Persona3.1	M-Location3.3 (talk “in person”)
	MM-Disables	Persona3.1 (AV)	M-Location3.2
	MM-Embeds	Persona3.1	M-Location3.4 (V-Meeting)
	MM-Disables	Persona3.1 (AV)	M-Location3.3
User2 (R-Worker)	MM-Embeds	Persona2.1	M-Location3.4 (V-Meeting)
	MM-Disables	Persona3.1 (AV)	M-Location2.2
	MM-Embeds	Entity2.1	(Whiteboard) M-Location3.4
	MM-Animate	Entity2.1	To operate Whiteboard
	MM-Embeds	Persona2.1 (AV)	M-Location2.1 (back home)
	MM-Disables	Persona2.1	From M-Location3.4
User3 (V-Worker)	MM-Embeds	Persona3.1 (AV)	M-Location3.1 (back home)
	MM-Disables	Persona3.1 (AV)	From M-Location3.4

8.4.3        Actions, Items, and Data Types

 

Table 15 – Hybrid Working Actions, Items, and Data Types

Actions	Items	Data Types
Author	Entity	Coordinates
Call	M-Location	Orientation
MM-Disable	Object (A)	Position
MM-Embed	Persona (AV)	Spatial Attitude
MM-Send	Service
Track	U-Location
	User

8.5        eSports Tournament

8.5.1        Description

A site manager makes a game landscape available to a game manager. The game manager deploys autonomous characters and places virtual camera and microphone in the landscape. They display the whole landscape onto a big screen and stream the whole landscape.

 

This is the detailed workflow:

1. User₁ (Site Manager)
   • Authors Entity₁ (game landscape).
   • MM-Embeds Entity₁ (game landscape) at M-Location_1.1.
2. User₂ (Game Manager)
   • MM-Embeds Personae_i with Spatial Attitude at M-Locations_2.i (Autonomous characters).
   • MM-Animates Personae_i.
   • Calls Service₁ (virtual camera/microphone control).
   • MU-Renders the Entities at M-Location₁ (landscape) to:
     • U-Location₁ via Device_1.1 (screen).
     • Various U-Locations (via streaming).

3. User₃ (Player) tracks Persona₁ (AV) at Location_3.1 with Spatial Attitude
4. Calls Process₁ to provide role-specific:
   • Costumes (e.g., magician, warrior).
   • Forms, physical features, and abilities (e.g., cast spells, shoot, fly, jump).

8.5.2        Workflow

 

Table 16 – eSports Tournament workflow and actions.

User1 (Site Manager)	Authors	Entity1.1	(Game landscape).
	MM-Embeds	Entity1.1	(Landscape) at M-Location1.1.
User2 (Game Manager)	MM-Embeds	Personae2.i w/SA	M-Locations2.i (AA).
	MM-Animates	Personae2.i.	M-Locations2.i (AA).
	Calls	Service2.1	(Vcamera/microphone control).
	MU-Renders	Entities	(Landscape) to: U-Location2.1 (via screen). U-Locations (via streaming).
User3 (Player)	Tracks	Persona3.1 w/ SA	Location3.1
	Calls	Process3.1	to provide role-specific: Costumes (magician, warrior). Forms, features, abilities.

8.5.3        Actions, Items, and Data Types

 

Table 17 – eSports Tournament Actions, Items, and Data Types.

Actions	Items	Data Types
Author	User	Spatial Attitude
Call	Persona (AV)	Coordinates
MM-Animate	Entity	Orientation
MM-Embed	Service	Position
Track	U-Location
	M-Location

8.6        Virtual performance

8.6.1        Description

Participant buys a ticket for an event with the right to stay close to the performance stage for 5 minutes. The event is organised by an organiser who has created a virtual auditorium and generates special effects by calling a service to collect participants’ preferences and another service to extract the participants status. The participant utters a private speech to another participant.

 

1. User₁ (Organiser)
   • Transacts Value₁ (buys a parcel at M-Location_1.1).
   • Authors Entity₁ (virtual auditorium).
   • MM-Embeds Entity₁ at M-Location_1.1.
   • Calls Service₁ (to collect Users’ Preferences).
2. User₂ (Performer)
   • Tracks Persona₁ at Location_2.1.
   • Embeds Persona₁ (AV) with Spatial Attitude at MLocation_2.2 (in virtual auditorium).
   • MM-Disables Persona₁ from Location_2.1.
3. User₃ (Participant)
   • Tracks Persona₁ at M-Location_3.1 (at home).
   • Transacts Value₁ (buys ticket).
   • Embeds Persona₁ (AV) with Spatial Attitude at Location_3.2 (in virtual auditorium).
   • MM-Disables Persona₁ (AV) from Location_3.1.
   • MM-Sends Object₁(A) to Persona_4.1 (Participant).
   • Calls Service₁ (expresses preferences).
   • MM-Adds Persona₁ at Location_3.2 (close to stage for 5 minutes).
4. User₁ (Organiser)
   • MM-Disables Persona₁ from Location_3.2 (5 minutes passed).
   • Calls Service₁ (Collects preferences).
   • Interprets Participants Status (of all participants).
   • MM-Embeds Entities_i (SFX).
   • Transacts Value₂ to User₂ (performance fees).
5. User₂ (Performer)
   • MM-Embeds Persona₁ (AV) to M-Location_2.1.
   • MM-Disables Persona₁ from M-Location_2.2.
6. User₃ (Participant)
   • MM-Embeds Persona₁ (AV) to M-Location_3.1.
   • MM-Disables Persona₁ from M-Location_3.2.

1.6.2        Workflow and Actions

 

Table 18 – Virtual Event workflow and actions.

User1 (Organiser)	Transacts	Value1.1	(Parcel at M-Location1.1).
	Authors	Entity1.1	(Virtual auditorium).
	MM-Embeds	Entity1.1	M-Location1.1.
	Calls	Service1.1	Collect Users’ Preferences).
User2 (Performer)	Tracks	Persona2.1	Location2.1.
	Embeds	Persona2.1 (AV) w/ SA	MLocation2.2 (Vauditorium).
	MM-Disables	Persona2.1	at Location2.1.
User3 (Participant)	Tracks	Persona3.1	M-Location3.1 (at home).
	Transacts	Value	(Buys ticket).
	Embeds	Persona3.1 (AV) w/ SA	Location3.2 (in Vauditorium).
	MM-Disables	Persona3.1 (AV)	Location3.1.
	MM-Sends	Object3.1 (A)	Persona4.1 (Participant).
	Calls	Service1.1	(Expresses preferences).
	MM-Adds	Persona3.1	Location3.2 (close to stage).
User1 (Organiser)	MM-Disables	Persona3.1	Location3.2 (after 5’).
	Calls	Service1.1	(Collects preferences).
	Interprets	Participants Status1.1.
	MM-Embeds	Entities1.i	(SFX).
	Transacts	Value1.2	User2 (performance fees).
User2 (Performer)	MM-Embeds	Persona2.1 (AV)	M-Location2.1.
	MM-Disables	Persona2.1	M-Location2.2.
User3 (Participant)	MM-Embeds	Persona3.1 (AV)	M-Location3.1.
	MM-Disables	Persona3.1	M-Location3.2.

8.6.3        Actions, Items, and Data Types

 

Table 19 – Virtual Event Actions, Items, and Data Types.

Actions	Items	Data Types
Author	Entity (AV)	Amount
Call	Object (A)	Cognitive State
Interpret	Persona (AV)	Coordinates
MM-Disable	M-Location	Currency
MM-Embed	Service	Emotion
MM-Send	U-Location	Orientation
Register	User	Personal Status
Track	Value	Position
Transact		Social Attitude
		Spatial Attitude
		Value

8.7        AR Tourist Guide

8.7.1        Description

In his Use Case human₃ engages the following humans:

1. human₁ to cause their User₁ to buy a virtual parcel and develop a virtual landscape suitable for a tourist application.
2. human₂ to cause their User₂ to develop scenes and autonomous agents for the different places of the landscape.
3. human₄ to create an app that alerts the holder of a smart phone where the app is installed.
4. human₅ holding a smart phone with the app to perceive Entities and talk to Personae MM-Embedded at M-Locations and MM-Animated by autonomous agents (AA).

 

This is the detailed workflow of the Use Case:

1. User₁
   • Buys M-Location₁ (parcel) in an M-Environment.
   • Authors Entity₁ (landscape suitable for a virtual path through n sub-M-Locations).
   • Embeds Entity₁ (landscape) on M-Location_1.1 (parcel).
   • Sells Entity₁ (landscape) and M-Location_1.1 (parcel) to a User₂.
2. User₂
   • Authors Entity₁ to Entity_2.n for the M-Locations.
   • Embeds the Entities at M-Location₁ to M-Location_2.n.
   • Sells the result to User₃.
3. human₄
   • Develops
     • Map recording the pairs M-Location_i – U-Location_2.i
     • App alerting a human₅ holding the Device with the App installed that a key U-Location has been reached.
   • Sells Map and App to human₃.
4. User₃ MM-Embeds one or more autonomous Personae at M-Location₁ to M-Location_2.n.
5. human₅ gets close to key U-Location₁:
6. App₁ MM-Sends Message_5.1 to Device_5.1
7. Device₁
   • MU-Renders Entity₁ MM-Embedded at M-Location_5.1 to key U-Location_5.1.
   • MU-Rendered Entity₁.
   • MU-Animated Persona₁.
   • UM-Animated Persona₂.

1.7.2        Workflow

 

Table 20 – AR Tourist Guide workflow.

Who	Does	What	Where/comment
User1	Transacts	Value1.1	M-Location1.1’s parcel.
	Authors	Entity1.1	(Path of n M-Locations).
	Embeds	Entity1.1	(Parcel).
	Transacts	Value1.1	(Landscape & parcel to User2).
User2	Authors	Entity2.1 to Entity2.n	(For M-Locations2.1-2.n).
	Embeds	Entity2.1-2.n	M-Location2.1-2.n
	Transacts2.1	Entity2.1-2.n	User3.
human4	develops	Map	M-Locations & U-Locations
	develops	App
	sells	Map and App	To human3.
User3	MM-Embeds	Personae	M-Location2.1-2.n.
	MM-Animates	Personae	M-Location2.1-2.n.
human5	comes to		At key U-Location2.i.
App5.1	MM-Sends	Message5.1	Device5.1
Device5.1	MU-Renders	Entity5.1 @M-Location5.1	At key U-Location5.1.
	MU-Renders	MM-Animated Persona5.1	At key U-Location5.1.
	MU-Renders	UM-Animated Persona5.2	At key U-Location5.1.

1.7.3        Actions, Items, and Data Types

 

Table 21 – AR Tourist Guide Actions, Items, and Data Types.

Actions	Items	Data Types
Author	App	Amount
Author	Device	Coordinates
MM-Animate	Entity	Currency
MM-Animate	Map	Orientation
MM-Embed	M-Location	Position
MM-Send	Persona	Spatial Attitude
MU-Export	Service	Value
MU-Render	U-Location
Send	User
Transact
UM-Animate

8.8        Virtual Dance

8.8.1        Description

This Use Cases envisages that:

1. A dance teacher:
   • Is in its office.
   • Places a virtual secretary in the dance school animated by an autonomous agent.
2. A student #1:
   • Is at home.
   • Shows up at the school.
   • Greets the secretary.
3. The secretary
   • Reciprocates the greeting.
   • Sends a private vocal message to the teacher.
4. The teacher:
   • Places its persona₁ (AVH) in the dance school.
   • Dances with student #1.
5. A student #2:
   • Is at home.
   • Shows up at school.
6. The teacher:
   • Places its persona₁ (AVH) close to student #2.
   • Places its persona₃ (AVH) where persona_2.1 was before.
   • Animates its persona₃ with autonomous agent to dance with student #1.
   • Dances with student #2.

 

1. User₂ (dance teacher)
   • Tracks Persona₁ at M-Location_2.1
   • MM-Embeds Persona₂ (AV) (another of its Personae) at M-Location_2.2.
   • MM-Animates Persona₂ (AV) (as virtual secretary to attend to students coming to learn dance).
2. User₁ (dance student #1):
   • MM-Embeds its Persona₁ (AV) at Location_1.1 (its “home”).
   • MM-Embeds Persona₁ (AVH) at Location_1.2 close to virtual secretary).
   • MM-Sends Object₁ (A) to Persona_2.2 (greets virtual secretary).
   • MM-Disables Persona₁ from Location_1.1.
3. User₂ (Persona₂):
   • MM-Sends Object₁ (A) (to dance student #1 to reciprocate greeting).
   • MM-Send Object₂ (A) (to call teacher’s Persona_2.1).
4. Dance teacher (Persona₁):
   • MM-Embeds (AVH) Persona₁ at Location_2.3 (classroom).
   • UM-Animates Persona₁ (dances with student #1).
5. While Persona₁ (student #1) and Persona_2.1 (teacher) dance, User₃ (dance student #2):
   • MM-Embeds (AV) Persona₁ (its digital twin) at Location_3.1 (its “home”).
   • MM-Embeds (AVH) Persona₁ at Location_3.2 (close to secretary).
   • MM-Disables Persona₁ from Location_3.1.
6. After a while, User₂ (dance teacher):
   • MM-Embeds (AVH) Persona₁ at Location_2.4 (close to student #2’s position).
   • MM-Disables Persona₁ (from where it was dancing with student #1).
   • MM-Embeds (AVH) Persona₃
   • MM-Animates Persona₃ with autonomous agent (to dance with student #1).

8.8.2        Workflow

 

Table 22 – Virtual Dance workflow.

User2 (teacher)	Tracks	Persona2.1	M-Location2.1
	MM-Embeds (AV)	Persona2.2	M-Location2.2.
	MM-Animates (AV)	Persona2.2	(As VS for students).
User1 (student1)	MM-Embeds (AV)	Persona1.1	Location1.1 (its “home”).
	MM-Embeds (AVH)	Persona1.1	Location1.2 (close to VS).
	MM-Sends	Object1.1 (A)	Persona2.2 (greets VS).
	MM-Disables	Persona1.1	from Location1.1.
User2 (Persona2.1)	MM-Sends	Object2.1 (A)	(Responds to student #1).
	MM-Send	Object2.2 (A)	(Calls teacher’s Persona2.1).
User2 (Persona2.2)	MM-Embeds (AVH)	Persona2.1	Location2.3 (classroom).
User2 (Persona2.2)	UM-Animates	Persona2.1	(Dances with student #1).
User3 (student2)	MM-Embeds (AV)	Persona3.1	Location3.1 (its “home”).
	MM-Embeds (AVH)	Persona3.1	Location3.2 (close to VS).
	MM-Disables	Persona3.1	from Location3.1.
User2 (teacher)	MM-Embeds (AVH)	Persona2.1	Location2.4 (near student2).
	MM-Disables	Persona2.1	(From previous position).
	MM-Embeds (AVH)	Persona2.3
	MM-Animates	Persona2.3	(w/ AA with student #1).

 

8.8.3        Actions, Items, and Data Types

 

Table 23 – Virtual Dance Actions, Items, and Data Types.

Actions	Items	Data Types
MM-Animate	M-Location	Amount
MM-Disable	Object (A)	Currency
MM-Embed	Persona (AV)	Orientation
MM-Send	Persona (AVH)	Position
Track	Service	Spatial Attitude
Transact	U-Location
	Value

8.9        Virtual Car Showroom

8.9.1        Description

This Use Cases envisages that:

1. A car dealer
   • Is in its office.
   • Embeds a persona animated by an autonomous agent in the car showroom (attendant).
2. A customer in its home
   • Embeds its persona in the car showroom.
   • Greets the showroom attendant.
3. The Showroom attendant
   • Reciprocates the greeting.
   • Privately calls the dealer.
4. The dealer
   • Animates the attendant with the human car dealer.
   • Converses with the customer.
   • Embeds a 3D AVH model of a car.
5. The customer
   • Interacts with the model (has a virtual drive).
   • Buys the car.
   • Returns home.

 

This is the detailed workflow of the Use Case:

1. User₁ (car dealer):
   • Tracks Persona₁ at M-Location_1.1 (“office”).
   • MM-Embeds Persona₂ with Spatial Attitude_1.1 at M-Location_1.2 (“showroom”).
   • MM-Animates Persona₂ (with an autonomous agent – showroom attendant).
2. User₂ (customer):
   • Tracks Persona₁ at M-Location_2.1 (“home”).
   • MM-Embeds Persona₁ at M-Location_2.1 (“in the showroom”).
   • MM-Sends Object₁ (A) to Persona_1.2 (greets showroom attendant).
   • MM-Disables Persona₁ at M-Location_2.1 (“home”).
3. User₁ (Persona₂):
   • MM-Sends Object₁ (A) to Persona_2.1 (responds to greetings).
   • MM-Sends Object₂ (A) to Persona_1.1 (“come attend customer”).
4. User₁ (Persona₁)
   • MM-Embeds Persona₁ at M-Location_1.3 (“in the showroom”).
   • MM-Sends Object₂ (A) to Persona_2.1 (engages in conversation).
   • MM-Embeds Model₁ (AVH) at M-Location_1.4 (model car “in the showroom”).
   • MM-Animates Model₁ (“animate model car”).
5. User₂ (customer)
   • MM-Embeds Persona₁ at M-Location_2.3 (where the virtual car is located)
   • UM-Animates Persona₁.
   • Transacts Value₁ (buys car).
   • MM-Disables Persona₁ at M-Location_1.3.
   • MM-Embeds Persona₁ at M-Location_2.1 (“at home”).

1.9.2        Workflow

Table 24 – Virtual Car Showroom workflow.

User1 (car dealer)	Tracks	Persona1.1	M-Location1.1 (“office”).
	MM-Embeds	Persona1.2 w/ SA1.1	M-Location1.2 (“showroom”).
	MM-Animates	Persona1.2 w/ AA	(Showroom attendant).
User2 (customer)	Tracks	Persona2.1	M-Location2.1 (“home”).
	MM-Embeds	Persona2.1	M-Location2.1 (“showroom”).
	MM-Sends	Object1.1 (A)	Persona1.2 (greets attendant).
	MM-Disables	Persona2.1	M-Location2.1 (“home”).
User1 (Persona1.2)	MM-Sends	Object1.1 (A)	Persona2.1 (responds to greetings).
	MM-Sends	Object1.2 (A)	Persona1.1 (“attend customer”).
User1 (Persona1.1)	MM-Embeds	Persona1.1	M-Location1.3 (“showroom”).
	MM-Sends	Object1.2 (A)	Persona2.1 (converses).
	MM-Embeds	Model1.1 (AVH)	M-Location1.4 (“in showroom”).
	MM-Animates	Model1.1 w/ AA	(“Animate model car”).
User2 (customer)	MM-Embeds	Persona2.1	M-Location2.3 (in virtual car)
	UM-Animates	Persona2.1	(Drives virtual car)
	Transacts	Value2.1	(Buys car).
	MM-Disables	Persona2.1	M-Location1.3.
	MM-Embeds	Persona2.1	M-Location2.1 (“at home”).

8.9.3        Actions, Items, and Data Types

 

Table 25 – Virtual Car Showroom Actions, Items, and Data Types.

Actions	Items	Data Types
Call	Object (A)	Amount
Embeds	Persona	Currency
MM-Animate	Scene (AVH)	Orientation
MM-Disable	Value	Position
MM-Embed		Spatial Attitude
MM-Send
Track
Transacts
UM-Animate

8.10    Drive a Connected Autonomous Vehicle

8.10.1    Description

MPAI is developing a Technical Report that includes a reference model of a Connected Autonomous Vehicle (CAV) based on the subdivision of a CAV in 4 subsystem each implemented as a workflow of AI Modules executed in the standard MPAI-AIF framework [5]. A CAV has the capability to autonomously reach a U-Location by understanding human utterances, planning a Route, sensing the U-environment, building a representation of it, exchanging such representations with other CAVs and CAV-aware entities, making decisions about how to execute the Route, and acting on the Motion Actuation Subsystem to implement the decision (see Figure 2).

Figure 2 – MPAI-CAV Reference Model

This Use Case assumes that a human having rights to or owning a CAV Registers with the CAV by providing:

1. The requested subset of their Personal profile.
2. Two User Processes required to operate a CAV:
   • User₁ to operate the Human-CAV Interaction Subsystem.
   • User₂ to operate the Autonomous Motion Subsystem.
3. User₁’s Personae.

The Processes of a CAV generate a persistent M-Instance resulting from the integration of:

1. The Environment Representation generated by the Environment Sensing Subsystem by UM-Capturing the U-Location being traversed by the CAV.
2. The Scenes MM-Captured from the M-Locations of the M-Instances that are digital twins of the U-Locations being traversed by other CAVs that are close to the U-Location of the Ego CAV and improve the accuracy of the CAV’s M-Locations.
3. Relevant Experiences of the Autonomous Motion Subsystem at the M-Location.

For simplicity, the Use Case assumes that there are only two CAVs: CAV_A and CAV_B. The convention of having Users identified by a sequential number is extended as follows: “a User of CAV_A is identified by A followed by a sequential number”. Items affected by User_A.1 are identified as A.1 followed by a sequential number.

1. User₁
   • Authenticates the human and gets it driving instructions.
   • Requests a series of options satisfying the instructions.
2. User₂
   • Gets information about CAV_A
   • Gets options from Route Planner.
   • Communicates options to User₁.
3. User₁
   • Converts the options to an utterance.
   • Communicates the utterance to the human.
4. human sends utterance with the option to User₁
5. User₁ converts utterance to a command.
6. User₂
   • Authenticates its peer User₂
   • Gets the Environment Representation from its ESS and User₂
   • Sends a command to the Motion Actuation Subsystem.
   • Requests permission to place Persona_1.1 in the virtual cabin of CAV_B.
   • Receives permission and places Persona_1.1
   • Watches the landscape through the window of CAV_B.

 

This is detailed workflow:

1. human_A
2. User₁
   • Tracks Persona_1.1 at M-Location_A.1.1 (`connects CAV_A’s M-Instance with U-Location).
   • Authenticates Object_1.1(AV) (recognises human_A).
   • Interprets Object_1.1(A) (human_A’s request to go home).
   • MM-Sends HCI-AMSCommand_1.1 to User_A.2.
3. User₂
   • MM-Sends ESS’s Scene_2.1 to RoutePlanner.
   • MM-Sends Route_2.1 to User_A.1.
4. User₁
   • MU-Renders Object_1.2 (A) (to human_A).
   • UM-Renders Object_1.3 (A) (human_A’s Route selection).
   • Interprets Object_1.3 (A) (understand Route).
   • MM-Sends HCI-AMSCommand_1.2 to User_A.2.
5. User₂
   • Authenticates User₂.
   • MM-Sends
     • ESS’s Scene_2.2 to Environment Representation Fusion (ERF).
     • Scene_2.3 at M-Location_A.2.1 (in CAV_B’s M-Instance) to ERF.
     • Path₁ to Motion Planner.
     • Trajectory_2.1 to Obstacle Avoider (does not request a new Trajectory).
     • Trajectory_2.1 to Command Issuer.
     • AMS-MASCommand_2.1 to Motion Actuation Subsystem.
     • MAS-AMS Response_2.1.

6. User₁
   • Authenticates User₂.
   • MM-Sends Object_1.4 (A) (request to Embed Persona_1.1 in CAV_B virtual cabin) to User_B.1.
7. User₁ MM-Sends Object_B.1.1 (A) (request accepted) to User_A.1.
8. User₁
   • MM-Embeds Persona_1.1 at M-Location_A.1.2 (User_B.1’s cabin).
   • MM-Captures Scene_1.1 M-Location_A.1.3 (Environment outside of User_B.1’s cabin).

 

User_A.1 can now view and navigate the M-instance created by CAV_A traversing the U-Environment (M-Location_A.1.2) and Device_A.1. allows User_A.1 to be MM-Embedded, i.e., to become part of the M-Location_A.1.1 (User_B.1’s cabin).

8.10.2    Workflow

Table 26 – Drive a Connected Autonomous Vehicle workflow.

Who	Does	What	Where/(comment)
humanA	Registers		(With CAVA).
UserA.1	Tracks	PersonaA.1.1	(M-LocationA.1.1 connects U-LocationA.1.1).
	Authenticates	ObjectA.1.1(AV)	(Recognises humanA).
	Interprets	ObjectA.1.1(A)	(humanA’s request to go).
	MM-Sends	HCI-AMSCmdA.1.1	UserA.2.
UserA.2	MM-Sends	ESS’s SceneA.2.1	Route Planner.
	MM-Sends	AMS-HCIRespA.2.1	RouteA.2.1 to UserA.1
UserA.1	MU-Renders	ObjectA.1.2 (A)	(To humanA).
	UM-Renders	ObjectA.1.3 (A)	(Route selection).
	Interprets	ObjectA.1.3 (A)	(Understand Route).
	MM-Sends	HCI-AMSCmdA.1.2	UserA.2
UserA.2	Authenticates	UserB.2
	MM-Sends	ESS’s SceneA.2.2	(To Environment Representation Fusion).
		SceneA.2.3	M-LocationA.2.1 (in CAVB’s to ERF).
		PathA2.1	Motion Planner.
		TrajectoryA.2.1	Obstacle Avoider.
		TrajectoryA.2.1	Command Issuer.
		AMS-MASCmdA.2.1	MAS.
		MAS-AMS RespA.2.1.	From MAS.
UserA.1	Authenticates	UserA.2.
	MM-Sends	ObjectA.1.4 (A)	(Request to Embed to UserB.1)
UserB.1	MM-Sends	ObjectB.1.1 (A)	(Request accepted to UserA.1).
UserA.1	MM-Embeds	PersonaA.1.1	M-LocationA.1.2 (UserB.1’s cabin).
	MM-Captures	SceneA.1.1	M-LocationA.1.3 (out of UserB.1’s cabin).

8.10.3    Actions, Items, and Data Types

Note: The MPAI-CAV specific Items are included.

 

Table 27 – Drive a Connected Autonomous Vehicle Actions, Items, and Data Types.

Action	Item	Data Types
Authenticate	AMS-MASCommand	Spatial Attitude
Interpret	AMS-HCIResponse	Coordinates
MM-Capture	Environment Representation	Orientation
MM-Capture	HCI-AMSCommand	Position
MM-Embed	MAS-AMS Response
MM-Send	M-Location
MM-Send	Object (A)
MU-Render	Object (AV)
Register	PathA2.1
Request	Persona
Request	Route
Track	Scene
UM-Render	Trajectory
	User

 

<- Data Types    Go to ToC    Functionality Profiles –>