Network Event Data Encoding and Comparison for Real-Time Reporting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network management methods, such as SNMP, telemetry, and YANG-based models, are limited in their ability to provide real-time event reporting from target devices to monitoring devices, hindering timely identification and addressing of network events.
Innovation Solution
A method for real-time logging of network data using a Network Management Interface, where a target device collects event data, encodes old and new values into a message packet, generates a comparison, and transmits the packet to monitor devices for action based on the comparison.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If traditional SNMP or telemetry methods are used for network data collection, then device compatibility and established protocol support are maintained, but real-time event reporting capability is insufficient
Solution Approach 1:
The patent introduces an intermediary mechanism that bridges traditional network management protocols with modern real-time reporting requirements. The system uses a message queue intermediary to receive events from multiple sources (SNMP traps, telemetry streams, log files) and redistributes them in real-time to subscribed clients, thereby achieving fast event reporting while maintaining compatibility with legacy protocols through the intermediary layer.
2Loss of time
If real-time event reporting is implemented, then timely identification of network events is improved, but system complexity increases
Solution Approach 1:
The patent segments the event reporting system into distinct modular components: event sources (SNMP agents, telemetry generators, log parsers), a central message queue infrastructure, and client subscription handlers. Each component operates independently with well-defined interfaces, allowing real-time event processing without requiring complex monolithic architecture. This segmentation enables incremental deployment and simplifies maintenance.
Solution Approach 2:
The message queue system serves multiple functions simultaneously: it acts as an event collection point for various protocol types, a real-time distribution network for subscribed clients, a buffering mechanism for load management, and a filtering/routing engine for event prioritization. This multi-functionality reduces overall system complexity by consolidating multiple specialized components into a single universal infrastructure.
3Measurement precision
If comprehensive event data is collected and reported, then monitoring accuracy is improved, but data transmission overhead increases
Solution Approach 1:
The patent implements partial action by allowing clients to subscribe to specific event types, source devices, or severity levels rather than requiring all events to be transmitted to all clients. The message queue system filters and routes only the relevant subset of events to each subscriber based on their subscription criteria, thereby maintaining high monitoring accuracy for relevant events while significantly reducing unnecessary data transmission and network overhead.
Data Source
AI summary
In some aspects, the system may include collecting, by a target device, event data regarding a new event on occurrence of the new event, where event data includes an old value configured to correlate the event data. Also, the system may include placing, by the target device, the event data into a service specification by using a plurality of intrinsic bindings. Furthermore, the system may include encoding both the old value and a new value into a message packet, where the new value further may include a newly updated value that is being reported as the new event. In addition, the system may include generating a comparison of the old value and the new value. Moreover, the system may include transmitting the message packet to plurality of receiving monitor devices to take action based on the comparison.