# US 2019/0173883 A1 · Systems and methods for device push provisioning

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

- Number: US 2019/0173883 A1
- Document ID: US20190173883A1
- Status: Published application
- Kind: A1
- Application number: 16/268,377
- Filed: 2019-02-05
- Published: 2019-06-06
- Earliest claimed: 2016-01-07
- Assignees: Visa International Service Association
- Inventors: Madhuri Chandoor; Jalpesh Chitalia; Gueorgui Petkov; Mohamed Nosseir; Parveen Bansal; Thomas Bellenger; Simon Law
- Web page: https://patentgrep.com/patent/US20190173883A1

## CPC

- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W 12/35: {Protecting application or service provisioning, e.g. securing SIM application provisioning}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 2463/121: Timestamp
- H04W 88/02: Terminal devices
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Techniques for provisioning access data may include receiving, by a first application installed on a communication device, user input selecting an account to provision to a second application installed on the communication device. The first application may invoke the second application and send a session identifier (ID) to the second application. The second application may send a user ID associated with the second application, a device ID, and the session ID to the first application. The first application may then generate encrypted provisioning request data and send the encrypted provisioning request data to the second application. The second application may send the encrypted provisioning request data to a remote server computer to request access data that can be used to access a resource. The second application may receive the access data provided by the remote server computer based on validation of the encrypted provisioning request data.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A method comprising:
receiving, by a server computer from a first application via a second application on a mobile device, encrypted provisioning request data including an account ID of an account to provision, a user ID, and a device ID in encrypted form;
validating, by the server computer, the encrypted provisioning request data; and
transmitting, by the server computer to the second application on the mobile device, access data based on validation of the encrypted provisioning request data, wherein the second application stores the access data.

### Claim 22 (depends on 21)

The method of claim 21, wherein the first application received user input selecting the account to provision to the second application, and in response to receiving the selection of the account to provision, the first application invoked the second application, and the second application sent the user ID, the user ID associated with the second application, and the device ID to the first application, which generated the encrypted provisioning request data.

### Claim 23 (depends on 21)

The method of claim 21, wherein validating the encrypted provisioning request data includes decrypting the received encrypted provisioning request data using a key associated with the first application to determine that the encrypted provisioning request data was generated by the first application.

### Claim 24 (depends on 21)

The method of claim 21, wherein the encrypted provisioning request data further includes a timestamp, and validating the encrypted provisioning request data includes determining whether a difference between a time at which the encrypted provision request data was received by the server computer and the time indicated in the timestamp is within a predefined time threshold.

### Claim 25 (depends on 21)

The method of claim 21, wherein validating the encrypted provisioning request data includes determining that the account ID is a valid account ID associated with first application.

### Claim 26 (depends on 21)

The method of claim 21, wherein the access data includes user credential data that the second application uses to access a service associated with the first application.

### Claim 27 (depends on 21)

The method of claim 21, wherein the first application is an issuer application and the second application is an digital wallet application.

### Claim 28 (depends on 21)

The method of claim 21, wherein the access data allows a user of the mobile device to access a building.

### Claim 29 (depends on 21)

The method of claim 21, wherein the access data is a token that is a substitute for the account ID.

### Claim 30 (depends on 21)

The method of claim 21, wherein validating the encrypted provisioning request data includes decrypting the received encrypted provisioning request data using a key associated with the first application to determine that the encrypted provisioning request data was generated by the first application, and wherein the method further comprises:
receiving, an application ID of the first application, and then using the application ID to retrieve the key.

### Claim 31

A server computer comprising:
a processor; and
a non-transitory computer readable medium, the non-transitory computer readable medium comprising code, executable by the processor, for implementing a method comprising
receiving, from a first application via a second application on a mobile device, encrypted provisioning request data including an account ID of an account to provision, a user ID, and a device ID in encrypted form,
validating the encrypted provisioning request data, and
transmitting, to the second application on the mobile device, access data based on validation of the encrypted provisioning request data, wherein the second application stores the access data.

### Claim 32 (depends on 31)

The server computer of claim 31, wherein the first application received user input selecting the account to provision to the second application, and in response to receiving the selection of the account to provision, the first application invoked the second application, and the second application sent the user ID, the user ID associated with the second application, and the device ID to the first application, which generated the encrypted provisioning request data.

### Claim 33 (depends on 31)

The server computer of claim 31, wherein validating the encrypted provisioning request data includes decrypting the received encrypted provisioning request data using a key associated with the first application to determine that the encrypted provisioning request data was generated by the first application.

### Claim 34 (depends on 31)

The server computer of claim 31, wherein the encrypted provisioning request data further includes a timestamp, and validating the encrypted provisioning request data includes determining whether a difference between a time at which the encrypted provision request data was received by the server computer and the time indicated in the timestamp is within a predefined time threshold.

### Claim 35 (depends on 31)

The server computer of claim 31, wherein validating the encrypted provisioning request data includes determining that the account ID is a valid account ID associated with first application.

### Claim 36 (depends on 31)

The server computer of claim 31, wherein the access data includes user credential data that the second application uses to access a service associated with the first application.

### Claim 37 (depends on 31)

The server computer of claim 31, wherein the first application is an issuer application and the second application is an digital wallet application.

### Claim 38 (depends on 31)

The server computer of claim 31, wherein the access data allows a user of the mobile device to access a building.

### Claim 39 (depends on 31)

The server computer of claim 31, wherein the access data is a token that is a substitute for the account ID.

### Claim 40 (depends on 31)

The server computer of claim 31, wherein validating the encrypted provisioning request data includes decrypting the received encrypted provisioning request data using a key associated with the first application to determine that the encrypted provisioning request data was generated by the first application, and wherein the method further comprises:
receiving, an application ID of the first application, and then using the application ID to retrieve the key.
