WO2023217543A1

WO2023217543A1 - Method for operating a remote desktop system, remote desktop system, and computer-readable medium

Info

Publication number: WO2023217543A1
Application number: PCT/EP2023/061091
Authority: WO
Inventors: Ulrich MERTZ; René VÖGELI
Original assignee: Rangee GmbH
Priority date: 2022-05-11
Filing date: 2023-04-27
Publication date: 2023-11-16
Also published as: DE102022111859A1

Abstract

The invention relates to a method for generating and controlling a composite view of local applications on a local graphical user surface of a remote desktop client, wherein the local graphical user surface is output on a local client-side device, and the remote desktop client is a virtual or physical computer, and a remote desktop, which is hosted by a remote desktop server, in a remote desktop environment, preferably a terminal server, with remote applications. The method has the steps of: generating a graphical user surface on the local client-side device in order to remotely control the remote applications from the local client-side device, the accessing of the remote desktop by means of the remote desktop client being carried out according to any remote desktop protocol; and generating a view of the remote application on the basis of display output data of the remote application, said data being received by the local client-side device. At least one additional communication channel is generated between the remote desktop client and the remote desktop server. In a first step, a client-side server application obtains information on the local applications, provides same to a client on the remote desktop side via the communication channel, and transmits information updates to the client on the remote desktop if the local application in question has already been opened. The client displays the information via the local applications in an additional view of the graphical user surface of the remote desktop connection so that a user can interact with the view and can select from a list of commands which are transmitted from the client to the client-side server via the communication channel and from the client-side server to the local application. The local application is ran on the remote desktop client, and the user can mask local applications in the view of the client on the remote desktop or mark the applications as favorites. The priority of the applications is changed during a communication between the client and the client-side server application, whereby the information updates are transmitted with varying frequency on the basis of the priority.

Description

METHOD FOR OPERATING A REMOTE DESKTOP SYSTEM, REMOTE DESKTOP SYSTEM AND COMPUTER READABLE MEDIUM

TECHNICAL FIELD

The invention relates to a method for operating a remote desktop system, consisting of a remote desktop client and a remote desktop server, which hosts a remote desktop in a remote desktop environment, the remote desktop connection being established following a remote desktop protocol.

STATE OF THE ART

The use of multimedia applications on terminal servers is generally very unperforming and unsatisfactory. Applications that need to transfer large amounts of data and/or require a high refresh rate, such as watching videos or participating in video conferences, place a strain on the server and network connection because the remote protocols are not designed for multimedia applications.

OBJECT OF THE INVENTION

The object of embodiments of the invention is to provide a method with which a user can particularly easily use local applications on a remote desktop client and remote applications on a remote desktop, for example on a terminal server, in parallel, a remote desktop system that is suitable to carry out the method and to provide a computer-readable medium comprising code for instructing processors of a remote desktop system.

PRESENTATION OF THE INVENTION

This task is solved via the method according to claim 1, the remote desktop system according to claim 9 and the computer-readable medium according to claim 10. Advantageous embodiments of the invention are defined by the dependent claims provided. The features of the exemplary embodiments described below can be combined with one another unless this is explicitly denied.

According to one embodiment of the invention, a method for generating and controlling a composite view of local applications on a local graphical user interface of a remote desktop client, the remote desktop client being a virtual or physical computer, and one of a remote desktop Server-hosted remote desktop in a remote desktop environment, for example a terminal server, with remote applications, the method comprising the following steps:

Generating a graphical user interface on a local client-side device for remotely controlling the remote applications from the local client-side device, with the Remote Desktop client accessing the Remote Desktop according to any Remote Desktop protocol,

Generate a view of the remote application based on display output data of the remote application received from the local client-side device.

The method according to the invention is characterized in that the communication channel available for the remote desktop connection is additionally used or at least one further communication channel is created between the remote desktop client and the remote desktop server and used in such a way that a client-side server application receives information about the local in one step obtains applications and provides them via the communication channel to a client on the remote desktop side and sends information updates to the client on the remote desktop if the local application in question is already open, with the client storing the information about the local applications in another View on the graphical user interface, the view comprising a list of local applications, so that a user can interact with the view and select for each list entry from a list of commands that are sent to the client via the communication channel or the further communication channel when activated client-side server and from the client-side server to the local application, with the local application running on the remote desktop client, where the user can hide or mark local applications as favorites in the view of the client on the remote desktop, with a priority of the Applications are changed during communication between client and client-side server application, whereby the information updates are sent at different frequencies depending on the priority.

