Network Contact Database Auto-Configuration via Call Logs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face inefficiencies in manually entering and managing contact information in their contact databases associated with network telephony devices, which is time-consuming and inconvenient.
Innovation Solution
A method and system that allows users to configure their contact databases based on contact information from previously-originated calls, using a network configuration entity that identifies and modifies contact information, enabling users to add, update, or remove entries efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If users manually enter contact information into their contact database, then the contact database can be configured with accurate contact details, but the process becomes time-consuming and inconvenient
Solution Approach 1:
The system performs preliminary actions by automatically capturing contact information from call logs before the user needs to add contacts. The network configuration entity retrieves calling party information, called party information, and call details in advance, preparing the contact data ready for user confirmation without requiring manual entry at the time of contact addition.
Solution Approach 2:
The system enables self-service by automatically generating contact database entries using information from the telephony system itself. The network configuration entity autonomously extracts contact details from call records and presents pre-configured contact entries to the user for approval, allowing the system to serve itself in gathering and organizing contact information without manual intervention.
2Loss of information
If users manually enter all contact details, then complete contact information can be stored, but the complexity of the process increases
Solution Approach 1:
The telephony system performs multiple functions: it not only handles call routing and communication but also automatically gathers contact information, formats it into database entries, and manages contact database updates. The network configuration entity serves as a multi-functional component that bridges telephony operations and contact management, eliminating the need for separate manual data entry processes.
Solution Approach 2:
The system merges the call management function with contact database management. By combining these previously separate functions, the system uses the same infrastructure and data streams (call logs, signaling information) to automatically populate and update the contact database, reducing overall system complexity while maintaining information completeness.
3Reliability
If the contact database is updated frequently with new contacts, then the database remains current and useful, but the time and effort required for maintenance increases
Solution Approach 1:
The system enables continuous updating of the contact database by automatically processing call information as it occurs. Each call generates or updates a contact entry, ensuring the database continuously reflects current contact information without requiring periodic manual updates. The network configuration entity maintains an ongoing process of information gathering and database synchronization.
Solution Approach 2:
The system implements feedback by using call information to automatically update the contact database, which in turn provides accurate contact details for future calls. The network configuration entity creates a feedback loop where telephony usage patterns continuously refine and update the contact database, improving its reliability over time while requiring minimal user intervention.
Data Source
AI summary
A method implemented by a network entity that comprises identifying contact information associated with a previously-originated call, receiving from a user information indicative of a desired modification to a database associated with the user, wherein the desired modification involves the contact information associated with the previously-originated call. The method further comprises configuring the database associated with the user at least in part on the basis of the desired modification and the contact information associated with the previously-originated call.