Application Context Deep Links via State Tokens

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for interacting with applications on electronic devices are cumbersome and time-consuming, as they often require users to navigate through multiple states and screens to access specific application contexts.

Innovation Solution

A method and system that enables deep links into application contexts by generating and using tokens to directly access specific states of applications, allowing users to skip initial and intermediate states, and sharing application state/location information between applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If users navigate through multiple states and screens to access specific application contexts, then they can reach the desired application state, but the process becomes cumbersome and time-consuming

Engineering Contradiction:
Improvetime to access application contextVSAvoidease of accessing application context
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The system generates and stores tokens that represent specific application states in advance. These tokens are created when applications are in desired states and stored for later retrieval, allowing users to directly access pre-prepared state representations without navigating through intermediate states.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Tokens serve as intermediary elements between the user and the application states. Instead of directly navigating through application screens, users interact with tokens that mediate the access process, translating user intent into direct state restoration without manual navigation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the system stores and manages application state tokens, then direct access to specific states is enabled, but the system complexity increases

Engineering Contradiction:
Improvespeed of application state accessVSAvoidsystem complexity for token management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The token mechanism serves multiple functions: it stores application state information, acts as a retrieval key, enables cross-application sharing, and facilitates state restoration. This multi-functionality reduces the need for separate systems for each purpose, managing complexity through consolidation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

Instead of storing entire application states which would be complex and resource-intensive, the system creates simplified token copies that represent specific states. These tokens are lightweight representations that capture essential state information without duplicating the full application context.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the system enables sharing of application state information between applications, then context sharing is improved, but the risk of information loss or security issues increases

Engineering Contradiction:
Improveability to share application contextVSAvoiddata integrity and security during sharing
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system extracts only the essential state information needed for sharing into tokens, separating critical data from complete application context. This extraction allows selective sharing of specific state elements while leaving sensitive or unnecessary information behind, improving both versatility and reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8510764B1Method and system for deep links in application contexts
Publication Date: 2013.08.13 GOOGLE LLC
  • US8510764B1 patent drawing
  • US8510764B1 patent drawing
  • US8510764B1 patent drawing

AI summary

A first application running on an electronic device may receive a first request that was triggered by a second application running on the electronic device. In response to the first request, the first application may provide a token that corresponds to a state of the first application at the time of receiving the first request. In response to receiving—after the state of the first application has changed—a second request that comprises the previously-provided token, the first application may return to the state that it was in at the time of the first request.