Session-Specific Topology for Cloud Application Troubleshooting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network management systems lack the ability to provide granular troubleshooting at an application session level, especially for cloud-based applications like VOIP or video conferencing, due to limitations in monitoring and analyzing connectivity issues across complex wireless networks.
Innovation Solution
A network management system (NMS) generates an application session-specific topology using data from a temporal graph database, allowing for backward-looking troubleshooting by visualizing connectivity issues and identifying third-party devices involved in the session, even if the current network topology has changed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If current network management systems monitor and analyze connectivity issues across complex wireless networks, then network visibility is improved, but the ability to provide granular troubleshooting at application session level deteriorates
Solution Approach 1:
The patent segments the network topology information by creating application session-specific topologies that isolate and focus on only the network devices and connections relevant to a particular application session. This segmentation transforms the overwhelming global network view into manageable, session-specific slices, enabling granular troubleshooting without losing overall network visibility.
Solution Approach 2:
The patent adds a temporal dimension to network topology by storing historical topology data in a temporal graph database. This allows reconstruction of past network states for backward-looking troubleshooting, enabling analysis of connectivity issues at application session level even after the session has ended or network topology has changed.
2Loss of time
If network management systems store and analyze historical network data, then backward-looking troubleshooting capability is improved, but system complexity deteriorates
Solution Approach 1:
The patent performs preliminary action by continuously collecting, storing, and organizing network topology data in a temporal graph database during normal network operation. This pre-processing of data enables rapid backward-looking troubleshooting without requiring complex real-time analysis, reducing troubleshooting time while managing system complexity through structured data storage.
Solution Approach 2:
The patent introduces a temporal graph database as an intermediary layer between network data collection and troubleshooting analysis. This intermediary structure simplifies complex historical data into queryable topology graphs, enabling efficient backward-looking troubleshooting without directly managing the full complexity of raw network data.
3Measurement precision
If network management systems identify third-party devices involved in application sessions, then complete topology visualization is improved, but data collection complexity deteriorates
Solution Approach 1:
The patent applies universality by using a unified data collection approach that handles both internal network devices and third-party devices through the same mechanisms. The system universally collects topology data from all device types using standardized protocols, simplifying data collection complexity while achieving complete and accurate topology visualization including third-party devices.
Data Source
AI summary
A network management system (NMS) is described that provides a granular troubleshooting workflow at an application session level using an application session-specific topology from a client device to a cloud-based application server. During an application session of a cloud-based application, a client device running the application exchanges data through one or more access point (AP) devices, one or more switches at a wired network edge, and one or more network nodes, e.g., switches, routers, and/or gateway devices, to reach a cloud-based application server. For a particular application session, the NMS generates a topology based on network data received from a subset of network devices, e.g., client devices, AP devices, switches, routers, and/or gateways, that were involved in the particular application session over a duration of the particular application session. In this way, the NMS enables backward-looking troubleshooting of the particular application session.