System and method for voice recognition password reset

BACKGROUND OF THE INVENTION

00011. Technical Field

0002The present invention relates in general to a method and system for improving password or PIN resets and providing new passwords or PINs to users.

00032. Description of the Related Art

0004Help desks play a vital and important role in today's computer-based organization. Help desk personnel are often the first line of defense for answering user' questions and handling problems that users face. The help desk often aids users having difficulty with common applications, especially customized or internally developed applications that have been tailored to the organization. In addition, help desks perform other tasks such as resetting user passwords when a user forgets or otherwise loses his or her password.

0005Many organizations and employers utilize passwords. A user may be prompted to enter a password for a variety of reasons. Some organizations require users to enter a password for security reasons; however, organizations may require users to enter a password to verify their age or some other requirement. If the user enters their password correctly, they are allowed access to their account or other information. However, if the user enters an incorrect password, access to the account is not permitted. At this point, the user may be able to use the organization's web page to find a hint or remember for their password. If the password is entered incorrectly, the user is not permitted to access the site. Sometimes passwords are used to verify the identity of the user and may also be used to access certain files.

0006As much as half of the calls received by a help desk are requests for password reset. Often, these passwords can be reset using the help desk web pages; however, this may or may not require the password that needs to be reset. More often, this reset must be done by telephone. This task often requires a significant amount of time and resources by the help desk. This drain upon help desk resources often prevents help desk personnel from performing other needed functions for the organization.

0007Help desks often ascertain the identify of the caller requesting a password reset by asking for information that is likely known only by the user. For example, the help desk employee may ask the caller for the caller's mother's maiden name, employee number, or social security number. One challenge facing organizations and help desks, therefore, is that the information requested from the caller is often not secure. An imposter may obtain a user's mother's maiden name or other information that is used to verify a user's identity. Once the information has been obtained, the imposter can pose as the user and receive a new password for the user's account presenting further security issues for the organization.

0008In answer to these security issues, passwords are often not given to the caller over the telephone. Instead, they are sent using another means so that the actual user may intercept the new password before the imposter gains access to the system. For example, the password may be sent to the user's manager's email account, or if the user can receive email without the new password, to the user's own email account. However, this presents further challenges in that a genuine user (i.e., not an imposter), has to perform additional steps in order to obtain his password. These steps are often difficult if the user is traveling, especially when out of the country. Receiving the reset password from the manager may take additional time if the manager is away or unavailable. Human help desks performing password resets cause organizations to employ individuals dedicated to this function, which cause greater expenses, and consequently reduces the organizations' profits. What is needed, therefore, is a system and method of providing a password reset without the use of human intervention. What is further needed is a way to provide a new password without introducing a delay between resetting the password and the user actually receiving the new password. Finally, what is needed is a technique to deliver the new password to the user in a way that further enhances the security of the system.

SUMMARY

0009It has been discovered that a password can be reset and a new password can be provided using voice recognition technology. The user calls the help desk using an ordinary telephone to reach the automated password function. The voice recognition program is programmed to ask the person on the phone to identify himself by name or a user identifier and to repeat a series of random words in order to authenticate the caller. The caller repeats the words that are used for identification by simply speaking into the telephone. The use of random words, rather than a script, prevents a caller's voice from being recorded and used later to reset the password by an imposter.

0010Once the user has been authenticated, the automated password reset program resets the password and delivers a new password to the user in a way that further enhances the overall security of the system. One option allows the automated password reset system to call the caller back at a predetermined phone number with the new password. This would prevent someone else from intercepting the new password. Another option allows the system to deliver the new password directly to the voice mailbox of the user. This option would allow the user access to the new password regardless of time of day or location of the user. The automated password reset system could also deliver the password to a predetermined e-mail account accessible by the user or someone that the user trusts. This e-mail could be delivered directly to the user's account or could be delivered to a manager or other administrator. The new password could also be mailed to the user through traditional postal mail. Finally, the password could simply be provided to the user over the telephone after the system verified the caller's identity. This option provides a aster response to the user and, because the users identify is verified using voice recognition, reduces the possibility of providing the new password to an imposter in particular since the password is then not exposed to any other system thus reducing the chances of it being intercepted and stolen.

