JavaScript Object for HTTP State Storage in UPnP RUI

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for storing and restoring state information of remote user interfaces (RUIs) in a Universal Plug and Play (UPnP) environment are not applicable to HyperText Transfer Protocol (HTTP)-based remote protocol models, which are stateless and do not allow state information to be stored, unlike binary protocol-based models like RDP and XRT.

Innovation Solution

A method and apparatus that utilize a JavaScript object to process HTTP requests without reloading the web page, allowing state information to be obtained and stored using a new socket, and a State Storage (SS) server to manage and restore state information, enabling storage and retrieval of state information in HTTP-based RUIs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional UPnP methods are used to store and restore state information, then state information can be preserved in binary protocol-based models (RDP, XRT), but the method cannot be applied to HTTP-based models due to their stateless characteristics

Engineering Contradiction:
Improveapplicability to different remote protocol modelsVSAvoidstate information preservation
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a JavaScript object as an intermediary component that mediates between the HTTP protocol and state information storage requirements. This JavaScript object intercepts HTTP requests and responses, extracts state information, and manages its persistence, thereby enabling stateful behavior in the stateless HTTP protocol without requiring changes to the core HTTP mechanism

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the operational parameters of HTTP by introducing a JavaScript object that modifies how requests and responses are handled. The JavaScript object captures and preserves state information that would otherwise be lost, effectively changing HTTP from a stateless protocol to one that can maintain state across transactions through the added functionality of the JavaScript object

Inventive Principle:
Principle #35Parameter changes

2Loss of energy

If HTTP-based remote protocol models are used, then network bandwidth consumption is reduced compared to binary protocols, but state information is lost due to stateless characteristics

Engineering Contradiction:
Improvenetwork bandwidth consumptionVSAvoidstate information
Core Design Contradiction:
Loss of energyVSLoss of information

Solution Approach 1:

The JavaScript object performs preliminary actions by intercepting and capturing state information from HTTP responses before the connection is closed. It proactively extracts and stores relevant state data, ensuring that state information is preserved before the stateless nature of HTTP would cause it to be lost

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The JavaScript object implements a feedback mechanism where it continuously monitors HTTP transactions, extracts state information from responses, and uses this information to reconstruct state in subsequent requests. This feedback loop ensures state information is maintained across multiple HTTP transactions without increasing bandwidth consumption

Inventive Principle:
Principle #23Feedback

3Stability of the object's composition

If state information is managed by RUI client in HTTP-based models, then stateless HTTP characteristics are maintained, but conventional storage and restoration processes cannot be applied

Engineering Contradiction:
Improvestateless HTTP characteristicsVSAvoidstorage and restoration process implementation
Core Design Contradiction:
Stability of the object's compositionVSEase of manufacture

Solution Approach 1:

The RUI client's JavaScript object provides self-service by automatically capturing, storing, and restoring state information without requiring external intervention or changes to the HTTP protocol. The JavaScript object independently manages the stateful aspects of HTTP communication, making the implementation straightforward while preserving HTTP's stateless characteristics at the protocol level

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2256646B1Improvements in and relating to remote user interfaces
Publication Date: 2016.08.24 SAMSUNG ELECTRONICS CO LTD
  • EP2256646B1 patent drawingFigure 1~2
  • EP2256646B1 patent drawingFigure 3~4
  • EP2256646B1 patent drawingFigure 5

AI summary

Provided are an apparatus and method of restoring a remote user interface (RUI) in a Universal Plug and Play (UPnP) environment. In the apparatus and method, an RUI client requests an external storage server to store the state information of the RUI by using a Hypertext Transfer Protocol (HTTP) object processing a HTTP request without reloading a web page, and restores the original state of the RUI by using the stored state information. Accordingly, it is possible to apply a method of storing and restoring state information of a remote user interface, in a UPnP environment, to a HTTP-based remote protocol model having stateless characteristics which do not allow state information of a remote user interface to be stored.