Secure Element Update Authentication With Block Cipher Package Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing secure element software update systems face challenges in maintaining software integrity and efficiency, particularly in small chip architectures, due to high memory consumption and the lack of optimal authentication and encryption schemes for operating system updates.
Innovation Solution
A method involving a block cipher-based authentication scheme using Message Authentication Codes (MAC) and checksums to generate and verify installation packages, ensuring secure and efficient software updates with reduced hardware footprint.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the GSMA remote provisioning architecture with SCP03t algorithm is used for authentication and encryption, then security and integrity of software updates are ensured, but the number of exchanges between TRE and server increases and performance decreases
Solution Approach 1:
The patent applies preliminary action by pre-computing and caching cryptographic keys and authentication data on the TRE before the actual software update operation. The authentication data is prepared in advance during device manufacturing or initial setup, eliminating the need for time-consuming cryptographic exchanges during the update process itself.
Solution Approach 2:
The patent extracts the authentication and encryption functions from the main update process by using pre-shared keys and authentication tokens that are obtained beforehand. This separates the security verification step from the data transfer step, allowing parallel execution and improving overall update speed.
2Reliability
If existing authentication schemes are used for software updates, then security is maintained, but the memory footprint of the secure element increases
Solution Approach 1:
The patent uses short-lived authentication tokens and session keys that are generated for each update operation and discarded afterward. Instead of storing long-term cryptographic keys and complex authentication algorithms in the secure element, the system uses lightweight, disposable authentication data that minimizes memory requirements while maintaining security.
Solution Approach 2:
The patent creates a simplified copy of the authentication mechanism that operates within the constraints of limited memory. Instead of implementing the full GSMA RSP authentication protocol, a streamlined version using pre-shared keys and lightweight cryptographic operations is used, achieving equivalent security with reduced memory footprint.
3Ease of manufacture
If the secure element is designed for production phase software, then manufacturing simplicity is maintained, but post-production software updates become impossible
Solution Approach 1:
The patent introduces dynamic update capabilities to a traditionally static secure element design. The secure element is configured with a software update agent that can receive, verify, and install updates throughout the device lifecycle. This transforms the rigid production-phase software into a dynamic, upgradable system while maintaining manufacturing simplicity through standardized update protocols.
Solution Approach 2:
The patent designs the secure element with multi-functionality, enabling it to perform both initial software installation during manufacturing and subsequent updates throughout the device lifecycle. The same hardware and basic software infrastructure support both production phase deployment and post-production updates, eliminating the need for separate systems.
4Reliability
If comprehensive authentication and encryption layers are implemented, then security for critical data like operating system updates is improved, but device complexity increases
Solution Approach 1:
The patent segments the authentication and encryption process into distinct, manageable phases: pre-authentication key exchange during manufacturing, authentication token generation before update, and verification during installation. This segmentation allows each phase to use appropriate security measures without overwhelming complexity, making the overall system more manageable and implementable.
Data Source
AI summary
A method, an update agent and an off-card entity are provided for implementing an authentication scheme for providing a software image to a secure element. An installation package includes a package binding function for linking the installation package to the secure element, a manifest, a manifest signature generated using a block-cipher algorithm, and a software image is received at an update agent within the secure element. The update agent implements an authentication and integrity scheme by verifying various signatures contained within the installation package and installing the software image in case of successful authentication and integrity verification.