EP1261168A1 - Verfahren und Agenten zur Verarbeitung von Ereignismeldungen - Google Patents
Verfahren und Agenten zur Verarbeitung von Ereignismeldungen Download PDFInfo
- Publication number
- EP1261168A1 EP1261168A1 EP01440143A EP01440143A EP1261168A1 EP 1261168 A1 EP1261168 A1 EP 1261168A1 EP 01440143 A EP01440143 A EP 01440143A EP 01440143 A EP01440143 A EP 01440143A EP 1261168 A1 EP1261168 A1 EP 1261168A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- agent
- processing
- sub
- event information
- event
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
Definitions
- the present invention relates to a method for processing event information, that of network elements of a communication network to one that manages it Network management systems are reported by an event processing agent of the network management system, an event processing agent for this as well as a sub-agent for this.
- Communication networks for example computer networks or telecommunications networks, are monitored by network management systems and controlled.
- Network elements of a communication network for example exchanges, Routers, apron devices or the like send event information to the network management system that manages them.
- processing agents for example of the respective Network management system executed processing processes, provided that process the respective event information.
- the event information can be, for example, a malfunction in the managed network element or the Act if a limit value is exceeded, e.g. alarm messages, or status messages, for example changing the configuration status of the managed network element.
- the processing agent writes the event information for example into a database from which it e.g. from a user interface of the network management system is read out.
- the event database then reflects, for example, the event status of the managed network element contrary.
- a processing agent responsible for all alarm messages from one or more network elements be sent.
- the processing agent is at the system start of the Network management system started and is based on a configuration file the contact person for one or more managed network elements.
- the processing agent must therefore be designed so that it can handle all types of event information managed network element can be sent, processed.
- it changes something about the configuration of the network element for example because new software is loaded, the processing agent may possibly due to the new software version new event information and / or compared changed the content or formatting of the old software version Do not process event information.
- Another problematic situation occurs when a processing agent that event information is already responsible for one or more network elements to process another network element and is thus overloaded.
- the invention is based on the idea that the processing agent or a Central communication agent for one or more network elements event information received.
- the event information is taken over by one or more subagents are optimally suited for processing the respective event information.
- the processing agent or the communication agent central contact for other agents of the network management system.
- a User interface agent that is used to generate a user interface of the network management system is provided at the processing agent or Query communication agent event information. For the user interface agent it remains hidden that sub-agents do the actual processing the event information, for example the entry in an event database, make.
- querying event information e.g. by the user interface agent
- one by the processing agent controlled and monitored query sub-agent is provided.
- a processing agent in principle it is possible for a processing agent to have several subagents in parallel operates or, for example, only one sub-agent, whom he may use replaced a replacement sub-agent.
- the subagents i.e. the original subagent and the substitute subagent, can be active in succession in the latter case or in parallel for a transition phase.
- Forwarding event information and / or requests to subagents can be done by the processing agent or agents. However, one or more communication agents can also do this be provided.
- the concept of sub-agents enables the network management system to the respective system requirements, e.g. number and / or adapt the operating properties of the managed network elements dynamically.
- the processing agent can search for one or use several criteria, a few of which are exemplary below to be named:
- the processing agent expediently starts those subagents that optimally adapted to the quality of the event information to be processed are.
- a first sub-agent for processing event information of a first type and a second sub-agent for processing event information of a second type can be provided.
- the processing agent can exceed the respective load limit of a sub-agent with regard to event information to be processed. For example, when a load limit of a first sub-agent is reached a second sub-agent can be started by the processing agent. Becomes the second sub-agent can end the load limit again become.
- the load limit can be exceeded, for example, by that a subagent only for a predetermined number of network elements, for example two network elements, may be responsible. However, a load limit can can also be exceeded temporarily, for example if a malfunction occurs a lot of event information has to be processed.
- Another criterion can be an individual assignment of one or more Network elements to be provided as sub-agents.
- the processing agent can react dynamically to such changes and thereby advantageously start new sub-agents, for example for new ones added network elements are responsible, and / or terminate sub-agents, when a network element is removed from the managed communication network, for example when its operation is stopped.
- new sub-agents for example for new ones added network elements are responsible, and / or terminate sub-agents, when a network element is removed from the managed communication network, for example when its operation is stopped.
- an adaptation to local ones Changes for example when a network element with changed configuration data is operated and / or the network element is operated with new software is easily possible: the processing agent sends to the or sub-agents responsible for the respective network element, for example control data, with which they adapt to the new conditions in the managed network element be adjusted.
- the processing agent has one or several new sub-agents will be launched instead of or in addition to the since then sub-agents responsible for the managed network element.
- the processing agent maintains the functionality of its Sub-agents monitored and error handling in the event of a malfunction
- the processing agent can have one or more new ones Start subagents that replace the disrupted subagent.
- the inventive concept is suitable for processing any type of Event information.
- the Event information is alarm messages from managed network elements.
- the event processing agent is preferably a program module, the program code contains that from a control means of a server of the network management system can be executed.
- the processing agent it is also possible for the processing agent to be a separate computer of a network management system is.
- realizations are also made with regard to sub-agents possible in hardware and software.
- the communication network NW shown in FIG. 1 is operated by a network management system NMS with servers SV1 - SV3 manages and assigns network elements SW1-SW4 which are, for example, exchanges, routers or Service computer for the provision of services of a so-called intelligent network (IN) acts.
- the network management system NMS has one, for example open system architecture and is used for administration, maintenance and operation of the Network elements SW1 - SW4 and other network devices not shown in the figure of the communication network NW.
- At the communication network NW can be both a telecommunications network, for example a telephone or Data network, act or a local network, for example a LAN (Local Area Network).
- the network elements SW1-SW4 can, for example Terminals not shown, for example telephone terminals, personal computers or the like.
- the network elements SW1-SW4 are sources for event information, for example Exceeding limit values, faults, load information or the like, which they send to the network management system NMS.
- event processing agents VO1, VO2. These are a process or a group of processes, whose program code is executed by the server SV2.
- the serve Processing agents VO1, VO2 in the present case also for controlling the network elements SW1 - SW4.
- the processing agents VO1, VO2 can also be managed Designate objects (English managed objects) that the network elements SW1, Represent SW4 or SW2, SW3 within the network management system NMS. In any case, processing agents VO1, VO2 can only do one at a time Represent partial aspect of the network elements SW1 - SW4, for example only for alarm messages sent by them, or within the Network management systems fully represent NMS.
- the processing agent VO1 is responsible for the network elements SW1, SW4, the processing agent VO2 for the network elements SW2, SW3. It is also conceivable that for a processing agent is responsible for each of the network elements SW1-SW4. Furthermore, several processing agents could be assigned to a resource and represent them differently. For example, the processing agent VO1 alarms of the network element SW1 and the processing agent VO2 thereof Represent measured values. In addition, the processing agents could also immediately are formed by the network elements SW1, SW2, SW3, SW4 or by these executed processes.
- Management objects or management agents MO1, MO2 are provided are designed as processes or process groups executed by the server SV1.
- the management object MO1 can be used to troubleshoot faults the network elements SW1 - SW4 and the management object MO2 for displaying their operating states on a server SV1 executed user interface Ul.
- the servers SV1-SV3 are computers or computer networks by an operating system, such as Unix or Windows NT.
- the servers SV1-SV3 have transmitting and receiving means on, for example, Ethernet interface cards, modems or the like, which are suitable for sending and receiving data.
- storage media for example hard disks and RAM modules and control means are provided, for example, individual processors or clusters of processors.
- the control means run program code sequences under the control of an operating system from program modules which are stored in the storage means. For example, they carry program code for the user interface U1, the management objects MO1, MO2 and also the processing agents VO1, VO2.
- the network elements SW1, SW4 send event information via connections VS1 and VS4 to the processing agent VO1, the network elements SW2, SW3 via Connections VS2, VS3 event information to the processing agent VO2.
- the event information is, for example, messages, the limit violations, a current system load or traffic values of through the network elements SW1-SW4 used or operated connections.
- the network management system When the network management system is started, it starts the Processing agents VO1, for example based on configuration data and based on their program code, each in storage means, not shown of the server SV2 are stored.
- a request manager (request manager) RM who for processing requests sent by the manager objects MO1, MO2 is provided, as well as a shipping filter EFD, for example a so-called Event Forwarding Discriminator, which is assigned to processing agent VO1, started.
- a start process or Starting agent may be provided.
- the processing agents VO1, VO2 for which network elements they are responsible.
- configuration data for example using start parameters and / or a configuration file
- the processing agents VO1, VO2 for which network elements they are responsible.
- processing agents VO1, VO2 dynamically the Determine the respective configuration of the network elements, i.e. for example that the Processing agents VO1, VO2 e.g. determine at network start for which network elements they are responsible.
- the processing agent VO1 is initially for the network element SW1 responsible (the network element SW4 is still out of operation) and starts for Processing sub-agent event information sent by it S1.
- the processing agent VO1 has a starting function for this INI provided, for example, based on the configuration data mentioned above determines which type of subagent to process the event information of the network element SW1 is suitable, and accordingly a suitable program module as sub-agent S1.
- the INI start function can also the subagent S1 start parameters or other configuration parameters, the transmit this to process event information.
- the processing agent VO2 starts sub-agents S21, S22 for processing of event information sent by the network element SW2 and a sub-agent S31, which is used for processing by the network element SW3 sent event information is provided.
- the network element In the present case, SW2 sends different types of event information, for example Limit value messages and alarm messages to the processing agents VO2.
- One of the sub-agents S21, S22 is for one in each case or several types of different event information process them optimally.
- sub-agents S21, S22 have different functions execute, for example that the sub-agent S21 event information in a Records log file, while the sub-agent S22 may have one Initiates error handling.
- the processing agent can VO2 the same event information both on the sub-agents S21 and also forward to sub-agent S22.
- the subagent S31 is for processing event information of the network element SW3 provided this due to the currently loaded operating software K31 sends.
- one or several subagents each have an event database in which they are reported to them Enter event information so that it can be used, for example, by the management objects MO1, MO2 can be queried.
- the sub-agent S1 as such an event database shows an event mirror MIRS, so to speak at least partially reflects the event status of the network element SW1.
- the subagents S1, S21, S22, S31 communicate via connections V1, V21, V22 or V31 with the processing agents VO1 and VO2.
- the connections V1 - V31 are, for example, interprocess communication connections.
- each of the sub-agents is S1-S31 an independent process, that of the operating system, not shown the server SV2 individually resources, for example processor time and memory, be allocated.
- the network element SW1 sends a message M1 with a destination address DA1 and one Source address SA1 and event information E1, for example one Limit violation, at processing agent VO1.
- TRV program function
- a DIS distribution function that can be integrated into the TRV connection function can, determined using an identifier in the message M1, in the present case using the source address SA1 that for processing the message M1 the subagent S1 responsible is.
- a Assignment table may be provided for the processing agent VO1.
- the processing agent VO1 the message M1 to the subagent S1, which contains the event information contained therein E1 enters MIRS in its event log.
- the Processing agent VO1 also other, not shown messages with event information the network element SW1 received and for the actual event processing, in the present case for entry in the MIRS event report, to the sub-agents Forward S1.
- the functions of the processing agent VO1 that is, the distribution function DIS Connection function TRV, the start function INI and the monitoring function CM can be implemented individually or in any grouping as separate processes his.
- the processing agent VO2 that of the network element, works in a similar manner SW2 sent messages M21, M22 forwards to sub-agents S21, S22.
- messages M21, M22 there are identical source addresses SA2 and identical destination addresses DA2 entered.
- those in the Messages M21, M22 contain event information E21, E22 where it is for example, an alarm message or a cyclically reported measured value is.
- the distribution function DIS of the processing agent VO2 determines here based on the source address SA2 that the sub-agents S21, S22 for the messages M21, M22 are responsible. It also determines based on the event information E21, E22 that the message M21 to the sub-agent S21 and the message M22 to be forwarded to sub-agent S22.
- the Distribution function DIS reads the source address SA3 contained therein and based on this determines that subagent S31 is responsible for processing message M31 and, for example, event information contained therein E311 into a Log file.
- the event information E1-E311 mentioned can be from the management objects MO1, MO2 are queried. These send corresponding inquiries via Connections VR1 or VR2 to the request manager RM, who the respective Processing agent requirements via VD1 or VD2 connections VO1 or VO2 forwards, depending on which of the processing agents VO1, VO2 is suitable for the respective requirement. For example, the request manager sends RM a request for event information of the network element SW2 to the processing agent VO2. This then decides whether the Subagent S21 and / or subagent S22 suitable for processing the request is.
- the respective sub-agent S21, S22 then sends the respective event information, for example the event information E21, E22, via its connection function TRS to the processing agent VO2 for forwarding to the management objects MO1 or MO2. These then generate, for example, from the answer a screen display that is connected to the VM1 or VM2 connections User interface UI is passed on.
- processing agent VO1 there is also a shipping filter agent EFD provided, the response messages from the processing agent VO1 and the Sub-agents S1 are generated, filters, that is, checked whether the in of the respective response message contained information for the higher-level management object MO1, MO2 is relevant at all. Irrelevant information will be filtered out by the dispatch filter agent EFD.
- CMIP protocol Common Management-Information-Protocol
- OSI Open Systems Interconnection
- the network element SW4 is now put into operation.
- This is assigned to the processing agent VO1, that is, the processing agent VO1 is now intended to send the event information sent by the network element SW4 process and, if necessary, to the management objects MO1, Report M02.
- a control process not shown, for example the initial one Initialization process mentioned, transmitted to the processing agent VO1 Data relating to the network element SW4, for example its address, the Formats of event information sent by it and / or other that Network element SW4 characterizing data.
- the processing agent VO1 sub-agent S1 with the processing of event information sent to the network element SW4.
- the processing agent starts VO1 a sub-agent SW4 specifically responsible for the network element SW4.
- the subagent becomes S4 executed by server SV3, with sufficient resources for this available.
- a connection VR3 is established, which is an interprocess interface, e.g. usable via a so-called Remote Procedure Call (RPC) is, or another interface on which, for example, with the TCP / IP protocol communicated, can act.
- RPC Remote Procedure Call
- the processing agent VO1 is therefore the sub-agent S4 starts because the sub-agent S1 has the format and / or the structure of the Network element SW4 event information sent is not supported.
- the network element In the exemplary embodiment, SW4 sends a message, for example M4, with a destination address DA1 and a source address SA4 as well as in the difference to the message M1 sent by the network element SW1, not just event information E1, but two event information per message, in the example event information E41, E42.
- VO1 first starts sub-agent S4 for processing the event information of the network element SW4 and ends the sub-agent S1 when the network element SW1 is taken out of operation. It is therefore not absolutely necessary for a processing agent to always have two or operates more sub-agents. Rather, a processing agent can only do so at a time operate a sub-agent and if necessary by a more suitable one Replace subagents, which is illustrated by the example of subagents S31, S32 shall be:
- the processing agent operates the sub-agent S31, which optimally matches the Operating software K31 of the network element SW3 is adapted. Now with that Network element SW3 a new operating software K32 put into operation. Consequently The network element SW3 no longer sends messages of the type of the message M31, but messages of the type of message M32.
- the messages M31 and M32 are identical.
- the difference for message M31, message M32 contains a comparison to the event information E311 event information modified in the data structure and / or in the information content E312, for example, additionally one using the operating software K32 contains determinable measured value.
- the subagent can S32, but not the subagent S31, process the event information E312.
- Reloading the operating software K32 is the processing agent VO2, for example of the central initialization and / or control process, not shown of the network management system NMS.
- the sub-agent S32 With whom he communicates via the connection V32 and which is suitable for processing messages of the type of message M32.
- Sub-agents S31, S32 can then e.g. operated in parallel, the Sub-agent S31 messages of the type of message M31, the sub-agent S32 messages of the type of message M32 can process. It is also possible that the Subagent S32 takes the place of subagent S31, and subagent S31 accordingly is terminated.
- the processing agent VO2 a data comparison between the Subagents S31, S32 and / or initializes subagents S32 with start data. It is also possible that the sub-agent S32 and / or the processing agent VO2, for example, trigger a data query with the network element SW3, in order to find out its current event status.
- the sub-agents S1, S4; S21, S22, S31, S32 work under the control, so to speak of processing agents VO1, VO2.
- this control can be based on this limit that processing agents VO1, VO2 sub-agents S1, S4; Start S21, S22, S31, S32 and schedule if necessary.
- the processing agents VO1, VO2 can be a command to terminate a sub-agent S1, S4; S21, S22, S31, S32 to the operating system of the server SV2 and / or the respective sub-agents S1, S4; S21, S22, S31, S32 as a control command to transfer.
- a request made by a processing agent VO1, VO2 a sub-agent S1, S4; S21, S22, S31, S32 sends for example a request to sub-agent S1 for sending the content of the event mirror MIRS, can be such a control command.
- Another control command can be a verification request, which is a monitoring function CM of processing agent VO1 sends to sub-agent S1 and which is answered by its MC reporting function. With such a review request the correct function of subagent S1 can be monitored.
- the verification request is sent cyclically, for example, and must be sent by the Sub-agents S1 are answered correctly. If not, then one The processing agent can malfunction in the respective subagent S1 VO1 start a new sub-agent to replace the faulty one Subagent S1 occurs and / or log an error message and / or a Send error message to management objects MO1, MO2.
- the processing agent VO2 corresponds in Essentially the processing agent VO2, i.e. it starts and ends the subagents S21, S22, S31, S32 in the manner described above.
- Processing agent VO2 is the communication between the subagents S21, S22, S31, S32 on the one hand and the network elements SW2, SW3 and the request manager RM, on the other hand, not through processing agent VO22, but controlled by the communication agent KS.
- the network elements SW2, SW3 send the event information M21, M22; M31, M32 therefore not to the Processing agent VO22, but at the communication agent KS, which the event information M21, M22; M31, M32 then to the relevant sub-agent S21, S22; S31, S32 forwards.
- the processing agent VO22 shares the communication agent KS the respective configuration and / or address of the Sub-agents S21, S22; S31, S32 with, for example, he informs him that the sub-agent S31 instead of sub-agent S32 for sent by network element SW3 Event information is responsible.
- the communication agent KS can be a separate one executed by the server SV2 Process or a sub-process of the processing agent VO22, this thus logically assigned.
- the management objects MO1, MO2 could be based on the concept according to the invention be set up and operate one or more sub-agents, each optimal to the event information to be processed, even in the event of changes of the communication network NW to be managed are adapted.
- processing agent VO2 Send the sub-agent S31 control data with which it can be sent to the new operating software K32 is adapted, for example control data, in which the data structure the message M32 is specified.
- the subagent S32 at least its program code, could also run at the time of Network management system NMS can be loaded into the server SV2. This in any case, makes it clear that the software maintenance of the network management system and / or a communication network managed by this the invention is significantly simplified.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Debugging And Monitoring (AREA)
- Hardware Redundancy (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- Figur 1
- ein erfindungsgemäßes Netzwerk-Management-System NMS eines Kommunikationsnetzes NW mit erfindungsgemäßen Verarbeitungsagenten VO1, VO2 sowie erfindungsgemäßen Unteragenten S1, S4; S21, S22, S31, S32,
- Figur 2
- eine schematische Detailansicht des Verarbeitungsagenten VO1,
- Figur 3
- eine schematische Detailansicht des Unteragenten S1, die
- Figuren 4-6
- von Netzelementen SW1 - SW4 des Kommunikationsnetzes NW gesendete Ereignisinformationen, und
- Figur 7
- eine Abwandlung der Anordnung aus Figur 1 mit einem zusätzlichen, mit einem anstelle des Verarbeitungsagenten VO2 vorgesehen Verarbeitungsagenten V22 kooperierenden Kommunikationsagenten KS.
Claims (12)
- Verfahren zur Verarbeitung von Ereignisinformationen (E1-E42), die von Netzelementen (SW1-SW4) eines Kommunikationsnetzes (NW) an ein dieses verwaltendes Netzwerk-Management-System (NMS) gemeldet werden, durch einen Ereignis-Verarbeitungsagenten (VO1, VO2) des Netzwerk-Management-Systems (NMS), dadurch gekennzeichnet,dass der Verarbeitungsagent (VO1, VO2) anhand von zumindest einem Kriterium einen ersten und mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) zur Verarbeitung von ersten bzw. zweiten Ereignisinformationen (E1-E42) startet, unddass der Verarbeitungsagent (VO1, VO2) oder ein Kommunikationsagent (KS) die ersten bzw. zweiten Ereignisinformationen (E1-E42) empfängt und an den ersten bzw. mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) zur Verarbeitung weiterleitet.
- Verfahren nach Anspruch 1, dadurch gekennzeichnet, dass der Verarbeitungsagent (VO1, VO2) als das zumindest eine Kriterium eine unterschiedliche Qualität der ersten und der zweiten Ereignisinformationen (E1-E42) und/oder eine Belastungsgrenze des ersten und/oder des mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) und/oder die jeweilige Quelle (SW1-SW4) der ersten und der zweiten Ereignisinformationen (E1-E42) auswertet.
- Verfahren nach Anspruch 1, dadurch gekennzeichnet, dass der Verarbeitungsagent eine Veränderung der Konfiguration des durch das Netzwerk-Management-System (NMS) verwalteten Kommunikationsnetzes (NW) und/oder der Konfiguration von Netzelementen (SW1-SW4) des Kommunikationsnetzes (NW) als das zumindest eine Kriterium ermittelt.
- Verfahren nach Anspruch 1, dadurch gekennzeichnet, dass der Verarbeitungsagent (VO1, VO2) bei einer Veränderung des mindestens einen Kriteriums nach dem Starten des ersten und mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) von dem Kriterium abhängige Steuerdaten an den ersten und/oder den mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) sendet und/oder den ersten und/oder den mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) terminiert und/oder mindestens einen dritten Unteragenten (S1, S4; S21, S22, S31, S32) startet.
- Verfahren nach Anspruch 1, dadurch gekennzeichnet, dass der Verarbeitungsagent (VO1, VO2) die Funktionsfähigkeit der ersten und/oder des mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) überwacht und bei einer Funktionsstörung eine Fehlerbehandlung initialisiert.
- Verfahren nach Anspruch 1, dadurch gekennzeichnet, dass die ersten und/oder die zweiten Ereignisinformationen (E1-E42) von Netzelementen (SW1-SW4) gesendete Alarmmeldungen enthalten.
- Ereignis-Verarbeitungsagent (VO1, VO2) eines Netzwerk-Management-Systems (NMS) zur Verarbeitung von Ereignisinformationen (E1-E42), die von Netzelementen (SW1-SW4) eines Kommunikationsnetzes (NW) an ein dieses verwaltendes Netzwerk-Management-System (NMS) gemeldet werden, dadurch gekennzeichnet,dass er Startmittel (INI) aufweist, die derart ausgestaltet sind, dass er anhand von zumindest einem Kriterium einen ersten und mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) zur Verarbeitung von ersten bzw. zweiten Ereignisinformationen (E1-E42) starten kann.
- Ereignis-Verarbeitungsagent (VO1, VO2) nach Anspruch 7, dadurch gekennzeichnet, dass er Sende- und Empfangsmittel (TRV) aufweist, die derart ausgestaltet sind, dass er die ersten bzw. zweiten Ereignisinformationen (E1-E42) empfangen und an den ersten bzw. mindestens einen zweiten Unteragenten (S1, S4; S21, S22, S31, S32) zur Verarbeitung weiterleiten kann.
- Unteragent (S1, S4; S21, S22, S31, S32) zur Verarbeitung von Ereignisinformationen (E1-E42), die von Netzelementen (SW1-SW4) eines Kommunikationsnetzes (NW) an ein dieses verwaltendes Netzwerk-Management-System (NMS) gemeldet werden, dadurch gekennzeichnet,dass der Unteragent (S1, S4; S21, S22, S31, S32) Empfangsmittel (TRS) zur Empfangen von Steuerbefehlen, die von einem Ereignis-Verarbeitungsagenten (VO1, VO2) des Netzwerk-Management-Systems (NMS) gesendet werden, sowie von ersten und/oder zweiten Ereignisinformationen (E1-E42), die von dem Ereignis-Verarbeitungsagenten (VO1, VO2) oder einem Kommunikationsagenten (KS) des Netzwerk-Management-Systems (NMS) gesendet werden, aufweist, unddass der Unteragent (S1, S4; S21, S22, S31, S32) Verarbeitungsmittel (MIRS, MC) zur Verarbeitung der Steuerbefehle sowie der ersten bzw. zweiten Ereignisinformationen (E1-E42) aufweist.
- Ereignis-Verarbeitungsagent (VO1, VO2) nach Anspruch 7 oder Unteragent (S1, S4; S21, S22, S31, S32) nach Anspruch 9, dadurch gekennzeichnet, dass sie Programmcode enthalten, der von einem Steuermittel eines Servers (SV2, SV3) des Netzwerk-Management-Systems (NMS) ausgeführt werden kann.
- Speichermittel, insbesondere Diskette oder CD-ROM, Digital Versatile Disc, Festplattenlaufwerk oder dergleichen, mit einem darauf gespeicherten Ereignis-Verarbeitungsagenten (VO1, VO2) nach Anspruch 10 und/oder einem darauf gespeicherten Unteragenten (S1, S4; S21, S22, S31, S32) nach Anspruch 10.
- Server (SV2) eines Netzwerk-Management-Systems (NMS) mit einem mit einem Ereignis-Verarbeitungsagenten (VO1, VO2) nach Anspruch 10 und/oder einem Unteragenten (S1, S4; S21, S22, S31, S32) nach Anspruch 10 sowie mit einem Steuermittel zur Ausführung des Ereignis-Verarbeitungsagenten (VO1, V02) bzw. des Unteragenten (S1, S4; S21, S22, S31, S32).
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP01440143A EP1261168B1 (de) | 2001-05-22 | 2001-05-22 | Verfahren und Agenten zur Verarbeitung von Ereignismeldungen |
AT01440143T ATE510377T1 (de) | 2001-05-22 | 2001-05-22 | Verfahren und agenten zur verarbeitung von ereignismeldungen |
US10/140,202 US20020178251A1 (en) | 2001-05-22 | 2002-05-08 | Method and agents for processing event signals |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP01440143A EP1261168B1 (de) | 2001-05-22 | 2001-05-22 | Verfahren und Agenten zur Verarbeitung von Ereignismeldungen |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1261168A1 true EP1261168A1 (de) | 2002-11-27 |
EP1261168B1 EP1261168B1 (de) | 2011-05-18 |
Family
ID=8183222
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP01440143A Expired - Lifetime EP1261168B1 (de) | 2001-05-22 | 2001-05-22 | Verfahren und Agenten zur Verarbeitung von Ereignismeldungen |
Country Status (3)
Country | Link |
---|---|
US (1) | US20020178251A1 (de) |
EP (1) | EP1261168B1 (de) |
AT (1) | ATE510377T1 (de) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6925475B2 (en) * | 2001-10-12 | 2005-08-02 | Commissariat A L'energie Atomique | Process and apparatus for management of multimedia databases |
DE602004001356T2 (de) * | 2003-03-17 | 2007-06-21 | Tyco Telecommunications (Us) Inc. | System und Verfahren zur Fehlerdiagnose mittels verteilter Alarmkorrelation |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999049474A1 (en) * | 1998-03-26 | 1999-09-30 | Avesta Technologies, Inc. | Dynamic modeling of complex networks and prediction of impacts of faults therein |
US5978845A (en) * | 1997-03-25 | 1999-11-02 | Sun Microsystems, Inc. | Network management relay mechanism |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5608720A (en) * | 1993-03-09 | 1997-03-04 | Hubbell Incorporated | Control system and operations system interface for a network element in an access system |
US6421719B1 (en) * | 1995-05-25 | 2002-07-16 | Aprisma Management Technologies, Inc. | Method and apparatus for reactive and deliberative configuration management |
US6477563B1 (en) * | 1998-04-13 | 2002-11-05 | Kabushiki Kaisha Toshiba | Agent system and information processing method for same |
US6519635B1 (en) * | 1998-04-30 | 2003-02-11 | Cisco Technology, Inc. | SNMP master agent that translates messages to a sub-agent proprietary format using a translation table by the sub-agent |
US6253243B1 (en) * | 1998-12-04 | 2001-06-26 | Sun Microsystems, Inc. | Automated trap control for a distributed network management system |
-
2001
- 2001-05-22 EP EP01440143A patent/EP1261168B1/de not_active Expired - Lifetime
- 2001-05-22 AT AT01440143T patent/ATE510377T1/de active
-
2002
- 2002-05-08 US US10/140,202 patent/US20020178251A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5978845A (en) * | 1997-03-25 | 1999-11-02 | Sun Microsystems, Inc. | Network management relay mechanism |
WO1999049474A1 (en) * | 1998-03-26 | 1999-09-30 | Avesta Technologies, Inc. | Dynamic modeling of complex networks and prediction of impacts of faults therein |
Non-Patent Citations (2)
Title |
---|
BIRON B ET AL: "IDEAL: A MULTI-AGENT ARCHITECTURE FOR THE MANAGEMENT OF COMPLEX NETWORKS", PROCEEDINGS OF THE INTERNATIONAL CONFERENCE ON COMMUNICATIONS (ICC). GENEVA, MAY 23 - 26, 1993, NEW YORK, IEEE, US, vol. 3, 23 May 1993 (1993-05-23), pages 1875 - 1879, XP000448445, ISBN: 0-7803-0950-2 * |
GARIJO M ET AL: "A MULTIAGENT SYSTEM FOR COOPERATIVE NETWORK-FAULT MANAGEMENT", PROCEEDINGS OF THE INTERNATIONAL CONFERENCE ON THE PRACTICAL APPLICATION OF INTELLIGENT AGENTS AND MULTI-AGENT TECHNOLOGY, XX, XX, 22 April 1996 (1996-04-22), pages 279 - 294, XP002068055 * |
Also Published As
Publication number | Publication date |
---|---|
US20020178251A1 (en) | 2002-11-28 |
ATE510377T1 (de) | 2011-06-15 |
EP1261168B1 (de) | 2011-05-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1034639B1 (de) | Verfahren und kommunikationssystem zur behandlung von alarmen durch ein mehrere managementebenen aufweisendes managementnetz | |
EP0632617B1 (de) | Verfahren und Einrichtung zur Unterstützung des Netzwerkmanagements | |
DE69634928T2 (de) | Netzwerkverwaltungssystem mit verbesserter Knotenerkennung und -überwachung | |
DE60031274T2 (de) | Mehrfachanschlussverfahren und -gerät für vituelle ports | |
EP1123622B1 (de) | Verfahren zur steuerung von netzelementen | |
DE10251911B4 (de) | Verfahren für das Konfigurationsmanagement und Netzwerk | |
EP1089529B1 (de) | System zur Steuerung und Überwachung von an Nebenstellenanlagen angeschlossenen ersten oder von an Weitverkehrsnetze angekoppelten zweiten Telekommunikationsendgeräten | |
EP1198143A2 (de) | Netzwerk-Management System | |
WO2003094046A2 (de) | Verzeichnisdienst in einem automatisierungssystem | |
EP1611730B1 (de) | Verfahren und anordnung zur konfiguration einer einrichtung in einem datennetz | |
EP1261168B1 (de) | Verfahren und Agenten zur Verarbeitung von Ereignismeldungen | |
WO2002023828A1 (de) | Verfahren zum aufbau von verbindungen mit vorgegebener dienstgüte für ein paketorientiertes kommunikationsnetz mit einem resourcenmanager | |
EP1195946A2 (de) | Verfahren zur Erbringung von Diensten in einem Netzwerk-Management-System mit einer offenen Systemarchitektur sowie Dienst-Objekt, Anforderungs-Objekt und Anforderungs-Manager hierzu | |
WO2002103959A2 (de) | Verfahren und system zum netzkonfigurationsmanagement und netzbestandsmanagement | |
DE60218631T2 (de) | Status - basierende Verfahrensverwaltungsmethode für ein Kommunikationstransportnetz | |
EP1145538B1 (de) | Verfahren und kommunikationssystem zur behandlung von zustandsinformationen durch ein mehrere managementebenen aufweisendes managementnetz | |
DE10132272C1 (de) | Verfahren und Anordnung zur Konfiguration eines Kommunikationsverbundes | |
EP1584176B1 (de) | Verfahren und anordnung zur steuerung und/oder überwachung eines an ein kommunikations-system angeschlossenen endgerätes | |
DE60107930T2 (de) | Kommunikation zwischen einer Applikation und einem Netzelement | |
EP1215869A2 (de) | Verfahren und Anordnung zum Betrieb einer aus mehreren Teilnehmern bestehenden Teamkonfiguration | |
EP1537719B1 (de) | Aktualisiering von auf einem rechner eines datenkommunikationssystems gespeicherter software | |
DE60104672T2 (de) | System zur überwachung von terminals | |
EP1460798A1 (de) | Verfahren und Kommunikationssystem zum Abbrechen von Management-Operationen in einem Managementnetz | |
EP3926925A1 (de) | Industrielles automatisierungssystem mit einem echtzeitfähigen kommunikationsnetzwerk | |
WO2003061200A1 (de) | Anordnung zur zustandsüberwachung von komponenten in einem paketvermittelten kommunikationsnetz |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
AX | Request for extension of the european patent |
Free format text: AL;LT;LV;MK;RO;SI |
|
17P | Request for examination filed |
Effective date: 20030520 |
|
AKX | Designation fees paid |
Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: ALCATEL LUCENT |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 50115887 Country of ref document: DE Effective date: 20110630 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20110518 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110919 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 |
|
BERE | Be: lapsed |
Owner name: ALCATEL LUCENT Effective date: 20110531 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110819 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110829 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FD4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110531 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110531 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110531 Ref country code: IE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 |
|
RAP2 | Party data changed (patent owner data changed or rights of a patent transferred) |
Owner name: ALCATEL LUCENT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110531 |
|
26N | No opposition filed |
Effective date: 20120221 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 50115887 Country of ref document: DE Effective date: 20120221 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MM01 Ref document number: 510377 Country of ref document: AT Kind code of ref document: T Effective date: 20110522 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110522 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20110522 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20110518 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: GC Effective date: 20131018 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: RG Effective date: 20141016 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20150521 Year of fee payment: 15 Ref country code: DE Payment date: 20150521 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20150521 Year of fee payment: 15 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 50115887 Country of ref document: DE |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20160522 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20170131 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20161201 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160531 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160522 |