Mobility Management Entity Configuration Pooling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As telecommunications networks grow in complexity, managing consistency in configuration data across multiple mobility management entities becomes increasingly challenging, especially after software updates, requiring manual configuration of each entity within a pool or group to ensure reliability and user experience.
Innovation Solution
A method where update configuration data is transmitted to a default mobility management entity within a group, which then propagates the changes to other entities, reducing the need for manual interaction and simplifying the distribution of configuration data, with automatic exchange of application parameters like bearer quality-of-service and mobility management counters.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual configuration is applied to each mobility management entity individually, then configuration consistency is ensured, but maintenance effort and operational cost increase significantly
Solution Approach 1:
The patent merges the configuration management functions into a centralized configuration server that serves multiple mobility management entities. Instead of manually configuring each entity separately, a single configuration update is distributed to all entities in the pool, combining multiple configuration operations into one action while maintaining consistency across all entities.
Solution Approach 2:
The configuration server acts as an intermediary between the network operator and the mobility management entities. It receives configuration updates and automatically distributes them to the appropriate entities, eliminating the need for direct manual configuration of each entity while ensuring consistency through centralized control.
2Productivity
If the number of mobility management entities increases to handle network growth, then network capacity improves, but configuration management complexity increases
Solution Approach 1:
The configuration server provides universal configuration management capabilities that can serve any number of mobility management entities in a pool. A single configuration server handles configuration for multiple entities simultaneously, making the system scalable without proportionally increasing configuration management complexity.
Solution Approach 2:
The system creates and distributes configuration copies from a central template to multiple mobility management entities. When configuration needs to be updated, the change is made once and automatically copied to all entities in the pool, eliminating the need to manually recreate configurations for each new entity as the network expands.
3Manufacturing precision
If configuration data is manually updated for each entity, then configuration accuracy is maintained, but time consumption increases
Solution Approach 1:
The configuration server performs preliminary validation and preparation of configuration data before distributing it to mobility management entities. Configuration updates are prepared centrally with proper validation, then distributed automatically, ensuring accuracy is maintained while eliminating the time-consuming manual update process for each entity.
Solution Approach 2:
The system implements feedback mechanisms where mobility management entities report their configuration status back to the configuration server. This allows the server to verify that configuration updates were applied correctly and to track the status of all entities, maintaining accuracy through automated verification rather than manual checking.
Data Source
AI summary
A method for enhanced performance of a telecommunications network includes a first step and/or a second step. The first step includes: the first mobility management entity receives update configuration data; the first configuration data of the first mobility management entity are at least in part replaced or modified by the update configuration data; either the update configuration data or at least part of the updated first configuration data are transmitted to the second mobility management entity; and the second configuration data of the second mobility management entity are at least in part replaced or modified by the update configuration data or by the at least part of the updated first configuration data. The second step includes: upon the second mobility management entity being either restarted and/or updated and/or added to the group of pooled mobility management entities the second mobility management entity receiving startup configuration data from the first mobility management entity, the startup configuration data being part of the first configuration data or being part of the updated first configuration data of the first mobility management entity.