Dynamic chain of actions for IOT devices
Various examples are disclosed for performing dynamic chains of action for Internet-of-Things (IoT) devices. In some aspects, IoT event data is received from an IoT device. An IoT dependency graph is identified based on an initial IoT event specified by the IoT dependency graph. An IoT event subsequent to the initial IoT event is identified according to the IoT dependency graph. A command is transmitted to an IoT device to perform the IoT event.
1. A system, comprising:
at least one computing device; and
program instructions stored in at least one memory of the at least one computing device, wherein the instructions, when executed by at least one processor, cause the at least one computing device to at least:
receive Internet-of Things (IoT) event data from an IoT device;
identify an IoT dependency graph that is identified based on an initial IoT event specified by the IoT dependency graph corresponding to the IoT event data;
identify at least one IoT event subsequent to the initial IoT event in the IoT dependency graph;
determine, by a server-layer device of a computing environment comprising a server layer and an edge layer, that the IoT dependency graph is evaluable at the edge layer based on the IoT dependency graph specifying a single edge device as an edge device through which a respective one of a plurality of IoT devices in the IoT dependency graph perform network communications; and
transmit, by the server-layer device to the single edge device, the IoT dependency graph to the single edge device, wherein the single edge device transmits, to at least one IoT device, at least one command for the at least one IoT device to perform the at least one IoT event.
2. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, from a respective IoT device of the at least one IoT device, an IoT event confirmation; and
update an IoT graph sequence of the IoT dependency graph based on the IoT event confirmation.
3. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
retrieve, from an IoT knowledge structure, instructions to perform the at least one IoT event; and
generate, based on the instructions, the at least one command for the at least one IoT device to perform the at least one IoT event.
4. The system of claim 1 , wherein the IoT dependency graph comprises a directed acyclic graph.
5. The system of claim 1 , wherein the IoT dependency graph specifies, for at least one event of a plurality of events of the IoT dependency graph: an event identifier, an IoT device identifier, an edge device identifier, and a parent event identifier.
6. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
determine that a second IoT dependency graph is unevaluable at the edge layer based on the second IoT dependency graph specifying a second plurality of IoT devices that are connected to a plurality of different edge devices; and
store the second IoT dependency graph at the server layer for server layer evaluation based on the IoT dependency graph being unevaluable at the edge layer.
7. The system of claim 1 , wherein the IoT event data comprises an edge device identifier, an IoT device identifier, and an event identifier.
8. A method performed by instructions executed by at least one computing device, the method comprising:
receiving, by the at least one computing device, Internet-of Things (IoT) event data from an IoT device;
identifying, by the at least one computing device, an IoT dependency graph that is identified based on an initial IoT event specified by the IoT dependency graph corresponding to the IoT event data;
identifying, by the at least one computing device, at least one IoT event subsequent to the initial IoT event in the IoT dependency graph
determining, by a server-layer device of a computing environment comprising a server layer and an edge layer, that the IoT dependency graph is evaluable at the edge layer based on the IoT dependency graph specifying a single edge device as an edge device through which a respective one of a plurality of IoT devices in the IoT dependency graph perform network communications; and
transmitting, by the server-layer device to the single edge device, the IoT dependency graph to the single edge device, wherein the single edge device transmits, to at least one IoT device, at least one command for the at least one IoT device to perform the at least one IoT event.
9. The method of claim 8 , further comprising:
receiving, from a respective IoT device of the at least one IoT device, an IoT event confirmation; and
updating an IoT graph sequence of the IoT dependency graph based on the IoT event confirmation.
10. The method of claim 8 , further comprising:
retrieving, from an IoT knowledge structure, instructions to perform the at least one IoT event; and
generating, based on the instructions, the at least one command for the at least one IoT device to perform the at least one IoT event.
11. The method of claim 8 , wherein the IoT dependency graph comprises a directed acyclic graph.
12. The method of claim 8 , wherein the IoT dependency graph specifies, for at least one event of a plurality of events of the IoT dependency graph: an event identifier, an IoT device identifier, an edge device identifier, and a parent event identifier.
13. The method of claim 8 , further comprising:
determining that a second IoT dependency graph is unevaluable at the edge layer based on the second IoT dependency graph specifying a second plurality of IoT devices that are connected to a plurality of different edge devices; and
storing the second IoT dependency graph at the server layer for server layer evaluation based on the IoT dependency graph being unevaluable at the edge layer.
14. The method of claim 8 , wherein the IoT event data comprises an edge device identifier, an IoT device identifier, and an event identifier.
15. A non-transitory computer-readable medium comprising program instructions that when executed by at least one processor, cause at least one computing device to at least:
receive Internet-of Things (IoT) event data from an IoT device;
identify an IoT dependency graph that is identified based on an initial IoT event specified by the IoT dependency graph corresponding to the IoT event data;
identify at least one IoT event subsequent to the initial IoT event in the IoT dependency graph;
determine, by a server-layer device of a computing environment comprising a server layer and an edge layer, that the IoT dependency graph is evaluable at the edge layer based on the IoT dependency graph specifying a single edge device as an edge device through which a respective one of a plurality of IoT devices in the IoT dependency graph perform network communications; and
transmit, by the server-layer device to the single edge device, the IoT dependency graph to the single edge device, wherein the single edge device transmits, to at least one IoT device, at least one command for the at least one IoT device to perform the at least one IoT event.
16. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, from a respective IoT device of the at least one IoT device, an IoT event confirmation; and
update an IoT graph sequence of the IoT dependency graph based on the IoT event confirmation.
17. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
retrieve, from an IoT knowledge structure, instructions to perform the at least one IoT event; and
generate, based on the instructions, the at least one command for the at least one IoT device to perform the at least one IoT event.
18. The non-transitory computer-readable medium of claim 15 , wherein the IoT dependency graph comprises a directed acyclic graph.
19. The non-transitory computer-readable medium of claim 15 , wherein the IoT dependency graph specifies, for at least one event of a plurality of events of the IoT dependency graph: an event identifier, an IoT device identifier, an edge device identifier, and a parent event identifier.
20. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
determine that a second IoT dependency graph is unevaluable at the edge layer based on the second IoT dependency graph specifying a second plurality of IoT devices that are connected to a plurality of different edge devices; and
store the second IoT dependency graph at the server layer for server layer evaluation based on the IoT dependency graph being unevaluable at the edge layer.