WO2023217543A1 - Procédé de fonctionnement d'un système de bureau à distance, système de bureau à distance et support lisible par ordinateur - Google Patents

Procédé de fonctionnement d'un système de bureau à distance, système de bureau à distance et support lisible par ordinateur Download PDF

Info

Publication number
WO2023217543A1
WO2023217543A1 PCT/EP2023/061091 EP2023061091W WO2023217543A1 WO 2023217543 A1 WO2023217543 A1 WO 2023217543A1 EP 2023061091 W EP2023061091 W EP 2023061091W WO 2023217543 A1 WO2023217543 A1 WO 2023217543A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
remote desktop
local
applications
application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2023/061091
Other languages
German (de)
English (en)
Inventor
Ulrich MERTZ
René VÖGELI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Rangee GmbH
Original Assignee
Rangee GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Rangee GmbH filed Critical Rangee GmbH
Publication of WO2023217543A1 publication Critical patent/WO2023217543A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
    • G06F3/1454—Digital output to display device ; Cooperation and interconnection of the display device with other functional units involving copying of the display data of a local workstation or window to a remote workstation or window so that an actual copy of the data is displayed simultaneously on two or more displays, e.g. teledisplay
    • G—PHYSICS
    • G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G2370/00—Aspects of data communication

Definitions

  • 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.
  • 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.
  • 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:
  • 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
  • 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.
  • RDP Remote Desktop Protocol
  • ICA Independent Computing Architecture
  • PColP PC over IP
  • VNC Virtual Network Computing
  • 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.
  • a self-starting server application 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • establishing a connection between Remote Desktop Client and Remote Desktop on a terminal server can follow the following steps:
  • Remote Desktop Client for example in the home office.
  • Server application starts automatically and provides an API for controlling controllable and startable or running programs.
  • Client regularly retrieves a list of controllable and startable or running programs via the server application API.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • local audio and/or video settings can be changed in the client on the remote desktop side, the client comprising the following functions:
  • Changing the output device especially the default output device, changing the output device for an application, adjusting the volume of an application.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 client on the remote desktop side can also be used to perform the following functions:
  • 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.
  • a remote desktop system 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.
  • 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.
  • Fig. 1 is a flowchart for carrying out a method for generating
  • 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.
  • a user 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.
  • 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).
  • VPN Virtual Private Network
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • the server application is opened in a window 341.
  • 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.
  • connection window 311 in Fig. 3c indicates.
  • information from the Server application can be transferred to the client if it runs permanently on the remote desktop server.
  • 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.
  • desktop shortcuts 371 to remote applications that a user can execute, for example, to work.
  • 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.
  • the user triggers one of the remote programs linked to the icons 371.
  • 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.
  • the user decides to look at the window 362 of the previously opened local application.
  • a thumbnail screenshot 366 of the local application is shown.
  • 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.
  • 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.
  • a composite view generated which can be controlled and adjusted by a user through appropriate communication between a client and a server application.
  • 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.
  • Fig. 4b the local program was started and the corresponding window 368 was brought forward without minimizing the view of the remote desktop 330.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé de génération et de commande d'une vue composite d'applications locales sur une interface utilisateur graphique locale d'un client de bureau à distance, l'interface utilisateur graphique locale étant délivrée sur un dispositif côté client local, et le client de bureau à distance étant un ordinateur virtuel ou physique, et un bureau à distance, qui est hébergé par un serveur de bureau à distance, dans un environnement de bureau à distance, de préférence un serveur de terminal, avec des applications à distance. Le procédé comprend les étapes consistant à : générer une interface utilisateur graphique sur le dispositif côté client local afin de commander à distance les applications à distance à partir du dispositif côté client local, l'accès au bureau à distance au moyen du client de bureau à distance étant réalisé selon n'importe quel protocole de bureau à distance ; et générer une vue de l'application à distance sur la base de données de sortie d'affichage de l'application à distance, lesdites données étant reçues par le dispositif côté client local. Au moins un canal de communication supplémentaire est généré entre le client de bureau à distance et le serveur de bureau à distance. Dans une première étape, une application de serveur côté client obtient des informations sur les applications locales, fournit celles-ci à un client sur le côté bureau à distance par l'intermédiaire du canal de communication, et transmet des mises à jour d'informations au client sur le bureau à distance si l'application locale en question a déjà été ouverte. Le client affiche les informations par l'intermédiaire des applications locales dans une vue supplémentaire de l'interface utilisateur graphique de la connexion de bureau à distance de telle sorte qu'un utilisateur peut interagir avec la vue et peut effectuer une sélection à partir d'une liste de commandes qui sont transmises du client au serveur côté client par l'intermédiaire du canal de communication et du serveur côté client à l'application locale. L'application locale est exécutée sur le client de bureau à distance, et l'utilisateur peut masquer des applications locales dans la vue du client sur le bureau à distance ou marquer les applications en tant que favoris. La priorité des applications est modifiée pendant une communication entre le client et l'application de serveur côté client, les mises à jour d'informations étant transmises avec une fréquence variable sur la base de la priorité.
PCT/EP2023/061091 2022-05-11 2023-04-27 Procédé de fonctionnement d'un système de bureau à distance, système de bureau à distance et support lisible par ordinateur Ceased WO2023217543A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102022111859.2 2022-05-11
DE102022111859.2A DE102022111859A1 (de) 2022-05-11 2022-05-11 Verfahren zum betreiben eines remote desktop systems, remote desktop system und computerlesbares medium

Publications (1)

Publication Number Publication Date
WO2023217543A1 true WO2023217543A1 (fr) 2023-11-16

Family

