Certificate Issuer Public Key Updates for eUICC Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Embedded universal integrated circuit cards (eUICCs) cannot successfully download profiles from a Subscription Manager-Data Preparation (SM-DP+) server due to the absence of a certificate issuer public key (CI public key), hindering the bidirectional authentication process.
Innovation Solution
A method and system for updating the CI public key in eUICCs by receiving a patch package containing the necessary CI public key through a Local Profile Assistant (LPA) and Operating System Patch Server (OPS), ensuring timely acquisition and installation of the missing key for successful authentication and profile download.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the eUICC uses a fixed set of CI public keys during manufacturing, then the initial authentication process is simple and reliable, but the eUICC cannot authenticate with SM-DP+ servers that use updated CI public keys
Solution Approach 1:
The patent implements dynamic updating of the CI public key list in the eUICC by receiving update information from the LPA and OPS. The eUICC transitions from a static key set (fixed at manufacturing) to a dynamic key set that can be updated remotely, allowing the authentication system to adapt to new CI public keys while maintaining reliability through verified update processes.
Solution Approach 2:
The patent performs preliminary verification of the update information before applying the update. The eUICC verifies the signature of the update information using an existing trusted CI public key before adding new CI public keys to its list. This preliminary verification action ensures that only authenticated updates are applied, maintaining security while enabling adaptability.
2Reliability
If the eUICC verifies CI public key identifiers against a local list, then authentication security is maintained, but profile downloading fails when the CI public key is not in the list
Solution Approach 1:
The patent implements a feedback mechanism where the eUICC detects when a received CI public key identifier is not in its local verification list, then requests update information from the OPS through the LPA. After receiving and verifying the update, the eUICC adds the new CI public key to its list and retries the profile download. This feedback loop resolves the contradiction by maintaining security verification while enabling successful downloads when keys are updated.
Solution Approach 2:
The patent introduces the LPA and OPS as intermediaries between the eUICC and the SM-DP+ server. When the eUICC cannot authenticate with a CI public key from the server, the LPA mediates by requesting update information from the OPS, which provides the missing CI public key. This intermediary mechanism maintains security through verified updates while enabling profile download success.
3Reliability
If the eUICC requests CI public key updates frequently, then the CI public key list remains current for authentication, but communication overhead and processing time increase
Solution Approach 1:
The patent implements a self-service update mechanism where the eUICC autonomously detects when authentication fails due to a missing CI public key and independently requests the necessary update information from the OPS. The update is triggered only when needed (on-demand), not through frequent scheduled checks. This self-service approach maintains current CI public key information while minimizing unnecessary communication overhead and processing time.
Data Source
AI summary
A method includes receiving, by an embedded universal integrated circuit card (eUICC), first information from a local profile assistant (LPA), where the first information includes a first certificate issuer (CI) public key identifier, and the first CI public key identifier is a CI public key identifier that the eUICC does not have. The method further includes sending, by the eUICC, second information to an OPS, where the second information includes the first CI public key identifier. The method further includes receiving, by the eUICC, a patch package from the OPS, where the patch package includes at least a first CI public key corresponding to the first CI public key identifier. The method further includes updating, by the eUICC, a CI public key of the eUICC by using the first CI public key.