Disclosed are various embodiments for the controlling the amount of active updates that can occur during a given time on devices that are associated with tenants (e.g., organizations) and subtenants (e.g., sub-organizations) in a multi-tenant environment. In particular, each tenant and subtenant is assigned throttle corresponding to different update parameters (e.g., an amount of devices executing an active update, an amount of data to be downloaded during a campaign, a time for completing the update campaign, etc.). When an update campaign is established, the update campaign can define the different devices that are to be updated. In some situations, the number of active updates required may exceed the allotted resources for a given subtenant. When a subtenant requires additional resources than what is assigned to complete the update, the subtenant can borrow resources defined by the update parameters from a subtenant peer that has a surplus.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A system for redistributing resources between suborganizations during an update campaign, the system comprising: at least one computing device; and at least one application executable on the at least one computing device, wherein, when executed, the at least one application causes the at least one computing device to at least: initiate an update campaign for a first organization, wherein the update campaign is associated with a configurable throttle limit for one or more update resources of the update campaign; identify a number of Internet of Things (IoT) devices in a first organization associated with the update campaign; determine that the update resources to execute the update campaign exceed the configurable throttle limit for the first organization based at least in part on the update campaign and the number of IoT devices; identify a second organization that is a lower priority than the first organization; allocate a surplus of the update resources from the second organization to the first organization; and execute the update campaign for the first organization based at least in part on the allocated surplus of the update resources.
2. The system of claim 1, wherein the first organization and the second organization are sub-organizations of an enterprise organization.
3. The system of claim 2, wherein the enterprise organization is allotted a predefined number of update resources, and the first organization and the second organization are allotted a subset of the predefined number of update resources.
4. The system of claim 1, wherein the update resources to execute the update campaign correspond to update parameters defining at least one of: an amount of data to be downloaded during the updated campaign or a time for completing the update campaign.
5. The system of claim 1, wherein the number of IoT devices are determined based at least in part on a distribution list included in the update campaign.
6. The system of claim 1, when executed, the at least one application further causes the at least one computing device to at least determine that the second organization has the surplus of the update resources, the second organization being identified based at least in part on the surplus.
7. The system of claim 6, wherein allocating the surplus resources from the second organization to the first organization comprises: increasing the configurable throttle limit associated with the first organization by the surplus associated with the second organization.
8. A method for redistributing resources between suborganizations during an update campaign, comprising: initiating an update campaign for a first organization, wherein the update campaign is associated with a configurable throttle limit for one or more update resources of the update campaign; identifying, by at least one computing device, a number of Internet of Things (IoT) devices in a first organization associated with the update campaign; determining, by the at least one computing device, that the update resources to execute the update campaign exceed the configurable throttle limit for the first organization based at least in part on the update campaign and the number of IoT devices; identifying, by the at least one computing device, a second organization that is a lower priority than the first organization; allocating, by the at least one computing device, a surplus of the update resources from the second organization to the first organization; and executing, by the at least one computing device, the update campaign for the first organization based at least in part on the allocated surplus of the update resources.
9. The method of claim 8, wherein the first organization and the second organization are sub-organizations of an enterprise organization.
10. The method of claim 9, wherein the enterprise organization is allotted a predefined number of update resources, and the first organization and the second organization are allotted a subset of the predefined number of update resources.
11. The method of claim 10, wherein the update resources to execute the update campaign correspond to update parameters defining at least one of: an amount of data to be downloaded during the updated campaign or a time for completing the update campaign.
12. The method of claim 8, wherein the number of IoT devices are determined based at least in part on a distribution list included in the update campaign.
13. The method of claim 8, further comprising determining that the second organization has the surplus of the update resources, the second organization being identified based at least in part on the surplus.
14. The method of claim 13, wherein allocating the surplus of the update resources from the second organization to the first organization comprises: increasing the configurable throttle limit associated with the first organization by the surplus associated with the second organization.
15. A non-transitory, computer-readable medium embodying a program for redistributing resources between sub-organizations during an update campaign, wherein when executed by a computing device, the program causes the computing device to at least: initiate an update campaign for a first organization, wherein the update campaign is associated with a configurable throttle limit for one or more update resources of the update campaign; identify a number of Internet of Things (IoT) devices in a first organization associated with the update campaign; determine that the update resources to execute the update campaign exceed the configurable throttle limit for the first organization based at least in part on the update campaign and the number of IoT devices; identify a second organization that is a lower priority than the first organization; allocate a surplus of the update resources from the second organization to the first organization; and execute the update campaign for the first organization based at least in part on the allocated surplus of the update resources.
16. The non-transitory, computer-readable medium of claim 15, wherein the first organization and the second organization are sub-organizations of an enterprise organization.
17. The non-transitory, computer-readable medium of claim 16, wherein the enterprise organization is allotted a predefined number of update resources, and the first organization and the second organization are allotted a subset of the predefined number of update resources.
18. The non-transitory, computer-readable medium of claim 15, wherein the number of IoT devices are determined based at least in part on a distribution list included in the update campaign.
19. The non-transitory, computer-readable medium of claim 15, when executed, the program further causes the at least one computing device to at least determine that the second organization has the surplus of the update resources, the second organization being identified based at least in part on the surplus, and wherein allocating the surplus of the update resources from the second organization to the first organization comprises increasing the configurable throttle limit associated with the first organization by the surplus associated with the second organization.
20. The non-transitory, computer-readable medium of claim 15, wherein the update resources to execute the update campaign correspond to update parameters defining at least one of: an amount of data to be downloaded during the updated campaign or a time for completing the update campaign.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
January 18, 2022
March 11, 2025
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.