Monitoring and controlling electronic message distribution

• US 20080140826A1
• Filed: 03/12/2007
• Published: 06/12/2008
• Est. Priority Date: 12/08/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Liao, Yi, Bolinger, Stephen, Roman, Todd, Galey, Lance, Pearson, Malcolm Erik, McColgan, Charles, Jhawar, Amit, Levy, Marc
• Application Number:
  US11/684,929
• Publication Number:
  US 20080140826A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A method for controlling a message distribution process comprising a series of coordinated processes by monitoring the performance of each process, determining that a monitored process is not processing properly, and skipping the process not processing properly. Another method for controlling the load of message traffic by determining the performance of a message server and altering the flow of messages based upon the determined performance of the message server. Another method for routing messages by identifying the addresses of senders of received messages, assigning a portion of the addresses to a category, and routing messages from the identified addresses according to their assigned category.

Claims

1. A method for controlling a message distribution process comprising a series of coordinated processes, said method comprising:

monitoring the performance of each of said series of coordinated processes;

determining that at least one of said monitored series of coordinated processes is not processing properly;

skipping said at least one of said monitored series of coordinated processes that is determined not to be processing properly.

2. A method as set forth in claim 1 wherein said determining that at least one of said monitored series of coordinated processes is not processing properly comprises determining that at least one of said monitored series of coordinated processes is at least one of failing to process and processing for longer than a maximum time limit.

3. A method as set forth in claim 1 further comprising reinstating said at least one skipped process after a skipping period has elapsed, said skipping period beginning at the time the process was first skipped.

4. A method as set forth in claim 1 further comprising:

weighting each of said processes of said monitored series of coordinated processes;

calculating the collective weight of all the processes being monitored, wherein said skipping comprises skipping only those processes having a total weight less than a difference between the collective weight and a minimum weight;

assigning each of said processes to a category; and

assigning a minimum collective weight to each of said categories, wherein said skipping comprises skipping a process only when said process has a weight less than the difference between a collective weight of the processes in its category currently being processed and a minimum collective weight for the category.

5. A method for controlling the load of message traffic processed by two or more message servers, said method comprising:

determining the performance of at least one of said two or more message servers; and

altering the flow of messages to the at least one message server based upon the determined performance without user intervention.

6. A method as set forth in claim 5 wherein said altering the flow of messages to the at least one message server comprises enabling a load balancer to alter the flow of messages based upon said determined performance without user intervention.

7. A method as set forth in claim 6 wherein said altering the flow of messages to the at least one message server comprises enabling a load balancer to allocate the flow of messages among two or more data centers, each comprising two or more message servers, based upon said determined performance without user intervention, such that each of the data centers exhibits substantially the same overall performance.

8. A method as set forth in claim 6 wherein said altering the flow of messages to the at least one message server comprises enabling a load balancer to allocate the flow of messages among the two or more message servers based upon said determined performance without user intervention, such that each of the message servers exhibits substantially the same overall performance.

9. A method as set forth in claim 5 wherein said altering the flow of messages to the at least one message server comprises changing the flow of messages to the message server when the determined performance meets a performance criteria.

10. A method as set forth in claim 9 wherein said altering the flow of messages to the at least one message server comprises decreasing the flow of messages to the message server when the determined performance is at or below an underperforming criteria.

11. A method as set forth in claim 10 wherein said altering the flow of messages to the at least one message server further comprises increasing the flow of messages to the message server when the determined performance increases from at or below the underperforming criteria to above the underperforming criteria.

12. A method as set forth in claim 10 wherein said altering the flow of messages to the at least one message server comprises stopping the flow of messages to the message server when the determined performance is at or below an unacceptable criteria and restarting the flow of messages to the message server when the determined performance increases from at or below the unacceptable criteria to above the unacceptable criteria.

13. A method as set forth in claim 5 wherein said determining the performance of a message server comprises at least one of determining the number of messages currently being processed by the message server, the latency of the messages in making a call, the latency of the queue of messages, the length of time a single message takes to be processed by the message server, the number of steps the message server skips in processing the messages, the number of crashes realized by the message server, the number of faults realized by the message server, and the amount of memory being consumed by the message server.

14. A method for routing messages through message routing resources according to the party associated with the message, said method comprising:

identifying the addresses of senders of all messages received by a set of users within a time period;

assigning at least a portion of the identified sender addresses to a category; and

routing messages from said identified sender addresses assigned to a category through the message routing resources according to their assigned category.

15. A method as set forth in claim 14 wherein said assigning comprises assigning at least a portion of the identified sender addresses to a category according to their desirability as a sender.

16. A method as set forth in claim 15 wherein said assigning at least a portion of the identified sender addresses to a category comprises assigning sender addresses of those senders who sent at least N number of messages that no recipient identified as undesirable in a desirable category.

17. A method as set forth in claim 16 wherein said routing messages further comprising routing messages from sender addresses assigned to the desirable category through at least one of a different filtering process and a different message routing resource than messages from sender addresses not assigned to the desirable category.

18. A method as set forth in claim 17 wherein said routing messages further comprises monitoring the flow of messages from sender addresses assigned to the desirable category;

and

allocating routing resources such that the flow of messages from sender addresses assigned to the desirable category remains above a minimum flow threshold

19. A method as set forth in claim 17 wherein said routing messages from sender addresses assigned to the desirable category through at least one of a different filtering process and a different routing resource comprises routing such messages through at least one of a less rigorous filtering process and one or more message routing resources dedicated to deliver only such messages.

20. A method as set forth in claim 16 further comprising identifying the addresses of recipients of all messages sent by a set of users;

assigning each of the identified recipient addresses to the desirable category; and

routing messages from sender addresses and recipient addresses assigned to the desirable category through at least one of a different filtering process and a different message routing resource than messages from sender addresses not assigned to the desirable category.