CA2232319C - A self-provisioning names database for caller identification services - Google Patents
A self-provisioning names database for caller identification services Download PDFInfo
- Publication number
- CA2232319C CA2232319C CA002232319A CA2232319A CA2232319C CA 2232319 C CA2232319 C CA 2232319C CA 002232319 A CA002232319 A CA 002232319A CA 2232319 A CA2232319 A CA 2232319A CA 2232319 C CA2232319 C CA 2232319C
- Authority
- CA
- Canada
- Prior art keywords
- database
- name
- party
- recited
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
- H04M3/4931—Directory assistance systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/57—Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
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 newcaller 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.
Description
A SELF-PROVISICINING NAMES DATABASE
FOR CALLER ID>E;NTIFICATION SERVICES
BACKGROUND OF THE INVENTION
1. Technical Field This invention relates to telecommunications services for providing caller identification information to a called party and, more particularly, to a self provisioning names database for such services.
FOR CALLER ID>E;NTIFICATION SERVICES
BACKGROUND OF THE INVENTION
1. Technical Field This invention relates to telecommunications services for providing caller identification information to a called party and, more particularly, to a self provisioning names database for such services.
2. Description of the Relevant Art Over the years caller services have increased due to the computerization of telecommunications services. For example, one such service that is now provided to telecommunications subscribers is caller identification. As a caller places a telecommunications call to a called party and enters address signaling data for signaling the called party, both the calling party's telephone number and the called party's telephone number are transmitted to the telecommunications switch, typically a Lucent Technologies #SESS electronic switch, serving the called party. As the called party's line rings, the switch serving the called party also provides data to the subscriber loop or trunk to the subscriber's premises which can actuate a display to display the calling party's telephone number at the called party's premises.
Since the introduction of the caller identification service by telephone number, local operating telephone companies have also offered a related service for providing the name of the calling party. Subscribers to such a service are provided a display of both the telephone number and name of the calling party for an extra fee. The local operating telephone company will generate a query during a call of a remote billing database, for example, a database maintained by the operating telephone company serving the calling party, to perform a number to name translation and forward the name data to the calling party along with the telephone number for display. Others besides the operating telephone companies may maintain a similar database that may attempt to maintain a names list, for example, for all the telephones in an, entire country or region thereof. Of course, any such entity may charge for access to such a regional or national database that it maintains.
A problem persists, however, in that in providing such name identification services, the local operating telephone companies must rely on other telephone companies or national database access providers to provide the name information. Also, the information may not be provided in time to be signaled via a subscriber's display before the subscriber must answer the phone.
Finally, the costs of providing such a service may become high in relation to the perceived value to the customer. Consequently, there remains a need in the art to provide a caller identification by number and name service that is economical and efficient.
SUMMARY OF THE INVENTION
In accordance with one aspect of the present invention there is provided 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 outputting 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.
Since the introduction of the caller identification service by telephone number, local operating telephone companies have also offered a related service for providing the name of the calling party. Subscribers to such a service are provided a display of both the telephone number and name of the calling party for an extra fee. The local operating telephone company will generate a query during a call of a remote billing database, for example, a database maintained by the operating telephone company serving the calling party, to perform a number to name translation and forward the name data to the calling party along with the telephone number for display. Others besides the operating telephone companies may maintain a similar database that may attempt to maintain a names list, for example, for all the telephones in an, entire country or region thereof. Of course, any such entity may charge for access to such a regional or national database that it maintains.
A problem persists, however, in that in providing such name identification services, the local operating telephone companies must rely on other telephone companies or national database access providers to provide the name information. Also, the information may not be provided in time to be signaled via a subscriber's display before the subscriber must answer the phone.
Finally, the costs of providing such a service may become high in relation to the perceived value to the customer. Consequently, there remains a need in the art to provide a caller identification by number and name service that is economical and efficient.
SUMMARY OF THE INVENTION
In accordance with one aspect of the present invention there is provided 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 outputting 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.
In accordance with another aspect of the present invention there is provided 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 o~ 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.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is a typical system diagram showing the self provisioning names database associated with a local telecommunications switch.
Figure 2 shows a typical field for a names record of the self provisioning database.
Figure 3 is a flowchart showing typical caller flow.
Figure 4 is a typical flowchart describing the self provisioning feature of the database.
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.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is a typical system diagram showing the self provisioning names database associated with a local telecommunications switch.
Figure 2 shows a typical field for a names record of the self provisioning database.
Figure 3 is a flowchart showing typical caller flow.
Figure 4 is a typical flowchart describing the self provisioning feature of the database.
Figure 5, similar to Figure 1, provides a more detailed system block diagram for describing one system implementation of the database for use in explaining the flowcharts of Figures 3 and 4.
DETAILED DESCRIPTION
Referring to Figure 1, there is shown a typical system diagram for describing the database of the present invention. A calling party 1 places a call through the public switched telephone network 2 and is ultimately connected to a local switch 3 serving a called subscriber 4 having a telephone and an associated caller identification display unit 4a. A number to name translation database 5 may comprise a database of a personal computer equipped with private line or switched modem access to local switch 3. Database 5 may be preferably located as close to the called subscriber 4 as. possible and may be located, for example, at a central office serving the subscriber 4, at a private branch exchange (not shown) or on the customer's premisca. Also associated with the names database 5 there is shown a separate link to a typical national or other names database 6.
Names database 6 typically on request of switch 3 performs a translation from a telephone address such as a telephone number or Internet address to a name and forwards fro display on display 4a. Now, in order to build a local names database 5 according to the present invention, the names translation result is reported to the database 5 on request.
There may be more than one such names database 5 under processor control, for example, one for each local telephone operating company, Internet service provider, private branch exclhange owner, station apparatus owner or other alternative database. Each performs the similar function of converting an address to a name and reporting the result.
Referring to Figure 1, the operation of the names database S will be briefly explained. When a caller first calls a database subscriber 4 (one who subscribes to the names database service), the local switch (or private branch exchange switch) is unable to forward an associated name to the subscriber display apparatus 4a. It can forward. other information known of the calling party such as a calling party's address or telephone number.
The local switch (or private branch exchange switch) requests the names database 5 to provide such a name. Database 5 queries itself, but, finding no name in its database associated with the calling party's address, database 5 initiates a further query to national dlatabase 6. If no response is forthcoming from database 6, the database 5 may request the information of an alternative database like a database (not shown), for example, of a local operating telephone company or a private names database.
If a name reply is retrieved, an entry is recorded in the self provisioning names database 5 in conformity with Figure 2. Figure 2 suggests that the data record for database 5 comprise a telephone number (or Internet address) 201, a name associated with the number or address 202, a count or number of hits 203, a date and time of the last hit 204 and a date and time of the first hit or when originally the name record was loaded 205 into the names database 5. A group 10 of subscribers share names database: 5 so that a name of a caller, even if the caller calls more than one subscriber, is typically only stored in the database once.
Now, in an embodiment not shown, there may be plural names associated with a single number or a nickname such as "mom" or "dad" that may be added/modified by a subscriber through a secure dial-in connection via the Internet or a telecommunications link to the names database 5. For example, if (540) 349-1757 represents the telephone number for "mom"and "dad", an associated station apparatus display 4a may indicate "mom and dad" instead of their directory listing names either together with their phone number or in place of their telephone number if a call is either directed to or from them. On the other hand, if called party A and called party B, who both subscribe to the names database service of the present invention, receive a call from the same calling party C, the name of calling party C may only appear once in the database 5 in order to save data storage capability in the database 5. Consequently, providing nicknames or plural names in the database for the same calling party C
requires additional memory. The record of Figure 2 would have to be modified to permit personalization information. This information would include the subscriber's telephone number and their personal name for Name field 202. An additional fee may be charged for the plural name storage or nickname storage service.
The field or display size of display 4a may be varied accordingly to _7_ accommodate alternate names, plural names or nick names as appropriate.
For the first call to a subscriber or by that subscriber, the database 5 may already have the name of the other party than the subscriber in their database because another subscriber may have already placed a call or received a call from that party. If not, a query must be made of database 6. If a reply is received from database 6 before the subscriber 4 answers the call, the display 4a can be updated with the name of the calling; party stored in the database 6 for the number of the caller. Also, the name received from database 6 is added to database 5 according to the suggestf;d format for Name 202 of Figure 2 along with their Phone number 201 and date loaded 205. More importantly, the next time that named caller calls subscriber 4 or any other subscriber to the names database 5, no query need be formulated of any database 6 from database 5. The self provisioning database 5 simply updates the count of the number of hits (Figure 2) from one to two and the date of the last hit 204 to the current date, and time and the expense of a query of database 6 is saved.
In accordance with the above discussion, the storage of a name or the updating of a name file according to~ Figure 2 is initiated on a call that terminates with a subscriber 4 of the present names database 5. In an alternative embodiment, the initiation of the storage of a name or a file update can be triggered by an outgoing call by a subscriber to the present database 5. That is, when a subscriber 4 initiates a call, l:he name query will be made of database unless the telephone number 201 is ;already in the database 5. According to an extension of Perado's Rule, the called name will likely be a frequent caller to the subscriber 4. Database 5 will store or update a record according to Figure 2 and be able to identify the name of the party the next time the called party calls the subscriber. In a further embodiment, the called party's name can be added to the database or the number of hits incremented and the date of last hit updated in either the event of a call by subscriber 4 to the named called party or when the called party calls the subscriber 4. On an outgoing call, displaying the name of a called party at subscriber display 4a provides feedback that the subscriber dialed _g_ the correct telephone number by providing the called party's name (which can supplement a display dialed number arrangement).
Referring to Figure 3, the call process will be described in greater detail with reference to Figures 1 and 2 and Figure 5. In the described embodiment, the addition of a name to the database is triggered by the placement of an incoming call to a subscriber to the .database 5 of Figure 1. An embodiment in which the addition of a name to database 5 is triggered by an outgoing call or either an incoming call or outgoing call is not shown but may be easily implemented by one of ordinary skill in the art and without having to resort to undue experimentation.
Figures 3 and 5, similar to Figure 1, describes a particular implementation of the calling party/names self provisioning database 5 but implemented in a Signaling System 7 (SS7) environment. Similar reference numerals are used in Figure 5 to denote similarly depicted elements in Figure 1.
Figure 3A describes steps 301-309 of the process; Figure 3B describes steps 315 of the process; and Figure 3C describes steps 316-318 of the process.
Arrows are used generally to indicate process flow; however, the process flow should not be deemed to be limited to the depicted process as steps may occur either before or after other steps in tlhe flow. For example, steps 312 and may be reversed in order and time among others.
Referring to Figure 3, at step 301, a caller A initiates a call to called party B. Schematically, caller A may be calling party 1 and called party B, subscriber apparatus 4, according to Figure 1.
At step 302 and referring to :Figure 5, originating local switch C (a part of the public switched network cloud 2 of Figure 1 ), based on the dialed digits received from caller A, begins signaling to establish a voice/data link between caller A and called party B connected to a terminating central office D, designated local switch 3. The sign<~ling information, including calling party number of caller A (CgPN-A) and the called party number of called party B
(CdPN-B), is forwarded to local switch 3 via a signaling link.
At step 303, the call may be routed via one or more intermediate switches in one or more public switched telephone networks J (cloud 2) to local switch 3.
These switches may comprise tandem switches and/or toll centers where voice/data links known as trunks arc: provided via satellite, optic fiber, coaxial 5 cable, land-based microwave and other facilities known in the art (not shown).
At step 304, at least a signaling link will be terminated at local switch 3 and, via the signaling link, at least tl~e terminating central office D
(switch 3) will receive the calling party telephone number or address CgPN-A and the called party number or address CdPN-B.
At step 305, the terminating office D (switch 3) will first determine what services, if any, the called party B has subscribed to, for example, the caller identification including name service of the present invention and referred to in the drawing as Calling Name Delivery Service. This may be accomplished by local switch 3 referring to a local service database (not shown) which associates a called party with the services they have subscribed to.
At step 306, to determine thc: services subscribed to by called party B, a database controller may perform a service look-up query from local switch 3.
If the called party B is a subscriber to the caller name service, then, the local switch 3 initiates the creation and transmittal of an SS7 or related query for processing.
20 The query may include a service indlicator for the present service (for example, shorthand data representing Caller rdame Delivery if the service is so named) and the calling party's telephone number CgPN-A.
At step 307, the SS7 network K, using, for example, Global Title Translation or related translation service, routes the query to a first SS7 processor F for processing. Processor F may be associated with database 5 shown in Figure 1. Processor F may have a local names database, I.
Alternatively, the SS7 network K, using, for example, Global Title Translation, might route the query to another, perhaps regional SS7 processor, m, having a names database, N.
At step 308, processor F checks its Name Database I (name database 5) for a match with CgPN-A. If a match is found, then, call progress steps to step 316 below. If not, call progress proceeds with step 309.
At step 309, when no match is found, the SS7 processor F initiates a query via, for example, a standard interface (e.g. telecommunications protocol/Internet Protocol (TCP/IP) interface) to Names Processor G associated with a database 6, which may be a national or other regional database or private database. The query should include the CgPN-A information, including area and even country code as required internationally to uniquely identify a calling subscriber, Name-A.
Names processor, G, at step 310~looks up CgPN-A to determine the corresponding Name-A.
At step 311, names processor G creates and transmits a query response containing CgPN-A and Name-A to SS7 Processor F (if it can).
At step 312, the SS7 processor F, responsive to receipt of the names processor response, creates and transmits a related query response via the SS7 network K to terminating end office D (local switch 3). The response includes Name-A.
At step 313, the SS7 processor F replaces the entry in Names Database I
(database 6) with the least number of queries and the least recent query (for entries with the same number of queries) with the CgPN-A, Name-A entry and other data per Figure 2. In particular, the current data will be populated in the fields for date loaded and date of last hit, and the query counter (number of hits field) will be incremented by one (and for the first hit be recorded as 1 ).
In furtherance of step 313, the conditions for replacement of old data may vary from requiring both least number of queries and least recent query to one or the other or other criteria that may developed therefrom such as number of hits over most recent unit of time (for example, number of hits in the last three month period).
In step 314, terminating end office D completes the call to called party B
and sends Name A data to Called Party B's display using, for example, in-band, ISDN or other signaling means.
At step 315, the display box of apparatus 4 interprets the incoming signaling data and displays calling party A's name. Step 315, thus, is the end of caller name processing if the name i s not already stored in database 5.
At step 316, following step 308, if a match is found in database 5, Names Database, I, to match with CgPN-A then, SS7 Processor F creates and transmits an SS7 query response via SS7 netvrork K containing Name-A to terminating central office switch D (switch 3).
At step 317, the entry for Cg;PN-A in the Names Table is updated per Figure 2, the count of hits 203 incremented by one, the date of this hit recorded as the last hit 204 and so on.
Step 318 relates to the display of the data at the subscriber apparatus 4 and so relates to the performance of steps 314 and 315. This is the end of call flow for CgPN in the Names Database I (database 5).
A slight variation relates to a situation when a first database 6 fails to provide a Name for a calling party. As described above, a TCP/IP query may result in a query of more than one database, but even these may come up empty.
Then, a back-up list of databases may be contacted for Name-A by other than a TCP-IP query, for example, by way of a dial up connection to a private database.
The name that is eventually retrieved may not be timely retrieved so it can be displayed in this call, but it may be locally stored in database 6 for the next call from that calling party A.
Note that as calls are compleaed to the local switch 3 and its group of subscribers to names services, the database will efficiently collect, store and maintain names that are likely candidates for repeats or hits according to Perado's Rule. Consequently, the names database should reach a size that becomes only dynamic in the sense that the desire for the service may grow.
The subscriber likely will continue to receive calls from the same calling parties. So once the database is grown and leartled, it assumes a relatively stable size.
Old names are automatically deleted and., often times, will be deleted, not so much because they have not called recently, but because, in fact, they have moved or changed telephone numbers.
Referring now to Figure 4, the non real-time self provisioning feature of the database 5 will be further described. In addition to the real-time provisioning feature where the database 5 learns .as described above the names of calling parties that are likely callers of called party 4, a non-real-time background provisioning activity is needed and described by Figure 4. This activity accounts for numbers that have been reassigned to new users.
According to step 401 and again referring to Figure 5, if the date loaded field for an entry (for example, CgPN-L) to Names Database I (database 5) is older than a to-be-provisioned time (for example, one month), then the SS7 processor F will create and transmit a query to Names Processor G (database 6) for an update.
At step 402, if the name, Name-L, matches an existing name field Name for CgPN-L, then the Date Loaded field 205 is updated to the current date and all other fields remain the same.
At step 403, if the name Narne-L does not match the existing name field Name 202 for entry CgPN-L, then tlhe Names field 202 is updated with the Name-L provided by the Names Database F and the Date Loaded field 205 is updated with the current date.
In this manner, off line, the value of the names data stored locally in database 5 can be periodically reevaluated.
The present invention is provided by way of description of one embodiment. The principles of the invention may be extended to providing names entries for telecommunications related services such as Internet services, television/video conferencing services and the like. The names database and service may be implemented at an e:nd office switch or in association with a private branch exchange on or off a customer's premises. ISDN or SS7 signaling may be used for the names query. In yet another embodiment, telephone station apparatus may been designed to penmit local storage of a names database for a residential user or group of subscribers for translating the forwarded calling party's telephone number into the caller's name or a shorthand therefor. The scope of the invention should only be deemed limited by the claims which follow.
DETAILED DESCRIPTION
Referring to Figure 1, there is shown a typical system diagram for describing the database of the present invention. A calling party 1 places a call through the public switched telephone network 2 and is ultimately connected to a local switch 3 serving a called subscriber 4 having a telephone and an associated caller identification display unit 4a. A number to name translation database 5 may comprise a database of a personal computer equipped with private line or switched modem access to local switch 3. Database 5 may be preferably located as close to the called subscriber 4 as. possible and may be located, for example, at a central office serving the subscriber 4, at a private branch exchange (not shown) or on the customer's premisca. Also associated with the names database 5 there is shown a separate link to a typical national or other names database 6.
Names database 6 typically on request of switch 3 performs a translation from a telephone address such as a telephone number or Internet address to a name and forwards fro display on display 4a. Now, in order to build a local names database 5 according to the present invention, the names translation result is reported to the database 5 on request.
There may be more than one such names database 5 under processor control, for example, one for each local telephone operating company, Internet service provider, private branch exclhange owner, station apparatus owner or other alternative database. Each performs the similar function of converting an address to a name and reporting the result.
Referring to Figure 1, the operation of the names database S will be briefly explained. When a caller first calls a database subscriber 4 (one who subscribes to the names database service), the local switch (or private branch exchange switch) is unable to forward an associated name to the subscriber display apparatus 4a. It can forward. other information known of the calling party such as a calling party's address or telephone number.
The local switch (or private branch exchange switch) requests the names database 5 to provide such a name. Database 5 queries itself, but, finding no name in its database associated with the calling party's address, database 5 initiates a further query to national dlatabase 6. If no response is forthcoming from database 6, the database 5 may request the information of an alternative database like a database (not shown), for example, of a local operating telephone company or a private names database.
If a name reply is retrieved, an entry is recorded in the self provisioning names database 5 in conformity with Figure 2. Figure 2 suggests that the data record for database 5 comprise a telephone number (or Internet address) 201, a name associated with the number or address 202, a count or number of hits 203, a date and time of the last hit 204 and a date and time of the first hit or when originally the name record was loaded 205 into the names database 5. A group 10 of subscribers share names database: 5 so that a name of a caller, even if the caller calls more than one subscriber, is typically only stored in the database once.
Now, in an embodiment not shown, there may be plural names associated with a single number or a nickname such as "mom" or "dad" that may be added/modified by a subscriber through a secure dial-in connection via the Internet or a telecommunications link to the names database 5. For example, if (540) 349-1757 represents the telephone number for "mom"and "dad", an associated station apparatus display 4a may indicate "mom and dad" instead of their directory listing names either together with their phone number or in place of their telephone number if a call is either directed to or from them. On the other hand, if called party A and called party B, who both subscribe to the names database service of the present invention, receive a call from the same calling party C, the name of calling party C may only appear once in the database 5 in order to save data storage capability in the database 5. Consequently, providing nicknames or plural names in the database for the same calling party C
requires additional memory. The record of Figure 2 would have to be modified to permit personalization information. This information would include the subscriber's telephone number and their personal name for Name field 202. An additional fee may be charged for the plural name storage or nickname storage service.
The field or display size of display 4a may be varied accordingly to _7_ accommodate alternate names, plural names or nick names as appropriate.
For the first call to a subscriber or by that subscriber, the database 5 may already have the name of the other party than the subscriber in their database because another subscriber may have already placed a call or received a call from that party. If not, a query must be made of database 6. If a reply is received from database 6 before the subscriber 4 answers the call, the display 4a can be updated with the name of the calling; party stored in the database 6 for the number of the caller. Also, the name received from database 6 is added to database 5 according to the suggestf;d format for Name 202 of Figure 2 along with their Phone number 201 and date loaded 205. More importantly, the next time that named caller calls subscriber 4 or any other subscriber to the names database 5, no query need be formulated of any database 6 from database 5. The self provisioning database 5 simply updates the count of the number of hits (Figure 2) from one to two and the date of the last hit 204 to the current date, and time and the expense of a query of database 6 is saved.
In accordance with the above discussion, the storage of a name or the updating of a name file according to~ Figure 2 is initiated on a call that terminates with a subscriber 4 of the present names database 5. In an alternative embodiment, the initiation of the storage of a name or a file update can be triggered by an outgoing call by a subscriber to the present database 5. That is, when a subscriber 4 initiates a call, l:he name query will be made of database unless the telephone number 201 is ;already in the database 5. According to an extension of Perado's Rule, the called name will likely be a frequent caller to the subscriber 4. Database 5 will store or update a record according to Figure 2 and be able to identify the name of the party the next time the called party calls the subscriber. In a further embodiment, the called party's name can be added to the database or the number of hits incremented and the date of last hit updated in either the event of a call by subscriber 4 to the named called party or when the called party calls the subscriber 4. On an outgoing call, displaying the name of a called party at subscriber display 4a provides feedback that the subscriber dialed _g_ the correct telephone number by providing the called party's name (which can supplement a display dialed number arrangement).
Referring to Figure 3, the call process will be described in greater detail with reference to Figures 1 and 2 and Figure 5. In the described embodiment, the addition of a name to the database is triggered by the placement of an incoming call to a subscriber to the .database 5 of Figure 1. An embodiment in which the addition of a name to database 5 is triggered by an outgoing call or either an incoming call or outgoing call is not shown but may be easily implemented by one of ordinary skill in the art and without having to resort to undue experimentation.
Figures 3 and 5, similar to Figure 1, describes a particular implementation of the calling party/names self provisioning database 5 but implemented in a Signaling System 7 (SS7) environment. Similar reference numerals are used in Figure 5 to denote similarly depicted elements in Figure 1.
Figure 3A describes steps 301-309 of the process; Figure 3B describes steps 315 of the process; and Figure 3C describes steps 316-318 of the process.
Arrows are used generally to indicate process flow; however, the process flow should not be deemed to be limited to the depicted process as steps may occur either before or after other steps in tlhe flow. For example, steps 312 and may be reversed in order and time among others.
Referring to Figure 3, at step 301, a caller A initiates a call to called party B. Schematically, caller A may be calling party 1 and called party B, subscriber apparatus 4, according to Figure 1.
At step 302 and referring to :Figure 5, originating local switch C (a part of the public switched network cloud 2 of Figure 1 ), based on the dialed digits received from caller A, begins signaling to establish a voice/data link between caller A and called party B connected to a terminating central office D, designated local switch 3. The sign<~ling information, including calling party number of caller A (CgPN-A) and the called party number of called party B
(CdPN-B), is forwarded to local switch 3 via a signaling link.
At step 303, the call may be routed via one or more intermediate switches in one or more public switched telephone networks J (cloud 2) to local switch 3.
These switches may comprise tandem switches and/or toll centers where voice/data links known as trunks arc: provided via satellite, optic fiber, coaxial 5 cable, land-based microwave and other facilities known in the art (not shown).
At step 304, at least a signaling link will be terminated at local switch 3 and, via the signaling link, at least tl~e terminating central office D
(switch 3) will receive the calling party telephone number or address CgPN-A and the called party number or address CdPN-B.
At step 305, the terminating office D (switch 3) will first determine what services, if any, the called party B has subscribed to, for example, the caller identification including name service of the present invention and referred to in the drawing as Calling Name Delivery Service. This may be accomplished by local switch 3 referring to a local service database (not shown) which associates a called party with the services they have subscribed to.
At step 306, to determine thc: services subscribed to by called party B, a database controller may perform a service look-up query from local switch 3.
If the called party B is a subscriber to the caller name service, then, the local switch 3 initiates the creation and transmittal of an SS7 or related query for processing.
20 The query may include a service indlicator for the present service (for example, shorthand data representing Caller rdame Delivery if the service is so named) and the calling party's telephone number CgPN-A.
At step 307, the SS7 network K, using, for example, Global Title Translation or related translation service, routes the query to a first SS7 processor F for processing. Processor F may be associated with database 5 shown in Figure 1. Processor F may have a local names database, I.
Alternatively, the SS7 network K, using, for example, Global Title Translation, might route the query to another, perhaps regional SS7 processor, m, having a names database, N.
At step 308, processor F checks its Name Database I (name database 5) for a match with CgPN-A. If a match is found, then, call progress steps to step 316 below. If not, call progress proceeds with step 309.
At step 309, when no match is found, the SS7 processor F initiates a query via, for example, a standard interface (e.g. telecommunications protocol/Internet Protocol (TCP/IP) interface) to Names Processor G associated with a database 6, which may be a national or other regional database or private database. The query should include the CgPN-A information, including area and even country code as required internationally to uniquely identify a calling subscriber, Name-A.
Names processor, G, at step 310~looks up CgPN-A to determine the corresponding Name-A.
At step 311, names processor G creates and transmits a query response containing CgPN-A and Name-A to SS7 Processor F (if it can).
At step 312, the SS7 processor F, responsive to receipt of the names processor response, creates and transmits a related query response via the SS7 network K to terminating end office D (local switch 3). The response includes Name-A.
At step 313, the SS7 processor F replaces the entry in Names Database I
(database 6) with the least number of queries and the least recent query (for entries with the same number of queries) with the CgPN-A, Name-A entry and other data per Figure 2. In particular, the current data will be populated in the fields for date loaded and date of last hit, and the query counter (number of hits field) will be incremented by one (and for the first hit be recorded as 1 ).
In furtherance of step 313, the conditions for replacement of old data may vary from requiring both least number of queries and least recent query to one or the other or other criteria that may developed therefrom such as number of hits over most recent unit of time (for example, number of hits in the last three month period).
In step 314, terminating end office D completes the call to called party B
and sends Name A data to Called Party B's display using, for example, in-band, ISDN or other signaling means.
At step 315, the display box of apparatus 4 interprets the incoming signaling data and displays calling party A's name. Step 315, thus, is the end of caller name processing if the name i s not already stored in database 5.
At step 316, following step 308, if a match is found in database 5, Names Database, I, to match with CgPN-A then, SS7 Processor F creates and transmits an SS7 query response via SS7 netvrork K containing Name-A to terminating central office switch D (switch 3).
At step 317, the entry for Cg;PN-A in the Names Table is updated per Figure 2, the count of hits 203 incremented by one, the date of this hit recorded as the last hit 204 and so on.
Step 318 relates to the display of the data at the subscriber apparatus 4 and so relates to the performance of steps 314 and 315. This is the end of call flow for CgPN in the Names Database I (database 5).
A slight variation relates to a situation when a first database 6 fails to provide a Name for a calling party. As described above, a TCP/IP query may result in a query of more than one database, but even these may come up empty.
Then, a back-up list of databases may be contacted for Name-A by other than a TCP-IP query, for example, by way of a dial up connection to a private database.
The name that is eventually retrieved may not be timely retrieved so it can be displayed in this call, but it may be locally stored in database 6 for the next call from that calling party A.
Note that as calls are compleaed to the local switch 3 and its group of subscribers to names services, the database will efficiently collect, store and maintain names that are likely candidates for repeats or hits according to Perado's Rule. Consequently, the names database should reach a size that becomes only dynamic in the sense that the desire for the service may grow.
The subscriber likely will continue to receive calls from the same calling parties. So once the database is grown and leartled, it assumes a relatively stable size.
Old names are automatically deleted and., often times, will be deleted, not so much because they have not called recently, but because, in fact, they have moved or changed telephone numbers.
Referring now to Figure 4, the non real-time self provisioning feature of the database 5 will be further described. In addition to the real-time provisioning feature where the database 5 learns .as described above the names of calling parties that are likely callers of called party 4, a non-real-time background provisioning activity is needed and described by Figure 4. This activity accounts for numbers that have been reassigned to new users.
According to step 401 and again referring to Figure 5, if the date loaded field for an entry (for example, CgPN-L) to Names Database I (database 5) is older than a to-be-provisioned time (for example, one month), then the SS7 processor F will create and transmit a query to Names Processor G (database 6) for an update.
At step 402, if the name, Name-L, matches an existing name field Name for CgPN-L, then the Date Loaded field 205 is updated to the current date and all other fields remain the same.
At step 403, if the name Narne-L does not match the existing name field Name 202 for entry CgPN-L, then tlhe Names field 202 is updated with the Name-L provided by the Names Database F and the Date Loaded field 205 is updated with the current date.
In this manner, off line, the value of the names data stored locally in database 5 can be periodically reevaluated.
The present invention is provided by way of description of one embodiment. The principles of the invention may be extended to providing names entries for telecommunications related services such as Internet services, television/video conferencing services and the like. The names database and service may be implemented at an e:nd office switch or in association with a private branch exchange on or off a customer's premises. ISDN or SS7 signaling may be used for the names query. In yet another embodiment, telephone station apparatus may been designed to penmit local storage of a names database for a residential user or group of subscribers for translating the forwarded calling party's telephone number into the caller's name or a shorthand therefor. The scope of the invention should only be deemed limited by the claims which follow.
Claims (33)
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;
outputting 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.
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;
outputting 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 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.
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.
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.
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.
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.
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.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US08/846,076 US5940484A (en) | 1997-04-25 | 1997-04-25 | Self-provisioning names database for caller identification services |
| US08/846,076 | 1997-04-25 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2232319A1 CA2232319A1 (en) | 1998-10-25 |
| CA2232319C true CA2232319C (en) | 2001-05-22 |
Family
ID=25296875
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002232319A Expired - Fee Related CA2232319C (en) | 1997-04-25 | 1998-03-17 | A self-provisioning names database for caller identification services |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US5940484A (en) |
| CA (1) | CA2232319C (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9143612B2 (en) | 2012-11-02 | 2015-09-22 | Ian James Roncoroni | Centralized caller profile system and methods for routing and prioritizing calls |
Families Citing this family (87)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| BR9809275A (en) * | 1997-05-09 | 2000-06-27 | Alcatel Usa Sourcing Lp | Multiple scp communication system |
| FI974259A (en) * | 1997-11-17 | 1999-05-18 | Nokia Telecommunications Oy | Dissemination of information in connection with the establishment of a call |
| US6779358B2 (en) * | 1997-12-30 | 2004-08-24 | International Water Makers, Inc. | Water collection and dispensing machine |
| US6330308B1 (en) * | 1998-04-09 | 2001-12-11 | Bell Atlantic Network Services, Inc. | Voice mail system for obtaining forwarding number information from directory assistance systems having speech recognition |
| US7272604B1 (en) | 1999-09-03 | 2007-09-18 | Atle Hedloy | Method, system and computer readable medium for addressing handling from an operating system |
| NO984066L (en) * | 1998-09-03 | 2000-03-06 | Arendi As | Computer function button |
| US6459779B2 (en) * | 1998-09-04 | 2002-10-01 | Ameritech Corporation | System and method for creating a billing record with a called party's name |
| US7116656B1 (en) * | 1998-10-23 | 2006-10-03 | Verizon Laboratories Inc. | Multi-line appearance telephony via a computer network |
| US6597772B1 (en) | 1998-12-21 | 2003-07-22 | Micron Technology, Inc. | Method of programming telephone numbers and identifiers in multiple databases |
| US7010116B1 (en) * | 1998-12-21 | 2006-03-07 | Micron Technology, Inc. | Method of programming telephone numbers and identifiers in a telephone |
| US6697484B1 (en) * | 1998-12-21 | 2004-02-24 | Micron Technology, Llc | Method of programming telephone numbers and identifiers in a telephone |
| US6625444B1 (en) | 1999-02-02 | 2003-09-23 | Micron Technology, Inc. | Method of programming a telephone |
| US6223165B1 (en) | 1999-03-22 | 2001-04-24 | Keen.Com, Incorporated | Method and apparatus to connect consumer to expert |
| US6449351B1 (en) * | 1999-10-28 | 2002-09-10 | Ameritech Corporation | Method and system of providing caller identification with name |
| FR2803153B1 (en) * | 1999-12-23 | 2002-03-15 | Cit Alcatel | METHOD FOR OBTAINING CALLER IDENTITY IN A TERMINAL OF A TELEPHONE COMMUNICATION NETWORK |
| KR100702772B1 (en) * | 1999-12-30 | 2007-04-03 | 주식회사 케이티 | Method of Calling identity delivery in electronic switching system |
| DE10015774A1 (en) * | 2000-03-30 | 2001-10-04 | Deutsche Telekom Ag | Identifying telecommunications subscriber from other subscribers involves subscriber sending trigger signal to data management unit which passes identification data to other subscriber |
| US7688958B2 (en) * | 2000-03-31 | 2010-03-30 | Callwave, Inc. | Methods and apparatus for providing expanded telecommunications service |
| US6556662B1 (en) * | 2000-05-04 | 2003-04-29 | Worldcom, Inc. | Method and apparatus for providing dialed number verification |
| US7289623B2 (en) | 2001-01-16 | 2007-10-30 | Utbk, Inc. | System and method for an online speaker patch-through |
| US20020133402A1 (en) | 2001-03-13 | 2002-09-19 | Scott Faber | Apparatus and method for recruiting, communicating with, and paying participants of interactive advertising |
| US7012999B2 (en) * | 2001-06-25 | 2006-03-14 | Bellsouth Intellectual Property Corporation | Audio caller identification |
| US7085358B2 (en) | 2001-06-25 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Visual caller identification |
| US7088994B2 (en) * | 2001-07-18 | 2006-08-08 | International Business Machines Corporation | Network address lookup for telephony devices |
| US6904137B2 (en) | 2001-07-31 | 2005-06-07 | Sbc Technology Resources, Inc. | System and method for creating and accessing outgoing telephone call log |
| US7315614B2 (en) | 2001-08-14 | 2008-01-01 | At&T Delaware Intellectual Property, Inc. | Remote notification of communications |
| US6704403B2 (en) | 2001-09-05 | 2004-03-09 | Ingenio, Inc. | Apparatus and method for ensuring a real-time connection between users and selected service provider using voice mail |
| FR2829340B1 (en) * | 2001-09-06 | 2004-10-22 | France Telecom | DEVICE FOR INDICATING CALLS TO ABSENT SUBSCRIBERS |
| US7269249B2 (en) | 2001-09-28 | 2007-09-11 | At&T Bls Intellectual Property, Inc. | Systems and methods for providing user profile information in conjunction with an enhanced caller information system |
| US7079837B1 (en) | 2001-11-06 | 2006-07-18 | Bellsouth Intellectual Property Corporation | Caller identification queue for wireless telephones |
| GB2381992A (en) * | 2001-11-07 | 2003-05-14 | Mitel Knowledge Corp | Subscriber-based calling name database |
| US6721406B1 (en) | 2001-11-28 | 2004-04-13 | Bellsouth Intellectual Property Corporation | Telephone caller location data retrieval |
| US7580850B2 (en) | 2001-12-14 | 2009-08-25 | Utbk, Inc. | Apparatus and method for online advice customer relationship management |
| US7315618B1 (en) | 2001-12-27 | 2008-01-01 | At&T Bls Intellectual Property, Inc. | Voice caller ID |
| US7937439B2 (en) | 2001-12-27 | 2011-05-03 | Utbk, Inc. | Apparatus and method for scheduling live advice communication with a selected service provider |
| US20030161450A1 (en) * | 2002-02-22 | 2003-08-28 | Clapper Edward O. | Providing information to facilitate telephone conversations |
| US6873692B1 (en) * | 2002-03-29 | 2005-03-29 | Bellsouth Intellectual Property Corporation | Telephone synchronization with software applications and documents |
| US6920208B1 (en) * | 2002-05-03 | 2005-07-19 | At&T Corp. | Call tracker |
| US6785368B1 (en) * | 2002-06-24 | 2004-08-31 | Bellsouth Intellectual Property Corporation | On-demand caller identification |
| US6707893B1 (en) | 2002-07-10 | 2004-03-16 | At&T Corp. | Call progress information in cable telephony |
| US7623645B1 (en) | 2002-07-23 | 2009-11-24 | At&T Intellectual Property, I, L.P. | System and method for gathering information related to a geographical location of a caller in a public switched telephone network |
| US7127488B1 (en) | 2002-07-23 | 2006-10-24 | Bellsouth Intellectual Property Corp. | System and method for gathering information related to a geographical location of a caller in an internet-based communication system |
| US7139374B1 (en) | 2002-07-23 | 2006-11-21 | Bellsouth Intellectual Property Corp. | System and method for gathering information related to a geographical location of a callee in a public switched telephone network |
| US6940954B1 (en) * | 2002-09-06 | 2005-09-06 | Cisco Technology, Inc. | Arrangement for retrieving recorded audio announcements from a messaging system for identification of a calling party |
| US7443964B2 (en) | 2003-04-18 | 2008-10-28 | At&T Intellectual Property, I,L.P. | Caller ID messaging |
| US7978833B2 (en) | 2003-04-18 | 2011-07-12 | At&T Intellectual Property I, L.P. | Private caller ID messaging |
| US7698183B2 (en) * | 2003-06-18 | 2010-04-13 | Utbk, Inc. | Method and apparatus for prioritizing a listing of information providers |
| US7886009B2 (en) | 2003-08-22 | 2011-02-08 | Utbk, Inc. | Gate keeper |
| US7120235B2 (en) | 2003-10-06 | 2006-10-10 | Ingenio, Inc. | Method and apparatus to provide pay-per-call performance based advertising |
| US8027878B2 (en) * | 2003-10-06 | 2011-09-27 | Utbk, Inc. | Method and apparatus to compensate demand partners in a pay-per-call performance based advertising system |
| US9984377B2 (en) | 2003-10-06 | 2018-05-29 | Yellowpages.Com Llc | System and method for providing advertisement |
| US8121898B2 (en) | 2003-10-06 | 2012-02-21 | Utbk, Inc. | Methods and apparatuses for geographic area selections in pay-per-call advertisement |
| US7428497B2 (en) | 2003-10-06 | 2008-09-23 | Utbk, Inc. | Methods and apparatuses for pay-per-call advertising in mobile/wireless applications |
| US7366683B2 (en) | 2003-10-06 | 2008-04-29 | Utbk, Inc. | Methods and apparatuses for offline selection of pay-per-call advertisers |
| US8024224B2 (en) | 2004-03-10 | 2011-09-20 | Utbk, Inc. | Method and apparatus to provide pay-per-call advertising and billing |
| US7424442B2 (en) * | 2004-05-04 | 2008-09-09 | Utbk, Inc. | Method and apparatus to allocate and recycle telephone numbers in a call-tracking system |
| US7623849B2 (en) | 2003-11-13 | 2009-11-24 | At&T Intellectual Property, I, L.P. | Method, system, and storage medium for providing comprehensive originator identification services |
| US7672444B2 (en) * | 2003-12-24 | 2010-03-02 | At&T Intellectual Property, I, L.P. | Client survey systems and methods using caller identification information |
| US6970546B2 (en) * | 2004-01-12 | 2005-11-29 | Bellsouth Intellecutal Property Corp. | Intelligent remote caller ID |
| GB2425375A (en) * | 2004-05-04 | 2006-10-25 | Utbk Inc | A method and apparatus to dynamically allocate and recycle telephone numbers in a call-tracking system |
| US20050249344A1 (en) * | 2004-05-07 | 2005-11-10 | Sbc Knowledge Ventures, L.P. | Network delivery of personalized caller identification |
| US7643627B2 (en) * | 2004-07-09 | 2010-01-05 | At&T Intellectual Property, I,L.P. | Methods, systems and storage mediums for providing a self-provisioning telephony service |
| US8195136B2 (en) | 2004-07-15 | 2012-06-05 | At&T Intellectual Property I, L.P. | Methods of providing caller identification information and related registries and radiotelephone networks |
| US9202219B2 (en) | 2005-02-16 | 2015-12-01 | Yellowpages.Com Llc | System and method to merge pay-for-performance advertising models |
| US8538768B2 (en) | 2005-02-16 | 2013-09-17 | Ingenio Llc | Methods and apparatuses for delivery of advice to mobile/wireless devices |
| US7979308B2 (en) | 2005-03-03 | 2011-07-12 | Utbk, Inc. | Methods and apparatuses for sorting lists for presentation |
| US8369311B1 (en) | 2005-07-01 | 2013-02-05 | Callwave Communications, Llc | Methods and systems for providing telephony services to fixed and mobile telephonic devices |
| US8599832B2 (en) | 2005-09-28 | 2013-12-03 | Ingenio Llc | Methods and apparatuses to connect people for real time communications via voice over internet protocol (VOIP) |
| US8761154B2 (en) | 2005-09-28 | 2014-06-24 | Ebbe Altberg | Methods and apparatuses to access advertisements through voice over internet protocol (VoIP) applications |
| US8125931B2 (en) | 2006-01-10 | 2012-02-28 | Utbk, Inc. | Systems and methods to provide availability indication |
| US7720091B2 (en) | 2006-01-10 | 2010-05-18 | Utbk, Inc. | Systems and methods to arrange call back |
| US9197479B2 (en) | 2006-01-10 | 2015-11-24 | Yellowpages.Com Llc | Systems and methods to manage a queue of people requesting real time communication connections |
| US8270582B1 (en) | 2006-04-05 | 2012-09-18 | Callwave, Inc. | Methods and systems for routing calls |
| US9317855B2 (en) | 2006-10-24 | 2016-04-19 | Yellowpages.Com Llc | Systems and methods to provide voice connections via local telephone numbers |
| US8451825B2 (en) | 2007-02-22 | 2013-05-28 | Utbk, Llc | Systems and methods to confirm initiation of a callback |
| US10958781B2 (en) | 2007-06-13 | 2021-03-23 | First Orion Corp. | Providing audio content to a device |
| US8548140B2 (en) | 2007-06-13 | 2013-10-01 | I D You, Llc | Providing audio announcement to called parties |
| US8811575B2 (en) * | 2007-06-13 | 2014-08-19 | I D You, Llc | Delivering additional information to receiving parties for text messaging based caller ID |
| US8625762B1 (en) | 2007-06-13 | 2014-01-07 | Accudata Technologies, Inc. | Providing additional information to called parties |
| US8488754B1 (en) | 2007-10-17 | 2013-07-16 | Accudata Technologies, Inc. | IP-enabled information delivery |
| US9277019B2 (en) | 2007-06-18 | 2016-03-01 | Yellowpages.Com Llc | Systems and methods to provide communication references to connect people for real time communications |
| US8160226B2 (en) | 2007-08-22 | 2012-04-17 | At&T Intellectual Property I, L.P. | Key word programmable caller ID |
| US8243909B2 (en) | 2007-08-22 | 2012-08-14 | At&T Intellectual Property I, L.P. | Programmable caller ID |
| US11811966B2 (en) | 2007-10-17 | 2023-11-07 | First Orion Corp. | IP-enabled information delivery |
| US20090202048A1 (en) * | 2008-02-12 | 2009-08-13 | Chazon Stein | System and Method for Communication |
| JP5410720B2 (en) * | 2008-09-25 | 2014-02-05 | 日立コンシューマエレクトロニクス株式会社 | Digital information signal transmitting / receiving apparatus and digital information signal transmitting / receiving method |
| US9191498B2 (en) * | 2010-04-29 | 2015-11-17 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for handling anonymous calls |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5526406A (en) * | 1992-01-29 | 1996-06-11 | Luneau; David J. | Calling party announcement apparatus |
| WO1994006236A2 (en) * | 1992-08-26 | 1994-03-17 | Bellsouth Corporation | Personal number communications system |
| JPH0795279A (en) * | 1993-09-20 | 1995-04-07 | Fujitsu Ltd | Memory dialing control system |
| US5481603A (en) * | 1993-09-28 | 1996-01-02 | At&T Corp. | Intelligent call processing based upon complete identification of calling station |
| WO1995015051A1 (en) * | 1993-11-29 | 1995-06-01 | Greater Harris County 9-1-1 Emergency Network | Integrated data collection and transmission for emergency calls |
| US5568546A (en) * | 1994-10-31 | 1996-10-22 | Lucent Technologies, Inc. | Method and apparatus for dynamic abbreviated dialing assignment |
| US5754636A (en) * | 1994-11-01 | 1998-05-19 | Answersoft, Inc. | Computer telephone system |
| US5748724A (en) * | 1995-06-30 | 1998-05-05 | Siemens Stomberg-Carlson | Method for transferring a subscriber to a new local service provider |
| US5734706A (en) * | 1995-07-27 | 1998-03-31 | Windsor; Victoria Brein | Caller identification and data retrieval system |
-
1997
- 1997-04-25 US US08/846,076 patent/US5940484A/en not_active Expired - Lifetime
-
1998
- 1998-03-17 CA CA002232319A patent/CA2232319C/en not_active Expired - Fee Related
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9143612B2 (en) | 2012-11-02 | 2015-09-22 | Ian James Roncoroni | Centralized caller profile system and methods for routing and prioritizing calls |
Also Published As
| Publication number | Publication date |
|---|---|
| US5940484A (en) | 1999-08-17 |
| CA2232319A1 (en) | 1998-10-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2232319C (en) | A self-provisioning names database for caller identification services | |
| US5903636A (en) | System and method for providing caller identification in conjunction with calling card calls | |
| US5425084A (en) | Computer-controlled telecommunications system | |
| US5832072A (en) | Communication network with hidden calling number capability | |
| US7020250B2 (en) | System and method for providing visual indication of caller and telephony platform information on customer premises equipment | |
| US5509062A (en) | Intelligent terminal based selective call forwarding | |
| JP2705864B2 (en) | Call connection method | |
| CA2258616C (en) | Telephone polling method | |
| US6085101A (en) | Communications network having a multicast capability | |
| US5764741A (en) | Least cost rooting system | |
| US6097801A (en) | Number portability using enhanced routing table | |
| JP2889053B2 (en) | Method and switch for establishing telephone call connection | |
| EP0756428B1 (en) | Database queries in a telecommunications network | |
| US5852657A (en) | Method for visual delivery to a caller of selected information associated with a telephone number in an advanced intelligent network via public switch telephone network | |
| WO1994013109A9 (en) | Computer-controlled telecommunications system | |
| US20070072596A1 (en) | Caller identification queue for wireless telephones | |
| US7499536B2 (en) | Apparatus and method for intelligent call routing and call return | |
| US20020126814A1 (en) | Apparatus, method and computer program product for automatic directory entry generation via caller-id | |
| WO1997033441A1 (en) | Providing number portability by means of enhanced routing tables | |
| US9247045B2 (en) | Operating a directory assistance call center based upon directory assistance database and caller ID data | |
| US7020267B2 (en) | Geographical number portability | |
| US7170984B2 (en) | Method for advanced determination and display of caller geographic information in a PBX | |
| US6343073B1 (en) | Method and system for efficient link utlization | |
| US20070105537A1 (en) | Network support for remote caller ID information | |
| US20070047717A1 (en) | Telephone record search system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |