Scalable notification delivery service

• US 7,024,459 B2
• Filed: 02/28/2002
• Issued: 04/04/2006
• Est. Priority Date: 02/28/2002
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Serdy, Frank Stephen, McNamara, Donald James
• Primary Examiner(s): Prieto, Beatriz
• Assistant Examiner(s): Meucci, Michael D.
• Application Number:
  US10/086,792
• Publication Number:
  US 20030163533A1
• Time in Patent Office: 1,496 Days
• Field of Search: 709/203, 709/206, 709/238
• US Class Current: 709/206
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A notification service that efficiently scales to the number and variety of notifications and users being serviced. The notification service is separated into three general functional components. A listener component receives a notification in a network format suitable for transmitting the notification over a network. The listener component translates the notification into an internal processing format used by the notification service. The notification is then forwarded to a routing component that determines a category associated with the notification, and performs a set of one or more operations on the notification based on its category. Finally, the notification service is forwarded to a delivery service for delivery of the notification to the notification sink. The listener component, the routing component, and the delivery component may each be scaled in order to adjust for current processing loads using load balancing functionality.

Claims

1. In a network environment comprised of one or more computer or devices such as mobile devices that serve as notification sources, meaning that such computer or devices serve as sources where notifications are generated in response to an event, such notifications being generated in a network format comprised of an XML document included within an HTTP post request or included with a SOAP message that is included within an HTTP post request, and wherein the network is also comprised of one or more computers or devices that serve as notification sinks, meaning that such computer or devices serve as destinations on the network where the generated notifications are to be sent, a method for delivering such notifications from a notification service that scales the notifications to the number and variety of notification sources and notification sinks at the time such notifications are generated and delivered, the method comprising:

(a) receiving, at a listening component of the delivery service, a notification generated by a notification source in a network format comprised of an XML document included within an HTTP post request, notification content of the notification being structured within the XML document that identifies data including a category of notification and transform operations associated with the category that may be performed on notifications of the particular category;

(b) translating the notification into an internal processing format

(c) forwarding the translated notification to a routing component of the notification service where categorizations of notifications that may be received are stored in an XML configuration document, wherein each of the categories has associated transform operations that may be performed for that category;

(d) referencing the XML configuration document at the routing component to determine a category associated with the notification and performing at the routing component one or more of the associated transform operations on the notification content of the XML document;

(e) forwarding the notification from the routing component to a delivery component of the notification service for delivery to the notification sinks of the network;

(f) changing the XML configuration document at the router by adding or deleting nodes of the XML document to add or delete different categories of notifications, and editing transform operations consistent with the added or deleted categories; and

(g) repeating parts (a) through (e) for any subsequent notification corresponding to the changed categories of notifications.

2. The method of claim 1, wherein the listener component of the notification service receives the notification from a wireless device.

3. The method of claim 2, further comprising:

an act of delivering the notification to a mobile service provider.

4. The method of claim 1, wherein the listener component of the notification service receives the notification from a mobile service provider.

5. The method of claim 4, further comprising:

an act of delivering the notification to a wireless device.

6. The method of claim 1, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is an instant message.

7. The method of claim 1, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

an act of failing to detect any category associated with the notification; and

an act of determining that the notification is of a default category based on the failure to detect any category associated with the notification.

8. The method of claim 1, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is a buddy list-related notification.

9. The method of claim 1, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is a news-related notification.

10. The method of claim 1, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is a mobile-originated notification.

11. The method of claim 1, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

determining whether to check that the notification should be muted.

12. The method of claim 1, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

accessing a user profile associated with a sender or receiver of the notification.

13. The method of claim 1, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

authenticating the notification by verifying whether a user account is disabled or authorized.

14. The method of claim 1, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

inserting an advertisement into the notification.

15. The method of claim 1, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

formatting the notification for the notification sink.

16. The method of claim 1, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

determining whether a user has exceeded a message limit.

17. The method of claim 1, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

determining the transform operations to perform based on the category.

18. The method of claim 17, further comprising an act of determining the order of operations to perform based on the category.

19. The method of claim 1, further comprising a step for scaling the notification service in order to take into account the changes in the number of notification sources or notification sinks on the network, the scaling being performed by:

