Authentication Correlation System for Reducing Processing Time

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing network-based authentication systems face challenges such as increased processing time, system complexity, and costs due to resource-intensive verification processes, particularly when preventing brute force attacks. Additionally, these systems often require redundant authentication requests, which can decrease security and inconvenience users.

Innovation Solution

The proposed authentication correlation (AC) system uses a computing device to correlate authentication requests across multiple secure systems based on security levels and timestamps. This system determines if a current authentication request meets predefined authentication rules, allowing for reduced authentication factors in subsequent requests and minimizing processing time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multifactor authentication is implemented to prevent brute force attacks, then security is improved, but processing time and computational resources increase

Engineering Contradiction:

ImprovesecurityVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs authentication correlation in advance by storing authentication factors and security levels from previous authentication requests. When a new request arrives, the system checks against stored data to determine if authentication is needed, avoiding redundant verification processes and reducing processing time for subsequent requests.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system applies different authentication requirements to different requests based on their specific characteristics. By evaluating security levels and authentication factors locally for each request against stored historical data, the system provides targeted authentication rather than uniform multifactor authentication for all requests, reducing overall processing time.

Inventive Principle:

Principle #3Local quality

2Reliability

If multifactor authentication is repeatedly requested from users, then security verification is improved, but user convenience and system utilization decrease

Engineering Contradiction:

Improvesecurity verificationVSAvoiduser convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system stores authentication factors and security levels from previous user authentications in advance. When processing new authentication requests, it correlates these with stored data to determine if additional authentication is necessary, thereby reducing the frequency of repeated authentication challenges presented to users and improving convenience.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses its own stored authentication data to automatically evaluate subsequent requests, reducing the need to repeatedly solicit authentication factors from users. The authentication correlation mechanism serves itself by leveraging historical authentication information to make authorization decisions.

Inventive Principle:

Principle #25Self-service

3Reliability

If authentication factors are repeatedly transmitted over the network, then authentication completeness is improved, but security risk increases

Engineering Contradiction:

Improveauthentication completenessVSAvoidsecurity risk

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

Instead of repeatedly transmitting original authentication factors over the network, the system creates and uses copies of authentication data by storing authentication factors and security levels from initial authentications. Subsequent authentication decisions are made by correlating new requests against these stored copies, eliminating the need for repeated transmission of sensitive authentication data.

Inventive Principle:

Principle #26Copying

4Reliability

If authentication correlation across multiple systems is implemented, then security is improved, but system complexity increases

Engineering Contradiction:

ImprovesecurityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The authentication correlation system is designed to handle multiple types of authentication requests (payment processing, portal login, etc.) through a single unified mechanism. By implementing a universal correlation system that stores and evaluates authentication factors across different application types, the patent reduces overall system complexity compared to maintaining separate authentication systems for each application.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12278813B2System architecture and database for context-based authentication

Publication Date: 2025.04.15 MASTERCARD INT INC

AI summary

An authentication correlation (AC) computing device is provided. The AC computing device includes a processor and a memory. The AC computing device receives a first authentication request from a requesting computer device including an account identifier, a first timestamp, and at least one authentication factor, and determines a first security level of the first authentication request. The AC computing device stores the first security level and the first timestamp. The AC computing device is also configured to receive a second authentication request including the account identifier and a second timestamp, determine that the second authentication satisfies an authentication rule based on the account identifier, the second timestamp, and the stored authentication data wherein the rule defines a timeframe and an authentication threshold, and generate an authentication response based on the determination and the authentication rule wherein the authentication response includes an approval indicator.