Runtime Configuration Management for Heterogeneous AON Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional application-oriented network (AON) systems struggle with managing heterogeneous networks, where multiple versions of applications and configurations evolve over time, leading to challenges in providing appropriate policies and configurations to nodes, which results in complex manual management and potential errors due to the need for manual configuration and monitoring across diverse hardware and software environments.

Innovation Solution

The system employs a configuration management component that includes a configuration distribution and selection component, enabling dynamic selection and deployment of appropriate configurations at runtime based on node capabilities and message traffic, using XML metadata and a rules engine to ensure backward and forward compatibility, and utilizes machine learning and reasoning mechanisms for enhanced performance and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration management is used in heterogeneous AON networks, then administrators can directly control each node, but the complexity and cost of management increases significantly

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service through automated configuration management where the system automatically discovers node capabilities, selects appropriate configurations, and deploys them without manual intervention. The configuration management component autonomously handles heterogeneous nodes by evaluating their capabilities and applying suitable configurations, eliminating the need for administrators to manually manage each node while maintaining configuration accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a configuration management component as an intermediary between administrators and heterogeneous nodes. This intermediary automatically manages configuration distribution by assessing node capabilities and selecting appropriate configurations, thereby reducing management complexity while ensuring reliable configuration deployment across diverse network environments.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple versions of applications and configurations are deployed across heterogeneous nodes, then the system gains flexibility and adaptability, but managing compatibility becomes increasingly difficult

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidversion management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies parameter changes by dynamically evaluating node capabilities and selecting configurations based on matching capability parameters. The system assesses each node's hardware and software parameters, then automatically selects the appropriate configuration version that is compatible with those parameters, enabling flexible multi-version deployment without manual compatibility management.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The configuration management component serves as an intermediary that handles version compatibility automatically. It evaluates node capabilities against available configuration versions and selects compatible pairings, thereby enabling the system to maintain multiple configuration versions across heterogeneous nodes without requiring administrators to manually manage version compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If automated configuration selection is implemented, then deployment efficiency improves, but the system complexity increases

Engineering Contradiction:
Improveconfiguration deployment speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-defining configuration templates and capability profiles before deployment. The system prepares configuration options and node capability criteria in advance, then automatically matches and deploys appropriate configurations without requiring complex real-time decision-making logic, thereby improving deployment efficiency while keeping system complexity manageable.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies segmentation by dividing the configuration management process into distinct modules: capability assessment, configuration selection, and deployment. This modular segmentation allows each component to perform a specific function with clear interfaces, improving overall deployment efficiency while maintaining manageable system complexity through structured organization.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8745179B2Managing multiple application configuration versions in a heterogeneous network
Publication Date: 2014.06.03 CISCO TECHNOLOGY INC
  • US8745179B2 patent drawing
  • US8745179B2 patent drawing
  • US8745179B2 patent drawing

AI summary

A system that enables automatic version provisioning in heterogeneous application oriented network (AON) architectures is provided. Generally, the specification enables appropriate version configurations to be selected at runtime as needed in an AON environment. More particularly, the subject specification describes the ability of a device (e.g., AON node) to perform and/or select a self-configuration operation based upon the environment and the runtime operation. To facilitate message-based runtime instantiation of the appropriate configuration, the system enables network applicable configurations to be pushed to each of the nodes in the AON architecture.