0011Another scenario is the user is at a kiosk or ATM machine, has forgotten their PIN, and uses the voice recognition program to permit the PIN to be reset. The voice recognition program permits the user to enter the new PIN, informs the owner via e-mail, post, etc. of the fact that the PIN was reset.

0012The foregoing is a summary and thus contains, by necessity, simplifications, generalizations, and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the present invention, as defined solely by the claims, will become apparent in the non-limiting detailed description set forth below.

BRIEF DESCRIPTION OF THE DRAWINGS

0013The present invention may be better understood, and its numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference symbols in different drawings indicates similar or identical items.

0014<figref idref="DRAWINGS">FIG. 1</figref> is a system diagram showing components involved when requesting a password reset;

0015<figref idref="DRAWINGS">FIG. 2</figref> is a high level flowchart showing the use of voice signatures to reset and deliver a new password to a user;

0016<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart showing authentication of a user's voice and providing the user a new password;

0017<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart showing the steps involved with providing the user with a new password;

0018<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart showing the steps involved with recording the user's voice signature; and

0019<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram of an information handling system capable of implementing the present invention.

DETAILED DESCRIPTION

0020The following is intended to provide a detailed description of an example of the invention and should not be taken to be limiting of the invention itself. Rather, any number of variations may fall within the scope of the invention that is defined in the claims following the description.

0021<figref idref="DRAWINGS">FIG. 1</figref> is a system diagram showing components involved when requesting a password reset. ATM machines and kiosks that access secured network sites often require a user identifier and a password, or PIN number. As used herein, the term “password” includes PIN numbers and any other access code used to gain access to a computer system. In ATM machines, and some kiosks, the user identifier is supplied by the user by using an access card, similar in shape and size as a credit card, that contains user identification material. The user is required to enter a password. Telephones may be located at or near ATM and kiosks to allow customers to readily retrieve or reset passwords when they forget or lose the password. In addition, password resets may be desired by a customer if he believes that his password has become compromised. In other situations, the user may be at his home, office, or even using a mobile telephone when he realizes that he has lost or forgotten a password needed to access a particular account.

0022Caller <b>100</b> dials a phone number corresponding with organization's help desk and is prompted with several menu options. The caller indicates the option for password reset request <b>105</b> by pressing a predetermined number on the telephone keypad or indicating the selection verbally. Password reset request <b>105</b> is transmitted through telephone network <b>110</b> and received as password reset request <b>120</b> by help desk server <b>130</b>.

