Automatic detection of agents

[0001] This application is based on and hereby claims priority to Indian Application No. 606/KOL/06 filed on Jun. 19, 2006 and PCT Application No. PCT/EP2007/056010 filed on Jun. 18, 2007, the contents of which are hereby incorporated by reference.

[0002] The invention concerns a method, a telecommunication network, and a central directory service element for managing components of the telecommunication network.

[0003] A telecommunications network is usually composed of different types of agents NE (which agents could also e.g. be “Network Elements” here).

[0004] An operator uses a Manager EM (which Manager could e.g. be an “Element Manager” here) to manage these agents. In order to manage a agent, the operator has to carry out some steps for configuring the agent on the manager like providing the address of the NE for communication, the user information to access the NE and so on. Similarly the operator also has to go through a few steps to configure the Manager on the Agent. These steps may vary depending on the type of the agent. Great care has to be taken while performing the administration since any mistake would mean more time will be spent on correcting it. Some times it is also required to configure the same agent on more than one managers.

[0005] All the agents in the telecommunications network need not be supplied by the same vendor. Vendors of agents usually provide their own Manager System to manage their NEs. The way these administrative steps have to be carried out on each of these Managers might differ significantly. This introduces additional overhead for the operator since he has to work on different Manager Systems.

[0006] Thus, the time and effort spent by the operator can be minimized if there is a more simple way of administering any type of NE on any Element Manger. This solution provides an automatic way of detecting Agents and Managers.

[0007] Currently, no solution exists which provides a single and easy way to administer NEs. Some solutions exist for automatic detection of agents in the SNMP world but these are specific to devices which support the SNMP protocol and do not present a generalized approach for all NE types. This solution cannot be extended to other protocols since implementing such a feature might not be possible because of restrictions imposed by the basic principle of the protocol. On the other hand the current idea proposes a generic framework for automatic detection of all type of NEs.

[0008] U.S. Pat. No. 5,909,549A describes a “Management station locating method for computer network management system”. This solution is specific to the SNMP protocol

[0009] US2003112765A1 describes a “Network devices discovering for data communication network”. This solution is also specific to SNMP protocol FI9901022A describes a “Agent connecting method in telecommunications network”. This solution only allows a Agent to connect to a Network Management system whereas the proposed solution allows a connection to be established from the Network Management system to the NE also.

[0010] It is one possible object to improve the configuration of network components in a telecommunication network.

[0011] The inventors propose a telecommunication network having agents, managers for configuring agents, and at least one central directory service element with a memory to store information about the agents and the managers, which information is at least partly used in case of a further agent or manager is inserted into the telecommunication network.

[0012] The inventors also propose a method for configuring agents and managers in a telecommunication network. According to the method, information is stored about agents and the managers of the telecommunication network, the information being stored in a memory of a central directory service element. This information is used to selectively notify the agents and managers of the telecommunication network when a new agent and/or a new manager is inserted into the telecommunication network and to configure communication with the new agent and/or manager.

[0017] Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like elements throughout.

[0018] The proposed solution allows automatic detection of Agents (NE) and Managers (EMs). To achieve this, the idea introduces a “Central Directory Service” (CDS) into the network. The CDS stores information about all the Agents (NE) and the Managers (EM) available in the network. Any new NE which comes into the network can retrieve the list of managers EMs from the CDS and initiate the process of automatic detection with the help of the CDS. Similarly, a new EM can also get the list of NEs available in the network from the CDS and trigger the process of automatic detection.

[0019] The automatic detection of the NE or the EM can be made more reliable by introducing a handshake procedure between the NE and the EM.

[0020] System Architecture

[0021] FIG. 1 shows the architecture of the proposed system. The difference of this architecture from the existing Network Management Framework is the addition of the central directory service (CDS) and a handshake procedure between the NE and the EM. The architecture of the CDS and the handshake mechanism is explained in the following sections.

