Systems and methods for management of subscriber databases within mobile communications networks

• US 8,660,991 B2
• Filed: 07/18/2011
• Issued: 02/25/2014
• Est. Priority Date: 01/11/2011
• Status: Active Grant

• Current Assignee: Amdocs Canadian Managed Services Inc. (Amdocs Ltd.), Amdocs Development Limited (Amdocs Ltd.)
• Original Assignee: Bridgewater Systems Corp. (Amdocs Ltd.)
• Inventors: Glaude, Normand
• Primary Examiner(s): MENG, JAU SHYA
• Assistant Examiner(s): Meng, Thomas
• Application Number:
  US13/185,096
• Publication Number:
  US 20120179652A1
• Time in Patent Office: 953 Days
• Field of Search: None
• US Class Current: 707/652
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

Systems and methods system for managing data objects that support the personalization of mobile communications services are provided. The system includes one or more databases that contain subscriber data, such as usage, or state information related to the subscriber. For one or more of the databases within the system, a database federator and a distributed object repository having multiple nodes is provided. The nodes are used to store data objects and duplicate data objects. Data objects may be distributed to the nodes based on, a hashing algorithm. Additionally, graceful redundancy degradation of stored duplicate objects is provided. Further, time-based triggering of duplicate objects stored within separate nodes is provided.

Claims

1. A method comprising:

establishing, utilizing a processor, at least one node utilization threshold for a plurality of nodes storing objects;

on determining that a first utilization threshold of the at least one node utilization threshold has been exceeded by a utilization of the nodes; and

in response to the determination that the first utilization threshold of the at least one node utilization threshold has been exceeded, reducing an original value of a replication factor to an updated value that is greater than zero;

storing a received one of the objects and at least one duplicate object that is a copy of the received object, wherein a number of the at least one duplicate object stored is determined by the updated value of the replication factor, wherein the received object and the at least one duplicate object are stored on separate nodes;

increasing the updated value of the replication factor to perform object replication by;

storing an abatement threshold, wherein the abatement threshold is configured based on an assessment of;

a capacity of the nodes, a rate of retrieval of the objects from the nodes, and a rate of deletion of the objects from the nodes,

determining that the abatement threshold has been met,

in response to the determination that the abatement threshold has been met, assessing the utilization of the nodes to determine that the capacity of the nodes is sufficient to increase the updated value of the replication factor, and

increasing the updated value of the replication factor based on the determination that the capacity of the nodes is sufficient to increase the updated value of the replication factor;

on determining that a second utilization threshold is exceeded, purging one or more of the objects; and

on determining that a third utilization threshold is exceeded, reducing the value of the replication factor to zero such that the object replication is prevented;

wherein the first utilization threshold is less than the second utilization threshold and the second utilization threshold is less than the third utilization threshold.

2. The method of claim 1, further comprising purging duplicate objects already stored, wherein a number of duplicate objects that are not purged for an object is based on the first utilization threshold that has been exceeded.

3. The method of claim 1, further comprising reducing the updated value of the replication factor based on a value of an object.

4. The method of claim 1, wherein the value of the object is based on one or more of a business importance of the object and whether the object can be recreated.

5. The method of claim 1, further comprising purging a stored duplicate object on determining a number of stored duplicate objects for a particular object exceed the updated value of the replication factor.

6. The method of claim 1, further comprising purging a stored duplicate object on determining a number of stored duplicate objects for a particular object exceed the updated value of the replication factor on an as needed basis.

7. The method of claim 1, wherein an object comprises a set of data.

8. The method of claim 1, wherein an object comprises a set of data that relates to provisioning of a communications service.

9. The method of claim 8, wherein an object includes at least one of service profile data, subscriber profile data, billing data, session information, and network usage data.

10. The method of claim 1, wherein increasing the updated value of the replication factor based on the determination that the capacity of the nodes is sufficient to increase the updated value of the replication factor includes resetting the updated value of the replication factor to the original value of the replication factor.

11. The method of claim 1, wherein multiple replication factors exist based on a priority of received objects.

12. The method of claim 11, wherein upon one of the node utilization thresholds being exceeded a first replication factor is applied to objects of a first priority and a second replication factor is applied to objects of a second priority, wherein the first priority is higher than the second priority and the first replication factor is greater than the second priority.

13. The method of claim 1, further comprising determining an overall replication factor of objects stored across the nodes.

14. The method of claim 13, further comprising generating an alarm on determining the overall replication factor drops below a threshold.

15. The method of claim 1, further comprising determining an overall replication factor on a per priority basis of objects stored across the nodes.