Call Controller Subscriber Record Versioning for Ongoing Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Call controllers in mobile environments face challenges in updating subscriber records without disrupting ongoing calls due to stale data and storage limitations, leading to dropped or interrupted communications, especially in mission-critical scenarios.
Innovation Solution
A method and device for call controllers that assign new version numbers to incoming subscriber records, update existing records based on configuration data, and add new records while maintaining ongoing calls by managing version numbers and storage efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If subscriber records are frequently updated to reflect variable personnel numbers, then data freshness is improved, but call continuity is compromised due to dropped calls during updates
Solution Approach 1:
The system performs preliminary actions by creating a copy of the subscriber database and assigning it a new version number before executing updates. This allows the update process to proceed without affecting ongoing calls that are using the old version, thereby maintaining call continuity while still achieving data freshness.
Solution Approach 2:
The system creates a copy of the subscriber database with a new version number to store updated records. This copying mechanism allows the original database to remain intact and continue supporting ongoing calls, while the new copy accumulates updates that can be applied without disrupting active communications.
2Measurement precision
If subscriber records are updated in real-time, then data accuracy is improved, but system stability deteriorates due to interruptions in ongoing calls
Solution Approach 1:
The system performs preliminary actions by creating a copy of the subscriber database and assigning it a new version number before executing updates. This allows the update process to proceed without affecting ongoing calls that are using the old version, thereby maintaining call continuity while still achieving data freshness.
Solution Approach 2:
The system dynamically manages multiple versions of the subscriber database, allowing different versions to coexist. This dynamic approach enables the system to switch between versions as needed, maintaining stability during updates while ensuring data accuracy through version control.
3Adaptability or versatility
If new subscriber records are added frequently, then system adaptability is improved, but storage efficiency worsens due to accumulation of old records
Solution Approach 1:
The system performs preliminary actions by creating a copy of the subscriber database and assigning it a new version number before executing updates. This allows the update process to proceed without affecting ongoing calls that are using the old version, thereby maintaining call continuity while still achieving data freshness.
Solution Approach 2:
The system discards old subscriber database versions after they have been superseded by new versions. This discarding mechanism frees up storage space while maintaining system adaptability, as the system can still reference historical versions if needed but prioritizes space efficiency by removing obsolete data.
Data Source
AI summary
Based on receiving new subscriber records at a device (e.g., a call controller), or the device being turned on, the device maintains, at a subscriber database, current subscriber records, each associated with a subscriber identifier and a version number. The device receives the new records and assigns a new and different version number thereto. For a new record comprising a respective subscriber identifier, the device: searches the current records for the respective identifier; when a current record having the respective identifier is found, updates the current record based on configuration data obtained from the new record and replaces the number associated with the current record with the new number; and when the respective identifier is not found, adds the new record to the database in association with the new number. The device removes, from the database, all current records associated with a respective number different from the new number.