Network Management System TRAP Message Identifier Comparison

Solution Overview

Problem

Network management systems face inefficiencies and data inconsistencies due to limited capacity for processing TRAP messages, leading to potential message loss and unnecessary synchronization, especially when configuration data changes infrequently.

Innovation Solution

Configuring identifiers for different types of device data, which are stored in the network management system's database, allowing for comparison with identifiers sent from the device during TRAP message processing and synchronization, enabling updates only when inconsistencies are detected, thus reducing redundant data access and improving synchronization efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the network management system processes all TRAP messages and performs full data synchronization, then data consistency between the database and device side is maintained, but the processing load and time consumption increase significantly

Engineering Contradiction:

Improvedata consistencyVSAvoidsynchronization time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential identification information (data identifiers) from the complete device data and transmits it via TRAP messages. The network management system compares these identifiers against the database to determine what needs updating, rather than transferring and processing all device data. This extraction approach maintains data consistency while dramatically reducing processing time and load.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing complete data synchronization every time a TRAP message is received, the system performs partial synchronization by only updating data when identifier changes are detected. This partial action approach avoids unnecessary full synchronizations, reducing time consumption while ensuring data consistency is maintained when actually needed.

Inventive Principle:

Principle #16Partial or excessive action

2Reliability

If the network management system performs frequent data synchronization with the device, then data consistency is ensured, but processing efficiency decreases and overhead increases

Engineering Contradiction:

Improvedata consistencyVSAvoidprocessing efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system implements periodic identification comparison rather than continuous data synchronization. TRAP messages containing data identifiers are sent at specific intervals or events, and the network management system periodically compares these identifiers against the database. This periodic action maintains data consistency while allowing the system to operate efficiently between comparison cycles without constant full synchronizations.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The patent extracts only the essential identification information (data identifiers) from the complete device data and transmits it via TRAP messages. The network management system compares these identifiers against the database to determine what needs updating, rather than transferring and processing all device data. This extraction approach maintains data consistency while dramatically reducing processing time and load.

Inventive Principle:

Principle #2Taking out (Extraction)

3Measurement precision

If the network management system retrieves complete device data for every TRAP message, then accurate data updates are achieved, but the number of data access operations and system load increase

Engineering Contradiction:

Improvedata update accuracyVSAvoidsystem load

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts only the essential identification information (data identifiers) from the complete device data and transmits it via TRAP messages. The network management system compares these identifiers against the database to determine what needs updating, rather than transferring and processing all device data. This extraction approach maintains data consistency while dramatically reducing processing time and load.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary comparison of data identifiers before initiating complete data retrieval. When a TRAP message arrives, the network management system first compares the contained identifier with the database entry. Only when an inconsistency is detected does the system then retrieve the complete device data for updating. This preliminary action filters out unnecessary full data retrievals, reducing system load while maintaining update accuracy.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS7711816B2Method for managing network device data and network management system

Publication Date: 2010.05.04 HUAWEI TECH CO LTD

AI summary

Embodiments of the present invention disclose a method for managing network device data and a network management system. The method including: storing identifiers respectively for different types of device data at the device side; the network management system storing the identifiers of the different types of device data into a database of the network management system upon synchronizing the device data; and during TRAP message processing and timing data synchronization, the network management system comparing the identifiers locally stored with the identifiers from the device side, and performing a corresponding update according to the comparison result.