NETCONF Session Management via Capability Intersection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of managing NETCONF sessions across network devices from different vendors, due to varying transport layer protocols, capability sets, and configuration data models, creates a burden for administrators in network management.

Innovation Solution

A method is introduced where a network management system (NMS) searches for supported transport layer protocols and defines metadata to establish NETCONF sessions, compares capability sets, and uses a protocol abstract architecture to perform configuration access, allowing for unified management across diverse vendor devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If NETCONF sessions are managed across network devices from different vendors using varying transport layer protocols, then comprehensive device compatibility is achieved, but management complexity increases

Engineering Contradiction:
Improvedevice compatibilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (NETCONF server or gateway) that mediates between the network management system and diverse network devices. This intermediary handles protocol translation and capability mapping, allowing the NMS to interact with a unified interface while the intermediary manages the complexity of multiple transport layer protocols and vendor-specific implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a universal NETCONF session management framework that can handle multiple transport layer protocols (SSH, TLS, TCP) and vendor-specific capabilities through a single unified interface. The system defines standardized capability sets that work across different device types, allowing one system to serve multiple functions and protocols without requiring separate management mechanisms for each.

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

2Adaptability or versatility

If vendor-specific transport layer protocols and capability sets are supported, then device-specific functionality is preserved, but ease of operation decreases

Engineering Contradiction:
Improvevendor-specific functionalityVSAvoidadministrator burden
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates standardized copies or abstractions of vendor-specific capabilities through defined capability sets. Instead of requiring administrators to directly manage diverse vendor protocols, the system creates unified capability representations that capture essential functions across vendors, allowing administrators to operate with standardized commands while the underlying vendor-specific implementations are handled automatically.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent segments the complexity by separating the user-facing interface from the protocol implementation details. The capability set framework divides functionality into discrete, manageable units that can be independently configured and managed. This segmentation allows administrators to work with high-level abstractions while the system handles the segmented protocol-specific complexities in the background.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If a unified NETCONF session management approach is implemented across diverse devices, then operational consistency is improved, but adaptability to vendor-specific protocols decreases

Engineering Contradiction:
Improveoperational consistencyVSAvoidprotocol flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic capability negotiation mechanism where the system adapts its behavior based on the specific vendor and device capabilities detected during session establishment. The capability sets are dynamically configured and selected based on the target device, allowing the unified management approach to automatically adjust to the appropriate protocol version and feature set for each vendor while maintaining consistent operational procedures.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10250441B2Network configuration access
Publication Date: 2019.04.02 HEWLETT PACKARD ENTERPRISE DEV LP
  • US10250441B2 patent drawing
  • US10250441B2 patent drawing
  • US10250441B2 patent drawing

AI summary

Searching, according to the type information of a network device, for a transport layer protocol supported by the network device in a transport layer architecture of a network configuration protocol (NETCONF) configuration framework and definition information which is to be used to implement a connection to the network device. Establishing a NETCONF session to the network device by using the transport layer protocol and the definition information. During establishment of the NETCONF session, comparing a first NETCONF capability set obtained from the network device with a second NETCONF capability set which is supported by the NMS and is defined in a metadata definition file. Assigning an intersection of the first NETCONF capability set and the second NETCONF capability set as an active capability set. Then, performing a network configuration access to the network device based on the active capability set.