Network Management Using Pattern-Based Data Structures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network management systems rely heavily on standardized protocols like SNMP, which consume significant bandwidth due to the inclusion of ASN.1/BER references, limiting flexibility and increasing costs by requiring network equipment to understand and implement complex management information base (MIB) specifications.
Innovation Solution
A method and system where management devices and equipment exchange management data using data structures represented as patterns with identifiers, allowing synchronization information to translate between the equipment's data structures and the management information base, enabling flexible management without reliance on the reference specification, thus reducing bandwidth usage and simplifying equipment design.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standardized protocols like SNMP with ASN.1/BER references are used for network management data exchange, then data exchange capability is ensured, but bandwidth consumption increases significantly
Solution Approach 1:
The management data exchange process is segmented into two distinct phases: a synchronization phase where the management device sends MIB portion definitions and references to the network equipment, and a subsequent data exchange phase where only compact pattern identifiers and encoded values are transmitted. This segmentation allows the bulky reference specifications to be sent once rather than repeatedly, significantly reducing ongoing bandwidth consumption while maintaining complete data exchange capability.
Solution Approach 2:
Instead of transmitting the full ASN.1/BER encoded management data with complete references in every message, the system creates compact copies using pattern identifiers that reference previously synchronized MIB portions. The network equipment stores local copies of the MIB portion definitions and uses these to encode/decode management data efficiently, reducing bandwidth usage to only the essential data changes rather than complete protocol messages.
2Adaptability or versatility
If network equipment implements full MIB specifications to understand management data, then management compatibility is achieved, but device complexity increases
Solution Approach 1:
The complex MIB specification knowledge is extracted from the network equipment and centralized in the management device. The management device sends only the necessary MIB portion definitions and references relevant to specific equipment types, rather than requiring equipment to implement complete MIB specifications. This extraction reduces equipment complexity while maintaining compatibility through selective knowledge distribution.
Solution Approach 2:
The management device acts as an intermediary that holds and manages the complete MIB specification knowledge. It translates between the simplified pattern-based data structures used in compact messages and the full MIB references needed for comprehensive management. This intermediary approach allows equipment to use simple patterns while the management device provides the complex reference resolution, separating knowledge requirements from implementation complexity.
3Loss of energy
If compact pattern-based data structures are used instead of ASN.1/BER references, then bandwidth consumption is reduced, but translation complexity increases
Solution Approach 1:
The translation infrastructure is set up in advance through a synchronization process where the management device sends MIB portion definitions, pattern mappings, and reference information to the network equipment before actual management data exchange begins. This preliminary action pre-configures the translation capabilities, so that during operational data exchange, only simple pattern identifier lookups are needed rather than complex real-time translation, reducing both bandwidth usage and operational complexity.
Data Source
AI summary
A device manages a management database in the form of objects to be managed that are referenced according to a reference specification. Equipment exchanges management data in the form of data structures indicated by patterns each corresponding to a respective referenced object and being assigned a respective identifier. In order to manage a given object, the device and the equipment store synchronization information associating the reference of the given object and the corresponding pattern identifier. In order to manage a given object, the equipment sends the corresponding pattern assigned the respective identifier and a data ticket which has a structure indicated by said pattern and is assigned said identifier. The device translates the pattern into the respective referenced object as a function of the identifier of said pattern and the synchronization information, and then stores the data from the received ticket in the management database.