Network Device Event Reporting Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Troubleshooting disruptions in large-scale network systems is challenging due to the complexity and inefficiency of conventional polling methods, which consume significant network bandwidth and are time-consuming.

Innovation Solution

Implementing a 'push' reporting mechanism where network devices initiate report messages upon detecting events, such as configuration changes or performance conditions, allowing the network management server to receive operational information proactively, reducing the need for repeated querying and improving troubleshooting efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If polling methods are used to monitor network devices, then network management systems can gather operational information, but network bandwidth is significantly consumed and troubleshooting becomes time-consuming

Engineering Contradiction:
Improvenetwork monitoring capabilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent inverts the traditional polling architecture by switching from pull-based (NMS queries devices) to push-based (devices send reports autonomously) information gathering. Network devices independently detect events and proactively report operational information to the NMS, eliminating the need for continuous polling and significantly reducing network bandwidth consumption while maintaining comprehensive monitoring capability

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

Network devices perform self-monitoring and autonomously generate event reports when specific conditions are detected. The devices take responsibility for detecting configuration changes, performance issues, and other operational events, then automatically report this information without requiring external queries from the NMS, thereby reducing overall system overhead and bandwidth usage

Inventive Principle:
Principle #25Self-service

2Reliability

If polling methods are used to monitor network devices, then operational information can be gathered, but troubleshooting efficiency decreases as systems become larger and more complex

Engineering Contradiction:
Improvenetwork monitoring capabilityVSAvoidtroubleshooting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by having network devices continuously monitor and detect events in real-time, maintaining a ready state for immediate reporting. When disruptions occur, the NMS can quickly query for relevant event reports that have already been collected and stored by devices, enabling rapid troubleshooting without the delays associated with initiating polling operations after a problem is detected

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where network devices provide continuous operational information and event reports to the NMS. This feedback loop enables the NMS to maintain an up-to-date view of network status and quickly analyze event data during troubleshooting, significantly reducing the time required to identify and resolve issues in large-scale networks

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9425976B2Reporting operational information of a network device
Publication Date: 2016.08.23 HEWLETT PACKARD ENTERPRISE DEV LP
  • US9425976B2 patent drawing
  • US9425976B2 patent drawing
  • US9425976B2 patent drawing

AI summary

A method for reporting operational information in a network is described herein. The network may include a network device and a network management server. The network device may detect an event triggering reporting of a modification to a configuration of the network device. A report message initiated by the network device may be provided. The report message may identify the modification to the configuration. The modification to the configuration may be committed after providing the report message. In another embodiment, the network device detects an event indicating a performance condition in the network device. A report message initiated by the network device is generated. The report message may include a state of the network device at the time of the event.