Security Module Card Mutual Trust Activation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile device activation methods lack a robust mechanism for establishing mutual trust between the mobile device, security module card, and activation server, which is essential for ensuring the authenticity and integrity of all components involved.

Innovation Solution

A method and system that employs a security module card to verify the activation server and mobile device using shared secret keys and challenges, establishing a three-way mutual trust by encrypting and decrypting challenges, and validating the trust between the security module card and mobile device, which is then communicated to the activation server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a robust mutual trust verification mechanism is implemented among mobile device, security module card, and activation server, then security and authenticity are improved, but system complexity and verification time increase

Engineering Contradiction:
Improvemutual trust verificationVSAvoidverification mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The verification process is segmented into three distinct challenge-response protocols: (1) server verifies card using shared secret key, (2) card mediates verification of server by mobile device using key pair, and (3) mobile device verifies card using encrypted challenges. This segmentation allows each verification step to be independently executed and validated, managing complexity through structured division of the authentication process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The security module card acts as an intermediary that mediates the verification between the mobile device and activation server. The card receives challenges from both parties, performs cryptographic operations, and coordinates the exchange of encrypted values, thereby simplifying the overall trust establishment process by centralizing the verification coordination function.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple challenge-response verification steps are performed, then authentication security is improved, but activation time increases

Engineering Contradiction:
Improveauthentication securityVSAvoidactivation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The shared secret key is pre-established between the security module card and activation server before the activation process begins. This preliminary cryptographic setup allows the subsequent challenge-response verification to proceed efficiently without requiring complex key exchange protocols during the actual activation, reducing time loss while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The verification process maintains continuous cryptographic validation throughout the activation sequence, with each challenge-response step flowing directly into the next without interruption. The server issues challenges, the card processes them continuously, and responses are immediately validated, ensuring that the useful action of verification proceeds without idle time while securing each transition.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentEP2845141B1Method and system for activation
Publication Date: 2018.09.12 ORACLE INT CORP
  • EP2845141B1 patent drawingFigure 1
  • EP2845141B1 patent drawingFigure 2
  • EP2845141B1 patent drawingFigure 3

AI summary

An activation method includes a security module card verifying an activation server using a shared secret key and a first challenge, mediating a verification of the activation server by a mobile device, and encrypting the second challenge using a generated key to obtain an encrypted second challenge. The security module card further transmits the encrypted second challenge and a third challenge to the mobile device. The method further includes receiving an encrypted third challenge from the mobile device, decrypting the encrypted third challenge to obtain a received third challenge, verifying the mobile device based on the received third challenge being equal to the third challenge sent to the mobile device, and sending a validation of mutual trust between the security module card and the mobile device to the activation server.