Pseudonymized Provisioning Token for Secure Device Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods face challenges in providing digital documents securely to mobile devices, particularly in ensuring cryptographically secure authorization and linking to the terminal device.
Innovation Solution
A method for pseudonymously generating a provisioning token involves an issuer service that creates a signed data set using a cryptographic signature key, incorporating a pseudonym and salt value to securely link the token to the terminal device, ensuring authorization and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a provisioning token is created without pseudonymization, then the authorization process is simpler, but the security and privacy protection is reduced
Solution Approach 1:
The patent introduces a pseudonym as an intermediary element that mediates between the requester's identity and the provisioning token. The pseudonym serves as a temporary identifier that allows the token to be linked to the terminal device without exposing the requester's real identity. This intermediary mechanism resolves the contradiction by enabling secure cryptographic operations while maintaining privacy, as the pseudonym can be used for authorization purposes without revealing sensitive personal information.
Solution Approach 2:
The patent segments the authorization process into distinct phases: pseudonym generation, token creation with pseudonym, and subsequent verification. By dividing the process, the system can handle security-sensitive operations (cryptographic signing) separately from identity management operations. This segmentation allows the provisioning token to be created with strong cryptographic security while the pseudonym handles the privacy aspect, thus resolving the contradiction between security and complexity.
2Reliability
If direct linking of provisioning token to terminal device is implemented, then authorization is stronger, but the risk of unauthorized access increases
Solution Approach 1:
The patent applies preliminary action by generating and storing the pseudonym in the terminal device before the provisioning token is created. This pre-established pseudonym serves as a secure foundation that allows the token to be linked to the device without directly exposing the requester's identity. The pseudonym is prepared in advance and can be used for cryptographic operations, thus strengthening authorization while preventing unauthorized access through identity protection.
Solution Approach 2:
The pseudonym acts as an intermediary that enables the provisioning token to be cryptographically linked to the terminal device without creating direct exposure of the requester's identity. This intermediary mechanism allows strong authorization (through cryptographic signing) while mitigating the risk of unauthorized access (by protecting the real identity). The pseudonym can be used for verification purposes without revealing sensitive personal information that could be exploited for unauthorized access.
3Reliability
If pseudonym and salt value are stored in database, then token verification is more secure, but data storage requirements increase
Solution Approach 1:
The patent applies local quality by storing the pseudonym and salt value specifically in the terminal device's local storage rather than in a centralized database. This local storage approach ensures that the verification data remains secure and is only accessible to the authorized device. The pseudonym and salt value are stored with appropriate security measures in the terminal device, providing secure token verification while minimizing unnecessary data storage requirements in centralized systems.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention relates to a method for the pseudonymized generation of a digital provisioning token (170) by an issuing service. The provisioning token (170) entitles the holder to receive the digital document (172) to be issued with an end device (150) and to cryptographically link it to the end device (150) during the issuance process. The method comprises a server (100) of the issuing service receiving a creation request for the creation of the provisioning token (170), identifying the requester using received identification data (186) of the requester, creating the requested provisioning token (170) in the form of a signed data record (602), and sending the provisioning token (170) to the identified requester.