Providing remote access to applications through interface hooks

• US 11,283,866 B2
• Filed: 07/07/2014
• Issued: 03/22/2022
• Est. Priority Date: 07/07/2014
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Kumar, Rakesh, Petrov, Julian, Summers, Jacob
• Primary Examiner(s): Wang, Liang Che A
• Assistant Examiner(s): Lin, Sherman
• Application Number:
  US14/324,646
• Publication Number:
  US 20160006803A1
• Time in Patent Office: 2,815 Days
• Field of Search: 709203
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems

Abstract

Methods, systems, and computer-readable media for providing remote access to applications executing on a host device are presented. Aspects described herein may enable a host device to provide remote access to applications executing in a user session by hooking one or more APIs (or other interfaces) associated with an application instance and a window composition module. Dynamically assigned ports may be generated and used to allow a client device to provide remote user input to an application instance operating in a remote access mode. One or more APIs associated with the application instance may be hooked to provide the remote user input to an input queue of the application instance, bypassing an operating system input queue in some embodiments. APIs associated with the application instance and the window composition module may be hooked to allow the host device to recognize window textures generated by the application instance. These recognized window textures may be sent to the remote client device. As a result, according to some aspects, a host device may enable remote access to the application instance by providing remote input to the application instance and forwarding output from the application instance to the remote client device. These and other features will be discussed further herein.

Claims

1. A method comprising:

providing, by a host device, a shadow desktop environment segregated from a first local desktop environment of the host device, output from applications of the first local desktop environment being presented to a local user on the host device, output from the shadow desktop environment being presented to a remote client, and instances of applications of the shadow desktop environment being unable to interact with instances of applications of the first local desktop environment;

transforming, by the host device, an instance of an application in the first local desktop environment from a local mode to a remote access mode in the shadow desktop environment by;

transferring execution of the instance of the application from the first local desktop environment to the shadow desktop environment;

assigning a port to the instance of the application; and

hooking one or more application programming interfaces (APIs) associated with the instance of the application to generate one or more first hooks, the one or more first hooks are configured such that;

first input, from a remote application viewer application locally executing on the remote client, is redirected to the instance of the application executing in the shadow desktop environment of the host device;

output from the instance of the application is redirected to the remote client;

second input, from the first local desktop environment of the host device and associated with the instance of the application, is suppressed; and

third input, from the host device and associated with different instances of the application executing on the host device, is permitted;

receiving, by the host device, user input from the remote client through the port;

providing, by the host device, the user input to the instance of the application via the one or more APIs;

identifying, by the host device, an application window associated with the instance of the application in the shadow desktop environment based on an identifier extracted via one or more composition APIs associated with a window composition module associated with the shadow desktop environment;

extracting the application window as image data from the window composition module; and

sending, by the host device, output from the shadow desktop environment to the remote client, wherein the output includes the application window associated with the instance of the application.

2. The method of claim 1, further comprising:

notifying, by the host device, the remote client of the port assigned to the instance of the application; and

storing, by the host device, a mapping between the port and the instance of the application,

wherein the stored mapping comprises first data associated with the port and second data corresponding to a process identifier associated with the instance of the application, and

wherein providing the user input to the instance of the application via the one or more APIs is based on determining, by the host device and based on the mapping, that the user input received through the port is intended for the instance of the application.

3. The method of claim 1, wherein initiating the instance of the application in the remote access mode is in response to receiving, by the host device, a request from the remote client to initiate the instance of the application.

4. The method of claim 1, wherein providing the user input to the instance of the application comprises injecting the user input into an input queue of the instance of the application via the one or more APIs.

5. The method of claim 1, wherein the host device executes a plurality of application instances including the instance of the application, and wherein the user input received through the port is provided to the instance of the application and not another application instance of the plurality of application instances.

6. The method of claim 1, wherein the user input is keyboard input or pointing device input from the remote client.

7. The method of claim 1, wherein identifying the application window comprises:

marking the application window with the identifier via a first API of the one or more APIs, wherein the first API is associated with the instance of the application; and

recognizing the application window based on extracting the identifier during processing by the window composition module via a second API of the one or more APIs, wherein the second API is associated with the window composition module.

8. The method of claim 1, wherein output from applications executing in the shadow desktop environment is not provided to the local user by the host device.

9. The method of claim 1, further comprising:

executing, by the host device, a remote viewer application in the first local desktop environment;

receiving, by the remote viewer application, the output including the application window associated with the instance of the application; and

displaying, by the host device and via the remote viewer application in the first local desktop environment, the application window to the local user.

10. A system comprising:

one or more processors; and

memory storing computer-readable instructions that, when executed by the one or more processors, cause the system to;

provide a shadow desktop environment segregated from a first local desktop environment of the system, output from applications of the first local desktop environment being presented to a local user of the system, output from the shadow desktop environment being presented to a remote client, and instances of applications of the shadow desktop environment being unable to interact with instances of applications of the first local desktop environment;

transform an instance of an application in the first local desktop environment from a local mode to a remote access mode in the shadow desktop environment by;

transferring execution of the instance of the application from the first local desktop environment to the shadow desktop environment;

assigning a port to the instance of the application; and

hooking one or more application programming interfaces (APIs) provided by the instance of the application or a window composition module to generate one or more first hooks, the one or more first hooks being configured such that;

first input, from a remote application viewer application locally executing on the remote client, is redirected to the instance of the application executing in the shadow desktop environment of the system;

output from the instance of the application is redirected to the remote client;

second input, from the first local desktop environment of the system and associated with the instance of the application, is suppressed; and

third input, from the local user of the system and associated with different instances of the application executing on the system, is permitted;

receive user input from the remote client through the port;

provide the user input to the instance of the application using the hooked one or more APIs;

identify an application window associated with the instance of the application in the shadow desktop environment based on an identifier extracted using the hooked one or more APIs

extract the application window as an image from the window composition module; and

send output from the shadow desktop environment to the remote client, wherein the output includes the extracted application window.

11. The system of claim 10, wherein the instructions, when executed by the one or more processors, further cause the system to:

notify the remote client of the port assigned to the instance of the application;

store a mapping between the port and the instance of the application, wherein the stored mapping comprises first data associated with the port and second data corresponding to a process identifier associated with the instance of the application; and

identify, based on the mapping, that the user input received through the port is intended for the instance of the application.

12. The system of claim 10, wherein the instructions, when executed by the one or more processors, cause the system to identify the application window by:

marking the application window with the identifier via a first API of the one or more APIs, wherein the first API is associated with the instance of the application; and

recognizing the application window based on extracting the identifier during processing by the window composition module via a second API of the one or more APIs, wherein the second API is associated with the window composition module.

13. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of a host device, cause the host device to:

provide a shadow desktop environment segregated from a first local desktop environment of the host device, output from applications of the first local desktop environment being presented to a local user on the host device, output from the shadow desktop environment being presented to a remote client, and instances of applications of the shadow desktop environment being unable to interact with instances of applications of the first local desktop environment;

transform an instance of an application in the first local desktop environment from a local mode to a remote access mode in the shadow desktop environment by;

transferring execution of the instance of the application from the first local desktop environment to the shadow desktop environment;

assigning a port to the instance of the application; and

hooking one or more application programming interfaces (APIs) associated with the instance of the application to generate one or more first hooks, the one or more first hooks are configured such that;

first input, from a remote application viewer application locally executing on the remote client, is redirected to the instance of the application executing in the shadow desktop environment of the host device;

output from the instance of the application is redirected to the remote client;

second input, from the first local desktop environment of the host device and associated with the instance of the application, is suppressed; and

third input, from the host device and associated with different instances of the application executing on the host device, is permitted;

receive user input from the remote client through the port;

provide the user input to the instance of the application via the one or more APIs;

identify an application window associated with the instance of the application in the shadow desktop environment based on an identifier extracted via one or more composition APIs associated with a window composition module associated with the shadow desktop environment;

extract the application window as image data from the window composition module; and

send output from the shadow desktop environment to the remote client, wherein the output includes the application window associated with the instance of the application.

14. The non-transitory computer-readable media of claim 13, wherein the instructions, when executed by the one or more processors, further cause the host device to:

notify the remote client of the port assigned to the instance of the application; and

store a mapping between the port and the instance of the application,

wherein the stored mapping comprises first data associated with the port and second data corresponding to a process identifier associated with the instance of the application, and

wherein the instructions, when executed by the one or more processors, further cause the host device to provide the user input to the instance of the application via the one or more APIs based on determining, based on the mapping, that the user input received through the port is intended for the instance of the application.

15. The non-transitory computer-readable media of claim 13, wherein the instructions, when executed by the one or more processors, further cause the host device to initiate the instance of the application in the remote access mode in response to receiving a request from the remote client to initiate the instance of the application.

16. The non-transitory computer-readable media of claim 13, wherein the instructions, when executed by the one or more processors, further cause the host device to provide the user input to the instance of the application by causing the host device to:

inject the user input into an input queue of the instance of the application via the one or more APIs.

17. The non-transitory computer-readable media of claim 13, wherein the host device executes a plurality of application instances including the instance of the application, and wherein the user input received through the port is provided to the instance of the application and not another application instance of the plurality of application instances.

18. The non-transitory computer-readable media of claim 13, wherein the user input is keyboard input or pointing device input from the remote client.

19. The non-transitory computer-readable media of claim 13, wherein the instructions, when executed by the one or more processors, further cause the host device to identify the application window by causing the host device to:

mark the application window with the identifier via a first API of the one or more APIs, wherein the first API is associated with the instance of the application; and

recognize the application window based on extracting the identifier during processing by the window composition module via a second API of the one or more APIs, wherein the second API is associated with the window composition module.

20. The non-transitory computer-readable media of claim 13, wherein output from applications executing in the shadow desktop environment is not provided to the local user by the host device.