Subscriber Record Versioning in Call Controllers to Preserve Ongoing Calls
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Call controllers in mobile and deployable environments face challenges in updating subscriber records without disrupting ongoing calls due to stale data and limited storage, leading to potential call drops and resource waste.
Innovation Solution
A method and device for call controllers that maintain current subscriber records by assigning new version numbers to incoming records, updating existing records based on configuration data, and adding new records while removing old records to manage storage efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If subscriber records are frequently updated in mobile call controller environments, then data currency is improved, but call integrity deteriorates due to potential call drops
Solution Approach 1:
The system performs preliminary actions by creating a copy of the subscriber record database before updates begin. This backup copy preserves the state during updates, allowing the call controller to switch back to the backup if updates cause call disruptions, thus preventing call drops while enabling frequent updates.
Solution Approach 2:
The patent introduces an intermediary mechanism - a backup database copy that mediates between the need for frequent updates and call stability. During updates, the system can reference or revert to the backup copy, acting as a buffer that protects ongoing calls from update-related disruptions.
2Adaptability or versatility
If subscriber records are updated frequently to reflect variable personnel numbers, then system adaptability is improved, but storage resources are depleted
Solution Approach 1:
The system changes the parameter of database organization by maintaining multiple versions of subscriber records with version identifiers. Instead of storing only current records, it preserves historical versions with metadata, allowing efficient retrieval of any version without duplicating entire database copies, thus managing storage resources while maintaining adaptability.
Solution Approach 2:
The patent segments the subscriber record database into versioned records, where each record is divided into identifiable units with version tags. This segmentation allows selective retention and deletion of specific record versions based on storage availability, enabling the system to adapt to variable personnel numbers while controlling storage consumption.
3Productivity
If subscriber records are updated without version control, then update speed is improved, but record tracking becomes impossible
Solution Approach 1:
The system creates copies of subscriber records with version identifiers during updates. Each update generates a new versioned copy rather than overwriting the original, enabling rapid updates while preserving the ability to track and retrieve any historical version through the version control mechanism.
Data Source
Figure 1
Figure 2
Figure 3
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.