Vmware, Inc.

Omnissa, LLC

Dobromir Ivanov

Ivo Petkov

Sabo Rusev

Militsa Borisova

Ilya Mayorski

Miroslav Mitevski

Nikola Atanasov

Stanislav Asenov Hadjiiski

Kristiyan Yankov

Sonya Ivanova Tsolova

Militsa Arnaudova

Disclosed are various embodiments for automatic enrollment of Internet of Things (IoT) endpoints. An identity of an IoT endpoint is verified by an IoT gateway. The IoT gateway is configured to transmit, over a network, an enrollment request to an IoT management service. The enrollment of the IoT endpoint with the IoT management service is confirmed. A compliance policy for the IoT endpoint is retrieved from a command queue. The compliance policy is stored in the command queue until retrieved by the IoT gateway. The IoT gateway enforces the compliance policy on the IoT endpoint.

Policy-based auto-enrollment of devices in ota campaigns

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.

Multitenancy hierarchical update campaigns

Examples of generating a result set from a data lake based upon a real-time data set are described. A data lake can be structured across multiple databases or tables that are not necessarily directly linked to one another. A conjunction schema can specify how data can be queried across the data lake. When an incoming real-time data set is obtained, a multi-query can be generated against the data lake by utilizing the conjunction schema.

Connecting real-time data sets to historical data

Disclosed are various embodiments for updating IoT endpoints. A software update package can be deployed to a IoT gateway. The software package can have lifecycle scripts and software executable for installation on IoT endpoints. The lifecycle scripts represent different lifecycle phases of the update process.

Deploying device campaign updates to IoT devices

Managing the creation and execution of update campaigns in an multitenancy hierarchy

Disclosed are various embodiments for automatically creating device campaigns. 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.

Automatic creation of device campaigns

Disclosed are various embodiments for automatic enrollment of Internet of Things (IoT) endpoints. An enrollment request is received from an internet of things (IoT) gateway, the enrollment request comprising an identifier for an IoT endpoint and at least one property of the IoT endpoint. In response to enrollment of the IoT endpoint, a campaign template is identified that matches the at least one property of the IoT endpoint. A campaign associated with the campaign template is then identified, the campaign comprising a collection of policies that are applicable to individual IoT endpoints assigned to the campaign. Subsequently, the IoT endpoint is assigned to the campaign.

Auto-enrollment of IoT endpoints

Disclosed are various embodiments for the automatic generation of configurations for Internet of Things (IoT) endpoints. At least one metric is collected for an Internet of Things (IoT) endpoint. Then, a function that generates configuration data for the IoT endpoint is invoked. In some instances, the at least one metric is supplied as an argument for the IoT endpoint. The configuration data is received as a result of the function. A device campaign is then created to apply the configuration data to the IoT endpoint. The IoT endpoint can then be assigned to the device campaign.

Automatic generation of configurations for IoT endpoints

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.

Growing community of inventors

Sofia, Bulgaria

Dobromir Ivanov