Electronic Card Memory Management for Redundant Application Removal

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Electronic cards with limited memory space are inefficiently utilized when pre-installed with multiple applications providing the same service, leading to unnecessary memory consumption and reduced storage for user data, as users typically use only one application.

Innovation Solution

A method that automatically detects and frees memory space occupied by redundant applications providing identical services, allowing the freed memory to be allocated for other uses, and includes selective access and detection features to ensure only relevant applications are retained.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If multiple applications providing the same service are pre-installed in the memory, then the card is ready for use without user intervention, but the memory space is unnecessarily consumed

Engineering Contradiction:
Improveautomatic readinessVSAvoidmemory space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts and removes redundant application code from the memory. The system detects that multiple applications provide the same service and automatically deletes the code of redundant applications, keeping only one instance. This resolves the contradiction by maintaining automatic readiness while eliminating unnecessary memory consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent discards redundant application code and recovers the memory space it occupied. By identifying duplicate service-providing applications and removing their code, the system recovers valuable memory space that can then be used for storing user data or other applications, thus resolving the memory space waste issue.

Inventive Principle:
Principle #34Discarding and recovering

2Reliability

If the memory space is allocated to multiple competing applications, then service availability is ensured, but the storage capacity for user data is reduced

Engineering Contradiction:
Improveservice availabilityVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts redundant application code from the memory, separating the necessary service functionality from duplicate code. By removing only the redundant portions while keeping one functional instance, the system maintains service availability while freeing up storage capacity for user data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the state of memory allocation by dynamically adjusting which application code is retained and which is removed. Based on detection of service equivalence, the system modifies the memory configuration to keep only necessary code, thereby optimizing the balance between service availability and storage capacity.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If redundant applications are kept in memory, then users have multiple options for the same service, but memory efficiency is degraded

Engineering Contradiction:
Improveapplication selectionVSAvoidmemory efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent extracts and removes redundant application code while preserving the functionality of one representative application. This maintains the adaptability of having service options (through the retained application) while dramatically improving memory efficiency by eliminating duplicate code that was degrading performance.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses a form of copying by retaining one instance of the application code that provides the service, rather than keeping multiple copies. This single copy maintains service functionality while improving memory efficiency, as opposed to storing multiple redundant copies of the same code.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3082042B8Method for managing an electronic card memory
Publication Date: 2017.12.13 IDEMIA IDENTITY & SECURITY FRANCE SAS

AI summary

A method for managing a memory (2) of an electronic card (1) is proposed, the electronic card (1) being capable of executing a first program (P1) and a second program (P2), the method comprising the steps of: • allocation (100) in the memory (2) of a first memory space (D1) accessible by the first program (P1), • allocation (106) in the memory (2) of a second memory space (C2) storing the code of the second program (P2), • detection (112) of a first writing of data on instruction of the first program in the first memory space (D1), • release (114) of the second memory space (C2) in response to the detection (112).