Extensible Data Repository

• US 20080235255A1
• Filed: 03/19/2007
• Published: 09/25/2008
• Est. Priority Date: 03/19/2007
• Status: Abandoned Application

• Current Assignee: Redknee Inc.
• Original Assignee: Redknee Inc.
• Inventors: Greer, Kevin Glen Roy, Rahim, Rubens
• Application Number:
  US11/688,078
• Publication Number:
  US 20080235255A1
• Time in Patent Office: Days
• US Class Current: 707/102
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

In telecommunication networks, the need for real-time extension of data repositories is increasing. The present application provides an extensible data repository that can be used by a plurality of different applications that each has a local data format structure and database command structure. A single data repository is available to all of the applications. A universal dynamic storage application resides between the common database and the applications, and permits each application to interact with the common database according to its local format structure and database command structure.

Claims

1. A method of operating a data repository comprising:

receiving a local database definition from a local application that utilizes said local database definition;

comparing fields in a universal database with said local database definition;

generating a viewing strategy for said local application;

said viewing strategy based on results of said comparing;

creating a view for said local application according to said local database definition based on said viewing strategy such that data in said universal database is viewable in said local application according to said local database definition.

2. The method of claim 1 further comprising the step of serving said local application from said universal database according to said view.

3. The method of claim 1 wherein said viewing strategy includes generating a list of fields that exist in said universal database that have not been used in said local database definition until now.

4. The method of claim 1 wherein said viewing strategy includes generating a list of fields that are not common between said universal database and said local database definition but which are compatible.

5. The method of claim 4 further comprising establishing read only privileges for said local database definition for said fields which are compatible but not in common.

6. The method of claim 4 wherein said list of fields include fields in said local database definition that contain only a portion of fields from said universal database.

7. The method of claim 4 wherein said list of fields include fields in said local database definition that are derived from multiple fields in said universal database.

8. The method of claim 1 further comprising the step of creating fields in said universal database that exist in said local database definition but do not exist in said universal database.

9. The method of claim 1 wherein fields in said local database include one or more of subscriber name, device type, service plan offering, Mobile Station International Subscriber Directory Number (“

MSISDN”

), International Mobile Station Identity (“

IMSI”

), Tariff Plan, Short Message Service (“

SMS”

) Counter, International Voice Call Minutes, Local Call Minutes, Free Call Counter, Data Volume Usage, Language, Barred Services, and Voucher Recharges.

10. The method of claim 1 wherein said application can be one of a customer resource management application, a bundling application, a location application, a Virtual Private Networking application, a Location Based Billing application, a Prepaid billing application, a Missed Call Return application, a Loyalty Reward and Promotion Program application, a Fraud Management application, a Policy Management application, a Call Screening and Redirection application.

11. A data repository system comprising:

a universal database;

a universal database application connected to said universal database;

a plurality of local applications connected to said universal database application;

each of said a local database configured to utilize a local database definition;

said universal database application configured to receive each said local database definition from said local application and to perform a comparison of fields in said universal database with said local database definition;

said universal database application further configured to generate a viewing strategy for said local application;

said viewing strategy based on results of said comparison;

said universal database application further configured to create a view for said local application according to said local database definition based on said viewing strategy such that data in said universal database is viewable in said local application according to said local database definition.

12. The system of claim 11 wherein said universal database application is further configured to serve said local application from said universal database according to said view.

13. The system of claim 11 wherein said viewing strategy includes a list of fields that exist in said universal database that have not been previously used in said local database definition.

14. The system of claim 11 wherein said viewing strategy includes a list of fields that are not common between said universal database and said local database definition but which are compatible.

15. The system of claim 14 wherein said universal database application enforces read only privileges for said local database definition for said fields which are compatible but not in common.

16. The system of claim 14 wherein said list of fields include fields in said local database definition that contain only a portion of fields from said universal database.

17. The system of claim 14 wherein said list of fields include fields in said local database definition that are derived from multiple fields in said universal database.

18. The system of claim 11 further comprising the step of creating fields in said universal database that exist in said local database definition but do not exist in said universal database.

19. The system of claim 11 wherein fields in said local database include one or more of subscriber name, device type, service plan offering, Mobile Station International Subscriber Directory Number (“

MSISDN”

), International Mobile Station Identity (“

IMSI”

), Tariff Plan, Short Message Service (“

SMS”

) Counter, International Voice Call Minutes, Local Call Minutes, Free Call Counter, Data Volume Usage, Language, Barred Services, and Voucher Recharges.

20. The system of claim 11 wherein said local application can be one of a customer resource management application, a bundling application, a location application, a Virtual Private Networking application, a Location Based Billing application, a Prepaid billing application, a Missed Call Return application, a Loyalty Reward and Promotion Program application, a Fraud Management application, a Policy Management application, a Call Screening and Redirection application, a Subscriber Profile Management application.

21. A method of operating a data repository comprising:

receiving a database command message in a local structure from one of a plurality of applications;

each of said applications associated with its own local formats;

each of said local formats sharing at least one common field;

modifying said database command message from said local format to conform with a universal database structure;

forwarding said command message in said universal database structure to a common database;

receiving a response message, responsive to said command message;

from said common database in said universal database structure;

modifying said response message to conform to said local format; and

returning said response to said command message in said local format to said one of said plurality of applications.