LDAP replication priority queuing mechanism

• US 8,190,561 B1
• Filed: 12/06/2006
• Issued: 05/29/2012
• Est. Priority Date: 12/06/2006
• Status: Expired due to Fees

• Current Assignee: Cingular Wireless II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Culver, Timothy, Poole, Jack
• Primary Examiner(s): Vital, Pierre
• Assistant Examiner(s): OBISESAN, AUGUSTINE KUNLE
• Application Number:
  US11/567,234
• Time in Patent Office: 2,001 Days
• Field of Search: 707/624, 707/610
• US Class Current: 707/610
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

A replication priority queuing system prioritizes replication requests in accordance with a predetermined scheme. An exemplary system includes a Replication Priority Queue Manager that receives update requests and assigns a priority based upon business rules and stores the requests in associated storage means. A Replication Decision Engine retrieves the requests from storage and determines a destination for the update based upon predetermined replication rules, and sends the update to the destination.

Claims

1. A method, for updating a lightweight directory access protocol server network, comprising:

receiving, at a replication priority queue manager of a replication management system, a plurality of update requests, each of which comprises instructions to replicate certain data from a master lightweight directory access protocol server of the server network to a plurality of slave lightweight directory access protocol servers of the server network;

assigning, at the replication priority queue manager, for each of the plurality of update requests, a priority level wherein assigning the priority level for each of the plurality of update requests includes;

(i) assigning, at the replication priority queue manager, the priority level for each of the plurality of update requests based upon an age of the update request;

(ii) monitoring, following assigning the priority for each of the plurality of update requests, a status of the update request in order to determine whether the age of the update request has gone beyond a predetermined time threshold; and

(iii) reassigning, to each of the plurality of update requests for which it is determined, in the monitoring, that the age of the update request goes beyond the predetermined time threshold, a higher priority;

storing, at the replication priority queue manager, each update request in one of a plurality of ordered storage locations in accordance with a priority last assigned to the update request, wherein;

the storing includes moving the update request, from a first storage location of the plurality of ordered storage locations to a second storage location, if the update request is reassigned from a first priority to a second, higher, priority;

the first storage location corresponds to the first priority; and

the second storage location corresponds to the second priority;

processing, at the replication decision engine, each of the plurality of update requests in order based upon the assigned storage locations; and

replicating data identified in each of the plurality of update requests from the master lightweight directory access protocol server to the plurality of slave lightweight directory access protocol servers in order based upon the assigned storage locations.

2. The method of claim 1, wherein processing, at the replication decision engine, each of the plurality of update requests based upon the assigned priority level for each update request further comprises determining a corresponding destination server of the plurality of slave lightweight directory access protocol servers for an update associated with each update request.

3. The method of claim 2, wherein processing, at the replication decision engine, each of the plurality of update requests based upon the assigned priority level for each update request further comprises sending each update to the corresponding destination server.

4. The method of claim 1, wherein processing the plurality of update requests in order based upon the assigned storage locations includes processing the update requests according to a scheme for processing the updates within each of the plurality of storage locations.

5. The method of claim 4, wherein processing the plurality of update requests according to the scheme for processing the updates within each of the plurality of storage locations includes:

checking, while processing a first update request of the plurality of update requests stored in a particular storage location of the plurality of storage locations, as to whether a higher priority update request has been received at the particular storage location in which the first update request was stored and, if a higher priority update request is received at the particular storage location; and

stopping execution of the first update request, and commencing execution of the higher priority update request received at the particular storage location, if it is determined in the checking that the higher priority update request was received at the particular storage location.

6. The method of claim 4, wherein processing the plurality of update requests according to the scheme for processing the updates within each of the plurality of storage locations includes processing the updates within each of the plurality of storage locations according to a first-in-first-out basis.

7. A replication management system comprising:

a replication priority queue manager comprising;

an instruction module having instructions for determining a priority of incoming update requests; and

a processor in communication with the instruction module, wherein the instructions, when executed by the processor, cause the processor to at least;

receive a plurality of update requests, each of which comprises instructions to replicate certain data from a master lightweight directory access protocol server of the server network to a plurality of slave lightweight directory access protocol servers of the server network;

assign, for each of the plurality of update requests, a priority level, wherein assigning the priority level for each of the plurality of update requests includes;

(i) assigning, at the replication priority queue manager, the priority level for each of the plurality of update requests based upon an age of the update request;

(ii) monitoring, following assigning the priority for each of the plurality of update requests, a status of the update request in order to determine whether the age of the update request has gone beyond a predetermined time threshold; and

(iii) reassigning, to each of the plurality of update requests for which it is determined, in the monitoring, that the age of the update request goes beyond the predetermined time threshold, a higher priority; and

store each update request in one of a plurality of ordered storage locations in accordance with a priority last assigned to the update request, wherein;

