Network Element Configuration Profiles With Conditional Activation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current configuration management in communication networks is complex and inefficient, particularly with the increasing heterogeneity and complexity of network elements, as existing standardized solutions like Standardized Configuration Profiles and OSS Stored Profiles are not reusable across software versions and require manual reconfiguration, consuming significant processing resources for monitoring and auditing.
Innovation Solution
The method involves receiving configuration profiles with activation conditions on network elements, which trigger parameter value settings only when specific conditions are met, allowing for conditional and automated configuration management across different software versions and network element types, enabling flexible and efficient configuration and monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If standardized configuration profiles are used, then configuration management is simplified for mature functionality, but the solution is not useful for new functionality areas and requires slow standardization processes
Solution Approach 1:
The patent segments configuration profiles into standardized parts (common parameters, data types, relationships) and vendor-specific parts (custom parameters). This allows the standardized portion to provide ease of manufacture while the vendor-specific portion maintains adaptability for new functionality areas without requiring slow standardization processes.
Solution Approach 2:
The patent extracts and separates the vendor-specific configuration parameters from the standardized configuration profile structure. This extraction allows new vendor-specific functionality to be added without affecting the standardized core, resolving the contradiction between standardization benefits and adaptability needs.
2Adaptability or versatility
If OSS Stored Profiles are used, then any network element type can be covered, but profiles are software version specific and require manual reconfiguration after software updates
Solution Approach 1:
The patent implements dynamic versioning and compatibility checking mechanisms that automatically detect software version changes and trigger profile adaptation. This allows configuration profiles to be reused across software versions through automated detection and adaptation, eliminating manual reconfiguration while maintaining broad network element type coverage.
Solution Approach 2:
The patent incorporates feedback mechanisms where the system monitors software version changes and automatically retrieves or adapts appropriate configuration profiles. This feedback loop enables automated configuration management across different software versions, resolving the contradiction between versatility and automation.
3Measurement precision
If manual configuration monitoring is performed, then configuration accuracy can be verified, but significant processing resources are consumed for reading and comparing parameter values
Solution Approach 1:
The patent extracts and stores configuration profile definitions locally at network elements, eliminating the need to continuously read and compare parameter values with centralized storage. This extraction maintains verification accuracy by enabling local validation while dramatically reducing processing resource consumption for monitoring and auditing operations.
Solution Approach 2:
The patent enables network elements to perform self-verification of their configuration against locally stored profiles. This self-service approach maintains measurement precision for configuration verification while eliminating the need for resource-intensive centralized reading and comparison operations.
Data Source
Figure 1
Figure 2A~2B
Figure 2C
AI summary
A technique for configuring a network element in a communication network is presented. A method aspect performed by a network element comprises receiving at least one configuration profile. The configuration profile defines a set of one or more parameters values for one or more associated configuration parameters of the network element as well as one or more activation conditions for the set of one or more parameter values. The network element then determines whether or not the one or more activation conditions for a particular configuration profile are fulfilled. In case the one or more activation conditions are fulfilled, it triggers activation of the parameter value set defined in the configuration profile for the one or more associated parameters.