Embedded SIM Data Model Validation for OS Update Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Updates to the operating system of subscriber identity modules, such as SIM cards, can cause compatibility issues with user data, leading to errors and operational problems due to changes in data format or type requirements.

Innovation Solution

Incorporating a data model that defines criteria for user data stored in a separate memory area, with a determination module to check compliance and a processing module to execute predetermined actions if the data does not meet these criteria, ensuring the operating system operates correctly even after updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the operating system is updated to improve functionality or fix bugs, then the operating system's capabilities are improved, but compatibility with existing user data may deteriorate, leading to errors and malfunctions

Engineering Contradiction:
Improveoperating system reliabilityVSAvoiddata format compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by checking data compatibility against the data model before the operating system update is fully applied. The system performs a validation step that detects potential incompatibilities in advance, allowing preventive measures to be taken before the update causes functional failures. This is evident in the update process where the new operating system code is loaded and validated against the data model prior to committing the update.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback through the data model validation mechanism that provides information about compatibility status. The system checks user data against the data model definitions and receives feedback on whether the data conforms to expected formats and structures. This feedback loop enables the system to detect incompatibilities and trigger appropriate error handling or rollback procedures.

Inventive Principle:
Principle #23Feedback

2Reliability

If strict validation of user data against the data model is performed to ensure compatibility, then data quality and system stability are improved, but system complexity increases due to additional validation mechanisms

Engineering Contradiction:
Improvedata compatibilityVSAvoidvalidation mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The data model serves as a preliminary validation framework that defines expected data structures, formats, and constraints before actual data processing occurs. By having the data model prepared in advance with all validation rules specified, the system can perform systematic checks without adding complex runtime validation logic. The data model acts as a template that simplifies the validation process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies self-service through automated validation where the data model automatically checks user data against defined criteria without requiring manual intervention. The validation mechanism is self-contained, using the data model's inherent structure to identify incompatibilities and trigger appropriate responses, reducing the need for complex external validation systems.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3531729B1Configuration of an on-board subscriber identity module
Publication Date: 2022.06.22 IDEMIA FRANCE SAS
  • EP3531729B1 patent drawingFigure 1~4
  • EP3531729B1 patent drawingFigure 5~6

AI summary

The invention proposes an embedded subscriber identity module (2), comprising: a first memory area (Z1) for storing an operating system (OS1); a second memory area (Z2) for storing user data (DT) accessible by the operating system (OS1); a third memory area (Z3) for storing a data model (MD) defining at least one criterion (CT) that the user data (DT) contained in the second memory area (Z2) must satisfy; the embedded subscriber identity module further comprising: a determination module (8) configured to determine whether said user data (DT) conforms to said at least one criterion; and a processing module (10) configured to cause the execution of at least one predetermined action, defined in the data model (MD), if said user data (DT) does not conform to said at least one criterion.