Push-Based Encryption Code Update for Mobile Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile device encryption mechanisms are vulnerable to breaches, leaving all users of the same software at risk until security updates are installed, as current update methods require user approval and can be delayed, exposing devices to exploitation during this time.
Innovation Solution
A push-based system for updating encryption mechanisms, where a replacement code segment is sent over-the-air to mobile terminals, allowing for automatic dynamic replacement of old encryption algorithms without user approval or recompilation, ensuring continuous security even between updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If client-initiated update requests are used, then users have control over updates, but security vulnerability window increases due to user delay or ignorance
Solution Approach 1:
The system performs preliminary actions by pre-preparing replacement code segments on the server side and pushing them to clients before security vulnerabilities are exploited. The push notification system proactively delivers update information to clients, eliminating the need for users to manually check for and initiate updates, thereby reducing the security vulnerability window while maintaining automated control.
2Reliability
If full software updates are deployed, then security mechanisms are completely refreshed, but update time and data transmission volume increase
Solution Approach 1:
The software update is segmented into specific replacement code segments that contain only the security mechanism changes rather than updating the entire software application. This segmentation allows the system to transmit and install only the necessary security updates, significantly reducing update time and data transmission volume while ensuring security mechanisms are completely refreshed.
Solution Approach 2:
The invention extracts the security mechanism code segments from the full software application and treats them as separate, independently updatable components. By taking out only the security-related code portions, the system can update security mechanisms without requiring full application updates, thereby reducing update time and bandwidth consumption while maintaining security freshness.
3Device complexity
If encryption algorithms are hardcoded in software, then implementation is simple, but security vulnerability affects all users simultaneously
Solution Approach 1:
The encryption algorithm is transformed from a static, hardcoded component into a dynamic element that can be remotely updated. The system maintains a repository of replacement code segments containing updated encryption algorithms, allowing the encryption mechanism to adapt and change over time without requiring software recompilation or reinstallation, thus preventing widespread vulnerability impact while managing complexity through centralized control.
Data Source
AI summary
A method for introducing a replacement code segment over-the-air through a wireless mobile communication network to an existing code resident on a mobile terminal: identifying the mobile terminal from among terminals served through the wireless mobile communication network; sending a push notification through the network to the mobile terminal, the push notification indicative of the replacement code segment ready for downloading; activating a dynamic update module resident in the mobile terminal, in response to the push notification; sending a request for the replacement code segment; downloading the replacement code segment to the mobile terminal; and transferring the downloaded replacement code segment to the dynamic update module for dynamic replacement of a corresponding old code segment within the mobile terminal with the replacement code segment, obviating a need to recompile the existing code.