Background task execution over a network

• US 10,021,005 B2
• Filed: 02/13/2015
• Issued: 07/10/2018
• 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): Springer, James E
• Application Number:
  US14/622,704
• Publication Number:
  US 20150188791A1
• Time in Patent Office: 1,243 Days
• Field of Search: 709224
• 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 computer-implemented method, comprising:

determining, by a daemon process executed by a processor of a device, a type of a network connection associated with a network interface of the device;

determining, by the daemon process, a status of a first software component that is currently being used by a user of the device;

determining whether the first software component is likely to access a network via the network interface based on the type of the network connection and the status of the first software component; and

in response to determining the first software component is unlikely to access the network, notifying a second software component to perform a background task through the network interface of the device.

2. The method of claim 1, further comprising:

registering the second software component with the daemon process for receiving notifications;

maintaining, in a storage device of the device, a list of software components, including the second software component, which have registered with the daemon process to receive a notification to perform a background task through the network interface.

3. The method of claim 2, 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 types of network connections associated with the physical network interfaces.

4. The method of claim 3, wherein registering the second software component comprises:

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

selecting a time period during which a notification will be received by the second software component.

5. The method of claim 1, further comprising identifying a type of the first software component to determine whether the type of the first software component will typically access the network via the network interface of the device.

6. The method of claim 1, further comprising monitoring user activities of a telephone keypad of the device to determine whether the user is likely to make a telephone call to decide whether to notify the second software component.

7. The method of claim 1, further comprising monitoring a duration of a period of time during which the user actively uses a third software component to determine whether the user is likely to use the network interface, wherein if the duration of time exceeds a predetermined threshold, the user is unlikely to use the network interface.

8. The method of claim 1, wherein determining a status of the first software component comprises detecting that the first software component transitions from a foreground to a background, which indicates the first software component is unlikely to access the network via the network interface.

9. The method of claim 1, wherein the first software component and the second software component represent different functionalities of a single program running within the device.

10. A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations, the operations comprising:

determining, by a daemon process executed by a processor of a device, a type of a network connection associated with a network interface of the device;

determining, by the daemon process, a status of a first software component that is currently being used by a user of the device;

determining whether the first software component is likely to access a network via the network interface based on the type of the network connection and the status of the first software component; and

in response to determining the first software component is unlikely to access the network, notifying a second software component to perform a background task through the network interface of the device.

11. The non-transitory machine-readable medium of claim 10, wherein the operations further comprise:

registering the second software component with the daemon process for receiving notifications;

maintaining, in a storage device of the device, a list of software components, including the second software component, which have registered with the daemon process to receive a notification to perform a background task through the network interface.

12. The non-transitory machine-readable medium of claim 11, 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 types of network connections associated with the physical network interfaces.

13. The non-transitory machine-readable medium of claim 12, wherein registering the second software component comprises:

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

selecting a time period during which a notification will be received by the second software component.

14. The non-transitory machine-readable medium of claim 10, wherein the operations further comprise identifying a type of the first software component to determine whether the type of the first software component will typically access the network via the network interface of the device.

15. The non-transitory machine-readable medium of claim 10, wherein the operations further comprise monitoring user activities of a telephone keypad of the device to determine whether the user is likely to make a telephone call to decide whether to notify the second software component.

16. The non-transitory machine-readable medium of claim 10, wherein the operations further comprise monitoring a duration of a period of time during which the user actively uses a third software component to determine whether the user is likely to use the network interface, wherein if the duration of time exceeds a predetermined threshold, the user is unlikely to use the network interface.

17. The non-transitory machine-readable medium of claim 10, wherein determining a status of the first software component comprises detecting that the first software component transitions from a foreground to a background, which indicates the first software component is unlikely to access the network via the network interface.

18. The non-transitory machine-readable medium of claim 10, wherein the first software component and the second software component represent different functionalities of a single program running within the device.

19. A data processing system, comprising:

one or more processors;

a memory coupled to the one or more processors; and

a daemon process loaded into the memory and executed by the one or more processors to perform operations, the operations including;

determining a type of a network connection associated with a network interface of the device,

determining a status of a first software component that is currently being used by a user of the device,

determining whether the first software component is likely to access a network via the network interface based on the type of the network connection and the status of the first software component, and

in response to determining the first software component is unlikely to access the network, notifying a second software component to perform a background task through the network interface of the device.

20. The system of claim 19, wherein the operations further comprise:

registering the second software component with the daemon process for receiving notifications;

maintaining, in a storage device of the device, a list of software components, including the second software component, which have registered with the daemon process to receive a notification to perform a background task through the network interface.

21. The system of claim 20, 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 types of network connections associated with the physical network interfaces.

22. The system of claim 21, wherein registering the second software component comprises:

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

selecting a time period during which a notification will be received by the second software component.

23. The system of claim 19, wherein the operations further comprise identifying a type of a first software component to determine whether the type of the first software component will typically access the network via the network interface of the device.

24. The system of claim 19, wherein the operations further comprise monitoring user activities of a telephone keypad of the device to determine whether the user is like to make a telephone call to decide whether to notify the second software component.