Service Provider Code Verification for Real-Time Call Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current call validation methods are burdensome and not fast enough to support real-time scam call management, as they often rely on manual operations and lack efficient mechanisms to differentiate between legitimate and illegitimate calls.

Innovation Solution

The proposed solution involves using a service provider code (SPC) linked to a public certificate repository, where a service provider network identifier is determined from a call message, and verified against a verification table to authenticate calls, enhancing call authorization and verification processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional call validation methods are used, then call verification can be performed, but the process is burdensome and not fast enough for real-time scam call management

Engineering Contradiction:
Improvecall validation speedVSAvoidtime required for call verification
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-establishing a verification table that maps service provider network identifiers to service provider codes before calls need validation. This pre-computed mapping enables rapid lookup during actual call verification, eliminating the need for time-consuming real-time validation operations and achieving real-time scam call management.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a simplified copy of the verification process by using pre-computed mappings between service provider network identifiers and service provider codes. Instead of performing complex real-time validation, the system uses these pre-prepared mappings to quickly determine call legitimacy, significantly reducing verification time while maintaining accuracy.

Inventive Principle:
Principle #26Copying

2Ease of operation

If manual operations are used for call validation, then verification can be performed, but the process is burdensome and inefficient

Engineering Contradiction:
Improvecall validation processVSAvoidcall management efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements self-service by enabling the system to automatically perform call validation using pre-established verification tables that map service provider network identifiers to service provider codes. The system autonomously compares extracted network identifiers against the verification table without requiring manual intervention, thereby simplifying the validation process and improving management efficiency.

Inventive Principle:
Principle #25Self-service

3Reliability

If current validation approaches are used, then call verification is possible, but they do not provide real-time scam call management capability

Engineering Contradiction:
Improvecall verification accuracyVSAvoidresponse time for scam detection
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-computing and storing the verification table with service provider network identifier to service provider code mappings before scam detection is needed. This pre-prepared data structure enables instant lookup during call verification, achieving real-time scam detection while maintaining high verification accuracy through the pre-established mapping relationships.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11290592B2Call authorization and verification via a service provider code
Publication Date: 2022.03.29 FIRST ORION CORP
  • US11290592B2 patent drawing
  • US11290592B2 patent drawing
  • US11290592B2 patent drawing

AI summary

One example method of operation may include extracting a calling device telephone number from a received call message, querying a verification table for the calling device telephone number, identifying the calling device telephone number and a corresponding service provider network identifier from the verification table, querying a mapping table for the service provider network identifier, and identifying whether a match between the service provider network identifier and a service provider code exists as an entry in the mapping table.