Network time out handling

• US 20070115845A1
• Filed: 10/24/2005
• Published: 05/24/2007
• Est. Priority Date: 10/24/2005
• Status: Active Grant

• Current Assignee: ServiceNow Incorporated
• Original Assignee: SAP AG (SAP SE)
• Inventors: Philipp, Marcus, Hochwarth, Christian, Erhard, Martin, Krebs, Andreas
• Granted Patent: US 7,921,208 B2
• Time in Patent Office: Days
• US Class Current: 370/252
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

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.

Claims

1. A method for time-out handling comprising:

establishing a session from a network-based application at a client to a web server;

identifying a time-out parameter of the web server;

saving a timestamp of the established session at the client;

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.

2. The method of claim 1, the network-based application comprising a learning content player.

3. The method of claim 2, the learning content player comprising a client of a learning management system, which further includes the web server, and the client comprising a timer API operable to track time between communications.

4. The method of claim 1, further comprising:

presenting an interactive notification to a user of the network-based application of a time-out approaching; and

triggering the communication after the user interfaces with the notification.

5. The method of claim 4, wherein presenting the notification comprises presenting the notification if the timestamp falls within of a certain timeframe.

6. The method of claim 1, further comprising resetting the timestamp based on the triggered communication.

7. The method of claim 6, further comprising incrementing a counter in response to the triggered communication.

8. The method of claim 7, further comprising continuing to trigger system-based communications to keep the session alive.

9. The method of claim 8, wherein continuing to trigger communications comprises continuing to trigger communications within a certain timeframe.

10. The method of claim 8, wherein continuing to trigger communications comprises continuing to trigger communications until the counter reaches a threshold.

11. The method of claim 10, further comprising, after the threshold is reached, presenting an interactive notification to a user of the network-based application of a time-out approaching and triggering the communication after the user interfaces with the communication.

12. The method of claim 1, further comprising saving recovery data prior to a subsequent time-out.

13. The method of claim 1, the triggered communication comprising one of the following:

a ping;

a servlet function;

a SCORM method;

a request to identify the web server;

or

a request for a time at the webserver.

14. Software for time-out handling operable to:

establish a session from a network-based application at a client to a web server;

identify a time-out parameter of the web server;

save a timestamp of the established session at the client;

determine a first time-out by adding the identified time-out parameter to the timestamp; and

trigger a system-based communication from the network-based application to keep the session alive.

15. The software of claim 14, the network-based application comprising a learning content player.

16. The software of claim 15, the learning content player comprising a client of a learning management system, which further includes the web server.

17. The software of claim 14, further operable to:

present an interactive notification to a user of the network-based application of a time-out approaching; and

trigger the communication after the user interfaces with the notification.

18. The software of claim 17, wherein the software operable to present the notification comprises software operable to present the notification if the timestamp falls within a certain timeframe.

19. The software of claim 14, further operable to reset the timestamp based on the triggered communication.

20. The software of claim 19, further operable to increment a counter in response to the triggered communication.

21. The software of claim 20, further operable to continue to trigger system-based communications to keep the session alive.

22. The software of claim 21, wherein the software operable to continue to trigger communications comprises software operable to trigger communications within a certain timeframe.

23. The software of claim 21, wherein the software operable to continue to trigger communications comprises software operable to trigger communications until the counter reaches a threshold.

24. The software of claim 23, further operable, after the threshold is reached, to present an interactive notification to a user of the network-based application of a time-out approaching and trigger the communication after the user interfaces with the communication.

25. The software of claim 14, further operable to save recovery data prior to a subsequent time-out.

26. The software of claim 14, the triggered communication comprising one of the following:

a ping;

a servlet function;

a SCORM method;

a request to identify the web server;

or

a request for a time at the webserver.

27. A system for time-out handling comprising:

means for establishing a session from a network-based application at a client to a web server;

means for identifying a time-out parameter of the web server;

means for storing a timestamp of the established session at the client;

means for determining a first time-out by adding the identified time-out parameter to the timestamp; and

means for triggering a system-based communication from the network-based application to keep the session alive.

28. A system for time-out handling, comprising:

memory storing a network-based application; and

one or more processors operable to;

establish a session from a network-based application at a client to a web server;

identify a time-out parameter of the web server;

store a timestamp of the established session in memory;

determine a first time-out by adding the identified time-out parameter to the timestamp; and

trigger a system-based communication from the network-based application to keep the session alive.

29. The system of claim 28, the network-based application comprising a learning content player.

30. The system of claim 29, the learning content player comprising a client of a learning management system, which further includes the web server.

31. The system of claim 28, the one or more processors operable to:

present an interactive notification to a user of the network-based application of a time-out approaching; and

trigger the communication after the user interfaces with the notification.

32. The system of claim 31, wherein the one or more processors operable to present the notification comprises one or more processors operable to present the notification if the timestamp falls within a certain timeframe.

33. The system of claim 28, the one or more processors further operable to reset the timestamp based on the triggered communication.

34. The system of claim 33, the one or more processors further operable to increment a counter in response to the triggered communication.

35. The system of claim 34, the one or more processors further operable to continue to trigger system-based communications to keep the session alive.

36. The system of claim 35, wherein the one or more processors operable to continue to trigger communications comprises one or more processors operable to trigger communications within a certain timeframe.

37. The system of claim 35, wherein the one or more processors operable to continue to trigger communications comprises one or more processors operable to trigger communications until the counter reaches a threshold.

38. The system of claim 37, the one or more processors further operable, after the threshold is reached, to present an interactive notification to a user of the network-based application of a time-out approaching and trigger the communication after the user interfaces with the communication.

39. The system of claim 28, the one or more processors further operable to save recovery data prior to a subsequent time-out.

40. The system of claim 28, the triggered communication comprising one of the following:

a ping;

a servlet function;

a SCORM method;

a request to identify the web server;

or

a request for a time at the webserver.