HTTP Transcoding Server for Remote Desktop Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional remote desktop protocols require proprietary software and browser plug-ins, limiting user access across different platforms and environments, and do not enable seamless, unified access to remote machines from various devices.

Innovation Solution

A transcoding server translates user input and drawing commands between web browsers and remote desktop clients, using HTTP for communication, allowing access to remote machines through a web browser with 2D rendering capabilities, eliminating the need for proprietary protocols and plug-ins, and enabling simultaneous connections to multiple servers.

Engineering Contradictions & Design Principles

VSEngineering 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 compatibility

Engineering Contradiction:
Improveplatform compatibilityVSAvoidsoftware infrastructure requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A gateway server is introduced as an intermediary component between the web browser and the remote desktop protocol. The gateway server receives HTTP requests from web browsers, translates them into appropriate remote desktop protocol commands, and forwards them to the target system. This mediator eliminates the need for proprietary browser plug-ins while maintaining protocol compatibility, thereby improving platform versatility without adding client-side complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the traditional mechanical approach of installing proprietary software or browser plug-ins with a web-based HTTP interface. By substituting the complex software installation mechanism with a standard web browser interface, the system achieves broader platform compatibility while reducing the complexity of software infrastructure requirements on client devices

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of operation

If protocol-specific software applications are required, then remote desktop access is achieved, but user convenience is reduced due to installation requirements

Engineering Contradiction:
Improveuser access convenienceVSAvoidinstallation requirements
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The gateway server provides self-service functionality by automatically translating and routing requests without requiring user configuration or installation of additional software. Users simply access the remote desktop through a standard web browser interface, and the gateway server handles all protocol translation and communication details automatically, maximizing ease of operation while minimizing installation requirements

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The gateway server is designed as a universal interface that can handle multiple remote desktop protocol types and translate them through a single HTTP interface. This multi-functional design allows users to access different remote desktop systems through a consistent web browser interface, improving ease of operation by eliminating the need for protocol-specific software applications

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10248374B2Methods and systems for a remote desktop session utilizing HTTP header
Publication Date: 2019.04.02 DELL MARKETING CORP
  • US10248374B2 patent drawing
  • US10248374B2 patent drawing
  • US10248374B2 patent drawing

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 of a client device through a web server without installing proprietary plug-ins or protocols on the client device. A web server may translate user input requests from a web browser into input calls compatible with a remote desktop display protocol. The web 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 web server may communicate with the web browser and the remote machine via HTTP and a remote desk top display protocol, respectively.