UICC File Access Optimization via Pre-stored FCP Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for accessing Universal Integrated Circuit Card (UICC) files in User Equipment (UE) are inefficient due to the need for explicit SELECT operations to determine file size and record count, leading to increased initialization times and suboptimal user experience.

Innovation Solution

A mechanism that stores File Control Parameter (FCP) files corresponding to multiple Elementary Files (EFs) in the UICC, allowing direct command execution, such as READ or UPDATE, without performing SELECT and GET RESPONSE commands, and uses these FCP values to perform SFI access during power cycles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If explicit SELECT operations are performed to determine FCP values, then accurate file size and record count information is obtained, but initialization time increases and access efficiency decreases

Engineering Contradiction:
Improvefile size and record count information accuracyVSAvoidinitialization time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-storing FCP values in a database during an initial setup process. Instead of querying FCP values on-demand through SELECT operations, the system performs the selection and storage of FCP values beforehand, so that when actual file access is needed, the information is already available and can be retrieved instantly, thereby eliminating the time-consuming SELECT operations during initialization.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If SELECT operations are performed to retrieve FCP values, then complete file control information is obtained, but access speed and processing efficiency are reduced

Engineering Contradiction:
Improvecomplete FCP information availabilityVSAvoidaccess speed and processing efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent applies copying by creating a copy of the FCP information and storing it in a database separate from the actual UICC file structure. This copy contains all necessary FCP values (file size, record count, record size) and allows the system to access this information through simple database queries rather than performing time-consuming SELECT operations on the UICC files themselves, thereby maintaining complete information availability while significantly improving access speed.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If traditional UICC access methods are used, then compatibility with existing specifications is maintained, but user experience and initialization performance are suboptimal

Engineering Contradiction:
Improvespecification compatibilityVSAvoiduser experience and initialization performance
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent applies the intermediary principle by introducing a database as a mediator between the UE and the UICC file system. This database stores FCP values and allows the UE to access file information through simplified database queries rather than direct SELECT operations on UICC files. This intermediary layer maintains compatibility with existing UICC specifications while dramatically improving initialization performance and user experience by eliminating the need for repeated SELECT operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10802714B2Optimizing access to universal integrated circuit card (UICC) files in a user equipment (UE)
Publication Date: 2020.10.13 SAMSUNG ELECTRONICS CO LTD
  • US10802714B2 patent drawing
  • US10802714B2 patent drawing
  • US10802714B2 patent drawing

AI summary

A method for optimizing access to files in Universal Integrated Circuit Card (UICC) for use in User Equipment (UE) is provided. The method includes transmitting, by UE, to UICC, SELECT command to select master file (MF); receiving, by UE, from UICC, file control parameter (FCP) values of MF; transmitting, by UE, to UICC, SELECT command to select elementary file directory (EF-DIR) based on FCP values of MF; receiving, by UE, from UICC, FCP values of EF-DIR; determining, by UE, application available in UICC listed in EF-DIR based on FCP values of EF-DIR; transmitting, by UE, to UICC, SELECT command to select application directory file (ADF); receiving, by UE, from UICC, FCP values of ADF; reading, by UE, an elementary file control parameter (EF_FCP) file by using a short file identifier (SFI) value included in the FCP values of the ADF; and obtaining, by the UE, contents of the EF_FCP file.