Bidirectional Call History Sync for Voice-Activated Telephony
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a discrepancy between server-based and client-based actions in telephone systems, resulting in incomplete or inaccurate call history records, as the client telephone does not record numbers dialed via voice recognition by the server, leading to misinterpretation of user actions when using redial or scrolling through call history.
Innovation Solution
Implementing synchronization logic between the client telephone and the server to ensure that actions performed by the server, such as voice-recognized calls, are reflected in the client's storage, allowing for a unified and accurate call history, and vice versa, ensuring that client-initiated actions are synchronized with the server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If the server performs speech recognition and dials numbers on behalf of the client telephone, then the server-based services become highly valuable and automated, but the client telephone's call history becomes incomplete and inaccurate
Solution Approach 1:
The server sends feedback messages to the client telephone containing call history information about server-initiated calls. This feedback mechanism ensures that the client's local call history is updated with calls made by the server through voice recognition, resolving the information loss while maintaining automation.
Solution Approach 2:
A synchronization message system acts as an intermediary between the server and client telephone. The server generates synchronization messages containing call details and transmits them to the client, which then updates its local storage. This intermediary mechanism bridges the information gap without reducing server automation.
2Ease of operation
If the client telephone maintains its own independent call history storage, then the client can operate autonomously, but the call history becomes inconsistent when server actions are not reflected
Solution Approach 1:
The system implements feedback loops where the server monitors its actions and sends update messages to the client telephone. This allows the client to maintain autonomous operation while receiving periodic feedback that synchronizes the call history, ensuring consistency without compromising ease of operation.
Solution Approach 2:
The server prepares synchronization messages in advance containing call history information and transmits them to the client telephone proactively. This preliminary action ensures that the client's call history is updated before the user might query it, maintaining consistency while allowing independent operation.
3Loss of information
If the server records all call history information, then the complete history is available centrally, but the client telephone cannot provide accurate redial functionality for server-initiated calls
Solution Approach 1:
The synchronization message system serves as an intermediary that transfers call history information from the server to the client telephone. This allows the client to have access to complete call history information locally, enabling accurate redial functionality for both client-initiated and server-initiated calls while the server maintains its central record.
Solution Approach 2:
The server creates copies of call history information and transmits them to the client telephone. This copying mechanism ensures that the client has a local replica of the complete call history, enabling full redial functionality without relying on server connection, while the server retains the master record.
Data Source
AI summary
Described is a technology by which a storage at a telephone device (e.g., a client telephone) is synchronized with information corresponding to actions performed at a computing device (e.g., a server) on behalf of the client. For example, the server may employ speech recognition to recognize a name or number spoken into the client telephone, and in response, dial out a corresponding telephone number for the client telephone. This action is synchronized back to the client storage so that the client's call history includes knowledge of the server's dialing action. Thereafter, an action at the telephone device that accesses the call history (e.g., for redialing or scrolling) obtains the full call history, independent of whether the telephone device or computing device performed the action. Changes made via telephone device may be similarly synchronized to the computing device, such as directly dialed calls, user-input speed dial information, and so forth.