Application State Breadcrumbs for Seamless Web Navigation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current internet navigation tools lack efficient methods for users to easily return to previously accessed web applications and their status across different websites, especially after navigating away from them.

Innovation Solution

A system where user devices maintain 'breadcrumbs' - files containing application data and status information in long-term storage, allowing users to save and retrieve the state of applications across different websites, enabling seamless reactivation of applications from their previous state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users navigate away from web applications, then they can access other content, but they lose the ability to quickly return to the previous application state

Engineering Contradiction:
Improveease of returning to previous applicationVSAvoidtime to return to previous application
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system automatically saves the application state to persistent storage in the background when the user navigates away, so that when the user wants to return, the state is already prepared and can be restored immediately without requiring manual intervention or time to re-establish the previous state

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If the system maintains application state in persistent storage, then users can resume applications from previous state, but storage space is consumed

Engineering Contradiction:
Improveability to resume applicationVSAvoidstorage space consumed
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The system extracts only the essential application state information (such as current page URL, form data, and navigation history) and stores it in persistent storage, rather than storing the complete application or all historical data, thereby minimizing storage space consumption while maintaining the ability to resume applications

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system discards detailed application state information after a certain period or when memory space becomes constrained, and recovers only the essential state data when needed for resumption, balancing storage efficiency with functional requirements

Inventive Principle:
Principle #34Discarding and recovering

3Adaptability or versatility

If the system stores multiple application files in persistent storage, then more applications can be resumed, but device memory becomes constrained

Engineering Contradiction:
Improvenumber of resumable applicationsVSAvoidmemory management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system dynamically manages persistent storage by automatically removing the oldest or least recently used application states when memory capacity is reached, allowing the system to adapt to varying storage conditions and maintain an optimal number of resumable applications without manual intervention

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system monitors available storage space and provides feedback mechanisms to manage application state files, automatically pruning or archiving old states when memory constraints are detected, thereby maintaining versatility while preventing memory exhaustion

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9411639B2System and method for managing network navigation
Publication Date: 2016.08.09 ALCATEL LUCENT SA
  • US9411639B2 patent drawing
  • US9411639B2 patent drawing
  • US9411639B2 patent drawing

AI summary

A file comprising an application and data corresponding to a status of the application at a particular time is maintained in a first memory of a user device, the first memory comprising a persistent storage. The application may be a software application, for example. In response to a request, the file is transferred to a second memory of the device, the second memory comprising a random-access memory. The file is activated, or set up, as a running application. The user device may be a cell phone, a wireless telephone, a personal digital assistant, a personal computer, a laptop computer, a workstation, a mainframe computer, etc. In one embodiment, the file is brought to a foreground of the user device.