Smart Card Execution Space Segmentation for Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Smart cards with limited hardware and software resources face security issues due to all applications being executed within the same execution space, leading to unnecessary security measures and resource wastage, as applications with different security requirements share the same environment.

Innovation Solution

Implementing two distinct execution engines within separate Java Cardâ„¢ virtual machines, allowing each application to be executed in a dedicated execution space with tailored security measures based on its specific needs, thereby isolating access to critical resources and optimizing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all applications are executed within the same execution space governed by the same security rules, then security measures are uniformly applied, but card resources are wasted on redundant security computations for applications that do not require high security

Engineering Contradiction:
Improvesecurity levelVSAvoidcard performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the single execution space into multiple distinct execution spaces (first execution space and second execution space), each with its own execution engine. This segmentation allows applications to be distributed across different execution spaces based on their security requirements, enabling differentiated security measures without impacting all applications uniformly.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different security measures locally to different execution spaces rather than uniformly across all applications. The first execution space implements extensive safety measures including redundant computation execution and redundant data storage, while the second execution space operates with reduced security measures, optimizing resource usage for applications that do not require high security.

Inventive Principle:
Principle #3Local quality

2Reliability

If extensive safety measures such as redundant computation execution and redundant data storage are implemented for all applications, then security is strengthened, but card resources are consumed unnecessarily for applications that do not require them

Engineering Contradiction:
Improvesecurity levelVSAvoidcard resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the execution environment into multiple execution spaces with different security configurations. This allows resources to be allocated differently across spaces - the first execution space receives extensive security resources including redundant computation and storage, while the second execution space receives minimal security resources, matching actual application needs.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial security measures selectively - extensive safety measures (redundant computation, redundant data storage) are applied only where necessary in the first execution space, while the second execution space operates with reduced measures. This avoids the waste of applying excessive security measures uniformly to all applications.

Inventive Principle:
Principle #16Partial or excessive action

3Device complexity

If a single virtual machine executes multiple Java Card applications, then the execution environment is simplified, but applications with different security requirements cannot be properly isolated

Engineering Contradiction:
Improveexecution environmentVSAvoidsecurity isolation
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the single virtual machine into multiple virtual machines (first virtual machine and second virtual machine), each with its own execution engine and execution space. This segmentation provides proper isolation between applications with different security requirements while maintaining a relatively simple overall structure compared to fully separate hardware environments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces virtual machines as intermediary layers between the physical card hardware and the applications. These virtual machines act as mediators that provide security isolation and resource management, allowing applications to run in isolated execution spaces without requiring complex direct hardware control for each application.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2497055B1Secure portable object
Publication Date: 2018.07.18 THALES DIS FRANCE SA
  • EP2497055B1 patent drawingFigure 1~2
  • EP2497055B1 patent drawingFigure 3

AI summary

The invention relates to a secure portable object of the smart card type comprising (a) an object body and (b) a micro-module comprising a processor and at least one memory in which a first application executed by a first execution engine in a first execution space is stored. The invention is characterised in that a second application is further stored in the said at least one memory, where the said second application is executed by a second execution engine distinct from the first execution engine, in a second execution space distinct from the first execution space. The invention particularly applies to smart cards.