Strategies for queuing events for subsequent processing

• US 20070027808A1
• Filed: 07/29/2005
• Published: 02/01/2007
• Est. Priority Date: 07/29/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Flaks, Jason, Gupta, Mukul, Kelly, Sean, Dooley, James, Ludwig, Charles
• Application Number:
  US11/192,510
• Publication Number:
  US 20070027808A1
• Time in Patent Office: Days
• US Class Current: 705/51
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: H04L 49/90 Buffering arrangements

Abstract

In one exemplary implementation, strategies are described which transmit notification information from a first device (e.g., a media server) to a second device (e.g., a remote media device). Based on this notification information, a recipient-user can use the first device to generate an event pertaining to the notification information and forward the event to the second device, where the event is logged. The second device can then send prompting information to a follow-up user (who may be the same as the recipient-user) to alert that user to the existence of the logged event. The follow-up user can further advance an action (such as buying a resource, printing a resource, and so forth) based on the prompting information. Filtering mechanisms are described for determining which recipient-users are able to send events, and for determining which follow-up users are able to receive prompting information that indicates the existence of events.

Claims

1. A method for handling a transaction, comprising:

providing notification information to a recipient-user that pertains to content;

receiving an event that indicates that the recipient-user has performed a commencement action in response to the notification information by activating a control associated with the commencement action, wherein the event describes;

a target object associated with the content; and

an operation to be performed on the target object;

logging the event to provide a logged event;

informing a follow-up user of the existence of the logged event; and

allowing the follow-up user to perform a follow-up action associated with the logged event, wherein the follow-up action pertains to the content and is associated with the operation identified in the event,

wherein the commencement action and the follow-up action together comprise at least part of the transaction.

2. The method of claim 1, wherein the commencement action comprises a request by the recipient-user to purchase a resource, and the follow-up action comprises an action pertaining to the purchase of the resource.

3. The method of claim 1, wherein the commencement action comprises a request by the recipient-user to perform some processing on a resource, and the follow-up action comprises an action pertaining to the performance of the processing.

4. The method of claim 3, wherein the processing comprises one or more of:

transferring the resource to a target destination;

performing data processing on the resource to transform the data associated with the resource;

altering a status associated with the resource;

or

backing up the resource.

5. The method of claim 1, wherein the control is a physical control element associated with the commencement action.

6. The method of claim 1, wherein the control is a graphical user interface element associated with the commencement action.

7. The method of claim 1, wherein a recipient device that the recipient-user uses to receive the notification information is a same device which the recipient-user uses to generate the event.

8. The method of claim 1, wherein a recipient device that the recipient-user uses to receive the notification information is different than a device which the recipient-user uses to generate the event.

9. The method of claim 1, further comprising determining if the recipient-user is pre-authorized to receive the notification information or if the recipient-user is pre-authorized to act on the notification information, and only providing the notification information to the recipient-user if the recipient-user is entitled to receive the notification

10. The method of claim 1, wherein the logging of the event comprises queuing the event in association with the recipient-user who generated the event.

11. The method of claim 1, wherein the recipient-user generates the event by using a device that performs a first role, and wherein the follow-up user performs the follow-up action using a device which performs a second role.

12. The method of claim 11, wherein the device that performs the first role is different than the device that performs the second role.

13. The method of claim 12, wherein the device that performs the first role has fewer processing resources compared to the device that performs the second role.

14. The method of claim 1, wherein the recipient-user is the same as the follow-up user.

15. The method of claim 1, wherein the recipient-user is not the same as the follow-up user.

16. The method of claim 1, wherein the informing of the follow-up user of the logged event comprises automatically sending the follow-up user prompting information through an auto-play routine when it is detected that the follow-up user is engaged in a device which presents the prompting the information.

17. The method of claim 16, further comprises determining if the follow-up user is entitled to consummate the transaction, and only providing the prompting information to the follow-up user if the follow-up user is entitled to receive the prompting information.

18. One or more computer readable media comprising computer readable instructions for performing the method of claim 1.

19. A method for handling a transaction, comprising:

at a first device;

providing notification information to a user that pertains to content;

at a second device;

receiving the notification information;

performing a commencement action associated with the content by invoking a control associated with the commencement action,

wherein the commencement action generates an event that describes;

a target object associated with the content; and

an operation to be performed on the target object;

at the first device;

receiving the event;

logging the event to provide a logged event;

informing the user of the existence of the logged event; and

allowing the user to perform a follow-up action associated with the logged event, wherein the follow-up action pertains to the content and is associated with the operation identified in the event,

wherein the commencement action and the follow-up action together comprise at least part of the transaction, and

wherein the first device has fewer processing resources compared to the second device.

20. A method for handling a transaction, comprising:

receiving a Universal Plug and Play (UPnP) event that indicates that a first action has been performed with respect to a device that serves a first role;

logging the event to provide a logged event; and

performing a second action associated with the logged event at a device that serves a second role, wherein the second action advances a the transaction that includes the first action as part thereof.