[0022] Central Directory Service

[0023] The central directory service (CDS), is a directory containing information about all the Agents and Manager systems within the network. The CDS provides interfaces through all protocols supported by the different NEs and EMs Thus NEs and EMs can access the same information using their native protocol itself. An object model which outlines the data that will be contained in the CDS and the operations that can be performed on the CDS is described.

[0024] Object Model for CDS

• • [0025] ManagedObjectClass
  • [0026] centralDirectoryService
  • [0027] “This object describes a central directory service class which would hold details about Agents, Managers available in a network.’

[0028] Attributes

• • [0029] i. centralDirectoryServiceDetails—‘Connection details of the CDS’
    • [0030] Port Number
    • [0031] IP Address
  • [0032] ii. neDetails—‘Details of a NE’
    • [0033] NeIdentifier—^Graphic String that identifies the NE′
    • [0034] NeType (as described below)
    • [0035] TaskDBDetails (as described below)
    • [0036] SupportedInterfaces (as described below)
    • [0037] SupportedApplications (as described below)
    • [0038] Contained Devices
  • [0039] iii. neDetailsList—‘To capture the list of Ne Managed by EM’
    • [0040] List of NEDetails
  • [0041] iv. ElementManagerDetails—‘Details of an EM’
    • [0042] ElementManagerIdentifier (as described below)
    • [0043] TaskDBDetails (as described below)
    • [0044] SupportedNETypes—same as the NeType (as described below)
    • [0045] SupportedApplications (as described below)
    • [0046] SupportedInterfaces (as described below)
    • [0047] ManagedNeDetails—is NeDetailsList
  • [0048] v. ElementManagerDetailsList—‘To capture the list of available EMS’
    • [0049] List of ElementManagerDetails
  • [0050] vi. neDeviceDetails—‘The fields that will be used will depend on the protocol’
    • [0051] NeDeviceID—‘graphic string which identifies the Ne Device’
    • [0052] IPAddress—‘graphic string that gives the IP address’
    • [0053] ApplicationTitle—‘APT—“1 3 12 2 1107 3 84 20 0”
    • [0054] Application Entity—203
    • [0055] Application Context—‘0 2 262 1 3 10 0 4’
    • [0056] P Sel
    • [0057] S Sel
    • [0058] T Sel
    • [0059] Listening Port
    • [0060] ManagerEMDetails—is ElementManagerDetailsList
    • [0061] ContainedDevices—‘Each NE Device can have contained devices A NE might be composed of more than one device capable of communicating with EM’
  • [0062] vii. ContainedDevices—‘This is to capture the containment of Nodes or Sub-Nodes’
    • [0063] List of NeDeviceDetails—List of NeDeviceDetails
  • [0064] viii. ElementManagerIdentifier—‘Address information of the EM’
    • [0065] ElementManagerId—‘Graphic String that identifies the EM’
    • [0066] ElementManagerIPAddress—‘Graphic string which has the IP Address’
  • [0067] ix. ElementManagerList
    • [0068] List of ElementManagerIdentifier
  • [0069] x. neType—‘Describes the type of NEs available in the network. This is not an exhaustive list. Only a sample list is provided to indicate what this attribute means’
    • [0070] CP
    • [0071] CPMP
    • [0072] MPSP
    • [0073] SP
    • [0074] ngRNC node B
    • [0075] MSC
    • [0076] BSC
  • [0077] xi. taskDBDetails—‘Describes the task object file of the NE. It is a free string to identify the task db of the NE’
    • [0078] GraphicString
  • [0079] xii. supportedInterfaces—‘Interfaces that will be supported by NEs and EMs in the network. ^λThis is not an exhaustive list. Only a sample list is provided to indicate what this attribute means’
    • [0080] MML
    • [0081] Q3
    • [0082] SNMP
    • [0083] CORBA
    • [0084] FT
    • [0085] TELNET
  • [0086] xiii. supportedApplications—‘Applications that will be supported by NEs and EMs in the network. ‘This is not an exhaustive list. Only a sample list is provided to indicate what this attribute means’
    • [0087] FM—Fault Management
    • [0088] CM—Configuration Management
    • [0089] PM—Performance Management
    • [0090] SM—Security Management
      Actions
  • [0091] i. registerNEwithCDS ([in] NeDetails)
    • [0092] To register the NeDetails to the CDS
  • [0093] ii. registerEMwithCDS ([in] ElementManagerDetails)
    • [0094] To register the EM to the CDS
  • [0095] iii. UnregisterNEwithCDS ([in] NeDetails)
    • [0096] To Unregister the NeDetails to the CDS
  • [0097] iv. UnregisterEMwithCDS ([in] ElementManagerDetails)
    • [0098] To Unregister the EM to the CDS
  • [0099] v. getAIINEsRegisteredWithCDS ([in] ElementManagerDetails, [out] NeDetailsList)
    • [0100] To get the NEs registered in the CDS
    • [0101] The ElementManagerDetails is looked into to validate the EM
    • [0102] The NeDetailsList should be a list of NEs which match the NeType as mentioned in ElementManagerDetails SupportedNETypes
  • [0103] vi. getAllEMsRegisteredWithCDS ([in] NeDetails, [out] ElementManagerDetailsList)
    • [0104] To get the EMs registered in the CDS
    • [0105] The NeDetails is looked into to validate the NE
    • [0106] The ElementManagerDetails should be a list which match the SupportedNeType as mentioned in the NeDetails NeType
  • [0107] vii. getNEFromCDS ([in] NeIdentifier, [in] ElementManagerDetails, [out] NeDetails)
    • [0108] To get one NE which was added to the CDS
    • [0109] The ElementManagerDetails is used for validation
    • [0110] The ElementManagerDetails SupportedNeType would be used to check if the NE asked for can be managed by this EM
  • [0111] viii. getEMFromCDS ([in] ElementManagerIdentifier, [in] NeDetails, [out] ElementManagerDetails)
    • [0112] To get one EM which was added to the CDS
    • [0113] The NeDetails is used for validation
    • [0114] The NeDetails NeType would be used to check if the EM asked for can manage this NE
      Notifications
  • [0115] i. broadcastSelf ( )
    • [0116] This notification broadcasts periodically the details of central directory services, that is the central DirectoryServiceDetails
  • [0117] ii. broadcastNECreated ( )
    • [0118] This notification is given to all the EMs registered in the CDS whenever a NE is created
  • [0119] iii. broadcastEMCreated ( )
    • [0120] This notification is given to all the NEs registered in the CDS whenever a EM is created

