Multi-Push Authentication for Secure Event Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing information systems face challenges in ensuring the security and safety of information while optimizing technical operations, particularly in preventing unauthorized access through electronic portals.

Innovation Solution

Implementing multi-push authentication techniques across a computing platform that receives event requests from enrolled devices, generates device-specific notifications, and executes commands based on user responses to ensure secure access and execution of events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication methods are used, then ease of operation is improved, but security and reliability deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The authentication process is segmented into multiple independent push notifications sent to different enrolled devices. Each device requires separate user interaction and authentication, dividing the security verification into discrete segments that collectively enhance reliability while maintaining operational simplicity through automated notification delivery.

Inventive Principle:
Principle #1Segmentation

2Reliability

If multiple authentication methods are implemented, then security is improved, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements multi-functional authentication by sending push notifications that can be approved or rejected across multiple enrolled devices. Each device serves multiple purposes: receiving notifications, authenticating users, and providing secure access control. This universal approach enhances security without requiring separate dedicated authentication devices for each method.

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

3Reliability

If security measures are strengthened, then reliability is improved, but productivity deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidproductivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Users pre-enroll their devices and configure authentication preferences in advance. The system stores authentication states and device information beforehand. When authentication is needed, the pre-configured devices receive push notifications immediately, eliminating setup time during critical authentication moments and maintaining high productivity while ensuring security.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If access control is tightened, then security is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system provides self-service authentication where users independently manage their enrolled devices and receive personalized push notifications. Each user's devices automatically receive authentication requests tailored to their specific accounts and permissions. This self-service approach maintains ease of operation by allowing users to authenticate through familiar devices without requiring manual intervention from administrators, while tight access control is enforced through device-specific authentication states.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10855686B2Preventing unauthorized access to secure information systems using multi-push authentication techniques
Publication Date: 2020.12.01 BANK OF AMERICA CORP
  • US10855686B2 patent drawing
  • US10855686B2 patent drawing
  • US10855686B2 patent drawing

AI summary

Aspects of the disclosure relate to preventing unauthorized access to secured information systems using multi-push authentication techniques. A computing platform may receive an event request associated with a group of enrolled devices. The computing platform may load multi-push settings and identify one or more user devices linked to the group of enrolled devices. Then, the computing platform may generate one or more notifications for the one or more user devices, and each notification may be generated for a corresponding user device based on device-specific user account state information. After sending the one or more notifications, the computing platform may generate one or more event execution commands based on prompt response information received from the one or more user devices and may send the one or more event execution commands to an event management computer system, which may execute an event corresponding to the event request.