Alias hiding in network data repositories

• US 9,112,873 B2
• Filed: 04/10/2007
• Issued: 08/18/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:
  US11/783,586
• Publication Number:
  US 20080256083A1
• Time in Patent Office: 3,052 Days
• Field of Search: 707/782
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9017 using directory or table look-up use of a directory or look-up table in file systems G06F16/13
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1095 Inter-network session transfer or sharing

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, comprising:

a processor, wherein the processor comprises computer hardware; and

at least one memory including computer program code,

the at least one memory and the computer program code configured, with the processor, to cause the processor to operate as;

a name resolution module configured to determine a location for data in a directory by resolving a path to an entry containing the data using an original path and alias dereferencing instructions, wherein the name resolution module uses alias dereferencing instructions in contradiction to an expectation of a requesting entity,

a search/update module configured to perform actions on data in the entry using a location for the entry in the directory and alias dereferencing instructions, and

an alias hiding module configured to

intercept a request to perform an action on data in a first entry stored in the directory sent by the requesting entity, wherein the request includes an original path to the first entry in the directory, the original path to the first entry is unique to the requesting entity and is stored before a first request is made by the requesting entity, and other requesting entities do not request the original path to the first entry in the directory;

locate instructions regarding alias dereferencing pertinent to the requesting entity,

provide the original path to the name resolution module along with the located instructions for alias dereferencing pertinent to the requesting entity,

receive from the name resolution module a resolved location for the data in the directory and an alias dereferenced path to a resolved entry that contains the data,

request the search/update module to perform the action on the data at the resolved location by providing the requested action and the located instructions for alias dereferencing, and

report to the requesting entity that the action has been performed on the data in the first entry having replaced the alias dereferenced path to the data with the original path that is unique to the requesting entity.

2. The system of claim 1 wherein the search/update module is further configured to:

determine that a second entry subordinate to the resolved location comprises a second alias;

resolve the second alias to determine a third entry at a second alias dereferenced path; and

perform the action on the data at the third entry,

wherein the alias hiding module is further configured to replace the second alias dereferenced path to the third entry with a path to the second entry that includes the alias dereferenced path.

3. The system of claim 2 wherein the search/update module is further configured to recursively perform alias dereferencing.

4. The system of claim 1 wherein the directory is stored across a plurality of directory servers and wherein the name resolution module determines that the location for data in the directory resides on another directory server in the plurality of directory servers, the processor further comprising:

a chaining module configured to forward the request and the located alias dereferencing instructions to the another directory server.

5. The system of claim 4 wherein the alias hiding module is further configured to receive from the chaining module a resolved location for the data received from the another directory server and include the resolved location in the request to the search/update module.

6. The system of claim 1 wherein the directory is stored across a plurality of directory servers and wherein the search/update module determines that the location for data in the directory resides on another directory server in the plurality of directory servers, the processor further comprising:

a chaining module configured to forward the request and the located alias dereferencing instructions to the another directory server.

7. The system of claim 6 wherein the search/update module is further configured to receive from the chaining module a resolved location for the data received from the another directory server and include the resolved location in a report to the alias hiding module.

8. The system of claim 1 wherein the name resolution module is further configured to determine the location by determining a distinguished name for the entry, wherein the distinguished name identifies the location for the entry in the directory.

9. The system of claim 1 wherein the alias hiding module resides in a directory server that resides in an interconnected network comprising a plurality of directory servers.

10. The system of claim 1 wherein the alias hiding module is further configured to receive requests to perform actions in accordance with at least one of the LDAP and DAP protocols.

11. The system of claim 1 wherein the alias hiding module is further configured to send reports to the requesting entity configured in accordance with at least one of the LDAP and DAP protocols.

12. The system of claim 1 wherein the requesting entity is one of a client application, an end user, or a directory server attempting to complete a data request and wherein the alias hiding module is further configured to prepare reports sent to the requesting entity in a format accessible to the requesting entity.

