Client-Side Session Timeout Handling in Learning Management Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional classroom training is inefficient and resource-intensive, leading to lost session context due to server-side time-outs in electronic learning management systems, where users are not adequately informed of session expiration, resulting in lost activity results.

Innovation Solution

Implementing a method for time-out handling that includes establishing a client-server session, receiving a time-out parameter, presenting an interactive notification to the user, and initiating a dummy client request to keep the session alive before interruption, ensuring users are aware of impending time-outs and allowing them to take action to prevent session loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If the server side session is terminated after a time span without client-server communication, then the server resource usage is optimized, but the user experience deteriorates and activity results are lost

Engineering Contradiction:
Improveserver resource usageVSAvoiduser experience and activity results
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system performs preliminary action by notifying the user before the session is actually terminated. The notification is displayed at a predetermined time interval before the timeout occurs, giving the user advance warning to complete or save their work, thus preventing loss of activity results while still allowing the server to terminate the session for resource optimization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by providing real-time notification to the user about the approaching session timeout. This feedback loop allows the user to take corrective action (save work, log out, or extend session) before the session is terminated, resolving the contradiction between server resource management and user experience.

Inventive Principle:
Principle #23Feedback

2Device complexity

If no notification is provided to users before session termination, then the system complexity is reduced, but the loss of information increases as users are unaware of session expiration

Engineering Contradiction:
Improvesystem complexityVSAvoidactivity results
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The notification mechanism performs preliminary action by alerting users before the session is terminated. This simple advance notice prevents information loss by giving users time to save their work, without requiring complex prediction or analysis systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service by automatically notifying users of upcoming session termination without requiring user configuration or complex system intervention. The notification is automatically displayed at the predetermined time interval, and users can independently decide how to respond.

Inventive Principle:
Principle #25Self-service

3Reliability

If the server side session holds context information for extended periods, then the user experience is improved, but the server resource consumption increases

Engineering Contradiction:
Improveuser experienceVSAvoidserver resource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

By notifying users in advance of session termination, the system allows users to complete or save their work before the session ends. This enables the server to terminate sessions at the predetermined time interval without losing user work, thus maintaining good user experience while optimizing server resource usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses periodic action by terminating sessions at predetermined time intervals without communication. The notification is displayed at a specific interval before termination, creating a regular cycle that balances resource management with user experience.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentEP1777675B1Network time out handling
Publication Date: 2011.04.27 SAP SE
  • EP1777675B1 patent drawingFigure 1~3
  • EP1777675B1 patent drawingFigure 4
  • EP1777675B1 patent drawingFigure 5A

AI summary

An example method for time-out handling comprises establishing a session from a network-based application at a client to a web server. The method includes identifying a time-out parameter for the web server. A timestamp of the established session is saved at the client. The method also includes determining a first time-out by adding the identified time-out parameter to the timestamp and triggering a system-based communication from the network-based application to keep the session alive. The method may be implemented by a client of a learning management system.