Browser Cookie Isolation via Session Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern web browsers lack effective mechanisms to isolate and manage cookie data across different sessions, leading to data loss and corruption, especially in customer service environments where multiple customer sessions are handled concurrently.

Innovation Solution

Implement a method that isolates and manages cookie data by using background storage and session storage to maintain separate cookie data for each tab, preventing overwriting and ensuring data integrity across sessions, and utilizing a cookie owner mapping to track and propagate cookies correctly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If cookie data is stored in a shared browser cookie store, then ease of operation is improved, but data integrity deteriorates due to overwriting between sessions

Engineering Contradiction:
Improvecookie managementVSAvoiddata integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the shared browser cookie store into isolated session-specific storage areas. Each session receives its own dedicated storage space through browser session isolation mechanisms, preventing cookie data from different sessions from overwriting each other while maintaining the simplicity of unified cookie management within each isolated session context.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple customer sessions are handled concurrently in the same browser, then productivity is improved, but data loss increases due to cookie overwriting

Engineering Contradiction:
Improvesession handling capacityVSAvoidcookie data loss
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent implements segmentation by creating distinct isolated storage contexts for each customer session. When multiple sessions are handled concurrently, each session's cookie data is confined to its own isolated storage space, eliminating cross-session overwriting while enabling unlimited concurrent session handling.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary isolation mechanism that mediates between multiple concurrent sessions and the underlying storage system. This intermediary layer ensures that cookie operations from different sessions are properly routed to their respective isolated storage contexts, preventing data loss while maintaining high session handling capacity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If traditional browser cookie storage is used, then device complexity is reduced, but data corruption occurs due to lack of session isolation

Engineering Contradiction:
Improvestorage mechanismVSAvoidcookie data integrity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent applies segmentation by dividing the monolithic browser cookie store into multiple isolated session-specific storage segments. This segmentation prevents data corruption between sessions while maintaining relatively simple implementation through browser-native session isolation features, avoiding the need for complex custom storage solutions.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11431809B1Session data isolation and management
Publication Date: 2022.08.30 UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)
  • US11431809B1 patent drawing
  • US11431809B1 patent drawing
  • US11431809B1 patent drawing

AI summary

Techniques are described for managing cookies, including separately managing cookie data associated with different browser tabs. Cookie management includes the isolation of whitelisted cookies from server responses into background storage and then back onto server requests, removing those cookies from the response header and thus from the cookie store. This isolation is managed with the concept of tab ownership between parent and child tabs to maintain isolation separately for each owner (e.g., the parent) and its children. Exposure to client pages is handled by placing those cookies into a keyed location in session storage for every tab where that cookie is to be visible. An event is then triggered for that client page to let it know that session storage has been updated.