Recommender Server for Entity Search via Communication Logs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing social network-based recommender systems are limited in finding entities outside the user's contact list and rely on the accuracy of user-stored data, leading to unreliable and incomplete search results.
Innovation Solution
A method and system that utilize a communication network to retrieve entities from a central database by analyzing communication session logs of a user's contacts, allowing identification of entities that have been involved in communication sessions, even if not listed as contacts, and providing reliable information by using a central database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If user-stored contact lists and profiles are used as the data source, then the system operates with simple decentralized architecture, but the search results are limited to pre-stored contacts and their veracity depends on user accuracy
Solution Approach 1:
The patent introduces a recommender server as an intermediary between users and the entity database. This server mediates the search process by receiving user requests, querying the entity database, and returning results. The intermediary enables access to comprehensive entity data while maintaining system reliability through centralized verification, resolving the contradiction between search versatility and data veracity.
Solution Approach 2:
The system automatically retrieves and verifies entity information from the centralized entity database without requiring users to manually store or verify contact information. The recommender server autonomously performs data retrieval, filtering, and validation, eliminating the need for users to maintain accurate contact lists while ensuring data reliability through automated processes.
2Quantity of substance
If only contacts stored in user's contact list are considered, then the system maintains simple data storage requirements, but entities outside the contact list cannot be found
Solution Approach 1:
The entity database serves multiple functions: it stores comprehensive entity information, verifies entity existence, provides entity details, and supports search operations. This universal database replaces the need for individual user contact lists and distributed storage, enabling the system to find any entity in the database without requiring users to store contact information locally, thus increasing the number of findable entities while reducing data storage requirements.
Solution Approach 2:
The patent merges the previously distributed contact list storage across multiple user devices into a single centralized entity database. This consolidation combines all entity data into one location, enabling any user to search for any entity without being limited by their personal contact list, thereby dramatically increasing the quantity of findable entities while reducing overall data storage requirements.
3Reliability
If decentralized user profiles are used, then the system operates with distributed architecture, but search reliability depends on individual user data accuracy
Solution Approach 1:
The recommender server acts as an intermediary that centralizes the verification process. Instead of relying on distributed user profiles, the server mediates all entity verification by querying the centralized entity database, ensuring consistent and reliable information across all users while maintaining a manageable system architecture through a single point of verification.
Solution Approach 2:
The patent extracts the verification and data storage function from individual user devices and concentrates it in a centralized entity database. This extraction removes the burden of maintaining accurate entity data from each user's device, centralizing it in a dedicated database that ensures reliability without requiring complex distributed architecture across all user devices.
Data Source
AI summary
A method for enabling a user of a communication network to get information about entities is presented. The entities are classified in an entity database according to a plurality of characteristics, and the user is associated with a list of contacts, each contact being associated with a log of communication sessions the contact has been involved in through the communication network. For each communication session the log includes an indication of parties involved in the communication session.