Session State Restoration via Request Type Classification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing session restoration methods face inconsistencies and data loss when handling stateless requests, leading to incorrect session state restoration after node failures, particularly in scenarios like online forms where background requests are made before a server failure.

Innovation Solution

Implement a system that categorizes client requests as stateful or stateless, restoring session state only upon receiving a stateful request, thereby avoiding restoration issues caused by interspersed stateless requests and ensuring consistent session state maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If session state is restored after receiving any request (including stateless requests), then session restoration coverage is improved, but session state consistency deteriorates due to incorrect restoration timing

Engineering Contradiction:
Improvesession restoration coverageVSAvoidsession state consistency
Core Design Contradiction:
ReliabilityVSManufacturing precision

Solution Approach 1:

The system changes the parameter of request type classification by distinguishing between stateful and stateless requests. This parameter change enables conditional session restoration logic that checks the request type before restoration, thereby maintaining session state consistency while ensuring proper restoration coverage.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system applies different restoration behaviors to different types of requests. Stateful requests trigger session state restoration, while stateless requests do not. This local differentiation in restoration quality ensures that session state is only restored when appropriate, preventing consistency issues.

Inventive Principle:
Principle #3Local quality

2Productivity

If session state is restored after stateless requests, then session availability is improved, but data accuracy deteriorates due to premature restoration

Engineering Contradiction:
Improvesession availabilityVSAvoiddata accuracy
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The system performs preliminary classification of requests into stateful and stateless categories before deciding on session restoration. This preliminary action ensures that restoration only occurs after appropriate stateful requests, maintaining data accuracy while ensuring session availability when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from request type analysis to control session restoration timing. By monitoring whether incoming requests are stateful or stateless, the system receives feedback that determines whether restoration should occur, ensuring data accuracy is maintained while session availability is preserved.

Inventive Principle:
Principle #23Feedback

3Reliability

If session state is persistently stored for all requests, then session recovery capability is improved, but system complexity increases due to unnecessary persistence operations

Engineering Contradiction:
Improvesession recovery capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts the persistence operation from the general request processing flow and applies it selectively only to stateful requests. This extraction eliminates unnecessary persistence operations for stateless requests, reducing system complexity while maintaining session recovery capability for requests that actually need it.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of applying persistence to all requests (excessive action), the system applies persistence partially only to stateful requests. This partial action reduces unnecessary database operations and system complexity while maintaining adequate session recovery capability for the subset of requests that require state persistence.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11196819B2System and method for session restoration after node failure
Publication Date: 2021.12.07 SERVICENOW INC
  • US11196819B2 patent drawing
  • US11196819B2 patent drawing
  • US11196819B2 patent drawing

AI summary

A system and method for restoring a session state of a client device has been provided. The system comprises a memory with instructions executable by a processor to receive a first request from the client device, where the first request is a first type of request and is associated with a new session of the client device; process the first request without persisting a session state of the new session in the database node; receive a second request from the client device, where the second request is a first instance of a second type of request and is associated with the new session; and in response to determining to restore a persisted session state, restore the persisted session state for the client device from the database node, and assign the persisted session state as the session state of the new session of the client device.