Device provisioning using partial personalization scripts
US-10235670-B2 · Mar 19, 2019 · US
US12293353B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12293353-B2 |
| Application number | US-202418618895-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 27, 2024 |
| Priority date | May 10, 2013 |
| Publication date | May 6, 2025 |
| Grant date | May 6, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments of the invention relate to systems and methods for efficiently provisioning mobile devices with personalization data. For some embodiments, a method is disclosed comprising receiving a request for provisioning comprising device information for a mobile device and user authentication information for a user, generating a partial personalization script, an activation script, and a deletion script using the device information, sending the partial personalization script, the activation script, and the deletion script to an application provider computer, wherein the application provider computer initiates execution of the partial personalization script on the mobile device, authenticating the user authentication information, and sending an activation message to the application provider computer, wherein the application provider computer initiates execution of the activation script.
Opening claim text (preview).
What is claimed is: 1. A method comprising: sending, by a mobile device, to an application provider computer, a request for provisioning the mobile device, the request including device information for the mobile device, the device information including a secure element identifier and a session identifier, wherein the application provider computer sends the request for provisioning the mobile device to a service provider computer, the service provider computer retrieves a personalization master key associated with the mobile device based on the secure element identifier, generates a personalization session key using a key derivation function, the secure element identifier, the session identifier, and the personalization master key, generates store data commands comprising personalization data, encrypts the store data commands using the personalization session key, generates a partial personalization script using the encrypted store data commands, generates an activation script, encrypts the activation script using the personalization session key, generates a deletion script, and encrypts the deletion script using the personalization session key; receiving, by the mobile device, from the application provider computer, the partial personalization script, the activation script and the deletion script; and executing, by the mobile device, the partial personalization script, including: decrypting the encrypted store data commands using an encryption key that matches the personalization session key; and executing, by the mobile device, at least one of the activation script and the deletion script, including: decrypting at least one of the activation script and the deletion script using the encryption key that matches the personalization session key, wherein execution of the activation script enables the mobile device with access to the personalization data and provisions the personalization data onto the mobile device. 2. The method of claim 1 , further comprising: receiving, by the mobile device, from the application provider computer, an activation message; and executing, by the mobile device, the activation script prior to initiating a transaction using the personalization data, and including: decrypting the activation script using the encryption key that matches the personalization session key. 3. The method of claim 1 , further comprising: receiving, by the mobile device, from the application provider computer, a deletion message; and executing, by the mobile device, the deletion script to delete the personalization data from the mobile device, and including: decrypting the deletion script using the encryption key that matches the personalization session key. 4. The method of claim 1 , further comprising: receiving, by the mobile device, from the application provider computer, the activation script; and executing, by the mobile device, the activation script, thereby provisioning the personalization data onto the mobile device, and including: decrypting the activation script using the encryption key that matches the personalization session key. 5. The method of claim 1 , further comprising: receiving, by the mobile device, from the application provider computer, the deletion script; and executing, by the mobile device, the deletion script to delete the personalization data from the mobile device, and including: decrypting the deletion script using the encryption key that matches the personalization session key. 6. The method of claim 1 , wherein the service provider computer determines that the personalization session key is expired, establishes a new session associated with a new personalization session key, and generates a new activation script using the new personalization session key, and further comprising: receiving, by the mobile device, from the application provider computer, the new activation script. 7. The method of claim 1 , wherein the partial personalization script includes a script operable to store the personalization data on the mobile device in a secured form. 8. The method of claim 1 , wherein the session identifier is a nonce value. 9. The method of claim 1 , wherein the personalization master key is a symmetric encryption key. 10. A mobile device comprising: a processor; a non-transitory computer-readable medium comprising code executable by the processor for implementing operations including: sending, to an application provider computer, a request for provisioning the mobile device, the request including device information for the mobile device, the device information including a secure element identifier and a session identifier, wherein the application provider computer sends the request for provisioning the mobile device to a service provider computer, the service provider computer retrieves a personalization master key associated with the mobile device based on the secure element identifier, generates a personalization session key using a key derivation function, the secure element identifier, the session identifier, and the personalization master key, generates store data commands comprising personalization data, encrypts the store data commands using the personalization session key, generates a partial personalization script using the encrypted store data commands, generates an activation script, encrypts the activation script using the personalization session key, generates a deletion script, and encrypts the deletion script using the personalization session key; receiving, from the application provider computer, the partial personalization script, the activation script and the deletion script; and executing the partial personalization script, including: decrypting the encrypted store data commands using an encryption key that matches the personalization session key, and executing at least one of the activation script and the deletion script, including: decrypting at least one of the activation script and the deletion script using the encryption key that matches the personalization session key, wherein execution of the activation script enables the mobile device with access to the personalization data and provisions the personalization data onto the mobile device. 11. The mobile device of claim 10 , further comprising: receiving, from the application provider computer, an activation message; and executing the activation script prior to initiating a transaction using the personalization data, and including: decrypting the activation script using the encryption key that matches the personalization session key. 12. The mobile device of claim 10 , wherein the executing the partial personalization script further includes: storing the personalization data in a secured form. 13. The mobile device of claim 10 , wherein the session identifier is a nonce value. 14. The mobile device of claim 10 , wherein the personalization master key is a symmetric encryption key. 15. The mobile device of claim 10 , further comprising: generating a device cryptogram using the encryption key that matches the personalization session key, wherein the device information further includes the device cryptogram, and wherein the service provider computer authenticates a user of the mobile device by validating the device cryptogram using the personalization session key. 16. The mobile device of claim 10 , wherein the request further includes user authentication information for a user of the mobile device, wherein the user authentication information includes an account identifier, and wherein the personalization data includes a token that represents the a
Generating enhanced content · CPC title
Use of certificates or encrypted proofs of transaction rights · CPC title
Downloading or loading of personalisation data · CPC title
Card activation or deactivation · CPC title
RFID or NFC payments by means of M-devices · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.