Compressed Code Libraries for Smart Card Memory Optimization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing method of providing smart cards with multiple application code libraries requires excessive non-volatile memory, leading to high costs and complexity for issuers due to the need for multiple card families to accommodate different applications, as each card family must be manufactured and maintained separately.

Innovation Solution

The method involves compressing multiple application code libraries during manufacturing and decompressing them during personalization, allowing a single card family to support various applications, thereby reducing memory requirements and eliminating the need for multiple card families.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple application code libraries are stored in non-volatile memory on smart cards, then the card can support multiple applications, but the memory size and cost increase significantly

Engineering Contradiction:

Improvenumber of applications supportedVSAvoidmemory size

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The code library is divided into multiple segments or partitions stored in non-volatile memory. Only the required segments are loaded into RAM during personalization, allowing the card to support multiple applications while keeping the permanent storage requirement manageable through segmented organization

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system pre-loads only the necessary code library segments into RAM during the personalization phase before the application is activated. This preliminary action ensures that code is available when needed without permanently storing all possible code libraries, resolving the contradiction between supporting multiple applications and maintaining manageable memory size

Inventive Principle:

Principle #10Preliminary action

2Reliability

If multiple card families are maintained to accommodate different applications, then each application has dedicated optimization, but the management complexity and cost for issuers increase

Engineering Contradiction:

Improveapplication compatibilityVSAvoidnumber of card families

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A single card family design is made universal by implementing dynamic code loading capability. The smart card can load different code library segments into RAM depending on which application is activated, allowing one card family to serve multiple applications that previously required separate card families, thereby reducing management complexity while maintaining application compatibility

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If all application code libraries are pre-loaded onto smart cards during manufacturing, then any application can be used immediately, but the memory requirements become excessively large

Engineering Contradiction:

Improveapplication availabilityVSAvoidmemory size

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

During manufacturing, the system performs preliminary actions by organizing and segmenting code libraries in non-volatile memory and preparing the loading mechanism. During personalization, only the specific code segments needed for the activated application are loaded into RAM. This two-stage approach ensures applications are available when needed while avoiding the need to permanently store all possible code libraries

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Code libraries are segmented into manageable portions stored in non-volatile memory. The segmentation allows selective loading of only required segments into RAM during personalization, ensuring application availability without requiring excessive permanent memory storage capacity

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS10509636B2System, method and personalizable portable device in which application code libraries are distributed in a compressed form

Publication Date: 2019.12.17 THALES DIS FRANCE SA

AI summary

A method for manufacturing a personalizable portable electronic device having a 0.libraries as well as a corresponding portable electronic device and personalization system. The method includes a step of storing a plurality of compressed application code libraries in the non-volatile memory a step of determining which application code libraries are not required for applications used on the personalizable portable electronic device, a step of deleting from the non-volatile memory any compressed application code libraries determined to not be required for applications used on the personalizable portable electronic device, and a step of decompressing an application code library required by an application used on the personalizable portable electronic device. Other systems and methods are disclosed.