System and method for priority scheduling of plurality of message types with serialization constraints and dynamic class switching

• US 8,428,076 B2
• Filed: 03/30/2011
• Issued: 04/23/2013
• Est. Priority Date: 09/13/2010
• Status: Active Grant

• Current Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Original Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Inventors: Mansharamani, Rajesh
• Primary Examiner(s): Ton, Dang
• Assistant Examiner(s): RANDHAWA, MANDISH K
• Application Number:
  US13/076,246
• Publication Number:
  US 20120076152A1
• Time in Patent Office: 755 Days
• Field of Search: 370/412, 370/413, 370/415, 370/419, 370/429, 718103-108
• US Class Current: 370/412
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/4881 Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

The present invention provides a preemptive priority scheduling system and method for optimal load balancing of messages and preserving the lightweight allocation resources in an intersystem communication. The invention also provides a system and method for scheduling of messages of a plurality of classes in an intersystem communication.

Claims

1. A preemptive priority scheduling system providing serialization by dynamic switching of a plurality of messages of a plurality of classes in an intersystem communication, the system comprising of:

an intersystem communication comprising a front office to handle a plurality of predefined first set of business operations and a back office to handle plurality of second set of business operations, the back office receiving a plurality of messages from the front office in a serialized sequence;

a plurality of inbound messages, each message assigned to a pre-identified class, comprising at least one highest priority message, at least one medium priority message and at least one lowest priority message stored in a cache memory of the front office system, wherein each message is assigned with a unique messageid and a class of messages corresponding to at least one pre-identified business activity is assigned a unique baseid;

an input message queue to index the queue with messageid and baseid of at least one message residing therein the cache memory of the front office system;

a plurality of output server processes running on at least one message output server identified by an assigned serverid thereof, wherein each output server process invokes a synchronous service call to fetch at least one message from the cache memory corresponding to the indexed messageid in the input message queue and sending messages in first come first serve order to at least one back office system;

at least one serialization constraint, pre-identified for priority based message scheduling, comprising of fully restrictive, partially restrictive and non restrictive constraints, each constraint allowing to identify priority of each class of the inbound message and subsequent processing thereof by a scheduling system;

a pending list comprising indexed messageid of a pre-identified at least one class of messages having medium priority messages with serialization conflict with the highest priority messages and one or more other priority message classes, wherein the conflicting messageid is fetched from the input message queue in response to the service call from at least one output server process;

a restrictive message list comprising indexed baseid of at least one class of messages having lowest priority messages with serialization conflict with the highest priority messages and one or more other priority message classes, wherein the baseid is linked to a linked list pointer thereof;

a dispatcher, communicatively coupled with the cache memory of the front office system, dynamically configurable to adapt to at least one serialization constraint, wherein the dispatcher assigns at least one message of at least one class, indexed in the input message queue, to at least one output server process according to predetermined priority thereof for priority based preemptive message transmission to at least one back office node in confirmation with at least one selected message serialization constraint; and

a service over queue, communicatively connected to the dispatcher, to assign at least one message to at least one output server process and updating a server process completion flag accessible by the dispatcher, enabling the dispatcher to resume dispatching of at least one new message from the input message queue to at least one output server process.

2. The preemptive priority scheduling system of claim 1, the dispatcher in the fully restrictive serialization constraint, accesses at least one message from the input message queue in a first come first serve order, compute at least one output server process corresponding to a modulus of the baseid of the message and routes the accessed message to the at least one computed output server process in response a synchronous service call therefrom.

3. The preemptive priority scheduling system of claim 1, the dispatcher for the fully restrictive serialization constraint assigns at least one non-conflicting messageid to at least one idle message output process for further processing thereof.

4. The preemptive priority scheduling system of claim 1, the dispatcher in the partially restrictive serialization constraint, accesses at least one message from the input message queue and upon countering true for serialization conflict with at least one existing baseid, swapping the associated message into the pending list and in a non conflicting event continue dispatching the highest priority message to at least one output server process for serialized processing thereof and upon detecting null of the input queue, resume the message processing from the pending list on at least one output server process.

5. The preemptive priority scheduling system of claim 1, the dispatcher in the partially restrictive serialization constraint, wherein a service over queue contains at least one serverid, baseid and the server process completion flag and to assign at least one message to at least one output server process and updating a server process completion flag accessible by the dispatcher, enabling the dispatcher to resume dispatching of at least one new message from the input message queue to at least one output server process.

6. The preemptive priority scheduling system of claim 1, a baseidhash table for the dispatcher for the partially restrictive serialization constraint contains baseid, status associate with the baseid, and pointer to the pending list.

7. The preemptive priority scheduling system of claim 1, the dispatcher in the partially restrictive serialization constraint, wherein the server process completion flag of the service over queue indicates a true status for a previous processed message is a medium priority message and a false status for an earliest non processing thereof.