0023Help desk server <b>130</b> likely contains many functions for assisting users, one of which is the password reset function. Help desk server <b>130</b> initiates verify caller routine <b>140</b> in response to the caller's request to reset his password. Verify caller routine <b>140</b> reads words from word data store <b>160</b>. Word data store contains a list of words that the user previously recited when the user's original voice signature was recorded (see <figref idref="DRAWINGS">FIG. 5</figref> for details concerning capturing the user's original voice signature). A random word is selected from word data store <b>160</b> and transmitted to caller <b>100</b> as word request <b>145</b>. Word request <b>145</b> is transmitted through telephone network <b>110</b> and received as word request <b>146</b> by caller <b>100</b>. In response, caller <b>100</b> repeats the word into the handset of his telephone (caller response <b>149</b>). Caller response <b>149</b> is transmitted through telephone network <b>110</b> and received by verify caller function <b>140</b> as caller response <b>150</b>. This process of sending word request <b>145</b> and receiving caller response <b>150</b> is repeated until verify user function <b>140</b> can determine whether the caller's voice matches the voice signature of the user stored in voice signatures <b>170</b>. If verify user function <b>140</b> determines that the caller's voice does not match the user's stored voice signature, data is provided to fraud detection subsystem <b>175</b> which gathers data concerning possible fraudulent attempts to reset passwords. Fraud detection subsystem <b>175</b> may also alert the user and the user's management that someone attempted to reset the user's password. Caller identification (i.e., Caller ID) information may also be gathered about caller <b>100</b> to ascertain the identity of the caller, especially if multiple attempts are made by caller <b>100</b> to reset passwords maintained by the system.

0024On the other hand, if verify user function <b>140</b> determines that the caller's voice matches the user's voice signature stored in voice signatures <b>170</b>, then reset password function <b>180</b> is initiated to reset the user's password. In some systems, the password may not be changed and reset password function <b>180</b> simply reads the user's current password from passwords data store <b>185</b> and provides password <b>195</b> to caller <b>100</b>. In other systems, the user's password may be reset (i.e., a new password is established for the user's system identifier) and this modified password <b>195</b> is provided to caller <b>100</b>. In either case, the password reset action is logged in audit trail database <b>190</b> including information such as the caller's caller id, a timestamp, and perhaps the recorded conversation. Password <b>100</b> may be provided to caller <b>100</b> in a variety of ways, such as reading the password to the user over the telephone (see <figref idref="DRAWINGS">FIG. 4</figref> for detailed options regarding password delivery). After successfully resetting the password, caller <b>100</b> is able to use the information to log into one or more systems using the provided password.

0025<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart showing the retrieval of voice signatures when a caller requests a password reset. Processing commences at <b>200</b> when the caller connects to voice recognition system <b>210</b>. This connection is made when the caller uses a standard telephone to dial a telephone number corresponding to voice recognition system <b>210</b> whereupon the voice recognition system answers the incoming call and provides the user with instructions for resetting the password. This may also be reached by selecting an option from a general help desk call-in system. The caller is prompted by voice recognition system <b>210</b> to repeat a series of random words <b>215</b>. The random words were previously recited by the user in another arrangement, such as a predefined script, in order to capture the user's voice signature. The user's voice signature is stored, along with other user' voice signatures, in voice signatures repository <b>220</b>. Voice recognition system compares the caller's response to the series of random words with the user's voice signature in order to authenticate the caller as being the corresponding user.

0026If the caller's voice is not authenticated, “no” branch <b>235</b> is taken whereupon the system records logs the failed attempt (step <b>240</b>) and the caller is disconnected from the system at <b>250</b>. On the other hand, if the caller's voice matches the voice signature retrieved from voice signature repository <b>220</b>, decision <b>230</b> branches to “yes” branch <b>255</b> and the user's password is reset (step <b>260</b>). As described in <figref idref="DRAWINGS">FIG. 1</figref>, the password may simply be retrieved from password repository <b>270</b> or may be reset and the new password stored in password repository <b>270</b>. In any event, the password corresponding with the user's system identifier (password <b>290</b>)) is delivered (step <b>280</b>) to caller <b>200</b>. In addition, information concerning the reset transaction, including the caller's id, a timestamp, the user identifiers involved, and perhaps a recording of the callers voice are recorded in reset log database <b>275</b>.

0027<figref idref="DRAWINGS">FIG. 3</figref> is a flowchart showing the authentication of a user's voice and providing the user with a new password. Authentication of user's voice commences at <b>300</b> whereupon the system receives user identification <b>305</b> from user. The user can provide his identification by using the telephone keypad, by speaking the individual letters of his user id and having the system translate the spoken letters into the identifier, using a list of users, or by some other means. This identification may consist of a user id used by the user or another identifier such as the user's social security number, or employee number. The system uses the received user id to find the user from a list of valid users (step <b>310</b>). A check is made to ensure that the identifier provided by user matches an identifier stored in the system (decision <b>315</b>). If the system does not find a match, decision <b>315</b> branches to “no” branch <b>318</b>. The system may allow the user to enter his or her identification several times in case user inadvertently entered incorrect number. However, if the user provides several consecutive incorrect identifiers, the system logs the intrusion (step <b>320</b>) and processing ends at <b>325</b>.

