Event-Driven Network Diagnostics Using Persisted Service Paths
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication network diagnostics are reactive and inefficient, leading to a high number of service tickets and delays in troubleshooting.
Innovation Solution
A proactive and customer-initiated diagnostic system that uses event-driven diagnostics, leveraging a persisted path and performance metrics to identify events and notify customers, reducing the need for service tickets by allowing real-time diagnostics and automated updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If reactive diagnostics are used (waiting for service calls), then device complexity is reduced, but service ticket volume increases and troubleshooting efficiency decreases
Solution Approach 1:
The system pre-generates persisted paths for services before any diagnostic requests are made. These paths map the complete service delivery chain including all devices and interfaces, enabling immediate proactive monitoring without requiring service calls to trigger path discovery
Solution Approach 2:
The diagnostic system automatically monitors performance metrics and detects events without requiring customer initiation. The system self-activates monitoring, collects metrics, detects anomalies, and notifies customers, eliminating the need for reactive service calls
2Reliability
If proactive diagnostics are implemented, then service ticket generation is reduced, but system complexity increases
Solution Approach 1:
The persisted path structure serves multiple functions: it maps service delivery, enables performance monitoring, supports event detection, and facilitates customer notification. This single data structure handles all proactive diagnostic operations without requiring separate systems for each function
Solution Approach 2:
The persisted path acts as an intermediary data structure that connects service identifiers to performance metrics and event detection logic. It pre-establishes the relationship between services and their constituent devices/interfaces, simplifying the monitoring process
3Measurement precision
If real-time performance monitoring is implemented, then event detection accuracy improves, but data processing requirements increase
Solution Approach 1:
Performance metrics collection and event criteria comparison are pre-configured based on the persisted path structure. The system establishes monitoring rules in advance for each service path, enabling efficient real-time detection without ad-hoc data processing
Solution Approach 2:
The system monitors performance metrics specifically for devices and interfaces identified in the persisted path for each service. Rather than blanket monitoring of all network elements, it focuses computational resources on the specific components that constitute actual service delivery paths
Data Source
AI summary
A device for performing event-driven diagnostics may identify a service identifier of a service provided by the communications network to a customer; identify, based on the service identifier, a persisted path for the service, the persisted path generated prior to any user request to perform a diagnostic on the service, and the persisted path including devices and interfaces used to provide the service; receive performance metrics of the devices and interfaces of the persisted path; detect, without receiving any user request to perform a diagnostic on the service, based on comparisons of the performance metrics to event criteria, an occurrence of an event in the persisted path; and present, based on the occurrence of the event, a notification of the event to the customer.