Configuration recovery after gateway failure

• US 7,206,826 B1
• Filed: 10/25/2001
• Issued: 04/17/2007
• Est. Priority Date: 10/25/2001
• Status: Expired due to Fees

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Parker, Benjamin J., Diaz, Charles, Werner, Shane W., Frederick, Terry M
• Primary Examiner(s): Najjar; Saleh
• Assistant Examiner(s): Bates; Kevin T
• Application Number:
  US10/054,103
• Time in Patent Office: 2,000 Days
• Field of Search: 709/206, 709/223, 709/227, 709/228, 709/220, 214/2, 214/6, 214/15
• US Class Current: 709/220
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

User connection sessions with a gateway in a computer network are preserved even after a temporary failure of the gateway. User status information is stored in a status table in a RADIUS server during times that an authenticated user session is established with the gateway. A failure of the gateway is detected wherein user data stored in the gateway is lost. The gateway sends a request to the RADIUS server to provide the user status information and user data corresponding to each user in the status table. The gateway routes the user traffic to continue the authenticated user session in response to the user data and the user status information without requiring re-authentication following the failure.

Claims

1. A method of managing user connection sessions with a gateway in a computer network, said method comprising the steps of:

storing user data on said gateway in response to authentication by said user;

storing user status information in a table in a RADIUS server during times that an authenticated user session is established with said gateway, said RADIUS server being on a physically separate machine than said gateway and being connected to said gateway via said computer network;

deleting said user status information from said table when said authenticated user session is terminated;

said gateway routing said user traffic in response to said user data;

detecting a failure of said gateway wherein said stored user data is lost;

said gateway sending a request to said RADIUS server to provide said user status information and user data corresponding to each user in said table;

storing said user data on said gateway; and

said gateway routing said user traffic to continue said authenticated user session in response to said user data and said user status information without requiring re-authentication following said failure.

2. The method of claim 1 wherein said user status information includes an IP address assigned to said user for said session.

3. The method of claim 1 wherein said detecting step is comprised of a power-up initialization.

4. The method of claim 1 wherein said step of requesting said RADIUS server to provide said user status information and said user data is included in a boot-up sequence of said gateway.

5. The method of claim 1 wherein said user data comprises a host object and a connection object.

6. The method of claim 5 wherein said step of storing user status information in said table is delayed until a connection object is created for said user.

7. The method of claim 1 wherein said gateway is comprised of a service selection gateway.