IP Library Granted Patent US 10,812,286
Granted Patent B2
US 10,812,286 · App. 16/247,674 · Granted Oct 20, 2020

Device scenario management

Inventors: Ramani Panchapakesan (Bangalore, IN); Suman Aluvala (Bangalore, IN)
Assignee: VMWARE, INC.
H04L12/2814H04L12/281H04L12/2809H04L12/2812H04L12/2818
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,812,286
App. No.
16/247,674
Granted
Oct 20, 2020
Kind
B2
Abstract

Disclosed are various examples for dynamically generating and implementing scenario profiles for a network of devices, including IoT devices. A managed device can receive a dynamically generated scenario profile that defines tasks to be performed by the device for a given scenario. The device can also receive a scenario message that is broadcasted to all managed devices in a network and identifies an occurrence of a given scenario. If the device determines that the device is an intended recipient of the scenario message, the device can identify the scenario profile associated with the given scenario and perform the tasks defined by the scenario profile. The scenario profile can be modified and/or updated based on event data associated with the device.

Claims (61)

1. A system for implementing scenario profiles, the system comprising:

a computing device; and

at least one application executable in the computing device, wherein the at least one application, when executed, causes the computing device to:

receive a message identifying a scenario associated with a performance of a plurality of different tasks performed by a plurality of computing devices having different capabilities, the message being broadcasted over a network including the plurality of computing devices, and the message comprising at least one of a scenario name, a scenario start time, or a link for accessing content associated with the scenario;

determine that the computing device is an intended recipient of the message;

access a scenario profile associated with the scenario, the scenario profile indicating at least one task of the plurality of different tasks to be performed by the computing device; and

execute the task.

2. The system of claim 1 , wherein when executed, the at least one application further causes the computing device to at least receive the scenario profile from a management server device.

3. The system of claim 1 , wherein:

the message further includes a scenario group identifier for a group of computing devices in a scenario group associated with the scenario, and

determining that the computing device is the intended recipient of the message further comprises determining that the computing device is included in the scenario group based on the scenario group identifier.

4. The system of claim 1 , wherein:

the computing device is a first computing device of the plurality of computing devices in the network; and

individual computing devices of the plurality of computing devices have different scenario profiles from one another for the scenario according to respective capabilities of the individual computing devices.

5. The system of claim 1 , wherein when executed, the at least one application further causes the computing device to at least:

determine that the task requires completion of another task by another computing device;

generate another message identifying another scenario associated with the other task; and

cause the other message to be broadcasted to a plurality of other computing devices in the network.

6. The system of claim 1 , wherein when executed, the at least one application further causes the computing device to at least:

identify an event associated with a capability of the computing device; and

send a notification of the event to a management server device, the notification including event data identifying the event.

7. The system of claim 6 , wherein when executed, the at least one application further causes the computing device to at least receive an updated scenario profile, the updated scenario profile being dynamically generated by the management server device based at least in part on the event data.

8. A computer-implemented method for implementing scenario profiles, the method comprising:

receiving, by a computing device, a message identifying a scenario associated with a performance of a plurality of different tasks performed by a plurality of computing devices having different capabilities, the message being broadcasted over a network including the plurality of computing devices, and the message comprising at least one of a scenario name, a scenario start time, or a link for accessing content associated with the scenario;

determining that the computing device is an intended recipient of the message;

accessing, on the computing device, a scenario profile associated with the scenario, the scenario profile indicating at least one task of the plurality of different tasks to be performed by the computing device; and

executing the task.

9. The computer-implemented method of claim 8 , further comprising receiving the scenario profile from a management server device.

10. The computer-implemented method of claim 8 , wherein:

the message further includes a scenario group identifier for a group of computing devices in a scenario group associated with the scenario, and

determining that the computing device is the intended recipient of the message further comprises determining that the computing device is included in the scenario group based on the scenario group identifier.

11. The computer-implemented method of claim 8 , wherein:

the computing device is a first computing device of the plurality of computing devices in the network; and

individual computing devices of the plurality of computing devices have different scenario profiles from one another for the scenario according to respective capabilities of the individual computing devices.

12. The computer-implemented method of claim 8 , further comprising:

determining that the task requires completion of another task by another computing device;

generating another message identifying another scenario associated with the other task; and

causing the other message to be broadcasted to a plurality of other computing devices in the network.

13. The computer-implemented method of claim 8 , further comprising:

identifying an event associated with a capability of the computing device; and

sending a notification of the event to a management server device, the notification including event data identifying the event.

14. The computer-implemented method of claim 13 , further comprising receiving an updated scenario profile, the updated scenario profile being dynamically generated by the management server device based at least in part on the event data.

15. A non-transitory computer-readable medium embodying a program executable in a computing device, wherein when executed, the program causes the computing device to at least:

receive a message identifying a scenario associated with a performance of a plurality of different tasks performed by a plurality of computing devices having different capabilities, the message being broadcasted over a network including the plurality of computing devices, and the message comprising at least one of a scenario name, a scenario start time, or a link for accessing content associated with the scenario;

determine that the computing device is an intended recipient of the message;

access a scenario profile associated with the scenario, the scenario profile indicating at least one task of the plurality of different tasks to be performed by the computing device; and

execute the task.

16. The non-transitory computer-readable medium of claim 15 , wherein when executed, the program further causes the computing device to at least receive the scenario profile from a management server device.

17. The non-transitory computer-readable medium of claim 15 , wherein:

the message further includes a scenario group identifier for a group of computing devices in a scenario group associated with the scenario, and

determining that the computing device is the intended recipient of the message further comprises determining that the computing device is included in the scenario group based on the scenario group identifier.

18. The non-transitory computer-readable medium of claim 15 , wherein:

the computing device is a first computing device of the plurality of computing devices in the network; and

individual computing devices of the plurality of computing devices have different scenario profiles from one another for the scenario according to respective capabilities of the individual computing devices.

19. The non-transitory computer-readable medium of claim 15 , wherein, when executed, the program further causes the computing device to at least:

determine that the task requires completion of another task by another computing device;

generate another message identifying another scenario associated with the other task; and

cause the other message to be broadcasted to a plurality of other computing devices in the network.

20. The non-transitory computer-readable medium of claim 15 , wherein, when executed the program further causes the computing device to at least:

identify an event associated with a capability of the computing device; and

send a notification of the event to a management server device, the notification including event data identifying the event.

Assignments (4)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067103/0030 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 28, 2019
From: PANCHAPAKESAN, RAMANI; ALUVALA, SUMAN
To: VMWARE, INC.
Reel/Frame 048155/0751 →