Subject-Based Call Notification Filtering System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face challenges in sorting through vast amounts of information across different communication media, with existing systems failing to effectively notify them of specific audio or video communications relevant to their interests, which are typically unidirectional and lack two-way interaction.
Innovation Solution
A system and method that allow users to request notifications for specific audio or video calls based on predefined subjects, using call processors to detect and verify calls through various authentication methods and sources, enabling targeted notifications to be sent only when the call matches the defined subject.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If users receive notifications for all calls made by or to specific entities, then users are kept informed of all communications, but users are overwhelmed by irrelevant information and waste time sorting through unnecessary notifications
Solution Approach 1:
The system applies local quality by filtering notifications based on specific subject criteria. Instead of notifying users about all calls uniformly, the system selectively notifies only when the call subject matches predefined interests (e.g., business calls, personal calls), thereby improving information relevance and reducing time spent sorting through irrelevant notifications
Solution Approach 2:
The notification system is segmented into multiple filters based on different subjects or criteria. Users can define multiple subject categories and the system segments notifications accordingly, delivering only the relevant segments to users based on their interests and reducing the overall information overload
2Loss of information
If the system notifies users of all calls without subject filtering, then users receive complete information, but the system becomes complex in managing and processing all possible notification scenarios
Solution Approach 1:
The system uses preliminary action by having users pre-define their notification preferences and subject interests before calls occur. Users configure their notification criteria in advance, and the system automatically applies these pre-set filters when calls happen, simplifying the real-time processing complexity while maintaining information completeness for relevant calls
Solution Approach 2:
The system introduces an intermediary layer of subject-based filtering between the call detection mechanism and the notification delivery. This intermediary subject filter acts as a mediator that processes call information and selectively passes only relevant notifications to users, reducing the complexity of managing all possible notification scenarios
3Measurement precision
If the system uses multiple authentication methods to verify call entities, then the system accurately identifies call subjects, but the authentication process becomes more complex and time-consuming
Solution Approach 1:
The system applies partial action by implementing authentication methods selectively based on the call scenario and required precision level. Rather than always using the most accurate but time-consuming authentication methods, the system uses appropriate authentication techniques matched to the specific call context, balancing accuracy requirements with processing efficiency
Data Source
AI summary
A user who wants to follow a call made by or to a specific entity (typically a person) sends a request to be notified when the entity makes or receives a call. The call is an audio or video call. The call can be based on a specific subject that the user has identified. When the entity makes or receives a call, a call processor detects that the call has been made. In response to the call, a notification is sent to the user. If the user has defined a subject, the system determines if the call is on the subject. If the call is on the subject, the notification is sent. If the call is not on the subject, the notification is not sent.