IP Library Granted Patent US 11,334,336
Granted Patent B2
US 11,334,336 · App. 16/249,077 · Granted May 17, 2022

Automatic creation of device campaigns

Inventors: Sabo Rusev (Sofia, BG); Militsa Borisova (Sofia, BG); Ivo Petkov (Sofia, BG); Dobromir Ivanov (Sofia, BG); Ilya Mayorski (Sofia, BG)
Assignee: VMware, Inc.
G06F8/65H04L9/3268H04L67/12H04L67/34
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 11,334,336
App. No.
16/249,077
Granted
May 17, 2022
Kind
B2
Abstract

Approaches for automatically creating device campaigns are disclosed herein. A computing device first determines that a second version of a software package assigned to an existing device campaign has been uploaded to a data store. The existing device campaign can include an existing compliance policy applicable to individual IoT endpoints assigned to the existing device campaign. The compliance policy may specify that a first version of the software package be installed on the individual IoT endpoints. In response, to the change, the computing device can create a new device campaign that includes a new compliance policy applicable to the individual IoT endpoints assigned to the new device campaign. The new compliance policy may specify that the second version of the software package be assigned to the individual IoT endpoints.

Claims (52)

1. A system, comprising:

a computing device comprising a processor and a memory;

machine readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:

determine that a second version of a software package assigned to an existing device campaign has been uploaded to a data store, the existing device campaign comprising an existing compliance policy applicable to individual IoT endpoints assigned to the existing device campaign, the compliance policy specifying that a first version of the software package be installed on the individual IoT endpoints; and

create a new device campaign comprising a new compliance policy applicable to the individual IoT endpoints assigned to the new device campaign, the new compliance policy specifying that the second version of the software package be assigned to the individual IoT endpoints, wherein the new device campaign is created by creating a copy of the existing device campaign created to install the first version of the software package on the individual IoT endpoints, replace a first policy identifier included in the existing device campaign with a second policy identifier associated with new compliance policy in the copy of the existing device campaign, wherein the second policy identifier specifies the second version of the software package.

2. The system of claim 1 , wherein the machine readable instructions that cause the computing device to determine that the second version of the software package has been uploaded to the data store further cause the computing device to at least:

determine that a first checksum of the first version of the software package differs from a second checksum of the second version of the software package.

3. The system of claim 1 , wherein the machine readable instructions that cause the computing device to determine that the second version of the software package has been uploaded to the data store further cause the computing device to at least:

compare a first version identifier included in a first set of metadata associated with the first version of the software package with a second version identifier included in a second set of metadata associated with the second version of the software package.

4. The system of claim 1 , wherein the machine readable instructions that cause the computing device to determine that the second version of the software package has been uploaded to the data store further cause the computing device to at least:

identify a version indicator submitted with the second version of the software package; and

determine that the version indicator specifies that the second version of the software package is a newer version than the first version of the software package.

5. The system of claim 1 , wherein the machine readable instructions that cause the computing device to create the new device campaign further cause the computing device to at least:

create a copy of the existing device campaign;

create the new compliance policy specifying that the second version of the software package be assigned to the individual IoT endpoints;

replace the existing compliance policy specified in the copy of the existing device campaign with the new compliance policy; and

save the copy of the existing device campaign as the new device campaign.

6. The system of claim 1 , wherein the software package comprises an installer for a binary application executable by the individual IoT endpoints.

7. The system of claim 1 , wherein the software package comprises an installer for a firmware for the individual IoT endpoints.

8. A method, comprising:

determining that a second version of a software package assigned to an existing device campaign has been uploaded to a data store, the existing device campaign comprising an existing compliance policy applicable to individual IoT endpoints assigned to the existing device campaign, the compliance policy specifying that a first version of the software package be installed on the individual IoT endpoints; and

creating a new device campaign comprising a new compliance policy applicable to the individual IoT endpoints assigned to the new device campaign, the new compliance policy specifying that the second version of the software package be assigned to the individual IoT endpoints, wherein the new device campaign is created by creating a copy of the existing device campaign created to install the first version of the software package on the individual IoT endpoints, replace a first policy identifier included in the existing device campaign with a second policy identifier associated with new compliance policy in the copy of the existing device campaign, wherein the second policy identifier specifies the second version of the software package.

