HTML5 Remote Desktop Transcoding Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional remote desktop protocols require proprietary software and browser plug-ins, limiting user access across different platforms and environments, and are cumbersome for users, as they are not platform-independent and often require specific installations on client devices.
Innovation Solution
A transcoding server that translates user input requests from web browsers into compatible protocols for remote desktop clients and vice versa, using HTML5 for platform-independent access to remote machines, eliminating the need for proprietary protocols and plug-ins, and enabling real-time rendering of remote desktops across various devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional remote desktop protocols are used, then remote desktop access is enabled, but proprietary software and browser plug-ins are required, limiting platform independence
Solution Approach 1:
A transcoding server acts as an intermediary between the web browser and the remote desktop protocol. The server receives HTTP requests from the browser, translates them into the appropriate remote desktop protocol commands, and sends responses back. This mediator eliminates the need for proprietary client software on the user's device, as all protocol translation occurs on the server side, thereby achieving platform independence while maintaining remote desktop functionality
Solution Approach 2:
The patent replaces the traditional mechanical approach of installing proprietary software clients on user devices with a web-based HTTP interface. Instead of requiring specialized remote desktop client applications, the system uses standard web browsers with HTTP support, substituting the complex software installation mechanism with a simple web-based access method that works across all platforms
2Adaptability or versatility
If proprietary remote desktop protocols are used, then remote desktop functionality is achieved, but user access across different platforms is limited
Solution Approach 1:
The transcoding server provides universal access by supporting multiple remote desktop protocols (such as RDP, VNC, SSH) through a single HTTP interface. The server can translate between different protocols, allowing users to access various types of remote desktops using the same web browser, thereby achieving multi-functionality and broad cross-platform accessibility without requiring different clients for different protocols
3Ease of operation
If protocol translation is performed in real-time, then seamless remote desktop access is enabled, but processing delays may occur
Solution Approach 1:
The system performs preliminary actions by pre-establishing the transcoding server infrastructure and preparing protocol translation capabilities in advance. The server maintains ready-to-use translation rules and protocol mappings, so when HTTP requests arrive, the translation process can proceed efficiently without ad-hoc processing delays. Connection pooling and buffer management are also implemented to minimize latency in real-time translation operations
Data Source
AI summary
Examples of methods, systems, apparatus, and machine-readable storage media are provided to facilitate access and control of a remote desktop of a remote machine by a web browser at a client device through a transcoding server without installing proprietary plug-ins or protocols on the client device. A transcoding server may translate user input requests from a web browser into input calls compatible with a remote desktop display protocol. The transcoding server may receive remote desktop drawing commands from the remote machine and translate the remote desktop drawing commands into web browser drawing updates compatible with the web browser. A transcoding server may communicate with is web browser via HTTP and communicate with a remote machine via a remote desktop display protocol. A web browser may be an HTML5 browser. A transcoding server may send drawing coordinates to the web browser via an HTTP header and may use long polling.


