MESSAGE REQUIREMENTS BASED ROUTING OF MESSAGES

• US 20100325215A1
• Filed: 06/19/2009
• Published: 12/23/2010
• Est. Priority Date: 06/19/2009
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: de Souza, Jeremy, Luttinen, Todd C., Gourevitch, Gregory, Kay, Jeffrey B., Boctor, Victor, De Graaf, Wilbert, Sanyal, Shubhankar
• Application Number:
  US12/487,656
• Publication Number:
  US 20100325215A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Architecture for enabling messages to be routed between network servers based on message requirements related to version, capabilities, and features, for example. The message requirements designate delivery over a transport path compatible with the message requirements. The message requirements can include a particular version or other features related to different software applications that require compatibility in message handling. Routing information is maintained related to a transport server or other network transport entity compatible with the message requirements and through which the message can be routed. The message is routed to the compatible transport server for delivery to the destination while avoiding delivery to transport servers incompatible with the message requirements.

Claims

1. A computer-implemented message system, comprising:

an input component of a transport server for receiving a message for delivery to a compatible destination, the message having message requirements that designate delivery over a compatible transport path; and

a routing component of the transport server for routing the message over the compatible transport path to the destination according to the message requirements.

2. The system of claim 1, wherein the message requirements include operational features, the message routed over a transport path having compatible operational features.

3. The system of claim 1, wherein the message requirements include server version information, the message routed over a transport path having compatible server versions.

4. The system of claim 1, wherein the message requirements include server capabilities information, the message routed over a transport path having compatible server capabilities.

5. The system of claim 1, further comprising a storage component for maintaining routing information related to transport servers via which the message can be routed.

6. The system of claim 1, further comprising a referral component for referring the message to a compatible server associated with the message requirements.

7. The system of claim 1, further comprising an advertising component for advertising the message requirements to compatible network components.

8. A computer-implemented message system, comprising:

an input component for receiving a message for delivery to a destination, the message having message requirements that designate delivery over a transport path compatible with the message requirements;

a storage component for maintaining routing information related to a network transport entity compatible with the message requirements and via which the message can be routed; and

a routing component for routing the message to the compatible network transport entity for delivery to the destination while avoiding delivery to network transport entities incompatible with the message requirements.

9. The system of claim 8, wherein the message requirements are version information, the message routes only to the compatible network transport entity having the same version information.

10. The system of claim 8, wherein the message requirements relate to software features, the message routed only to network entities having the same software features.

11. The system of claim 8, further comprising routing tables for maintaining message routes along server paths operating with respective compatible message requirements.

12. The system of claim 8, further comprising an exception handling component for routing the message to a different compatible network transport entity in the event of delivery of the message to an incompatible network transport entity.

13. The system of claim 8, further comprising a lookup component of the input component to locate available compatible network transport entities through which the message can be routed.

14. A computer-implemented messaging method, comprising:

receiving a message for delivery to a destination;

examining message requirements of the message;

selecting only a network entity compatible with the message requirements; and

sending the message to the compatible network entity for delivery to the destination.

15. The method of claim 14, further comprising computing that the network entity meets the message requirements based on a compatible software version.

16. The method of claim 14, further comprising computing that the network entity meets the message requirements based on compatible server capabilities.

17. The method of claim 14, further comprising triggering an exception when routing the message to an incompatible network entity.

18. The method of claim 14, further comprising maintaining routing tables of transport entities and mailbox servers on transport paths against which the message requirements can be resolved.

19. The method of claim 14, further comprising referring the message to a network server having compatible message requirements.

20. The method of claim 14, further comprising advertising compatible message requirements to a network server.