Secure Element Profile Template Version Alignment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The management of templates during the loading, creation, or update of profiles in secure elements often results in version mismatches between the secure element and the remote server, leading to potential errors and malfunctions in profile loading or execution.
Innovation Solution
A method and system for aligning the versions of profile-element templates between a secure element and a remote server by obtaining version information, determining differences, updating the templates as needed, and generating profiles referencing the aligned templates, ensuring that the secure element receives the correct template versions for proper profile processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If profiles are loaded into secure elements using remote personalization infrastructure, then profile loading capability is improved, but version mismatches between secure element templates and server templates occur leading to errors
Solution Approach 1:
The system performs preliminary actions by obtaining version information of templates stored in the secure element before generating and transmitting profiles. This allows the server to verify template version compatibility in advance, preventing version mismatches that would cause profile loading errors.
Solution Approach 2:
The system implements feedback by having the secure element transmit version information of its stored templates back to the server. The server uses this feedback to determine whether to generate profiles based on aligned template versions, ensuring compatibility between server-generated profiles and secure element templates.
2Manufacturing precision
If template versions are aligned between secure element and server, then profile loading accuracy is improved, but additional version checking and updating steps are required
Solution Approach 1:
The system extracts only the version information of templates from the secure element, rather than transferring entire templates. This minimal extraction approach enables version checking and alignment without significantly increasing communication overhead or system complexity.
Solution Approach 2:
The system changes the parameter being transmitted from the entire template content to just the version information (metadata). This parameter change allows for efficient version comparison and alignment while minimizing the complexity of template management operations.
Data Source
AI summary
Disclosed is a method for loading, by a manager, a profile into a memory of a secure element, SE. A profile allows the SE to identify itself to a service. The profile includes a profile element created by reference to a template. A template is identified by an OID identifier, which it keeps despite changes. The manager may transmit an audit request or update the operating system of the SE in order to obtain, in response, a piece of information representative of the version of the template stored by the SE. The manager then identifies any difference in version with the corresponding template it holds. In case of difference, the template of the SE or the template of the manager is updated so as to align their versions. Thus, a profile generated on the basis of this version of the template will be loaded, without malfunction, by the SE.