Container Background Unlock Mechanism for Synchronization Delay
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems cause delays when applications need to synchronize data upon being brought to the foreground after a period of inactivity, as they must decrypt and re-sync large amounts of data, which is inefficient and inconvenient for users.
Innovation Solution
Implementing a background unlock mechanism that allows partial access to application containers without user interaction, using a copied and encrypted container key with a time limit, enabling data synchronization and access while the container is in the background state, and requiring user authentication upon foreground access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the container is fully encrypted when in background state, then security is improved, but data synchronization delay increases when brought to foreground
Solution Approach 1:
The system performs preliminary decryption of the container in the background state before the application is brought to foreground. A background unlock trigger detects when the device transitions to an unlocked state, and the system automatically decrypts the container key and synchronizes data in advance, so that when the user opens the application, the data is already synchronized and no delay occurs.
Solution Approach 2:
The encryption state of the container is made dynamic rather than static. The container transitions between encrypted and decrypted states based on the device's unlock status and background unlock triggers. When the device is unlocked, the container can be automatically decrypted in the background; when the device is locked, the container remains encrypted. This dynamic state management allows the system to balance security and performance.
2Speed
If the container is decrypted in foreground state, then data access speed is improved, but user authentication requirement increases
Solution Approach 1:
The system performs self-service decryption by automatically detecting background unlock triggers and decrypting the container without requiring user authentication. When the device transitions to an unlocked state, the system monitors for background unlock triggers and automatically decrypts the container key, eliminating the need for users to manually authenticate each time they open an application.
Solution Approach 2:
The system performs preliminary decryption actions in the background before the user needs to access the data. By decrypting the container in advance when the device is unlocked, the system prepares the data access environment beforehand, so that when the user opens the application, the data is already decrypted and ready for immediate access without additional authentication steps.
3Productivity
If background unlock is implemented, then synchronization efficiency is improved, but system complexity increases
Solution Approach 1:
The background unlock mechanism uses the existing device unlock functionality and key management infrastructure for multiple purposes. The same key encryption mechanism used for foreground decryption is also utilized for background decryption, and the existing trigger detection system is leveraged to monitor device state changes. This multi-functional approach allows background unlock to be implemented without adding entirely new systems, thereby limiting the increase in complexity.
Data Source
AI summary
Described herein is a system and method of application container access, the method includes performing a foreground unlock on an application container; creating a copy of a container key of the application container; locking the application container; receiving a background unlock trigger; determining whether a background unlock is authorized; performing the background unlock on at least a portion of the application container using the copy of the container key in response to determining the background unlock is authorized; and storing data in the at least a portion of the application container while the application container is in the background unlock.