Content based message dispatch

• US 20030212818A1
• Filed: 05/08/2002
• Published: 11/13/2003
• Est. Priority Date: 05/08/2002
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Klein, Johannes, Elien, Jean-Emile, Saha, Sanjib, Graber, Lee, Mehta, Bimal Kumar
• Application Number:
  US10/141,464
• Publication Number:
  US 20030212818A1
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Systems and methodologies are disclosed to facilitate for routing messages in a communications framework, which can include one or more computers. Determinations as to whether and where to route messages are based at least in part upon the content of messages. Services interested in receiving messages specify one or more subscriptions, which are employed to make routing decisions for messages. The subscriptions are evaluated relative to messages, and more particularly content based message properties of respective messages, to determine whether and where to route messages.

Claims

1. A system to facilitate routing of messages, comprising:

at least one filter associated with a service, the at least one filter including filter criteria indicative of message content; and

a dispatch engine operative to receive a message and to route the message to the service based on at least some content of the message satisfying the filter criteria.

2. The system of claim 1 further comprising a plurality of filters, each having properties specified by one of a plurality of respective services, the properties being specified based on message content.

3. The system of claim 2, the dispatch engine correlating the message relative to at least some of the plurality of filters to discern whether to route the message to a service associated with a respective one of the at least some of the plurality of filters.

4. The system of claim 2, the message further comprising a set of properties derived based at least in part on the content of the message, the dispatch engine evaluating the plurality of filters relative to the message properties.

5. The system of claim 4, the message further comprising another set of message properties that restrict which filters are applied to the message.

6. The system of claim 1, further comprising a service queue associated with the at least one filter, the service queue being operative to receive messages from the dispatch engine that satisfy that at least one filter, such that the associated service can access the messages.

7. The system of claim 1, further comprising a filter generator invocable by the associated service to create the at least one filter by specifying what attributes of message content are sufficient to indicate that the dispatch engine is to route a given message to the associated service.

8. The system of claim 1, the filter criteria further comprising at least one identifier that corresponds to a predefined message property and a value associated with the at least one identifier.

9. The system of claim 1, the at least one filter further comprising at least one predicate that must be satisfied by the message to satisfy the filter.

10. The system of claim 9, the at least one predicate further comprising an identifier and associated value related to the identifier by an operator.

11. The system of claim 10, further comprising at least one conjunct that includes the at least one predicate to define a condition that can be satisfied to satisfy the filter criteria.

12. The system of claim 9, the at least one filter further comprising an associated action that is implemented by the dispatch engine in response to the message satisfying the at least one predicate of the at least one filter, whereby the at least one filter defines a condition-action pair.

13. The system of claim 12, the at least one filter further comprising an expression that includes a plurality of predicates in disjunctive form, each of the plurality of predicates comprising a property identifier, a value and a particular relationship between the property identifier and the respective value.

14. The system of claim 13, the expression further comprising at least one Boolean expression.

15. The system of claim 1, the at least one filter further comprising multiple filter phases associated with the service, the dispatch engine applying a first of the filter phases operative to identify if the message is a potential match for the service, and if the message satisfies the first filter phase, then applying at least another of the filter phases.

16. The system of claim 1, the message comprising message properties derived from and indicative of at least some of the content of the message, the dispatch engine evaluating the message properties relative to the filter criteria and providing the message to the service based on the evaluation.

17. The system of claim 16, further comprising a message service that parses an incoming message and extracts the message properties based at least in part on content of the incoming message, the message service posting the message including the message properties to a message space for evaluation relative to the least one filter.

18. The system of claim 17, the message service further extracting the message properties based on transport information in the incoming message.

19. The system of claim 17, the posted message being stored in the message space according to a common internal representation to facilitate evaluation relative to the at least one filter.

20. The system of claim 17, the extracted message properties being predefined by the service.

21. The system of claim 17, further comprising a plurality of filters, each of the plurality of filters having properties specified by one of a plurality of respective services to identify selected message content, the dispatch engine evaluating the message relative to at least some of the plurality of filters and providing the message to each service associated with a filter satisfied by the message.

22. The system of claim 21, the message properties defining a first set of message properties, the message further comprising a second set of properties that restricts which of the plurality of filters can be evaluated relative to the message.

23. The system of claim 16, each of the message properties further comprising an identifier-value pair, in which the identifier defines a property by name and the value identifies an associated value for the named property.

24. The system of claim 1, the at least one filter further comprising a plurality of filters having properties specified by respective services to identify selected message content, at least some of the plurality of filters being dynamically created and deleted at runtime.

25. The system of claim 1, further comprising a locking component associated with the service to acquire an instance lock between the message and an instance of the service if the message satisfies the at least one filter associated with the service and the dispatch engine provides the message to a queue for processing by the instance of the service, whereby the instance lock facilitates retrieval of relevant data for processing the message by the instance of the service.

