# US 2021/0241264 A1 · Device provisioning using partial personalization scripts

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0241264 A1
- Document ID: US20210241264A1
- Status: Published application
- Kind: A1
- Application number: 17/232,079
- Filed: 2021-04-15
- Published: 2021-08-05
- Earliest claimed: 2013-05-10
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Erick Wong; Oleg Makhotin
- Web page: https://patentgrep.com/patent/US20210241264A1

## CPC

- G06Q 20/363: {with the personal data of a user}
- G06F 21/1065: {Generating enhanced content}
- G06Q 20/3227: {using secure elements embedded in M-devices}
- G06Q 20/3265: {characterised by personalisation for use}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/354: {Card activation or deactivation}
- G06Q 20/3552: {Downloading or loading of personalisation data}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3829: {involving key management}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim at position 1

-20. (canceled)

### Claim 21

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, and generates a partial personalization script using the encrypted store data commands;
receiving, by the processor, from the service provider computer, the partial personalization script; and
initiating, by the processor, execution of the partial personalization script on the mobile device, wherein the mobile device decrypts the store data commands using an encryption key that matches the personalization session key.

### Claim 22 (depends on 21)

The computer-implemented method of claim 21, wherein the service provider computer 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, and further comprising:
receiving, by the processor, from the service provider computer, the activation script and the deletion script; and
initiating execution of at least one of the activation script and the deletion script on the mobile device, wherein the mobile device decrypts at least one of the activation script and the deletion script using the encryption key that matches the personalization session key.

### Claim 23 (depends on 22)

The computer-implemented method of claim 22, 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, execution of the activation script on the mobile device, 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 prior to initiating a transaction using the personalization data, and wherein the mobile device decrypts the activation script using the encryption key that matches the personalization session key.

### Claim 24 (depends on 22)

The computer-implemented method of claim 22, 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, 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.

### Claim 25 (depends on 22)

The computer-implemented method of claim 22, further comprising:
receiving, by the processor, from the service provider computer, an activation message; and
wherein initiating 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, and 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.

### Claim 26 (depends on 22)

The computer-implemented method of claim 22, further comprising:
receiving, by the processor, from the service provider computer, a deletion message; and
wherein initiating 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.

### Claim 27 (depends on 22)

The computer-implemented method of claim 22, 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.

### Claim 28 (depends on 21)

The computer-implemented method of claim 21, wherein the partial personalization script includes a script operable to store the personalization data on the mobile device in a secured form.

### Claim 29 (depends on 21)

The computer-implemented method of claim 21, wherein the session identifier is a nonce value.

### Claim 30 (depends on 21)

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

### Claim 31

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, and generates a partial personalization script using the encrypted store data commands;
receiving, from the service provider computer, the partial personalization script; and
initiating execution of the partial personalization script on the mobile device, wherein the mobile device decrypts the store data commands using an encryption key that matches the personalization session key.

### Claim 32 (depends on 31)

The application provider computer of claim 31, wherein the service provider computer 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, and further comprising:
receiving, from the service provider computer, the activation script and the deletion script; and
initiating execution of at least one of the activation script and the deletion script on the mobile device, wherein the mobile device decrypts at least one of the activation script and the deletion script using the encryption key that matches the personalization session key.

### Claim 33 (depends on 32)

The application provider computer of claim 32, 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, execution of the activation script on the mobile device, 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 prior to initiating a transaction using the personalization data, and wherein the mobile device decrypts the activation script using the encryption key that matches the personalization session key.

### Claim 34 (depends on 31)

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

### Claim 35 (depends on 31)

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

### Claim 36 (depends on 31)

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

### Claim 37 (depends on 31)

The application provider computer of claim 31, 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.

### Claim 38 (depends on 31)

The application provider computer of claim 31, 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.

### Claim 39 (depends on 31)

The application provider computer of claim 31, 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.

### Claim 40 (depends on 31)

The application provider computer of claim 31, 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.