In the context of this application, a remote desktop client is understood to mean a virtual or physical computer, for example a laptop or a computer with low computing capacity, as is the case with a thin client, which is capable of following a remote desktop protocol, such as for example, the proprietary Remote Desktop Protocol (RDP) and the Independent Computing Architecture (ICA) or PC over IP (PColP) or Virtual Network Computing (VNC) to gain access to a remote desktop. The Remote Desktop Client can use any operating system, such as Windows, Linux or MaxOS.

A remote desktop server, in the context of this application, is also a virtual or physical computer and is used to host the remote desktop in a remote desktop environment, such as a terminal server. The remote desktop is a Windows desktop, such as a desktop on the Windows Terminal Server, a desktop on the Azure Virtual Desktop, or any other Windows desktop system that runs on a remote desktop system.

The client-side server application can be, for example, a self-starting server application, a communication server or a web server, which is started automatically when the user's end device is started or when the remote desktop client is started and is suitable for controlling local programs. Via an application programming interface (API), the client is informed on the remote desktop side which functions are available for which local applications on the local remote desktop client and/or which functions can be activated for remote access. The functions can, for example, be added or removed by the user or an administrator in the server application on the Remote Desktop Client. These functions correspond to the commands that the user can send on the remote desktop via the client, so that only software instructions are sent from the client to the server application. Additional information that the server application provides to the client includes, for example, an icon, a name, a thumbnail screenshot, and a location and dimension of a local application. For example, this information becomes local in the list of the client's view (GUI) on the remote desktop Applications are taken into account in such a way that for running applications, thumbnail screenshots of the local window are sent at regular intervals and are displayed in the client's view next to the respective list entry for the corresponding local application, while for local applications that are not running, only the icon is shown next to it corresponding list entry is shown. For example, the client can be permanently active on the Remote Desktop Server and wait for the request from the server application and, when a user establishes a remote desktop connection, show the local applications available on his Remote Desktop Client in a view. However, it is also possible that the user only starts the client after the remote desktop connection has been established.

The additional communication channel can be formed, for example, by a TCP channel between the remote desktop client and the remote desktop server. However, it is also possible to run communication via a side channel embedded in the respective Remote Desktop protocol, also called a virtual channel. Communication via a side channel of a Remote Desktop Protocol is preferably used, and a TCP channel is used if a Remote Desktop Protocol does not support the Virtual Channel functionality. In many use cases, this eliminates the need for the terminal server to be able to reach the ThinClient (the Remote Desktop Client) via a TCP connection. This is not necessarily possible, especially in home office setups and particularly secure networks, so the solution of using virtual channels of the remote desktop protocols overcomes this problem.

The information updates that are sent from the client-side server to the client on the remote desktop can, for example, be displayed if the user “hovers” his or her cursor over the list entry of the corresponding application for a while without closing the mouse button actuate. Alternatively, the list of local applications is maintained in the client's view. This means that the list entries for running local applications show the information, which receives updates at regular intervals, at the position where the icon of the application is shown in the list entries for local applications that are not running. The information includes, for example, the position and size of a window of a running local application. This makes it easier for the user to track the progress of individual processes on their local device, for example during a download, a compilation process or similar processes that may take a long time.

The user hides local applications in the client on the remote desktop or marks them as favorites, changing the priority of the applications in communication between the client and the client-side server. Prioritization means that some information is sent more frequently than others. For a download that the user is very interested in completing, it is advisable, for example, to favorite the download manager, which means that updates for this application are sent more frequently, for example in the form of miniature screenshots, so that the user is always informed of the progress image is. The prioritization can also be taken into account by the communication channel when transmitting the updates. This can ensure that information that is particularly relevant to the user has priority when transmitted to the client on the remote desktop and is delivered even if the data transfer rate is limited.

Another local application that can be started and favorited by the user on the remote desktop is, for example, the task manager. This offers the user the opportunity to monitor local applications and in particular to view the memory and/or processor utilization of the client-side server. This allows the user to decide to terminate a locally running application and, if necessary, “move” it to the Remote Desktop Server or start it on the Remote Desktop Server. This is of particular relevance for a remote desktop client with limited capacities, particularly limited storage and/or computing capacity.

