Network Incident Event Sequence Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network management systems face challenges in efficiently tracking and managing incidents across network elements, as information related to these incidents is often dispersed across various systems without clear associations, making it difficult to leverage previous responses for consistent and efficient issue resolution.
Innovation Solution
The system creates and manages event records associated with network incidents, determining dependencies between incidents to store related records in the same event sequence, allowing for efficient management, tracking, and presentation of incident data to users, including automatic generation of reports and notifications, and enabling user interaction with event records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If information related to network incidents is stored in various systems without association, then each system can maintain its own data independently, but it becomes difficult to leverage existing knowledge for consistent and efficient responses
Solution Approach 1:
The patent merges dispersed incident information from multiple systems into a unified event sequence structure. Related event records are linked through dependency relationships, creating a cohesive narrative of incident progression and response actions across previously siloed systems.
Solution Approach 2:
The patent segments incident information into discrete event records that can be independently created and managed, then associates them through dependency relationships. This allows flexible organization of information while maintaining clear relationships between related events.
2Productivity
If multiple separate systems track network incidents, then each system can specialize in specific aspects, but it increases the difficulty of tracking and managing incidents across the network
Solution Approach 1:
The event sequence structure serves multiple functions: it tracks incident progression, records response actions, establishes dependencies between events, and provides a unified view across network elements. This multi-functional approach consolidates what would otherwise require multiple specialized systems.
3Loss of information
If incident information is dispersed across various systems, then system flexibility is maintained, but it becomes difficult to provide a clear audit trail and facilitate post-mortem analysis
Solution Approach 1:
The system preliminarily organizes incident information into event records with explicit dependency relationships as they occur. This pre-structuring ensures that the audit trail is maintained automatically throughout the incident lifecycle, eliminating the need for retrospective data assembly during post-mortem analysis.
Data Source
AI summary
One or more event records associated with incidents that may occur in a network may be created and stored in an event sequence with other related event records. Whether the event records are related may be determined based at least in part on a dependency between network elements associated with the incidents. The one or more event records may be executed by event handlers to create additional event records, which may also be stored in an event sequence with related event records. A user may request event sequences for display at a user device. Event sequences may be processed to provide at least a portion of the sequences based at least in part on user-specific information. A user may interact with and/or respond to event records in the network. Such interactions or responses may also be stored as event records in an event sequence.