[0121] Availability of the CDS

[0122] Since the CDS is a single source of information about the network, a failure in the CDS can affect the normal functioning of the network. It should be possible to have a redundant CDS in order to prevent such a situation. The data contained in the CDS does not change very dynamically hence replicating the data on another CDS should be easy using any existing technique for replication. In case a working CDS goes down, the redundant CDS can take over. Different ways exist using which the redundant CDS can learn about the failure of the primary CDS. For example, The redundant CDS can know about the failure if the broadcastSelf () notification is not received for a predefined interval.

[0123] Handshake Between the NE and EM

[0124] Once the automatic detection of the NE and the EM is complete, the NE and the EM can communicate with each other. But when the EM does not want to manage a NE or when a NE does not want to be managed by an EM, there has to be some mechanism to undo the automatic detection. This can be achieved by introducing a mechanism which will enable the NE to communicate its willingness to be managed by the EM and the EMs willingness to manage the NE. This can either be achieved automatically or through manual intervention by the operator. This mechanism is referred to as the handshake between the NE and the EM.

[0125] System Functioning

[0126] The CDS maintains a list of all NEs and EMs that are currently available in the network. It periodically sends the “broadcastSelf” notification to all the NEs and the EMs. Any new NE or EM which is introduced into the network should register itself with the CDS giving all the required details. Two different cases exist, which are explained below