The method thus provided offers the advantage that a user can use a remote desktop client with limited computing capacity to run remote applications on a remote desktop server and, via the client on the remote desktop, with local applications running on the remote desktop client are located to interact and give commands. This means that software instructions can be sent to the local applications via the client on the Remote Desktop while the local application is running on the Remote Desktop Client. The client on the remote desktop provides an interface for accessing and controlling running graphical interface applications and their information. Local applications include, for example Multimedia applications, conference solutions, as well as office applications, emails and graphic editing. This procedure eliminates the remote desktop connection as a bottleneck.

For example, establishing a connection between Remote Desktop Client and Remote Desktop on a terminal server can follow the following steps:

1. User starts Remote Desktop Client, for example in the home office.

2. Server application starts automatically and provides an API for controlling controllable and startable or running programs.

3. (Optional if required for remote desktop access) User connects to VPN.

4. User establishes remote desktop connection.

5. User opens client view on Remote Desktop.

6. Client regularly retrieves a list of controllable and startable or running programs via the server application API.

7. The user finds a list of local programs that are already running or can be started in the client view and, when clicking on a list entry, sees a list of available commands, e.g. -Start, -Focus, -Bring to Front.

8. User interacts with local programs and remote applications simultaneously without closing or minimizing the remote desktop connection.

The list of the client's view can, for example, be sorted by the user and is structured in such a way that each list entry corresponding to an available local application is displayed in a line of the list with the name of the local application and the associated icon, or a miniature screenshot. For example, the icon or thumbnail screenshot is displayed on the left or right side next to the name of the local application in the line of the list. The thumbnail screenshot can be displayed instead of the icon when the local application is running on the Remote Desktop Client. To call up the list of commands for a respective local application, the user clicks on the corresponding list entry with their mouse, whereby the commands are listed, for example, in the form of a context menu.

Advantageously, the list of commands that the user can give includes starting a local application, focusing on a local application, minimizing a local application, maximizing a local application, closing a local application, and bringing a local application forward, wherein the view of the local application or the local applications can be kept at the front, in particular so that parallel work on at least one Remote application and at least one local application is possible.

Thus, the user of the Remote Desktop Client can use the client on the Remote Desktop to select a local application that may already be running and is located on the Remote Desktop Client and is/is being executed there, and focus on this local application so that his input can be used to control it serve the local application and put the local application at the front so that the user sees the graphical interface of the local program and can make entries there while the remote desktop connection view remains open. Advantageously, the user can activate a function that fixes the local application at the front, so that the focus can switch to the remote desktop and the user can work on the remote application while the local application remains visible to him. Other commands for controlling the open windows of local applications include minimizing, maximizing, closing, moving and resizing the window. For example, it is also possible to change the local volume settings of the Remote Desktop Client via the client on the Remote Desktop. This can be advantageous, for example, if the remote desktop connection obscures the local taskbar and volume settings.

According to an advantageous embodiment of the invention, TCP and/or UDP-based transmission techniques are used for the communication protocol of the communication channel or channels between the client-side server application and the client on the remote desktop and the communication takes place via a wired or wireless computer network, whereby the Communication channel or channels can be freely selected and/or the communication preferably runs via side channels of the Remote Desktop Protocol and switches to a TCP channel if the Remote Desktop Protocol does not support the functionality of side channels. The use of virtual channels (side channels) eliminates the need for the terminal server to be able to reach the ThinClient (the remote desktop client) via a TCP connection and is not essential, especially in home office setups and particularly secure networks possible. The process is therefore particularly suitable for use in the home office and for a variety of remote desktop protocols, or uses them advantageously.

Advantageously, the local application or the local applications that were started by the user, in particular started via the client on the remote desktop, are displayed, in particular without minimizing the view of the remote desktop connection on the local client-side device. A user can thus run running local applications, in particular multimedia applications, e-mail, graphics applications and conference solutions, for the transmission of which the remote desktop connection represents the bottleneck due to the image repetitions, on his local device and, if necessary, move them to the front, but without the view of the remote desktop connection to minimize or abandon. If you focus on a local application and bring it to the foreground, no graphical information about the communication channel and, so to speak, only an image of the local application is projected onto the remote desktop, but rather the actual local application that is running on the remote desktop client brought forward for use with their GUI. For example, if the information that the server application communicates to the client on the remote desktop side includes the location and dimension of the local application window, the client can place a contentless window on the remote desktop "underneath" the local application window, which corresponds to the position and dimension of the local application window, enabling combined handling of local applications and remote applications and enabling functions such as AeroSnap to be executed. For this purpose, it can be advantageous to transmit the information regarding the size and position of the window of the local application at close intervals, so that the user has a particularly fluid feeling. If a user “pins” an application to the front, i.e. marks it so that it should always be in the foreground, the client can also do this for the copied contentless window and the user can continue working on the remote desktop without the remote desktop connection immediately opening the application covered again.