8. The preemptive priority scheduling system of claim 1, the dispatcher in the partially restrictive serialization constraint, wherein in an event of true for the service over queue, a cleanup operation is initiated, hashing the status thereof into a BaseidHash table, a linked list of the pending list, referring to the pointer therein to the pending list associated with the currently processed baseid, indicating null for BaseidHash table in the absence of at least one medium priority message in the pending list and deletes the baseid node in the pending list.

9. The preemptive priority scheduling system of claim 1, the dispatcher in the non restrictive and partially restrictive serialization constraints, wherein for the false status of the pending list indicating absence of at least one medium priority message associated to a baseid in the pending list, nullifying the pointer to pending list in the BaseidHash table, removing the associated baseid from the BaseidHash table for null of pending list and restrictive list pointers.

10. The preemptive priority scheduling system of claim 1, the dispatcher in the non restrictive serialization constraint comprising of the restrictive message list containing at least one lowest priority message, the pending message list containing at least one medium priority message, and the input message queue containing at least one highest priority message pre-identified for a default transmission, wherein each of the medium and lowest priority message processes message according to predefined serialization constraint and at least one message server process is always accessible to each highest priority message.

11. The preemptive priority scheduling system of claim 1, a BaseidHash table for implementation of the dispatcher for the non restrictive serialization constraint contains baseid, status associated with the baseid, pointer to pending list and a pointer to the restrictive list.

12. The preemptive priority scheduling system of claim 1, the BaseidHash table for implementation of the non restrictive serialization constraint, wherein for processing at least one lowest priority message, a baseid verification in the BaseidHash table corresponding to the lowest priority message is done, upon detecting null status of the restrictive list pointer, a new baseid node is created, restrictive list and a corresponding pointer thereof is indexed into the hash table, the associated messageid is inserted in to the linked list for the newly created node.

13. The preemptive priority scheduling system of claim 1, wherein while processing of at least one class of messages corresponding to priority thereof, the other classes of messages, excluding the highest priority messages, are blocked form processing on any of the output server process.

14. The preemptive priority scheduling system of claim 1, wherein while processing of at least one class of messages corresponding to priority thereof, a dynamic class switching occurs upon detection of true state of at least one corresponding flag of associated message list, indicating availability of output processing server corresponding to the baseid thereof.

15. The preemptive priority scheduling system of claim 1, wherein a water mark flag bind to at least one class of message having lower priority, is accessible to the dispatcher and the water mark flag of the class is coupled with at least one output message processing server through a switching routine, the switching routine switching the processing from highest priority message class to the coupled water mark flagged class.

16. The preemptive priority scheduling system of claim 1, the dispatcher for every dynamic class switching and processing of each message on associated output server process, detects the presence of water mark flag on the lower priority classes of messages wherein the dispatcher dynamically reserves and assigns output server process to serve each low priority class corresponding to the water mark according to the pre-identified serialization constraints thereof.

17. A method for preemptive priority scheduling of messages in an intersystem communication causing dynamic class switching of messages corresponding to a selected serialization constraint, the method comprises the computer implemented steps of:

receiving a plurality of inbound messages associated with a plurality of message classes from a front office in a serialized sequence into a cache memory of the front office system, each message having pre-assigned priority and a unique messageid and a class thereof a unique baseid, wherein all the related messages corresponding to at least one pre-identified business activity have the same baseid;

indexing each inbound message residing therein the cache memory of the front office system according to a serialization constraint, assigned baseid and messageid into an input message queue, wherein the serialization constraint comprising of fully restrictive, partially restrictive and non restrictive constraints, each constraint allowing to identify priority of each class of the inbound message and subsequent processing thereof by a scheduling system;

receiving at least one synchronous service call from at least one output service server process running on at least one message output server having a unique serverid for fetching at least one message from the cache memory;

communicating a work status of the outbound message processing server'"'"'s to a dispatcher, wherein the dispatcher is communicatively coupled with the cache memory of the front office system and is dynamically configurable to adapt to at least one serialization constraint;

assigning at least one message of at least one class, indexed in the input message queue, to at least one output server process according to predetermined priority thereof for priority based preemptive message transmission to at least one back office node in accordance with at least one selected message serialization constraint;

creating a pending list and a restrictive list of messages for swapping the lower priority messages and for further processing thereof in accordance with the associated serialization constraint therewith, wherein the dispatcher swapping and indexing the messageids associated with the lower priority messages and fetching the conflicting messageid from the input message queue in response to the service call from at least one output server process;

creating a linked list hash table for storing a pointers for the lower priority messages in the pending list and restrictive list, wherein the hashing is performed in relation to a baseid of each message;

transmitting the messages in first come first serve order to at least one back office system;

communicating the completion of each message processing associated with each output server, wherein a service over queue, communicatively connected to the dispatcher, assigns at least one message to at least one output server process and updating a server process completion flag accessible by the dispatcher, enabling the dispatcher to resume dispatching of at least one new message from the input message queue to at least one output server process; and

repeating iteratively the message server processes in accordance with the serialization constraint for the messages in the input queue.