Method and system for executing applications on a mobile device

• US 20040122774A1
• Filed: 07/31/2003
• Published: 06/24/2004
• Est. Priority Date: 08/02/2002
• Status: Abandoned Application

• Current Assignee: Cardtronic
• Original Assignee: Cardtronic
• Inventors: Watson, Martin, Alme, Chris, Studd, Martin
• Application Number:
  US10/631,612
• Publication Number:
  US 20040122774A1
• Time in Patent Office: Days
• US Class Current: 705/65
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/3574 Multiple applications on card
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 30/018 Certifying business or products
• 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: 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
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and apparatus for integrating and instantiating custom applications in a multi-application smart card system are described. In one embodiment, the method includes receiving an indication that a mobile device is present, where the mobile device includes a first set of one or more mobile device applications, and where each mobile device application is associated with one or more of a second set of framework applications. The method also includes selecting a mobile device application from the first set. The method also includes selecting a framework application from the second set, wherein the mobile device application is associated with the framework application. The method further includes activating the framework application, wherein activating includes successfully authenticating device; and after activating the framework application, receiving transaction data from the mobile device application.

Claims

1. A method comprising:

receiving an indication that a mobile device is operative for data transmission, the mobile device including a first set of one or more mobile device applications, wherein each mobile device application is associated with one or more of a second set of framework applications;

selecting a mobile device application from the first set;

selecting a framework application from the second set, wherein the mobile device application is associated with the framework application;

activating the framework application, wherein activating includes successfully authenticating the mobile device; and

after activating the framework application, receiving transaction data from the mobile device application.

2. The method of claim 1, wherein the mobile device is a smart card.

3. The method of claim 1, wherein the computing device located at a service provider location.

4. The method of claim 3, where the service provider location is a physician'"'"'s office, clinic, hospital or location where healthcare services are performed.

5. The method of claim 1, wherein the mobile device applications of the first set are each provided by a sponsor.

6. The method of claim 5, wherein the sponsors include a health insurance company.

7. The method of claim 5 wherein the sponsors include a financial services company.

8. The method of claim 5, wherein the sponsor includes a healthcare provider.

9. The method of claim 5 wherein the sponsor includes a healthcare services administrator.

10. A method comprising:

receiving an indication that a smart card is operative for data transmission, wherein the smart card includes a smart card application, wherein the smart card application includes transaction data, and wherein the transaction data is inaccessible until the smart card is authenticated;

selecting the smart card application, wherein the smart card application is configured to communicate with a framework application;

instantiating the framework application, wherein instantiating includes successfully authenticating the smart card, wherein the smart card is authenticated according to an authentication method designated by the framework application; and

receiving the transaction data from the smart card application.

11. The method of claim 10, wherein the framework application is instantiated through an Internet browser.

12. The method of claim 10, where the smart card application is a Java Card applet.

13. The method of claim 10, wherein the smart card application and the framework application are associated with one or more sponsors.

14. The method of claim 13, wherein the sponsors include a health insurance company.

15. The method of claim 13, wherein the sponsors include a financial services company.

16. The method of claim 13, wherein the sponsor includes a healthcare provider.

17. The method of claim 13, wherein the sponsor includes a healthcare services administrator.

18. A method comprising:

transmitting to an application framework a first indication that a smart card is available, wherein the smart card includes a first set of one or more smart card applications, wherein each smart card application of the first set includes transaction data, wherein each smart card application of the first set is associated with one or more of a plurality of framework applications;

receiving a second indication from the application framework that a smart card application from the first set is selected;

authenticating the smart card according to an authentication method designated by one of the plurality of framework applications; and

after authenticating the smart card, transmitting transaction data to the application framework.

19. The method of claim 18, wherein, the smart card applications are Java Card applets.

20. The method of claim 18, wherein the transaction data includes a patient'"'"'s name and health plan information.

21. The method of claim 18, wherein smart card applications of the first set and the plurality of framework applications are associated with one or more sponsors.

22. The method of claim 21, wherein the sponsors include a health insurance company.

23. The method of claim 21, wherein the sponsors include a financial services company.

24. A method comprising:

transmitting an first indication that a mobile device is operative for data transmission, wherein the mobile device includes a set of one or more mobile device applications, wherein each of the mobile device applications includes transaction data, and wherein the transaction data is inaccessible until the mobile device is authenticated;

receiving a second indication that a mobile device application of the set of mobile device applications is selected;

authenticating the mobile device;

receiving a request for the mobile device application'"'"'s transaction data from a framework application of a plurality of framework applications;

transmitting the transaction data to the framework application.

25. The method of claim 24, where the mobile device applications are Java Card applets.

26. The method of claim 24, wherein the authentication data includes a personal identification number (PIN).

27. The method of claim 24, wherein smart card applications of the first set and the plurality of framework applications are associated with one or more sponsors.

28. The method of claim 27, wherein the sponsors include a health insurance company.

29. The method of claim 27, wherein the sponsors include a financial services company.

31. The apparatus of claim 28, wherein the mobile device is a smart card.

32. The apparatus of claim 28, wherein the transaction data includes health insurance information of a patient.

33. The apparatus of claim 28, wherein the mobile device applications are Java Card applets.

30. An apparatus comprising:

an application framework, the application framework including,

a mobile device interface unit to receive an indication that a mobile device is operative for data transmission, the mobile device including a set of one or more mobile device applications, wherein each of the mobile device applications includes transaction data, and wherein the transaction data is inaccessible until the mobile device is authenticated;