26. The system of claim 25, the instance lock comprising instance data based on properties of the message to inhibit concurrent access to the message associated with a single service instance.

27. A system to facilitate routing of messages, comprising:

means for accessing a message that includes a message body and a message context, the message context having message properties based at least in part on content of the message body;

means for evaluating the message properties of the message relative to at least one subscription having filter criteria specified by at least one respective service; and

means for routing the message to the at least one respective service based on at least some of the message properties satisfying the filter criteria of the subscription.

28. The system of claim 27, the at least one respective service including a plurality of services, each of the plurality of services having a respective subscription used by the means for evaluating the message.

29. The system of claim 28, further comprising means for restricting relative to which of the plurality of subscriptions the message is evaluated

30. The system of claim 27, further comprising means for storing the message in response to the message satisfying the filter criteria to facilitate processing of the stored message by the one respective service.

31. The system of claim 30, further comprising means for locking the message relative to the one respective service to inhibit concurrent access to the message associated with a single instance of the one respective service, the means for locking being based on properties of the message.

32. The system of claim 27, further comprising means for extracting properties of the message based at least in part on the content of the message body and for storing a representation of the message that includes the extracted properties separately from and associated with other information of the message.

33. The system of claim 27, further comprising means for applying a first part of the filter criteria to ascertain whether the message is a potential match for the at least one service, and means for applying at least another part of the filter criteria provided that the message satisfies the part of the filter criteria.

34. The system of claim 27, further comprising means for at least one of dynamically creating and deleting subscriptions that have filter criteria specified by respective services, the means for evaluating further evaluating the message properties of the message relative to at least some of the subscriptions to determine if the message should be routed to any services associated with the at least some of the subscriptions.

35. A system to facilitate routing of messages, comprising:

means for receiving an incoming message and extracting properties of the message based at least in part on content of the message and storing a representation of the message that includes the extracted properties associated with other information of the message;

means for evaluating the extracted properties of the message relative to filter criteria specified by at least one associated service; and

means for routing the representation of the message to the associated service based on at least some of the extracted properties satisfying the filter criteria.

36. A method to facilitate dispatching messages, comprising:

accessing a message that includes a message body and a message context having message properties based at least in part on content of the message body;

evaluating the accessed message relative to at least one filter associated with a service, the at least one filter including filter criteria indicative of message content; and

routing the accessed message to the service based on at least some of the message properties satisfying the filter criteria.

37. The method of claim 36, the at least one filter further comprising a plurality of filters, each of the plurality of filters having properties specified by one of a plurality of respective services based on message content, the method further comprising:

evaluating the accessed message relative to at least some of the plurality of filters; and

providing the accessed message to each service associated with a filter satisfied by the message.

38. The method of claim 37, the evaluating further comprising correlating the properties of the accessed message relative to at least some of the plurality of filters to discern whether to route the accessed message to a service associated with a respective the least some of the plurality of filters.

39. The method of claim 37, further comprising parsing an incoming message having content and deriving a set of properties that define the properties of the accessed message based at least in part on the content of the incoming message.

40. The method of claim 39, further comprising restricting which of the plurality of filters are evaluated relative to accessed message according to another set of properties associated with the accessed message.

41. The method of claim 39, further comprising deriving the message properties based on transport information in the incoming message.

42. The method of claim 39, further comprising posting the accessed message in a message space according to a predetermined schema to facilitate evaluation of the accessed message relative to the at least one filter.

43. The method of claim 39, each of the properties in the set of properties being selected from a set of properties predefined by the service.

44. The method of claim 36, the routing further comprising storing the accessed message in a queue if the accessed message satisfies the filter criteria so as to facilitate processing of the message by the service.

45. The method of claim 44, further comprising locking the stored message relative to the one respective service to inhibit concurrent access to the store associated with a single instance of the one respective service, the locking being based on properties of the accessed message.

46. The method of claim 36, the filter criteria further comprising an expression that specifies property names, property values, and relationships of the property names relative to respective property values that are required for the accessed message to satisfy the filter criteria.

47. The method of claim 36, the method further comprising:

evaluating a first part of the filter criteria relative to the accessed message to identify if the accessed message is a potential match for the service; and

if the accessed message satisfies the first part of the filter criteria, evaluating at least another of the part of the filter criteria relative to the accessed message.

48. The method of claim 36, further comprising at least one of dynamically creating and deleting subscriptions that have filter criteria specified by respective services, the properties of the accessed message being evaluated relative to at least some of the subscriptions to determine if the message should be routed to any services associated with the at least some of the subscriptions.

49. A computer readable medium having computer executable instructions for:

accessing a message that includes a message body and a message context having message properties based at least in part on content of the message body;

evaluating the accessed message relative to at least one filter associated with a service, the at least one filter including filter criteria indicative of message content; and

routing the accessed message to the service based on at least some of the message properties satisfying the filter criteria.