MULTI-INTERFACE POWER-AWARE NETWORKING

• US 20170359272A1
• Filed: 06/10/2016
• Published: 12/14/2017
• Est. Priority Date: 06/10/2016
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Srinivasan, Harish, Flores Assad, Javier N., Gray, Chris C., Powell, JR., David Richard, Schultz, Benjamin M., Wood, Ryan Gregory
• Granted Patent: US 10,511,542 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 12/10 Current supply arrangements
• CPC Class Codes: H04L 41/0823 characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for optimising operational conditions of wireless networks H04W24/02
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/808 User-type aware
• CPC Class Codes: H04W 52/0225 using monitoring of external events, e.g. the presence of a signal
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

The techniques described herein monitor, store, and evaluate network information associated with an application to determine a connectivity option to use to communicate data. A connectivity option includes a network interface and a type of network connection. The determination is made based on power consumption information associated with available connectivity options. Consequently, a device on which the application is installed can better manage its power consumption associated with network communications.

Claims

1. A device comprising:

one or more processors;

a plurality of network interfaces configured to create and maintain a plurality of different types of network connections;

memory storing a policy store of the device that maintains application profiles for a plurality of applications stored on the device; and

a network connection management module stored on the memory and executable by the one or more processors, the network connection management configured to;

receive, from one of the plurality of applications, a request to communicate data over a network;

access an application profile associated with the one of the plurality of applications, the application profile describing network performance requirements for the one of the plurality of applications;

for each network interface of the plurality of network interfaces, obtain a connectivity profile associated with the network interface, the connectivity profile including one or more types of network connections, an expected power consumption associated with an individual type of network connection, an expected network performance associated with an individual type of network connection, and information of a current location of the device;

determine, based at least in part on the connectivity profiles obtained and the network performance requirements for the one of the plurality of applications, an order of connectivity options, wherein an individual connectivity option comprises a network interface and a type of network connection;

select a connectivity option from the order of connectivity options; and

use the network interface and the type of network connection of the selected connectivity option to communicate the data.

2. The device of claim 1, wherein the selection of the connectivity option is based at least in part on the expected power consumption of the connectivity option being less than an expected power consumption of another connectivity option.

3. The device of claim 1, further comprising a traffic logging module stored on the memory and executable by the one or more processors to:

monitor device-specific network traffic patterns for the one of the plurality of applications;

report the device-specific network traffic patterns to a remote monitoring service that aggregates network traffic patterns for the one of the plurality of applications to generate the network performance requirements;

receive, from the remote monitoring service, the network performance requirements for the application; and

in response to receipt of the network performance requirements, update the application profile of the one of the plurality of applications.

4. The device of claim 3, wherein the network connection management module is further configured to calculate the network performance requirements based on observed network interactions between the one of the plurality of applications and one or more other applications.

5. The device of claim 1, wherein the network performance requirements for the one of the plurality of applications are based on an execution state of the one of the plurality of applications.

6. The device of claim 5, wherein the execution state is based at least in part on whether the one of the plurality of applications is actively using a display screen to perform a function.

7. The device of claim 1, wherein:

the network performance requirements define, as a threshold to be satisfied, at least one of;

a minimum amount of throughput, a maximum amount of latency, a maximum amount of jitter, a maximum packet loss rate, or a maximum packet error rate; and

the network performance requirements are generated to ensure an acceptable level of usage of the one of the plurality of applications.

8. The device of claim 1, further comprising a proxy service, the proxy service configured to manage application flows and decouple application management from network connection management.

9. A device comprising:

one or more processors;

a plurality of network interfaces configured to create and maintain a plurality of different types of network connections;

memory storing a policy store of the device that maintains application profiles for a plurality of applications stored on the device; and

a network connection management module stored on the memory and executable by the one or more processors, the network connection management configured to;

maintain a first network connection to communicate data for an application executing on the device, the first network connection being associated with a first connectivity option, wherein an individual connectivity option comprises a network interface and a type of network connection;

determine an occurrence of an event that causes an evaluation of network connectivity;

access an application profile associated with the application, the application profile describing network performance requirements for the application based on a current execution state of the application;

obtain a first connectivity profile associated with the first connectivity option, the first connectivity profile describing expected performance and expected power consumption of the first network connection based on a current location of the device;

obtain a second connectivity profile associated with a second connectivity option, the second connectivity profile describing expected performance and expected power consumption of a second network connection based on the current location of the device;

determine that the network performance requirements for the application are satisfied by the expected performance of the second network connection; and

based on the determination that the network performance requirements are satisfied by the expected performance of the second network connection, switch from using the first network connection to communicate data for the application to using the second network connection to communicate data for the application.

10. The device of claim 9, wherein the event comprises movement of the device from a previous location to the current location.

11. The device of claim 9, wherein:

the event comprises a state transition of the application from a previous execution state to the current execution state;

use of the second network connection consumes less power than use of the first network connection; and

switching from using the first network connection to communicate data for the application to using the second network connection to communicate data for the application is based at least in part on the use of the second network connection consuming less power than the use of the first network connection.

12. The device of claim 9, wherein the event comprises a determination that the first network connection is no longer satisfying previously determined network performance requirements for the application.

13. The device of claim 9, wherein the event comprises expiration of a predetermined time interval.

14. The device of claim 9, wherein the event comprises an indication that a current battery level is below a threshold battery level.

15. The device of claim 9, wherein the first connectivity option and the second connectivity option use different network interfaces.

16. The device of claim 9, wherein the first connectivity option and the second connectivity option use a same network interface but different types of network connections.

17. A method comprising:

receiving, from one of a plurality of applications stored on a device, a request to communicate data over a network;

accessing an application profile associated with the one of the plurality of applications, the application profile describing network performance requirements for the one of the plurality of applications;

for each of a plurality of network interfaces of the device, obtaining a connectivity profile associated with the network interface, the connectivity profile including one or more types of network connections, an expected power consumption associated with an individual type of network connection, an expected network performance associated with an individual type of network connection, and information of a current location of the device;

determining, based at least in part on the connectivity profiles obtained and the network performance requirements for the one of the plurality of applications, an order of connectivity options, wherein an individual connectivity option comprises a network interface and a type of network connection;

selecting a connectivity option from the order of connectivity options; and

using the network interface and the type of network connection of the selected connectivity option to communicate the data.

18. The method of claim 17, wherein the selection of the connectivity option is based at least in part on the expected power consumption of the connectivity option being less than an expected power consumption of another connectivity option.

19. The method of claim 17, wherein the request is associated with a communication session, the communication session defined based on at least one of:

a user that is logged into a device, global positioning system (GPS) coordinates, or a timestamp.

20. The method of claim 17, further comprising:

monitoring device-specific network traffic patterns for the one of the plurality of applications;

reporting the device-specific network traffic patterns to a remote monitoring service that aggregates network traffic patterns for the one of the plurality of applications to generate the network performance requirements;

receiving, from the remote monitoring service, the network performance requirements for the application; and

in response to receipt of the network performance requirements, updating the application profile of the one of the plurality of applications.