Remote User Interface State Migration via Bookmark Module

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional UPnP networks struggle with managing and migrating state information of Remote User Interfaces (RUIs) across different clients, particularly in internet-based models with stateless features like HTTP, where all state information is typically stored on the server, limiting flexibility and compatibility.

Innovation Solution

A method and apparatus that enables an RUI client to manage state information by receiving migration requests, storing and restoring it locally, and transmitting this information between different RUI clients using location information, allowing seamless migration and storage across various devices within a home network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If all state information of RUIs is stored on the RUI server in conventional UPnP networks, then the server can maintain centralized control, but the RUI client cannot independently manage or migrate state information between devices

Engineering Contradiction:
Improvestate information migration capabilityVSAvoidstate information management architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts state information management capability from the server and places it in the client device. The client obtains state information from the server but stores and manages it locally in its own storage device, enabling independent migration without server involvement in the migration process.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a bookmark module as an intermediary layer between the server and client application. This bookmark module stores state information locally and provides it to applications when needed, decoupling the client from direct server dependency for state management.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If state information is stored on the server, then data consistency is maintained, but additional discovery processes are required for clients to access stored state information

Engineering Contradiction:
Improvestate information access processVSAvoiddiscovery process time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent performs preliminary action by obtaining and storing state information in the client's bookmark module during the initial RUI establishment phase. This pre-stored local state information eliminates the need for subsequent discovery processes when accessing or migrating state information between devices.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the RUI client manages state information locally, then migration between devices becomes possible, but the client must handle storage and retrieval operations

Engineering Contradiction:
Improvedevice migration flexibilityVSAvoidclient storage management operations
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling the client device to autonomously obtain, store, manage, and migrate its own state information without requiring server intervention during these operations. The client's bookmark module independently handles all state information lifecycle management.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2353102B1Method and apparatus for managing state information of remote user interface
Publication Date: 2019.10.30 SAMSUNG ELECTRONICS CO LTD
  • EP2353102B1 patent drawingFigure 1~3
  • EP2353102B1 patent drawingFigure 4
  • EP2353102B1 patent drawingFigure 5

AI summary

A method for managing state information of a Remote User Interface (RUI) received from a server providing the RUI in a client. The method includes extracting the state information in response to a store request for the state information from a user; providing the state information to the server; receiving from the server location information indicating a route to a location where the state information is stored; and storing the location information in a bookmark module.