Network Configuration Translation via Common Network Data Graph Schema

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Network management systems face challenges in managing diverse network elements due to differences in configuration management messaging formats, which hinder effective querying, anomaly detection, and discrepancy correction.

Innovation Solution

An integrated network configuration management system translates configuration management messaging data from various formats into a Common Network Data (CND) model format, enabling unified storage and querying, and facilitating anomaly detection and discrepancy correction through a flexible graph schema.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network management systems use multiple different configuration management messaging formats to support diverse network elements, then the system can accommodate more types of network elements, but the complexity of managing and processing these different formats increases significantly

Engineering Contradiction:

Improveability to manage diverse network elementsVSAvoidcomplexity of managing configuration formats

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Common Information Model (CIM) as an intermediary layer between diverse network elements and the network management system. Configuration data from different network elements is translated into the standardized CIM format, which serves as a common language that simplifies management while maintaining compatibility with diverse equipment types.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system transforms configuration data by changing its format parameters - converting proprietary formats from different vendors into a unified CIM structure. This parameter transformation allows the same underlying data to be represented in a consistent manner across diverse network elements without losing vendor-specific capabilities.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If the system stores configuration data in multiple proprietary formats from different vendors, then all vendor-specific features are preserved, but querying and analyzing this data becomes difficult and inconsistent

Engineering Contradiction:

Improvepreservation of vendor-specific featuresVSAvoidease of querying and analyzing data

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The CIM schema acts as an intermediary representation that preserves vendor-specific features through optional attributes while providing a consistent querying interface. The standardized structure allows uniform queries to be executed across all vendor data, with vendor-specific details accessible when needed through the common framework.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The configuration data is segmented into hierarchical levels: a standardized CIM core structure that enables consistent querying, and vendor-specific extensions that preserve proprietary features. This segmentation allows the system to operate efficiently on the standardized portion while maintaining access to vendor-specific capabilities.

Inventive Principle:

Principle #1Segmentation

3Reliability

If the system processes configuration data in original proprietary formats, then data integrity is maintained, but anomaly detection and discrepancy correction become less effective

Engineering Contradiction:

Improvedata integrityVSAvoiddifficulty of anomaly detection

Core Design Contradiction:

ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system changes the format parameters of configuration data into CIM while maintaining data integrity through structured translation. This parameter transformation enables standardized anomaly detection algorithms to operate on the translated data, improving detection effectiveness while preserving the original data's integrity through reversible or lossless translation where possible.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS11496610B2Network management data translation, querying, and discrepancy detection

Publication Date: 2022.11.08 VERIZON PATENT & LICENSING INC

AI summary

A network device receives a first configuration management message from a first network element, where the first configuration management message has a first data format. The network device translates the first configuration management message from the first data format to a Common Network Data (CND) model format to produce a first translated message, where the CND model format comprises a graph schema based on nodes, edges, and properties to represent and store configuration management message data. The network device stores the first translated message in a CND model format data structure for subsequent use in message querying, message comparison, message anomaly detection, or message discrepancy detection.