Self-provisioning names database for caller identification services

• US 5,940,484 A
• Filed: 04/25/1997
• Issued: 08/17/1999
• Est. Priority Date: 04/25/1997
• Status: Expired due to Term

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: DeFazio, Pamela Lilly, Serinese, Joseph J.
• Primary Examiner(s): Kuntz, Curtis A.
• Assistant Examiner(s): TIEU, BINH KIEN
• Application Number:
  US08/846,076
• Time in Patent Office: 844 Days
• Field of Search: 379/112, 379/115, 379/121, 379/122, 379/125, 379/127, 379/130, 379/134, 379/136, 379/137, 379/139, 379/140, 379/142, 379/45, 379/93.14, 379/93.17, 379/93.23 , 379/93.25, 379/111, 379/120, 379/128, 379/133, 379/242, 379/247, 379/93.01, 379/143, 379/354, 379/355, 379/207, 379/201, 455/415, 455/433, 455/575, 455/566-567
• US Class Current: 379/142.06
• CPC Class Codes: H04M 1/57 Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set at the operator set in a manual exchange H04M5/20
• CPC Class Codes: H04M 3/4931 Directory assistance systems
• CPC Class Codes: H04M 7/12 for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking

Abstract

A self-provisioning names database adds new names to a database for associating names to calling address data in a caller identification with name delivery service. A new caller'"'"'s name is added to the database each time the new caller places a call to a service subscriber. The database reaches only a nominal size in accordance with Perado'"'"'s rule that approximately 80% of incoming calls to a subscriber will be from the same small group of callers. Alternatively or in addition, a new party'"'"'s name is added to the database each time a service subscriber places a call to a party whose name is not already in the names database. Caller names that have been stored in the database and not retrieved for a long period of time are discarded to store new names. Also, the database may periodically request updated data for a stored name, for example, to determine if a different telephone number or address has been assigned to the given name data.

Claims

1. A method of administering a database for use in providing a call party name delivery service comprising the steps of:

receiving at the database party address data at the initiation of a first call;

querying another database for a party name responsive to the received party address data

storing the party name with the party address in the database;

out putting the party name for display prior to answer of the first call;

receiving the same party address data at the initiation of a second call; and

retrieving and outputting the stored party name from the database responsive to the same party address data prior to answer of the second call.

2. A method of administering a database as recited in claim 1 wherein said name querying step comprises an SS7 network query.

3. A method of administering a database as recited in claim 1 wherein said name querying step comprises a local query.

4. A method of administering a database as recited in claim 1 wherein said storing step comprises the step of storing calling party names for a predetermined subset of subscribers.

5. A method of administering a database as recited in claim 1 wherein said party name storage step further comprises storing data representing the date the party name was loaded in the database with the party name and address.

6. A method of administering a database as recited in claim 1 wherein said party name storage step further comprises storing data representing the date of last receipt of party address data for the party name with the party name and address stored in the database.

7. A method of administering a database as recited in claim 1 wherein said party name storage step further comprises incrementing a counter of matches between party name data and stored name data and storing the count of matches with the party name and address stored in the database.

8. A method of administering a database as recited in claim 1 further comprising the step of matching party name data with name data stored in the database.

9. A method of administering a database as recited in claim 8 further comprising the step of incrementing a counter of the number of matches for each match of party name data with stored name data.

10. A method of administering a database as recited in claim 9 further comprising the step of deleting a name record with the least number of matches when a new name record is stored.

11. A method of administering a database as recited in claim 6 further comprising the step of deleting a name record with the oldest date of last receipt when a new name record is stored.

12. A method of administering a database as recited in claim 1 further comprising the step of deleting the oldest name entry when the a new name record is stored and the database reaches a predetermined capacity.

13. A method of administering a database as recited in claim 4 further comprising the step of initiating a query for a new address when the name loaded date is older than a predetermined period.

14. A method of administering a database as recited in claim 13 further comprising the step of loading a new address for a name and updating the date loaded date to the current date if a new number is assigned to the queried name.

15. A method of administering a database as recited in claim 13 further comprising the step of updating the date loaded date to the current date if the name and address data has not changed in response to the query.

16. A method of administering a database as recited in claim 1 wherein said address data receiving step is responsive to an incoming call to a subscriber to the call party name delivery service.

17. A method of administering a database as recited in claim 1 wherein said address data receiving step is responsive to an outgoing call from a subscriber to the call party name delivery service, the party name data being output for display to the subscriber prior to outgoing call answer.

18. A method of administering a database as recited in claim 1 further comprising the steps of:

receiving alternate name data from a subscriber to the call party name delivery service;

storing said alternate name data associated with address data of said subscriber, and

outputting said alternate name data for display prior to call answer.

19. A method of administering a database as recited in claim 1 comprising the initial step of associating said database with a central office switch serving a subscriber of said calling party name delivery service.

20. A method of administering a database as recited in claim 1 comprising the initial step of locating said database on the premises of the user of said service.

21. A method of administering a database as recited in claim 1 comprising the initial step of associating said database with a private branch exchange.

22. A method of administering a database as recited in claim 1 comprising the initial step of associating said database with station apparatus.

23. A method of administering a database as recited in claim 1 further comprising the step of generating calling party name output data for transmission to an output device of a subscriber to the call party name delivery service.

24. A method of administering a database as recited in claim 1 wherein said name querying step comprises the steps of querying a first database for said name and, in the event said query is unsuccessful, querying a second database for said name.

25. A method of administering a database as recited in claim 24 wherein said first database is local and said second database is remote and further comprising the step of

providing a subscriber to the service with data representing the party name identified from the name querying step.

26. A method of providing a service to a user with the use of a first database and a second database, said method comprising the steps of:

receiving party address data at the initiation of a user communication;

querying said first database for a party name responsive to received party address data;

providing said user with data representing a party name from said first database at the initiation of the user communication when the first database querying step is successful,

when the first database querying step is unsuccessful, querying said second database for a party name responsive to received party address data,

providing said user with data representing a party name from said second database at the initiation of the communication when the second database querying step is successful, and

storing name data obtained from the second database querying step in the first database, the name data being associated in the first database with the received party address data.

27. A method of providing a service as recited in claim 26 further comprising the step of

deleting a name record with the least number of matches when said name data from querying said second database is stored in said first database.

28. A method of providing a service as recited in claim 26 further comprising the step of

deleting the oldest name entry in said first database when said name data from querying said second database is stored in said first database.

29. A method of providing a service as recited in claim 26 wherein said name data storage step is performed when said first database has not reached a predetermined capacity.

30. A method of providing a service as recited in claim 29 wherein said name data storage step is performed when said name data is associated with address data within a geographic region served by said first database.

31. A method of providing a service as recited in claim 26 wherein the success of a query is determined by the age of the name data retrieved from the query.

32. A method of providing a service as recited in claim 26 wherein the success of a query is determined from the result of a match between received party address data and stored party address data in one of said databases.

33. A method of providing a service as recited in claim 26 wherein said second database name querying step comprises an SS7 network query.