UICC Subscription Profile Management via Component Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for managing subscription profiles in Universal Integrated Chip Cards (UICC) require complete deletion of profiles, leading to loss of update information and increased network traffic when re-establishing profiles, and do not efficiently manage memory space or ensure consistency of profile versions over time.

Innovation Solution

A method for managing subscription profiles that differentiates between static and non-static components, allowing for selective disabling and transfer of non-static components during the profile-disabling process, enabling efficient memory management and version consistency by sending the non-static component to the server, which can then be used to restore the profile upon re-enabling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If complete deletion of subscription profile is performed, then memory space is freed for other purposes, but update information is lost and network traffic increases when re-establishing profile

Engineering Contradiction:
Improvememory spaceVSAvoidupdate information
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The subscription profile is segmented into static components (profile structure, security elements) and non-static components (update information, application data). When a profile is disabled, only the non-static component is extracted and transferred to the server, while the static component remains in the UICC. This segmentation allows memory space to be freed while preserving update information for future restoration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The non-static component containing update information is extracted from the subscription profile during the disabling process. This extracted data is transferred to the server and stored separately. The extraction principle enables selective removal of only the necessary data for profile restoration, leaving the UICC memory available for other purposes while preventing information loss.

Inventive Principle:
Principle #2Taking out (Extraction)

2Quantity of substance

If complete deletion of subscription profile is performed, then memory space is freed for other purposes, but profile re-establishment time increases due to piece-by-piece loading

Engineering Contradiction:
Improvememory spaceVSAvoidprofile re-establishment time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The non-static component containing all update information is extracted and transferred to the server in advance during the profile disabling process. When the profile needs to be re-established, the server can provide the complete non-static component in a single operation rather than requiring piece-by-piece loading, significantly reducing re-establishment time.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If subscription profile is disabled instead of deleted, then update information is preserved, but memory space is not freed for other purposes

Engineering Contradiction:
Improveupdate informationVSAvoidmemory space
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The non-static component is extracted from the profile and transferred to the server during the disabling process. This extraction frees the memory space in the UICC while the extracted data is safely stored on the server. The profile can be restored later by transferring the non-static component back, thus preserving update information without occupying UICC memory.

Inventive Principle:
Principle #2Taking out (Extraction)

4Quantity of substance

If subscription profile is deleted, then memory space is freed, but profile version consistency cannot be ensured for long-term enabled profiles

Engineering Contradiction:
Improvememory spaceVSAvoidprofile version consistency
Core Design Contradiction:
Quantity of substanceVSStability of the object's composition

Solution Approach 1:

The server acts as an intermediary that stores the non-static component containing update information. For long-term enabled profiles, the server maintains the latest version of the non-static component, ensuring version consistency. When profiles need to be disabled or restored, the server provides the correct version, preventing inconsistencies that would arise from complete deletion and re-download scenarios.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3606117B1Method for managing subscription profiles, subscription managing server and uicc
Publication Date: 2021.10.06 GIESECKE & DEVRIENT EPAYMENTS GMBH
  • EP3606117B1 patent drawingFigure 1
  • EP3606117B1 patent drawingFigure 2
  • EP3606117B1 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, the method comprising the steps of: Receiving a profile-disabling command from a server for disabling an enabled subscription profile in the UICC, wherein the subscription profile comprises a static component and a non-static component; Disabling the subscription profile by the UICC; and Sending a profile-disabling command response to the server, wherein this response includes the non-static component of the disabled subscription profile. The invention also relates to a method for managing subscription profiles in subscription managing server, preferably a subscription manager secure routing server. The invention also relates to a subscription managing server, an eUICC and a computer-program-product.