Background task execution over a network
First Claim
Patent Images
1. A machine implemented method comprising:
- monitoring network activity at a device'"'"'s network interface, the network activity being monitored by a daemon process to determine idle time at the device'"'"'s network interface, wherein the network interface includes a plurality of physical network interfaces;
executing a first software component as a foreground process;
registering a second software component with the daemon process including specifying at least one of the physical network interfaces, the second software component to be called back by the daemon process based on a level of network activity at the specified physical network interface, the daemon process being configured, after the registering, to monitor each of the plurality of physical network interfaces to determine idle time and to notify the second software component in response to a level of idle time of network activity at the device'"'"'s network interface;
notifying the second software component, in response to the level of idle time associated with the specified physical network interface, to cause the second software component to perform a background task using the specified physical network interface of the device'"'"'s network interface, wherein notifying the second software component includes notifying the second software component when the specified physical network interface is idle.
0 Assignments
0 Petitions
Accused Products
Abstract
Network activity of a client device that is coupled to a data network is monitored, to detect network activity idle time. Based upon detecting the idle time, an application running in the client device is automatically signaled that its background task be executed over the data network. Other embodiments are also described and claimed.
-
Citations
18 Claims
-
1. A machine implemented method comprising:
-
monitoring network activity at a device'"'"'s network interface, the network activity being monitored by a daemon process to determine idle time at the device'"'"'s network interface, wherein the network interface includes a plurality of physical network interfaces; executing a first software component as a foreground process; registering a second software component with the daemon process including specifying at least one of the physical network interfaces, the second software component to be called back by the daemon process based on a level of network activity at the specified physical network interface, the daemon process being configured, after the registering, to monitor each of the plurality of physical network interfaces to determine idle time and to notify the second software component in response to a level of idle time of network activity at the device'"'"'s network interface; notifying the second software component, in response to the level of idle time associated with the specified physical network interface, to cause the second software component to perform a background task using the specified physical network interface of the device'"'"'s network interface, wherein notifying the second software component includes notifying the second software component when the specified physical network interface is idle. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. An article of manufacture comprising:
a non-transitory computer storage medium that stores instructions for an operating system program which configure a client device that is coupled to a data network to; monitor network activity at the client device'"'"'s network interface, the network activity being monitored by a daemon process to determine idle time at the client device'"'"'s network interface, wherein the network interface includes a plurality of physical network interfaces; execute a first software component as a foreground process in the client device; register a second software component with the daemon process including specifying at least one of the physical network interfaces, the second software component to be called back by the daemon process based on a level of network activity at the specified physical network interface, the daemon process being configured, after the registering, to monitor each of the plurality of physical network interfaces to determine idle time and to notify the second software component in response to a determination of idle time of network activity at the device'"'"'s network interface; notify the second software component, in response to the determination of idle time associated with the specified physical network interface, to cause the second software component to perform a background task using the specified physical network interface of the device'"'"'s network interface, wherein notifying the second software component includes notifying the second software component when the specified physical network interface is idle. - View Dependent Claims (10, 11, 12, 13, 14)
-
15. An apparatus comprising:
-
a hardware processor, wherein the hardware processor is running a foreground process and one or more background processes; a network interface coupled to a data network, the network interface including a plurality of physical network interfaces; and a daemon process unit that registers the one or more background processes running on the hardware processor including specifying one or more physical network interfaces, a second software component to be called back by the daemon process based on a level of network activity at the specified physical network interface, wherein the daemon process unit monitors network activity at the network interface to determine idle time at the network interface, including monitoring how much time the foreground process is performing a task that utilizes the data network through the network interface, wherein the daemon process unit monitors each of the plurality of physical network interfaces to determine idle time and notifies one of the one or more background processes to perform a background network task upon detecting an idle time of the corresponding physical network interface, wherein notifying the second software component includes notifying the second software component when the specified physical network interface is idle. - View Dependent Claims (16, 17, 18)
-
Specification