Secure Element Update Logging Through an Embedded Update Agent
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Secure elements lack the capability to maintain a record of past software updates, necessitating external devices to track and provide this information, which is inefficient and lacks direct accessibility.
Innovation Solution
Implementing an update agent with a log memory on the secure element to store update-related data, including software identifiers and timestamps, allowing direct tracking and retrieval of software updates without external communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If software updates are tracked by external devices, then update history information can be maintained, but the secure element lacks direct access to its own update history and requires constant external communication
Solution Approach 1:
The secure element is equipped with an update agent that autonomously tracks and logs software updates internally. The update agent maintains a log of all software updates performed on the secure element, allowing it to self-report update history without requiring external tracking mechanisms. This self-service approach resolves the contradiction by enabling the secure element to maintain and access its own update history independently.
Solution Approach 2:
The update agent is embedded within the secure element as an internal component. By nesting the update tracking functionality directly inside the secure element rather than relying on external devices, the system enables the secure element to contain and manage its own update history information, eliminating the need for constant external communication while preserving complete update records.
2Reliability
If update tracking is performed externally, then comprehensive update records can be maintained, but system complexity increases due to required external communication and coordination
Solution Approach 1:
The update tracking functionality is extracted from external devices and transferred to the secure element itself through the update agent. By taking out the tracking responsibility from the external system and embedding it within the secure element, the invention maintains reliable update records while simplifying the overall system architecture by eliminating the need for external tracking infrastructure and communication protocols.
3Ease of operation
If the secure element stores update logs internally, then direct access to update history is enabled, but the secure element requires additional memory and processing capabilities
Solution Approach 1:
The update agent implements a streamlined logging mechanism that records only essential update information (such as update identifiers and timestamps) rather than comprehensive detailed logs. This partial action approach enables the secure element to store and retrieve update history internally with minimal additional memory and processing requirements, resolving the contradiction by providing sufficient functionality without excessive resource consumption.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention relates to a method and an update agent for managing software updates on a secure element, which secure element comprises an update agent and an operating system. The method comprises following steps performed by the update agent. In a first step, an installation package is received from an external device. The installation package comprises a software image of a software to be updated onto the secure element. In a subsequent step, update-related data is extracted from the installation package. A software update is performed at the secure element based on the received software image, upon which a log stored on the secure element is updated based on the update-related data.