Distributed framework for resilient machine-to-machine system management
US-2018375720-A1 · Dec 27, 2018 · US
US12015499B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12015499-B2 |
| Application number | US-202217702264-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 23, 2022 |
| Priority date | Feb 5, 2017 |
| Publication date | Jun 18, 2024 |
| Grant date | Jun 18, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An Internet of Things (IoT) system that includes an orchestration device is provided. The orchestration device receives resource requirements and accesses a device/capability map to produce a task deployment map.
Opening claim text (preview).
What is claimed is: 1. An orchestration device to orchestrate an Internet of Things (IoT) network, comprising: a processor; a memory device including instructions, which when executed by the processor, cause the processor to: receive resource requirements for an application to execute on a first plurality of devices in the IoT network; access a capability graph of a second plurality of devices in the IoT network; identify a container deployment plan, based on the capability graph, that satisfies the resource requirements; and communicate with one of the second plurality of devices in the IoT network to deploy containers based on the container deployment plan. 2. The orchestration device of claim 1 , wherein the capability graph comprises attributes and capabilities of a device of the second plurality of devices. 3. The orchestration device of claim 1 , wherein the instructions cause the processor to obtain current device state and metrics from a device. 4. The orchestration device of claim 3 , wherein the instructions cause the processor to provide the current device state and metrics for the device to the capability graph. 5. The orchestration device of claim 1 , comprising a container repository comprising containerized tasks. 6. The orchestration device of claim 1 , comprising instructions, which cause the processor to identify a device and its capabilities, during onboarding, and incorporate the device and its capabilities into the capability graph. 7. The orchestration device of claim 1 , wherein a device of the first plurality of devices includes a containerized task to implement a portion of the application. 8. A method for orchestrating an Internet of Things (IoT) network, comprising: receiving, at an orchestration device, resource requirements for an application to execute on a first plurality of devices in the IoT network; accessing a capability graph of a second plurality of devices in the IoT network; identifying a container deployment plan, based on the capability graph, that satisfies the resource requirements; and communicating with one of the second plurality of devices in the IoT network to deploy containers based on the container deployment plan. 9. The method of claim 8 , wherein the capability graph comprises attributes and capabilities of a device of the second plurality of devices. 10. The method of claim 8 , comprising obtaining current device state and metrics from a device. 11. The method of claim 10 , comprising providing the current device state and metrics for the device to the capability graph. 12. The method of claim 8 , wherein the orchestration device comprises a container repository comprising containerized tasks. 13. The method of claim 8 , comprising identifying a device and its capabilities, during onboarding, and incorporating the device and its capabilities into the capability graph. 14. The method of claim 8 , wherein a device of the first plurality of devices includes a containerized task to implement a portion of the application. 15. At least one non-transitory machine-readable medium including instructions for orchestrating a mesh an Internet of Things (IoT) network, which when executed by an orchestrator device, cause the orchestrator device to: receive resource requirements for an application to execute on a first plurality of devices in the IoT network; access a capability map of a second plurality of devices in the IoT network; identify a container deployment plan, based on the capability map, that satisfies the resource requirements; and communicate with one of the second plurality of devices in the IoT network to coordinate deployment of containers based on the container deployment plan. 16. The non-transitory machine-readable medium of claim 15 , wherein the capability map comprises attributes and capabilities of a device of the second plurality of devices. 17. The non-transitory machine-readable medium of claim 15 , wherein the instructions cause the orchestrator device to access current device state and metrics from a device. 18. The non-transitory machine-readable medium of claim 17 , wherein the instructions cause the orchestrator device to provide the current device state and metrics for the device to the capability map. 19. The non-transitory machine-readable medium of claim 15 , wherein the orchestration device comprises a container repository comprising containerized tasks. 20. The non-transitory machine-readable medium of claim 15 , comprising instructions, which cause the orchestrator device to identify a device and its capabilities, during onboarding, and incorporate the device and its capabilities into the capability map. 21. The non-transitory machine-readable medium of claim 15 , wherein a device of the first plurality of devices includes a containerized task to implement a portion of the application.
Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) · CPC title
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
involving control of end-device applications over a network · CPC title
indicating a format for calling an appliance service function in a home automation network (for remote control or remote monitoring of applications H04L67/025) · CPC title
Partitioning or combining of resources · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.