ID=86383000

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/061091 Ceased WO2023217543A1 (fr) 2022-05-11 2023-04-27 Procédé de fonctionnement d'un système de bureau à distance, système de bureau à distance et support lisible par ordinateur

Country Status (2)

Country Link
DE (1) DE102022111859A1 (fr)
WO (1) WO2023217543A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118331882A (zh) * 2024-05-09 2024-07-12 深圳市芯睿视科技有限公司 测试方法、主控设备、受控设备和测试系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090210817A1 (en) * 2008-02-15 2009-08-20 Microsoft Corporation Mechanism for increasing remote desktop responsiveness
US9032325B2 (en) * 2001-06-08 2015-05-12 Real Enterprise Solutions Development B.V. Management of local applications in local and remote desktops in a server-based computing environment
US20210152626A1 (en) * 2012-03-02 2021-05-20 Citrix Systems, Inc. Reverse Seamless Integration Between Local and Remote Computing Environments
WO2021130500A1 (fr) * 2019-12-23 2021-07-01 Ultima Business Solutions Limited Système et méthode d'orchestration de processus automatisés

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102010021130A1 (de) 2010-05-21 2011-11-24 Xompu Gmbh Vorrichtung und Verfahren zur Übertragung, Steuerung und Integration von Lokal auf einem Computer Client ausgeführten Anwendungen in entfernt auf Server-Computern ausgeführte Remote Desktops
US8866701B2 (en) 2011-03-03 2014-10-21 Citrix Systems, Inc. Transparent user interface integration between local and remote computing environments

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9032325B2 (en) * 2001-06-08 2015-05-12 Real Enterprise Solutions Development B.V. Management of local applications in local and remote desktops in a server-based computing environment
US20090210817A1 (en) * 2008-02-15 2009-08-20 Microsoft Corporation Mechanism for increasing remote desktop responsiveness
US20210152626A1 (en) * 2012-03-02 2021-05-20 Citrix Systems, Inc. Reverse Seamless Integration Between Local and Remote Computing Environments
WO2021130500A1 (fr) * 2019-12-23 2021-07-01 Ultima Business Solutions Limited Système et méthode d'orchestration de processus automatisés

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118331882A (zh) * 2024-05-09 2024-07-12 深圳市芯睿视科技有限公司 测试方法、主控设备、受控设备和测试系统

Also Published As

Publication number Publication date
DE102022111859A1 (de) 2023-11-16

Similar Documents

Publication Publication Date Title
DE69817158T2 (de) Benutzerschnittstellen-Mechanismus zur Manipulierung von Kontexten in Computerverwaltungsapplikationen
DE69805990T2 (de) Verfahren und vorrichtungen zum zugriff auf information und einheiten in mehreren arbeitsflächen
DE69808501T3 (de) Verfahren zum erstellen von makrobefehlen für ein hausnetzwerk
DE69517029T2 (de) Hilfsanforderungssystem für vernetzte arbeitstationen, welches das fernausführen von dateien erlaubt
DE69931024T2 (de) Internet-basierter aktualisierungsdienst für eine programmierbare steuerungsvorrichtung
DE69523593T2 (de) Vorrichtung und verfahren zur aufteilung der anwendung in einer graphischen benutzerschnittstelle
DE69433754T2 (de) Verfahren und Systeme zum Integrieren von verschiedenen Vertreterleistungsverbesserungsmodulen in einer Anrufzentrale
DE60311608T2 (de) Verfahren und Vorrichtung zum Schalten der Steuerung zwischen verbundenen Vorrichtungen
DE60029774T2 (de) Videokonferenzsystem
DE102012214941B4 (de) Mobilkommunikationsgerät und Verfahren zum Wechseln einer Anwendungsschnittstelle
DE69129536T2 (de) Objektbasiertes rechnersystem
DE19522185A1 (de) Ein Verfahren und System zur dynamischen Übersetzung zwischen verschiedenen grafischen Benutzeroberflächen-Systemen
EP2643752A1 (fr) Procédé et dispositif pour l'affichage d'une interface utilisateur graphique d'un ordinateur portable, sur un appareil d'affichage externe
DE112012001230T5 (de) System und Verfahren zum Verteilen von Benutzerschnittstellen-Gerätekonfigurationen
DE202017105691U1 (de) Intelligente Assistenz für wiederholte Aktionen
WO2007128512A1 (fr) Procédé et système permettant d'obtenir un menu de sélection associé à un symbole affiché
DE102012219119A1 (de) Intelligente Fenstererstellung in einer grafischen Benutzeroberfläche
DE10247165A1 (de) System und Verfahren für eine mobile Rechenvorrichtung zum Steuern von Geräten
DE10247114A1 (de) Mobile Rechenvorrichtung mit Verfahren und System zum Unterbrechen einer Inhaltsdurchführung unter Geräten
DE4434878A1 (de) Fern-Anzeige von Objekten und Cursorbewegungen in einem Konferenzsystem
EP3084742A1 (fr) Dispositif portable de commande à distance d'une pluralité d'appareils électroménagers, système, procédé correspondant et produit logiciel informatique
EP3570164A1 (fr) Procédé et système de génération d'une application mobile à partir d'une application bureau
WO2023217543A1 (fr) Procédé de fonctionnement d'un système de bureau à distance, système de bureau à distance et support lisible par ordinateur
WO2007128514A1 (fr) Procédé et dispositif pour établir des fenêtres de communication adaptées pour la communication avec un partenaire de communication dans une application sur un appareil de terminaison d'un utilisateur
DE112013000749T5 (de) Interaktives System und Verfahren für intelligente Fernsehgeräte

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23723844

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23723844

Country of ref document: EP

Kind code of ref document: A1