Offloading network connectivity and execution tasks to an assistant device

• US 10,228,930 B2
• Filed: 01/28/2016
• Issued: 03/12/2019
• Est. Priority Date: 01/28/2016
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Srinivasan, Harish, Schultz, Benjamin M., Gray, James C., Mulye, Nishad
• Primary Examiner(s): Chang, Kenneth W
• Assistant Examiner(s): Champakesanatusptodotgov, Badridot
• Application Number:
  US15/009,594
• Publication Number:
  US 20170220332A1
• Time in Patent Office: 1,139 Days
• Field of Search: 726 7
• CPC Class Codes: G06F 13/102 where the programme performs an interfacing function, e.g. device driver G06F13/105 takes precedence; scheduling within device drivers G06F9/52; contention policies within device drivers G06F9/4881
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/452 Remote windowing, e.g. X-Window System, desktop virtualisation protocols for virtual reality H04L67/131
• CPC Class Codes: G06F 9/5094 where the allocation takes into account power or heat criteria power management in computers in general G06F1/3203; thermal management in computers in general G06F1/206
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/1433 Vulnerability analysis
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Functionality is described herein for performing at least one network connectivity task on a client device with the aid of one or more assistant devices. In some implementations, a client device (such as a smartphone, desktop personal computing device, etc.) relies on an assistant device to assist it in updating its programs, including its driver programs. In other implementations, a client device relies on an assistant device in establishing a network connection with a network-accessible entity. Functionality is also described herein for performing at least one program execution task on a client device with the aid of one or more assistant devices. For instance, the client device may rely on the assistant device to assist it in executing a driver program. The driver program, in turn, enables the client device to interact with a peripheral device or some other component.

Claims

1. A method comprising:

obtaining information reflecting capabilities of a plurality of candidate assistant devices that are configured to communicate with a client device over respective local communication links, the plurality of candidate assistant devices providing supplemental resources for use by the client device;

based at least on the capabilities of the plurality of candidate assistant devices, identifying a selected assistant device to execute a driver program on behalf of the client device, the driver program being configured to control a specific peripheral output device other than the client device; and

sending a driver-invoking event from the client device to the selected assistant device over a selected local communication link, the selected assistant device executing the driver program using selected supplemental resources of the selected assistant device to provide a driver output result,

wherein the driver output result is configured to control the specific peripheral output device.

2. The method of claim 1, further comprising:

determining that it is appropriate to run the driver program by the selected assistant device based at least on an indication that the driver program poses a security risk to the client device.

3. The method of claim 2, wherein the driver program is determined to pose the security risk when:

an update service or other source from which the driver program originates is determined to pose the security risk;

an access path of obtaining the driver program from the update service or other source is determined to pose the security risk;

or

threat analysis performed on the driver program indicates that the driver program poses the security risk.

4. The method of claim 1, wherein the selected supplemental resources provided by the selected assistant device include processing and memory resources.

5. The method of claim 4, further comprising:

sending the driver output result to the specific peripheral output device.

6. The method of claim 4, further comprising:

executing the driver program on the selected assistant device, the executing comprising emulating running of the driver program in an instruction set of the client device using an emulator that executes in another instruction set on the selected assistant device.

7. The method of claim 1, the capabilities reflecting round-trip times for individual assistant devices to contact a network-accessible entity.

8. The method of claim 7, further comprising:

measuring the round-trip times for each of the individual assistant devices.

9. The method of claim 1, wherein the specific peripheral output device comprises a printer.

10. The method of claim 1, performed entirely by the client device.

11. The method of claim 1, wherein the client device lacks the driver program that is executed by the selected assistant device.

12. The method of claim 1, further comprising:

discovering existence of the plurality of candidate assistant devices.

13. The method of claim 12, further comprising identifying the selected assistant device based at least on multiple factors comprising at least two of:

monetary cost of using each candidate assistant device;

power available to each candidate assistant device;

a location of each candidate assistant device relative to the client device; and

a performance of each candidate assistant device, measured with respect to one or more performance metrics.

14. The method of claim 1, further comprising:

determining power capabilities of the client device and the selected assistant device, to provide discovered power information; and

determining a manner of supplying power to the client device and/or the selected assistant device based at least on the discovered power information.

15. The method of claim 14, wherein the discovered power information includes at least one of:

an indication of a type of power source that is available to the client device and a type of power source that is available to the selected assistant device;

an indication of an amount of power that is available to the client device and an amount of power that is available to the selected assistant device;

or

an indication of whether the client device can receive power from the selected assistant device, and whether the selected assistant device can receive power from the client device.

16. An assistant device comprising:

a storage resource configured to store a driver program received from an update service, the driver program being configured to control a specific peripheral output device that is coupled to the assistant device; and

a hardware processor that is configured to;

send, over a local communication link to a client device, information reflecting capabilities of the assistant device for executing the driver program;

send, to the client device over the local communication link, an indication that the driver program is available at the assistant device;

receive a driver-invoking event from the client device over the local communication link;

in response to the driver-invoking event, execute the driver program using resources of the assistant device to provide a driver output result; and

control the specific peripheral output device by communicating the driver output result to the specific peripheral output device.

17. The assistant device of claim 16, wherein the hardware processor is configured to:

determine whether it is appropriate to run the driver program by the assistant device based at least on one or more factors.

18. The assistant device of claim 16, wherein the specific peripheral output device is a printer.

19. A system comprising:

a client device,

an assistant device; and

a peripheral output device,

the client device including;

a client device communication interface that is configured to communicatively couple the client device with the assistant device;

a client device storage resource that provides one or more client device programs; and

a client device hardware processor that is configured to;

select the assistant device from among a plurality of candidate assistant devices to execute a particular driver program, based at least on information reflecting capabilities of the plurality of candidate assistant devices; and

execute the one or more client device programs in the client device storage resource;

the assistant device including;

an assistant device communication interface that is configured to communicatively couple the assistant device with the client device;

an assistant device storage resource that provides one or more assistant device programs; and

an assistant device hardware processor that is configured to;

execute the particular driver program on behalf of the client device to obtain a driver output result; and

control the peripheral output device on behalf of the client device by communicating the driver output result to the peripheral output device.

20. The system of claim 19, wherein the peripheral output device comprises a printer or a display device.