Dynamic Rule Generation for Network Alarm Classification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing rule generation techniques for network failures are limited by fixed event definitions in IF-THEN rules, which cannot be updated, leading to inaccurate alarm classification and prolonged operator effort in determining failure causes.
Innovation Solution
A database and unique determination unit that generate and correct rules based on dynamic event patterns, combined with an event mapping file to normalize and convert alarm information, allowing for accurate classification and updating of failure events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If fixed event definitions are used in IF-THEN rules, then rule structure is simple and stable, but event classification accuracy deteriorates when new failure cases occur
Solution Approach 1:
The patent applies dynamics by enabling the event definition in the IF part of rules to be dynamically updated. The system allows operators to modify event definitions and classifications during operation, transforming the previously static rule structure into a dynamic one that can adapt to new failure cases while maintaining operational stability through controlled update mechanisms.
Solution Approach 2:
The patent implements parameter changes by allowing the event definition parameters (alarm classifications, event types) in the IF part to be modified. When new failure patterns are detected or operators identify inaccuracies, the system updates the event definition parameters to improve classification accuracy without requiring complete rule restructuring.
2Device complexity
If fixed event definitions are used, then system complexity is low, but operator workload increases due to manual rule determination
Solution Approach 1:
The patent applies self-service by enabling the system to automatically update event definitions and rule conditions based on operator input and detected failure patterns. Instead of requiring operators to manually analyze and update every rule, the system autonomously adjusts event classifications and associations, reducing operator workload while maintaining improved accuracy.
Solution Approach 2:
The patent implements feedback mechanisms where operator corrections and new failure case information are fed back into the system to update event definitions. This continuous feedback loop allows the system to learn from operational experience and automatically refine its classification accuracy without proportionally increasing operator time investment.
3Stability of the object's composition
If event definitions cannot be updated, then rule consistency is maintained, but adaptability to various failure cases deteriorates
Solution Approach 1:
The patent resolves this contradiction by making the event definition dynamic while maintaining rule consistency through structured update processes. The system allows controlled modifications to event definitions that preserve the logical consistency of the rule base while adapting to new failure scenarios, balancing stability and versatility.
Solution Approach 2:
The patent applies universality by creating a unified event definition structure that can serve multiple failure case types. The standardized event definition framework allows the same rule structure to adapt to various failure scenarios through parameter modifications, enhancing versatility without compromising consistency across different failure types.
Data Source
AI summary
To enable more accurate determination of a failure cause event, an event mapping acquiring unit acquires an event mapping file defining a normalized alarm message indicating a normalized alarm content, a resource type indicating an event failure location, an alarm type, and an event type indicating event classification of the alarm in association with one another. An event type conversion unit determines whether input alarm information matches the definition of the event mapping file acquired, when the input alarm information matches the definition, sets the event type to a value defined in the event mapping file, when the input alarm information does not match the definition, sets the event type to the alarm type of alarm information, and registers the event type and the alarm information in association with each other as a failure event in the database.