According to one embodiment, the information updates that are sent from the client-side server to the client on the remote desktop, in particular at regular intervals, include in particular miniature screenshots reduced in size, provided that the local application in question is already open. For example, the thumbnail screenshot of the local application can be displayed, if the user hovers over the list entry of the corresponding application for a while without pressing the mouse button. Alternatively, the list of local applications is maintained in the client's view as described above, that is, the list entries for running local applications show a miniature screenshot, updated at regular intervals, at the position where the icon for the list entries of local applications that are not running the application is shown.

It is advantageous if the client-side server application automatically generates quick access functions for the started local applications, in particular multimedia applications, and transmits them to the client on the remote desktop. Such quick access functions include, for example, answer/hang up a call, screen share, mute or turn camera on/off in case the local application is a conference solution, or they include, for example, fast forward, rewind, go back to the beginning, next/next content, play/pause , in the case of multimedia applications. However, it can be advantageous if a user can define their own quick access functions by telling the server application which button is selected and defining under which name or symbol this function should be listed in the client.

Again preferably, the list order is changed by prioritizing the local applications. The list means the overview of the local applications listed in the client with which the client can interact. By allocating different list positions, some information is sent more frequently than others. For a download that the user is very interested in completing, it is advisable, for example, to favorite the download manager, which means that updates for this application are sent more frequently, for example in the form of miniature screenshots, so that the user is always informed of the progress image is.

Advantageously, local audio and/or video settings can be changed in the client on the remote desktop side, the client comprising the following functions:

changing a volume of an output device,

Changing the output device, especially the default output device, changing the output device for an application, adjusting the volume of an application. This means that the volumes of the output devices, for example a headset and a loudspeaker, that are connected to the remote desktop client can be changed via the client on the remote server. In addition, a first application, which is running locally, for example, can be assigned a first output device and a second output device can be assigned to a second application, which is also running locally, and a third application, which is a remote application. For example, a user can only have conference software, such as MS Teams, output on their headset and all other sounds can be output via laptop speakers, which creates a particularly uninterrupted entertainment experience for them, especially if the conference solution is running locally on their remote desktop client running. In addition, adjusting the volumes of the applications offers the advantage that the ratio of the volumes of the applications to one another can be adjusted via the client. To do this, a user can, for example, call up a menu in the client in which all applications running locally on the Remote Desktop Server and on the Remote Desktop Client are listed, assign each of them a local or remote output device and adjust the volume levels of the applications in the client. This method also provides a combined sound control with which settings on the remote desktop and the remote desktop client can be advantageously combined.

In the client on the remote desktop side, various power management functions of the remote desktop client can be carried out, for example the following functions: shutdown, restart, standby, information about the battery level, logout of the locally logged in user, locking the local device, adjusting the screen brightness the local client-side device.

For example, if the user wants to switch it off via the client's function on the remote desktop, the remote desktop client can first save all open saves in the local applications and then, following the remote desktop protocol through which the remote desktop connection is established, the connection to the Remote Desktop and then the Remote Desktop Client shut down directly. This eliminates the inconvenient “double” logout/shutdown when logging out of the workplace.

The following functions can also be carried out with the client on the remote desktop side:

Safely eject a locally connected USB stick, eject a CD drive.

This allows you to easily interact with the hardware of your end device, which serves as a remote desktop client, and to control the local machine, the remote desktop client, from the remote desktop.

The client on the remote desktop side can also be used to perform the following functions:

Changing from a first view on the local client-side device to a second view on the local client-side device, particularly if the local client-side device uses multiple screens for output, changing the resolution,