0028If the system matches the user's identification number, decision <b>315</b> branches to “yes” branch <b>328</b>. The system retrieves a list of words (step <b>330</b>) and plays random word for the user (output <b>335</b>). The user is instructed to repeat the words provided by the system. The system retrieves and analyzes the words received from the user (step <b>340</b>) by comparing the user's voice spoken into the telephone with the user's voice signature stored in voice signature repository <b>345</b>. A determination is made as to whether enough data has been received from the caller to authenticate his voice (decision <b>350</b>). If more information is required by the system to authenticate the user's voice, decision <b>350</b> branches to “no” branch <b>352</b> which loops back and plays more random word(s) (output <b>335</b>) and receives and analyzes the additional input (step <b>340</b>) until enough data has been gathered.

0029When enough information has been received and analyzed, decision <b>350</b> branches to “yes” branch <b>354</b>. The system determines whether the caller's voice has been authenticated as belonging to the user based on the user's stored voice signature (decision <b>355</b>). If the user is not been authenticated, “no” branch <b>358</b> is taken whereupon a system log is created (step <b>360</b>) before processing ends at <b>365</b>. On the other hand, if the user is authenticated, decision <b>355</b> branches to “yes” branch <b>368</b> whereupon the system retrieves system identification numbers corresponding to the user from the system identification table <b>371</b> (step <b>370</b>).

0030System identification table <b>371</b> includes three components. User identifier <b>372</b> is the identifier the user uses (i.e., a user id) to access a particular system. This System name <b>373</b> includes system identifiers when multiple systems can be accessed by users. The user may have access to one or more system names within the organization. A password <b>374</b> is assigned to each user id/system name combination. In some environments, a policy is used to ensure that a user has different passwords for each system, while the user's user id may remain constant. In other environments, no such policy exists and the user can have the same password on multiple systems.

0031The system prompts the user with each system name to which the user has access within the organization (step <b>375</b>). Each system name may be read to the user with a corresponding number or other means to clearly distinguish it from other system names. The user then selects one or more systems to which he needs to have his password reset (step <b>380</b>). Based on the user's selections, the system generates new password(s) and delivers them to the user (step <b>385</b>). Information concerning the password reset transaction, such as the user identifier(s) reset, caller identification (Caller ID) information, timestamps, and possibly recorded portions of the caller's responses are recorded in an audit database used to track password resets (step <b>390</b>). Processing subsequently ends at <b>395</b>.

0032<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart showing the steps involved with delivering a new password to a user. Processing commences at <b>400</b> whereupon processing reads system policy (input <b>405</b>). The system policy is established by the organization and includes the accepted methods by which passwords can be delivered to users. The user's profile is read (input <b>410</b>) to determine the delivery method selected by the user within the system policy. Based upon the system's policy and the user's profile, there may be a variety of acceptable methods to deliver a new password. A decision is made as to the delivery method chosen by the user and accepted by the organization (decision <b>415</b>). If the user has selected voice mail as his or her delivery method, decision <b>415</b> branches to “yes” branch <b>418</b> whereupon the system calls the user's voice mail (step <b>420</b>) and records the new password (step <b>423</b>). After the password has been saved on the user's voice mail, processing ends at <b>425</b>. If the user has not selected voice mail as delivery method, decision <b>415</b> branches to “no” branch <b>428</b>.

0033If the user has selected electronic mail (email) as the delivery method, decision <b>430</b> branches to “yes” branch <b>433</b> whereupon the system prepares an email message (step <b>435</b>) with new password and sends the message to the user's e-mail account (step <b>438</b>). After the email message has been sent, processing ends at <b>440</b>. If the user has not selected e-mail as delivery method, decision <b>430</b> branches to “no” branch <b>443</b>.

