Concurrency-Aware Session Establishment via Negotiation Algorithm

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing session management systems struggle to reliably group multiple concurrent requests from a single browser instance, especially in complex scenarios like single sign-on products, due to limitations in web APIs and the stateless nature of HTTP.

Innovation Solution

A concurrency-aware session establishment system that uses a negotiation algorithm to determine a unique browser-session identifier by requiring a unique cookie per concurrent request, deferring session creation until the identifier is negotiated, and employing secure cookie management to prevent attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a stateless HTTP protocol is used for web communication, then network simplicity and speed are improved, but the ability to track user flows and associate requests to single identity deteriorates

Engineering Contradiction:
Improvenetwork communication speedVSAvoiduser flow tracking reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent segments the session management into multiple components: a session cookie for high-level session identification, a browser-session synchronization cookie for concurrency control, and a negotiation algorithm for coordinating between concurrent requests. This segmentation allows each component to handle specific aspects of session tracking independently, maintaining reliability without compromising HTTP's stateless nature.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces cookies as intermediary mechanisms to carry session state information between the client and server. The session cookie acts as a mediator that contains session data, while the synchronization cookie mediates the concurrency negotiation process. These intermediaries enable reliable user flow tracking despite HTTP's stateless design.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple concurrent requests are handled independently, then request processing speed is improved, but session consistency and security deteriorate

Engineering Contradiction:
Improverequest processing throughputVSAvoidsession consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent performs preliminary actions by first negotiating and establishing a unique browser-session identifier before processing the actual request body. The synchronization cookie is set up in advance to coordinate concurrent requests. This preliminary negotiation phase ensures session consistency is established before independent request processing begins, allowing both high throughput and reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the server responds to concurrent requests with synchronization cookies that contain negotiation results. This feedback loop allows each concurrent request to receive updates about session status, enabling them to adjust their processing accordingly while maintaining session consistency across all requests.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If session management complexity is increased to handle concurrent requests, then session accuracy is improved, but system complexity and implementation difficulty deteriorate

Engineering Contradiction:
Improvesession identification accuracyVSAvoidsession management system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the complex session management into distinct, manageable components: a session cookie for identification, a synchronization cookie for concurrency control, and a negotiation algorithm for coordination. Each component has a specific function and can be implemented independently, reducing overall implementation difficulty while maintaining high session identification accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent designs the session management system to handle multiple scenarios universally: single requests, concurrent requests, browser sessions, and cross-domain communications all use the same fundamental mechanism of negotiation algorithms and synchronization cookies. This multi-functionality reduces complexity by using a single approach for diverse situations rather than requiring separate specialized systems.

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

4Object-affected harmful factors

If secure cookie management is implemented to prevent attacks, then security is improved, but performance and compatibility deteriorate

Engineering Contradiction:
Improvesecurity against attacksVSAvoidsession establishment speed
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

The patent performs security-related preliminary actions by setting the synchronization cookie with secure attributes (httpOnly, secure flags) before the main request processing begins. This preliminary security configuration ensures that subsequent request processing can proceed efficiently without repeated security checks, maintaining both security and performance.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250126175A1Concurrency-aware session establishment with a web-based authentication service
Publication Date: 2025.04.17 CISCO TECHNOLOGY INC
  • US20250126175A1 patent drawing
  • US20250126175A1 patent drawing
  • US20250126175A1 patent drawing

AI summary

The present disclosure is directed to receiving multiple concurrent requests from multiple applications for session establishment from a user device, wherein the concurrent requests originated from a single browser instance, communicating a redirect response comprising a query parameter to each of the applications to the user device, receiving a browser-session synchronization cookie from each of the applications responsive to each corresponding redirect response from the user device, determining a browser-session identifier based on the browser-session synchronization cookies and by a negotiation algorithm, generating a browser-session cookie based on the browser-session identifier and by the negotiation algorithm, and establishing a session for the applications via the single browser instance based on the browser-session cookie.