Distributed user management information in telecommunications networks

• US 7,020,696 B1
• Filed: 11/01/2000
• Issued: 03/28/2006
• Est. Priority Date: 05/20/2000
• Status: Expired due to Term

• Current Assignee: Ciena Corporation
• Original Assignee: Ciena Corporation
• Inventors: Snow, Kevin D., Black, Darryl, Perry, James R.
• Primary Examiner(s): Maung, Zarni
• Assistant Examiner(s): Nguyen, Phuoc H.
• Application Number:
  US09/703,531
• Time in Patent Office: 1,973 Days
• Field of Search: 709223-229, 709205-207, 709/217, 709/219, 709/203
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0661 by reconfiguring faulty entities
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0829 Packet loss
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/16 Threshold monitoring
• 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

Abstract

The present invention provides a method and apparatus for implementing distributed user management information in telecommunications networks. At least a portion of a user'"'"'s management information is stored in a team session file that is accessible by a network management system (NMS) client. For example, the team session file may be saved in memory that is local to the NMS client or, if a user logs in through a remote system using a web browser, the team session file may be saved as a cookie in memory local to the remote system. The NMS client may then utilize the user management information in the team session file while the user is logged into the NMS client. In one embodiment, the user management information stored within the team session file includes NMS server connection information. Thus, when a user logs into an NMS client, the NMS client uses the NMS server connection information to connect to an NMS server. The user management information stored within the team session file may be retrieved from user profile information corresponding to the user and stored in a central data repository, and since the user profile data is stored in a central repository, changes may be easily made to the user profile data and consequently pushed out to the team session files accessible by one or more NMS clients. Consequently, a user'"'"'s management data may widely distributed for access by NMS clients located anywhere in the network.

Claims

1. A method, for managing a telecommunications network, comprising:

detecting a log-on request from a user at a network management system (NMS) client, wherein the log-on request includes a user identification;

accessing a team session file corresponding to the user identification and including current NMS server connection information;

connecting the NMS client to an NMS server using the current NMS server connection information included in the team session file;

wherein prior to detecting a log-on request from a user at an NMS client, the method comprises;

detecting an initial log-on request from the user at the NMS client;

receiving initial NMS server connection information from the user at the NMS client connecting to an NMS server using the initial NMS server connection information;

retrieving user profile data corresponding to the user identification from the NMS server;

wherein the user profile data includes the current NMS server connection information;

saving the current NMS server connection information and the user identification in the team session file;

wherein the log-on request is a first log-on request and the NMS server is a first NMS server, and wherein the method further comprises;

changing the current NMS server connection information in the user profile data;

sending the changed user profile data, including the changed current NMS server connection information, to the NMS client;

detecting a second log-on request from the user at the NMS client, wherein the second log-on request includes the user identification;

accessing the team session file corresponding to the user identification and including the changed current NMS server connection information; and

connecting the NMS client to a second NMS server using the changed current NMS server connection information included in the team session file.

2. The method of claim 1, wherein receiving initial NMS server connection information from the user at the NMS client, comprises:

displaying a connection dialog box to the user; and

receiving the initial NMS server connection information from the user through the connection dialog box.

3. The method of claim 1, wherein the team session file is stored locally to the NMS client.

4. The method of claim 1, wherein the log-on request is from a remote system through a web browser and the team session file is stored as a cookie in memory local to the remote system.

5. The method of claim 1, wherein the current NMS server connection information comprises primary NMS server connection information and secondary NMS server connection information and wherein connecting the NMS client to an NMS server using the current NMS server connection information included in the team session file, comprises:

sending a first connection request from the NMS client to a first NMS server using the primary NMS server connection information; and

sending a second connection request from the NMS client to a second NMS server using the secondary NMS server connection information if the first connection request fails.

6. The method of claim 1, wherein the user identification comprises a username.

7. The method of claim 1, wherein the current NMS server connection information comprises an NMS server port number.

8. The method of claim 1, wherein the current NMS server connection information comprises a domain name server (DNS) name.

9. A method for managing a telecommunications network, comprising:

detecting a log-on request from a user at a network management system (NMS) client, wherein the log-on request includes a user identification;

accessing a team session file corresponding to the user identification and including current NMS server connection information;

connecting the NMS client to an NMS server using the current NMS server connection information included in the team session file

wherein prior to detecting a log-on request from a user at an NMS client, the method comprises;

detecting an initial log-on request from the user at the NMS client;

receiving initial NMS server connection information from the user at the NMS client;

connecting to an NMS server using the initial NMS server connection information;

retrieving user profile data corresponding to the user identification from the NMS server;

wherein the user profile data includes the current NMS server connection information;

saving the current NMS server connection information and the user identification in the team session file;

