Daemon process determination of idle time of network activity at network interface

• US 8,959,213 B2
• Filed: 01/14/2014
• Issued: 02/17/2015
• Est. Priority Date: 01/05/2007
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Wyld, Jeremy, Ganatra, Nitin, Williamson, Richard John
• Primary Examiner(s): Patel, Haresh N
• Application Number:
  US14/154,445
• Publication Number:
  US 20140156834A1
• Time in Patent Office: 399 Days
• Field of Search: 709/224, 709/203, 726/1
• US Class Current: 709/224
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: H04L 43/0805 by checking availability

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.

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;

executing a first software component as a foreground process;

registering a plurality of software components with the daemon process;

determining, by the daemon process, an idle time of network activity at the device'"'"'s network interface; and

notifying the plurality of software components, in response to the determined idle time, to cause the software components to perform a background task through the device'"'"'s network interface.

2. The method as in claim 1, the method further comprising:

maintaining, in storage, a list of software components that have registered with the daemon process to receive a notification to perform a background task through the device'"'"'s network interface, and wherein one of the plurality of software components performs the background task while the first software component executes as a foreground process.

3. The method as in claim 1, wherein the monitoring network activity comprises counting a number of upstream or downstream data units passing through the network interface of the device to a data network during a predetermined time interval.

4. The method as in claim 1, wherein the monitoring network activity comprises determining a type of the network interface.

5. The method as in claim 1, wherein the monitoring network activity comprises:

determining a task that is about to be performed by the device; and

classifying the task as a network task or a non-network task.

6. The method as in claim 1, wherein the monitoring network activity comprises monitoring input from a user to determine the likelihood the foreground process will be performing a network task during a predetermined time interval.

7. The method as in claim 1, wherein one of the plurality of software components passes the background task to the daemon process for execution.

8. The method as in claim 1, wherein one of the plurality of software components returns a notification to the daemon process to inform the daemon process that one of the plurality of software components does not have a background task to perform.

9. The method as in claim 1, wherein the network interface includes a plurality of physical network interfaces and the daemon process monitors each of the plurality of physical network interfaces to determine idle time.

10. The method as in claim 9, wherein registering one of the plurality of software components comprises:

selecting a preferred physical network interface from the plurality of physical network interfaces; and

selecting a time period during which notifications may be received.

11. The method as in claim 10, wherein the notifying one of the plurality of software components comprises notifying one of the plurality of software components when the preferred physical network interface is idle.

12. 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;

execute a first software component as a foreground process in the client device;

register a plurality of software components with the daemon process;

determine an idle time of network activity at the device'"'"'s network interface; and

notify the plurality of software components, in response to the determination of idle time, to cause the software components to perform a background task using the client device'"'"'s network interface.

13. The article of manufacture of claim 12, wherein the medium stores further instructions which cause the client device to:

maintain, in storage, a list of software components that have registered with the daemon process to receive a notification to perform a background task through the client device'"'"'s network interface, and wherein one of the plurality of software components performs the background task while the first software component executes as a foreground process.

14. The article of manufacture of claim 12, wherein the monitoring network activity comprises counting a number of upstream or downstream data units passing through the network interface of the device to a data network during a predetermined time interval and comparing the counted number of units to a predetermined value.

15. The article of manufacture of claim 12, wherein the monitoring network activity comprises determining a type of the network interface.

16. The article of manufacture of claim 12, wherein the monitoring network activity comprises:

determining a task that is about to be performed by the device; and

classifying the task as a network task or a non-network task.

17. The article of manufacture of claim 12, wherein the monitoring network activity comprises monitoring input from a user to determine the likelihood the foreground process will be performing a network task during a predetermined time interval.

18. An apparatus comprising:

a hardware processor, wherein the hardware processor is running a foreground process and a plurality of background processes;

a network interface coupled to a data network; and

a daemon process unit that registers the plurality of background processes running on the hardware processor, 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 notifies the plurality of background processes to perform a background network task upon detecting an idle time.

19. The apparatus as in claim 18, further comprising:

a storage unit to store a list of the background processes that have registered with the daemon process to receive a notification to perform a background network task through the network interface, wherein the background network task is performed while the foreground process is executing in the foreground.

20. The apparatus as in claim 18, wherein the daemon process unit monitors network activity by counting a number of upstream or downstream data units passing through the network interface to the data network during a predetermined time interval.

21. The apparatus as in claim 18, wherein the daemon process unit monitors network activity by:

determining a task that is about to be performed by the foreground process; and

classifying the task as a network task or a non-network task.

22. 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;

executing a first software component as a foreground process;

registering a second software component with the daemon process;

determining a type for the first software component or for a task of the first software component, wherein the type is not likely to generate network activity;

determining, by the daemon process, an idle time of network activity at the device'"'"'s network interface; and

notifying the registered second software component, in response to the determined type and idle time, to cause the second software component to perform a background task through the device'"'"'s network interface.

23. The method of claim 22, the method further comprising:

maintaining, in storage, a list of software components that have registered with the daemon process to receive a notification to perform a background task through the device'"'"'s network interface, and wherein the second software component performs the background task while the first software component executes as a foreground process.

24. The method of claim 22, wherein the monitoring network activity comprises counting a number of upstream or downstream data units passing through the network interface of the device to a data network during a predetermined time interval.

25. The method of claim 22, wherein the monitoring network activity comprises determining a type of the network interface.

26. The method of claim 22, wherein the monitoring network activity comprises monitoring input from a user to determine the likelihood the foreground process will be performing a network task during a predetermined time interval.

27. The method of claim 22, wherein the network interface includes a plurality of physical network interfaces and the daemon process monitors each of the plurality of physical network interfaces to determine idle time, and wherein registering the second software component comprises:

selecting a preferred physical network interface from the plurality of physical network interfaces; and

selecting a time period during which notifications may be received.

28. A non-transitory computer-readable medium storing instructions, which when executed by a processing device, cause the processing device to perform a 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;

executing a first software component as a foreground process;

registering a second software component with the daemon process;

determining a type for the first software component or for a task of the first software component, wherein the type is not likely to generate network activity;

determining, by the daemon process, an idle time of network activity at the device'"'"'s network interface; and

notifying the registered second software component, in response to the determined type and idle time, to cause the second software component to perform a background task through the device'"'"'s network interface.

29. The non-transitory computer-readable medium of claim 28, the method further comprising:

maintaining, in storage, a list of software components that have registered with the daemon process to receive a notification to perform a background task through the device'"'"'s network interface, and wherein the second software component performs the background task while the first software component executes as a foreground process.

30. The non-transitory computer-readable medium of claim 28, wherein the monitoring network activity comprises counting a number of upstream or downstream data units passing through the network interface of the device to a data network during a predetermined time interval.

31. The non-transitory computer-readable medium of claim 28, wherein the monitoring network activity comprises determining a type of the network interface.

32. The non-transitory computer-readable medium of claim 28, wherein the monitoring network activity comprises monitoring input from a user to determine the likelihood the foreground process will be performing a network task during a predetermined time interval.

33. The non-transitory computer-readable medium of claim 28, wherein the network interface includes a plurality of physical network interfaces and the daemon process monitors each of the plurality of physical network interfaces to determine idle time, and wherein registering the second software component comprises:

selecting a preferred physical network interface from the plurality of physical network interfaces; and

selecting a time period during which notifications may be received.