Device scenario management
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.
1. A system for implementing scenario profiles, the system comprising:
at least one computing device; and
at least one application executable in the at least one computing device, wherein the at least one application, when executed, causes the at least one computing device to:
identify a client device associated with a scenario, the scenario being associated with a performance of a plurality of different tasks performed by a plurality of client devices having different capabilities;
determine one or more capabilities of the client device;
generate a scenario profile for the client device, the scenario profile defining at least one task of the plurality of different tasks to be performed by the client device during the scenario based at least in part on one or more capabilities of the client device; and
cause the scenario profile to be distributed to the client device.
2. The system of claim 1 , wherein the client device is identified based at least on a client device location and a scenario location.
3. The system of claim 1 , wherein, when executed, the at least one application further causes the at least one computing device to at least receive scenario profile settings defining the scenario profile via one or more user interactions by an administrator with an administrator console.
4. The system of claim 1 , wherein the scenario profile further defines a device setting associated with at least one of a function or a feature of the client device.
5. The system of claim 4 , wherein, when executed, the at least one application further causes the at least one computing device to at least:
determine a modification of the device setting by a user input during an occurrence of the scenario; and
update the scenario profile to change the device setting to the modified device setting.
6. The system of claim 4 , wherein when executed, the at least one application further causes the at least one computing device to at least:
determine to update the scenario profile to add a second device setting based at least in part on a determination that the second device setting has been updated a threshold number of times during one or more occurrences of the scenario;
modify the scenario profile to include the second device setting; and
cause the modified scenario profile to be distributed to the client device.
7. The system of claim 1 , wherein when executed, the at least one application further causes the at least one computing device to at least:
receive event data from the client device, the event data comprising a timestamp and an indication of an event associated with t functionality of the client device;
determine that the event occurred during an occurrence of the scenario based on the timestamp; and
adjust the scenario profile based at least in part on the event data.
8. A computer-implemented method for implementing scenario profiles, the method comprising:
identifying, by at least one computing device, a client device associated with a scenario, the scenario being associated with a performance of a plurality of different tasks performed by a plurality of client devices having different capabilities;
determining, by the at least one computing device, one or more capabilities of the client device;
generating, by the at least one computing device, a scenario profile for the client device, the scenario profile defining the at least one task of the plurality of different tasks to be performed by the client device during the scenario based at least in part on one or more capabilities of the client device; and
causing, by the at least one computing device, the scenario profile to be distributed to the client device.
9. The computer-implemented method of claim 8 , wherein the client device is identified based at least on a client device location and a scenario location.
10. The computer-implemented method of claim 8 , further comprising receiving, by the at least one computing device, scenario profile settings defining the scenario profile via one or more user interactions by an administrator with an administrator console.
11. The computer-implemented method of claim 8 , wherein the scenario profile further defines a device setting associated with at least one of a function or a feature of the client device.
12. The computer-implemented method of claim 11 , further comprising:
determining, by the at least one computing device, a modification of the device setting by a user input during an occurrence of the scenario; and
updating, by the at least one computing device, the scenario profile to change the device setting to the modified device setting.
13. The computer-implemented method of claim 11 , further comprising:
determining, by the at least one computing device, to update the scenario profile to add a second device setting based at least in part on a determination that the second device setting has been updated a threshold number of times during one or more occurrences of the scenario;
modifying, by the at least one computing device, the scenario profile to include the second device setting; and
causing, by the at least one computing device, the modified scenario profile to be distributed to the client device.
14. The computer-implemented method of claim 8 , further comprising:
receiving, by the at least one computing device, event data from the client device, the event data comprising a timestamp and an indication of an event associated with t functionality of the client device;
determining, by the at least one computing device, that the event occurred during an occurrence of the scenario based on the timestamp; and
adjusting, by the at least one computing device, the scenario profile based at least in part on the event data.
15. A non-transitory computer-readable medium embodying a program executable in at least one computing device, wherein when executed, the program causes the at least one computing device to at least:
identify a client device associated with a scenario, the scenario being associated with a performance of a plurality of different tasks performed by a plurality of client devices having different capabilities;
determine one or more capabilities of the client device;
generate a scenario profile for the client device, the scenario profile defining the at least one task of the plurality of different tasks to be performed by the client device during the scenario based at least in part on one or more capabilities of the client device; and
cause the scenario profile to be distributed to the client device.
16. The non-transitory computer-readable medium of claim 15 , wherein the client device is identified based at least on a client device location and a scenario location.
17. The non-transitory computer-readable medium of claim 15 , wherein, when executed, the program further causes the at least one computing device to at least receive scenario profile settings defining the scenario profile via one or more user interactions by an administrator with an administrator console.
18. The non-transitory computer-readable medium of claim 15 , wherein:
the scenario profile further defines a device setting associated with at least one of a function or a feature of the client device, and
when executed, the program further causes the at least one computing device to at least:
determine a modification of the device setting by a user input during an occurrence of the scenario; and
update the scenario profile to change the device setting to the modified device setting.
19. The non-transitory computer-readable medium of claim 15 , wherein:
the scenario profile further defines a device setting associated with at least one of a function or a feature of the client device, and
when executed, the program further causes the at least one computing device to at least:
determine to update the scenario profile to add a second device setting based at least in part on a determination that the second device setting has been updated a threshold number of times during one or more occurrences of the scenario;
modify the scenario profile to include the second device setting; and
cause the modified scenario profile to be distributed to the client device.
20. The non-transitory computer-readable medium of claim 15 , wherein, when executed the program further causes the at least one computing device to at least:
receive event data from the client device, the event data comprising a timestamp and an indication of an event associated with t functionality of the client device;
determine that the event occurred during an occurrence of the scenario based on the timestamp; and
adjust the scenario profile based at least in part on the event data.