Caller ID Verification System Using Calling History Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing caller identification systems lack verification mechanisms to ensure the accuracy of displayed caller names, allowing for potential fraudulent changes and a lack of confidence for recipients regarding the authenticity of incoming calls.

Innovation Solution

A system that verifies caller identification name changes by accessing multiple databases, analyzing calling patterns, and using machine learning models to determine the likelihood of name accuracy, providing visual indicators to recipients about the verification status of displayed names.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If caller identification name changes are allowed without verification, then ease of operation is improved, but reliability deteriorates due to potential fraudulent changes

Engineering Contradiction:
Improveease of updating caller identificationVSAvoidaccuracy of caller identification
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary verification actions before allowing caller identification updates. Multiple databases are queried in advance to validate the requested name change, and confidence scores are calculated beforehand to determine whether to approve the update, preventing fraudulent changes before they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where verification results and confidence scores are fed back into the decision-making process. The verification system continuously monitors and adjusts its validation criteria based on patterns detected in incoming update requests, improving reliability while maintaining operational ease.

Inventive Principle:
Principle #23Feedback

2Reliability

If verification mechanisms are implemented, then reliability is improved, but device complexity worsens due to multiple databases and analysis systems

Engineering Contradiction:
Improveaccuracy of caller identificationVSAvoidcomplexity of verification system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The verification system is designed as a universal multi-functional platform that can validate caller identification across different databases and scenarios. The same core verification engine handles multiple types of validation (database queries, pattern analysis, machine learning evaluation), reducing overall system complexity through consolidation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

An intermediary verification system is introduced between the caller identification update request and the final database update. This mediator layer coordinates queries across multiple databases, performs unified analysis, and makes centralized decisions, simplifying the overall architecture by providing a single point of control.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If multiple databases are queried for verification, then measurement precision is improved, but loss of time worsens due to multiple data access operations

Engineering Contradiction:
Improveconfidence score accuracyVSAvoidtime for verification process
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary queries to frequently accessed databases before the actual verification moment. Common validation data is pre-fetched and cached, so that when a caller identification update is requested, the system can quickly retrieve already-prepared verification information rather than querying all databases in real-time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The verification system implements partial querying strategies where not all databases are queried for every update request. Based on the type of change and the caller's history, the system selectively queries only the necessary subset of databases, reducing verification time while maintaining sufficient precision through targeted data access.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11627218B2Caller identification information analyzer
Publication Date: 2023.04.11 T MOBILE US INC
  • US11627218B2 patent drawing
  • US11627218B2 patent drawing
  • US11627218B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for implementing a caller identifier are disclosed. In one aspect, a method includes the actions of receiving, by a server and from a user of a computing device, data indicating a request to update a name that corresponds to a phone number in a caller identification information storage. The actions further include accessing, by the server, a calling history that indicates previous telephone calls of the phone number. The actions further include accessing, by the server, identification data of the user. The actions further include based on the calling history that indicates previous telephone calls of the phone number and the identification data of the user, determining whether to update the caller identification information storage to indicate that the name corresponds to the phone number.