Bidirectional Authentication Sequence Code Verification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional authentication methods, such as one-time password (OTP) challenges, are one-sided and do not establish mutual trust, making users vulnerable to fraudulent activities like phishing and impersonation scams. These methods also fail to verify granular actions performed on user accounts.

Innovation Solution

The system establishes bi-directional trust between client and agent users by creating a communication channel for authentication sequence codes. The primary device determines an authentication sequence code, which is then provided to the recipient device. The recipient device generates a candidate authentication sequence code message, which is verified by the system device, updating the verification status and providing a shared trust decision message.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional one-sided authentication methods are used, then the authentication process is simple, but users are vulnerable to fraudulent activities and mutual trust is not established

Engineering Contradiction:

Improvesecurity against fraudulent activitiesVSAvoidauthentication process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent inverts the traditional authentication model by having both the user and agent verify each other's identities through mutual authentication sequence code verification, rather than only the system verifying the user. This bidirectional verification establishes mutual trust while maintaining operational simplicity through automated code exchange.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The system implements feedback mechanisms where authentication results are communicated back to both parties, and where failed authentication attempts trigger additional verification steps or alerts. This creates a dynamic authentication process that adapts to security needs while maintaining user-friendly operation.

Inventive Principle:

Principle #23Feedback

2Measurement precision

If traditional broad verification methods are used, then the authentication process is straightforward, but granular actions on user accounts cannot be verified

Engineering Contradiction:

Improveverification granularityVSAvoidoperation simplicity

Core Design Contradiction:

Measurement precisionVSEase of operation

Solution Approach 1:

The patent segments the authentication process into distinct phases: initial connection verification, action-specific authentication code generation, and granular action verification. Each phase uses targeted authentication sequences for specific actions (viewing, modifying, deleting data) rather than a single broad verification, enabling precise control while maintaining operational flow.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system performs preliminary authentication verification before allowing specific granular actions on user accounts. Authentication sequence codes are generated and verified in advance for each type of action, ensuring that only authorized operations can proceed while keeping the actual user interactions simple and intuitive.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If unidirectional trust is established, then the authentication mechanism is simple, but users have no assurance of agent identity

Engineering Contradiction:

Improveuser assurance of agent identityVSAvoidtrust establishment mechanism

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements bidirectional authentication where both the user and agent must verify each other's identities using authentication sequence codes. This mutual verification process ensures that users can be certain of the agent's identity while agents can also verify user authentication, creating symmetric trust relationships without significantly complicating the interaction model.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS20250119426A1Systems and methods for establishing shared trust between a primary agent user and recipient client user

Publication Date: 2025.04.10 WELLS FARGO BANK NA

AI summary

Systems, apparatuses, methods, and computer program products are disclosed for establishing shared trust between a client user and an agent user for a current communication. An example method includes providing a logon request for a client user account associated with a client user to a system device. The example method further includes generating a candidate authentication sequence code message using the mobile application in an instance in which the logon request was successfully authenticated and providing the candidate authentication sequence code message to a system device. The example method further includes receiving a shared trust decision message from the system device, wherein the shared trust decision message is indicative of the current communication verification status.