INITIATING AND COMPLETING TRANSACTIONS VIA NOTIFICATION ELEMENTS

• US 20120089943A1
• Filed: 10/06/2010
• Published: 04/12/2012
• Est. Priority Date: 10/06/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Jain, Kalpit, Neafsey, Jeffrey Scott
• Application Number:
  US12/899,188
• Publication Number:
  US 20120089943A1
• Time in Patent Office: Days
• US Class Current: 715/808
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/42 Confirmation, e.g. check or permission by the legal debtor of payment

Abstract

Initiating and completing transactions using a notification architecture associated in part with an operating system executing on a first computing device. The transactions are associated with a second computing device (e.g., a merchant computing device). Transaction messages relating to the transactions are conveyed via the notification architecture to the first computing device of a user. User interface notification elements associated with the operating system on the first computing device display the transaction messages, and receive authorization from the user relating to the transactions. The authorization is provided to the merchant computing device by the notification architecture. The transactions are completed without executing, on the first computing device, an application associated with the merchant computing device.

Claims

1. A system comprising:

a memory area associated with a mobile computing device of a user, said memory area storing an operating system and one or more applications; and

a processor programmed to;

receive a subscription request from the user;

provide the received subscription request to a notification service in communication with a merchant computing device;

receive, by the mobile computing device from the merchant computing device based on the subscription request, a transaction message identifying a transaction associated with one of the applications stored in the memory area, said transaction message further specifying the user of the mobile computing device;

provide the received transaction message to the user via a user interface notification element associated with the operating system;

receive user input to the user interface notification element, said user input indicating an authorization relating to the transaction; and

provide the authorization to the merchant computing device.

2. The system of claim 1, wherein the processor is programmed to provide the received transaction message to the user via the user interface notification element separate from said one of the applications.

3. The system of claim 1, wherein the transaction message comprises one or more of the following:

a bill pay notification, a network connection notification, a stock quote, and data relating to an auction transaction.

4. The system of claim 1, wherein the user interface notification element comprises one or more of the following:

a tile, a toast, a popup, and a bubble.

5. The system of claim 1, wherein the processor is further programmed to:

receive, from the user, a request to execute said one of the applications; and

responsive to the received request, execute said one of the applications.

6. The system of claim 1, further comprising means for providing the transaction message to the user without executing said one of the applications, and means for exchanging data with the user via the user interface notification element to complete the transaction.

7. The system of claim 1, wherein the user input comprises one or more of the following:

a check mark indicating a positive authorization, and a letter X indicating a negative authorization.

8. A method comprising:

receiving, by a first computing device from a second computing device, a transaction message identifying a transaction associated with an application available on the first computing device, said transaction message further specifying a user of the first computing device;

providing the received transaction message to the user via a user interface notification element associated with an operating system executing on the first computing device;

receiving user input to the user interface notification element, said user input indicating an authorization relating to the transaction; and

providing the authorization to the second computing device.

9. The method of claim 8, wherein receiving the user input comprises receiving user input indicating a positive authorization or a negative authorization.

10. The method of claim 8, wherein providing the received transaction message to the user comprises providing the received transaction message to the user via a plurality of user interface notification elements.

11. The method of claim 8, wherein an operating system associated with the first computing device has notification functionality associated therewith, said notification functionality being separate from the application, and wherein providing the received transaction message comprises providing the received transaction message via the notification functionality.

12. The method of claim 8, wherein providing the received transaction message and receiving the user input occurs without executing the application.

13. The method of claim 8, wherein receiving the transaction message comprises receiving a plurality of transaction messages each associated with one of a plurality of applications available on the first computing device.

14. The method of claim 13, wherein providing the received plurality of transaction messages comprises providing the received plurality of transaction messages to the user via a plurality of user interface notification elements arranged for display in a single user interface of the first computing device.

15. The method of claim 13, wherein the first computing device comprises a mobile computing device, and wherein providing the received plurality of transaction messages comprises providing the received plurality of transaction messages to the user via a plurality of user interface notification elements arranged for display on a home screen of the mobile computing device.

16. The method of claim 8, further comprising:

receiving a request from the user via the user interface notification element to execute the application; and

responsive to the received request, executing the application.

17. One or more computer-readable media having computer-executable components, said components comprising:

a communications interface component that when executed by at least one processor of a first computing device of a user causes the at least one processor to receive, by the first computing device from a second computing device, a transaction message identifying a transaction associated with an application available on the first computing device, said transaction message further specifying the user of the first computing device;

a graphics component that when executed by at least one processor of the first computing device causes the at least one processor to generate a sequence of user interface notification elements corresponding to the transaction message received by the communications interface; and

a user interface component that when executed by at least one processor of the first computing device causes the at least one processor to display, without execution of the application by the at least one processor, the sequence of user interface notification elements generated by the graphics component to convey to the user the transaction message received by the communications interface, said user interface component further executing to receive user input to one or more of the displayed user interface notification elements, said user input indicating an authorization relating to the transaction;

wherein the communications interface component further executes to provide the authorization to the second computing device.

18. The computer-readable media of claim 17, wherein the transaction is associated with one or more of the following:

payment of an invoice, rejection of an invoice, acceptance of a network connection, rejection of a network connection, entry of an auction bid, purchase of a security, and sale of a security.

19. The computer-readable media of claim 17, wherein the user interface component is associated with an operating system.

20. The computer-readable media of claim 17, wherein the user input comprises one or more of the following:

a gesture, a movement of the first computing device, and a button press.