Mobile SDK Secure Credential Display via Server Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices face security challenges in storing sensitive credentials due to compliance issues with security organizations' standards, and the inconsistent performance of authentication functions across different applications leads to cumbersome and time-consuming development processes.

Innovation Solution

A method using a software development kit (SDK) on a mobile device to transmit an access credential identifier to a processing computer, which initiates an authentication process, receives the main credential and additional data, and displays them securely, shifting the burden of handling sensitive data to compliant systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If applications store sensitive credentials (main credentials and additional data) locally on mobile devices, then users can access credential information for transactions and secure area access, but security compliance requirements become difficult and costly to satisfy

Engineering Contradiction:
Improveaccess to credential informationVSAvoidsecurity compliance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts sensitive credential data (main credentials and additional data) from local application storage and relocates it to a secure server environment. The application on the mobile device no longer stores sensitive data locally but instead retrieves it through secure transmission from the server when needed, thereby achieving both ease of access and security compliance

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a server as an intermediary between the mobile application and the credential data. The server acts as a mediator that securely stores sensitive information and transmits it to the application only when authentication is successful, eliminating the need for the application to store sensitive data locally while maintaining accessibility

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If each application is built by different entities with their own authentication functions, then applications can be independently developed and deployed, but authentication performance becomes inconsistent and development becomes cumbersome and time consuming

Engineering Contradiction:
Improveindependent application developmentVSAvoidauthentication function consistency
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal authentication mechanism through the SDK that can be used across multiple applications from different entities. The SDK provides standardized authentication functions that handle credential verification, main credential retrieval, and additional data transmission consistently across all applications, eliminating the need for each application to implement its own authentication logic

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

Solution Approach 2:

The patent merges authentication functionality into a shared SDK that is common across multiple applications. Instead of having separate authentication implementations in each application, the SDK consolidates authentication logic, credential management, and secure transmission functions into a single reusable component that all applications can utilize

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20240405994A1Secure device information display with authentication using software development kit (SDK)
Publication Date: 2024.12.05 VISA INTERNATIONAL SERVICE ASSOCIATION
  • US20240405994A1 patent drawing
  • US20240405994A1 patent drawing
  • US20240405994A1 patent drawing

AI summary

A method is disclosed. The method can be performed by at least a mobile device comprising a processor, and memory and display coupled to the processor, the memory storing an application comprising an SDK. The method comprises transmitting, by the SDK, an access credential identifier associated with a main credential to a processing computer. The processing computer then initiates an authentication process with respect to a user of the main credential. The processing computer then receives the main credential and additional data associated with the main credential. The method then includes the SDK receives the main credential and additional data from the processing computer. After the SDK receives the data, the main credential and the additional data are displayed on a display of the mobile device via the SDK.