0034If the user has selected to receive a telephone call as his or her delivery method, decision <b>445</b> branches to “yes” branch <b>446</b> whereupon the system calls the user at predetermined number (step <b>448</b>), such as the user's home telephone number or the user's office number, and reads the new password to the user. After the call has been terminated, processing ends at <b>450</b>. If the user has not selected to receive a telephone call as the delivery method, decision <b>445</b> branches to “no” branch <b>453</b>.

0035If the user has selected to receive the password by means of a wireless device (i.e., pager, cellular phone, personal digital assistant) as his or her delivery method, decision <b>455</b> branches to “yes” branch <b>456</b>. The system calls the user at a predetermined number (step <b>458</b>) corresponding to the user's wireless device and provides the new password. After the password has been delivered, processing ends at <b>460</b>. If the user has not selected to receive passwords using a wireless device, decision <b>455</b> branches to “no” branch <b>463</b>.

0036If the user has selected to receive a letter as his or her delivery method, decision <b>465</b> branches to “yes” branch <b>468</b>. The system prepares a letter (step <b>470</b>) and sends it to the user's mailing address (step <b>473</b>). After the letter has been sent, processing ends at <b>475</b>. If the user has not selected to receive a letter as a delivery method, decision <b>465</b> branches to “no” branch <b>478</b>.

0037The system policy may allow the user to receive the password using another delivery mechanism (step <b>480</b>). For example, the policy may allow the new password to be provided on the same telephone call that the user used to request the password reset. This option would provide the user with the new password instantaneously. On the other hand, providing the user a new password using other non-instantaneous methods could provide an additional level of security. If no other delivery mechanisms are utilized and the new password has been delivered to user, processing ends at <b>490</b>.

0038<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart showing the steps involved with recording the user's voice signature. The user's voice signature is captured before the user is able to reset his passwords using the voice recognition password reset function. During a subsequent password reset request, the voice signature captured using the steps shown in <figref idref="DRAWINGS">FIG. 5</figref> is used to authenticate the user.

0039Processing commences at <b>500</b> whereupon the system receives the user's user id and personal identification number (PIN) (input <b>510</b>). The organization provides the user with the user id to identify the user on one or more computer systems. The organization also provides the user with a PIN code that is used as a password to access the system used to capture the user's voice signature. In order to enhance security, it may be desirable to have the user record his voice signature at a known location that can be verified by the system. For example, the user could call the system from his office or home and the phone number used can be obtained using caller identification (i.e., Caller ID) technology and verified by matching the phone number with the user's phone number stored in the organization's directory.

0040Other security techniques could be used to authenticate the user may include receiving additional information (date of birth, zip code, social security number, etc.) from the user. For further security, the system could call the user back at his office or home after the receiving the user's user id and PIN. Once answered by the user, the system could ask a series of additional questions to authenticate user. Using the information provided by the user, the system authenticates the user's identity (step <b>520</b>).

0041A determination is made as to whether the information received from the user authenticates the user (decision <b>530</b>). If the user is not authenticated, decision <b>530</b> branches to “no” branch <b>535</b> whereupon a log is created (step <b>540</b>) of the attempt to enter the system and processing ends at <b>550</b>. If the user is authenticated, decision <b>530</b> branches to “yes” branch <b>555</b> and a script file is retrieved (input <b>560</b>). The user may be asked to repeat the script after being prompted by the system or may be able to retrieve the script from a network file on the organization's intranet or from a web site belonging to the organization and accessible from the Internet. The system receives the user's voice input (input <b>565</b>) in response to the user reading the script. The system stores the user's voice (input <b>570</b>) in a data storage area. In order to determine the user's voice signature (step <b>575</b>), the voice recognition software converts the analog signal received from telephone to a digital representation. This digital representation is stored as the user's voice signature (step <b>580</b>). The voice signature may be used at a later date if the user needs to reset one of his passwords (see <figref idref="DRAWINGS">FIGS. 1–3</figref>). After the user's voice signature is captured, processing ends at <b>590</b>.