providing the listener, routing, and delivery components of the notification service with a plurality of identical modules for performing the functions of the listener, routing, and delivery components;

providing each of the listener, routing, and delivery components with a load balancing function that distributes a received notification to one of the modules of that component; and

changing the number of modules at one or more of the listener, routing, and delivery components in order to take into account changes in the number of notification sources or notification sinks on the network.

20. In a network environment comprised of one or more computer or devices such as mobile devices that serve as notification sources, meaning that such computer or devices serve as sources where notifications are generated in response to an event, such notifications being generated in a network format comprised of an XML document included within an HTTP post request or included with a SOAP message that is included within an HTTP post request, and wherein the network is also comprised of one or more computers or devices that serve as notification sinks, meaning that such computer or devices serve as destinations on the network where the generated notifications are to be sent, a computer program product for implementing a method for delivering such notifications from a notification service that scales the notifications to the number and variety of notification sources and notification sinks at the time such notifications are generated and delivered, the method comprising:

(a) receiving, at a listening component of the delivery service, a notification generated by a notification source in a network format comprised of an XML document included within an HTTP post request, notification content of the notification being structured within the XML document that identifies data including a category of notification and transform operations associated with the category that may be performed on notifications of the particular category;

(b) translating the notification into an internal processing format

(c) forwarding the translated notification to a routing component of the notification service where categorizations of notifications that may be received are stored in an XML configuration document, wherein each of the categories has associated transform operations that may be performed for that category;

(d) referencing the XML configuration document at the routing component to determine a category associated with the notification and performing at the routing component one or more of the associated transform operations on the notification content of the XML document;

(e) forwarding the notification from the routing component to a delivery component of the notification service for delivery to the notification sinks of the network;

(f) changing the XML configuration document at the router by adding or deleting nodes of the XML document to add or delete different categories of notifications, and editing transform operations consistent with the added or deleted categories; and

(g) repeating parts (a) through (e) for any subsequent notification corresponding to the changed categories of notifications.

21. The computer program product of claim 20, wherein the listener component of the notification service receives the notification from a wireless device.

22. The computer program product of claim 21, further comprising:

an act of delivering the notification to a mobile service provider.

23. The computer program product of claim 20, wherein the listener component of the notification service receives the notification from a mobile service provider.

24. The computer program product for implementing the method of claim 23, further comprising:

an act of delivering the notification to a wireless device.

25. The computer program product of claim 20, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is an instant message.

26. The computer program product of claim 20, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

an act of failing to detect any category associated with the notification; and

an act of determining that the notification is of a default category based on the failure to detect any category associated with the notification.

27. The computer program product of claim 20, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is a buddy list-related notification.

28. The computer program product of claim 20, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is a news-related notification.

29. The computer program product of claim 20, wherein the act of referencing the configuration XML document at the routing component to determine a category associated with the notification comprises:

determining that the notification is a mobile-originated notification.

30. The computer program product of claim 20, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

determining whether to check that the notification should be muted.

31. The computer program product of claim 20, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

accessing a user profile associated with a sender or receiver of the notification.

32. The computer program product of claim 20, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

authenticating the notification by verifying whether a user account is disabled or authorized.

33. The computer program product of claim 20, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

inserting an advertisement into the notification.

34. The computer program product of claim 20, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

formatting the notification for the notification sink.

35. The computer program product of claim 20, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

determining whether a user has exceeded a message limit.

36. The computer program product of claim 20, wherein the act of performing one or more transform operations on the notification content based on the category associated with the notification comprises:

determining the transform operations to perform based on the category.

37. The computer program product of claim 36, further comprising an act of determining the order of operations to perform based on the category.

38. The computer program product of claim 20, further comprising a step for scaling the notification service in order to take into account the changes in the number of notification sources or notification sinks on the network, the scaling being performed by:

providing the listener, routing, and delivery components of the notification service with a plurality of identical modules for performing the functions of the listener, routing, and delivery components;

providing each of the listener, routing, and delivery components with a load balancing function that distributes a received notification to one of the modules of that component; and

changing the number of modules at one or more of the listener, routing, and delivery components in order to take into account changes in the number of notification sources or notification sinks on the network.