Branded Call Content Delivery for Spoof-Resistant Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing branded calling delivery methods face challenges in securely and efficiently reaching end customers while protecting against illegal spoofing, with STIR/SHAKEN infrastructure being ineffective and complex, and lacking support for the originating side of calls.

Innovation Solution

A method and apparatus that manage call content delivery by receiving pre-call setup messages, identifying enhanced content, and storing it for a time-to-live period, using a content delivery network to securely insert branded assets into call signaling, and ensuring legitimacy through real-time policy compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If STIR/SHAKEN infrastructure is used for branded calling, then authentication and verification protection is provided, but the process complexity and call flow complexity increase tremendously

Engineering Contradiction:
Improveauthentication protectionVSAvoidprocess complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the authentication and verification functions from the complex STIR/SHAKEN infrastructure and implements them as a simplified branded calling service. The service provider manages authentication separately through branded calling profiles, while the call flow itself remains simple and standardized, avoiding the complexity of integrating STIR/SHAKEN directly into every call setup.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a branded calling service as an intermediary layer between the calling party and the called party. This service handles authentication, verification, and asset management separately, allowing standard call flows to proceed without direct involvement of complex authentication protocols. The intermediary manages the complexity behind the scenes while presenting a simple interface to users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If branded calling assets are delivered through complex onboarding and management systems, then security and legitimacy are ensured, but the ease of operation and deployment are reduced

Engineering Contradiction:
ImprovesecurityVSAvoidease of deployment
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent enables self-service deployment of branded calling assets. Service providers can upload and manage their own branded calling profiles, assets, and authentication credentials through simplified interfaces without requiring complex manual onboarding processes. The system automatically handles asset validation, security verification, and integration, making deployment straightforward while maintaining security standards.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If traditional caller ID services are used, then basic call identification is provided, but protection against scam calls and spoofing is insufficient

Engineering Contradiction:
Improvecall identificationVSAvoidprotection against spoofing
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent combines multiple elements - traditional caller ID functionality, branded calling assets, authentication credentials, and verification mechanisms - into a composite branded calling service. This composite approach maintains the simplicity of caller ID display while integrating multiple layers of security and verification, providing both ease of operation and robust protection against spoofing and scam calls.

Inventive Principle:
Principle #40Composite materials

Data Source

PatentUS12627758B2Call enhancement service via in-network branded calling delivery
Publication Date: 2026.05.12 FIRST ORION CORP
  • US12627758B2 patent drawing
  • US12627758B2 patent drawing
  • US12627758B2 patent drawing

AI summary

One example may include receiving a call event message associated with a call from a calling entity at a server, extracting call data from the call event message identifying enhanced content delivery instructions associated with the calling entity, retrieving enhanced call content to include with the call, and providing a portion of the enhanced call content to a call recipient device and a link to additional portions of the enhanced call content.