Network Management Protocol Conversion to Markup Language

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing network routers with multiple protocols and interfaces is complex due to the need for separate backend processes and updates across CLI, SNMP, and XML management interfaces, leading to increased complexity and maintenance challenges.

Innovation Solution

A method that converts network management protocol requests into markup language representation using an instrumentation module to generate XML tags and content, enabling unified backend processing through a centralized configuration manager.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate backend processes are maintained for all management applications and protocols (CLI, SNMP, XML), then each protocol can be fully supported, but device complexity increases and maintenance becomes difficult

Engineering Contradiction:
Improveprotocol supportVSAvoidbackend processes
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple protocol-specific backend processes into a single unified backend process that handles CLI, SNMP, and XML requests through a common configuration database interface, eliminating the need for separate maintenance routines for each protocol

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified backend process is designed to perform multiple functions by accepting requests from different management protocols and translating them into a common internal representation, allowing one process to serve multiple protocol interfaces

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If the router supports numerous protocols and control applications, then network management capability is enhanced, but configuration management complexity increases

Engineering Contradiction:
Improveprotocol supportVSAvoidconfiguration management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a unified configuration database as an intermediary layer between multiple management protocols and the router's configuration data, providing a single point of access that simplifies configuration management while supporting numerous protocols

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If multiple management interfaces (CLI, SNMP, XML) access the configuration database, then management flexibility is improved, but maintaining recognition of all interface commands becomes difficult

Engineering Contradiction:
Improvemanagement flexibilityVSAvoidcommand recognition
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the management interface functionality by separating the protocol-specific command parsing from the configuration database access, allowing each protocol interface to be maintained independently while sharing a common backend processing mechanism

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7657635B2Method and apparatus for converting network management protocol to markup language
Publication Date: 2010.02.02 EXTREME NETWORKS INC
  • US7657635B2 patent drawing
  • US7657635B2 patent drawing
  • US7657635B2 patent drawing

AI summary

A method is provided to convert network management protocol request into a markup language representation. In one embodiment, the present invention includes receiving a network management protocol request at a network device, generating a plurality of markup language tags and content embedded in the markup language tags based on the received request, and responding to the request using the plurality of markup language tags and content embedded in the markup language tags using a unified backend interface. In one embodiment, routines used to generate the plurality of markup language tags and content are generated automatically using an instrumentation module.