wherein retrieving user profile data corresponding to the user identification from the NMS server, comprises;

retrieving user profile data at the NMS server from a central data repository, wherein the user profile data includes the current NMS server connection information;

generating a user profile logical managed object (LMO) at the NMS server, including the current NMS server connection information; and

sending the user profile LMO to the NMS client; and

wherein saving the current NMS server connection information and the user identification in the team session file, comprises;

saving the current NMS server connection information and the user identification from the user profile LMO in the team session file.

10. A method for managing a telecommunications network, comprising:

detecting a log-on request from a user at a network management system (NMS) client, wherein the log-on request includes a user identification;

accessing a team session file corresponding to the user identification and including current NMS server connection information;

connecting the NMS client to an NMS server using the current NMS server connection information included in the team session file

wherein prior to detecting a log-on request from a user at an NMS client, the method comprises;

detecting an initial log-on request from the user at the NMS client;

receiving initial NMS server connection information from the user at the NMS client;

connecting to an NMS server using the initial NMS server connection information;

retrieving user profile data corresponding to the user identification from the NMS server;

wherein the user profile data includes the current NMS server connection information;

saving the current NMS server connection information and the user identification in the team session file;

wherein retrieving user profile data corresponding to the user identification from the NMS server, comprises;

retrieving user profile data at the NMS server from a central data repository, wherein the user profile data includes the current NMS server connection information;

generating a user profile logical managed object (LMO) at the NMS server, including the current NMS server connection information;

generating a client user profile LMO at the NMS server, including at least the current NMS server connection information from the user profile LMO and in a format expected by the NMS client; and

sending the client user profile LMO to the NMS client; and

wherein saving the current NMS server connection information and the user identification in the team session file, comprises;

saving the current NMS server connection information and the user identification from the client user profile LMO in the team session file.

11. A method, for managing a telecommunications network, comprising:

detecting a log-on request from a user at a network management system (NMS) client, wherein the log-on request includes a user identification;

accessing a team session file corresponding to the user identification and including current NMS server connection information;

connecting the NMS client to an NMS server using the current NMS server connection information included in the team session file;

wherein prior to detecting a log-on request from a user at an NMS client, the method comprises;

detecting an initial log-on request from the user at the NMS client;

connecting to an NMS server using default NMS server connection information;

retrieving user profile data corresponding to the user identification from the NMS server,

wherein the user profile data includes the current NMS server connection information; and

saving the current NMS server connection information in the team session file;

wherein the log-on request is a first log-on request and the NMS server is a first NMS server, and wherein the method further comprises;

changing the current NMS server connection information in the user profile data;

sending the changed user profile data, including the changed current NMS server connection information, to the NMS client;

detecting a second log-on request from the user at the NMS client, wherein the second log-on request includes the user identification;

accessing the team session file corresponding to the user identification and including the changed current NMS server connection information; and

connecting the NMS client to a second NMS server using the changed current NMS server connection information included in the team session file.

12. A method for managing a telecommunications network, comprising:

detecting a logon request from a user at a network management system (NMS) client, wherein the log-on request includes a user identification;

accessing a team session file corresponding to the user identification and including current NMS server connection information;

connecting the NMS client to an NMS server using the current NMS server connection information included in the team session file;

wherein prior to detecting a log-on request from a user at an NMS client, the method comprises;

detecting an initial log-on request from the user at the NMS client;

connecting to an NMS server using default NMS server connection information;

retrieving user profile data corresponding to the user identification from the NMS server,

wherein the user profile data includes the current NMS server connection information; and

saving the current NMS server connection information in the team session file;

wherein retrieving user profile data corresponding to the user identification from the NMS server, comprises;

retrieving user profile data at the NMS server from a central data repository, wherein the user profile data includes the current NMS server connection information;

generating a user profile logical managed object (LMO) at the NMS server, including the current NMS server connection information; and

sending the user profile LMO to the NMS client; and

wherein saving the current NMS server connection information and the user identification in the team session file, comprises;

saving the current NMS server connection information and the user identification from the user profile LMO in the team session file.

13. The method of claim 12, wherein retrieving user profile data corresponding to the user identification from the NMS server, comprises:

retrieving user profile data at the NMS server from a central data repository, wherein the user profile data includes the current NMS server connection information;

generating a user profile logical managed object (LMO) at the NMS server, including the current NMS server connection information;

generating a client user profile LMO at the NMS server, including at least the current NMS server connection information from the user profile LMO and in a format expected by the NMS client; and

sending the client user profile LMO to the NMS client; and

wherein saving the current NMS server connection information and the user identification in the team session file, comprises;

saving the current NMS server connection information and the user identification from the client user profile LMO in the team session file.