Enabling and disabling individual parts of the local client-side device. It is particularly advantageous if the resolution and dimension of the remote desktop connection can also be changed. The user can thus handle the remote desktop in a similar way to his local workstation and in a particularly intuitive way, even after the connection has been established, add or deactivate screens that are understood to be part of the local client-side device. This is advantageous, for example, if multiple monitors with different resolutions have been added to the client-side device and the user wants to adjust the resolution of a screen or remove it again.

With a further embodiment of the invention, a remote desktop system is provided which has a remote desktop client, preferably a virtual or physical computer, and a remote desktop server, which is formed by a virtual or physical computer and is suitable for a remote desktop a remote desktop environment, for example in a terminal server, wherein the remote desktop client accesses a remote desktop on the remote desktop server according to a remote desktop protocol, wherein the remote desktop client is suitable for running local applications and the remote desktop is suitable for executing remote applications, and wherein there is an additional communication channel between the remote desktop client and the remote desktop server, via which a user can control the local application from the remote desktop and via which information about the local applications depends on a priority the applications can be sent at different frequencies. The remote desktop system thus provided is therefore suitable for carrying out the method described above.

According to a further embodiment of the invention, a computer-readable medium comprising code to cause processors of a remote desktop system, in particular of the aforementioned remote desktop system, to carry out one of the methods described above.

BRIEF DESCRIPTION OF THE FIGURES

Further advantageous embodiments can be derived from the following description and the drawings. In it shows

Fig. 1 is a flowchart for carrying out a method for generating and

Controlling a Composite View;

Fig. 2 a remote desktop system;

Figure 3 pseudo-screenshots of a local client-side device demonstrating connection setup and some steps of a method for generating and controlling a composite view;

Fig. 4 Pseudo screenshots of a local client-side device demonstrating further steps of a method for generating and controlling a composite view.

DETAILED DESCRIPTION OF THE FIGURES

The invention will be generally described with reference to all reference numerals. Details are explained in connection with the respective figure. The steps for carrying out a method 100 for generating and controlling a composite view are described with reference to FIG. 1 in combination with a remote desktop system 200 from FIG. 2.

In a first step 110, a user, not shown, starts his remote desktop client 220, for example a laptop, with local applications 260 and a local graphical user interface that is output on a local client-side device. For example, the user is in the home office. A server application 240 is then started in a second step 120. This preferably happens automatically immediately after the first step 110 when starting up the remote desktop client 220. The server application 240 provides an API for controlling controllable and startable or running local programs 260. If this is provided for by the Remote Desktop Protocol, in a next step 130 a connection is established between the Remote Desktop Client and a Virtual Private Network (VPN). Otherwise, this step 130 is skipped and the remote desktop connection is established directly in the fourth step 140 in accordance with known remote desktop protocols via a wired or wireless network 210. A graphical interface for operating the remote desktop 230 is built on the local client-side device, and the user can select from a selection of remote applications 270 and start them. The user then opens the client 250 on the remote desktop 230 in the next step 150. In the following step 160, the client calls 250 via an additional channel, which is, for example, a side channel of a remote desktop protocol or an additional TCP channel can, the information 251 from the server application 240, which contains a list of controllable and startable or running programs 260. In a next step 170, the user is presented with the list of available local programs 260 in the client 250 and is allowed to choose from a list of commands which, for example, enable starting a local application 260. If the user gives a command 252, this is sent to the server application 240 via the communication channel and translated from there to the local application 260 via the API. Accordingly, the user only sends software instructions to operate their local programs. If the user has started both a remote application 270 on the remote desktop 230, which is executed by the remote desktop server 235, and a local application 260, which is executed by the remote desktop client 220, he can now use 180 simultaneously in a next step local programs 260 and remote Programs 270 interact without minimizing or closing the remote desktop connection 210.

However, this only represents one embodiment of a method 100 for generating and controlling a composite view. It is clear to the person skilled in the art that, depending on the type of remote desktop server 235 and the remote desktop client 220, it can be advantageous for the client 250 for example, runs permanently on the remote desktop server 235 and when the remote desktop client 220 establishes a connection to the remote desktop server 235, the client 250 checks whether a server application 240 is active on the remote desktop client 220 and information 251 is already available during the connection establishment local applications 260 are accessed, so that the user already finds an open view of the client 250 when setting up the graphical user interface of the remote desktop 230.

Since this invention relates to a method for generating and controlling a composite view of local applications on a local graphical user interface of a remote desktop client and a remote desktop, the method is explained in more detail below using pseudo screenshots. These are in no way to be interpreted as restrictive when interpreting the claims, but merely serve to provide better clarity.

