Parallel Configuration Data Structure Update Without Freezing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for maintaining configuration data structures in network devices, such as network elements, face challenges where updates require freezing the configuration and consume significant resources due to the need for detailed modeling or lengthy lists of change descriptors.

Innovation Solution

A processing system that runs an operative process to make changes and adds change descriptors, while also running an auxiliary process in parallel to update the configuration data structure by replacing a portion with an auxiliary configuration data structure constructed from reported configurations, allowing updates without freezing the configuration and reducing the need for detailed modeling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the configuration data structure is updated by requesting functional entities to report their configurations and re-constructing the configuration data structure, then the configuration data structure can be updated to correspond to the prevailing configuration, but the configuration has to be frozen during the update process, preventing changes from being made

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration update flexibility
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent divides the configuration data structure into two separate components: an auxiliary configuration data structure that captures the state at a specific time instant, and a list of change descriptors that record subsequent changes. This segmentation allows the system to maintain accurate configuration history without requiring the entire configuration to be frozen during updates, as changes can be appended to the change descriptors list while the auxiliary structure remains static.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by creating an auxiliary configuration data structure that captures the configuration state at a specific time instant before any subsequent changes occur. This preliminary snapshot allows the system to later reconstruct the configuration at that time instant without needing to freeze the configuration during normal operations, as the snapshot already preserves the historical state.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If a detailed model of the device is maintained to ensure the configuration model is an exact copy of the device configuration, then the configuration can be accurately represented, but significant resources are consumed because the model is quite complex

Engineering Contradiction:
Improveconfiguration model accuracyVSAvoiddevice resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent creates a copy of the configuration data structure at a specific time instant (auxiliary configuration data structure) rather than maintaining a continuously synchronized detailed model. This copy captures the essential state information needed for historical analysis without requiring the overhead of continuous model synchronization, thereby reducing resource consumption while maintaining accuracy for the specific purpose of tracking configuration changes over time.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent extracts only the necessary configuration information at a specific time instant into an auxiliary configuration data structure, rather than maintaining a complete and detailed model of all device aspects. This extraction approach captures the essential configuration state needed for historical tracking while eliminating unnecessary model complexity and associated resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If the list of change descriptors becomes inconveniently long, then the update process is triggered, but this requires freezing the configuration and stops further changes during the update

Engineering Contradiction:
Improveconfiguration maintenance efficiencyVSAvoidconfiguration change continuity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent segments the configuration tracking into a static auxiliary configuration data structure (capturing state at a specific time) and a dynamic list of change descriptors (recording subsequent changes). This segmentation allows the system to maintain a manageable auxiliary structure that triggers updates only when necessary, while changes can continue to be recorded in the change descriptors list without requiring the entire system to be frozen.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables continuity of useful action by allowing configuration changes to be continuously recorded in the change descriptors list even when the auxiliary configuration data structure is being updated. The system can append changes to the change descriptors without freezing the overall configuration management process, maintaining continuous operation while still performing necessary updates to the auxiliary structure.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentEP3257196B1A method and an appliance for maintaining a configuration data structure
Publication Date: 2020.04.08 CORIANT
  • EP3257196B1 patent drawingFigure 1
  • EP3257196B1 patent drawingFigure 2
  • EP3257196B1 patent drawingFigure 3

AI summary

The invention relates to maintaining a configuration data structure (101) expressing configuration (105) of a device. The configuration is maintained by an operative process making desired changes to the configuration and adding, to the configuration data structure, change descriptors (102) indicative of the changes. When the configuration data structure is updated, an auxiliary process is run in parallel with the operative process. The auxiliary process comprises requesting functional entities of the device to report their configurations (105a) prevailing at an update time instant, and constructing an auxiliary configuration data structure (101b) on the basis of the reported information. The configuration data structure is updated by replacing a portion (103) of the configuration data structure corresponding to the update time instant with the auxiliary configuration data structure. There is no need to freeze the configuration during the update because the auxiliary process is run in parallel with the operative process.