Resumption of user authentication and restoration of interrupted virtual sessions in a stateless network

• US 20030233361A1
• Filed: 06/13/2002
• Published: 12/18/2003
• Est. Priority Date: 06/13/2002
• Status: Abandoned Application

• Current Assignee: McKesson Information Solutions LLC (McKesson Corp.)
• Original Assignee: McKesson Information Solutions LLC (McKesson Corp.)
• Inventors: Cady, C. Conrad
• Application Number:
  US10/172,178
• Publication Number:
  US 20030233361A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session

Abstract

This invention is embodied in an interactive message communication system in a stateless network such as the Internet, providing for resumption of user authentication and restoration of interrupted virtual sessions without loss of data or disruption of workflow. When a user enters the application from any source, he starts a new session by a successful login. The login page includes hidden contextual information describing the initial user request. The hidden contextual information, once submitted together with the proper user ID and password is used to resume the user request and allow the Web server to respond. While in the circumstances where a session is expired or timed-out, when the user completes his message and submits his request, the Web server sends the hidden contextual information included in the request, along with a login page, back to the browser. The user is required to reenter his login information. When he logs in again, all contextual information included in his original request is resubmitted with the login information. An authenticator in the Web server then verifies the login information against the server'"'"'s database. If the login information is correct, the user is authenticated, and therefore his request is proceeded and the virtual session is restored without loss of data. If the login information is incorrect, the authentication fails, and the login page is returned to the browser. This cycle may be repeated as many times as the user submits incorrect login information. Alternatively, it may be repeated until a predetermined number of attempts is reached, at which point the server refuses to respond further.

Claims

1. A process, embodied in an interactive message communication system via a stateless network, for resuming user authentication and restoration of interrupted virtual sessions without loss of data or disruption of workflow, comprising the steps of:

receiving a service request from a user who has logged into a service provider Website application via a browser running on a Web client device,

wherein said service provider Website application runs on a Web server coupled to a Web content, a database, and an authenticator;

authenticating said user, wherein said Web server returns a login page to said browser if authentication fails for any reason; and

upon a successful authentication, proceeding said service request submitted by said user.

2. A process as set forth in claim 1, wherein said step of receiving a service

request further comprises the steps of:

receiving URL and all contextual information associated with said service request, wherein said contextual information is the information that identifies where said user is and where he is going to during a communication session.

3. A process as set forth in claim 1, wherein said step of authenticating said user further comprises the sub-steps of:

checking whether a session already exists for said user,

wherein if there is no existing session found, a new session is created by extracting said user'"'"'s login information from said service request submitted by said user,

wherein if there is an existing session found, said authenticator retrieves said user'"'"'s original login information stored in said session; and

verifying said user'"'"'s login information against said database,

wherein if said login information is successfully verified, authentication success is returned, and thus said user'"'"'s service request is proceeded and the corresponding Web content is displayed on said user'"'"'s screen,

wherein if said login information is not verified for any reason, authentication failure will be returned and said login page will be sent to said browser.

4. A process as set forth in claim 3, further comprising the steps of:

if said login information is not verified for any reason, creating said login page that contains a login form, wherein said user'"'"'s original service request URL is retrieved and set to next URL for said login page;

formatting said user'"'"'s original contextual information into hidden fields in said login page; and

sending said login page along with said contextual information in hidden format to said user'"'"'s Web browser, from which said user is able to see said login page, re-enter his login information, and initiate a new login for authentication.

5. A process as set forth in claim 4, wherein said authenticator first conducts a registration check, wherein if said user has been disabled or deactivated or blocked off, said user is directed to a new user registration page so that said user may register as a new user.

6. A process as set forth in claim 4, wherein said steps from authentication failure to resubmission of login information may be repeated as many times as said user enters incorrect login information.

7. A process as set forth in claim 4, wherein said steps from authentication failure to resubmission of login information may be repeated until a predetermined number of attempts for login is reached, at which point said server refuses to respond further.

8. A process as set forth in claim 1, wherein said step of proceeding said service request further comprises any of the steps of:

sending a Web content selected by said user to said browser in an uninterrupted session; and

