Shared Database for Network Element Configuration Congruence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In data transfer networks, maintaining congruence between different functional entities' configuration systems and managing configuration data traffic is challenging, leading to potential functional issues and significant workload.
Innovation Solution
A database that is writable and readable by each functional entity within the network element facilitates maintaining congruence and data exchange, allowing functional entities to write and read configuration entries, and implement them into their systems, enabling efficient cooperation and resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each functional entity maintains its own configuration system, then the network element can operate with modular functional entities, but the configuration systems of different functional entities may become non-congruent causing functional troubles
Solution Approach 1:
The patent merges the configuration systems of multiple functional entities into a single shared configuration system. The network element maintains one configuration system that is jointly used by all functional entities, eliminating the non-congruence problem while preserving modular operation. Each functional entity reads and writes configuration data to this shared system, ensuring all entities operate with consistent configuration information.
2Adaptability or versatility
If each functional entity maintains its own configuration system, then functional entities can operate independently, but significant configuration data traffic is required between functional entities to maintain congruence
Solution Approach 1:
By consolidating multiple configuration systems into one shared configuration system, the patent eliminates the need for extensive data transfer between functional entities to synchronize configurations. All functional entities access the same configuration data stored in a shared database, reducing configuration data traffic to minimal update notifications rather than continuous data synchronization.
Solution Approach 2:
The shared database acts as an intermediary between functional entities for configuration data exchange. Instead of functional entities directly exchanging configuration data with each other, they all interact with the shared database which manages the configuration information centrally, significantly reducing the data traffic required to maintain congruence.
3Reliability
If a shared configuration system is used by all functional entities, then configuration congruence is maintained, but the complexity of managing the shared configuration system increases
Solution Approach 1:
The shared configuration system is designed to be self-managing through automated mechanisms. When a functional entity writes configuration data to the shared database, the system automatically notifies other functional entities of the changes. The configuration system manages its own synchronization and consistency without requiring complex external management, reducing the perceived complexity for operators.
Solution Approach 2:
The system implements automatic feedback mechanisms where functional entities receive notifications when configuration data changes in the shared database. This feedback loop ensures all entities are automatically synchronized with the latest configuration without manual intervention, simplifying the management of the shared configuration system while maintaining reliability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A network element (201) for a data transfer network comprises functional entities (221-226) each being adapted to maintain an entity-specific configuration system which comprises configuration entries with the aid of which the functional entity under consideration is able to co-operate with the other functional entities so that the network element is capable of operating as a part of the data transfer network. The network element maintains a database that is writeable and readable by the functional entities. At least one configuration entry related to one or more of the functional entities is composed of data items written by many functional entities to the database, and thereafter the relevant one or more functional entities read the configuration entry from the database. The database that is commonly used by the functional entities facilitates maintaining the congruence between the functional entities and reduces the amount of configuration data traffic between the functional entities.