Security Element Application Loading with Type and Provider Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data transfer mechanisms in secure communication channels, such as those used by smart cards, do not adequately control the nature of applications being downloaded, allowing improper data to be sent, even through secure channels, due to lack of user-specific and provider-specific verification.

Innovation Solution

A method and device for authorizing application loading in security elements that verifies the type and provider of the application using user and provider identifiers, combined with validation information, ensuring only authorized applications are loaded, utilizing cryptographic keys and electronic certificates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If secure communication channels are used for data transfer, then confidentiality and integrity of data are guaranteed, but the nature of the data cannot be controlled before acceptance

Engineering Contradiction:
Improveconfidentiality and integrity of dataVSAvoidimproper data being sent
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by performing verification of the data nature before the actual data transfer and loading into the security element. The remote machine verifies the type and provider information of the application data beforehand, and only after verification succeeds does it proceed to transfer and load the data. This preliminary verification step prevents improper data from being loaded while maintaining secure communication channels.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If application loading is allowed without verification, then ease of operation is improved, but security and trust in data exchange deteriorates

Engineering Contradiction:
Improveapplication loadingVSAvoidsecurity and trust
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements self-service by enabling the security element to autonomously perform verification of application data before loading. The security element itself checks the type and provider information against authorized lists without requiring external intervention or manual user verification. This automated self-verification maintains ease of operation while ensuring security and trust.

Inventive Principle:
Principle #25Self-service

3Reliability

If verification of application type and provider is implemented, then security and trust are enhanced, but device complexity increases

Engineering Contradiction:
Improvesecurity and trustVSAvoidverification mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by implementing a single verification mechanism that handles multiple verification tasks: verifying the type of application data, verifying the provider identifier, checking against authorized lists, and controlling the loading process. This multi-functional verification system enhances security and trust while minimizing the increase in device complexity by consolidating verification functions into one integrated mechanism.

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

Data Source

PatentEP3912065B1Authorization of loading an application in a security element
Publication Date: 2026.02.25 ORANGE SA
  • EP3912065B1 patent drawingFigure 1~2
  • EP3912065B1 patent drawingFigure 3~4

AI summary

The invention relates to a method and device for authorizing the loading of an application (APP) onto a security element (ES) that can communicate with a loading server (SAES) of an application provider. The method is implemented by the security element and comprises the following steps: - obtaining (E0) at least one type of authorized application (APP_tid); - obtaining (E2) the type of application to be loaded (APP_t); - comparing the type of application to be loaded (APP_t) and the type of authorized application (APP_tid); - depending on the results of the comparision, authorizing the loading (E6) of the application.