Contextually aware device management

• US 9,288,235 B1
• Filed: 09/17/2014
• Issued: 03/15/2016
• Est. Priority Date: 09/17/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Kaufman, Peter J., Hou, Justin A., Novales, Javier, Kartaltepe, Erhan J., Spaith, John C.
• Primary Examiner(s): Zaidi, Syed
• Application Number:
  US14/489,339
• Publication Number:
  US 20160080421A1
• Time in Patent Office: 545 Days
• Field of Search: 726/1
• US Class Current: 1/1
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 2221/2129 Authenticate client device independently of the user
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/085 Retrieval of network configuration; Tracking network configuration history
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04M 1/72454 according to context-related or environment-related conditions
• CPC Class Codes: H04W 12/37 Managing security policies for mobile devices or for controlling mobile applications
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

Contextually aware device management techniques are described. Identifying data is provided via a communication connection by a client device to a service provider via a network that is usable by the service provider to identify the client device or functionality of the client device. One or more contexts are received at the client device from the service provider via the network that correspond to the identifying data. Each of the one or more contexts includes management objects along with one or more triggers configured to cause the context to transition to a corresponding one of a plurality of context states and thereby cause performance of one or more actions corresponding to the context state. The one or more contexts are implemented locally by the client device effective to identify and perform the one or more actions corresponding to the context state by the client device based on identification of the one or more triggers without use of network communication by the client device.

Claims

1. A method comprising:

providing identifying data, by a client device, to a service provider via a network, the identifying data being usable by the service provider to identify the client device or functionality associated with the client device, or both;

receiving one or more contexts at the client device from the service provider via the network, the one or more contexts corresponding to the identifying data, and each of the one or more contexts having management objects and one or more triggers configured to cause the one or more contexts to transition to a corresponding one of a plurality of context states, the transition to the corresponding one of the plurality of context states causing performance of one or more actions associated with the corresponding one of the plurality of context states; and

implementing the one or more contexts locally by the client device effective to identify and perform the one or more actions by the client device based on identification of the one or more triggers without use of network communication by the client device.

2. The method as described in claim 1, wherein the one or more management objects specify management settings, management policies, or management resources.

3. The method as described in claim 1, wherein the identifying data is configured to cause the service provider to select the one or more contexts from a plurality of contexts and to communicate the selected one or more contexts to the client device via the network automatically and without user intervention.

4. The method as described in claim 1, wherein the implementing is performed without communication with the service provider.

5. The method as described in claim 1, wherein the one or more contexts are formed to support tiered applicability and through specified dependencies of at least one of the one or more contexts with another of the one or more contexts.

6. The method as described in claim 1, wherein the one or more contexts have a specified lifespan after which the one or more contexts are deactivated.

7. The method as described in claim 6, wherein the lifespan is specified using one or more non-temporal conditions.

8. The method as described in claim 1, wherein the one or more triggers include active queries of signal data.

9. The method as described in claim 1, wherein the one or more triggers include:

location data; and

at least one of API calls, sensor data, inferences form user actions, NFC data, systems states, or network connections.

10. A service provider comprising:

one or more modules implemented at least partially in hardware, the one or more modules configured to perform operations comprising;

receiving identifying data from a client device via a network;

responsive to the receiving, identifying one or more of a plurality of contexts based on the identifying data, each of the one or more contexts having management objects and one or more triggers configured to cause the one or more contexts to transition to a corresponding one of a plurality of context states, the transition to the corresponding one of the plurality of context states causing performance of one or more actions associated with the corresponding one of the plurality of context states; and

communicating the identified one or more contexts to the client device via the network effective to cause the client device to implement the one or more contexts locally and to identify and perform the one or more actions associated with the corresponding one of the plurality of context states based on identification of the one or more triggers without communicating with the service provider.

11. The service provider as described in claim 10, wherein the one or more management objects specify management settings, management policies, and management resources.

12. The service provider as described in claim 10, wherein the one or more contexts have a specified lifespan after which the one or more contexts are deactivated.

13. The service provider as described in claim 10, wherein the one or more triggers include active queries of signal data.

14. The service provider as described in claim 10, wherein the one or more triggers do not include location data.

15. A client device comprising:

a processing system; and

memory maintaining instructions that are executable by the processing system to implement an operating system configured to cause operations to be performed comprising;

providing identifying data, to a service provider via a network, the identifying data being usable by the service provider to identify the client device or functionality associated with the client device, or both;

receiving one or more contexts from the service provider via the network, the one or more contexts corresponding to the identifying data, and each of the one or more contexts having management objects and one or more triggers configured to cause the one or more contexts to transition to a corresponding one of a plurality of context states, the transition to the corresponding one of the plurality of context states causing performance of one or more actions associated with the corresponding one of the plurality of context states; and

implementing the one or more contexts locally effective to identify and perform the one or more actions by the client device based on identification of the one or more triggers without use of network communication by the client device.

16. The client device as described in claim 15, wherein the triggers include API calls or system states.

17. The client device as described in claim 15, wherein the triggers include sensor data and location information.

18. The client device as described in claim 15, wherein the triggers include inferences from user actions.

19. The client device as described in claim 15, wherein the one or more management objects specify management settings, management policies, and management resources.

20. The client device as described in claim 15, wherein the one or more contexts have a specified lifespan after which the one or more contexts are deactivated.