Intelligent work load manager

• US 8,621,074 B2
• Filed: 04/27/2012
• Issued: 12/31/2013
• Est. Priority Date: 04/27/2012
• Status: Active Grant

• Current Assignee: Grant Rodolph, III Holdings 6, LLC (Intellectual Ventures LLC)
• Original Assignee: Xerox Business Services, LLC (Conduent, Inc.)
• Inventors: Shikari, Faiyaz, Matta, Madhav, Venkatesan, Suresh
• Primary Examiner(s): Nguyen, Tammy
• Application Number:
  US13/458,327
• Publication Number:
  US 20130290513A1
• Time in Patent Office: 613 Days
• Field of Search: 709/224, 709/220, 709/226, 710/74, 710/33, 711/114
• US Class Current: 709/224
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• 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

Abstract

A management system for processing message-based communications comprising a plurality of servers configured to implement a plurality of sessions that process a plurality of messages, a plurality of message queues coupled to the servers and configured to exchange the messages with the servers, and a workload manager coupled to the servers and the message queues and configured to reallocate the sessions to the different servers and the corresponding message queues to achieve load balance between the servers and the message queues in a recurring manner during processing of the messages by the servers based on a depth of each of the message queues, a quantity of sessions for each of the servers, and a workload manager configuration.

Claims

1. A management system for processing message-based communications comprising:

a plurality of servers configured to implement a plurality of sessions that process a plurality of messages;

a plurality of message queues coupled to the servers and configured to exchange the messages with the servers; and

a workload manager coupled to the servers and the message queues and configured to reallocate the sessions to the different servers and the corresponding message queues to achieve load balance between the servers and the message queues in a recurring manner during processing of the messages by the servers based on a depth of each of the message queues, a quantity of sessions for each of the servers, and a workload manager configuration, wherein the workload manager configuration indicates a threshold percentage of queue depth per queue with respect to the quantity of sessions associated with the queue that triggers a redistribution of sessions if reached.

2. The management system of claim 1, wherein the workload manager configuration is updatable during processing of the sessions by the servers.

3. The management system of claim 1, wherein the workload manager configuration further indicates a list of the servers and a list of the message queues to be monitored.

4. The management system of claim 1, wherein the workload manager configuration further indicates a recurring monitoring interval for assessing the depth of each of the message queues and the quantity of sessions for each of the servers to determine the allocation of the sessions.

5. The management system of claim 1, wherein the workload manager configuration further indicates a recommended maximum number of sessions for transfer per server and a recommended minimum number of sessions that are kept per server.

6. The management system of claim 1, wherein the workload manager configuration further indicates a percentage of sessions that is allowed to be transferred per server in one instance.

7. The management system of claim 1, wherein the messages comprise a plurality of healthcare institutional claims, a plurality of healthcare professional claims, and a plurality of healthcare dental claims, wherein the servers comprise a first server for processing the healthcare institutional claims, a second server for processing the healthcare professional claims, and a third server for processing the healthcare dental claims, and wherein the message queues comprise a first queue associated with the first server and the healthcare institutional claims, a second queue associated with the second server and the healthcare professional claims, and a third queue associated with the third server and the healthcare dental claims.

8. An application for healthcare claims management comprising a plurality of instructions that cause a processor to:

obtain a plurality of parameters including a server list, a message queue list, a plurality of threshold settings, and a monitoring interval, wherein the threshold settings comprise a recommended minimum number of sessions to be allocated per server, a recommended maximum number of sessions for transfer per server, a percentage of the sessions that is allowed for transfer at one instance between servers, and a percentage of queue depth that when reached triggers a transfer of the sessions;

monitor a plurality of servers indicated in the server list and a plurality of message queues coupled to the servers and indicated in the message queue list at each recurring monitoring interval; and

reallocate a plurality of sessions implemented on the servers and associated with the message queues based on the quantity of sessions on each of the servers, the depth of each of the message queues, and the threshold settings.

9. The application of claim 8, wherein the instructions further cause the processor to move a plurality of sessions of a monitored queue if a percentage of the depth of the monitored queue with respect to a number of sessions associated with the monitored queue is less than or about equal to the percentage of queue depth of the threshold settings.

10. The application of claim 9, wherein the relation (((asCount−

mqDepth)/asCount)*100)>

freeQueueDepthPercent is used to determine whether to move the sessions, where asCount is the number of sessions, mqDepth is the depth of the monitored queue, and freeQueueDepthPercent is the percentage of queue depth of the threshold settings.

11. The application of claim 9, wherein the instructions further cause the processor to move the sessions of a monitored server that is associated with the monitored queue if the product of a number of sessions on the monitored server and the percentage of the sessions that is allowed for transfer at one instance between servers is greater than a determined maximum allowed number of sessions for transfer per server.

12. The application of claim 11, wherein the relation aCount−

availableAS>

minASTransfer is used to determine whether to move the sessions, where availableAS=(maxASTransferPercent*asCount)/100, maxASTransferPercent is the percentage of the sessions that is allowed for transfer at one instance between servers, and asCount is the number of sessions on the monitored server.

13. The application of claim 9, wherein the instructions further cause the processor to move a plurality of sessions from one or more first monitored servers to a second monitored server if a percent of the depth of a monitored queue associated with the second server with respect to a number of sessions associated with the monitored queue is greater than or about equal to the percentage of queue depth of the threshold settings.