Multi-Channel Authentication via Mobile Provision Token

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile authentication techniques using multiple channels are inadequate for secure access to protected resources, as they rely on manual transfer of token codes and PINs, which can be vulnerable to hacking and require complex multi-factor authentication processes.

Innovation Solution

The proposed solution involves a mobile device generating a provision token for accessing a protected resource using a second device, with encoded transaction data being decoded and signed by the user's private key, ensuring secure authentication across multiple channels without storing sensitive data, thus enhancing security and reducing vulnerability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual transfer of token codes and PINs is used for authentication, then authentication can be performed across multiple channels, but security is compromised and the process becomes complex

Engineering Contradiction:
Improvemulti-channel authentication capabilityVSAvoidsecurity against hacking
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a server as an intermediary that automatically transfers authentication credentials between the mobile device and the access device. The server receives the token code from the mobile device, verifies it with the authentication server, and then provides the verified credentials to the access device without requiring manual user transfer. This intermediary approach maintains multi-channel authentication capability while eliminating the security vulnerabilities of manual transfer.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple authentication factors are required, then security is improved, but the authentication process becomes more complex

Engineering Contradiction:
Improveauthentication securityVSAvoidauthentication process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service authentication where the mobile device automatically performs the authentication process without requiring manual intervention. The device automatically retrieves the token code, verifies it with the authentication server, and transfers the verified credentials to the access device. This automation maintains the security benefits of multi-factor authentication while significantly reducing the complexity of the authentication process for the user.

Inventive Principle:
Principle #25Self-service

3Productivity

If sensitive data is stored for authentication, then authentication can be performed efficiently, but vulnerability to data breaches increases

Engineering Contradiction:
Improveauthentication efficiencyVSAvoiddata breach vulnerability
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts sensitive authentication data from local storage and processes it through the server intermediary. The mobile device stores only minimal identification information, while the actual token codes and credentials are handled by the server during authentication. This extraction of sensitive data from local storage eliminates the vulnerability to data breaches while maintaining authentication efficiency, as the server automatically verifies credentials without requiring repeated local storage access.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8769289B1Authentication of a user accessing a protected resource using multi-channel protocol
Publication Date: 2014.07.01 RSA SECURITY USA LLC
  • US8769289B1 patent drawing
  • US8769289B1 patent drawing
  • US8769289B1 patent drawing

AI summary

A user accessing a protected resource is authenticated using multiple channels, including a mobile device of the user. A user attempting to access a protected resource is authenticated by receiving a request from a mobile device of the user to access the protected resource; receiving a public key from the mobile device of the user; providing a provision token to the mobile device, wherein the provision token is used by the user to access the protected resource using a second device; and confirming the provision token to a provider of the protected resource to authorize the user to access the protected resource. The user then communicates with the provider using a second device to authorize the provisioning token. A transaction signing protocol is also provided.