Secure Element Object Re-instantiation via Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Secure elements face challenges in maintaining existing objects in a functional state when the operating system is updated, as re-instantiating objects requires significant resources and can result in data loss, especially when multiple objects need to be recreated, and remote servers may lack access to relevant packages installed by third parties.

Innovation Solution

A method is introduced that involves creating metadata associated with objects stored in the secure element, which is used to re-instantiate objects in the updated operating system, allowing for automatic re-creation of objects while maintaining or updating dependent data, and ensuring compatibility with the new OS context.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If objects are re-instantiated from packages when the operating system is updated, then new instances can be created in the updated OS context, but significant computing resources and time are consumed

Engineering Contradiction:
Improveobject functionality after OS updateVSAvoidOS update efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by storing metadata about object parameters before the OS update occurs. This metadata includes information about object classes, their parameters, and initial values. When the OS is updated, this pre-stored metadata allows for rapid re-instantiation of objects without needing to re-process the entire package or re-execute complex initialization routines, thus resolving the contradiction between maintaining object functionality and preserving update efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating metadata copies of object definitions and parameter values. Instead of re-creating objects from scratch by loading and processing complete packages, the system copies essential object information into metadata structures that can be quickly instantiated. This copying approach maintains object reliability after OS updates while significantly reducing the computational resources and time required compared to full package re-processing

Inventive Principle:
Principle #26Copying

2Reliability

If a large number of objects are re-created in a secure element, then the secure element can maintain functionality with the updated operating system, but the computing resources of the secure element are significantly depleted

Engineering Contradiction:
Improveapplication functionalityVSAvoidsecure element resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts essential object information from complete package structures and stores only the critical metadata needed for re-instantiation. This extraction process removes unnecessary bloat from the update process, keeping only the essential class definitions, parameter names, and initial values in metadata. When objects need to be re-created after an OS update, this extracted metadata can be quickly processed without the overhead of handling complete packages, thus maintaining application functionality while reducing secure element resource consumption

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary action by pre-processing and storing object metadata in an optimized format before OS updates occur. This metadata includes pre-validated class structures and parameter configurations that can be directly applied during re-instantiation. This preliminary preparation eliminates the need for complex runtime processing during OS updates, reducing the computational burden on the secure element while ensuring applications remain functional

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If remote servers are used to manage secure element content, then remote updates can be performed, but servers may not have access to packages installed by third parties

Engineering Contradiction:
Improveremote management capabilityVSAvoidpackage access management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing the metadata structure to be self-contained and universally applicable to all objects regardless of their origin or the OS version. The metadata format can represent any object class and parameter combination, making it universally compatible across different OS versions and third-party applications. This universal metadata approach allows remote servers to manage secure element content effectively without needing special access to third-party packages, as the metadata captures all necessary information in a standardized format that works across diverse scenarios

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3391209B1Method for managing objects in a secure element
Publication Date: 2021.10.20 THALES DIS FRANCE SA
  • EP3391209B1 patent drawingFigure 1~2
  • EP3391209B1 patent drawingFigure 3~4

AI summary

The invention is a method of managing an object which is represented by a first instance of a class. The first instance is stored in a secure element comprising an initial operating system. The method comprises a step of updating the initial operating system to generate an updated operating system, a step of creating a metadata uniquely associated with the object, said metadata being permanently stored in the secure element and comprising a value of a parameter of said class which has been used to create said first instance. The method comprises a step of re-instantiating the object by generating an updated instance of the class in the updated operating system by using said value to set said parameter of the class, said updated instance representing the object. The re-instantiating step is automatically triggered by the step of updating the initial operating system.