Session State Backup via DOM Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing systems are dependent on physical devices, leading to data loss when devices are misplaced or become inoperable, and moving session states between devices is cumbersome for users.

Innovation Solution

The system provides session state information to a server by accessing the Document Object Model (DOM) of web applications, determining predetermined events to update the session state, and sending contextual information to differentiate between session states, allowing seamless state restoration across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If session state information is stored locally on physical devices, then data access is fast and simple, but data is lost when devices are misplaced or become inoperable

Engineering Contradiction:
Improvesession state data preservationVSAvoidsession state data loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

A server acts as an intermediary between multiple client devices and session state information. The server stores session state data centrally, allowing clients to access and restore sessions across different devices. This mediator approach prevents data loss when individual devices fail or are lost, as the session state persists on the server.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates and maintains copies of session state information on a server, separate from the original client devices. When a user logs in from any device, the system retrieves the session state copy from the server and restores it locally. This copying mechanism ensures data preservation while enabling cross-device accessibility.

Inventive Principle:
Principle #26Copying

2Reliability

If session state information is synchronized in real-time across all devices, then data consistency is maintained, but network bandwidth and system resources are consumed continuously

Engineering Contradiction:
Improvesession state consistencyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Instead of continuous real-time synchronization, the system uses event-driven periodic updates. Session state information is transmitted to the server only when specific events occur, such as user login, state changes, or device connection. This approach maintains data consistency while significantly reducing network bandwidth consumption compared to continuous synchronization.

Inventive Principle:
Principle #19Periodic action

3Reliability

If complete session state information is transmitted to the server, then data integrity is ensured, but network traffic and server storage requirements increase

Engineering Contradiction:
Improvesession state data integrityVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system extracts and transmits only the essential session state information required for restoration to the server, rather than transmitting complete device states. By identifying and sending only critical session data (such as application states, user preferences, and contextual information), the system maintains data integrity for recovery purposes while minimizing network traffic and server storage requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3186719B1Resuming session states
Publication Date: 2021.08.04 GOOGLE LLC
  • EP3186719B1 patent drawingFigure 1
  • EP3186719B1 patent drawingFigure 2
  • EP3186719B1 patent drawingFigure 3

AI summary

Providing state information to a server includes accessing a document object model (DOM) for a web application, the DOM corresponding to a tree structure which represents a first state of the web application. An indication of the first state of the web application is provided to a server based on the DOM. A determination is made that a predetermined event has occurred at the system, the predetermined event indicating that a second state of the web application, different than the first state of the web application, is to be provided to the server. In response to the determination, an indication of the second state of the web application, corresponding to an updated version of the DOM, is provided to the server.