Remote User Interface Transfer via Server State Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current remote user interface (RUI) technologies, such as browser-based implementations and RVU, face limitations in memory requirements, processing speed, and network resource usage, especially when transferring graphical user interfaces across devices with varying capabilities, leading to performance issues and incompatibilities with cost-sensitive consumer electronics.

Innovation Solution

A method and system for transferring a remote user interface by storing state information on a server and using it to seamlessly transition the RUI from one device to another, allowing for media transfer while maintaining the interface's state, utilizing a persistent application state and remote graphics rendering to migrate rendering tasks across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a browser-based implementation is used for RUI, then the interface can be displayed on various devices, but the memory and processor requirements become substantial

Engineering Contradiction:
Improveinterface compatibilityVSAvoidmemory requirements
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system divides the RUI architecture into two separate components: a thin server application that generates the user interface and a browser-based client that displays it. This segmentation allows the heavy rendering logic to reside on the server while the client maintains minimal memory requirements, resolving the contradiction between interface versatility and memory consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a server application as an intermediary between the user interface generation and the browser display. This intermediary handles the substantial processing requirements, allowing the browser client to remain lightweight while still providing comprehensive interface functionality across multiple devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a browser-based implementation is used for RUI, then the interface can be displayed on various devices, but the processing speed requirements are not met

Engineering Contradiction:
Improveinterface compatibilityVSAvoidprocessing speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

By segmenting the system into a server application that performs complex processing and a browser client that handles display, the patent achieves both high processing speed on the server and broad device compatibility on the client side. The server handles computationally intensive tasks while the browser renders the output.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If a browser-based implementation is used for RUI, then the interface can be displayed on various devices, but it is not ideal for limited button remote control

Engineering Contradiction:
Improveinterface compatibilityVSAvoidremote control usability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system dynamically adapts the user interface based on the input device being used. When a remote control is detected, the interface automatically adjusts its controls and layout to be optimized for button-based interaction, rather than mouse or keyboard operations. This dynamic adaptation maintains ease of operation across different device types while preserving interface compatibility.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If substantial effort is made to rewrite or translate graphics applications to fit the browser framework, then compatibility is improved, but device complexity increases

Engineering Contradiction:
Improveinterface compatibilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of converting graphics applications to fit the browser framework, the patent inverts the approach by having the server application generate the user interface in the desired format and stream it to the browser. This eliminates the need for complex rewriting and translation efforts, reducing implementation complexity while maintaining compatibility.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS8769110B2Transferring RUI from one device to another
Publication Date: 2014.07.01 SATURN LICENSING LLC
  • US8769110B2 patent drawing
  • US8769110B2 patent drawing
  • US8769110B2 patent drawing

AI summary

A method of and system for transferring a remote user interface from one device to another device is described herein. A server stores state information and uses the information to transfer the RUI and/or other data from one device to the other device. This enables a user to transition from one device to another device seamlessly and without interruption of their user interface and/or programming.