Call Log Resynchronization Using Tie-Breaker Values
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enhanced communication systems, multiple client devices/applications may generate duplicate call logs during network outages, leading to inaccurate information when connectivity is restored, as they lack the means to detect and filter these duplicates.
Innovation Solution
Implementing a mechanism where client devices generate communication records with tie-breaker values to identify individual sessions, allowing for evaluation and filtering of duplicate records after a trigger event, such as a network outage, to provide accurate information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple client devices generate call logs independently during network outage, then each client can maintain local communication records, but duplicate records are created for the same external event
Solution Approach 1:
The system performs preliminary actions by generating unique identifiers for call events before network connectivity is restored. Each client device assigns a unique identifier to each call event it records during network outage, enabling later identification and elimination of duplicate records when synchronization occurs.
Solution Approach 2:
The system implements feedback mechanisms by comparing unique identifiers across multiple client devices during synchronization. When duplicate records are detected through identifier matching, the system provides feedback to remove redundant entries, ensuring call log accuracy is maintained while preventing record proliferation.
2Loss of information
If duplicate call log records are not filtered, then all recorded communication sessions are preserved, but inaccurate call log information is displayed to the user
Solution Approach 1:
The system performs preliminary actions by embedding unique identifiers in each call log record at the time of creation. This preliminary tagging enables accurate identification of duplicate records during synchronization without losing any genuine communication session information.
Solution Approach 2:
The system extracts and removes only the duplicate portions of call log records while preserving the unique communication events. By using unique identifiers to identify duplicates, the system selectively extracts redundant records for removal, maintaining completeness of genuine sessions while eliminating inaccurate duplicates.
3Reliability
If tie-breaker values are generated for each call record, then duplicate records can be identified and filtered, but the system complexity increases
Solution Approach 1:
The system changes parameters by adding unique identifier fields to call log records, which serve as tie-breaker values. This parameter addition enables automatic duplicate detection through simple identifier comparison, achieving high reliability without requiring complex evaluation mechanisms.
Data Source
AI summary
Client devices/applications associated with a subscriber of an enhanced communication system are enabled to generate communication records identifying individual communication sessions along with tie-breaker values such that the records can be evaluated following a trigger event and duplicate records for the same subscriber can be removed in order to provide accurate information to the subscriber when the event is over.