Profile Management Server Audit for Secure Entity Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current profile management systems for secure entities in mobile communication terminals face desynchronization issues when messages indicating profile activation status are not received, leading to incorrect profile information and potential failures in communicating updates.

Innovation Solution

Implementing an audit procedure triggered by a time counter if no message indicating the active profile is received within a predetermined duration, using APDU GET STATUS commands to determine the actual active profile and synchronize tables.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server relies on receiving confirmation messages from the secure entity to update profile status, then the system operates with simple message exchange, but desynchronization occurs when messages are lost or not received

Engineering Contradiction:
Improveprofile status synchronizationVSAvoidmessage exchange protocol
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The server implements an active feedback mechanism by initiating audit procedures to query the secure entity about its actual profile status. Instead of passively waiting for confirmation messages that may be lost, the server actively seeks verification of the profile status through time-triggered audits, ensuring reliable synchronization despite message transmission failures

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The server performs preliminary actions by establishing time counters and scheduling audit procedures in advance. Before desynchronization can occur, the system proactively initiates status verification through timed audits, preventing the problem rather than reacting to it after message loss

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the server frequently audits the secure entity to verify profile status, then synchronization reliability improves, but network traffic and processing overhead increase

Engineering Contradiction:
Improveprofile status accuracyVSAvoidnetwork communication overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The server implements periodic auditing using time counters that trigger audits at predetermined intervals. This periodic approach balances reliability with resource efficiency by verifying profile status at regular intervals rather than continuously or on every profile modification attempt, reducing unnecessary network traffic while maintaining synchronization

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs audits selectively based on whether a confirmation message was received within an expected time window. Instead of auditing every single profile modification, the system performs partial audits only when needed (when confirmation is missing), reducing overall overhead while maintaining reliability

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3149983B1Profile management method and server
Publication Date: 2018.07.04 IDEMIA FRANCE SAS
  • EP3149983B1 patent drawingFigure 1
  • EP3149983B1 patent drawingFigure 2~3

AI summary

The invention relates to a method implemented by a profile management server (500) for managing the profiles (P1, P2, PROV) of a secure entity. Said method comprises: a step (S25) of sending a message (302) to said secure entity in order to modify the active profile of said entity; a step (V50) of initialising and initiating a time-recording meter (TIM); and in the event that said server (500) does not receive a message indicating the active profile in said secure entity (100) before the expiry of a predetermined period starting from said initiation: a step of initiating an audit procedure (V100) in order to determine the effectively active profile in said secure entity (100).