Declarative Parametric Architecture for Modular Network Software Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing network hardware solutions for adding new features and configurations are costly, time-consuming, and prone to software incompatibilities, leading to operational inefficiencies and potential breakdowns.

Innovation Solution

A declarative parametric language parser generates data structures to combine software components like component data collectors, feature managers, and managed objects within a binary executable file, allowing for independent updates without affecting other components, thus enabling quick and efficient addition of new features and configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If hardware is upgraded to handle increased network capacity, then network capacity is improved, but costs and software incompatibility risks increase

Engineering Contradiction:

Improvenetwork capacityVSAvoidsoftware incompatibility

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent segments software into modular components that can be independently updated and managed. Each software module can be upgraded separately without requiring full system reconfiguration, allowing hardware upgrades while maintaining software compatibility through selective module deployment.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a universal software platform with standardized interfaces and abstraction layers that can accommodate multiple hardware configurations. This multi-functional software architecture allows the same software to run on different hardware generations, reducing incompatibility risks during hardware upgrades.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Productivity

If new software features are added to increase node efficiency, then node efficiency is improved, but validation overhead and bug risks increase

Engineering Contradiction:

Improvenode efficiencyVSAvoidvalidation overhead

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary validation through automated testing frameworks and static analysis tools that check new software features before deployment. Configuration management systems pre-validate software-hardware compatibility, catching potential bugs before they reach production environments.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent incorporates continuous feedback mechanisms including automated monitoring, logging, and performance tracking that detect issues early in the deployment process. Real-time feedback from test environments allows rapid identification and correction of bugs before full system rollout.

Inventive Principle:

Principle #23Feedback

3Productivity

If software is updated to use hardware more efficiently, then hardware utilization is improved, but system downtime and update costs increase

Engineering Contradiction:

Improvehardware utilizationVSAvoidsystem downtime

Core Design Contradiction:

ProductivityVSDuration of action of moving object

Solution Approach 1:

The patent implements dynamic software loading and hot-swapping capabilities that allow software updates without complete system shutdown. Software modules can be dynamically loaded, updated, and unloaded while the system remains operational, minimizing downtime during software updates.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent ensures continuous system operation through redundancy mechanisms and graceful degradation modes. During software updates, backup systems maintain critical functions, and updates are applied incrementally to maintain continuous useful action without complete system interruption.

Inventive Principle:

Principle #20Continuity of useful action

4Productivity

If the number of nodes is increased to meet capacity demands, then network capacity is improved, but operational costs and software compatibility issues increase

Engineering Contradiction:

Improvenetwork capacityVSAvoidsoftware incompatibility between nodes

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent enforces homogeneous software configurations across all network nodes through centralized management and standardized deployment templates. All nodes run compatible software versions with consistent configurations, eliminating compatibility issues while allowing linear scaling of network capacity.

Inventive Principle:

Principle #33Homogeneity

Solution Approach 2:

The patent uses configuration copying and templating systems that automatically replicate proven working configurations across multiple nodes. New nodes inherit validated configurations from existing nodes, ensuring compatibility and reducing manual configuration errors when scaling the network.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS12619448B2Defining architectures using declarative parametric language

Publication Date: 2026.05.05 INFINERA CORP

AI summary

A method is described in which a processor receives a file containing declarative parametric language. The declarative parametric language is parsed by the processor to generate a data structure. Then, within a binary executable file, at least three software components are combined based upon the data structure. The software components include a component data collector, a feature manager, and a managed object. The component data collector is software configured to collect data from at least one of a hardware component and a software component. The feature manager is software configured to selectively obtain first data from at least one component data collector and provide second data to at least one managed object. The managed object is software configured to expose the second data outside of the binary executable file.