WebRTC Gateway for VDI Browser Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Real-Time Communication (RTC) clients in Remote Desktop Service (RDS) and Virtual Desktop Infrastructure (VDI) environments experience service degradation due to lack of RTC support in Remote Desktop Protocol (RDP), leading to unacceptable user experience, especially in metropolitan and wide area networks, and existing WebRTC solutions do not function properly in VDI environments without vendor-specific implementations.
Innovation Solution
A method for controlling accessible browser functions on a physical side of remote or virtual desktop environments using a WebRTC data channel between a physical unit and a virtual unit, enabling direct and immediate usage of WebRTC without VDI vendor-specific implementations, by establishing a WebRTC data channel between WebRTC media engines in web browsers and utilizing a head-less WebRTC extension to control local device APIs and peer connection APIs, ensuring real-time data handling and media streaming.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional RTC clients are deployed in RDS/VDI environments using RDP, then the system can provide remote desktop access, but service degradation occurs due to missing RTC support leading to unacceptable user experience
Solution Approach 1:
The patent introduces a gateway as an intermediary component that mediates between the RDP protocol and WebRTC protocol. The gateway translates RDP traffic into WebRTC format, enabling RTC functionality in VDI environments without requiring changes to existing RDP infrastructure. This intermediary resolves the contradiction by providing RTC support (improving reliability) while maintaining compatibility with conventional RDP clients (preserving ease of operation).
Solution Approach 2:
The patent changes the protocol parameter from RDP to WebRTC by introducing a protocol translation layer. The gateway converts RDP session parameters into WebRTC-compatible format, enabling real-time communication capabilities. This parameter change allows the system to achieve acceptable RTC service quality while maintaining the existing VDI architecture and user interface.
2Adaptability or versatility
If WebRTC solutions are implemented in VDI environments without vendor-specific implementations, then vendor independence is achieved, but existing solutions do not function properly
Solution Approach 1:
The patent creates a universal gateway that works with multiple VDI protocols and vendors without requiring vendor-specific implementations. The gateway implements a standardized interface that can translate various RDP variants into WebRTC format. This universal approach achieves vendor independence while maintaining reliable WebRTC functionality through protocol-agnostic translation capabilities.
Solution Approach 2:
The gateway serves as a vendor-neutral intermediary that sits between the VDI infrastructure and WebRTC applications. It translates vendor-specific RDP protocols into standardized WebRTC format, enabling reliable WebRTC functionality across different VDI environments without requiring vendor-specific implementations. This intermediary layer decouples the WebRTC functionality from specific VDI vendors.
3Ease of operation
If ICA channel is used for tunneling RTC payload data to physical unit, then device access is enabled, but delay and quality loss occur especially in metropolitan and wide area networks
Solution Approach 1:
The gateway acts as an intermediary that establishes direct WebRTC media channels between endpoints, bypassing the need to tunnel RTC payload data through the ICA channel. The gateway translates RDP control signals into WebRTC format and enables direct media streaming. This eliminates the delay and quality loss associated with ICA tunneling while maintaining device access capabilities.
Solution Approach 2:
The patent replaces the mechanical tunneling approach (ICA channel) with a modern WebRTC media channel. Instead of forcing RTC payload data through the legacy ICA protocol, the system uses WebRTC's optimized media streaming capabilities. This substitution reduces delay and improves quality by utilizing protocols designed for real-time media transmission rather than general-purpose remote desktop protocols.
4Area of stationary object
If distance between physical unit and server increases, then wider network coverage is achieved, but delay and quality loss in payload tunneling worsen
Solution Approach 1:
The gateway serves as a distributed intermediary that can be deployed closer to end users in metropolitan and wide area networks. By positioning gateways strategically across the network infrastructure, the system maintains low-latency WebRTC connections even over long distances. The gateway translates RDP to WebRTC locally, avoiding the need to tunnel media data across long network distances through legacy protocols.
Solution Approach 2:
The patent replaces the distance-sensitive ICA tunneling mechanism with WebRTC's robust media streaming protocol. WebRTC is specifically designed to handle variable network conditions and long-distance transmission with minimal quality degradation. The substitution enables wide network coverage while maintaining payload quality by using protocols optimized for real-time media over various network conditions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This patent application discloses to a method of controlling accessible browser functions of a physical side of a remote or virtual desktop environment, said method comprising steps of: - setting up a virtual desktop infrastructure between a physical unit (1) of a user, on said physical side, and a virtual unit (2) assigned to said user, on a virtual or remote side; - running a first web browser (31) at the physical unit (1) and a second web browser (41) at the virtual unit (2); - establishing a WebRTC data channel (68) between said first and second web browsers (41) running at the physical unit (1) and the virtual unit (2), respectively; and - controlling said browser functions of said first web browser (31) running at the physical unit (1) remotely by said virtual unit (2) utilizing said WebRTC data channel (68) established between the physical unit (1) and the virtual unit (2). The disclosure also covers a corresponding server and software product.