Notifications Platform

• US 20110314064A1
• Filed: 06/16/2010
• Published: 12/22/2011
• Est. Priority Date: 06/16/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Jeyaseelan, Thomas Anand, Weinberg, Kerstin, Parameshwar, Suresh, Mukunthu, Deepak B., Marrs, Brad Michael, Cunningham, Andrew E.
• Application Number:
  US12/816,402
• Publication Number:
  US 20110314064A1
• Time in Patent Office: Days
• US Class Current: 707/803
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases

Abstract

Described is a notifications platform that routes notifications to endpoints of recipients, corresponding to email, instant messaging, text messaging, telephones, social networks, blogs and/or the like. A publisher of a notification designates the recipients, while preference data of each recipient determines whether that publisher is able to send to that recipient, and if so, to which endpoints. The notification may be modified via one or more templates to be appropriate for a locale of the recipient, as well as appropriately formatted for the endpoint, which may also be locale-specific.

Claims

1. In a computing environment, a system comprising, a notifications platform that receives sets of notification data corresponding to notifications that are capable of being directed towards one or more potential recipients, and for each set of notification data:

accesses a preference data store to determine whether each potential recipient is an actual recipient to be sent the notification; and

for each actual recipient, determines an endpoint set comprising at least one endpoint corresponding to the actual recipient, and for each endpoint in the endpoint set, formats a notification payload for that endpoint and sends the notification payload to that endpoint.

2. The system of claim 1 wherein for each event corresponding to a notification, the notifications platform processes event data associated with that event into a notification data structure, the notification data structure comprising, a notification identifier, a publisher, a recipient set that identifies each of the one or more recipients, and custom data.

3. The system of claim 2 wherein the notification identifier comprises an application identifier, a change type and a scenario.

4. The system of claim 1 wherein the notifications platform includes an asynchronous queue that maintains at least some of the notifications as enqueued notifications, the notifications platform deleting at least some of the enqueued notifications, or processing at least some of the enqueued notifications before dequeuing.

5. The system of claim 1 wherein at least some of the sets of data corresponding to notifications comprise client events, and wherein the notifications platform includes a client library entrypoint for receiving the events, or an API entrypoint for receiving at least some of the sets of data, including sets of data from external web services, or wherein the notifications platform includes both a client library entrypoint for receiving the events and an API entrypoint for receiving at least some of the sets of data.

6. The system of claim 1 wherein the preference store comprises a set of zero or more notifications service instances for each potential recipient, each notifications service instance corresponding to a notifications scenario and comprising zero or more roles, each role corresponding to an endpoint.

7. The system of claim 1 wherein the notification includes an application identifier, a change type, wherein the platform notifications selects a notifications template based upon the application identifier and the change type to obtain layout properties, and wherein the notifications platform formats the notification payload using the layout properties and a UI template selected for the endpoint.

8. The system of claim 7 wherein the notifications template is selected based upon a locale associated with the actual recipient, or wherein the UI template is selected based upon a locale associated with the endpoint, or wherein both the notifications template is selected based upon a locale associated with the actual recipient and the UI template is selected based upon a locale associated with the endpoint.

9. The system of claim 1 wherein the endpoint set includes an e-mail endpoint, an SMS endpoint, an instant message endpoint, or an outside entity endpoint, or any combination of an e-mail endpoint, an SMS endpoint, an instant message endpoint, or an outside entity endpoint.

10. The system of claim 1 wherein the notification payload is sent to a recipient, and wherein the notifications platform includes an incoming notifications pipeline that receives a reply from the recipient that received the notification payload, the incoming notifications pipeline determining to which notification the reply is associated based upon metadata associated with the reply, and processing the reply based upon the notification associated with that reply.

11. In a computing environment, a method performed on at least one processor comprising:

processing notification data that identifies a publisher, a recipient set comprising one or more potential recipients for receiving a notification corresponding to the notification data, and type information of the notification data; and

for each potential recipient, accessing preference data associated with that recipient to determine based upon the publisher and type information whether the notification is allowed to be sent to that recipient, and if so, determining from the preference data an endpoint set comprising one or more endpoints to which the notification is able to be sent.

12. The method of claim 11 wherein the type information comprises a scenario for the notification data, wherein accessing the preference data includes determining a selected scenario from the type information and locating one or more roles for the selected scenario, each role corresponding to an endpoint and including information that identifies whether the publisher is allowed to publish to that endpoint.

13. The method of claim 11 further comprising, sending the notification to an endpoint, receiving data and metadata corresponding to a reply from the endpoint, and using the metadata to associate the reply with the notification.

14. The method of claim 11 further comprising, accessing the preference data associated with a recipient to determine based on one or more conditions whether the notification is able to be sent to that recipient.

15. The method of claim 14 wherein accessing the preference data associated with a recipient to determine based on one or more conditions whether the notification is able to be sent to that recipient, comprises determining whether the endpoint is in a quiet time.

16. One or more computer-readable media having computer-executable instructions, which when executed perform steps, comprising:

(a) processing a notification directed to a recipient and an endpoint of that recipient, including;

(i) determining a notifications template based upon information associated with the notification and locale information associated with the recipient;

(ii) using the notifications template and the information associated with the notification to obtain layout properties for that notification;

(iii) determining a UI template based upon the endpoint; and

(iv) using the UI template and the layout properties to obtain a notification payload;

and

(b) sending the notification payload to the endpoint of the recipient.

17. The one or more computer-readable media of claim 16 wherein determining a UI template based upon the endpoint includes selecting the UI template based upon the locale information.

18. The one or more computer-readable media of claim 16 having computer-executable instructions, comprising, receiving data and metadata corresponding to a reply from the endpoint, and using the metadata to associate the reply with the notification.

19. The one or more computer-readable media of claim 16 having computer-executable instructions, comprising, determining the recipient and the endpoint, including accessing preference data associated with that recipient, determining from the preference data that the notification is allowed to be sent to that recipient based upon a publisher of the notification and type information of the notification, and selecting the endpoint for that publisher and the type information.

20. The one or more computer-readable media of claim 19 wherein the type information comprises a scenario for the notification data, wherein accessing the preference data includes determining a selected scenario from the type information and locating a role for the selected scenario that corresponds to the endpoint, the role including information that identifies whether the publisher is allowed to publish to that endpoint.