# US 2021/0173727 A1 · Multitenancy hierarchical update campaigns

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0173727 A1
- Document ID: US20210173727A1
- Status: Published application
- Kind: A1
- Application number: 16/702,768
- Filed: 2019-12-04
- Published: 2021-06-10
- Earliest claimed: 2019-12-04
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Sabo Rusev; Ivo Petkov; Militsa Borisova; Ilya Mayorski; Dobromir Ivanov
- Web page: https://patentgrep.com/patent/US20210173727A1

## CPC

- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/62: Establishing a time schedule for servicing the requests
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed are various embodiments for separating creation of and executing of updated campaigns in multitenancy environments. For example, an organization can have a hierarchical structure such that a root organization includes multiple sub-organizations. A root organization administrator may create an update campaign for enforcing software policies on devices that are included in the sub-organizations. A sub-organization administrator can approve and define the execution schedule for when the devices included in the sub-organization can execute the update campaign.

## Claims

### Claim 1

A system for separating creation and execution of update campaigns, 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:
create an update campaign to update a plurality of devices in a root organization;
receive a request to review an update campaign status for the update campaign from an administrator of a sub-organization of the root organization;
display a read-only view of an update campaign configuration of the update campaign;
receive an execution schedule for executing the update campaign by the devices included in the sub-organization; and
initiate an execution of the update campaign for the devices in the sub-organization during a timeframe defined by the execution schedule.

### Claim 2 (depends on 1)

The system of claim 1, wherein the update campaign comprises a software package and a distribution list defining the devices in the root organization that are subject to the update campaign.

### Claim 3 (depends on 2)

The system of claim 2, wherein the devices in the distribution list belong to a plurality of different sub-organizations in the root organization, and execution of the update campaign for the devices being based on a respective execution schedule for the different sub-organizations in the root organization.

### Claim 4 (depends on 2)

The system of claim 2, wherein:
when executed, the at least one application further causes the at least one computing device to at least receive user inputs defining at least one parameters of the update campaign, the at least one parameter including at least one of: a distribution list criteria for defining the distribution list or a selection of the software package; and
the user inputs are associated with a root administrator for the root organization.

### Claim 5 (depends on 2)

The system of claim 2, wherein the distribution list and the software package of the update campaign are modifiable by a root administrator of the root organization.

### Claim 6 (depends on 1)

The system of claim 1, wherein the sub-organization is a first sub-organization of the root organization, the execution schedule comprises a first execution schedule, and when executed, the at least one application further causes the at least one computing device to at least receive a second execution schedule for executing the update campaign by the devices included in a second sub-organization, the second execution schedule being different from the execution schedule of the first sub-organization.

### Claim 7 (depends on 1)

The system of claim 1, wherein, when executed, the at least one application further causes the at least one computing device to at least:
enable an execution setting of the update campaign for the devices included in the sub-organization; and
initiating the execution of the update campaign comprises writing the update campaign to a command queue associated with the devices included in the sub-organization.

### Claim 8

A method for separating creation and execution of update campaigns, comprising:
creating, by a computing device, an update campaign to update a plurality of devices in a root organization;
receiving, by the computing device, a request to review an update campaign status for the update campaign from an administrator of a sub-organization of the root organization;
displaying, by the computing device, a read-only view of an update campaign configuration of the update campaign;
receiving, by the computing device, an execution schedule for executing the update campaign by the devices included in the sub-organization; and
initiating, by the computing device, an execution of the update campaign for the devices in the sub-organization during a timeframe defined by the execution schedule.

### Claim 9 (depends on 8)

The method of claim 8, wherein the update campaign comprises a software package and a distribution list defining the devices in the root organization that are subject to the update campaign.

### Claim 10 (depends on 9)

The method of claim 9, wherein the devices in the distribution list belong to a plurality of different sub-organizations in the root organization, and execution of the update campaign for the devices being based on a respective execution schedule for the different sub-organizations in the root organization.

### Claim 11 (depends on 9)

The method of claim 9, further comprising:
receiving user inputs defining at least one parameters of the update campaign, the at least one parameter including at least one of: a distribution list criteria for defining the distribution list or a selection of the software package, and
wherein the user inputs are associated with a root administrator for the root organization.

### Claim 12 (depends on 9)

The method of claim 9, wherein the distribution list and the software package of the update campaign are modifiable by a root administrator of the root organization.

### Claim 13 (depends on 8)

The method of claim 8, wherein the sub-organization is a first sub-organization of the root organization, the execution schedule comprises a first execution schedule, further comprising receiving a second execution schedule for executing the update campaign by the devices included in a second sub-organization, the second execution schedule being different from the execution schedule of the first sub-organization.

### Claim 14 (depends on 8)

The method of claim 8, further comprising:
enabling an execution setting of the update campaign for the devices included in the sub-organization; and
wherein initiating the execution of the update campaign comprises writing the update campaign to a command queue associated with the devices included in the sub-organization.

### Claim 15

A non-transitory, computer-readable medium embodying a program for separating creation and execution of update campaigns, wherein when executed by a computing device, the program causes the computing device to at least:
create an update campaign for updating a plurality of devices in a root organization;
receive a request to review an update campaign status for the update campaign from an administrator of a sub-organization of the root organization;
display a read-only view of an update campaign configuration of the update campaign;
receive an execution schedule for executing the update campaign by devices included in the sub-organization; and
initiate an execution of the update campaign for devices in the sub-organization during a timeframe defined by the execution schedule.

### Claim 16 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the update campaign comprises a software package and a distribution list defining devices in the root organization that are subject to the update campaign.

### Claim 17 (depends on 16)

The non-transitory, computer-readable medium of claim 16, wherein the devices in the distribution list belong to a plurality of different sub-organizations in the root organization, and execution of the update campaign for the devices being based on a respective execution schedule for the different sub-organizations in the root organization.

### Claim 18 (depends on 16)

The non-transitory, computer-readable medium of claim 16, wherein:
when executed, the program further causes the computing device to at least receive user inputs defining at least one parameters of the update campaign, the at least one parameter including at least one of: a distribution list criteria for defining the distribution list or a selection of the software package, and
the user inputs are associated with a root administrator for the root organization.

### Claim 19 (depends on 16)

The non-transitory, computer-readable medium of claim 16, wherein the distribution list and the software package of the update campaign are modifiable modified by a root administrator of the root organization.

### Claim 20 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein, when executed, the program further causes the computing device to at least:
enable an execution setting of the update campaign for the devices included in the sub-organization; and
initiating the execution of the update campaign comprises writing the update campaign to a command queue associated with the devices included in the sub-organization.
