Call Authentication via Header Attestation Signatures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions fail to adequately address unwanted or scam phone calls, particularly those with spoofed information, and do not consider legitimate reasons for initiating calls with spoofed information.

Innovation Solution

The implementation of methods and systems that authenticate information associated with messages, specifically by analyzing header data to determine the authenticity of sender identifiers, and applying attestation values to generate signatures for updated messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service providers take action against calls with spoofed information, then unwanted or scam calls are prevented, but legitimate calls with spoofed information are also blocked

Engineering Contradiction:
Improvecall authentication accuracyVSAvoidhandling of legitimate spoofed calls
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system changes the parameter of call handling from binary (block or allow) to multi-level (intercept, allow, or monitor) based on the attestation value. Different attestation levels trigger different actions, allowing the system to differentiate between scam calls and legitimate spoofed calls while maintaining high reliability in blocking unwanted calls.

Inventive Principle:
Principle #35Parameter changes

2Object-affected harmful factors

If all calls with spoofed information are intercepted, then scam calls are reduced, but call throughput and legitimate communication are impacted

Engineering Contradiction:
Improvescam call reductionVSAvoidcall throughput
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

The system applies partial action by intercepting only calls with insufficient attestation values while allowing calls with sufficient attestation to pass through. This selective approach reduces scam calls without unnecessarily blocking legitimate traffic, thereby maintaining higher call throughput while still achieving harmful factor reduction.

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If header data analysis is performed on all calls, then call authenticity is improved, but processing time and network latency increase

Engineering Contradiction:
Improvesender identifier verificationVSAvoidcall setup time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary action by analyzing header data and determining attestation values during the call setup phase before the actual communication begins. This allows authenticity verification to be completed in advance, ensuring measurement precision while minimizing the time impact on the actual call duration.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If intercept criteria are applied to forked calls, then scam call identification is improved, but system complexity increases

Engineering Contradiction:
Improvescam call detectionVSAvoidcall routing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies local quality by implementing intercept criteria at specific termination points in the call routing path rather than uniformly across all routing decisions. Each termination point can independently evaluate calls against intercept criteria, allowing reliable scam detection while distributing system complexity across multiple localized decision points rather than centralizing it.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20250175509A1Systems and methods for processing calls
Publication Date: 2025.05.29 COMCAST CABLE COMM LLC
  • US20250175509A1 patent drawing
  • US20250175509A1 patent drawing
  • US20250175509A1 patent drawing

AI summary

Methods and systems are described for authenticating calls. An example method may comprise receiving a message indicative of a call request. Header data associated with the message may be analyzed to determine an attestation value. A signature may be generated based on the attestation value. A signed message comprising the signature and at least a portion of the message may be sent.