Microsoft Technology Licensing, LLC

Affan Arshad Dar

Konstantin Dotchkoff

Elio Damaggio

Samuel John George

Cameron William Skinner

Juan J Perez

Nicole Elaine Berdy

Sanjib Saha

Arjmand Samuel

Michael Richard Yagley

Simon Porter

Varun Puranik

Ian Vaughan Hollier

Xin Chen

Ajith Kumar Gande

Ritesh Rao

Anca Mihaela Antochi

Manohar Bangalore Puttaswamaiah

Nicholas Alexander Allen

Muralidhar Krishnaprasad

John Anthony Taylor

James Ernest Johnson

Kartik Paramasivam

Balendran Mugundan

Rajeev Mandayam Vokkarne

Pramod Gurunath

Chipalo Street

Vaibhav Sharma

Samar Abbas

Kapil Agarwal

Edward John Triou, Jr

Anush Prabhu Ramachandran

Murali Krishnaprasad

Raimundo Robledo Pontes Filho

Andre Milbradt

Osarumwemse U Agbonile

Nicole E Berdy

Sudeep Satish Pradhan

Roopesh Kumar Manda

Jayu Katti

In one example of the technology, a first third-party service is registered with the IoT support service. A first IoT device of a plurality of IoT devices is caused to be provisioned with the IoT support service. An authentication is received token for the first IoT device. The authentication token is based on an authentication of the first IoT device with the first third-party service. The authentication token is verified. The first IoT device is authenticated with the IoT support service based on the verification.

Single sign-in for IoT devices

The disclosed technology is generally directed to communications in an IoT environment. In one example of the technology, a plurality of module twins that respectively correspond to a plurality of modules of edge applications on a plurality of edge devices are stored. The plurality of module twins individually include metadata associated with the corresponding module of the plurality of modules. At least one module of the plurality of modules to be modified by adding a declarative rule is determined, such that the declarative rule causes determining whether an event has been triggered based on a particular event having been determined to have occurred, and, in response to the triggering of the event, communicating the triggering of the event to at least one declarative target. The determined at least one module of the plurality of modules is caused to be modified by adding the declarative rule.

Distribution of events in edge devices

Described herein is a device (e.g., IoT device) having bootstrap code that communicates with a secure global registry (e.g., private distributed shared blockchain database). The bootstrap code of the device uses a globally unique device identifier of the device to the secure global registry. The bootstrap code receives information from the secure global registry which the bootstrap code uses to obtain information to connect to a cloud-based endpoint. The bootstrap code can download an appropriate software development kit (SDK) associated with the particular cloud based, at least in part, upon the received information. The device can be registered in the secure global registry by creating a globally unique identifier for the device. An initial entry can be created in the secure global registry comprising the globally unique identifier, with the secure global registry stores current cloud-based endpoint information, if any, for the device.

Discovery and matching of internet of things (IoT) devices and services using a secure global registry

The disclosed technology is generally directed to communications in an IoT environment. In one example of the technology, device twins for corresponding IoT devices are stored, wherein the device twins include metadata that is associated with the corresponding IoT devices. A schedule job instruction may be received, and at least one candidate IoT device among the IoT devices that is associated with the schedule job instruction may be identified. In some examples, executors associated with the at least one candidate IoT device are created, and jobs are executed via the executors such that the executors are capable of resuming execution after at least one of an outage or a failure.

IoT device jobs

A plurality of module twins that respectively correspond to modules of a plurality of modules of an edge application are stored on an edge device, and the modules comprise the edge application. The modules of the plurality of modules are capable of being used interoperably with other modules without altering the other modules. The plurality of module twins individually include metadata associated with the corresponding module of the plurality of modules. Communications are enabled between the modules of the plurality of modules and the IoT support service according to a common security context, and the metadata of each module twin of the plurality of module twins is synchronized based on the module.

Creation of modular applications with corresponding twins in the cloud

