Context Data Server for Secure Web Session Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current methods for storing user-specific context data on the web are limited by size constraints, security concerns, and fail to support redundancy and load-balancing effectively, leading to potential data loss and reduced system efficiency during server failures.

Innovation Solution

A context data server is placed in the data path between the user computer and the web server, intercepting messages to securely store and retrieve context data without adding complexity, facilitating redundancy and efficient load-balancing by piggybacking data management on standard network messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If context data is stored on a web server, then user-specific context data can be securely stored, but load balancing becomes ineffective and system complexity increases

Engineering Contradiction:

Improvesecure storage of context dataVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the context data storage function from the web server and places it in a separate dedicated storage system. The web server only retains index data in cookies, while the actual context data is stored externally in a distributed file system, separating concerns and reducing web server complexity.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a file server as an intermediary component between the web server and the storage medium. This file server manages the actual context data storage and retrieval, acting as a mediator that handles the complexity of data management away from the web server while maintaining secure storage.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If context data is stored on a specific web server, then data security is maintained, but load balancing effectiveness is reduced

Engineering Contradiction:

Improvedata securityVSAvoidload balancing effectiveness

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments the context data storage into two parts: index data stored in cookies on the user's browser and actual context data stored in a distributed file system. This segmentation allows any web server to access any user's context data through the file system, enabling effective load balancing while maintaining data security through controlled access.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a universal storage architecture where the file server serves all web servers in the farm. Any web server can retrieve any user's context data from the shared file system, making the storage system multi-functional and compatible with load balancing across multiple servers.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If cookies are used to store context data, then user-specific data can be associated with user computers, but data security and user privacy are compromised

Engineering Contradiction:

Improveuser-specific data associationVSAvoidsecurity and privacy risks

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments context data into two types: index data (stored in cookies) and actual context data (stored securely on the server). The cookie only contains a reference key, not the sensitive information itself, maintaining user association capability while eliminating security risks of storing sensitive data in cookies.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts sensitive context data from the cookie storage location and places it in a secure server-side storage system. Only non-sensitive index data remains in the cookie, removing the security vulnerability while preserving the ability to associate data with user computers.

Inventive Principle:

Principle #2Taking out (Extraction)

4Productivity

If multiple web servers are used to handle high traffic volume, then system capacity increases, but context data loss risk increases due to server failures

Engineering Contradiction:

Improvesystem capacityVSAvoidcontext data persistence

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent merges the storage capacity of multiple web servers into a single centralized file system. All context data from multiple servers is stored in one location with proper redundancy, combining the benefits of multiple servers for handling traffic while ensuring data persistence through centralized secure storage.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent implements prior cushioning by storing context data in a secure, persistent file system before any server failure can occur. The distributed file system with redundancy acts as a cushion against data loss, ensuring that even if multiple servers fail, the context data remains preserved and accessible.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS7937435B2Identifying, storing, and retrieving context data for a network message

Publication Date: 2011.05.03 RADWARE LTD

AI summary

A system and method for storing context data in a network device that is in the data path between a user computer and a server, thereby allowing for the secure and ongoing storage of user computer-specific context data without adding unnecessary complexity to existing web server methods, while at the same time supporting redundancy and facilitating effective load-balancing. By storing user computer-specific context data in the data path between the user computer and the server, the invention reduces the complexity of the web server, improves the handling of server failure, and increases the overall scalability of the system.