HTML Encapsulation via Transcoding Agent for Secure Remote Display

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile client devices accessing network resources are vulnerable to malicious software and viruses due to remote rendering and transcoding of HTML, which increases loading latency and resource consumption, and lacks visibility and control for administrators.

Innovation Solution

A system and method for encapsulating HTML using a transcoding agent in a remote browser, which renders HTML locally on the client device, bypassing remote rendering and transcoding, and utilizing web components APIs to block JavaScript and extensions from reacting to events, ensuring secure and efficient rendering.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If HTML is rendered remotely and transcoded for delivery to client devices, then administrators can maintain control and visibility over web application delivery, but loading latency increases and resource consumption increases

Engineering Contradiction:
Improveadministrative controlVSAvoidloading latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the HTML rendering process by separating the rendering engine (remote browser on server) from the presentation layer (local browser on client). The remote browser renders HTML to a virtual DOM, which is then encapsulated and delivered to the local browser for rendering. This segmentation allows administrative control to be maintained at the remote browser level while enabling efficient local rendering that reduces latency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a virtual DOM as an intermediary data structure between the remote browser and local browser. The virtual DOM encapsulates the rendered HTML content in a controlled format that can be efficiently transmitted and rendered locally. This intermediary enables the system to maintain administrative oversight while achieving fast local rendering performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If HTML is rendered remotely and transcoded, then administrators can control web application delivery, but client devices consume more resources

Engineering Contradiction:
Improveadministrative controlVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the computational workload by performing heavy HTML rendering operations in the remote browser on the server, then delivering only the essential virtual DOM structure to the client. This segmentation reduces the resource consumption on client devices while maintaining administrative control at the server level through the remote browser.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a virtual DOM as a simplified copy of the rendered HTML content that can be efficiently transmitted and rendered locally. Instead of transmitting and processing the full rendered HTML with all its complexity, the system uses the virtual DOM copy to enable efficient local rendering with reduced resource consumption.

Inventive Principle:
Principle #26Copying

3Loss of time

If local browsers render HTML directly without remote encapsulation, then loading latency and resource consumption are reduced, but security vulnerabilities increase due to exposure to malicious software

Engineering Contradiction:
Improveloading latencyVSAvoidsecurity vulnerability
Core Design Contradiction:
Loss of timeVSObject-affected harmful factors

Solution Approach 1:

The patent introduces the virtual DOM as a secure intermediary layer between the remote browser and local browser. The virtual DOM encapsulates HTML content in a controlled format that prevents malicious scripts from directly interacting with the local browser environment. This intermediary maintains security while enabling efficient local rendering by blocking harmful factors at the encapsulation boundary.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts and isolates potentially harmful elements by rendering them in the remote browser environment first. The virtual DOM captures only the safe, essential structure and content, leaving malicious scripts and harmful factors behind in the remote rendering environment. This extraction process removes security threats while preserving useful content for local rendering.

Inventive Principle:
Principle #2Taking out (Extraction)

4Reliability

If remote rendering and transcoding are used, then administrative control is maintained, but device complexity increases

Engineering Contradiction:
Improveadministrative controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the system into distinct functional components: remote browser for rendering, virtual DOM for encapsulation, and local browser for display. This segmentation organizes complexity into manageable modules with clear interfaces, making the overall system easier to understand and maintain while preserving administrative control at the remote browser level.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11281744B2Systems and methods for improved remote display protocol for HTML applications
Publication Date: 2022.03.22 CITRIX SYSTEMS INC
  • US11281744B2 patent drawing
  • US11281744B2 patent drawing
  • US11281744B2 patent drawing

AI summary

Embodiments described herein include systems and methods for encapsulating HTML. A remote browser executing on a server may be configured to provide a document object model (DOM) of HTML of a webpage rendered by the remote browser at the server. A transcoding agent executing in the remote browser may be configured to encapsulate the HTML. The transcoding agent may be configured to send the encapsulated HTML via a remote delivery session to a local browser for rendering. The local browser may execute on a client device and may maintain a DOM for the encapsulated HTML. The transcoding agent may be configured to receive events corresponding to the DOM maintained by the local browser. The remote browser may further be configured to cause the received events to execute on the DOM provided by the remote browser.