9. The method of claim 8 , wherein determining that the second version of the software package has been uploaded to the data store further comprises:

determining that a first checksum of the first version of the software package differs from a second checksum of the second version of the software package.

10. The method of claim 8 , wherein determining that the second version of the software package has been uploaded to the data store further comprises:

comparing a first version identifier included in a first set of metadata associated with the first version of the software package with a second version identifier included in a second set of metadata associated with the second version of the software package.

11. The method of claim 8 , wherein determining that the second version of the software package has been uploaded to the data store further comprises:

identifying a version indicator submitted with the second version of the software package; and

determining that the version indicator specifies that the second version of the software package is a newer version than the first version of the software package.

12. The method of claim 8 , wherein creating the new device campaign further comprises:

creating a copy of the existing device campaign;

creating the new compliance policy specifying that the second version of the software package be assigned to the individual IoT endpoints;

replacing the existing compliance policy specified in the copy of the existing device campaign with the new compliance policy; and

saving the copy of the existing device campaign as the new device campaign.

13. The method of claim 8 , wherein the software package comprises an installer for a binary application executable by the individual IoT endpoints.

14. The method of claim 8 , wherein the software package comprises an installer for a firmware for the individual IoT endpoints.

15. A non-transitory, computer-readable medium, comprising machine readable instructions that, when executed by a processor, cause a computing device to at least:

determine that a second version of a software package assigned to an existing device campaign has been uploaded to a data store, the existing device campaign comprising an existing compliance policy applicable to individual IoT endpoints assigned to the existing device campaign, the compliance policy specifying that a first version of the software package be installed on the individual IoT endpoints; and

create a new device campaign comprising a new compliance policy applicable to the individual IoT endpoints assigned to the new device campaign, the new compliance policy specifying that the second version of the software package be assigned to the individual IoT endpoints, wherein the new device campaign is created by creating a copy of the existing device campaign created to install the first version of the software package on the individual IoT endpoints, replace a first policy identifier included in the existing device campaign with a second policy identifier associated with new compliance policy in the copy of the existing device campaign, wherein the second policy identifier specifies the second version of the software package.

16. The non-transitory, computer-readable medium of claim 15 , wherein the machine readable instructions that cause the computing device to determine that the second version of the software package has been uploaded to the data store further cause the computing device to at least:

determine that a first checksum of the first version of the software package differs from a second checksum of the second version of the software package.

17. The non-transitory, computer-readable medium of claim 15 , wherein the machine readable instructions that cause the computing device to determine that the second version of the software package has been uploaded to the data store further cause the computing device to at least:

compare a first version identifier included in a first set of metadata associated with the first version of the software package with a second version identifier included in a second set of metadata associated with the second version of the software package.

18. The non-transitory, computer-readable medium of claim 15 , wherein the machine readable instructions that cause the computing device to determine that the second version of the software package has been uploaded to the data store further cause the computing device to at least:

identify a version indicator submitted with the second version of the software package; and

determine that the version indicator specifies that the second version of the software package is a newer version than the first version of the software package.

19. The non-transitory, computer-readable medium of claim 15 , wherein the machine readable instructions that cause the computing device to create the new device campaign further cause the computing device to at least:

create a copy of the existing device campaign;

create the new compliance policy specifying that the second version of the software package be assigned to the individual IoT endpoints;

replace the existing compliance policy specified in the copy of the existing device campaign with the new compliance policy; and

save the copy of the existing device campaign as the new device campaign.

20. The non-transitory, computer-readable medium of claim 15 , wherein the software package comprises an installer for a binary application executable by the individual IoT endpoints or for a firmware for individual IoT endpoints.

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 067102/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2019
From: RUSEV, SABO; BORISOVA, MILITSA; PETKOV, IVO; IVANOV, DOBROMIR; MAYORSKI, ILYA
To: VMWARE, INC.
Reel/Frame 048218/0399 →