[0127] Example of a Handshake Mechanism

[0128] The following example of a handshake mechanism is considered for explaining the two cases. The EM sends a task to the NE after it completes the administration. The NE sends a notification to the Manager after sending the response to the task. For the handshake to complete the EM should have successfully executed the task and should also have received the notification from the NE. If the task fails or if the notification is not received from the NE by the EM, it does not administer the NE. If the NE does not receive a task from the EM for a predefined period, it does not administer the EM. The EM retries the task a few times before giving up.

[0129] Case 1 (FIG. 2): A new NE is Created

a. NE waits for the broadcastSelf ( ) notification from the CDS after it is brought up.

b. NE registers with CDS using registerNEWithCDS ( )

c. CDS broadcasts this information to all the managers which are suitable for this NE type using the notification broadcastNECreated ( )

d. The managers retrieve details about the NE using getNEFromCDS ( )

e. The managers administer these NEs automatically.

f. The NE retrieves information about all the EMs using getAllEMsRegisteredWithCDS ( )

g. NE administers the EM

h. The NE and the EM perform the handshake to complete the administration

i. Steps g to f are repeated for all EMs.

[0130] Case 2 (FIG. 3): A new EM is created

a. EM waits for the broadcastSelf ( ) notification from the CDS

b. EM registers with CDS using registerEMWithCDS ( )

c. CDS broadcasts this information to all the NEs which can be managed by the EM using broadcastEMCreated ( ).

d. The NEs retrieve the information about the EM using getEMFromCDS ( )

e. NEs administer the EM automatically.

f. The EM retrieves all the NEs from the CDS using getAllNEsRegisteredWithCDS ( )

g. EM administers the NE

h. The NE and the EM perform the handshake to complete the administration

i. Steps g to f are repeated for all NEs

[0131] Possible Key Features of the Solution

[0132] 1. A method of automatic detection of Agents and Managers in a network using a Central Directory Service, enabled by an object model, which allows a new Agent or Manager to be discovered and administered automatically.

[0133] 2. An improved method of automatic detection of Agents and Managers in a network using a Central Directory Service, enabled by an object model and a handshake mechanism between the NE and the EM, in which the handshake mechanism confirms that the NE and the EM which were detected automatically are interested in communicating with each other.

[0134] 3. An improved method of automatic detection of Agents and Managers in a network using a Central Directory Service, enabled by an object model, in which redundancy is provided to the CDS to prevent the CDS from becoming a single point of failure.

[0135] Possible Advantages of the Solution

[0136] 1. If a new NE has to be administered, the operator only has to introduce the NE into the network. The Automatic detection process will enable the operator to manage the NE from an Manager almost immediately.

[0137] 2. If a new EM has to be introduced, then the operator does not have to administer all the NEs on the EM. The automatic detection process will ensure that the manager starts managing the NEs. We can thus make the EM Apluggable' into any network.

[0138] 3. Since the CDS provides interfaces using all available protocols, all NEs, irrespective of the protocol supported by them, can be discovered automatically.

[0139] 4. The operator need not remember the steps required to configure a NE or an EM. There is also the benefit of quicker and error free configuration.

[0140] 5. A standardized object model for the CDS will allow interoperability between NEs and EMs from different vendors. This will give the operator an advantage of managing the whole network composed of NEs from different vendors on a single manager of his choice.

[0141] The invention has been described in detail with particular reference to preferred embodiments thereof and examples, but it will be understood that variations and modifications can be effected within the spirit and scope of the invention covered by the claims which may include the phrase “at least one of A, B and C” as an alternative expression that means one or more of A, B and C may be used, contrary to the holding in Superguide v. DIRECTV, 69 USPQ2d 1865 (Fed. Cir. 2004).