UICC Subscription Profile Management via Selective Data Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for managing subscription profiles in Universal Integrated Chip Cards (UICC) are inefficient, as disabling profiles consumes valuable memory space without securely deleting data, leading to time-consuming re-establishment and increased network traffic during profile re-enablement, and existing deletion procedures result in loss of static profile data.

Innovation Solution

A method for managing subscription profiles in UICC, involving receiving a profile-disabling command, disabling the profile, sending non-static profile data to the local profile assistant, and deleting it without removing the profile issuer security domain, thereby freeing memory space while ensuring data security and facilitating faster profile re-establishment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If the entire profile data is deleted when disabling a subscription profile, then memory space is freed, but all static and non-static profile data is lost requiring complete re-download

Engineering Contradiction:
Improvememory spaceVSAvoidprofile data
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The profile data is segmented into static profile data and non-static profile data. When a profile is disabled, only the non-static profile data is deleted while the static profile data is preserved in the UICC. This segmentation allows selective deletion that frees memory space while maintaining essential profile information for faster re-establishment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The non-static profile data is discarded (deleted) when the profile is disabled to free memory space, but the static profile data is recovered and retained in the UICC. This enables partial recovery of profile information, avoiding the need to re-download complete profile data when re-enabling the profile.

Inventive Principle:
Principle #34Discarding and recovering

2Quantity of substance

If the profile data is completely deleted upon profile disabling, then memory is freed, but re-establishment time increases due to complete re-download requirement

Engineering Contradiction:
Improveavailable memoryVSAvoidprofile re-establishment time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

By segmenting profile data into static and non-static components, the system deletes only non-static data upon profile disabling. This preserves static data in the UICC, enabling faster profile re-establishment by avoiding complete re-download and reducing the time required to re-enable profiles.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If the entire profile including ISD-P is deleted, then profile data is removed, but security domain structure is disrupted and re-establishment is complex

Engineering Contradiction:
Improveprofile data removalVSAvoidprofile management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system segments the profile structure into the Profile Issuer Security Domain (ISD-P) and profile data components. When disabling a profile, only the profile data is deleted while the ISD-P structure is preserved. This maintains the security domain architecture integrity and simplifies re-establishment procedures compared to complete ISD-P deletion.

Inventive Principle:
Principle #1Segmentation

4Loss of time

If non-static profile data is retained in disabled profiles, then data is preserved for faster re-enablement, but valuable memory space is consumed

Engineering Contradiction:
Improveprofile re-enablement speedVSAvoidmemory space usage
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The system segments profile data into static and non-static components and applies different retention policies: non-static profile data is deleted when profiles are disabled to free memory space, while static profile data is retained. This segmentation enables optimal balance between memory utilization and re-enablement speed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the retention parameter of profile data based on its type: non-static data is set to be deleted upon profile disabling, while static data is set to be preserved. This parameter change optimizes memory space usage while maintaining essential profile information for efficient re-establishment.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3606119B1Method for managing subscription profiles, subscription managing server and uicc
Publication Date: 2021.03.17 GIESECKE & DEVRIENT EPAYMENTS GMBH
  • EP3606119B1 patent drawingFigure 1
  • EP3606119B1 patent drawingFigure 2
  • EP3606119B1 patent drawingFigure 3

AI summary

The invention relates to a method for managing subscription profiles in a Universal Integrated Chip Card, UICC, preferably an embedded UICC, included in a terminal device having a local profile assistant, the method comprising the steps of: Receiving a profile-disabling command from the local profile assistant for disabling an enabled subscription profile in the UICC, wherein the subscription profile comprises profile data; Disabling the subscription by the UICC; and Sending at least the non-static profile data to the local profile authority. The invention also relates to an eUICC and a computer-program-product.