System for managing inactivity in concurrently operating executable applications

• US 20060059556A1
• Filed: 09/09/2005
• Published: 03/16/2006
• Est. Priority Date: 09/10/2004
• Status: Abandoned Application

• Current Assignee: Siemens Medical Solutions Health Services Corporation (Siemens AG)
• Original Assignee: Siemens Medical Solutions Health Services Corporation (Siemens AG)
• Inventors: Royer, Barry Lynn
• Application Number:
  US11/223,305
• Publication Number:
  US 20060059556A1
• Time in Patent Office: Days
• US Class Current: 726/22
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 2209/508 Monitor
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

A system, for use with a first application concurrently operating together with a second application, includes an activity manager and a communication processor. The activity manager intermittently receives data identifying activity associated with the first application, and determines that the first application is inactive in response to a first application timeout window being exceeded because of insufficient activity associated with the first application. The communication processor communicates to a managing application an indication that the first application is inactive, and receives from the managing application an indication that the second application is inactive determined in response to a second application timeout window being exceeded because of insufficient activity associated with the second application.

Claims

1. A system for use in a first application concurrently operating together with a second application, comprising:

an activity manager for intermittently receiving data identifying activity associated with said first application and determining said first application is inactive in response to a first application timeout window being exceeded because of insufficient activity; and

a communication processor for communicating to a managing application an indication said first application is inactive and for receiving from said managing application an indication said second application is inactive determined as a result of a second application timeout window being exceeded due to insufficient activity associated with said second application.

2. A system according to claim 1, wherein

said first and second applications are concurrently operating applications of a particular user initiated session, and

said activity manager initiates logoff of said particular user initiated session in response to a determination that both said first and second applications are inactive.

3. A system according to claim 1, wherein

said first and second applications are concurrently operating applications of a particular user initiated session, and

said communication processor receives from said managing application an indication said second application is active determined as a result of sufficient activity associated with said second application preventing said second application timeout window being exceeded and

said activity manager inhibits logoff of said particular user initiated session in response to a determination said second application is active.

4. A system according to claim 1, wherein

said intermittently received data identifying activity prevents an inactivity timeout of said first application, and

said first and second applications are concurrently operating applications of a particular user initiated session.

5. A system according to claim 1, wherein

said managing application comprises said second application.

6. A system according to claim 1, wherein

said managing application interrogates said second application to determine if said second application timeout window is exceeded in response to said indication that said first application is inactive.

7. A system according to claim 1, wherein

said user action comprises at least one of the following:

(a) keyboard activity, (b) mouse activity, (c) other data input device activity, and (d) another user initiated personal computer (PC) application operation activity.

8. A system according to claim 1, wherein

said first application and said managing application reside in the same personal computer (PC), and

said indication said first application is inactive includes one or more of the following:

(a) a session identifier for identifying a particular user initiated session, (b) a universal resource locator (URL) to be contacted if said activity notification is not successful, and (c) an identification of a type of event preventing said activity notification from being successful.

9. A system according to claim 1, including

an entitlement processor enabling user access to said first application in response to validation of user identification information, and

said communication processor communicates with a browser application providing a user interface display permitting user entry of identification information for validation by said entitlement processor.

10. A system for use by a managing application supporting concurrent operation of a first application together with a second application, comprising:

an input processor for receiving an activity status indication from said first application identifying whether said first application is inactive; and

a communication processor for, in response to said received activity status indication from said first application,

communicating to said second application, data indicating a change of status of said first application from active to inactive;

receiving from said second application data indicating said second application activity status; and

communicating data indicating said second application activity status to said first application.

11. A system according to claim 10, wherein

said first and second applications are concurrently operating applications of a particular user initiated session.

12. A system according to claim 11, wherein

said first application initiates logoff of said particular user initiated session in response to a determination both said first and second applications are inactive.

13. A system according to claim 11, wherein

said managing application initiates logoff of said particular user initiated session in response to a determination that both said first and second applications are inactive.

14. A system according to claim 10, wherein

said input processor receives said activity status indication in data representing a plurality of different commands including an activity notification command, and a command involving at least one of the following:

(a) determining a user operation session identifier from said managing application and (b) sending a universal resource locator (URL) to said managing application.

15. A system according to claim 10, wherein

said activity status indication includes one or more of the following:

(a) an identification of a particular user initiated session, (b) a URL to be contacted if said activity notification is not successful, and (c) an identification of a type of event preventing said activity notification from being successful.

16. A system supporting concurrent operation of a plurality of Internet compatible applications, comprising:

a browser application providing a user interface display permitting user entry of identification information and commands for a plurality of Internet compatible applications; and

a managing application for exchanging data representing activity status indications between a plurality of concurrently operating applications, said activity status indications being received from individual applications of said plurality of concurrently operating applications and indicating change of status of individual applications from active to inactive, said plurality of concurrently operating applications being initiated by user commands via said browser user interface.

17. A method for use in a first application concurrently operating together with a second network compatible application, comprising the activities of:

intermittently receiving data identifying activity associated with said first application and determining said first application is inactive in response to a first application timeout window being exceeded because of insufficient activity;

communicating to a managing application an indication said first application is inactive; and

receiving from said managing application an indication said second application is inactive determined because of a second application timeout window being exceeded due to insufficient activity associated with said second application.