Microsoft Technology Licensing, LLC

Madhavan Kesavan

Arun Ramadasan Mannengal

Tanmay Dileep Bhagwat

Zhenyu Guo

Hanumantha Rao Kommalapati

Kun Cong

Brian Robert Crawford

Ritesh Rao

Christopher Samuel Green

Harini Avula

Ravi Kumar Reddy Yellasiri

Constraint based command invocations are dynamically queued in a cloud queue such that aspects of remote user devices may be remotely controlled with reduced exposure to inconvenient remotely issued commands. By monitoring conditions that may trigger command invocations, verifying rules of associated constraints prior to queuing command invocations, evaluating parameters to prioritize command invocations in a dynamic issuing order within cloud queue, examining factors and reverifying previously verified rules when determining whether to transmit a command from an command invocation located at a transmission position of the cloud queue, systems and methods herein provide a constrained environment within which user devices may be remotely controlled relatively free from unexpected cloud caused encumbrances during inopportune moments.

Intellegent queuing of rules based command invocations

The pre-configuring of a set of cloud endpoints to connect to a device in response to receiving a request that cloud endpoints be pre-configured for connection to the device. The request is used to identify the set of cloud endpoints that is to be so pre-configured. Then, a pre-configuration instruction is formulated that is structured to be interpretable by each cloud endpoint to establish device-specific connection configuration that is specific to the device. Furthermore, the pre-configuration is structured to assist the respective cloud endpoint to establish a connection with the device upon request of the device. The pre-configuration instruction is then sent to each cloud endpoint in the set of cloud endpoints, causing the pre-configuration to occur. Thus, subsequent connection to the device is more efficient.

Device-specific pre-configuration of cloud endpoints

The device capability model (DCM) sharing system disclosed herein includes one or more computer implemented instructions including receiving a request from a device for access to the DCM, generating a request to a token issuing authority to request a device identification token; evaluating the device identification token to determine the device's DCM access level; communicating the device identification token with the device's capability model access level to a DCM repository; receiving the DCM from the DCM repository; and providing the device an access to the DCM.

Device capability model sharing

One disclosed example provides, enacted on a computing system, a method of resolving a device capability model (DCM) for a network connected device, the method comprising receiving, from the network connected device, an identifier of the DCM, based on the identifier received, determining whether the DCM is stored on the computing system, when the DCM is stored on the computing system, then retrieving the DCM from the computing system, when the DCM is not stored on the computing system, then retrieving the DCM from one or more of the network connected device and a DCM repository and storing the DCM on the computing system, receiving, from a software solution, an application programming interface (API) call to retrieve the DCM from the computing system, and in response to receiving the API call, returning the DCM to the software solution.

Discovery and resolution of network connected devices

A computing system includes a logic subsystem and memory storing instructions executable by the logic subsystem. The instructions are executable by the logic subsystem to store, in the memory, a plurality of software models that each describe aspects of a network connected device or a software service, the plurality of software models comprising a first version of a selected software model. The logic subsystem is configured to receive a second version of the selected software model and validate the second version of the selected software model via validation logic by applying one or more versioning rules to the second version of the selected software model. Based on the application of the one or more versioning rules, the logic subsystem is configured to execute a versioning action on the selected software model.

Growing community of inventors

Redmond, WA, United States of America

Madhavan Kesavan