Unwanted Caller Identification via Synchronized Address Book Database

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing caller ID and message sender identification methods fail in restricted communication environments where APIs are inaccessible, and devices or applications do not allow programmatic access to call and message logs, or replacement of default caller ID services, making it difficult to identify and notify users of unwanted callers and message senders.

Innovation Solution

A method that utilizes the communication device's default caller ID service by storing and updating a separate database of unwanted caller and message sender information, which uses phone numbers, email addresses, or social network user names as unique identifiers, and synchronizes with the device's address book, allowing for automatic notification of unwanted contacts even if they are not stored in the user's personal contacts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a separate database of unwanted caller information is stored and synchronized with the device's address book, then unwanted callers can be automatically identified and notified, but the device complexity increases due to additional storage and synchronization mechanisms

Engineering Contradiction:

Improveunwanted caller identification accuracyVSAvoiddatabase storage and synchronization complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a separate unwanted caller database that mirrors the structure of the device's address book, allowing independent storage and management of unwanted contact information without modifying the original contacts database. This copying approach enables automatic identification while maintaining structural simplicity.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent segments the contact management system into two independent databases: the original address book and the separate unwanted caller database. This segmentation allows the unwanted caller identification function to operate independently without affecting the main contact management system, reducing overall system complexity.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If the default caller ID service is utilized without replacement, then compatibility with restricted devices is maintained, but the ability to provide enhanced caller identification services is limited

Engineering Contradiction:

Improvecompatibility with restricted devicesVSAvoidcaller identification information

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary unwanted caller database that bridges the gap between restricted devices' default caller ID service and enhanced spam identification needs. The database acts as a mediator, allowing the default service to function while adding unwanted caller detection capabilities without requiring service replacement.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent performs preliminary action by pre-populating and synchronizing the unwanted caller database before calls occur. This advance preparation ensures that when calls come in, the device can immediately check against the pre-synchronized database, providing enhanced identification without modifying the default service flow.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If call and message logs are accessed programmatically, then real-time unwanted caller detection is possible, but access restrictions prevent this in many devices and applications

Engineering Contradiction:

Improvereal-time unwanted caller detection speedVSAvoidaccess to call and message logs

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The patent performs preliminary synchronization of the unwanted caller database with the device's address book before call events occur. This advance preparation allows real-time detection during calls without requiring access to call logs, as the identification data is already prepared and available.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The unwanted caller database is designed to be self-synchronized with the device's address book using available device interfaces. The system serves itself by utilizing public APIs for address book access without requiring privileged access to restricted call and message logs, making it compatible with devices that have limited accessibility.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS10080112B2Unwanted caller and message sender identification for restricted communication devices

Publication Date: 2018.09.18 HIYA INC

AI summary

Method for enabling unwanted caller notifications or unwanted message sender notifications for all communication devices and applications including those with restricted programmatic call and message log access. The method delivers and stores a database of unwanted caller/message sender identification information in the device default contacts list, which is made available to the device's default caller/message sender identification service and to applications installed on the device. In one embodiment the unwanted caller/message sender identification information database is delivered as a separate synchronized address book, which can include additional unwanted caller notification information, for example the number or type of complaints about a given phone number.