Real-Time HTML Rendering of Legacy Windows Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Companies face inefficiencies and risks when migrating from legacy system technologies to modern development platforms, including regression in functionality, security concerns, lost productivity, disruption to business operations, and high costs, especially when trying to expose legacy system screens to remote locations.

Innovation Solution

A system and method for real-time HTML rendering of desktop applications, which identifies and transforms desktop-based legacy system applications into HTML-based applications by querying and mapping user interface elements, and establishing a web-socket for data and event transfer, enabling seamless operation across platforms without the need for dedicated clients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If legacy system applications are migrated to modern development platforms through re-write or buying new products, then modern functionality and security are improved, but costs, time, and business disruption increase significantly

Engineering Contradiction:
ImprovesecurityVSAvoidmigration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a visual copy of the legacy application interface using HTML5 and WebGL, rendering the legacy desktop application screen in real-time within a web browser. This copy allows users to access legacy functionality through modern web technologies without actually migrating the underlying legacy code, thus achieving modern interface standards while preserving the original application logic and data layer.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces an intermediary rendering layer that sits between the user and the legacy application. This layer captures the legacy application's screen output and re-renders it using HTML5 canvas and WebGL, acting as a mediator that translates legacy visual output into modern web-compatible graphics without requiring changes to the legacy application itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If legacy system applications are migrated through re-write or tool-based migration, then functionality is improved, but regression in functionality and loss of productivity occur during transition

Engineering Contradiction:
ImprovefunctionalityVSAvoidproductivity during migration
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent performs preliminary actions by pre-rendering and caching static portions of the legacy application interface before user interaction. When the HTML5 version loads, commonly displayed elements are already prepared and can be displayed immediately, while dynamic elements are generated on-demand based on user actions, thus eliminating the need for users to wait during the migration transition.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a dynamic rendering approach where the HTML5 interface adapts its rendering strategy based on user interaction. Static elements are pre-rendered for immediate display, while dynamic elements triggered by user actions are rendered in real-time, creating a responsive experience that maintains productivity during the transition to modern platforms.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If third party virtualization solutions are purchased to expose legacy system screens to remote locations, then remote access capability is improved, but costs and device complexity increase

Engineering Contradiction:
Improveremote access capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the legacy application universally accessible by rendering it in standard HTML5 that can run in any modern web browser across multiple platforms (desktop, mobile, tablet). This single HTML5 implementation serves all remote access needs without requiring separate virtualization solutions for different devices or operating systems, thereby reducing overall system complexity.

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

Solution Approach 2:

The patent replaces the mechanical virtualization infrastructure (third-party software agents, remote desktop protocols, dedicated client applications) with a lightweight HTML5-based rendering approach. Instead of installing complex virtualization software on remote devices, the system uses standard web browsers to display the legacy application, substituting heavy mechanical systems with lightweight web technologies.

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

4Ease of manufacture

If legacy applications are accessed remotely without virtualization, then cost is reduced, but security concerns and functionality limitations arise

Engineering Contradiction:
ImprovecostVSAvoidsecurity
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent creates a secure visual copy of the legacy application interface that runs within the user's existing web browser sandbox environment. This copy displays the legacy application's output without exposing the underlying legacy system to remote devices, maintaining security boundaries while enabling cost-effective remote access through standard web technologies.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10956533B1System, method, and computer program for real-time HTML rendering of windows applications
Publication Date: 2021.03.23 AMDOCS DEV LTD
  • US10956533B1 patent drawing
  • US10956533B1 patent drawing
  • US10956533B1 patent drawing

AI summary

A system, method, and computer program product are provided for real-time HTML rendering of desktop applications. In operation, a system identifies one or more desktop based legacy system applications for transforming into one or more HTML based applications in real-time. The system queries user interface (UI) elements of the one or more desktop based legacy system applications. The system maps the UI elements of the one or more desktop based legacy system applications to HTML UI elements associated with the one or more HTML based applications. Additionally, the system opens a web-socket between the HTML UI elements and the UI elements associated with the one or more desktop based legacy system applications to transfer data and events based on user actions in the one or more HTML based applications and responses from the one or more desktop based legacy system applications.