Efficient context monitoring
First Claim
1. A method comprising:
- receiving, at a context daemon executing on a computing device, a first context callback request from a context client, the first context callback request initiating a first communication session between the context client and the context daemon;
terminating the context client after the context daemon receives the first context callback request and in response to determining that the context client is idle;
receiving, by the context daemon, current context information;
determining that the current context information corresponds to the first context callback request;
in response to the determining, detecting, by the context daemon, that the first communication session with the context client has terminated; and
in response to the detecting, sending, by the context daemon, a restart message to a launch daemon requesting that the launch daemon restart the context client.
1 Assignment
0 Petitions
Accused Products
Abstract
Disclosed are systems, methods, and non-transitory computer-readable storage media for efficiently monitoring the operating context of a computing device. In some implementations, the context daemon and/or the context client can be terminated to conserve system resources. For example, if the context daemon and/or the context client are idle, they can be shutdown to conserve battery power or free other system resources (e.g., memory). When an event occurs (e.g., a change in current context) that requires the context daemon and/or the context client to be running, the context daemon and/or the context client can be restarted to handle the event. Thus, system resources can be conserved while still providing relevant context information collection and callback notification features.
-
Citations
17 Claims
-
1. A method comprising:
-
receiving, at a context daemon executing on a computing device, a first context callback request from a context client, the first context callback request initiating a first communication session between the context client and the context daemon; terminating the context client after the context daemon receives the first context callback request and in response to determining that the context client is idle; receiving, by the context daemon, current context information; determining that the current context information corresponds to the first context callback request; in response to the determining, detecting, by the context daemon, that the first communication session with the context client has terminated; and in response to the detecting, sending, by the context daemon, a restart message to a launch daemon requesting that the launch daemon restart the context client. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A computing device for efficient context monitoring comprising:
-
a hardware processor; and logic, which when executed by the hardware processor on the computing device, causes a context daemon to; receive a first context callback request from a context client, the first context callback request initiating a first communication session between the context client and the context daemon; terminate the context client after the context daemon receives the first context callback request and in response to determining that the context client is idle; receive current context information; determine that the current context information corresponds to the first context callback request; detect, in response to the determination, that the first communication session with the context client has terminated; and send, in response to the detection, a restart message to a launch daemon requesting that the launch daemon restart the context client. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A non-transitory computer-readable medium containing instructions that, when executed by a computing device, cause a context daemon of the computing device to:
-
receive a first context callback request from a context client, the first context callback request initiating a first communication session between the context client and the context daemon; terminate the context client after the context daemon receives the first context callback request and in response to determining that the context client is idle; receive current context information; determine that the current context information corresponds to the first context callback request; detect, in response to the determination, that the first communication session with the context client has terminated; and send, in response to the detection, a restart message to a launch daemon requesting that the launch daemon restart the context client. - View Dependent Claims (14, 15, 16, 17)
-
Specification