Mobile Push Authentication for Fraud Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current digital security systems lack effective authentication and authorization methods that are burdensome to users, often requiring them to remember information or carry extra devices, making them vulnerable to fraudulent transactions.

Innovation Solution

A system and method that utilizes push-based challenges on mobile devices for real-time authentication and authorization, allowing users to confirm or deny transactions through registered authority devices, providing improved security with minimal time lag and incorporating multifactor authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication methods (passwords, physical devices) are used, then security is provided, but user burden increases requiring memory or extra devices

Engineering Contradiction:
Improveauthentication securityVSAvoiduser burden
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system uses the user's own mobile device to perform authentication functions. The mobile device itself serves as the authentication tool through push notifications and biometric verification, eliminating the need for separate physical authentication devices or complex password management by the user.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The mobile device performs multiple functions including receiving push notifications, storing biometric data, conducting authentication verification, and communicating with the authentication server. This multi-functional approach replaces multiple separate authentication tools with a single universal device.

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

2Reliability

If real-time transaction notification is implemented, then fraud prevention is improved, but system complexity increases

Engineering Contradiction:
Improvefraud preventionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication server acts as an intermediary between the user's mobile device and the transaction system. It receives transaction requests, sends push notifications to the mobile device, verifies biometric authentication, and returns authorization decisions. This intermediary approach centralizes complexity in the server rather than requiring complex client-side implementation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements real-time feedback through push notifications that immediately inform the user of transaction attempts. The user's biometric authentication result is fed back to the server, which then provides authorization feedback to the transaction system, creating a closed-loop real-time verification process.

Inventive Principle:
Principle #23Feedback

3Speed

If push-based challenges on mobile devices are used, then authentication speed is improved, but user attention requirement increases

Engineering Contradiction:
Improveauthentication speedVSAvoiduser attention
Core Design Contradiction:
SpeedVSEase of operation

Solution Approach 1:

The system replaces manual authentication actions (typing passwords, physically handling security tokens) with automated push notifications delivered to the mobile device. The biometric authentication process is automatically triggered and processed, requiring only the user's natural biometric response rather than deliberate mechanical actions.

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

Data Source

PatentUS11832099B2System and method of notifying mobile devices to complete transactions
Publication Date: 2023.11.28 CISCO TECHNOLOGY INC
  • US11832099B2 patent drawing
  • US11832099B2 patent drawing
  • US11832099B2 patent drawing

AI summary

A method including registering an authority device for an account on an auth platform; receiving transaction request from an initiator to the auth platform; messaging the authority device with the transaction request; receiving an authority agent response from the authority device to the auth platform; if the authority agent response confirms the transaction, communicating a confirmed transaction to the initiator; and if the authority agent response denies the transaction, communicating a denied transaction to the initiator.