Authentication Token Reader Bias Member Ejection Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing access control systems, such as multi-factor authentication systems, face challenges in preventing the transfer of malicious code when users move between devices, as authentication tokens can inadvertently carry and spread malware.

Innovation Solution

The implementation of an authentication token reader with a bias member that applies an ejection force to the authentication token after use, ensuring it is automatically moved to a non-operative position, thereby isolating it from potential malicious access and preventing unauthorized data access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the authentication token is retained in the authentication token reader during authentication, then the authentication process can be completed, but the authentication token may transfer malicious code from one computer to another

Engineering Contradiction:
Improveauthentication securityVSAvoidmalicious code transfer
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The bias member applies a preliminary ejection force to the authentication token before the authentication process completes, automatically ejecting the token from the reader after use. This preliminary anti-action prevents the token from remaining in the reader where it could potentially transfer malicious code, while still allowing the authentication process to complete successfully.

Inventive Principle:
Principle #9Preliminary anti-action

2Object-affected harmful factors

If the authentication token is automatically ejected after authentication, then malicious access is prevented, but the user must continuously hold the token during authentication

Engineering Contradiction:
Improvemalicious access preventionVSAvoiduser operation convenience
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The authentication token reader incorporates a bias member that automatically ejects the authentication token after the authentication process completes. This self-service mechanism eliminates the need for manual ejection by the user, reducing the risk of malicious access while maintaining ease of operation. The system performs the ejection action autonomously based on the authentication state.

Inventive Principle:
Principle #25Self-service

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

This solution effectively protects authentication data and prevents malicious access by ensuring the authentication token is isolated after the authentication process, enhancing security and reliability in access control systems.

Implementation Method 1

The authentication token reader includes a bias member that applies an ejection force to the authentication token while the authentication token is at the first position

Methodology Applied
Scientific EffectElastic force: Elasticity

Data Source

PatentEP2650816B1User authentication
Publication Date: 2015.07.01 THE BOEING CO
  • EP2650816B1 patent drawingFigure 1
  • EP2650816B1 patent drawingFigure 2A~2C
  • EP2650816B1 patent drawingFigure 3

AI summary

A method includes receiving user input including a user password while an authentication token is retained at a first position in an authentication token receiver of an authentication token reader by an insertion force applied to the authentication token by a user. The authentication token reader includes a bias member that applies an ejection force to the authentication token while the authentication token is at the first position. The method also includes reading authentication data from a memory of the authentication token while the authentication token is retained at the first position by the insertion force applied to the authentication token by the user. The method also includes authenticating the user based on the authentication data.