Network Device Configuration Template Preprocessing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional network device configuration approaches are cumbersome and impractical due to the need for extensive templates that account for various device types and capabilities, lacking scalability and adequate access to external information, leading to inefficient management and potential undesirable configurations.

Innovation Solution

The introduction of preprocessing techniques that provide external information as additional input data to templates through preprocess files, enabling the templating service to dynamically determine device configurations and leverage server-side features without containing server-side code, thus optimizing network device variability and access to external information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional templates are used to account for all different types and capabilities of network devices, then the templates can cover all device scenarios, but the template size and complexity become unmanageable

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

Solution Approach 1:

The patent divides the monolithic template into multiple smaller templates, each handling specific device types or capabilities. Templates can be composed and combined to cover various device scenarios without requiring a single large template, thus reducing individual template complexity while maintaining overall device coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a universal template framework that can be applied across different device types. By defining common template structures and parameters that can be reused and customized, the system achieves versatility without proportionally increasing template complexity for each device type.

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

2Adaptability or versatility

If templates contain extensive logic to handle all device variations, then all device scenarios can be addressed, but the templates become difficult to maintain and update

Engineering Contradiction:
Improvedevice scenario coverageVSAvoidtemplate maintainability
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

By segmenting device-specific logic into separate templates, the patent reduces the logic burden on each individual template. This segmentation makes templates easier to maintain and update, as changes to one device type do not require examining or modifying other templates, while still achieving comprehensive device scenario coverage through template composition.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If templates require extensive user input to specify all necessary information, then accurate device configurations can be generated, but the configuration process becomes time-consuming and impractical

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by automatically gathering device information from external sources and pre-configuring template parameters before the actual configuration process. This preliminary data collection and template preparation reduces the need for extensive user input during configuration, maintaining accuracy while significantly reducing configuration time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where template rendering results are validated and used to refine future template configurations. By learning from configuration outcomes and device responses, the system reduces the need for manual specification of all parameters, achieving accurate configurations with less user input over time.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If templates are updated frequently to accommodate new device capabilities, then device variability can be addressed, but template stability and reliability decrease

Engineering Contradiction:
Improvedevice capability coverageVSAvoidtemplate stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

By segmenting templates into modular, device-type-specific units, the patent isolates changes to individual templates rather than requiring system-wide template updates. This segmentation allows new device capabilities to be addressed by adding or modifying specific templates without affecting the stability of other templates, thus maintaining overall template reliability while improving adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The universal template framework provides stable, reusable structures that can accommodate new device capabilities through parameter customization rather than template restructuring. This universality maintains template stability while enabling adaptability to new device types through configuration rather than code changes.

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

Data Source

PatentUS11770299B2Systems and methods for preprocessing automated network device configuration generation templates
Publication Date: 2023.09.26 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11770299B2 patent drawing
  • US11770299B2 patent drawing
  • US11770299B2 patent drawing

AI summary

Systems and methods are provided for receiving a template usable to generate a configuration for at least one network device. A specification in a preprocess file can be interpreted to request at least one server-side feature to be used for the template. Data can be received from a server based on the interpreting the specification. The data can be provided to the template. The template can reference the data when generating the configuration.