Local Loader Bypasses Browser for Java App Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Java-based embedded device management applications are inefficient due to the need to download the embedded application each time a user interfaces with a networking device through a browser, which is slow and resource-intensive, and limits runtime parameters such as memory allocation.

Innovation Solution

A method and system that launches a locally installed loader on a client workstation to access and compare checksum values of a Java-based embedded application, allowing the locally stored version to be launched directly without a browser interface, enabling automatic version upgrades and efficient execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the embedded application is accessed through a browser interface, then compatibility with the networking device is ensured, but the execution speed and efficiency deteriorate due to repeated downloads

Engineering Contradiction:
ImprovecompatibilityVSAvoidexecution speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The loader is installed on the client workstation in advance through the browser, enabling local execution of the embedded application without repeated downloads. The checksum verification mechanism is also prepared in advance to ensure compatibility before execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The embedded application is copied from the networking device to the client workstation's local storage. This allows the application to be executed locally from the copied version, eliminating the need to download the application each time it is accessed, thereby improving execution speed while maintaining compatibility through checksum verification.

Inventive Principle:
Principle #26Copying

2Reliability

If the embedded application is downloaded each time through the browser, then compatibility is maintained, but resource consumption increases and efficiency decreases

Engineering Contradiction:
ImprovecompatibilityVSAvoidefficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The loader is installed on the client workstation in advance through the browser, enabling local execution of the embedded application without repeated downloads. The checksum verification mechanism is also prepared in advance to ensure compatibility before execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The embedded application is copied from the networking device to the client workstation's local storage. This allows the application to be executed locally from the copied version, eliminating the need to download the application each time it is accessed, thereby improving execution speed while maintaining compatibility through checksum verification.

Inventive Principle:
Principle #26Copying

3Reliability

If the embedded application is stored on the networking device, then compatibility is ensured, but runtime parameters such as memory allocation are limited

Engineering Contradiction:
ImprovecompatibilityVSAvoidruntime parameters
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The embedded application is copied from the networking device to the client workstation's local storage. This allows the application to be executed locally from the copied version, eliminating the need to download the application each time it is accessed, thereby improving execution speed while maintaining compatibility through checksum verification.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The application execution environment is shifted from the networking device to the client workstation, adding a new dimension to the system architecture. This enables the client workstation to provide enhanced runtime parameters such as increased memory allocation while the networking device maintains compatibility through checksum verification.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP1866758B1Method, system and apparatus for launching an interface with an electronic device
Publication Date: 2018.09.19 CISCO TECHNOLOGY INC
  • EP1866758B1 patent drawingFigure 1
  • EP1866758B1 patent drawingFigure 2
  • EP1866758B1 patent drawingFigure 3

AI summary

A method for launching (310) an interface with a remotely located electronic device (315). Specifically, a loader that is locally installed is launched. The loader is associated with an embedded application stored on a remote device. Communication is established with the remote device to access a first checksum value (320) that is stored on the remote device. Thereafter, the first checksum value is compared (330) against a second checksum vale of a locally stored version of the embedded application. The locally stored version of the embedded application is launched (355) when the first check value matches the second checksum value.