Unified Multi-Channel Authentication Policy Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current multi-factor authentication systems across different channels in call centers are standalone and lack seamless integration, making it difficult to leverage previous authentication results and maintain state consistency, leading to inefficiencies and increased costs.

Innovation Solution

A method for generating and implementing a real-time multi-factor authentication policy across multiple channels using a smart decision engine that maps authentication flows to scenarios, enabling the combination of various authentication methods and providing a unified authentication result while detecting fraudulent activity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple standalone authentication vendors and service channels are used, then authentication coverage is improved, but system complexity and integration difficulty increase

Engineering Contradiction:
Improveauthentication coverageVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines multiple standalone authentication vendors and service channels into a unified authentication system. The centralized authentication server aggregates authentication methods from multiple vendors and coordinates authentication across IVR, mobile, and other channels, eliminating the need for separate integrations with each vendor and channel while maintaining comprehensive authentication coverage.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The authentication system is designed with universal functionality to work across multiple service channels (IVR, mobile, web) and integrate with multiple authentication vendors simultaneously. The system provides a single authentication framework that can adapt to different channels and vendors, making the system multi-functional without requiring separate implementations for each.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of operation

If each service channel maintains separate authentication state, then channel independence is preserved, but information sharing and cost efficiency deteriorate

Engineering Contradiction:
Improvechannel independenceVSAvoidauthentication result sharing
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent introduces a centralized authentication server as an intermediary between different service channels. This server maintains the authentication state and shares authentication results across channels. When a user authenticates through one channel, the result is stored centrally and can be leveraged by other channels, enabling information sharing while preserving channel independence for user interactions.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If authentication is performed manually by live agents, then flexibility is improved, but productivity and fraud detection capability deteriorate

Engineering Contradiction:
Improveauthentication flexibilityVSAvoidauthentication efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements automated authentication systems that perform authentication without requiring live agents. The system uses automated voice recognition, biometric verification, and multi-factor authentication methods to independently verify user identities. This self-service approach dramatically improves productivity by handling authentication automatically while maintaining flexibility through multiple authentication methods.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual authentication processes performed by live agents with automated electronic authentication systems. Instead of human agents manually verifying identities, the system uses automated biometric recognition, database verification, and algorithmic decision-making to perform authentication, thereby increasing efficiency and enabling better fraud detection through consistent automated processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If multiple authentication factors are used, then security is improved, but authentication time and user friction increase

Engineering Contradiction:
Improvesecurity strengthVSAvoidauthentication duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements dynamic authentication that adapts the number and type of authentication factors based on the specific situation. The system assesses risk levels, user history, and transaction context to determine the appropriate authentication strength. For low-risk transactions, fewer authentication factors are required, while high-risk transactions trigger additional verification steps, thereby optimizing security without unnecessarily increasing authentication time for all users.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11743288B2System and method for generating and implementing a real-time multi-factor authentication policy across multiple channels
Publication Date: 2023.08.29 NICE LTD
  • US11743288B2 patent drawing
  • US11743288B2 patent drawing
  • US11743288B2 patent drawing

AI summary

Systems and methods for generating and implementing a real-time multi-factor authentication policy across multiple channels, are configured to: during a pre-authentication stage: receive, via a user interface, information defining one or more scenarios; receive, via the user interface, information defining one or more authentication flows; for each of the one or more scenarios, map one of the one or more authentication flows to a given scenario; and generate a multi-factor authentication policy associated with each of the one or more scenarios; and during a real-time authentication stage: upon receiving an interaction, identify, by a decision engine, a relevant scenario of the one or more scenarios; implement, by the decision engine, the multi-factor authentication policy associated with the relevant scenario; and determine, by the decision engine, an authentication result.