0042<figref idref="DRAWINGS">FIG. 6</figref> illustrates information handling system <b>601</b> which is a simplified example of a computer system capable of performing the mobile telephone company operations. Computer system <b>601</b> includes processor <b>600</b> which is coupled to host bus <b>605</b>. A level two (L2) cache memory <b>610</b> is also coupled to the host bus <b>605</b>. Host-to-PCI bridge <b>615</b> is coupled to main memory <b>620</b>, includes cache memory and main memory control functions, and provides bus control to handle transfers among PCI bus <b>625</b>, processor <b>600</b>, L2 cache <b>610</b>, main memory <b>620</b>, and host bus <b>605</b>. PCI bus <b>625</b> provides an interface for a variety of devices including, for example, LAN card <b>630</b>. PCI-to-ISA bridge <b>635</b> provides bus control to handle transfers between PCI bus <b>625</b> and ISA bus <b>640</b>, universal serial bus (USB) functionality <b>645</b>, IDE device functionality <b>650</b>, power management functionality <b>655</b>, and can include other functional elements not shown, such as a real-time clock (RTC), DMA control, interrupt support, and system management bus support. Peripheral devices and input/output (I/O) devices can be attached to various interfaces <b>660</b> (e.g., parallel interface <b>662</b>, serial interface <b>664</b>, infrared (IR) interface <b>666</b>, keyboard interface <b>668</b>, mouse interface <b>670</b>, and fixed disk (HDD) <b>672</b>) coupled to ISA bus <b>640</b>. Alternatively, many I/O devices can be accommodated by a super I/O controller (not shown) attached to ISA bus <b>640</b>.

0043BIOS <b>680</b> is coupled to ISA bus <b>640</b>, and incorporates the necessary processor executable code for a variety of low-level system functions and system boot functions. BIOS <b>680</b> can be stored in any computer readable medium, including magnetic storage media, optical storage media, flash memory, random access memory, read only memory, and communications media conveying signals encoding the instructions (e.g., signals from a network). In order to attach computer system <b>601</b> to another computer system to copy files over a network, LAN card <b>630</b> is coupled to PCI-to-ISA bridge <b>635</b>. Similarly, to connect computer system <b>601</b> to an ISP to connect to the Internet using a telephone line connection, modem <b>675</b> is connected to serial port <b>664</b> and PCI-to-ISA Bridge <b>635</b>.

0044While the computer system described in <figref idref="DRAWINGS">FIG. 6</figref> is capable of executing the invention described herein, this computer system is simply one example of a computer system. Those skilled in the art will appreciate that many other computer system designs are capable of performing the copying process described herein.

0045One of the preferred implementations of the invention is an application, namely, a set of instructions (program code) in a code module which may, for example, be resident in the random access memory of the computer. Until required by the computer, the set of instructions may be stored in another computer memory, for example, on a hard disk drive, or in removable storage such as an optical disk (for eventual use in a CD ROM) or floppy disk (for eventual use in a floppy disk drive), or downloaded via the Internet or other computer network. Thus, the present invention may be implemented as a computer program product for use in a computer. In addition, although the various methods described are conveniently implemented in a general purpose computer selectively activated or reconfigured by software, one of ordinary skill in the art would also recognize that such methods may be carried out in hardware, in firmware, or in more specialized apparatus constructed to perform the required method steps.

0046While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from this invention and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this invention. For example, the bank account numbers, etc., may be placed on the preprinted checks differently depending on standards in other countries or based upon a particular situation. Furthermore, it is to be understood that the invention is solely defined by the appended claims. It will be understood by those with skill in the art that if a specific number of an introduced claim element is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation no such limitation is present. For non-limiting example, as an aid to understanding, the following appended claims contain usage of the introductory phrases “at least one” and “one or more” to introduce claim elements. However, the use of such phrases should not be construed to imply that the introduction of a claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an”; the same holds true for the use in the claims of definite articles.