IP Library › Granted Patent US 11,972,412
Granted Patent B2
US 11,972,412 · App. 17/232,079 · Granted Apr 30, 2024

Device provisioning using partial personalization scripts

Inventors: Erick Wong (Vancouver, CA); Oleg Makhotin (Paris, FR)
Assignee: VISA INTERNATIONAL SERVICE ASSOCIATION
G06Q20/363G06Q20/3227G06Q20/3278G06Q20/354G06Q20/3552G06Q20/38215G06Q20/3829
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,972,412
App. No.
17/232,079
Granted
Apr 30, 2024
Kind
B2
Abstract

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.

Claims (44)

1. A computer-implemented method comprising:

receiving, by a processor of an application provider computer, from a mobile device, 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;

sending, by the processor, to a service provider computer, the request for provisioning the mobile device, wherein 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 processor, from the service provider computer, the partial personalization script and the activation script and the deletion script; and

initiating, by the processor, execution of the partial personalization script and at least one of the activation script and the deletion script on the mobile device, wherein the mobile device decrypts the store data commands and at least one of the activation script and the deletion script using an encryption key that matches the personalization session key, and wherein the 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 computer-implemented method of claim 1 , further comprising:

sending, by the processor, to the mobile device, the activation script and the deletion script;

receiving, by the processor, from the service provider computer, an activation message; and

initiating, by the processor, the execution of the activation script on the mobile device, wherein the mobile device decrypts the activation script using the encryption key that matches the personalization session key.

3. The computer-implemented method of claim 1 , further comprising:

sending, by the processor, to the mobile device, the activation script and the deletion script;

receiving, by the processor, from the service provider computer, a deletion message; and

initiating, by the processor, the execution of the deletion script to delete the personalization data from the mobile device, wherein the mobile device decrypts the deletion script using the encryption key that matches the personalization session key.

4. The computer-implemented method of claim 1 , further comprising:

receiving, by the processor, from the service provider computer, an activation message; and

wherein initiating the execution of at least one of the activation script and the deletion script on the mobile device includes:

in response to receiving the activation message, sending, by the processor, to the mobile device, the activation script, wherein the mobile device executes the activation script.

5. The computer-implemented method of claim 1 , further comprising:

receiving, by the processor, from the service provider computer, a deletion message; and

wherein initiating the execution of at least one of the activation script and the deletion script on the mobile device includes:

in response to receiving the deletion message, sending, by the processor, to the mobile device, the deletion script, wherein the mobile device executes the deletion script to delete the personalization data from the mobile device.

6. The computer-implemented 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 processor, from the service provider computer, the new activation script.

7. The computer-implemented 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 computer-implemented method of claim 1 , wherein the session identifier is a nonce value.

9. The computer-implemented method of claim 1 , wherein the personalization master key is a symmetric encryption key.

10. An application provider computer comprising:

a processor;

a non-transitory computer-readable medium comprising code executable by the processor for implementing operations including:

receiving, from a mobile device, 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;

sending, to a service provider computer, the request for provisioning the mobile device, wherein 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 service provider computer, the partial personalization script and the activation script and the deletion script; and

initiating execution of the partial personalization script and at least one of the activation script and the deletion script on the mobile device, wherein the mobile device decrypts the store data commands and at least one of the activation script and the deletion script using an encryption key that matches the personalization session key, and wherein the 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 application provider computer of claim 10 , further comprising:

sending, to the mobile device, the activation script and the deletion script;

receiving, from the service provider computer, an activation message; and

initiating, the execution of the activation script on the mobile device, wherein the mobile device decrypts the activation script using the encryption key that matches the personalization session key.

12. The application provider computer of claim 10 , wherein the execution of the partial personalization script stores the personalization data onto the mobile device a secured form.

13. The application provider computer of claim 10 , wherein the session identifier is a nonce value.

14. The application provider computer of claim 10 , wherein the personalization master key is a symmetric encryption key.

15. The application provider computer of claim 10 , wherein the device information includes a device cryptogram generated by the mobile device using the encryption key that matches the personalization session key, 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 application provider computer 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 account identifier.

17. The application provider computer of claim 10 , wherein the request does not include the personalization master key, and wherein the personalization master key is not sent between the mobile device and the service provider computer.

18. The application provider computer of claim 10 , wherein the personalization master key is associated with an issuer of a user account or a manufacturer of a secure element associated with the secure element identifier.

Continuity (6)
Continuation 16255559 · Jan 23, 2019
Continuation 15658897 · Jul 25, 2017
Continuation 14275404 · May 12, 2014
Provisional Application 61898428 · Oct 31, 2013
Provisional Application 61822271 · May 10, 2013
Related Publication 20210241264A1 · Aug 5, 2021