Payment application download to mobile phone and phone personalization

• US 9,307,341 B2
• Filed: 11/21/2013
• Issued: 04/05/2016
• Est. Priority Date: 04/27/2007
• Status: Expired due to Fees

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: III Holdings 1, LLC
• Inventors: Saunders, Peter D., Beenau, Blayn W., Peart, Lee J., Warren, Jessica U.
• Primary Examiner(s): MEHRA, INDER P
• Application Number:
  US14/086,080
• Publication Number:
  US 20140080470A1
• Time in Patent Office: 866 Days
• Field of Search: 705/26.7, 705/44, 705/26.62, 705/39, 705/41, 705/7.29, 705/14.49, 705/14.64, 705/2, 705/28, 705/38, 705/76, 705/14.16, 705/14.19, 705/14.41, 705/14.53, 705/14.66, 705/26.41, 705/26.5, 705/26.81, 705/3, 705/319, 705/37, 705/42, 705/5, 705/67, 705/72, 705/7.19, 455/414.1, 455/416, 455/41.1, 455/41.2, 455/456.3, 455/457, 455/550.1, 455/552.1, 455/563, 455/11.1, 455/411, 455/575.8, 370/280
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/3221 Access to banking information through M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3265 characterised by personalisation for use
• CPC Class Codes: G06Q 20/3552 Downloading or loading of personalisation data
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

A method and system of personalizing a mobile phone over a wireless network is provided. The method is fast, reliable, and eliminates the need for an uninterrupted online connection to a host server in order to achieve successful download of user information. With the method and system, a mobile phone can be personalized for various purposes, such as for conducting financial transactions.

Claims

1. A method, comprising:

receiving, at a computer system and from a user device, a request in the form of a text message to personalize the user device;

storing, by the computer system and in a database maintained by a provider of a transaction account associated with a user of the user device, information indicating that the user device is authorized to interact with the transaction account to make a mobile payment;

generating, by the computer system, a personalized data package, wherein the personalized data package includes transaction account information specific to the transaction account;

in response to the request, the computer system sending a text message addressed to a phone number associated with the user device, wherein the text message indicates that a resource file related to a software module to be installed on the user device is ready for download at a URL;

in response to receiving information indicating that the user device has visited the URL, transmitting, by the computer system, the resource file to the user device, wherein the resource file is configured to facilitate installation of the software module in a first internal memory of the user device; and

in response to receiving information indicating the user device has accessed the software module, transmitting, by the computer system, the personalized data package to the user device, wherein the software module is configured to store the personalized data package in the first internal memory of the user device, wherein, based upon instructions included in the resource file, the software module is configured to copy the personalized data package to a second, secure memory element of the user device and delete the personalized data package from the first internal memory, and wherein the software module is configured to access the transaction account information in the second, secure memory element in order to enable the user device to operate as a mobile financial transaction instrument.

2. The method of claim 1, wherein the software module is configured to cause the user device, based upon the personalized data package, to operate as the mobile financial transaction instrument.

3. The method of claim 1, wherein the software module is configured to instruct the user device to transmit, via radio frequency (RF), the transaction account information to a point of sale device (POS).

4. The method of claim 1, wherein the user device is a mobile phone.

5. The method of claim 1, wherein the resource file is a Java archive file.

6. The method of claim 1, further comprising processing, by the computer system, a financial transaction via the user device.

7. The method of claim 1, wherein the second, secure memory element is a secure card using a JCOP operating system.

8. The method of claim 1, wherein the resource file is based on the personalized data package.

9. The method of claim 1, further comprising authenticating, by the computer system, the request to personalize the user device.

10. The method of claim 1, further comprising providing, by the computer system, a description file to the user device over a wireless network, wherein the description file comprises the resource file comprising the software module.

11. A system comprising:

one or more processors; and

a first memory element and a second, secure memory element both coupled to the one or more processors, wherein the first memory element has stored thereon instructions executable to cause the system to perform operations comprising;

sending, via text message, a request to personalize the system, wherein the text message relates to a transaction account associated with a user of the system;

receiving a reply text message to the request indicating that a resource file comprising a software module to be installed on the system is ready for download at a URL indicated in the reply text message;

in response to accessing the URL, receiving the resource file and installing the software module in the first memory element;

in response to transmitting information indicating the system has accessed the software module, receiving a personalized data package, wherein the personalized data package includes transaction account information associated with the user and the transaction account;

storing the personalized data package in the first memory element; and

based on instructions included in the resource file, copying the personalized data package to the second, secure memory element and deleting the personalized data package from the first memory element.

12. The system of claim 11, wherein the operations further comprise accessing the personalized data package via the software module.

13. The system of claim 11, wherein the operations further comprise conducting a transaction via the transaction account.

14. The system of claim 11, wherein the system is a mobile phone.

15. The system of claim 11, wherein the second, secure memory element is a secure card using a Java-based operating system.

16. A non-transitory computer-readable medium having stored thereon instructions executable by a system including one or more processors to the system to perform operations comprising:

sending, via text message, a request to personalize the system, wherein the text message relates to a transaction account associated with a user of the system;

receiving a reply text message to the request indicating that a resource file comprising a software module to be installed on the system is ready for download at a URL indicated in the reply text message;

in response to accessing the URL, receiving the resource file and installing the software module in a first memory element;

in response to transmitting information indicating the system has accessed the software module, receiving a personalized data package, wherein the personalized data package includes transaction account information associated with the user and the transaction account;

storing the personalized data package in the first memory element; and

based on instructions included in the resource file, copying the personalized data package to a second, secure memory element and deleting the personalized data package from the first memory element.

17. The non-transitory computer-readable medium of claim 16, wherein the operations further comprise performing a transaction via the software module.

18. The non-transitory computer-readable medium of claim 16, wherein the operations further comprise accessing the personalized data package via the software module.

19. The non-transitory computer-readable medium of claim 16, further comprising receiving information indicating that the system has been authenticated.