Secure Element Package Update Reference Redirection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for updating executable code in secure elements often result in data loss and require significant bandwidth, as they involve deleting instances linked to the previous package, backing up instance data, and sending it to a remote server for new package installation.

Innovation Solution

A method that loads an upgrade file to create a new package, replaces the reference to the old package with a reference to the new package in the secure element's package list, while keeping the class instance and instance data unchanged, allowing the old package to be disabled or deleted, and ignoring static fields in the upgrade file.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the existing package update method is used (deleting instances and backing up data to server), then the new package can be installed, but data loss occurs and bandwidth consumption increases

Engineering Contradiction:

Improvedata integrityVSAvoidbandwidth consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by creating a reference mapping between the old package and new package before the actual update occurs. The package reference information is prepared and stored in advance, so that when the update happens, the instance data can be directly redirected to the new package without needing to be backed up or transferred, thus preventing data loss and reducing bandwidth consumption.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of a package reference table that mediates between the old package and the new package. This reference table stores the mapping relationship, allowing the system to transition from the old package to the new package while maintaining instance data integrity without direct data transfer, thereby solving both data loss and bandwidth consumption issues.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the existing package update method is used (deleting instances and backing up data), then the new package can be installed, but the update process becomes complex and time-consuming

Engineering Contradiction:

Improvepackage update capabilityVSAvoidupdate process complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by separating the package reference information from the instance data itself. The reference table is segmented as a独立 component that manages package relationships, while instance data remains unchanged. This separation simplifies the update process by allowing reference updates without affecting data integrity, reducing overall system complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent uses copying by creating a reference copy or mapping in the package reference table that points from the old package to the new package. Instead of copying or migrating the actual instance data, a lightweight reference copy is created that redirects to the new package, significantly simplifying the update process while maintaining full adaptability.

Inventive Principle:

Principle #26Copying

3Reliability

If instance data is backed up to remote server during package update, then new package can be installed, but security risks increase due to data transport over network

Engineering Contradiction:

Improvepackage update reliabilityVSAvoidnetwork security threats

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the package reference information from the data transport process entirely. By storing only lightweight reference mappings in the local package reference table rather than transporting actual instance data over the network, the system eliminates the security vulnerabilities associated with network data transmission while maintaining update reliability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies self-service by maintaining the package reference table locally within the secure element. The update process serves itself by using local reference information to redirect instances to the new package without requiring external server intervention for data backup, thereby eliminating network security threats while ensuring reliable updates.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS10430177B2Method for updating a package

Publication Date: 2019.10.01 THALES DIS FRANCE SA

AI summary

The invention is a method of updating a first executable code comprised in a first package in a secure element, a class instance being instantiated from said first package and comprising instance data. The method comprises the following steps:loading in the secure element an upgrade file comprising a second executable code and creating a second package from said upgrade file,changing said first executable code for said second executable code by replacing a reference to the first package by a reference to the second package in a package list stored in the secure element, while leaving the class instance alive and said instance data unchanged.