A plurality of module twins that respectively correspond to a plurality of modules of edge applications on a plurality of edge devices are stored. The plurality of module twins individually include metadata associated with the corresponding module of the plurality of modules. At least one further module to be deployed is determined. Edge devices of the plurality of edge devices to receive the determined at least one module are identified. The determined at least one further module is caused to be deployed to the identified edge devices. In response to deploying the determined at least one further module, the plurality of module twins is updated by adding, to the plurality of modules twins, modules twins corresponding to the deployed modules.

Deployment of modular applications from the cloud to local devices

In one example of the technology, a mapping is established between: IoT devices that are tenants of an IoT support service, and tenants of a first third-party cloud service. On the IoT support service, device twins are stored, such that each device twin corresponds to a corresponding IoT device, and such that each device twins includes at least a first section that includes properties of the corresponding IoT device, and a second section that includes properties associated with the first third-party cloud service. The IoT support service is used to invoke a first method associated with at least one IoT device based on metadata in at least one corresponding device twin. The first method is associated with the first third-party cloud service.

IoT cloud to cloud architecture

A method for uniquely authenticating a device provides for receiving a scoping request, allocating a scope ID responsive to the request, and storing one or more device identification credentials in a database. Each device identification credential stored in the database includes the allocated scope ID and a device ID provided within the scoping request. The method further provides for receiving a registration request specifying a device identification credential and authenticating the specified device identification credential by confirming a match between the specified device identification credential and one of the device identification credentials stored in the database. The method further provides for provisioning the device with initial configuration information responsive to the authentication.

Scoping mechanism for globally unique device identification

The disclosed technology is generally directed to device provisioning in an IoT environment. For example, such technology is usable in provisioning IoT devices to an IoT Hub. In one example of the technology, an identification message that includes information associated with identification of a first IoT device is received. The validity of the first IoT device is then verified. After the first IoT device is verified, based at least in part on the identification message, an IoT hub is selected from a plurality of IoT hubs. The first IoT device is then caused to be registered with the selected IoT hub.

IoT provisioning service

The disclosed technology is generally directed to IoT communications. For example, such technology is usable in provisioning IoT devices in an automatic manner with no manual steps. In one example of the technology, upon initial boot, identification information is automatically sent to a provisioning service endpoint stored in the IoT device. The identification information includes an identification (ID) of the first IoT device. Cryptographic information is received from the provisioning service. The cryptographic information is associated with an IoT hub selected from a plurality of IoT hubs based, in part, on the ID of the first IoT device. A message is automatically sent to the IoT hub in response to receiving the cryptographic information. A new configuration file and a firmware update are received from the IoT hub without requiring a user association. The new configuration file and the firmware update are automatically installed.

Automatic provisioning of IoT devices

In one example of the technology, a first third-party service is registered with the IoT support service. A first IoT device of a plurality of IoT devices is caused to be provisioned with the IoT support service. An authentication token is received for the first IoT device. The authentication token is based on an authentication of the first IoT device with the first third-party service. The authentication token is verified. The first IoT device is authenticated with the IoT support service based on the verification.

The disclosed technology is generally directed to communications in an IoT environment. In one example of the technology, module twins that respectively correspond to modules of edge applications on a plurality of edge devices are stored. The module twins individually include metadata associated with the corresponding module. Communications between the modules and the IoT support service according to a common security context is enabled. At least one module to be modified is determined. The determined at least one module is caused to be modified.

Cloud modification of modular applications running on local devices

Multiple geo-replicated and independent IoT (Internet of Things) hubs configured as servers with storage capacities are utilized and span across various regions in the world, to each of which IoT devices can connect and transmit telemetry data. The IoT devices, configured with sensors to generate telemetry data (e.g., temperature, pressure, etc.), can fail over to another geo-replicated IoT hub (the 'target geo-replicated IoT hub') when one IoT hub experiences technical failures or the IoT device changes location to a region which is covered by the target IoT hub. Upon receiving a connection request from the IoT device, the target geo-replicated IoT hub submits a proposal to available geo-replicated IoT hubs for ownership over the IoT device, that is, receive data from and transmit messages to the IoT device. A quorum is sought so that all IoT hubs are in agreement as to a current owner of the IoT device.

Geo-replicated IoT hub

Growing community of inventors

Redmond, WA, United States of America

Affan Arshad Dar