Group-Based Network Event Notification Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The conventional approach of sending individual SNMP trap messages for each network event in a network management environment leads to a high processing burden on SNMP managers, consuming significant computing and network resources, especially in virtualized environments with numerous managed nodes, resulting in information overload for administrators.

Innovation Solution

Implementing group-based network event notification, where network management entities aggregate multiple events into a single notification based on configured groups, reducing the frequency of notifications by sending them only when specific conditions are met, such as time-based or count-based thresholds.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If individual SNMP trap messages are sent for each network event, then complete event information is provided to the manager, but the processing burden on the SNMP manager increases significantly

Engineering Contradiction:
Improveevent information completenessVSAvoidSNMP manager processing capacity
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

Multiple individual SNMP trap messages are merged into a single aggregated notification message that contains information about multiple network events. The aggregation function combines events based on their type and source, reducing the number of separate messages while preserving complete event information through structured data organization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The aggregation process segments events into distinct categories based on event type and source identifier. By organizing events into structured groups with specific fields (event type, source, timestamp, details), the system maintains information completeness while enabling efficient processing through clear data segmentation.

Inventive Principle:
Principle #1Segmentation

2Loss of time

If individual SNMP trap messages are sent for each network event, then all events are notified immediately, but network bandwidth and processing resources are consumed excessively

Engineering Contradiction:
Improveevent notification timelinessVSAvoidnetwork and processing resource consumption
Core Design Contradiction:
Loss of timeVSLoss of energy

Solution Approach 1:

Multiple event notifications are combined into a single aggregated message, reducing the total number of network transmissions. This merging operation decreases network bandwidth consumption and processing resource usage while maintaining notification timeliness through efficient data consolidation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The notification mechanism changes parameters from individual event-level messages to aggregated group-level messages. By modifying the notification structure to include summary information and event counts, the system reduces resource consumption while preserving essential timing information for effective network management.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If multiple notifications are sent for different event types, then comprehensive monitoring is achieved, but information overload for administrators increases

Engineering Contradiction:
Improvenetwork monitoring completenessVSAvoidadministrator workload
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Multiple notification types are merged into a unified aggregated notification structure that organizes events by type and source. This merging approach maintains comprehensive monitoring coverage while presenting information in a consolidated format that reduces administrator workload and improves ease of operation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The notification system segments information into organized categories within the aggregated message, using structured fields to separate different event types and sources. This segmentation enables comprehensive monitoring while presenting data in an organized manner that reduces information overload for administrators.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11831492B2Group-based network event notification
Publication Date: 2023.11.28 VMWARE INC
  • US11831492B2 patent drawing
  • US11831492B2 patent drawing
  • US11831492B2 patent drawing

AI summary

Example methods are provided for network management entity to perform group-based network event notification in a network environment that includes the network management entity and a notification consumer. The method may comprise: in response to detection of a first network event associated with a group, withholding notification of the first network event to the notification consumer; and in response to detection of a second network event associated with the group, withholding notification of the second network event to the notification consumer. The method may further comprise generating a group notification associated with the group, wherein the group notification is an aggregate notification to report the detection of at least the first network event and second network event; and sending the group notification to the notification consumer.