UPDATING A WIDGET THAT WAS DEPLOYED TO A SECURE WALLET CONTAINER ON A MOBILE DEVICE

• US 20140130035A1
• Filed: 01/14/2014
• Published: 05/08/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,626,675 B2
• Time in Patent Office: Days
• US Class Current: 717/172
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06Q 20/08 Payment architectures
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0641 Shopping interfaces

Abstract

Updating a widget comprises receiving a query from a mobile device for the existence of an updated widget; transmitting information indicative of the availability of the updated widget to the mobile device; receiving a request for the updated widget from the mobile device; and transmitting the updated widget to the mobile device.

Claims

1. A method comprising:

receiving an alert that an updated version of a widget is available;

confirming that the update applies to a widget that is deployed on the mobile device;

configuring a wallet container that is deployed on the mobile device to accept the updated widget;

accessing the updated widget with the wallet container;

dispositioning the existing widget to restrict further use thereof; and

configuring a runtime environment for processing widgets on the mobile device to use the updated widget in place of the existing widget.

2. The method of claim 1, wherein the alert is received with a multi-domain secure wallet container that is executing on a mobile device.

3. The method of claim 1, wherein the widget is a service provider-specific widget that is deployed on a mobile device that is configured with portions of an enabling tier and a service tier of a multi-tier mobile computing ecosystem for facilitating secure personalized transactions between the mobile device and the specific service provider.

4. The method of claim 1, wherein accessing the updated widget comprises communicating through a service tier of a multi-tier computing ecosystem with a participant of the computing ecosystem to facilitate access of the updated widget.

5. The method of claim 4, wherein the multi-tier computing ecosystem comprises the service tier, a personalization tier, and an enabling tier.

6. The method of claim 1, wherein accessing the updated widget comprises accessing a mobile-device resident copy of the updated widget via an enabling tier of a multi-tier computing ecosystem.

7. The method of claim 6, wherein the multi-tier computing ecosystem comprises the service tier, a personalization tier, and an enabling tier.

8. A method comprising:

transmitting a query regarding an update for a deployed widget from a multi-domain wallet container operating on a mobile device to a deployer of the widget;

receiving information from the deployer indicative of availability of an update for the widget;

requesting an updated widget that comprises the update;

receiving the updated widget at the mobile device;

dispositioning the deployed widget to restrict further use thereof; and

storing the updated widget on the mobile device.

9. The method of claim 8, wherein storing the updated widget on the mobile device comprises a trusted service manager facility deploying the widget in a secure element of the mobile device.

10. The method of claim 9, wherein storing the updated widget further comprises transmitting a confirmation of storing the updated widget to the trusted service manager facility.

11. The method of claim 8, wherein dispositioning the deployed widget comprises configuring a runtime environment of the mobile device through which widgets are processed to process the updated widget instead of the deployed widget.

12. The method of claim 8, wherein transmitting a query is performed at predefined time intervals.

13. The method of claim 8, wherein transmitting a query is performed in response to the execution of a widget on the mobile device.

14. The method of claim 8, wherein requesting the updated widget comprises communicating through a service tier of a multi-tier computing ecosystem with the deployer server to facilitate access of the updated widget.

15. A method comprising:

receiving a query from a mobile device for the existence of an updated widget;

transmitting information indicative of the availability of the updated widget to the mobile device;

receiving a request for the updated widget from the mobile device; and

transmitting the updated widget to the mobile device.

16. The method of claim 15, wherein the query is received at predefined time intervals.

17. The method of claim 15, wherein the query is received in response to the execution of a widget on the client device.

18. The method of claim 15, further comprising receiving a confirmation of storing the updated widget.

19. The method of claim 15, wherein receiving a request for the updated widget comprises communicating through a service tier of a multi-tier computing ecosystem with the mobile device to facilitate access of the updated widget.

20. The method of claim 19, wherein the multi-tier computing ecosystem comprises the service tier, a personalization tier, and an enabling tier.