|Publication number||US6724866 B2|
|Application number||US 10/072,387|
|Publication date||Apr 20, 2004|
|Filing date||Feb 8, 2002|
|Priority date||Feb 8, 2002|
|Also published as||US20030152199|
|Publication number||072387, 10072387, US 6724866 B2, US 6724866B2, US-B2-6724866, US6724866 B2, US6724866B2|
|Inventors||Roland Kuhn, Matteo Contolini, Robert C. Boman|
|Original Assignee||Matsushita Electric Industrial Co., Ltd.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (5), Referenced by (31), Classifications (14), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates generally to telephone call screening. More particularly, the invention relates to a call screening system and method that uses speaker verification and/or speech recognition to ascertain the identity of a caller and thereafter handle the incoming call in a predetermined way based on the system user's desires or usage profile.
Many people use caller ID to screen incoming calls. That is, they look at a screen display giving the identity of the caller—if the caller's number is not blocked—before deciding whether to pick up the telephone or not. However, a high proportion of telephone numbers in North America is blocked, and in any case, a familiar caller may be calling from an unfamiliar number. In such case the familiar caller might be inadvertently rejected by the user.
There have been a number of proposed solutions to the problem, however each has proven deficient in certain important respects. One existing system is provided as a call screening service, typically a service that the user subscribes to at additional cost, in conjunction with the caller ID service. With this screening service, if the caller's number is blocked, the system intercepts the call prior to ringing the user's telephone. The caller is then prompted to state his or her name, or company affiliation, which are recorded as audio information, whereupon the call is then allowed to ring through to the user regardless of what the caller says. When the user answers the incoming call, rather than being immediately connected to the caller, the user is placed in communication with the call screening server. The server replays a prerecorded announcement that the incoming call was intercepted and then replays how the caller responded to the prompt for the caller's name or company affiliation. The user then has the option to either (1) accept the incoming call, (2) reject the incoming call with a message to the caller that the call is refused or (3) reject the call with a message to the caller asking that the user be placed on the caller's “do not call” list.
While the aforementioned call screening system does give the user a means to avoid talking to unwanted callers, it still requires the user to pick up the telephone, listen to the call screening server's message containing the incoming caller's name or company affiliation and select one of the three call handling options. Thus, while this call screening system can eliminate the need to talk to unwanted callers, it does not insulate the user from having a tranquil evening spoiled by numerous calls by telemarketers. Although the user can select the parties with whom to speak, the telephone still rings.
Another proposed solution is the telemarketing call “zapper” that screens out calls that are placed using predictive dialer computers. Some telemarketers will use predictive dialer computers to rapidly place calls, allowing them to spend time only on those calls where the party actually answers. The zapper emits a special tone that fools the dialing computer into thinking that the called number is disconnected or no longer in service. When the computer hears this tone it hangs up before the telemarketer is able to connect with the called party's phone and the computer deletes the called party's phone number from its database. In theory, over time, as the zapper-protected number is removed from more and more databases, the user experiences fewer and fewer telemarketing calls.
While interesting in theory, unfortunately, the zapper does not fully solve the call screening problem, because calls that are placed without use of predictive dialing computers or auto-dialer systems are not intercepted by the zapper.
The present invention affords considerable more functionality than either of the aforementioned call screening solutions. The present invention uses speaker verification and speaker recognition technology to construct an acceptable caller list, which is then used to screen incoming callers. In the presently preferred embodiment, when the user first signs up for the screening service based on the invention (or purchases a physical device in which the invention is incorporated), the system begins constructing speaker voice models for each of the people with whom the user carries out conversations of reasonable length. After each telephone call, the system will ask the user whether or not to enter the other person's voice profile and telephone number (if unblocked) in the acceptable caller list. It may also prompt the user for the other person's name.
Subsequently, if a person on the acceptable caller list calls the user back from the same unblocked number, the call will be put through immediately (as in the existing technology). On the other hand, if an acceptable caller calls from a blocked number or from a new number, the system will ask the caller for his or her name, and/or for other information. If the voice profile (possibly together with the name) matches the profile for someone on the acceptable caller list, the call will be put through; otherwise a message may be taken by routing the call to a suitable answering machine or voicemail system.
The invention can be implemented as either a server-based system or as a locally deployed hardware or software system associated with the user's telephone equipment. The invention is also capable of being extended to more complex versions of the basic idea, in which there are several classes of callers and different actions to be taken for each. For instance, some callers might be subjected to a detailed series of questions by the system, with the resulting action determined by their recognized response. Also, the system can be configured to take other action based on who the caller is, or what the caller says. For example, the system can be configured so that the telephone system interface selectively communicates a message over a computer network, such as the internet.
As will be more fully explained herein, the invention offers a number of advantages over prior call screening systems. Calls from telemarketers and other unwelcome callers may be handled automatically by the system, based on rules established by the user. The invention allows the recipient of telephone calls to determine exactly how each class of call is to be handled, depending on the identity of the caller. Compared with existing systems, the invention has the advantage that calls from unwelcome people (e.g., telemarketers) do not consume any of the recipient's time. For familiar, welcome callers using a blocked or unfamiliar number, the system imposes only a very slight delay (the time required for them to identify themselves to the system), rather than the longer delay imposed by other conventional systems which play back the response to the user. In effect, the invention gives users the capability to “hire” an automatic secretary who will screen their calls and respond to them appropriately.
In accordance with one aspect of the invention, the call screener employs a telephone system interface having at least one port for connection to a telephone network, and at least one port for connection to the telephone device of a user. The interface is operable to selectively route calls (and refrain from routing calls) originating from the telephone network to the telephone device, or to another device, such as an answering machine or voice mail system. A dialogue system coupled to the telephone system interface elicits speech from an incoming caller and causes the telephone system interface to route calls from the incoming caller based on a comparison of the elicited speech with a set of stored speaker models.
The stored speaker models may be maintained automatically by the system, using either a passive mode, in which calls exceeding a predetermined duration are assumed to be “acceptable” callers; and a proactive mode in which the system prompts the user at the end of the call to elect whether to save the speech models developed during that call in the acceptable user database. If desired, the user can attach other attributes or special tags to the stored models, indicating special handling or call routing rules to be applied when that caller calls again.
For a more complete understanding of the invention, its objects and advantages, refer to the remaining specification and to the accompanying drawings.
Further areas of applicability of the present invention will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.
The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:
FIG. 1 is a block diagram of a presently preferred embodiment of the invention;
FIG. 2 is a flowchart diagram illustrating how the acceptable caller database is maintained in the presently preferred embodiment.
The following description of the preferred embodiment(s) is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.
A presently preferred embodiment of the invention will now be described in an exemplary application in which the user has a telephone 10 and a voicemail system or answering machine 12. In the illustrated embodiment the telephone 10 and voicemail system 12 may be connected to the same telephone line or extension, or they may be connected to different telephone lines or extensions. Instead of being coupled to the public switched telephone network (PSTN) 14 by direct connection, the telephone 10 and voicemail system 12 are coupled to the call routing and screening interface module 16. This module is in turn connected to the public switched telephone network 14. Thus incoming calls are intercepted by the call routing and screener interface and then passed on to the telephone 10 or voicemail system 12 based on the outcome of the call screening features of the invention.
The preferred embodiment employs a speech recognizer 18 with an associated set of speech recognition models 20, and a speaker verification system 22 with an associated set of speaker models 24. In FIG. 1 these recognizer and verification modules are illustrated as being bundled or packaged within a voice processing module 26. Preferably, the recognizer 18 and speaker verification module 22 are designed to work cooperatively. Each is able to use the services of the other, as needed to perform the respective recognition and verification functions involved in the call screening and routing process. The voice processing module is designed to receive speech data input from both the user's telephone, as on line 28 and from the call routing and screening interface 16 as on line 30. This speech data may be analog audio data, or it may be digital data. In the latter case, the digital data may be generated by the telephone 10 and by the call routing and screening interface 16. The speech data supplied to the voice processing module 26 is thus made available to both recognizer 18 and speaker verification module 22.
The voice processing module 26 is also coupled to a database system through database interface 32. The database interface 32 provides access to the acceptable caller database 34. As illustrated, the acceptable caller database maintains records, as illustrated by exemplary record 36, in which pertinent acceptable caller information is maintained. For example, the database may contain records of caller's name, caller ID, a speaker model (key linking that record with one of the speaker models 24) and an acceptability rating. The acceptability rating may be used to signify, for example, that a call from a particular caller will always be allowed to ring through, or will conditionally be allowed to ring through or will receive other handling.
The results of speech recognition (performed by recognizer 18) and/or speaker verification (performed by speaker verification module 22) serve as commands that are processed by the database interface 32. By way of illustration, if the speaker verification module 22, through access to its speaker models 24, ascertains that an incoming caller matches a speaker it has record of, a query is issued via database interface 32 to retrieve the corresponding record for that speaker using the speaker model key.
In this case, perhaps the incoming caller has been previously set up by the user as an acceptable caller who will be permitted to ring through only from 10 a.m. until 12 noon. The acceptable caller database would contain such information in the acceptability rating associated with that speaker. The system would then determine, based on time of day information maintained by the system processor, whether the incoming call should be allowed to ring through, or not.
A multipurpose dialogue system 40 connects the database interface 32 with the call routing and screening interface 16. The database interface 32 examines the acceptable caller record associated with the incoming caller, extracts the acceptability rating information and provides it to the dialogue system 40 for action. In the previous example, if the hour of the day falls between 10 a.m. and 12 noon, the dialogue system would send a switching command on line 42 to the call routing and screening interface 16. Interface 16 would, in turn, allow the incoming call from PSTN 14 to be connected to the telephone 10. If the hour of day was not within the accepted range, the call routing and screening interface 16 would block the call (or route it to the voicemail system 12 if that was the user's preprogrammed instruction).
In some applications, a user may wish to permit a caller of unknown identity to ring through, if that caller is able to supply certain prearranged or preassigned information. For example, if the user is expecting to receive a call from a rare coin vendor, in response to a previous inquiry, the user can generate a user defined record in the acceptable caller database to accommodate this. Specifically, the user would create an entry such that any caller who mentions the word “coin” or “coins” in response to a prompt would be permitted to ring through. The multipurpose dialogue system 40 is programmed to the user to ask the incoming caller to state the caller's name and purpose of the call. If the system is programmed by the user to expect certain preprogrammed message responses (such as the word coin or coins) the dialogue system 40 instructs the database interface 32 to obtain and process information from recognizer 18. Thus, if the incoming caller mentions coin or coins in response to the prompt, recognizer 18 will identify these words and make that fact known to database interface 32. This, in turn, allows the database interface to retrieve the acceptable caller record associated with those keywords.
The multipurpose dialogue system can also be used to provide dialogue services for the user. The user would typically operate the system using the telephone 10. The user would supply commands by either keypad data entry over line 44 or by using speech that would be supplied via the handset as illustrated by line 28. Keypad data on line 44 may be supplied directly to database interface 32. The dialogue system 40 provides prompts to the user on line 48.
The presently preferred system automatically builds and maintains speaker models to be used by the speaker verification module 22. These are generated by the voice processing module 26 and stored in the acceptable caller database using the procedure illustrated in FIG. 2. Two presently preferred embodiments are illustrated for constructing the speaker models. Both construct the models automatically as the user and incoming caller converse. One embodiment implements a “Passive” mode, in which the models are automatically stored for all calls of a predetermined duration. The other embodiment implements a “Proactive” mode in which the user is prompted to make the decision whether (and how) a speaker model will be stored at the end of the call.
Referring to FIG. 2, both procedures begin at step 50, by parsing the input speech using a suitable turn-taking algorithm to separate the speech of the user (system owner) from that of the incoming caller. The speech of the user and incoming caller are separated at this stage, so that the system can begin to construct a speaker model for the incoming caller. If desired, the system can also construct a speaker model for the user (system owner), as well. Having such model would allow the user to call his or her own system from another telephone, to leave a voice mail message for a spouse, for example.
After separating the incoming caller's speech from that of the user, the system begins building a speaker model for the incoming caller at step 52. While there are many suitable ways to construct speaker models for speaker verification, one way is to construct an eigenvoice representation of the speaker by capturing speech recognition parameters and then performing dimensionality reduction. Another way to construct speaker models is to use Gaussian mixture models. For more information on the eigenvoice technique, see U.S. Pat. No. 6,141,644, to Kuhn et. al., entitled, “Method for Speaker Verification and Speaker Identification Based on Eigenvoices.”
While either a passive mode implementation or a proactive mode implementation can be separately constructed, the flowchart of FIG. 2 illustrates how to implement both, giving the user a choice of which mode to use. Thus the mode of operation is determined at step 54. The left-branch describes the Passive mode and the right-branch describes the Proactive mode.
Taking the Passive mode first, the procedure maintains a call duration timer that is tested at step 56. If the predetermined time (e.g., N seconds) has elapsed, the system presumes that the incoming caller is one with whom the user will wish to speak to again. If the user terminates the call in less than the predetermined time, then the system presumes that the incoming caller is not to be deemed an “acceptable” caller in future calls. Thus the system discards the speaker model at step 58 if the predetermined time is not met; otherwise the system stores the speaker model at step 60 into the acceptable caller database 34. Of course, if desired, the system could also maintain an “unacceptable caller” database as well. If such is constructed, it would be stored at step 58. If desired, such unacceptable caller database could be implemented as part of database 34, with appropriate attribute set to indicate unacceptability.
Turning now to the Proactive mode (right-branch), the procedure waits until call termination (hang up) occurs at step 62. The system then prompts the user at step 64 for a storage decision. The user's decision may be indicated through keypad entry (via line 44, FIG. 1) or by voice, using the services of the speech recognizer 18 (FIG. 1) to decode the user's instructions. The user's filing instructions are then parsed at step 66 and the appropriate storage action is taken. As illustrated, the user may elect not to store the speech model of the last caller, in which case the system discards the model at 68. The user may elect to store the model, in which case the model may be stored as at 70 without special instruction, or with associated special handling or routing attribute or tag as at 72. The special handling tag would be set, for example, if the user wishes to limit the time to receive a call from this caller to certain hours of the day, or if the user wishes to have the dialog system 40 issue that caller with a particular prompt or message the next time he or she calls.
From the foregoing, it will be seen that the present system gives a great deal of flexibility in deciding who the user wishes to talk to and how all incoming calls should be handled. The description of the invention is merely exemplary in nature and, thus, variations that do not depart from the gist of the invention are intended to be within the scope of the invention. Such variations are not to be regarded as a departure from the spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5724408 *||Apr 12, 1994||Mar 3, 1998||Syntellect Technology Corp.||Automated call screening|
|US6321197 *||Jan 22, 1999||Nov 20, 2001||Motorola, Inc.||Communication device and method for endpointing speech utterances|
|US6327343 *||Jan 16, 1998||Dec 4, 2001||International Business Machines Corporation||System and methods for automatic call and data transfer processing|
|US6349290 *||Jun 30, 1999||Feb 19, 2002||Citibank, N.A.||Automated system and method for customized and personalized presentation of products and services of a financial institution|
|US6404859 *||May 6, 1999||Jun 11, 2002||Lockheed Martin Corporation||Voice enabled system for remote access of information|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6917672||Feb 21, 2002||Jul 12, 2005||International Business Machines Corporation||Third party regulation of calls based on the caller and callee pair to a call|
|US6959081||Dec 3, 2001||Oct 25, 2005||International Business Machines Corporation||Expert hold queue management|
|US7076041 *||Feb 21, 2002||Jul 11, 2006||International Business Machines||Third party regulation of calls through a particular line based on a call context|
|US7092508||Feb 21, 2002||Aug 15, 2006||International Business Machines Corporation||Rating parties according to party identities|
|US7095835||Feb 26, 2002||Aug 22, 2006||International Business Machines Corporation||Time based regulation of use of a telephone line|
|US7095842||Dec 3, 2001||Aug 22, 2006||International Business Machines Corporation||Enabling caller controlled hold queue position adjustment|
|US7116769 *||Feb 25, 2003||Oct 3, 2006||Sanyo Electric Co., Ltd.||Telephone having phone number registration function, phone number registration method, and call register display method|
|US7200215||Feb 21, 2002||Apr 3, 2007||International Business Machines Corporation||Time based regulation of access to callees|
|US8270588 *||Jan 5, 2007||Sep 18, 2012||Ronald Schwartz||Method and system for incoming call management|
|US8655662 *||Nov 29, 2012||Feb 18, 2014||At&T Intellectual Property I, L.P.||System and method for answering a communication notification|
|US8781825||Aug 24, 2011||Jul 15, 2014||Sensory, Incorporated||Reducing false positives in speech recognition systems|
|US8805347||Jun 28, 2011||Aug 12, 2014||Motorola Mobility Llc||Caller identification for missed calls|
|US8892442||Feb 17, 2014||Nov 18, 2014||At&T Intellectual Property I, L.P.||System and method for answering a communication notification|
|US9191500||Aug 8, 2014||Nov 17, 2015||Google Technology Holdings LLC||Caller identification for missed calls|
|US9319504||Nov 12, 2014||Apr 19, 2016||At&T Intellectual Property I, Lp||System and method for answering a communication notification|
|US9525767 *||Mar 2, 2016||Dec 20, 2016||At&T Intellectual Property I, L.P.||System and method for answering a communication notification|
|US20020052226 *||Oct 30, 2001||May 2, 2002||Pioneer Corporation||Portable information terminal device|
|US20030103618 *||Dec 3, 2001||Jun 5, 2003||International Business Machines Corporation||Voice browsing while waiting in a hold queue|
|US20030103619 *||Dec 3, 2001||Jun 5, 2003||Ibm Corporation||Enabling caller controlled hold queue position adjustment|
|US20030103621 *||Dec 3, 2001||Jun 5, 2003||International Business Machines Corporation||Expert hold queue management|
|US20030156696 *||Feb 21, 2002||Aug 21, 2003||International Business Machines Corporation||Third party regulation of calls through a particular line based on a call context|
|US20030156700 *||Feb 21, 2002||Aug 21, 2003||International Business Machines Corporation||Time based regulation of access to callees|
|US20030156707 *||Feb 21, 2002||Aug 21, 2003||International Business Machines Corporation||Rating parties according to party identities|
|US20030161456 *||Feb 26, 2002||Aug 28, 2003||International Business Machines Corporation||Time based regulation of use of a telephone line|
|US20030220099 *||Feb 25, 2003||Nov 27, 2003||Mitsuji Hama||Telephone having phone number registration function, phone number registration method, and call register display method|
|US20060140357 *||Dec 27, 2004||Jun 29, 2006||International Business Machines Corporation||Graphical tool for creating a call routing application|
|US20080084975 *||Jan 5, 2007||Apr 10, 2008||Ronald Schwartz||Method and System for Incoming Call Management|
|US20090103696 *||Oct 19, 2007||Apr 23, 2009||Davison Scott F||Telephone System|
|US20130090100 *||Nov 29, 2012||Apr 11, 2013||At&T Intellectual Property I, L.P.||System and Method for Answering a Communication Notification|
|US20160182700 *||Mar 2, 2016||Jun 23, 2016||At&T Intellectual Property I, Lp||System and method for answering a communication notification|
|WO2013028518A1 *||Aug 17, 2012||Feb 28, 2013||Sensory, Incorporated||Reducing false positives in speech recognition systems|
|U.S. Classification||379/88.21, 704/231, 379/142.01, 704/244|
|International Classification||H04M1/57, H04M1/663, H04M1/27, H04M3/436|
|Cooperative Classification||H04M1/57, H04M1/271, H04M1/663, H04M3/436|
|European Classification||H04M1/663, H04M3/436|
|Feb 8, 2002||AS||Assignment|
Owner name: MATSUSHITA ELECTRIC INDUSTRIAL CO., LTD., JAPAN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KUHN, ROLAND;BORMAN, ROBERT C.;CONTLINI, MATTEO;REEL/FRAME:012587/0789
Effective date: 20020205
|Jun 3, 2002||AS||Assignment|
Owner name: MATSUSHITA ELECTRIC INDUSTRIAL CO., LTD., JAPAN
Free format text: SUBMISSIO;ASSIGNORS:KUHN, ROLAND;CONTOLINI, MATTEO;BOMAN, ROBET C.;REEL/FRAME:012948/0848
Effective date: 20020205
|Oct 26, 2004||CC||Certificate of correction|
|Oct 29, 2007||REMI||Maintenance fee reminder mailed|
|Apr 20, 2008||LAPS||Lapse for failure to pay maintenance fees|
|Jun 10, 2008||FP||Expired due to failure to pay maintenance fee|
Effective date: 20080420