Trap Event Listener Port Segmentation for Network Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current SNMP trap/event registration mechanisms require decoding or polling to determine event types, leading to scalability and performance issues due to unnecessary network traffic and prolonged processing times.

Innovation Solution

Implementing a mechanism where distinct trap/event types are registered on separate management system input ports, allowing trap/event signals to be communicated directly to corresponding listener ports for immediate identification and processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If all trap/event types are registered on a single standard port (e.g., port 162), then the management system can receive all events at one location, but the system must decode or poll the device to determine event types, causing increased network traffic and processing time

Engineering Contradiction:
Improvetrap/event reception simplicityVSAvoidevent identification time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent segments the single trap reception port into multiple dedicated ports, with each port handling a specific trap/event type. This allows the management system to receive events directly at their designated ports without needing to decode or poll the device, eliminating the time loss associated with event type determination.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If the management system polls the device to determine trap/event types, then the system can identify event types accurately, but it causes unnecessary network traffic and scalability issues

Engineering Contradiction:
Improveevent type identification accuracyVSAvoidnetwork traffic volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

By segmenting trap reception into dedicated ports for each event type, the system eliminates the need for polling to determine event types. Events are delivered directly to their specific ports, reducing network traffic volume while maintaining accurate event type identification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dedicated ports as intermediaries between the device and the management system. Each port acts as a mediator that receives specific trap types directly from the device, eliminating the need for the management system to poll the device for event type information.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If the management system uses a single port for all trap events, then the registration process is simple, but processing and decoding all event types becomes complex and time-consuming

Engineering Contradiction:
Improveregistration mechanism simplicityVSAvoidevent processing speed
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments the trap processing function by creating dedicated ports for each trap type. This allows the management system to process events more quickly by directing them to appropriate ports without needing to decode or interpret all event types, thereby improving processing speed while keeping the registration mechanism straightforward.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9094296B2Method and apparatus for determining trap/event information via intelligent device trap/event registration and processing
Publication Date: 2015.07.28 CONDUENT BUSINESS SERVICES LLC
  • US9094296B2 patent drawing
  • US9094296B2 patent drawing
  • US9094296B2 patent drawing

AI summary

Methods and systems are disclosed comprising a trap/event registration mechanism wherein a management system in a device network registers each trap/event type on a separate unique listener port. Each unique port number has intelligent binding of the kind of trap/event that can be received thereat. Each trap/event type is tightly bound to the special unique listener port so that the management system will know by virtue of receiving the trap/event at the unique port what kind of trap/event occurred on the device.