Abstract: Managing power-consuming resources on a first computing device by adjusting data delivery from a plurality of second computing devices based on a state of the first computing device. The state of the first computing device is provided to the second computing devices to alter the data delivery. In some embodiments, the first computing device provides the second computing devices with actions or commands relating to data delivery based on the device state. For example, the second computing devices are instructed to store the data, forward the data, forward only high priority data, or perform other actions. Managing the data delivery from the second computing devices preserves battery life of the first computing device.

Abstract: Managing power-consuming resources on a first computing device by adjusting data delivery from a plurality of second computing devices based on a state of the first computing device. The state of the first computing device is provided to the second computing devices to alter the data delivery. In some embodiments, the first computing device provides the second computing devices with actions or commands relating to data delivery based on the device state. For example, the second computing devices are instructed to store the data, forward the data, forward only high priority data, or perform other actions. Managing the data delivery from the second computing devices preserves battery life of the first computing device.

Abstract: Managing power-consuming resources on a first computing device by adjusting data delivery from a plurality of second computing devices based on a state of the first computing device. The state of the first computing device is provided to the second computing devices to alter the data delivery. In some embodiments, the first computing device provides the second computing devices with actions or commands relating to data delivery based on the device state. For example, the second computing devices are instructed to store the data, forward the data, forward only high priority data, or perform other actions. Managing the data delivery from the second computing devices preserves battery life of the first computing device.

Abstract: Combining network connection maintenance operations that use a resource to extend battery life. Each of the network connections has a timer and a defined tolerance for early connection maintenance. After receiving notification of an event, the network connections are accessed to identify the connections for which a maintenance operation may be performed early based on the timer and the tolerance. In an embodiment, the maintenance operation includes sending a transmission control protocol (TCP) keep-alive packet on the connection.

Abstract: Coalescing schedules that use a resource to extend battery life. Each of the schedules is defined to execute at a recurrent activation time within a defined tolerance. After receiving notification of an event, the schedules are accessed to identify the schedules that may be executed early based on their activation time and tolerance. The identified schedules are aggregated for execution.

Abstract: Managing power-consuming resources on a first computing device by adjusting data delivery from a plurality of second computing devices based on a state of the first computing device. The state of the first computing device is provided to the second computing devices to alter the data delivery. In some embodiments, the first computing device provides the second computing devices with actions or commands relating to data delivery based on the device state. For example, the second computing devices are instructed to store the data, forward the data, forward only high priority data, or perform other actions. Managing the data delivery from the second computing devices preserves battery life of the first computing device.

Abstract: Managing recurrent schedules based on events and conditions. Schedules from a plurality of applications are identified based on an activation time for the schedules and a determination of whether or not conditions defined for the schedules are met. The identified schedules are activated by performing actions associated with each of the identified schedules. In an embodiment, the schedules are grouped based on functionality and prioritized to avoid conflicts within each group.

Abstract: Combining network connection maintenance operations that use a resource to extend battery life. Each of the network connections has a timer and a defined tolerance for early connection maintenance. After receiving notification of an event, the network connections are accessed to identify the connections for which a maintenance operation may be performed early based on the timer and the tolerance. In an embodiment, the maintenance operation includes sending a transmission control protocol (TCP) keep-alive packet on the connection.

Abstract: Managing power-consuming resources on a first computing device by adjusting data delivery from a plurality of second computing devices based on a state of the first computing device. The state of the first computing device is provided to the second computing devices to alter the data delivery. In some embodiments, the first computing device provides the second computing devices with actions or commands relating to data delivery based on the device state. For example, the second computing devices are instructed to store the data, forward the data, forward only high priority data, or perform other actions. Managing the data delivery from the second computing devices preserves battery life of the first computing device.

Abstract: Combining network connection maintenance operations that use a resource to extend battery life. Each of the network connections has a timer and a defined tolerance for early connection maintenance. After receiving notification of an event, the network connections are accessed to identify the connections for which a maintenance operation may be performed early based on the timer and the tolerance. In an embodiment, the maintenance operation includes sending a transmission control protocol (TCP) keep-alive packet on the connection.

Abstract: Managing power-consuming resources on a first computing device by time-based and condition-based scheduling of data delivery from a plurality of second computing devices. A scheduler executing on the first computing device has knowledge of recurrent schedules for activation by the second computing devices. The first computing device determines availability of the power-consuming resources and adjusts an activation time for the schedules to use the power-consuming resources when the resources are available. Managing the schedules associated with the second computing devices preserves battery life of the first computing device.

Abstract: Coordinating delivery of data to a first computing device from a plurality of second computing devices based on known power times for a resource associated with the first computing device. One of the second computing devices requests a time interval for data delivery. The first computing device compares the requested time interval to the known power times to determine a delivery time. For example, the requested time interval is compared against activation times for recurrent schedules that use the resource, and against previously determined delivery times. The second computing device delivers data at the determined delivery time to preserve the resource. In some embodiments, the delivery time is adjusted for processing delays and network latency.

Abstract: A unique system and method that facilitates synchronizing data across multiple accounts at about the same time is provided. The system and method involve configuring an intelligent set of synchronization rules that can apply to various data types from one or more user accounts or storage locations. In addition, the system or method can leverage off of existing search folders or search queries to configure the synchronization rules.

Abstract: Managing power-consuming resources on a first computing device by time-based and condition-based scheduling of data delivery from a plurality of second computing devices. A scheduler executing on the first computing device has knowledge of recurrent schedules for activation by the second computing devices. The first computing device determines availability of the power-consuming resources and adjusts an activation time for the schedules to use the power-consuming resources when the resources are available. Managing the schedules associated with the second computing devices preserves battery life of the first computing device.

Abstract: Managing power-consuming resources on a first computing device by adjusting data delivery from a plurality of second computing devices based on a state of the first computing device. The state of the first computing device is provided to the second computing devices to alter the data delivery. In some embodiments, the first computing device provides the second computing devices with actions or commands relating to data delivery based on the device state. For example, the second computing devices are instructed to store the data, forward the data, forward only high priority data, or perform other actions. Managing the data delivery from the second computing devices preserves battery life of the first computing device.

Abstract: Combining network connection maintenance operations that use a resource to extend battery life. Each of the network connections has a timer and a defined tolerance for early connection maintenance. After receiving notification of an event, the network connections are accessed to identify the connections for which a maintenance operation may be performed early based on the timer and the tolerance. In an embodiment, the maintenance operation includes sending a transmission control protocol (TCP) keep-alive packet on the connection.

Abstract: Managing recurrent schedules based on events and conditions. Schedules from a plurality of applications are identified based on an activation time for the schedules and a determination of whether or not conditions defined for the schedules are met. The identified schedules are activated by performing actions associated with each of the identified schedules. In an embodiment, the schedules are grouped based on functionality and prioritized to avoid conflicts within each group.

Abstract: Coalescing schedules that use a resource to extend battery life. Each of the schedules is defined to execute at a recurrent activation time within a defined tolerance. After receiving notification of an event, the schedules are accessed to identify the schedules that may be executed early based on their activation time and tolerance. The identified schedules are aggregated for execution.