Method and system for minimizing database structure overhead in handling large volume advanced intelligent network services

• US 6,654,453 B1
• Filed: 12/03/1998
• Issued: 11/25/2003
• Est. Priority Date: 12/03/1998
• Status: Expired due to Fees

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Inventors: Malik, Dale W.
• Primary Examiner(s): Matar, Ahmad F.
• Assistant Examiner(s): BUI, BING Q
• Application Number:
  US09/205,544
• Time in Patent Office: 1,818 Days
• Field of Search: 379/101.01, 379/201.01, 379/207.02, 379/211.01, 379/212, 379/269, 379/207.11, 379/221.08, 379/230, 707/104.1
• US Class Current: 379/201.01
• CPC Class Codes: H04M 3/42153 by subscriber
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking

Abstract

A method and system for minimizing database overhead associated with AIN services includes a cascaded database structure having at least two databases. The first database is a seed database containing basic information about the subscriber and his available services. The second database is a real-time database containing additional information that will be used by the appropriate service application. When the subscriber initially requests the service, the service management system creates an entry in the seed database for the subscriber. The entry contains an identifier for the subscriber and an identifier for the service. Until the subscriber actually uses the service, the seed database remains the only entry for the subscriber. When the subscriber actually uses the service, the service application reads the seed database to determine the privileges for the subscriber and creates a larger entry in the real-time database. The service application may not write to the seed database. When the subscriber cancels the service, both the seed database entry and the real-time database entry are removed.

Claims

1. A system for using databases in providing telecommunications services to a subscriber in an intelligent network, the system comprising:

a seed database storing information regarding a selection of services associated with the subscriber;

a real-time application database storing information for use in providing a service to the subscriber with the real-time application database not storing specific information about the subscriber until the subscriber makes a use of the service; and

a service application, resident on at least one computer in the network, that creates entries in the real-time application database using information from the seed database upon the use of the service by the subscriber.

2. The system for using databases, as recited in claim 1, further comprising a service management system that creates entries in the seed database when the subscriber subscribes to the service.

3. The system for using databases, as recited in claim 1, wherein the seed database is coupled to a service control point.

4. The system for using databases, as recited in claim 1, wherein the seed database includes an entry for the subscriber, each entry comprising:

a subscriber identifier field storing information identifying the subscriber; and

a service identifier field storing information identifying the service.

5. The system for using databases, as recited in claim 1, wherein the application may only read from the seed database.

6. The system for using databases, as recited in claim 1, further comprising a service circuit node operative to collect information from the subscriber relative to the service and further operative to provide the collected information to the service application.

7. The system for using databases, as recited in claim 6, wherein the service application, in response to receiving the collected information from the service circuit node, searches the real-time database to determine whether an entry exists for the subscriber.

8. In an advanced intelligent network, a method for using databases in providing telecommunications service to a subscriber to minimize database overhead, the method comprising:

receiving a request for the service from the subscriber;

in response to the request, storing information associating the subscriber and the service in a seed database;

receiving a request to use the service from the subscriber;

in response to the request to use the service, accessing a real-time database to determine whether an entry exists for the subscriber;

in response to failing to find an entry for the subscriber in the real-time database, accessing the seed database to obtain the information regarding the subscriber;

storing the information regarding the subscriber and information for use in providing the service to the subscriber in the real-time database.

9. The method for using databases, as recited in claim 8, wherein storing information regarding the subscriber and the service in a seed database further comprises:

creating an entry in the seed database, the entry comprising;

a subscriber identifier field storing information identifying the subscriber; and

a service identifier field storing information identifying the service.

10. The method for using databases, as recited in claim 8, further comprising:

collecting information from the subscriber regarding the service.

11. The method for using databases, as recited in claim 8, further comprising:

receiving a request to cancel the service from the subscriber; and

removing the information from the real-time database.

12. The method for using databases, as recited in claim 11, further comprising removing the information from the seed database.

13. The method for using databases, as recited in claim 8, wherein storing information in the seed database is performed by a service management system.

14. The method for using databases, as recited in claim 8, wherein storing information in the real-time database is performed by a service application that performs the requested service.

15. The method for using databases, as recited in claim 8, wherein accessing the seed database is performed by a service application that performs the requested service.

16. The method for using databases, as recited in claim 8, wherein the seed database may not be written to by a service application performing the requested service.

17. In an intelligent network, a system for providing a telecommunications service to a subscriber, the system comprising:

an advanced intelligent network (“

AIN”

) element;

a seed database storing a selection of particular services associated with the subscriber;

a real-time application database storing information for use in providing the service to the subscriber with the real-time application database not storing specific information about the subscriber until the subscriber makes a use of the service; and

a service application, resident on at least one computer in the network, that creates entries in tile real-time application database upon use of the service by the subscriber.

18. With respect to a real-time database used in providing telecommunications services, a method of minimizing the number of entries in the real-time database yet having information available to the real-time database when needed for provision of a service to a user, comprising:

in response to a user'"'"'s subscription to a service, storing information about the user and the service in a seed database instead of the real-time database; and

in response to a user'"'"'s activation of the service, causing an application implementing the service

to obtain the information from the seed database, and

to create an entry with the information from the seed database in the real-time database,

whereby the number of entries in the real-time database is minimized by the failure to create the entry in the real-time database in response to the user'"'"'s subscription to the service and by the delay in creating the entry in the real-time database until the user'"'"'s activation of the service.

19. The method of claim 18, wherein, prior to the application obtaining the information from the seed database, the application fails to find the entry with the information in the real-time database.

20. The method of claim 18, further comprising:

in response to de-activation of the service by the user, removing the entry with the information from the real-time database, but not removing the information from the seed database.

21. With respect to a real-time database used in providing telecommunications services, a system for minimizing the number of entries in the real-time database yet having information available to the real-time database when needed for provision of a service to a user, comprising:

seed database for storing information associating the user and the service in response to a user'"'"'s subscription to the service; and

an application operative to respond to a user'"'"'s activation of the service by obtaining the information from the seed database and by creating an entry with the information from the seed database in the real-time database.

22. The system of claim 21, wherein, prior to the application obtaining the information from the seed database, the application fails to find the entry with the information in the real-time database.

23. The method of claim 21, wherein the application is responsive to de-activation of the service by the user by removing the entry with the information from the real-time database, but not removing the information from the seed database.