Method In A Database Server

• US 20110270807A1
• Filed: 12/30/2008
• Published: 11/03/2011
• Est. Priority Date: 12/30/2008
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Terrill, Stephen, Pudas, Stefan, González López, Maria Pilar, Gomez Maturana, Susana
• Application Number:
  US13/142,629
• Publication Number:
  US 20110270807A1
• Time in Patent Office: Days
• US Class Current: 707/690
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/24564 Applying rules; Deductive queries

Abstract

Method, apparatus and computer program for storing by a database server a plurality of data entries containing data related to a plurality of applications. The database server receives a request to modify the content of a data entry and checks a validation rule related to the entry before performing the modification. The validation rule contains information usable for determining valid data contents that can be stored in said entry, and information for building the validation rule is received from one or more application servers serving said applications. When a back end database server system stores data related to a plurality of applications, data validation check mechanisms are simplified, as information for performing validity checks are received from the application servers in the database system.

Claims

1. A method of storing data in a database server arranged to store data related to a plurality of applications, wherein a data stored for a first application is a data that is used by a second application the method comprising the step of:

receiving a message from an application server serving the first application, the message containing description information (D1) specifying valid data contents for performing a data entry with said database server,

checking (330) by the database server whether any validation rule is already stored for said data entry,

In the event there already exists a validation rule for said data entry,

maintaining unchanged by the database server the previously existing validation rule, or

updating the previously existing validation rule by adding new validation data content provided by said first application;

otherwise,

In the event there is no validation rule already stored for said data entry,

storing, based on the received description information, a validation rule in relationship with the identified data entry.

3. The method of claim 1, wherein a validation rule contains information for determining at least one of:

allowed value ranges, or

allowed value types that can be stored in said entry.

4. The method of claim 1 further comprising the steps of:

receiving a request to modify the content of a data entry from a server serving any of said plurality of applications,

checking said validation rule stored in relationship with at least said data entry, and

performing the requested modification in the event said step of checking determines that there exists no conflict between said requested modification and said existing validation rule.

5. The method of claim 4, wherein the validation rule stored in relationship with said data entry contains information for determining a subsequent data content modification to be made over a second data entry upon a data content modification mode over said first data entry, and wherein the step of performing a requested modification comprises the steps of:

performing by the database server the requested data content modification over the first data entry, and

performing by the database server a subsequent data content modification over the second data entry.

6. The method of claim 1, wherein a server serving any of said plurality of applications is a node of a telecommunications system, and wherein the database server stores data entries arranged to contain data related to a plurality of subscribers of said system usable by at least said node to serve a service to at least one of these subscribers.

2. (canceled)

7. (canceled)

8. (canceled)

13. (canceled)

14. A system for storing data in a database server arranged to store data related to a plurality of applications, wherein a data stored for a first application is a data that is used by a second application, comprising:

means for receiving a message from an application server serving the first application, the message containing description information specifying valid data contents for performing a data entry with said database server,

means for checking by the database server whether any validation rule is already stored for said data; and

In the event there already exists a validation rule for said data entry,

means for updating the previously existing validation rule by adding new validation data content provided by said first application;

otherwise,

In the event there is no validation rule already stored for said data entry,

means for storing based on the received description information, a validation rule in relationship with the identified data entry.

9. The database server of claim 14, wherein the validation rule contains information for determining at least one of:

allowed value ranges, or

allowed value types that can be stored in said entry.

10. The database server of claim 14, further comprising:

means for receiving a request to modify the content of a data entry from a server serving any of said plurality of applications,

means for checking said validation rule stored in relationship with at least said data entry, and

means for performing the requested modification in the event said means for checking determines that there exists no conflict between said requested modification and said existing validation rule

11. The database server of claim 10, wherein the validation rule stored in relationship with said data entry contains information for determining a subsequent data content modification to be made over a second data entry upon a data content modification made over said first data entry, and wherein the means for performing a requested modification comprises:

means for performing a requested data content modification over the first data entry, and

means for performing a subsequent data content modification over the second data entry.

12. The database server of claim 9, wherein a server serving any of said plurality of applications is a node of a telecommunications system, and wherein the database server stores data entries arranged to contain data related to a plurality of subscribers of said system usable by at least said node to serve a service to at least one of these subscribers.

15. A method for storing data associated with a plurality of applications within a telecommunication network wherein said data are stored within a database server node and said plurality of applications are provided by one or more application server node communicably coupled to said database server node, said method comprising the steps of:

receiving a first message from a first application, said first message including first description information specifying the requirements for validating a particular data entry associated with said first application;

storing said description information with said database server node for serving said first application;

receiving a second message from a second application, said second message including second description information specifying the requirements for validating a particular data entry associated with said second application;

updating said description information already stored with said database server to add said second description information;

in response to receiving a request from either said first application or second application for making a data entry into said database server,

performing said requested data entry if said requested data entry complies with requirements associated with said updated description.

16. The method of claim 15 where said first message further includes a particular data entry requested by said first application.

17. The method of claim 15 wherein said step of updating said description information already stored with said database server to add said second description information further comprises the step of checking whether said second description information does not conflict with said already stored description information.

18. The method of claim 17 wherein such conflict includes mutually exclusive conditions required between said stored description information and said second description information.

19. The method of claim 15 wherein said telecommunication network includes an IMS network and said first application includes a call forwarding feature.

20. The method of claim 19 wherein said data entry includes MSISDN number associated with a mobile subscriber within said IMS network.

21. The method of claim 20 wherein said second application includes a SMS feature for said MSISDN number.