Messaging Use Cases

Participant Injects Object

Participant puts a new object into a bubble. The actual object is simulated on the participant side. Bubble only contains state data and rough 3d location, bounds and orientation.

Participant Modifies Object

Participant modifies an object in a bubble. Daemon objects may update objects owned by others to enforce fundamental laws of the bubble.

Participant Executes Object Action

Participant sends an action message to bubble which is broadcasted to participant inside observation radius from the object in question.

Participant Ejects Object

Participant removes an object from a bubble.

Participant Interacts with Object

Participant interacts with others object directly or via owned object (avatar).

Participant Interacts with Participant

Participant interacts with other participant.

Participant Observes Bubble

Participant observes limited volume of a bubble for events.

Bubble Observes Bubble

One bubble observes limited volume of another bubble for events.

Participant Connects to Bubble

• Opening and closing connections.
• Controlling the connection.

Bubble Connects to Bubble

• Opening and closing connections.
• Controlling the connection.

Handover

Roaming object is handed from one bubble to another. Bubbles detect that object is moving out of their range and transfer it to another bubble in analogy with mobile devices and base stations. Participant has to connect to the new bubble when notified of the handover. If participant has objects in several bubbles then it needs connection to all these bubbles.

Validate Peer Implementation

For some closed clouds it might be allowed to join with only certain implementations.