Remote Contact List Management via Server Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telephone contact management systems require users to manually manage and transfer contact lists when switching devices and do not efficiently handle changes in telephone numbers, lacking privacy and control over who can contact the user.
Innovation Solution
A remote list of telephone contacts is provided, using unique identifiers like email addresses to store and manage contact information on a server system, allowing users to access and update their contacts independently of their device and maintain privacy, with automatic updates for changed numbers and permission-based access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If contact lists are stored locally on telephone devices, then users have direct access and control over their contacts, but users must manually transfer and update contacts when switching devices or when contact information changes
Solution Approach 1:
The patent introduces a server system as an intermediary between users and their contact lists. The server stores and manages contact information centrally, automatically updating contacts when changes occur. Users access contacts through the server rather than storing them locally, eliminating manual transfer when switching devices while maintaining ease of access through the server interface.
Solution Approach 2:
The system enables automatic detection and updating of contact information changes without requiring user intervention. When a user's contact information changes (e.g., phone number), the server automatically detects this change and updates all associated contact lists, allowing the system to serve itself rather than requiring manual user action.
2Object-affected harmful factors
If telephone numbers are used as contact identifiers, then direct telephone connection is enabled, but users lose privacy control and cannot easily manage who can contact them
Solution Approach 1:
The server acts as an intermediary layer between contact identification and telephone connection. Instead of directly using telephone numbers as contact identifiers, the system uses unique identifiers (such as email addresses or custom IDs) that users can control. When a connection is needed, the server mediates by translating the unique identifier into the appropriate telephone number, preserving privacy while enabling connection.
Solution Approach 2:
The system separates the contact identification function from the connection function. Unique identifiers are used for identification and contact list management, while telephone numbers are used solely for actual connection establishment. This segmentation allows users to control who can identify them in contact lists without exposing their telephone numbers, thereby protecting privacy while maintaining ease of connection when authorized.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
In one implementation a computer-implemented method includes generating a group of telephone contacts for a first user, wherein the generating includes identifying a second user as a contact of the first user based upon a determination that the second user has at least a threshold email-based association with the first user; and adding the identified second user to the group of telephone contacts for the first user. The method further includes receiving a first request to connect a first telephone device associated with the first user to a second telephone device associated with the second user. The method also includes identifying a contact identifier of the second telephone device using the generated group of telephone contacts for the first user, and initiating a connection between the first telephone device and the second telephone device using the identified contact identifier.