Dynamic Context Management for Network Node Data Collection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current operations management systems require users to set up filters to sift through large amounts of data, leading to missed key information and degraded database and network performance due to excessive data handling.

Innovation Solution

The system determines context information for network nodes, sending data collection rules to dynamically configure data gathering, allowing for real-time data collection and organization, which is then displayed on a user interface, enhancing efficiency and reducing data overload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users setup filters to sift through large amounts of data in centrally managed systems, then specific information can be viewed, but key information may be missed and database access performance degrades

Engineering Contradiction:
Improveinformation retrievalVSAvoidinformation completeness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system automatically determines context information and configures data collection rules without requiring user intervention. The operations management system autonomously identifies relevant context, sends appropriate data collection rules to network nodes, and retrieves necessary information, eliminating the need for users to manually setup filters while ensuring complete and accurate information retrieval.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary context determination and data collection rule configuration before information retrieval is needed. By pre-establishing context information and configuring appropriate data collection rules at the network nodes, the system ensures that relevant data is already prepared and available when needed, improving both retrieval ease and information completeness.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If large amounts of data are sent and stored in centrally managed databases, then comprehensive information is available, but database access and network performance degrade

Engineering Contradiction:
Improvedata volumeVSAvoiddatabase access performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system extracts only the necessary context information from the overall data set and sends targeted data collection rules to specific network nodes. Instead of gathering and storing all possible data centrally, the system extracts and transmits only the relevant context information needed for operations management, reducing data volume while maintaining information quality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements local data collection by sending specific data collection rules to individual network nodes based on their context. Each node collects and processes data locally according to its specific needs and the received rules, rather than all nodes sending all data to a central repository. This distributes the data handling workload and improves overall system performance.

Inventive Principle:
Principle #3Local quality

3Loss of information

If comprehensive data is collected from all network nodes, then complete information is available, but the time required to retrieve and display information increases

Engineering Contradiction:
Improveinformation completenessVSAvoidinformation retrieval time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system dynamically configures data collection rules based on determined context information. The data collection process is not static but adapts to the specific operational context, sending different rules to different nodes based on their current state and requirements. This dynamic approach ensures that only relevant information is collected and transmitted, reducing retrieval time while maintaining completeness.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system establishes continuous context determination and data collection rule configuration, ensuring that the appropriate data is continuously gathered from network nodes. By maintaining continuous useful action in data collection based on context, the system ensures information is available when needed without requiring lengthy retrieval processes.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS11546475B2System and method for dynamic driven context management
Publication Date: 2023.01.03 MICRO FOCUS LLC
  • US11546475B2 patent drawing
  • US11546475B2 patent drawing
  • US11546475B2 patent drawing

AI summary

Context information associated with a network node is determined. For example, a network node (e.g., a server) has indicated that an application on the network node appears to be having performance problems. The context information may be to gather data about the application, such as, load, number of users accessing the application, etc. The context information comprises one or more rules for dynamically configuring how data is collected on the node. For example, the rule may indicate what specific statistics should be gathered from the application in real-time. The context information is sent to the network node. Node information is received from the network node in response to sending the context information. The node information is collected based on the one or more rules for configuring how data is collected on the network node. The node information is organized and is displayed on a user interface to a user.