a framework application manager coupled with the mobile device interface, the framework application manager to activate an internal framework application or an external framework application after the indication is received;

an authentication services unit to perform operations for authenticating the mobile device; and

a mobile device interface unit to receive the transaction data from the mobile device and to transmit the transaction data to the internal framework application or the external framework application.

34. An apparatus comprising:

a smart card, the smart card including,

a memory unit to store a set of one or more smart card applications, wherein each of the smart card applications includes transaction data that is inaccessible until the smart card is authenticated, and wherein each of the smart card applications is associated with one or more of a plurality of framework applications; and

a central processing unit to transmit to an application framework an indication that the smart card is available, to process a smart card application selection received from a framework application of the plurality of framework applications, and to transmit the smart card application'"'"'s transaction data to the framework application.

35. The apparatus of claim 34, wherein the transaction data of each of the smart card applications is not accessible until the framework application authenticates the smart card.

36. The apparatus of claim 36, wherein the smart card applications are Java Card applets and the framework application is a Java application.

37. The apparatus of claim 36, wherein ones of the set of smart card applications and ones of the plurality of framework applications are associated with one or more sponsors.

38. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising:

receiving an indication that a mobile device is operative for data transmission, the mobile device including a first set of one or more mobile device applications, wherein each mobile device application is associated with one or more of a second set of framework applications;

selecting a mobile device application from the first set;

selecting a framework application from the second set, wherein the mobile device application is associated with the framework application;

activating the framework application, wherein activating includes successfully authenticating the mobile device; and

after activating the framework application, receiving transaction data from the mobile device application.

39. The machine-readable medium of claim 38, wherein the mobile device is a smart card.

40. The machine-readable medium of claim 38, wherein the computing device located at a service provider location.

41. The machine-readable medium of claim 40, where the service provider location is a physician'"'"'s office, clinic, hospital or location where healthcare services are performed.

42. The machine-readable medium of claim 38, wherein the mobile device applications of the first set are each provided by a sponsor.

43. The machine-readable medium of claim 42, wherein the sponsors include a health insurance company.

44. The machine-readable medium of claim 42, wherein the sponsors include a financial services company.

45. The machine-readable medium of claim 42, wherein the sponsor includes a healthcare provider.

46. The machine-readable medium of claim 42, wherein the sponsor includes a healthcare services administrator.

47. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising:

receiving an indication that a smart card is operative for data transmission, wherein the smart card includes a smart card application, wherein the smart card application include transaction data, and wherein the transaction data is inaccessible until the smart card is authenticated;

selecting the smart card application, wherein the smart card application is configured to communicate with a framework application;

instantiating the framework application, wherein instantiating includes successfully authenticating the smart card, wherein the smart card is authenticated according to an authentication method designated by the framework application; and

receiving the transaction data from the smart card application.

48. The machine-readable medium of claim 47, wherein the framework application is instantiated through an Internet browser.

49. The machine-readable medium of claim 47, where the smart card application is a Java Card applet.

50. The machine-readable medium of claim 47, wherein the smart card application and the framework application are associated with one or more sponsors.

51. The machine-readable medium of claim 50, wherein the sponsors include a health insurance company.

52. The machine-readable medium of claim 50, wherein the sponsors include a financial services company.

53. The machine-readable medium of 50, wherein the sponsor includes a healthcare provider.

54. The machine-readable medium of 50, wherein the sponsor includes a healthcare services administrator.

55. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising:

transmitting to an application framework a first indication that a smart card is operative for data transmission, wherein the smart card includes a first set of one or more smart card applications, wherein each smart card application of the first set includes transaction data, wherein each smart card application of the first set is associated with one or more of a plurality of framework applications;

receiving a second indication from the application framework that a smart card application from the first set is selected;

authenticating the smart card according to an authentication method designated by one of the plurality of framework applications; and

after authenticating the smart card, transmitting transaction data to the application framework.

56. The machine-readable medium of claim 55, wherein, the smart card applications are Java Card applets.

57. The machine-readable medium of claim 55, wherein the transaction data includes a patient'"'"'s name and health plan information.

58. The machine-readable medium of claim 55, wherein smart card applications of the first set and the plurality of framework applications are associated with one or more sponsors.

59. The machine-readable medium of claim 58, wherein the sponsors include a health insurance company.

60. The machine-readable medium of claim 58, wherein the sponsors include a financial services company.

61. A machine-readable medium that provides instructions, which when executed by a machine, cause said machine to perform operations comprising:

transmitting an first indication that a mobile device is available, wherein the mobile device includes a set of one or more mobile device applications, wherein each of the mobile device applications includes transaction data, and wherein the transaction data is inaccessible until the mobile device is authenticated;

receiving a second indication that a mobile device application of the set of mobile device applications is selected;

authenticating the mobile device;

receiving a request for the mobile device application'"'"'s transaction data from a framework application of a plurality of framework applications;

transmitting the transaction data to the framework application.

62. The machine-readable medium of claim 61, where the mobile device applications are Java Card applets.

63. The machine-readable medium of claim 61, wherein the authentication data includes a personal identification number (PIN).

64. The machine-readable medium of claim 61, wherein smart card applications of the first set and the plurality of framework applications are associated with one or more sponsors.

65. The machine-readable medium of claim 64, wherein the sponsors include a health insurance company.

66. The machine-readable medium of claim 64, wherein the sponsors include a financial services company.