Variant entries in network data repositories

• US 8,996,572 B2
• Filed: 04/20/2012
• Issued: 03/31/2015
• Est. Priority Date: 04/10/2007
• Status: Active Grant

• Current Assignee: Apertio Ltd. (Nokia Corporation)
• Original Assignee: Apertio Ltd. (Nokia Corporation)
• Inventors: Wakefield, Kevin
• Primary Examiner(s): Richardson, James E
• Application Number:
  US13/451,730
• Publication Number:
  US 20120203781A1
• Time in Patent Office: 1,075 Days
• Field of Search: 707/759, 707/764, 707/768, 707/775, 707/782, 707/787
• US Class Current: 707/782
• CPC Class Codes: H04L 61/4517 using open systems interconnection [OSI] directories, e.g. X.500
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• 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

Abstract

A logical network directory database compliant with the X.500 standard for a directory data system is disclosed. The network directory database provides a source of subscriber and service data accessible by various control and management processes that require subscriber information. The network directory database may be extensible across various communications service providers and IT domain. Further, the disclosed network directory database may be applied to new and existing services, such as, IP Multimedia Subsystem, Unlicensed Mobile Access (UMA) and other IP services.

Claims

1. A system for accessing data in a directory by a plurality of requesting entities, comprising:

a protocol adaptation module configured to review a data request from a requesting entity received in a directory operations server, determine if the data request should be mapped to a first operation using a rule set of mapping instructions;

a rule selector configured to select the rule set of the mapping instructions by matching rule selection data against a putative rule set, wherein the rule set is selected at least in part based on an identity of the requesting entity, wherein the rule set is selected from more than one set of rules; and

hardware, wherein the protocol adaptation module controls execution of the first operation on the directory, wherein the protocol adaptation module is implemented as software running on the hardware or as the hardware alone,

wherein the rule selector is configured to select using the identity of the requesting entity as contextual information in determining which rule set of the more than one set of rules to select.

2. The system of claim 1 wherein the protocol adaptation module is configured to:

determine that the data request should be mapped to the first operation and is further configured to determine that the data request should also be mapped to a second operation using the rule set of mapping instructions,

control execution of the second operation and wherein the protocol adaptation module is further configured to merge results from the first operation with results from the second operation,

send the merged results to a directory operations server configured to send the merged results to the requesting entity as a response to the data request, and

determine if the first operation can be performed by the directory operations server.

3. The system of claim 1 wherein the rule selector is configured to, at least one of

match the rule selection data against the putative rule set by computing logical combinations of values found in the selection data against values found in the putative rule set,

derive the rule selection data from a first field from the data request,

derive the rule selection data from a combination of the first field and a second field from the data request,

derive the rule selection data from the first field from the data request and the identity of the requesting entity,

derive the rule selection data from the first field from the data request and contextual information, and,

find the putative rule set in configuration data, wherein the configuration data relates to the directory.

4. The system of claim 3 wherein the rule selector is configured to compute the logical combinations of the values found in the selection data against values found in the putative rule set, wherein the logical combinations used by the rule selector include at least one of an “

and”

operation and an “

or”

operation.

5. The system of claim 4 wherein the rule selector is configured to select one of

the first field from one of an operation type field and an entry name field, and,

the first field from the entry name field and wherein the rule selector is further configured to find the rule selection data by determining a maximum number of ordered relative distinguished names (RDN) in a section of the directory that match the entry name field.

6. The system of claim 4 wherein the first field comprises an entry name provided by the requesting entity, and wherein the rule selection data and the putative rule set identify a set of adaptive name mappings between the entry name and a name in the directory.

7. The system of claim 6 wherein the rule selector is configured to determine that the data request is a search, then the rule selector locates a filter that reduces a scope of the search.

8. The system of claim 6 wherein the protocol adaptation module is configured to report results of the data request to the requesting entity using the entry name provided by the requesting entity.

9. The system of claim 3 wherein the rule selector is configured to derive the rule selection data from the first field from the data request and contextual information, wherein the contextual information relates to a time of day and wherein the rule selector is further configured to determine a time of day in order to select the rule set of mapping instructions.

10. The system of claim 1 wherein the rule selector is configured to identify an attribute mapping for an entity name provided by the requesting entity such that at least one attribute associated with the entity name corresponds an entry in the directory, and/or, wherein the attribute mapping is configured to instruct the protocol adaptation module to perform a set of mappings between the entry and the at least one attribute.

11. The system of claim 10 wherein the attribute mapping is configured to:

instruct the protocol adaptation module to translate a data format of the entry into another data format for the at least one attribute, or

instruct the protocol adaption module to translate a name of the entry into another name for the at least one attribute.

12. The system of claim 1 wherein the rule selection data is configured to direct the rule selector to send a request to perform an action on data in a first entry stored in the directory sent by the requesting entity, wherein the action on data in the first entry produces an alias dereferenced name that the rule selector uses to select the rule set of mapping instructions.