3a to 3h show a local client-side device at various times in performing a method for generating and controlling a composite view of local applications on a local graphical user interface of a remote desktop client and a remote desktop. First, the graphical interface 320 of the local desktop is shown, on which a local application is opened in a window 362. Additional desktop shortcuts 361 indicate additional local applications on the Remote Desktop Client. The taskbar 301 with local volume settings 321 indicates via the symbol 322 that a VPN connection is already active. In Fig. 3b the server application is opened in a window 341. Here the user or an administrator can enable additional local programs for remote access. For example, the server application carries out an automatic scan on the remote desktop client and lists all programs that it has found and considers to be controllable. The user then connects to the remote desktop server, as the connection window 311 in Fig. 3c indicates. During the connection, for example, information from the Server application can be transferred to the client if it runs permanently on the remote desktop server. In Fig. 3d, the remote desktop client is connected to the remote desktop and a graphical user interface 330 of the remote desktop is generated, as indicated by the connection bar 331 and the modified taskbar 302. On the graphical user interface 330 of the remote desktop there are desktop shortcuts 371 to remote applications that a user can execute, for example, to work. At the bottom right corner of the graphical user interface 330 of the remote desktop is a view 350 of the client, which has already prepared the information from the server application and keeps a list 363 of available local programs. The client can have been started by the user or can be started automatically when the Remote Desktop Client connects to the Remote Desktop Server. The list 363 of local applications can be sorted, for example, according to favorites and/or divided into open and startable programs. In this case, the user triggers one of the remote programs linked to the icons 371. In Fig. 3e, a window 372 of the remote application is open and the user, for example, works with the remote application as usual with his local input devices connected to the client-side device. In Fig. 3f, the user decides to look at the window 362 of the previously opened local application. When hovering the cursor 303 over the corresponding list entry 365 in the list 363 of the view 350 of the client 350, a thumbnail screenshot 366 of the local application is shown. In order to be able to work better with the local application, the user in Fig. 3g has given the command to bring the window 362 forward so that he can work with it. The remote desktop connection remains open and the view 330 of the remote desktop is not minimized. The local program continues to run locally on the Remote Desktop Client and Window 362 is also on the local device, so no further graphical data or similar is transferred. In Figure 3h, the user has adjusted the ratio of the local program 362 and remote application 372 windows to maximize use of the local client-side device for output. The server application helps in conjunction with the client by obtaining information about the position and size of the window 362 and taking this into account when dividing the screen. For example, a contentless window is created on the remote desktop and placed below the local window 362. The client enables interaction with windows 362 of local applications as well as windows 372 of remote applications, for example via AeroSnap. Thus is a composite view generated, which can be controlled and adjusted by a user through appropriate communication between a client and a server application.

In Fig. 4a, the state of the graphical user interface 330 of the remote desktop from Fig. 3g is repeated. The user has already opened a window of a local application 362 and a window of a remote application 372 and has now used the cursor 303 to press a second list entry 3651 of the client's view 350, the list entry 3651 corresponding to a second local application that is not yet was started. The only available command 367 is to start the second local program. In Fig. 4b, the local program was started and the corresponding window 368 was brought forward without minimizing the view of the remote desktop 330. In this example, this second local program is a communication program. The user first minimizes the window 368 of the second local application using the button 369 and divides the monitor area maximally between the window 362 of the first local program and the window 372 of the remote program and works with both simultaneously. To do this, he can mark the window 362 of the local application as “always on top”, for example via the view 350 of the client. In Fig. 4d, the user receives a notification 355 from the minimized client that a call is incoming to his locally running communication program and is provided with two quick access functions 356 with which he can react directly. When activated, only one software instruction is sent from the client to the server application and then executed locally via the API in the second local application. In Figure 4e, the user has answered the incoming call and the second local program window 368 has been brought forward. The user can control the locally running program as usual using the buttons 369 shown.

The present disclosure enables the person skilled in the art to implement the particularly advantageous combination of method steps in the respective remote desktop system.

Claims

Patent claims

1. Method for generating and controlling a composite view of local applications (260) on a local graphical user interface (320) of a remote desktop client (220), the local graphical user interface (320) being output on a local client-side device and being the remote desktop client (220) is a virtual or physical computer, and a remote desktop (230) hosted by a remote desktop server (235) in a remote desktop environment, for example a terminal server, with remote applications (270). :

