SNMP Access via Service Objects and XML Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

SNMP access requires in-depth knowledge of MIB objects and their OIDs, making it tedious for managers to build variable bindings and translate responses, which hinders user-friendly network management.

Innovation Solution

Mapping MIB objects to XML objects and generating a class library to create service objects that simplify SNMP access by translating instructions into command messages and OIDs, reducing the need for MIB knowledge and response translation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If SNMP access uses traditional MIB objects and OIDs, then network management functionality is complete, but user operation complexity increases and ease of operation deteriorates

Engineering Contradiction:
Improveease of SNMP accessVSAvoidMIB knowledge requirement
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces service objects as an intermediary layer between users and MIB objects. Service objects provide a simplified interface that automatically translates user-friendly service names into the corresponding OIDs and command messages required by SNMP agents, eliminating the need for users to directly handle complex MIB structures and OID sequences

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates service objects that are conceptual copies or abstractions of underlying MIB objects. Each service object encapsulates the essential functionality of one or more MIB objects while presenting a simplified interface, allowing users to interact with network devices through intuitive service names rather than technical OID identifiers

Inventive Principle:
Principle #26Copying

2Productivity

If SNMP access requires building variable bindings with OIDs, then precise object identification is achieved, but time consumption and productivity decrease

Engineering Contradiction:
ImproveSNMP access efficiencyVSAvoidtime to build variable bindings
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-defining service objects that encapsulate the mapping between service names and OIDs before actual SNMP operations. This allows the system to automatically retrieve and use the correct OID mappings during runtime without requiring users to manually construct variable bindings, significantly reducing time consumption

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The service object mechanism enables self-service by automatically handling the translation from service names to OIDs and command messages. The system autonomously manages the complexity of variable binding construction, error handling, and response translation without requiring user intervention in these tedious tasks

Inventive Principle:
Principle #25Self-service

3Ease of operation

If SNMP managers directly access MIB objects, then full control over network devices is achieved, but device complexity for users increases

Engineering Contradiction:
Improvesimplicity of SNMP accessVSAvoidMIB object detail knowledge
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent segments the monolithic MIB object structure into multiple service objects, each representing a specific network management function. This segmentation allows users to access only the relevant service objects needed for their tasks without being overwhelmed by the complete MIB hierarchy, while the system maintains full access to underlying MIB details for accurate device control

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP2009842B1System and method for SNMP access
Publication Date: 2012.12.26 IYUKO SERVICES
  • EP2009842B1 patent drawingFigure 1
  • EP2009842B1 patent drawingFigure 2
  • EP2009842B1 patent drawingFigure 3

AI summary

Systems and methods for SNMP access are disclosed. A computer-implemented method of SNMP access includes mapping a MIB object in a MIB into an XML object in an XML document, generating a class library based on the XML document, creating a service object representative of a service associated with SNMP access to the MIB object, and linking the class library according to the service object to perform the service.