CONTEXT NOTIFICATIONS

• US 20160360007A1
• Filed: 05/10/2016
• Published: 12/08/2016
• Est. Priority Date: 06/05/2015
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Siracusa, Michael R., de Lacerda, Joao Pedro Forjaz, Wan, Kit-Man, Kapoor, Gaurav, Vaishampayan, Umesh S.
• Granted Patent: US 10,491,708 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: G06F 11/3024 where the computing system component is a central processing unit [CPU]
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/461 Saving or restoring of program or task context
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06N 7/01 Probabilistic graphical models, e.g. probabilistic networks
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 52/0264 by selectively disabling software applications
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

Disclosed are systems, methods, and non-transitory computer-readable storage media for notifying context clients of changes to the current context of a computing device. In some implementations, a context client can register to be called back when the context daemon detects specified context. For example, the context client can specify a context in which the context client is interested. When the context daemon detects that the current context of the computing device corresponds to the registered context, the context daemon can notify the context client that the current context matches the context in which the context client is interested. Thus, context clients do not require the programming necessary to independently obtain context updates and detect changes in context that are relevant or of interest to the context client.

Claims

1. A method comprising:

generating, by a context daemon process executing on a computing device, information describing a current context of the computing device;

receiving, by the context daemon process, a callback request from a context client process that specifies a predicate for sending a notification to the context client process, the predicate specifying context conditions for calling back the context client;

detecting, by the context daemon process, that the current context corresponds to the predicate; and

in response to the detecting, sending, by the context daemon process, a callback notification to the requesting client.

2. The method of claim 1, wherein the context conditions specify values of one or more context items which when detected in the current context cause the context daemon to send the callback notification to the context client.

3. The method of claim 1, wherein the callback request includes an identifier for the context client and the predicate;

and further comprising;

generating, by the context daemon, a unique identifier for the callback request; and

sending, by the context daemon, the unique identifier to the requesting client.

4. The method of claim 3, further comprising:

storing, by the context daemon, an association between the unique identifier, the context client identifier, and the predicate.

5. The method of claim 4, wherein the storing includes storing the unique identifier, the context client identifier, and the predicate in memory associated with the context daemon.

6. The method of claim 4, wherein the storing includes storing the unique identifier, the context client identifier, and the predicate in a predicate database.

7. The method of claim 1, further comprising:

receiving, by the context daemon, device state information describing the current state of software and hardware components of the computing device; and

generating, by the context daemon, the current context information based on the received device state information.

8. A computing device for context notification comprising:

a context daemon process, which when executed on the computing device, causes the context daemon process to;

generate information describing a current context of the computing device;

receive a callback request from a context client process that specifies a predicate for sending a notification to the context client process, the predicate specifying context conditions for calling back the context client;

detect that the current context corresponds to the predicate; and

in response to the detection, send a callback notification to the requesting client.

9. The computing device of claim 8, wherein the context conditions specify values of one or more context items which when detected in the current context cause the context daemon to send the callback notification to the context client.

10. The computing device of claim 8, wherein the callback request includes an identifier for the context client and the predicate;

and the context daemon process is further executed to;

generate a unique identifier for the callback request; and

send the unique identifier to the requesting client.

11. The computing device of claim 10, further comprising the context daemon process executed to:

store an association between the unique identifier, the context client identifier, and the predicate.

12. The computing device of claim 11, further comprising the context daemon process executed to:

store the unique identifier, the context client identifier, and the predicate in memory associated with the context daemon.

13. The computing device of claim 11, further comprising the context daemon process executed to:

store the unique identifier, the context client identifier, and the predicate in a predicate database.

14. The computing device of claim 8, further comprising the context daemon process executed to:

receive device state information describing the current state of software and hardware components of the computing device; and

generate the current context information based on the received device state information.

15. A non-transitory computer-readable medium containing instructions that, when executed by a computing device, cause a context daemon process of the computing device to:

generate information describing a current context of the computing device;

receive a callback request from a context client process that specifies a predicate for sending a notification to the context client process, the predicate specifying context conditions for calling back the context client

detect that the current context corresponds to the predicate; and

in response to the detection, send a callback notification to the requesting client.

16. The non-transitory computer-readable medium of claim 15, wherein the context conditions specify values of one or more context items which when detected in the current context cause the context daemon to send the callback notification to the context client.

17. The non-transitory computer-readable medium of claim 15, wherein the callback request includes an identifier for the context client and the predicate;

and further instructions which when executed cause the context daemon process to;

generate a unique identifier for the callback request; and

send the unique identifier to the requesting client.

18. The non-transitory computer-readable medium of claim 17, further comprising instructions, which when executed cause the context daemon process to:

store an association between the unique identifier, the context client identifier, and the predicate.

19. The non-transitory computer-readable medium of claim 18, further comprising instructions, which when executed cause the context daemon process to:

store the unique identifier, the context client identifier, and the predicate in memory associated with the context daemon.

20. The non-transitory computer-readable medium of claim 18, further comprising instructions, which when executed cause the context daemon process to:

store the unique identifier, the context client identifier, and the predicate in a predicate database.