Generating a graphical user interface (330) on the local client-side device for remotely controlling the remote applications (270) from the local client-side device, wherein the remote desktop client (220) accesses the remote desktop (230) according to any remote desktop protocol takes place, generating a view (372) of the remote application (270) based on display output data of the remote application (270) received from the local client-side device, characterized in that the communication channel (210) available for the remote desktop connection is additionally used in this way is or at least one further communication channel is created between the remote desktop client and the remote desktop server and used in such a way that a client-side server application (240) obtains information (251) about the local applications (260) via the communication channel in one step and sends it to one Provides client (250) on the remote desktop (230) side and sends information updates (251) to the client (250) on the remote desktop (230) if the relevant local application (260) is already open, the Client (250) displays the information (251) about the local applications (260) in a further view (350) on the graphical user interface (330), the view (350) comprising a list (363) of the local applications (260). , so that a user can interact with the view (350) and select from a list of commands (367) for each list entry (365, 3651), which when activated by the client (250) are sent to the client-side server via the communication channel or the further communication channel (240) and are sent from the client-side server (240) to the local application (260), the local application (260) being executed on the remote desktop client (220), with the user in the view (350) of the client (240) 250) on the remote desktop (230) can hide local applications (260) or mark them as favorites, with a priority of the applications (260) in communication between client (250) and client-side server application (240), whereby the information updates (251) are sent at different frequencies depending on the priority.

2. The method according to claim 1, characterized in that the list of commands (367) includes the following actions: starting a local application (260), focusing on a local application (260), minimizing a local application (260), maximizing a local application (260), closing a local application (260), and bringing a local application (260) forward, wherein the view (362) of the local application (260) or the local applications (260) are kept at the front can, in particular so that parallel work on at least one remote application (270) and at least one local application (260) is possible.

3. The method according to claim 2, characterized in that the communication protocol of the communication channel or channels between the client-side server and the client uses transmission techniques based on the remote desktop TCP and / or UDP and the communication takes place via a wired or wireless computer network and the Communication channel or channels can be freely selected and/or that communication preferably runs via side channels of the Remote Desktop Protocol and switches to a TCP or UDP channel if the Remote Desktop Protocol does not support the functionality of side channels.

4. The method according to claim 3, characterized in that the local application (260) or the local applications (260) that were started by the user, in particular via the client (250) on the remote desktop, are displayed, in particular without minimizing the graphical user interface (330) of the remote desktop connection on the local client-side device.

5. Method according to one of the preceding claims, characterized in that the information updates (251) include miniature screenshots (366) that are reduced in size.

6. Method according to one of the preceding claims, characterized in that the client-side server application (240) automatically generates quick access functions (356) for the started local applications (260), in particular multimedia applications, and sends them to the client (250) on the remote desktop (230 ) transmitted.

7. The method according to any one of the preceding claims, characterized in that the user can hide the view (350) of the client (250) on the remote desktop (230) or mark local applications (260) as favorites, whereby an order of the list ( 363) is changed.

8. Method according to one of the preceding claims, characterized in that local audio and/or video settings can be changed in the client (250) on the remote desktop (230) side, the client (250) comprising the following functions: changing a volume of an output device,

Changing the output device, especially the default output device, changing the output device for an application, adjusting the volume of an application.

9. Remote desktop system (200), comprising a remote desktop client (220), preferably formed by a virtual or physical computer, and a remote desktop server (235), which is formed by a virtual or physical computer and is suitable for a remote Desktop (230) in a remote desktop environment, for example in a terminal server, wherein the remote desktop client (220) accesses a remote desktop (230) on the remote desktop server (235) according to a remote desktop protocol, wherein the Remote Desktop Client (220) is suitable for executing local applications (260) and the Remote Desktop (230) is suitable for executing remote applications (270), and wherein a side channel or an additional communication channel between the Remote Desktop Client (220) and the Remote Desktop Server (235) is present, via which a user can control local applications (260) from the Remote Desktop (230) and via which information (251) can be sent at different frequencies via the local applications (260) depending on a priority of the applications (260).

10. Computer-readable medium comprising code for causing processors of a remote desktop system (200), in particular a remote desktop system (200) according to claim 9, to carry out a method for generating and controlling a composite view according to any one of claims 1 to 8 .