13. The system of claim 12 wherein the requesting entity implements a client application comprising one of Home Location Register (HLR), Home Subscriber Server (HSS), a Voicemail system, Authentication, Authorization and Accounting system (AAA), Mobile Number Portability (MNP) and wherein the alias hiding module is further configured to communicate with the client application using a native data protocol for the client application.

14. The system of claim 1 wherein the action is one of a read or a write.

15. The system of claim 1, the processor further caused to operate as:

an alias creation module configured to create an alias entry in the directory.

16. A method, comprising:

intercepting, by a processor, a request to perform an action on data at a first entry stored in a directory sent by a requesting entity, wherein the request includes an original path to the first entry in the directory, the original path to the first entry is unique to the requesting entity and is stored before a first request is made by the requesting entity, and other requesting entities do not request the original path to the first entry in the directory;

locating, by the processor, instructions regarding alias dereferencing pertinent to the requesting entity in contradiction to an expectation of the requesting entity;

determining, by the processor, an alias dereferenced path to the data in the directory by resolving a path from the first entry to a second entry that contains the data using the original path and the located alias dereferencing instructions;

performing, by the processor, the action on the data at the second entry; and

reporting, by the processor, to the requesting entity that the action has been performed on the data in the first entry having replaced the alias dereferenced path to the data with the original path that is unique to the requesting entity.

17. The method of claim 16 wherein performing the action on the data at the second entry further comprises:

determining that an entry subordinate to the second entry comprises a second alias;

resolving the second alias to determine a third entry at a second alias dereferenced path;

performing the action on the data at the third entry; and

replacing the second alias dereferenced path to the third entry with a path to the second entry that includes the alias dereferenced path.

18. The method of claim 17 wherein performing the action on the data at the second entry further comprises recursively performing alias dereferencing.

19. The method of claim 16 wherein the directory is stored across a plurality of directory servers and wherein determining the alias dereferenced path to the data indicates that the data resides in another directory server in the plurality of directory servers, the method further comprising:

chaining the request and the located alias dereferencing instructions to the another directory server.

20. The method of claim 19, further comprising:

receiving from the another directory server a resolved location for the data and using the resolved location in performing the action on the data at the second entry.

21. The method of claim 16 wherein the directory is stored across a plurality of directory servers and wherein performing the action on the data at the second entry involves determining that the location for the data in the directory resides on another directory server in the plurality of directory servers, the method further comprising:

chaining the request and the located alias dereferencing instructions to the another directory server.

22. The method of claim 21, the method further comprising:

receiving from the another directory server a resolved location for the data and using the resolved location in performing the action on the data at the second entry.

23. The method of claim 16 wherein determining the alias dereferenced path to the data in the directory comprises determining a distinguished name for the entry, wherein the distinguished name identifies the location for the entry in the directory.

24. The method of claim 16 wherein the intercepted requests to perform actions are formatted in accordance with at least one of the LDAP and DAP protocols.

25. The method of claim 16 wherein the reports sent to the requesting entity are configured in accordance with at least one of the LDAP and DAP protocols.

26. The method of claim 16, the method further comprising preparing reporting to the requesting entity that an action has been performed in a manner such that the requesting entity receives no information regarding a data path to the second entry.

27. The method of claim 16 wherein the requesting entity is one of a client application, an end user, or a directory server attempting to complete a data request, the method further comprising formatting reports sent to the requesting entity in a native format accessible to the requesting entity.

28. The method of claim 16 wherein the requesting entity implements a client application comprising one of Home Location Register (HLR), Home Subscriber Server (HSS), a Voicemail system, Authentication, Authorization and Accounting system (AAA), Mobile Number Portability (MNP), the method further comprising communicating with the client application using a native data protocol for the client application.

29. The method of claim 16 wherein the action is one of a read or a write.

30. The method of claim 16, further comprising:

creating an alias entry in the directory.