Techniques to manage remote events

Patent metadata

Field	Value
Publication number	US-9324055-B2
Application number	US-201113314428-A
Country	US
Kind code	B2
Filing date	Dec 8, 2011
Priority date	Dec 8, 2011
Publication date	Apr 26, 2016
Grant date	Apr 26, 2016

Abstract

Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.

First claim

The invention claimed is:

1. An apparatus, comprising:
a processor circuit; and
a remote event application operative on the processor circuit to manage remote event notifications between a publisher entity and a subscriber entity, the remote event application comprising:
an event monitor component operative to:
receive an external event notification message identifying a publisher entity event, wherein the publisher entity event is an update to data stored in a data source maintained by the publisher entity, wherein the publisher entity is remote from the apparatus and the subscriber entity;
select a custom event receiver component corresponding to the publisher entity from among multiple custom event receiver components, wherein the selected custom event receiver component comprises at least one code callout for performing at least one operation; and
send the external event notification message to the selected custom event receiver component;

the selected custom event receiver component operative to:
automatically invoke the code callout to perform at least one operation, wherein the at least one operation is responsive to the publisher entity event; and

an event notification component operative to:
send a client event notification message to the subscriber entity upon performing the at least one operation, wherein the subscriber entity is not in direct communication with the publisher entity.

2. The apparatus of claim 1 , the event monitor component comprising a representational state transfer (REST) based input point.

3. The apparatus of claim 1 , the data source corresponding to an external application of the publisher entity.

4. The apparatus of claim 3 , the publisher entity event comprising a change in state of the data stored by the data source for the external application.

5. The apparatus of claim 1 , the event monitor component operative to select the custom event receiver component for the external event notification message based on a globally unique identifier (GUID) for the publisher entity associated with the external event notification message.

6. The apparatus of claim 1 , wherein the code callout is arranged to perform custom logic in response to the publisher entity event.

7. The apparatus of claim 1 , the event notification component further operative to retrieve a notification parameter associated with the subscriber entity, and send the client event notification message to a client application associated with the subscriber entity, wherein the subscriber entity subscribes to the publisher entity.

8. The apparatus of claim 1 , the remote event component comprising an event management component operative to manage a subscription between the publisher entity and the subscriber entity.

9. The apparatus of claim 8 , the event management component operative to manage a level of reliability for external event notification messages.

10. The apparatus of claim 8 , the event management component operative to retrieve a reliability parameter representing a reliability level associated with the publisher entity, and process the external event notification message based on the reliability parameter.

11. The apparatus of claim 10 , comprising a set of message handling parameters associated with the reliability parameter, the message handling parameters comprising a duplicate message parameter, a standby server parameter, or a replay parameter, the duplicate message parameter indicating whether to accept or reject duplicate external event notification messages received from the external application, the standby server parameter indicating whether to send the external event notification message to a standby server when a primary server is non-operational, and the replay parameter indicating whether to replay the external event notification message when the event monitor component detects an error condition when processing the external event notification message.

12. A computer-implemented method, comprising:
receiving, at a second server device, an external event notification message identifying a publisher entity event, wherein the publisher entity event is an update to data stored by a publisher entity, wherein the publisher entity operates from a first server device that is remote from the second server device;
selecting, at the second server device, a custom event receiver component corresponding to the publisher entity from among multiple custom event receiver components, wherein the selected custom event receiver component comprises at least one code callout for performing at least one operation;
sending the external event notification message to the selected custom event receiver component at the second server device, wherein the selected custom event receiver component automatically invokes the code callout to perform the at least one operation, wherein the at least one operation is responsive to the publisher entity event; and
upon performing the at least one operation, sending a client event notification message from the second server device to a subscriber entity operating on a client device, wherein the subscriber entity is not in direct communication with the publisher entity.

13. The computer-implemented method of claim 12 , comprising selecting the custom event receiver component for the external event notification message based on a globally unique identifier (GUID) for the publisher entity associated with the external event notification message.

14. The computer-implemented method of claim 12 , wherein the code callout is arranged to perform custom logic in response to the publisher entity event.

15. The computer-implemented method of claim 12 , comprising sending the client event notification message as an electronic mail message, a short messaging service (SMS) message, a multimedia messaging service (MMS) message, or a social networking service (SNS) message.

16. An article of manufacture comprising a computer-readable storage medium containing instructions that when executed enable a computer system to:
receive an external event notification message identifying a publisher entity event, wherein the publisher entity event is an update to data stored by the publisher entity;
select a custom event receiver component corresponding to the publisher entity from among multiple custom event receiver components, wherein the selected custom event receiver component comprises at least one code callout for performing at least one operation; and
send the external event notification message to the selected custom event receiver component, wherein the selected custom event receiver component automatically invokes the code callout to perform the at least one operation, wherein the at least one operation is responsive to the publisher entity event; and
upon performing the at least one operation, send a client event notification message to a subscriber entity, wherein the subscriber entity is not in direct communication with the publisher entity.

17. The article of manufacture of claim 16 , further comprising instructions that when executed enable the computer system to:
select the custom event receiver component for the external event notification message based on a globally unique identifier (GUID) for the publisher entity associated with the external event notification message.

18. The article of manufacture of claim 16 , wherein the code callout is arranged to perform custom logic in response to the publisher entity event.

19. The article of manufacture of claim 16 , further comprising instructions that whe

Assignees

• Shah Roma
• Balaji M Vijay
• Nandwani Sharad
• Kamalakumar Pradeep
• Banerjee Atanu
• Singhal Ashish Kumar
• Sunku Suresh
• Microsoft Technology Licensing Llc

Inventors

• Shah Roma
• Balaji M Vijay
• Nandwani Sharad
• Kamalakumar Pradeep
• Banerjee Atanu
• Singhal Ashish Kumar
• Sunku Suresh

Classifications

• H04L67/025

  for remote control or remote monitoring of applications · CPC title

• G06Q10/10 Primary

  Office automation; Time management · CPC title

• H04L51/52

  for supporting social networking services · CPC title

• H04L67/55

  Push-based network services · CPC title

• H04L41/5064

  Customer relationship management · CPC title