storing includes moving the update request, from a first storage location of the plurality of ordered storage locations to a second storage location, if the update request is reassigned from a first priority to a second, higher, priority;

the first storage location corresponds to the first priority; and

the second storage location corresponds to the second priority; and

the replication decision engine being configured to;

process each of the plurality of update requests in order based upon the assigned storage locations; and

replicate data identified in each of the plurality of update requests from the master lightweight directory access protocol server to the plurality of slave lightweight directory access protocol servers in order based upon the assigned storage locations.

8. The replication management system of claim 7, wherein the instructions further cause the processor is further configured to determine a corresponding destination server of the plurality of slave lightweight directory access protocol servers for an update associated with each update request.

9. The replication management system of claim 8, wherein the instructions further cause the processor replication decision engine is further configured to send each update to the corresponding destination server.

10. The replication management system of claim 7 wherein processing the plurality of update requests in order based upon the assigned storage locations includes processing the update requests according to a scheme for processing the updates within each of the plurality of storage locations.

11. The replication management system of claim 10 wherein processing the plurality of update requests according to the scheme for processing the updates within each of the plurality of storage locations, includes at least the following:

checking, while processing a first update request of the plurality of update requests stored in a particular storage location of the plurality of storage locations, as to whether a higher priority update request has been received at the particular storage location in which the first update request was stored and, if a higher priority update request is received at the particular storage location; and

stopping execution of the first update request, and commencing execution of the higher priority update request received at the particular storage location, if it is determined in the checking that the higher priority update request was received at the particular storage location.

12. The replication management system of claim 10 wherein processing the plurality of update requests according to the scheme for processing the updates within each of the plurality of storage locations, includes processing the updates within each of the plurality of storage locations according to a first-in-first-out basis.

13. A server network system comprising:

a server network comprising a lightweight directory access protocol lightweight directory access protocol client tier that includes at least one lightweight directory access protocol client server, and lightweight directory access protocol master tier that includes at least one lightweight directory access protocol master server, wherein the lightweight directory access protocol master tier is configured to receive update requests from the lightweight directory access protocol client tier and process the update requests via a replication management system; and

the replication management system, being communicatively coupled to the server network and having a processor and instructions that, when executed by the processor, cause the processor to;

receive a plurality of update requests, each of which comprises instructions to replicate certain data from a master lightweight directory access protocol server of the server network to a plurality of slave lightweight directory access protocol servers of the server network;

assign, for each of the plurality of update requests, a priority level, wherein assigning the priority level for each of the plurality of update requests includes;

(i) assigning, at the replication priority queue manager, the priority level for each of the plurality of update requests based upon an age of the update request

(ii) monitoring, following assigning the priority for each of the plurality of update requests, a status of the update request in order to determine whether the age of the update request has gone beyond a predetermined time threshold; and

(iii) reassigning, to each of the plurality of update requests for which it is determined, in the monitoring, that the age of the update request goes beyond the predetermined time threshold, a higher priority;

store each update request in one of a plurality of ordered storage locations in accordance with a priority last assigned to the update request, wherein;

storing includes moving the update request, from a first storage location of the plurality of ordered storage locations to a second storage location, if the update request is reassigned from a first priority to a second, higher, priority;

the first storage location corresponds to the first priority; and

the second storage location corresponds to the second priority;

process each of the plurality of update requests in order based upon the assigned storage locations; and

replicate data identified in each of the plurality of update requests from the master lightweight directory access protocol server to the plurality of slave lightweight directory access protocol servers in order based upon the assigned storage locations.

14. The server network system of claim 13, wherein the instructions, when executed by the processor, further cause the processor to determine a corresponding destination server of the plurality of slave lightweight directory access protocol servers for an update associated with each update request.

15. The server network system of claim 14, wherein the instructions, when executed by the processor, further cause the processor to send each update to the corresponding destination server.

16. The server network system of claim 13, wherein the instructions, when executed by the processor, further cause the processor to, in processing the plurality of update requests in order based upon the assigned storage locations, process the update requests according to a scheme for processing the updates within each of the plurality of storage locations.

17. The server network system of claim 16, wherein the instructions, when executed by the processor, further cause the processor to, in processing the plurality of update requests according to the scheme for processing the updates within each of the plurality of storage locations, perform at least the following:

checking, while processing a first update request of the plurality of update requests stored in a particular storage location of the plurality of storage locations, as to whether a higher priority update request has been received at the particular storage location in which the first update request was stored and, if a higher priority update request is received at the particular storage location; and

stopping execution of the first update request, and commencing execution of the higher priority update request received at the particular storage location, if it is determined in the checking that the higher priority update request was received at the particular storage location.

18. The server network system of claim 16, wherein the instructions, when executed by the processor, further cause the processor to, in processing the plurality of update requests according to the scheme for processing the updates within each of the plurality of storage locations, process the updates within each of the plurality of storage locations according to a first-in-first-out basis.