returning the Web content to which said user accessed immediately before interruption or timing-out in an interrupted session.

9. A process as set forth in claim 1, wherein said user is a service provider such as a physician or a customer such as a patient.

10. A process as set forth in claim 1, wherein said browser is any suitable browser software.

11. A process as set forth in claim 1, wherein said Web client device is a personal computer or a personal digital assistant or any other kind of Web-enabled devices capable of sending and receiving information via the Internet.

12. A process as set forth in claim 1, wherein said Web content entails all the services and data that said service provider Website application provides to its clients.

13. A method for restoration of an interrupted virtual session in a stateless network comprising the steps of:

authenticating said user when said Web server receives said user'"'"'s service request;

if authentication succeeds, restoring said session by returning a Web content to said browser, wherein said Web content is the Web content to which said user accessed immediately before said session was interrupted; and

if authentication fails for any reason, sending a login page, together with said contextual information associated with said service request, back to said browser, wherein said user is required to reenter his login information and submit said login information to said Web server for authentication.

14. A method as set forth in claim 13, wherein said authenticator calls a subroutine that leads to either an authentication failure or an authentication success.

15. A method as set forth in claim 14, wherein said subroutine comprises the sub-steps of:

checking whether a session already exists for said user,

wherein if there is no existing session found, said Web server creates a new session by extracting said user'"'"'s login information from said service request submitted by said user;

wherein if there is an existing session found, said Web server retrieves said user'"'"'s login information stored in said session; and

verifying said user'"'"'s login information against said database that contains said user'"'"'s correct login information,

wherein if said user'"'"'s login information matches with said user'"'"'s correct login information stored in said database, authentication success is returned;

wherein if said user'"'"'s login information does not match with said user'"'"'s correct login information stored in said database, authentication failure is returned and a second subroutine is called.

16. A method as set forth in claim 15, wherein said second subroutine comprises the sub-steps of:

creating a login page that contains a login form, wherein said user'"'"'s original request URL is retrieved and set to next URL for the login page;

formatting said original contextual information into hidden fields in said login page; and

sending said login page, together with said contextual information in hidden format, to said browser from which said user can see said login page.

17. A method as set forth in claim 15, wherein said second subroutine further comprises the steps of:

checking if said user has been disabled from said Web server,

wherein if said user has been disabled from said Web server for any reason, then said login page is not sent to said browser, instead, a new user registration page is sent to said browser in order that said user may register as a new user;

wherein ifsaid user is currently enabled but authentication fails for any reason, then said login page is sent to said browser.

18. A computer network comprising:

a service provider Website, wherein said service provider Website comprises a Web server, a Web content, and a database, wherein said Web content is coupled to an authenticator;

a number of service provider Web clients, wherein said service provider Web client comprises a browser installed on a service provider Web client device;

a number of service user clients, wherein said service user Web client comprises a browser installed on a service user Web client device;

an Internet via which said Web server, said service provider clients, and said service user Web clients communicate; and

further comprising means for;

receiving a service request from a user who has logged into a service provider Website application via a browser running on a Web client device,

wherein said service provider Website application runs on a Web server coupled to a Web content, a database, and an authenticator;

authenticating said user, wherein said Web server returns a login page to said browser if authentication fails for any reason; and

upon a successful authentication, proceeding said service request submitted by said user.

19. A computer network as set forth in claim 18, wherein said service provider Web site is a medical service provider Web site, wherein said service provider is a medical doctor or a doctor extender which may comprise any of a registered nurse, medical assistant or technician, pharmacy, medical device manufacturer or retailer, or any other person or entity which provides services to or on behalf of medical professionals, wherein said service user Web client is a patient for medical service.

20. A computer network as set forth in claim 18, wherein said browser may be any suitable browser software.

21. A computer network as set forth in claim 18, wherein said service provider Web client device and said service user Web client device may be a personal computer or a personal digital assistant or any other kind of Web-enabled devices capable of sending and receiving information via the Internet.

22. A computer network as set forth in claim 18, wherein said Web content entails all the services and data that said service provider Website provides to its clients.