DEPLOYING AN ISSUER-SPECIFIC WIDGET TO A SECURE WALLET CONTAINER ON A CLIENT DEVICE

• US 20140095382A1
• Filed: 12/11/2013
• Published: 04/03/2014
• Est. Priority Date: 10/06/2005
• Status: Active Grant

• Current Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Original Assignee: C-SAM Incorporated (MasterCard Incorporated)
• Inventors: Desai, Mehul, Pitroda, Satyan G., Maniar, Nehal
• Granted Patent: US 9,886,691 B2
• Time in Patent Office: Days
• US Class Current: 705/41
• CPC Class Codes: G05B 2219/25107 Pluggable card, magnetic or smart with configuration data, staying in device
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 3/08 from or to individual record carriers, e.g. punched card , memory card, integrated circuit [IC] card or smart card
• CPC Class Codes: G06K 7/0065 comprising keyboard or display, e.g. a pocket calculator sized casing suitable for off-line checking the remaining money on a smart banking card
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Deploying an issuer-specific widget to a wallet container on a client device is accomplished by configuring a widget to provide access to an issuer-specific service group of services that are accessible in a service tier of a multi-tier platform for providing secure transactions, determining service-provider specific resource access requirements for operating the widget, configuring a widget descriptor with the access requirements, and communicating with wallet container to ensure successful deployment of the configured widget that meets the access requirements in the widget descriptor.

Claims

1. A method comprising:

configuring a widget, at least partially, by a networked server to provide access to an issuer-specific service group of services accessible via a service tier of a multi-tier platform for providing secure transactions, the platform comprising at least enabling, service, and personalization tiers;

determining service provider-specific platform resource access requirements that facilitate securely operating the widget on a client device;

configuring a widget descriptor with the access requirements and associating the widget descriptor with the widget;

requesting a secure wallet container operating on a client mobile device to deploy the configured widget by sending at least one of the configured widget and the widget descriptor from an issuer-specific server to the client mobile device; and

receiving a confirmation of successful deployment of the configured widget, wherein the successful deployment meets the access requirements configured in the widget descriptor.

2. The method of claim 1, further comprising communicating from the server to the deployed widget to provide at least one service from the issuer-specific service group, wherein the at least one service comprises following a service provider-specific workflow.

3. The method of claim 2, wherein the service provider-specific workflow facilitates a trust model-based secure personalized transaction using each of the enabling, service, and personalization tiers.

4. The method of claim 1, wherein the widget descriptor comprises access requirements for a service provider-specific workflow, device operating system actions, domains, user interface code, and widget persistent data.

5. The method of claim 1, wherein the widget descriptor comprises a data structure that is signed by the issuer-specific server.

6. The method of claim 1, wherein platform resources for which access requirements are determined comprise at least one of Secure Element applets and mobile wallet accounts.

12. The method of claim 1, wherein platform resources for which access requirements are determined comprise at least one of Secure Element applets and mobile wallet accounts.

7. A method comprising:

configuring a widget, at least partially, by a networked server to provide access to an issuer-specific service group of services accessible via a service tier of a multi-tier platform for providing secure transactions, the platform comprising at least enabling, service, and personalization tiers;

determining service provider-specific platform resource access requirements that facilitate securely operating the widget on a client device;

configuring a widget descriptor with the access requirements and associating the widget descriptor with the widget;

receiving a request from a component of the multi-tier platform operating on a client mobile device to deploy the configured widget and in response thereto sending at least one of the configured widget and the widget descriptor from an issuer-specific server to the client mobile device; and

receiving a confirmation of successful deployment of the configured widget on the client mobile device, wherein the successful deployment meets the access requirements configured in the widget descriptor.

8. The method of claim 7, further comprising communicating from the server to the deployed widget to provide at least one service from the issuer-specific service group, wherein the at least one service comprises following a service provider-specific workflow.

9. The method of claim 8, wherein the service provider-specific workflow facilitates a trust model-based secure personalized transaction using each of the enabling, service, and personalization tiers.

10. The method of claim 7, wherein the widget descriptor comprises access requirements for a service provider-specific workflow, device operating system actions, domains, user interface code, and widget persistent data.

11. The method of claim 7, wherein the widget descriptor comprises a data structure that is signed by the issuer-specific server.

13. A method comprising:

receiving in a secure wallet container operating on a client mobile device an indication of availability of a mobile device executable widget configured to provide access to an issuer-specific service group of services accessible in a service tier of a multi-tier platform for providing secure transactions, the platform comprising at least enabling, service, and personalization tiers;

determining service provider-specific platform resource access requirements that facilitate securely operating the widget on the client device to provide at least one service from the issuer-specific service group of services, wherein the service provider-specific access requirements are based on a widget descriptor that is associated with the widget;

receiving a request that the configured widget be installed with the secure wallet container;

receiving at least one of the configured widget and the widget descriptor from an issuer-specific server at the client mobile device; and

installing the configured widget, based on the access requirements, on the mobile device through the secure wallet container.

14. The method of claim 13, wherein installing the configured widget comprises determining widget isolation requirements for operating the widget on the client device and configuring the secure wallet container to ensure that the widget isolation requirements are met.

15. The method of claim 13, further comprising transmitting a confirmation of successful deployment of the configured widget on the client mobile device, wherein the successful deployment meets the access requirements configured in the widget descriptor.

16. The method of claim 13, further comprising communicating from the deployed widget to a server to provide at least one service from the issuer-specific service group, wherein the at least one service comprises following a service provider-specific workflow.

17. The method of claim 16, wherein the issuer-specific service facilitates a trust model-based secure personalized transaction using each of the enabling, service, and personalization tiers.

18. The method of claim 13, wherein the widget descriptor comprises access requirements for a service provider-specific workflow, device operating system actions, domains, user interface code, and widget persistent data.

19. The method of claim 13, wherein the widget descriptor comprises a data structure that is signed by the issuer-specific server.

20. The method of claim 13, wherein platform resources for which access requirements are determined comprise at least one of Secure Element applets and mobile wallet accounts.