Abstract: A method and Graphical User Interface (GUI) for viewing and editing attribute values of Managed Objects (MOs) representative of Network Elements (NEs) and NEs components of a managed network that use different versions of Management Object Model (MOM). An administrator selects one or more MOs from a list of MOs and the GUI displays the attribute values for each selected MO based on the MOM version information relative to the NEs that corresponds to the selected MOs. The administrator further edits one or more attribute values of one or more MO, which may include editing a first value of an MO, and then copying it to other MOs. The copied value is adapted to the MOM version used by the target MO(s), and then displayed on the GUI. Finally, the administrator issues a command, and the updated values are translated into commands understandable by the appropriate NEs, which received the commands.

Abstract: In a management system, a method, system, and agent for dynamically connecting event producers to event consumers, when the type of event notifications requested by event consumer(s) matches the type of event notification issued event producer(s). The agent receives advertisement or subscription request from event producers and consumers, and detects a match between the type of event notifications created by event producers and requested by event consumers. When a match is detected, the agent dynamically connects the egress port of the event producer to the ingress port of the event consumer. When another subscription request is received by the agent from another event consumer for the same type of event notifications, the agent first detects the optimal duplication node for duplicating the event notifications before sending them to both event consumers.

Abstract: An alarm notification structure, method, system, and management node for uniquely identifying alarm notifications. When a condition is met, a new alarm notification is created, the alarm comprising a SystemDN field identifying the alarm supplier that created the alarm, an alarm attribute carrying a payload and an alarm identifier field for uniquely identifying the alarm. The alarm identifier field comprises a path portion including a series of nodes corresponding to the path followed by the alarm, and the alarm identification as originally assigned. Each time the alarm is relayed by an intermediate node, that node appends its identity to the path portion of the alarm identifier field. When an operation is performed on the alarm, such as an acknowledgement operation, the alarm identifier field is used and sent in the acknowledgement message, so that intermediate nodes can know the path to be followed back for acknowledging the alarm.

Abstract: A method, system and agent for exchanging the Third Generation Partnership Project (3GPP) Technical Specification document number a first node uses, with a second node of the network, so that subsequent communications can be properly carried between the nodes. The first node may be an agent and the second node may be a manager of a management system. The manager sends a GetXXXIRPVersion request message, a GetNotificationCategories request message, or a GetNetworkResourceSchemeId request message, to which the agent responds with an abridged version of the 3GPP TS document number the agent uses in this type of communications, so that the manager is informed of the protocol employed by the agent and can expect communications of the type indicated by the agent.

Abstract: In an Alarm Management System (AMS) a method and a management network entity for forwarding and processing Alarm Information (AI) such as alarm notifications and alarm lists. The management network entity, that may be an Alarm Collector (AC), receives the AI from an upstream network entity such as an Alarm Reporter (AR) or another AC in a Forwarding Process (FP) that relays the AI concomitantly to at least one downstream network entity and to a Verification Process (VP) that synchronizes the internal Alarm List (IAL) of the management network entity. The forwarding of the AI may include filtering the AI based on the preferences of the downstream network entity. The FP and the VP are separated processes, software modules or software applications, that may run in parallel on the same, or on separated processors.