Wireless Network Troubleshooting Intent for Real-Time Tool Activation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current troubleshooting tools for wireless networks require substantial offline interaction and are statically configured, leading to delays in identifying network issues and inability to be programmed, especially for dynamic performance problems.
Innovation Solution
A centralized troubleshooting engine in the core network that programs and collects troubleshooting information from management entities using a programmable intent framework, combining existing tools for real-time analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If current troubleshooting tools are used, then troubleshooting can be performed, but substantial offline interaction and delays occur in identifying network issues
Solution Approach 1:
The troubleshooting system transitions from static configuration to dynamic programmability. The intent framework allows troubleshooting tools to be programmed and activated in real-time based on network conditions and specific troubleshooting needs, enabling the system to adapt and respond dynamically rather than relying on pre-configured static tools that require offline engineering work.
Solution Approach 2:
A centralized troubleshooting engine is introduced as an intermediary component that coordinates between multiple management entities and troubleshooting tools. This engine receives intent messages, identifies appropriate tools across different management entities, and orchestrates their activation and information collection, thereby reducing the need for direct offline interaction and accelerating the troubleshooting process.
2Adaptability or versatility
If static troubleshooting tools are used, then configuration is simple, but the tools cannot be programmed for dynamic performance problems
Solution Approach 1:
The intent framework provides a universal programming interface that can be applied across multiple management entities and troubleshooting tools. This single framework enables diverse troubleshooting scenarios to be handled through a common mechanism, increasing adaptability without proportionally increasing complexity. The framework acts as a universal layer that simplifies the interface between the user and the complex underlying tools.
Solution Approach 2:
The centralized troubleshooting engine serves as an intermediary that manages the complexity of multiple troubleshooting tools. It receives high-level intent messages from users and translates them into specific tool activations and configurations across different management entities. This intermediary absorbs the complexity, presenting a simplified interface to users while coordinating the underlying complex toolset.
3Ease of operation
If multiple troubleshooting tools are distributed across management entities, then tool functionality is distributed, but resource consumption increases and coordination becomes complex
Solution Approach 1:
The system implements feedback mechanisms where the centralized troubleshooting engine receives status information from distributed troubleshooting tools and management entities. Based on this feedback, the engine can intelligently determine which tools to activate, how long to run them, and when to collect information. This feedback loop enables optimized resource consumption by activating only the necessary tools for each specific troubleshooting scenario rather than continuously running all tools.
Solution Approach 2:
The patent combines multiple distributed troubleshooting tools under a unified centralized control framework. While the tools remain distributed across management entities for functionality, their coordination and resource management are merged into a single centralized engine. This merging of control functions reduces overall resource consumption by eliminating redundant operations and optimizing the activation patterns of distributed tools.
Data Source
Figure 1
Figure 2(A)~2(B)
Figure 3
AI summary
A control network node (45) of a wireless network (10) comprises a troubleshooting engine (100) for troubleshooting a wireless network (10). The control network node (45) receives, from a plurality of management entities (200), capability information identifying troubleshooting tools for each of the plurality of management entities (200). The control network node (45) also receives, from a troubleshooting entity (300), a troubleshooting intent message requesting troubleshooting information. The control network node (45) identifies, using the capability information, at least one of the plurality of management entities (200) having active troubleshooting tools capable of providing the requested troubleshooting information and collects the requested troubleshooting information from the identified at least one of the plurality of management entities (200) using the active troubleshooting tools. The control network node (45) forwards the collected troubleshooting information to the troubleshooting entity (300).