Device Token Reuse for Application Installation Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of generating and maintaining signed device tokens for improved security in applications is resource intensive, requiring significant CPU, memory, and battery power.
Innovation Solution
A system and method that leverages existing device tokens during application installation by scanning for and validating device tokens associated with previously installed applications, thereby reducing the need for new token generation and associated resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If signed device tokens are generated and maintained for improved security, then security is improved, but resource consumption (CPU, memory, battery power) increases
Solution Approach 1:
The device token is generated in advance during device provisioning or first application installation, before the application needs to use it. The token is stored in the device's secure storage, so when the application needs authentication, the pre-generated token is retrieved and used directly without requiring real-time generation, thus saving CPU and battery resources while maintaining security
Solution Approach 2:
Instead of generating a new signed device token for each application installation, the system creates a copy of the existing validated device token and associates it with the new application. This copying approach eliminates the need for resource-intensive re-generation of tokens while preserving the security properties of the original token
2Reliability
If signed device tokens are generated and maintained for improved security, then security is improved, but device complexity increases
Solution Approach 1:
A single device token is created to serve multiple applications on the same device. Instead of each application requiring its own separate token generation and management process, one universal device token is generated and then associated with multiple applications, simplifying the overall system architecture while maintaining security across all applications
Solution Approach 2:
The patent introduces an intermediary mechanism (the device token stored in secure storage) that mediates between the device and multiple applications. This intermediary handles the authentication function centrally, eliminating the need for each application to implement its own complex token generation and validation logic, thus reducing overall system complexity
3Use of energy by moving object
If device tokens are scanned and validated during application installation, then resource requirements are reduced, but installation time increases
Solution Approach 1:
The device token validation is performed in advance during the application installation process rather than waiting until the application needs to use it. By validating the token beforehand and caching the validation result, the system avoids repeated validation operations, reducing both time and energy consumption during actual application execution
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer device configured to install computer applications is provided. The computer device includes at least one processor in communication with at least one memory device. The at least one processor is programmed to receive a request to install a first application on a user computer device. The at least one processor is also programmed to scan at least one memory device of the user computer device for a device token associated with a second application. Upon detection of the device token, the at least one processor is programmed to retrieve the device token from the at least one memory device of the user computer device. The at least one processor is further programmed to validate the retrieved device token. Upon validation of the device token, the at least one processor is also programmed to install the first application and associate the device token with the first application.