Incoming Call Authentication Using Separate Device Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional caller ID systems provide limited information to the called party, typically restricted to a 15-character name associated with the calling party's phone number, lacking context about the caller's intentions or interests.

Innovation Solution

Systems and methods that generate context data based on device activities of a calling device, including internet browsing history, application usage, and user inputs, to provide a called device with enhanced information about the caller, enabling personalized and efficient communication experiences.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If conventional caller ID systems are used, then the system is simple and easy to operate, but the information provided is limited to a 15-character name

Engineering Contradiction:
Improveinformation about callerVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by collecting device activity data (browsing history, application usage, user inputs) before the call is established. This allows context data to be prepared in advance and transmitted to the called device, providing comprehensive caller information without adding complexity to the call establishment process itself.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A context data generation system acts as an intermediary between the calling device and the called device. This intermediary collects activity data, processes it into context information, and transmits it separately from the call signal, thereby providing enhanced information without complicating the core telephony system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If context data based on device activities is collected, then personalized communication experiences are enabled, but data processing complexity increases

Engineering Contradiction:
Improvepersonalization capabilityVSAvoiddata processing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the information processing by separating call signaling from context data transmission. Call setup follows conventional protocols while context data (browsing history, application usage, user inputs) is collected, processed, and transmitted as distinct data streams, allowing personalization without complicating the core call handling system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The calling device automatically generates and transmits its own context data without requiring manual input from the user. The system self-services by autonomously collecting device activity information and formatting it for transmission, reducing the operational burden on users while enabling personalized communication.

Inventive Principle:
Principle #25Self-service

3Reliability

If authentication data is verified separately from the call, then call authentication reliability is improved, but communication time is increased

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidcommunication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Authentication data is collected and verified in advance before the call is established. The system performs preliminary authentication checks using device identifiers and activity data, so that by the time the call connects, authentication is already complete or near-complete, minimizing any time delay in the actual communication.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The authentication process runs continuously in the background alongside normal call operations. Rather than pausing call setup for authentication, the system performs verification tasks concurrently, maintaining continuous useful action and reducing the perceived delay for users.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12489843B2Systems and methods for automatically authenticating communications with a calling device
Publication Date: 2025.12.02 NEUSTAR INC
  • US12489843B2 patent drawing
  • US12489843B2 patent drawing
  • US12489843B2 patent drawing

AI summary

Systems and methods for automatically authenticating an incoming call are disclosed. In one implementation a method for automatically authenticating an incoming call includes receiving a call from a calling device. The call includes an identifier associated with the calling device. The method further includes receiving, separately from the call, authentication data associated with a device or a user, determining, using the identifier and the authentication data, that the authentication data is associated with the same calling device that initiated the call, verifying the authentication data, and based on a result of the verification, determining that the call is initiated by an authenticated device or user.