13. The system of claim 12, further comprising:

a name resolution module configured to determine a location for data in the directory by resolving a path to an entry containing the data using an original path and alias dereferencing instructions and further configured to report the alias dereferenced path to the rule selector.

14. The system of claim 1 wherein the protocol adaptation module is configured to provide results from execution of the first operation to the rule selector such that the rule selector derives the rule set of mapping instructions for a second operation using results from the first operation.

15. The system of claim 14 wherein the protocol adaptation module is configured to control execution of the second operation and wherein the protocol adaptation module is further configured to merge results from the first operation with results from the second operation.

16. The system of claim 1 wherein the data request comprises a chained data request wherein the rule set of mapping instructions includes an instruction that results provided to the requesting entity are derived from the first operation actually performed in a directory operations server local to the protocol adaptation module.

17. The system of claim 1 wherein the directory represents a first portion of a distributed directory and wherein the first operation involves data found in a second portion of the distributed directory, the protocol adaptation module further configured to control a chaining request for the data found in the second portion of the distributed directory.

18. The system of claim 17 wherein the protocol adaptation module is configured to determine that the data request should be mapped to a second operation wherein the second operation involves data found in a third portion of the distributed directory, the protocol adaptation module further configured to control a chaining request for data found in the third portion of the distributed directory.

19. The system of claim 18 wherein the protocol adaptation module is further configured to merge results of the first operation with results of the second operation.

20. The system of claim 17 wherein the directory resides in a plurality of directory servers and wherein the location deriver is configured to determine that the location for data in the directory resides on another directory server in the plurality of directory servers, the system further comprising:

a chaining module configured to chain the variant data request to another directory server of the plurality of directory servers that contains a portion of the directory having the second entry.

21. The system of claim 1 wherein the rule set of mapping instructions specifies an error message to be returned to the requesting entity by the protocol adaptation module.

22. The system of claim 1 wherein first operation comprises a variant data request, wherein the protocol adaptation module forwards the variant data request to a processing unit of the system, the processing unit comprising:

a data request receiver configured to receive the variant data request to perform an action on data in an attribute of a first entry at a first location in the directory provided by the protocol adaptation module, wherein data for the attribute requested in the data request resides in a second entry at a second location in the directory;

a location deriver configured to derive the second location in the directory for the data in the attribute of the variant data request using information associated with the first entry, wherein the location deriver performs the derivation at a point of access to/from a data storage mechanism for the directory; and

a read/update module configured to find the data in the attribute of the data request at the second entry using the derived second location and perform the action on the data at the derived second location.

23. The system of claim 1, further comprising:

another protocol adaptation module configured to intercept data requests, for data in the directory, sent to a directory operations server, determine if the data request should be mapped to a first operation using a rule set of mapping instructions, and controlling execution of the first operation, wherein the another protocol adaptation module is configured to forward results of the first operation to the directory operations server in place of the data request from the requesting entity.

24. The system of claim 23 wherein the data requests are formatted according to at least one of the LDAP or DAP protocols and wherein the another protocol adaptation module is further configured to interpret LDAP and DAP operations.

25. The system of claim 1 wherein the rule set comprises at least one rule that specifies results or errors to be immediately returned to the requesting entity.

26. A system for accessing data in a directory by a plurality of requesting entities, comprising:

a protocol adaptation module configured to review a data request from a requesting entity received in a directory operations server, determine if the data request should be mapped to a first operation using a rule set of mapping instructions; and

a rule selector configured to select the rule set of the mapping instructions by matching rule selection data against a putative rule set, wherein the rule set is selected at least in part based on the requesting entity,

wherein the protocol adaptation module controls execution of the first operation on the directory,

wherein the protocol adaptation module is implemented in hardware as software running on the hardware or as the hardware alone, wherein the system comprises the hardware on which the software is running or the hardware alone, respectively,

wherein the directory represents a first portion of a distributed directory and wherein the first operation involves data found in a second portion of the distributed directory, the protocol adaptation module further configured to control a chaining request for the data found in the second portion of the distributed directory, and

wherein the chained data request is a portion of a data request that further comprises another chained request, and wherein the protocol adaptation module is further configured to;

modify the another chained data request to comprise at least one revised data request based on the rule set of mapping instructions in parallel with modifying the chained data request to comprise the first operation based on the rule set of mapping instructions.

27. A method for accessing data in a directory by one of a plurality of requesting entities, comprising:

reviewing a data request from the requesting entity received in a directory operations server by a protocol adaptation module;

determining by the protocol adaptation module if the data request should be mapped to a first operation using a rule set of mapping instructions;

selecting the rule set of the mapping instructions by a rule selector that matches rule selection data against a putative rule set, wherein the rule set is selected at least in part based on an identity of the requesting entity, wherein the rule set is selected from more than one set of rules; and

controlling execution of the first operation in the directory by the protocol adaptation module,

wherein the selecting uses the identity of the requesting entity as contextual information in determining which set of the more than one set of rules to use.