Adaptive Session Timeout Management for Stateful Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current stateful client-server applications have a fixed session timeout period, leading to user disconnection and data loss if a user doesn't complete a task within the set time, without adapting to individual user needs, resulting in inefficient user experience and data management.
Innovation Solution
A method and system dynamically adapt the session timeout period by determining the rate of timed out sessions and comparing it to a threshold value, adjusting the timeout period based on user behavior, allowing for shorter or longer sessions as needed to optimize user interaction and data retention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a fixed session timeout period is used for the entire application, then the system is simple to manage and implement, but users are disconnected and lose data if they cannot complete tasks within the fixed time, leading to poor user experience
Solution Approach 1:
The patent divides the application into multiple parts (e.g., login, product selection, checkout) and assigns different session timeout periods to each part based on the time required to complete that specific part. This segmentation allows each part to have its own optimized timeout period rather than using a single fixed timeout for the entire application.
Solution Approach 2:
The patent implements dynamic session timeout periods that adapt to user behavior and task requirements. The timeout period for each part is determined based on historical data about the average time users take to complete that part, allowing the system to dynamically adjust timeouts rather than using static fixed values.
2Duration of action of moving object
If a pop-up window is used to extend session timeout, then the session duration is extended, but users must continually confirm to keep sessions open, creating annoyance and additional complexity
Solution Approach 1:
The patent determines and sets appropriate session timeout periods in advance for each part of the application based on historical user behavior data. This preliminary configuration eliminates the need for pop-up windows that require user confirmation during the session, as the timeout periods are pre-optimized to match actual user needs.
Solution Approach 2:
The system uses feedback from user behavior patterns to automatically adjust and optimize session timeout periods for different parts of the application. By monitoring how long users actually take to complete tasks in each part, the system learns and adapts the timeout values without requiring user intervention or confirmation.
3Adaptability or versatility
If a uniform session timeout period is applied to all parts of the application, then the configuration is simple, but it does not adapt to the time needed by individual users for different parts, resulting in data loss and inefficiency
Solution Approach 1:
The patent applies different session timeout periods to different parts of the application based on the specific requirements of each part. For example, the login part may have a shorter timeout while the product selection part has a longer timeout, matching the local needs of each section rather than applying a uniform timeout throughout.
Solution Approach 2:
The system changes the timeout parameter dynamically based on the part of the application and user behavior patterns. By using historical data to determine optimal timeout values for each part, the system adapts the timeout parameter to match actual usage patterns, improving both adaptability and efficiency.
Data Source
AI summary
A method for adapting a session timeout period of an application comprising one or more parts, each part of the application having a corresponding predetermined session timeout period for receiving an input from a user connected to a part of the application, comprising the steps of determining the rate of timed out sessions for the part of the application after the number of connections to the part has reached a predetermined level; comparing the rate of timed out sessions of the part of the application with a predetermined threshold value of the rate of timed out sessions; adapting the predetermined session timeout period of that part (400) of the application based on the comparison to give rise to an adapted session timeout period.