Debug Data Collection via User-Driven Session Quality
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for collecting debug information in communication systems require significant memory and often collect uninformative data, and typically need a system administrator or custom support engineer to initiate data collection, which can occur after a problem has already occurred.
Innovation Solution
Monitoring communication sessions based on user-driven conditions, where data is gathered only if the session is unsatisfactory, and marking specific call control data for debug information collection, allowing users to determine session quality and reducing unnecessary data collection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If debug information is collected for nearly all communication sessions, then the quantity of debug data is increased, but memory usage increases and performance decreases
Solution Approach 1:
The patent extracts only the necessary debug information (call control data) from communication sessions rather than collecting all possible data. By selectively taking out only the relevant call control parameters, the system obtains sufficient debug information while minimizing memory consumption and performance impact.
Solution Approach 2:
The patent applies local quality by collecting debug information with different characteristics based on specific conditions. Call control data is collected for all sessions (satisfactory or not), while detailed debug traces are collected only for unsatisfactory sessions. This localized approach optimizes the balance between data quantity and resource usage.
2Device complexity
If debug information is collected after problem detection by system administrator, then the complexity of automated collection is reduced, but informative debug information may be lost before collection
Solution Approach 1:
The patent performs preliminary action by automatically collecting call control data for all communication sessions from the outset, before any problem detection occurs. This ensures that informative debug information is captured at the moment it occurs, eliminating the delay inherent in administrator-initiated collection while maintaining simple automated operation.
Solution Approach 2:
The system performs self-service by automatically monitoring communication sessions and collecting debug information without requiring system administrator intervention. The system itself identifies and collects data for unsatisfactory sessions, making the process both simple to operate and timely in capturing relevant information.
3Measurement precision
If monitoring continues until communication session is satisfactory, then the accuracy of quality assessment is improved, but the time for data collection is increased
Solution Approach 1:
The patent extracts call control data continuously for all sessions while reserving detailed debug trace collection for only those sessions that are determined to be unsatisfactory. This extraction approach allows comprehensive quality assessment monitoring without the time penalty of collecting full debug information for every session.
Solution Approach 2:
The patent applies local quality by differentiating the collection intensity based on session quality status. Call control data is collected with consistent quality for all sessions, while detailed debug information is collected locally only where needed (unsatisfactory sessions), optimizing both assessment accuracy and collection time.
Data Source
AI summary
Collecting debug information includes facilitating a communication session for an endpoint operated by a user. One or more user-driven conditions are monitored, where a user-driven condition results from an action by the user. Data is gathered during the monitoring. Whether the communication session is satisfactory or unsatisfactory is determined from the one or more user-driven conditions. Monitoring is discontinued if the communication session is satisfactory, and debug information is generated from the gathered data if the communication session is unsatisfactory.