US20100332918A1 - Alarm correlation system - Google Patents
Alarm correlation system Download PDFInfo
- Publication number
- US20100332918A1 US20100332918A1 US12/495,345 US49534509A US2010332918A1 US 20100332918 A1 US20100332918 A1 US 20100332918A1 US 49534509 A US49534509 A US 49534509A US 2010332918 A1 US2010332918 A1 US 2010332918A1
- Authority
- US
- United States
- Prior art keywords
- alarms
- list
- alarm
- objects
- correlated
- 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
- 230000002596 correlated effect Effects 0.000 claims abstract description 52
- 238000000034 method Methods 0.000 claims abstract description 32
- 238000004519 manufacturing process Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 2
- 230000001629 suppression Effects 0.000 abstract description 6
- 230000006870 function Effects 0.000 description 5
- 230000001419 dependent effect Effects 0.000 description 4
- 238000013500 data storage Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000015654 memory Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
- 208000024891 symptom Diseases 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
Definitions
- the invention relates to generally to alarm correlation in communication networks and is particularly concerned with suppression of correlated alarms so as to simplify alarm cause analysis.
- Functionality of equipment is provided by both hardware circuitry and software functions. Failures can occur in either of these elements. As well, failures of operation can occur due to faults within the equipment or due to circumstances exterior to the equipment. For example, a component on a circuit board may fail, or an optical fiber may be severed in the field.
- alarm message Upon detection of a failure of operation or fault, telecommunications equipment normally produces a short message, known as an alarm message, which indicates that it is experiencing some condition or abnormality. Typically, the alarm message will contain information about the device issuing the alarm, the time of the message, and some description of the abnormal operation. Alarm messages may be considered symptoms of faults and a single fault may result in a large number of alarms.
- a method for managing alarms arising on a plurality of objects in telecommunications equipment comprising the steps of: establishing a list of networked alarm relations among the plurality of objects, wherein the list specifies correlated alarms and correlating alarms associations between the objects; establishing a list of correlating alarms; establishing a list of correlated alarms; and and upon a new alarm being raised on an object of the plurality of objects; traversing the list of networked alarm relations in conjunction with the list of correlating alarms and the list of correlated alarms; and assigning the new alarm to one of either the list of correlating alarms or the list of correlated alarms.
- an object of the plurality of objects may be either a hardware device or a software function.
- the traversing step includes traversing at least one of the set of parent objects, affecting objects, and children objects.
- the list of networked alarm relations among said plurality of objects further includes a priority attribute.
- the priority attribute may be used in the assigning step in the event that the new alarm can be correlated by two different alarms
- an article of manufacture for use in programming a telecommunications equipment to manage alarms arising on a plurality of objects in the telecommunications equipment, the article of manufacture comprising computer useable media accessible to the telecommunications equipment, wherein the computer useable media includes at least one computer program that is capable of causing the telecommunications equipment to perform the steps of: establishing a list of networked alarm relations among said plurality of objects, wherein said list specifies correlated alarms and correlating alarms associations between said objects; establishing a list of correlating alarms; establishing a list of correlated alarms; and and upon a new alarm being raised on an object of said plurality of objects; traversing said list of networked alarm relations in conjunction with said list of correlating alarms and said list of correlated alarms; and assigning said new alarm to one of either said list of correlating alarms or said list of correlated alarms.
- FIG. 1 illustrates a set of dependent objects
- FIG. 2 illustrates a hierarchical depiction of a correlated alarms list in accordance with an embodiment of the present invention
- FIG. 3 illustrates a flowchart of a method for correlating alarms in accordance with an embodiment of the present invention
- FIG. 4 illustrates a flowchart of a method for traversing parent objects in accordance with an embodiment of the present invention.
- an object may be defined as a hardware element or a software function.
- Alarms are raised on objects due to a failure of operation of the object, or due to a fault, for example a performance which is out of the required range of operation for that object.
- Given objects may have other objects which are dependent in operation on the given objects.
- FIG. 1 there may be seen a set of dependent objects, some of which are hardware objects and others of which are software functions.
- the hardware objects include node 102 , shelf 104 , slot 106 , card 108 , and port 110 .
- the software objects include Service Access Point (SAP) 112 , site 114 , and service 116 . Due to the functional relation of the objects, faults on one of the objects will necessarily raise alarms on the dependent objects. For example a failure of node 102 will raise a node alarm, but will also raise a card 108 alarm, and potentially a slot 106 alarm, a shelf 104 alarm, and a port 110 alarm. Further, a failure of port 110 may raise a SAP 112 alarm.
- SAP 112 alarm Service Access Point
- a correlated alarm is defined as an alarm that will clear when another alarm, the correlating alarm, is cleared.
- a port 110 fails due to a link being down, and there are 1000 SAPs on that port, the 1000 SAPs will each raise an alarm.
- the 1000 SAP alarms are correlated alarms, and the port 110 alarm is the correlating alarm. All these alarms appear in the operator's alarm display window, and make it difficult to notice that the primary alarm is the port.
- Alarm suppression hides the correlated alarms and shows only the correlating alarms. According to an embodiment of the invention, provisions are made to allow the operator to drill into the correlating alarm to see all the correlated alarms.
- the correlation manager is the function which performs the alarm correlation and manages display suppression.
- the correlation manager is typically rendered in software, but in certain embodiments may be implemented in hardware or via Application Specific Integrated Circuits (ASICs).
- ASICs Application Specific Integrated Circuits
- alarms themselves are objects.
- alarm objects possess a correlating alarm field which indicates which alarm the current alarm is correlated under.
- the correlation manager maintains the following structures:
- the correlation manager performs a recursive traversal of all the alarms correlated under the specified alarm.
- FIG. 2 there may be seen a graphically depicted example of a correlation list illustrating the correlation dependencies of the alarms A 1 , A 2 , A 3 , A 4 , A 5 , and A 6 .
- correlation rules describe how alarms will be correlated. To do so, correlation rules have the following structure:
- FIG. 3 there may be seen a flowchart of a method for correlating alarms in accordance with an embodiment of the present invention.
- the method commences when a new alarm 300 is raised.
- the next step 302 is to traverse the Parents/Affecting Objects for alarms.
- a test is made as to whether the Parents/Affecting Objects contain a correlating alarm. If there is no correlating alarm, then control passes to step 306 and the alarm is loaded normally. If there is a correlating alarm, then control passes to step 308 and the alarm is determined to be a correlated alarm and is thereby suppressed.
- control subsequently passes to step 310 where there is a test for a Correlation Rule for this alarm. If the answer is negative, then the alarm correlation process passes to 312 and Ends.
- control passes to step 318 and the alarm is determined to be a correlated alarm and is thereby suppressed. This concludes the alarm correlation process and control subsequently passes to 312 and Ends.
- alarms are correlated as they are loaded and created. Parents are first traversed to identify if they contain a correlating alarm under which the new alarm could be correlated. If such a correlating alarm is found, the alarm will be suppressed. If no such alarm is found, the affecting objects are traversed to identify correlating alarms, and suppress the alarm if found.
- the correlation rules will be scanned for one matching the alarm name, type, etc. If one is found the current alarm is handled as a correlating alarm. Its children and dependants are scanned to find alarms that can be correlated under the current alarm.
- Traversing parent objects is the most straightforward traversal as each object has at most a single parent. The only conflict that arises is when a parent has several correlating alarms. Those conflicts are resolved by correlating under the alarm with the highest priority.
- FIG. 4 there may be seen a flowchart of a method for traversing parent objects in accordance with an embodiment of the present invention.
- the method commences when a new alarm 400 is raised.
- control is routed back to step 302 . This eventuality may occur when the new alarm being processed does not have a NULL parent, but the correlating alarm has not yet been processed.
- Traversing affecting objects is more complex as is equates to traversing a graph.
- the method used is a depth-first search which stops searching a tree branch when one of the following conditions is met:
- the one with the highest priority is selected.
- affecting object traversal In order to find alarms that should be correlated under the new alarm; an affecting object traversal will be required.
- the affecting object list is already compiled to maintain each object's status. Once again, this traversal is a depth—first one with the following conditions determining the tree leaves:
- the correlated alarms should eventually be cleared since the root cause should be resolved.
- alarms which are not cleared are un-correlated. These alarms are then processed as if they were being raised. As a consequence they may be correlated under a different alarm or simply shown as a normal alarm.
- the net effect is that an equipment operator is presented with an error management display system capable of suppressing correlated alarms to simplify the presentation of alarm data, allowing the operator to see the alarms of importance, and facilitating the expeditious resolution of these alarms.
- program storage devices e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods.
- the program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.
- the embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.
Abstract
Description
- The invention relates to generally to alarm correlation in communication networks and is particularly concerned with suppression of correlated alarms so as to simplify alarm cause analysis.
- The increasing processing power of telecommunications equipment has resulted in an increased volume of data traffic concentrated per unit of equipment. As well, increased equipment density due to enhanced ASICs is resulting in more lines per card, more cards per shelf, and even more shelves per equipment bay.
- Functionality of equipment is provided by both hardware circuitry and software functions. Failures can occur in either of these elements. As well, failures of operation can occur due to faults within the equipment or due to circumstances exterior to the equipment. For example, a component on a circuit board may fail, or an optical fiber may be severed in the field.
- Upon detection of a failure of operation or fault, telecommunications equipment normally produces a short message, known as an alarm message, which indicates that it is experiencing some condition or abnormality. Typically, the alarm message will contain information about the device issuing the alarm, the time of the message, and some description of the abnormal operation. Alarm messages may be considered symptoms of faults and a single fault may result in a large number of alarms.
- Operational problems in networks can be difficult and time consuming to debug because a problem in one place affects many other network objects, and many alarms are raised at the same time
- In the presence of alarms, it is necessary to trace the relationship between the alarms to understand what alarm may be signaling the root cause and which alarms are a consequence of failures entailed by the root cause.
- Alarm association allows the operator to quickly:
-
- Identify that a problem has occurred
- Identify which network objects and services have been affected
- Troubleshoot to find the objects closest to the cause
- Therefore, it would be desirable to have an error management display system capable of suppressing correlated alarms to simplify the presentation of alarm data for the operator.
- It is an object of the invention to provide a method of alarm correlation.
- According to an aspect of the invention there is provided a method for managing alarms arising on a plurality of objects in telecommunications equipment, the method comprising the steps of: establishing a list of networked alarm relations among the plurality of objects, wherein the list specifies correlated alarms and correlating alarms associations between the objects; establishing a list of correlating alarms; establishing a list of correlated alarms; and and upon a new alarm being raised on an object of the plurality of objects; traversing the list of networked alarm relations in conjunction with the list of correlating alarms and the list of correlated alarms; and assigning the new alarm to one of either the list of correlating alarms or the list of correlated alarms.
- In some embodiments of the invention an object of the plurality of objects may be either a hardware device or a software function.
- Advantageously, the traversing step includes traversing at least one of the set of parent objects, affecting objects, and children objects.
- Further, advantageously the list of networked alarm relations among said plurality of objects further includes a priority attribute. The priority attribute may be used in the assigning step in the event that the new alarm can be correlated by two different alarms
- According to another aspect of the invention there is provided an article of manufacture for use in programming a telecommunications equipment to manage alarms arising on a plurality of objects in the telecommunications equipment, the article of manufacture comprising computer useable media accessible to the telecommunications equipment, wherein the computer useable media includes at least one computer program that is capable of causing the telecommunications equipment to perform the steps of: establishing a list of networked alarm relations among said plurality of objects, wherein said list specifies correlated alarms and correlating alarms associations between said objects; establishing a list of correlating alarms; establishing a list of correlated alarms; and and upon a new alarm being raised on an object of said plurality of objects; traversing said list of networked alarm relations in conjunction with said list of correlating alarms and said list of correlated alarms; and assigning said new alarm to one of either said list of correlating alarms or said list of correlated alarms.
- Note: in the following the description and drawings merely illustrate the principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the invention and are included within its spirit and scope. Furthermore, all examples recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventor(s) to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.
- The present invention will be further understood from the following detailed description of embodiments of the invention, with reference to the drawings in which:
-
FIG. 1 illustrates a set of dependent objects; -
FIG. 2 illustrates a hierarchical depiction of a correlated alarms list in accordance with an embodiment of the present invention; -
FIG. 3 illustrates a flowchart of a method for correlating alarms in accordance with an embodiment of the present invention; and -
FIG. 4 illustrates a flowchart of a method for traversing parent objects in accordance with an embodiment of the present invention. - Within the operational environment of telecommunications equipment an object may be defined as a hardware element or a software function. Alarms are raised on objects due to a failure of operation of the object, or due to a fault, for example a performance which is out of the required range of operation for that object.
- Given objects may have other objects which are dependent in operation on the given objects. Referring to
FIG. 1 there may be seen a set of dependent objects, some of which are hardware objects and others of which are software functions. The hardware objects includenode 102,shelf 104,slot 106,card 108, andport 110. The software objects include Service Access Point (SAP) 112,site 114, andservice 116. Due to the functional relation of the objects, faults on one of the objects will necessarily raise alarms on the dependent objects. For example a failure ofnode 102 will raise a node alarm, but will also raise acard 108 alarm, and potentially aslot 106 alarm, ashelf 104 alarm, and aport 110 alarm. Further, a failure ofport 110 may raise aSAP 112 alarm. - From the viewpoint of the telecommunications equipment operator, it would be useful to see the alarms of importance. This facilitates and expedites troubleshooting of alarms.
- For the purpose of understanding the operation of an embodiment of the invention, the following definition of a correlated alarm is used. A correlated alarm is defined as an alarm that will clear when another alarm, the correlating alarm, is cleared.
- By way of example, if a
port 110 fails due to a link being down, and there are 1000 SAPs on that port, the 1000 SAPs will each raise an alarm. The 1000 SAP alarms are correlated alarms, and theport 110 alarm is the correlating alarm. All these alarms appear in the operator's alarm display window, and make it difficult to notice that the primary alarm is the port. Alarm suppression hides the correlated alarms and shows only the correlating alarms. According to an embodiment of the invention, provisions are made to allow the operator to drill into the correlating alarm to see all the correlated alarms. - For the purposes of the following description, the correlation manager is the function which performs the alarm correlation and manages display suppression. The correlation manager is typically rendered in software, but in certain embodiments may be implemented in hardware or via Application Specific Integrated Circuits (ASICs).
- Within the telecommunications equipment, alarms themselves are objects. To facilitate alarm suppression, alarm objects possess a correlating alarm field which indicates which alarm the current alarm is correlated under.
- In order to correlate alarms efficiently, the correlation manager maintains the following structures:
-
- List of correlating alarms
- List of correlated alarms for each correlating alarm
- List of correlation rules
- To build the correlated alarm list for each alarm, the correlation manager performs a recursive traversal of all the alarms correlated under the specified alarm. Referring to
FIG. 2 there may be seen a graphically depicted example of a correlation list illustrating the correlation dependencies of the alarms A1, A2, A3, A4, A5, and A6. - Correlation rules describe how alarms will be correlated. To do so, correlation rules have the following structure:
-
- A correlation tag will require a type attribute which will indicate whether this rule is correlating alarms on children (aggregation) or dependant objects (association). It will also include a priority attribute, which will indicate which rule should be used when an alarm can be correlated by two different alarms.
- A filter tag will specify a filter which will be evaluated when the alarm is created to determine whether the alarm is a correlating alarm or not.
- A “Can Suppress” tag will also be added to the alarm. This will indicate whether a specific alarm should be considered for suppression or not. When not specified, the default value will be yes.
- Referring to
FIG. 3 there may be seen a flowchart of a method for correlating alarms in accordance with an embodiment of the present invention. The method commences when anew alarm 300 is raised. - The
next step 302 is to traverse the Parents/Affecting Objects for alarms. At step 304 a test is made as to whether the Parents/Affecting Objects contain a correlating alarm. If there is no correlating alarm, then control passes to step 306 and the alarm is loaded normally. If there is a correlating alarm, then control passes to step 308 and the alarm is determined to be a correlated alarm and is thereby suppressed. - In either
case - If the answer is positive, then there are Children/Depending Objects, and control passes to 314 where they are traversed. A check for whether they contain an alarm occurs at
step 316, and if the answer is negative then the alarm correlation process passes to 312 and Ends. - If the answer is positive then there is a correlating alarm, at which point control passes to step 318 and the alarm is determined to be a correlated alarm and is thereby suppressed. This concludes the alarm correlation process and control subsequently passes to 312 and Ends.
- Summarizing, alarms are correlated as they are loaded and created. Parents are first traversed to identify if they contain a correlating alarm under which the new alarm could be correlated. If such a correlating alarm is found, the alarm will be suppressed. If no such alarm is found, the affecting objects are traversed to identify correlating alarms, and suppress the alarm if found.
- Then, the correlation rules will be scanned for one matching the alarm name, type, etc. If one is found the current alarm is handled as a correlating alarm. Its children and dependants are scanned to find alarms that can be correlated under the current alarm.
- Traversing parent objects is the most straightforward traversal as each object has at most a single parent. The only conflict that arises is when a parent has several correlating alarms. Those conflicts are resolved by correlating under the alarm with the highest priority.
- Referring to
FIG. 4 there may be seen a flowchart of a method for traversing parent objects in accordance with an embodiment of the present invention. The method commences when anew alarm 400 is raised. - Control passes to step 302 wherein it is checked if the parent is NULL i.e. no parent exists. If the check confirms that the parent is NULL, control passes to 304 and the process Ends.
- If the check determines that the parent is not NULL, then control passes to step 306 wherein a check is made for the presence of a correlating alarm. If the check is affirmative, then the alarm is suppressed, control passes to 304 and the process Ends.
- If the check does not determine the presence of a correlating alarm then control is routed back to
step 302. This eventuality may occur when the new alarm being processed does not have a NULL parent, but the correlating alarm has not yet been processed. - Traversing affecting objects is more complex as is equates to traversing a graph. The method used is a depth-first search which stops searching a tree branch when one of the following conditions is met:
-
- The current node is a leaf
- The current node is the starting node (cycle)
- The current node contains a correlating alarm
- If multiple correlating alarms are found, the one with the highest priority is selected.
- In order to find alarms that should be correlated under the new alarm; a children traversal is required. This is facilitated by a naming convention which denotes children objects as having an portion of their names consisting of their parent's names. The search is then done by finding all alarmed objects' names which start with the current object's full name. Once again, this traversal is a depth-first one with the following conditions determining the tree leaves:
-
- The current node has no children
- The current node contains a correlating alarm
- In order to find alarms that should be correlated under the new alarm; an affecting object traversal will be required. The affecting object list is already compiled to maintain each object's status. Once again, this traversal is a depth—first one with the following conditions determining the tree leaves:
-
- The current node has no affected objects
- The current node has been visited
- The current node contains a correlating alarm
- Once correlated, the alarm is suppressed, while uncorrelated alarms will be unaffected. As a consequence suppressed alarms are no longer visible in the operator's Alarm Display window (unless the operator has elected to display correlated alarms).
- When a correlating alarm is remedied, the correlated alarms should eventually be cleared since the root cause should be resolved. According to one embodiment, after a preset delay has expired alarms which are not cleared are un-correlated. These alarms are then processed as if they were being raised. As a consequence they may be correlated under a different alarm or simply shown as a normal alarm.
- Accordingly, what has been disclosed is a method and process for correlating alarms raised on objects by specifying rules associating objects and alarms, and then processing alarms as they are raised so as to suppress correlated alarms.
- The net effect is that an equipment operator is presented with an error management display system capable of suppressing correlated alarms to simplify the presentation of alarm data, allowing the operator to see the alarms of importance, and facilitating the expeditious resolution of these alarms.
- Note, in the preceding discussion a person of skill in the art would readily recognize that steps of various above-described methods can be performed by programmed computers. Herein, some embodiments are also intended to cover program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods. The program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. The embodiments are also intended to cover computers programmed to perform said steps of the above-described methods.
- Numerous modifications, variations and adaptations may be made to the embodiment of the invention described above without departing from the scope of the invention, which is defined in the claims.
Claims (12)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/495,345 US8166352B2 (en) | 2009-06-30 | 2009-06-30 | Alarm correlation system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/495,345 US8166352B2 (en) | 2009-06-30 | 2009-06-30 | Alarm correlation system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20100332918A1 true US20100332918A1 (en) | 2010-12-30 |
US8166352B2 US8166352B2 (en) | 2012-04-24 |
Family
ID=43382112
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/495,345 Active 2030-02-17 US8166352B2 (en) | 2009-06-30 | 2009-06-30 | Alarm correlation system |
Country Status (1)
Country | Link |
---|---|
US (1) | US8166352B2 (en) |
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110252126A1 (en) * | 2010-04-12 | 2011-10-13 | Peter Van Horne | Controlling emission of events from managed systems to external management systems |
US20120144251A1 (en) * | 2010-12-07 | 2012-06-07 | International Business Machines Corporation | Relevant Alert Delivery In A Distributed Processing System With Event Listeners and Alert Listeners |
US20120304013A1 (en) * | 2011-05-27 | 2012-11-29 | International Business Machines Corporation | Administering Event Pools For Relevant Event Analysis In A Distributed Processing System |
WO2013189110A1 (en) * | 2012-06-19 | 2013-12-27 | 国网电力科学研究院 | Power communication fault early warning analysis method and system |
US8621277B2 (en) | 2010-12-06 | 2013-12-31 | International Business Machines Corporation | Dynamic administration of component event reporting in a distributed processing system |
US8639980B2 (en) | 2011-05-26 | 2014-01-28 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8660995B2 (en) | 2011-06-22 | 2014-02-25 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US8676883B2 (en) | 2011-05-27 | 2014-03-18 | International Business Machines Corporation | Event management in a distributed processing system |
US8688769B2 (en) | 2011-10-18 | 2014-04-01 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8689050B2 (en) | 2011-06-22 | 2014-04-01 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8713581B2 (en) | 2011-10-27 | 2014-04-29 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8730816B2 (en) | 2010-12-07 | 2014-05-20 | International Business Machines Corporation | Dynamic administration of event pools for relevant event and alert analysis during event storms |
US8756462B2 (en) | 2011-05-24 | 2014-06-17 | International Business Machines Corporation | Configurable alert delivery for reducing the amount of alerts transmitted in a distributed processing system |
US8769096B2 (en) | 2010-11-02 | 2014-07-01 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system |
US8805999B2 (en) | 2010-12-07 | 2014-08-12 | International Business Machines Corporation | Administering event reporting rules in a distributed processing system |
US8880943B2 (en) | 2011-06-22 | 2014-11-04 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8887175B2 (en) | 2011-10-18 | 2014-11-11 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8898299B2 (en) | 2010-11-02 | 2014-11-25 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US20150006459A1 (en) * | 2013-06-29 | 2015-01-01 | Huawei Technologies Co., Ltd. | Alarm Correlation Analysis Method, Apparatus and System |
US8943366B2 (en) | 2012-08-09 | 2015-01-27 | International Business Machines Corporation | Administering checkpoints for incident analysis |
US8954811B2 (en) | 2012-08-06 | 2015-02-10 | International Business Machines Corporation | Administering incident pools for incident analysis |
US20150058676A1 (en) * | 2013-08-23 | 2015-02-26 | International Business Machines Corporation | Determining Whether To Send An Alert In A Distributed Processing System |
US9086968B2 (en) | 2013-09-11 | 2015-07-21 | International Business Machines Corporation | Checkpointing for delayed alert creation |
US9170860B2 (en) | 2013-07-26 | 2015-10-27 | International Business Machines Corporation | Parallel incident processing |
US9178936B2 (en) | 2011-10-18 | 2015-11-03 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US9246865B2 (en) | 2011-10-18 | 2016-01-26 | International Business Machines Corporation | Prioritized alert delivery in a distributed processing system |
US9286143B2 (en) | 2011-06-22 | 2016-03-15 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US9348687B2 (en) | 2014-01-07 | 2016-05-24 | International Business Machines Corporation | Determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system |
US9361184B2 (en) | 2013-05-09 | 2016-06-07 | International Business Machines Corporation | Selecting during a system shutdown procedure, a restart incident checkpoint of an incident analyzer in a distributed processing system |
US9602337B2 (en) | 2013-09-11 | 2017-03-21 | International Business Machines Corporation | Event and alert analysis in a distributed processing system |
US9658902B2 (en) | 2013-08-22 | 2017-05-23 | Globalfoundries Inc. | Adaptive clock throttling for event processing |
US20170153935A1 (en) * | 2015-12-01 | 2017-06-01 | Oracle International Corporation | Performance engineering platform using probes and searchable tags |
US20200065173A1 (en) * | 2018-08-22 | 2020-02-27 | Ca, Inc. | Controlled monitoring based on root cause analysis recommendations |
US20200099570A1 (en) * | 2018-09-26 | 2020-03-26 | Ca, Inc. | Cross-domain topological alarm suppression |
CN113568991A (en) * | 2021-09-22 | 2021-10-29 | 北京必示科技有限公司 | Alarm processing method and system based on dynamic risk |
US11258659B2 (en) | 2019-07-12 | 2022-02-22 | Nokia Solutions And Networks Oy | Management and control for IP and fixed networking |
WO2023093527A1 (en) * | 2021-11-25 | 2023-06-01 | 中兴通讯股份有限公司 | Alarm association rule generation method and apparatus, and electronic device and storage medium |
US20230239206A1 (en) * | 2022-01-24 | 2023-07-27 | Rakuten Mobile, Inc. | Topology Alarm Correlation |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107276818B (en) * | 2017-07-04 | 2020-03-20 | 上海欣诺通信技术股份有限公司 | Enhanced alarm suppression method applied to optical transmission equipment |
US11734086B2 (en) | 2019-03-29 | 2023-08-22 | Hewlett Packard Enterprise Development Lp | Operation-based event suppression |
JP7344041B2 (en) | 2019-08-08 | 2023-09-13 | 横河電機株式会社 | Alarm management device, alarm management system, and alarm management method |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5309448A (en) * | 1992-01-03 | 1994-05-03 | International Business Machines Corporation | Methods and systems for alarm correlation and fault localization in communication networks |
US6604208B1 (en) * | 2000-04-07 | 2003-08-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Incremental alarm correlation method and apparatus |
US6701459B2 (en) * | 2000-12-27 | 2004-03-02 | Egurkha Pte Ltd | Root-cause approach to problem diagnosis in data networks |
US6707795B1 (en) * | 1999-04-26 | 2004-03-16 | Nortel Networks Limited | Alarm correlation method and system |
US6862698B1 (en) * | 2002-01-22 | 2005-03-01 | Cisco Technology, Inc. | Method of labeling alarms to facilitate correlating alarms in a telecommunications network |
US7107496B1 (en) * | 2000-07-24 | 2006-09-12 | Nortel Networks Limited | Method, apparatus, computer-readable media and user interface for annunciating problems in a system |
US7131037B1 (en) * | 2002-06-05 | 2006-10-31 | Proactivenet, Inc. | Method and system to correlate a specific alarm to one or more events to identify a possible cause of the alarm |
US7257744B2 (en) * | 2003-03-17 | 2007-08-14 | Tyco Telecommunications (Us) Inc. | System and method for fault diagnosis using distributed alarm correlation |
US20100156623A1 (en) * | 2008-12-24 | 2010-06-24 | At&T Intellectual Property I, L.P. | Method and Apparatus for Network Service Assurance |
US20100157812A1 (en) * | 2008-12-23 | 2010-06-24 | Aaron Blocker | Method and apparatus for asynchronous alarm correlation |
-
2009
- 2009-06-30 US US12/495,345 patent/US8166352B2/en active Active
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5309448A (en) * | 1992-01-03 | 1994-05-03 | International Business Machines Corporation | Methods and systems for alarm correlation and fault localization in communication networks |
US6707795B1 (en) * | 1999-04-26 | 2004-03-16 | Nortel Networks Limited | Alarm correlation method and system |
US6604208B1 (en) * | 2000-04-07 | 2003-08-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Incremental alarm correlation method and apparatus |
US7107496B1 (en) * | 2000-07-24 | 2006-09-12 | Nortel Networks Limited | Method, apparatus, computer-readable media and user interface for annunciating problems in a system |
US6701459B2 (en) * | 2000-12-27 | 2004-03-02 | Egurkha Pte Ltd | Root-cause approach to problem diagnosis in data networks |
US6862698B1 (en) * | 2002-01-22 | 2005-03-01 | Cisco Technology, Inc. | Method of labeling alarms to facilitate correlating alarms in a telecommunications network |
US7131037B1 (en) * | 2002-06-05 | 2006-10-31 | Proactivenet, Inc. | Method and system to correlate a specific alarm to one or more events to identify a possible cause of the alarm |
US7257744B2 (en) * | 2003-03-17 | 2007-08-14 | Tyco Telecommunications (Us) Inc. | System and method for fault diagnosis using distributed alarm correlation |
US20100157812A1 (en) * | 2008-12-23 | 2010-06-24 | Aaron Blocker | Method and apparatus for asynchronous alarm correlation |
US20100156623A1 (en) * | 2008-12-24 | 2010-06-24 | At&T Intellectual Property I, L.P. | Method and Apparatus for Network Service Assurance |
Cited By (61)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110252126A1 (en) * | 2010-04-12 | 2011-10-13 | Peter Van Horne | Controlling emission of events from managed systems to external management systems |
US8352592B2 (en) * | 2010-04-12 | 2013-01-08 | Cisco Technology, Inc. | Controlling emission of events from managed systems to external management systems |
US8825852B2 (en) | 2010-11-02 | 2014-09-02 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system |
US8898299B2 (en) | 2010-11-02 | 2014-11-25 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8769096B2 (en) | 2010-11-02 | 2014-07-01 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system |
US8621277B2 (en) | 2010-12-06 | 2013-12-31 | International Business Machines Corporation | Dynamic administration of component event reporting in a distributed processing system |
US8627154B2 (en) | 2010-12-06 | 2014-01-07 | International Business Machines Corporation | Dynamic administration of component event reporting in a distributed processing system |
US20120144251A1 (en) * | 2010-12-07 | 2012-06-07 | International Business Machines Corporation | Relevant Alert Delivery In A Distributed Processing System With Event Listeners and Alert Listeners |
US8868984B2 (en) * | 2010-12-07 | 2014-10-21 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system with event listeners and alert listeners |
US8868986B2 (en) * | 2010-12-07 | 2014-10-21 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system with event listeners and alert listeners |
US8730816B2 (en) | 2010-12-07 | 2014-05-20 | International Business Machines Corporation | Dynamic administration of event pools for relevant event and alert analysis during event storms |
US8805999B2 (en) | 2010-12-07 | 2014-08-12 | International Business Machines Corporation | Administering event reporting rules in a distributed processing system |
US8737231B2 (en) | 2010-12-07 | 2014-05-27 | International Business Machines Corporation | Dynamic administration of event pools for relevant event and alert analysis during event storms |
US8756462B2 (en) | 2011-05-24 | 2014-06-17 | International Business Machines Corporation | Configurable alert delivery for reducing the amount of alerts transmitted in a distributed processing system |
US8645757B2 (en) | 2011-05-26 | 2014-02-04 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8639980B2 (en) | 2011-05-26 | 2014-01-28 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US9201756B2 (en) * | 2011-05-27 | 2015-12-01 | International Business Machines Corporation | Administering event pools for relevant event analysis in a distributed processing system |
US9344381B2 (en) | 2011-05-27 | 2016-05-17 | International Business Machines Corporation | Event management in a distributed processing system |
US20120304013A1 (en) * | 2011-05-27 | 2012-11-29 | International Business Machines Corporation | Administering Event Pools For Relevant Event Analysis In A Distributed Processing System |
US8676883B2 (en) | 2011-05-27 | 2014-03-18 | International Business Machines Corporation | Event management in a distributed processing system |
US20130091386A1 (en) * | 2011-05-27 | 2013-04-11 | International Business Machines Corporation | Administering event pools for relevant event analysis in a distributed processing system |
US9213621B2 (en) * | 2011-05-27 | 2015-12-15 | International Business Machines Corporation | Administering event pools for relevant event analysis in a distributed processing system |
US8660995B2 (en) | 2011-06-22 | 2014-02-25 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US8689050B2 (en) | 2011-06-22 | 2014-04-01 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8880943B2 (en) | 2011-06-22 | 2014-11-04 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8880944B2 (en) | 2011-06-22 | 2014-11-04 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8713366B2 (en) | 2011-06-22 | 2014-04-29 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US9286143B2 (en) | 2011-06-22 | 2016-03-15 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US9419650B2 (en) | 2011-06-22 | 2016-08-16 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US8688769B2 (en) | 2011-10-18 | 2014-04-01 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8893157B2 (en) | 2011-10-18 | 2014-11-18 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US9246865B2 (en) | 2011-10-18 | 2016-01-26 | International Business Machines Corporation | Prioritized alert delivery in a distributed processing system |
US9178936B2 (en) | 2011-10-18 | 2015-11-03 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US9178937B2 (en) | 2011-10-18 | 2015-11-03 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8887175B2 (en) | 2011-10-18 | 2014-11-11 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8713581B2 (en) | 2011-10-27 | 2014-04-29 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
WO2013189110A1 (en) * | 2012-06-19 | 2013-12-27 | 国网电力科学研究院 | Power communication fault early warning analysis method and system |
US8954811B2 (en) | 2012-08-06 | 2015-02-10 | International Business Machines Corporation | Administering incident pools for incident analysis |
US8943366B2 (en) | 2012-08-09 | 2015-01-27 | International Business Machines Corporation | Administering checkpoints for incident analysis |
US9361184B2 (en) | 2013-05-09 | 2016-06-07 | International Business Machines Corporation | Selecting during a system shutdown procedure, a restart incident checkpoint of an incident analyzer in a distributed processing system |
US9256828B2 (en) * | 2013-06-29 | 2016-02-09 | Huawei Technologies Co., Ltd. | Alarm correlation analysis method, apparatus and system |
US20150006459A1 (en) * | 2013-06-29 | 2015-01-01 | Huawei Technologies Co., Ltd. | Alarm Correlation Analysis Method, Apparatus and System |
US9170860B2 (en) | 2013-07-26 | 2015-10-27 | International Business Machines Corporation | Parallel incident processing |
US9658902B2 (en) | 2013-08-22 | 2017-05-23 | Globalfoundries Inc. | Adaptive clock throttling for event processing |
US9256482B2 (en) * | 2013-08-23 | 2016-02-09 | International Business Machines Corporation | Determining whether to send an alert in a distributed processing system |
US20150058676A1 (en) * | 2013-08-23 | 2015-02-26 | International Business Machines Corporation | Determining Whether To Send An Alert In A Distributed Processing System |
US9086968B2 (en) | 2013-09-11 | 2015-07-21 | International Business Machines Corporation | Checkpointing for delayed alert creation |
US10171289B2 (en) | 2013-09-11 | 2019-01-01 | International Business Machines Corporation | Event and alert analysis in a distributed processing system |
US9602337B2 (en) | 2013-09-11 | 2017-03-21 | International Business Machines Corporation | Event and alert analysis in a distributed processing system |
US9348687B2 (en) | 2014-01-07 | 2016-05-24 | International Business Machines Corporation | Determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system |
US9389943B2 (en) | 2014-01-07 | 2016-07-12 | International Business Machines Corporation | Determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system |
US20170153935A1 (en) * | 2015-12-01 | 2017-06-01 | Oracle International Corporation | Performance engineering platform using probes and searchable tags |
US10127128B2 (en) * | 2015-12-01 | 2018-11-13 | Oracle International Corporation | Performance engineering platform using probes and searchable tags |
US10853217B2 (en) | 2015-12-01 | 2020-12-01 | Oracle International Corporation | Performance engineering platform using probes and searchable tags |
US20200065173A1 (en) * | 2018-08-22 | 2020-02-27 | Ca, Inc. | Controlled monitoring based on root cause analysis recommendations |
US10884840B2 (en) * | 2018-08-22 | 2021-01-05 | Ca, Inc. | Controlled monitoring based on root cause analysis recommendations |
US20200099570A1 (en) * | 2018-09-26 | 2020-03-26 | Ca, Inc. | Cross-domain topological alarm suppression |
US11258659B2 (en) | 2019-07-12 | 2022-02-22 | Nokia Solutions And Networks Oy | Management and control for IP and fixed networking |
CN113568991A (en) * | 2021-09-22 | 2021-10-29 | 北京必示科技有限公司 | Alarm processing method and system based on dynamic risk |
WO2023093527A1 (en) * | 2021-11-25 | 2023-06-01 | 中兴通讯股份有限公司 | Alarm association rule generation method and apparatus, and electronic device and storage medium |
US20230239206A1 (en) * | 2022-01-24 | 2023-07-27 | Rakuten Mobile, Inc. | Topology Alarm Correlation |
Also Published As
Publication number | Publication date |
---|---|
US8166352B2 (en) | 2012-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8166352B2 (en) | Alarm correlation system | |
US20230155895A1 (en) | Component detection and management using relationships | |
US7631222B2 (en) | Method and apparatus for correlating events in a network | |
AU2019201687B2 (en) | Network device vulnerability prediction | |
US8583779B2 (en) | Root cause analysis approach with candidate elimination using network virtualization | |
US9612892B2 (en) | Creating a correlation rule defining a relationship between event types | |
US8370462B2 (en) | Service configuration assurance | |
US10652103B2 (en) | System and method for handling events involving computing systems and networks using fabric monitoring system | |
JP4598065B2 (en) | Monitoring simulation apparatus, method and program thereof | |
CN105183619B (en) | A kind of system failure method for early warning and system | |
US8935388B2 (en) | Systems and methods of automated event processing | |
CN113973042B (en) | Method and system for root cause analysis of network problems | |
US20200099570A1 (en) | Cross-domain topological alarm suppression | |
US10089167B2 (en) | Log file reduction according to problem-space network topology | |
US9443196B1 (en) | Method and apparatus for problem analysis using a causal map | |
CN105763371A (en) | Alarm processing method and apparatus | |
CN113821412A (en) | Equipment operation and maintenance management method and device | |
CN114679295B (en) | Firewall security configuration method and device | |
CN115185641A (en) | Cloud native asset discovery method and system | |
CN115134367A (en) | Cloud platform and service processing method | |
US20190207805A1 (en) | Node fault isolation | |
CN110933066A (en) | Monitoring system and method for illegal access of network terminal to local area network | |
CN113542192B (en) | Illegal network equipment access detection method and device, computing equipment and storage medium | |
CN115150253B (en) | Fault root cause determining method and device and electronic equipment | |
CN115567319A (en) | Log collection analysis rule optimization and system performance optimization |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ALCATEL-LUCENT CANADA INC., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HARNOIS, PASCAL;REEL/FRAME:022977/0578 Effective date: 20090712 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCATEL-LUCENT CANADA INC.;REEL/FRAME:027729/0753 Effective date: 20120216 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NOKIA TECHNOLOGIES OY;NOKIA SOLUTIONS AND NETWORKS BV;ALCATEL LUCENT SAS;REEL/FRAME:043877/0001 Effective date: 20170912 Owner name: NOKIA USA INC., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP LLC;REEL/FRAME:043879/0001 Effective date: 20170913 Owner name: CORTLAND CAPITAL MARKET SERVICES, LLC, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP, LLC;REEL/FRAME:043967/0001 Effective date: 20170913 |
|
AS | Assignment |
Owner name: NOKIA US HOLDINGS INC., NEW JERSEY Free format text: ASSIGNMENT AND ASSUMPTION AGREEMENT;ASSIGNOR:NOKIA USA INC.;REEL/FRAME:048370/0682 Effective date: 20181220 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 |
|
AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PROVENANCE ASSET GROUP LLC;REEL/FRAME:059352/0001 Effective date: 20211129 |
|
AS | Assignment |
Owner name: BARINGS FINANCE LLC, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:RPX CORPORATION;REEL/FRAME:063429/0001 Effective date: 20220107 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |