Patent Description:
Today, the majority of people utilize mobile devices to conduct much of their day-today activities such as conducting banking activities, performing business tasks, utilizing for entertainment, etc. People are also utilizing their mobile devices to conduct telephone calls and speak with other people. In some instances, these telephone calls may require the user to speak aloud, which may be overheard by other people nearby. Due to the mobile nature of the mobile devices may be used in public locations. Other people overhearing the user's conversation may be problematic when the user is saying sensitive information, such as personal information, banking information, health information and so forth. For example, a large number of purchases are still made over telephone calls. These interactions typically require the user to read aloud sensitive information such as their credit card number, expiration date, and security code. These interactions can take a long time, are prone to errors, and opens the door to 3rd party eaves droppers who can steal the sensitive information. Thus, embodiments discussed herein relate to solving these problems and enable users to provide sensitive information in a secure manner. Document <CIT> is a further relevant prior-art document.

Embodiments may be generally directed to detecting a request for sensitive information over a phone connection, electronically generating the sensitive data, and provide it a user or person over a phone connection. For example, embodiments may include systems and techniques to detect a request to provide banking account information over a voice connection, wherein the voice connection is established between the mobile device and a phone device via the communication interface, apply a speech-recognition analyzer to identify the banking account information in the request, and generate speech data representing the banking account information requested, wherein the speech data is in an audible format. Embodiments also include techniques to cause communication of the speech data to the phone device via the communication interface on the voice connection.

In another example, embodiments may include system and techniques to detect a request to provide banking account information over a three-way voice connection, apply a speech-recognition analyzer to identify the banking account information in the request, and generate speech data representing the banking account information requested, wherein the speech data is in an audible format capable of being played through a speaker of the second phone device. Embodiments further include techniques to cause communication of the speech data on the three-way voice connection.

The invention is defined in the independent claims <NUM>, <NUM> and <NUM>. Various embodiments may be generally directed to systems, devices, apparatuses, and so forth to enable users to provide sensitive information over a voice connection between telephone devices. Occasionally, people are asked to provide sensitive information during a voice call, such as providing bank card information to perform a transaction. However, when this information is spoken by a user, other people in the vicinity may hear the sensitive information and steal it. Embodiments discussed herein enable users to provide the information without saying it out loud. For example, embodiments include perform one or more operations to detect when sensitive information is being requested, determine the information requested, generate synthesized speech data including the requested information, and providing the information over the voice connection.

Although embodiments discussed herein are directed to sharing bank account information over the voice connection, embodiments are not limited in this manner. The techniques discussed herein can be applied to any situation where a user is providing sensitive information, e.g., medical information, social security information, personal information such as an address, phone number, and so forth.

Various embodiments may include one or more elements. An element may comprise any structure arranged to perform certain operations. Each element may be implemented as hardware, software, or any combination thereof, as desired for a given set of design parameters or performance constraints. Although an embodiment may be described with a limited number of elements in a certain topology by way of example, the embodiment may include more or fewer elements in alternate topologies as desired for a given implementation. It is worthy to note that any reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrases "in one embodiment," "in some embodiments," and "in various embodiments" in various places in the specification are not necessarily all referring to the same embodiment.

<FIG> illustrates an example of a communication system <NUM> to enable users to provide bank account information to another party over a voice connection <NUM> without people in the hearing the sensitive information. The system <NUM> may enable a user, via a mobile device <NUM>, to conduct a telephone voice conversation with another person via phone device <NUM>. The telephone voice conversation may include requiring the user to give the person their banking account information, such as a credit or debit card number over the voice connection <NUM>. Previously, the user would be required to verbally say their banking accounting information to the other person. However, verbally providing the banking information runs the risk of someone else hearing and stealing the information. Embodiments discussed herein overcome these issues and include the mobile device <NUM> detecting the request for the banking account information, generating speech data including the requested banking account information, and communicating the speech data to the phone device <NUM> and the other person. Thus, the mobile device <NUM> itself "speaks" the bank account information and the user is not required to say the information out loud and for other people to hear.

In embodiments, the system <NUM> may enable a voice connection <NUM> to be established between the mobile device <NUM> and the telephone device <NUM>. The mobile device <NUM> may be any device capable of conducting a voice telephone call, e.g., a mobile phone device, a smartphone, a personal digital assistant, a wearable device, a smart home device, and so forth. In some instances, the mobile device <NUM> may be a telephone device, such as a landline telephone. The telephone device <NUM> may also be any type of device capable of making a telephone call over a voice connection <NUM> including a landline telephone, a mobile device, a smartphone, and so forth.

In embodiments, the mobile device <NUM> may establish a voice connection <NUM> with the telephone device <NUM> by establishing a call with the telephone device <NUM> over one or more of a cellular telephone network, voice over Internet Protocol (VOIP) network, a public switched telephone network, or a combination thereof. In one example, the mobile device <NUM> may establish the voice connection <NUM> with the telephone device <NUM> by performing an outbound call based on received user input, e.g., a user selection on a touchscreen interface to initiate a call to someone. In another example, the mobile device <NUM> may establish the voice connection <NUM> based on reception of an incoming call, e.g., the user of telephone device <NUM> calls the user of mobile device <NUM>. Once the voice connection <NUM> is established between the mobile device <NUM> and telephone device <NUM>, the users may verbally communicate with each other.

In some instances, a conversation may include a user of the telephone device <NUM> verbally requesting sensitive information, such as banking account information to perform a transaction. For example, the user of mobile device <NUM> may call a pizza parlor to order a pizza and may be required to give banking account information over the voice connection <NUM> to finalize the order. Embodiments are not limited to this example, and embodiments discussed herein apply to any instance where a user is required to provide sensitive information verbally to another user.

In embodiments, the mobile device <NUM> may detect the request to provide the banking account information over a voice connection <NUM>. In one example, the mobile device <NUM> may automatically detect the request by utilizing a speech recognition analyzer. The speech recognition analyzer may be software trained to detect keywords relating to the request for sensitive information, such as banking information. The speech recognition analyzer may be a standalone software component or application (app) on the mobile device <NUM> or may be implemented as part of another app, such as a banking app or an app associated with a banking provider. In the banking information example, the keywords may include terms, such as "bank account number", "credit card number", "debit card number", "name", "expiration date", "Card Verification Value", "CVV", and so forth. Other sensitive information may include a person's social security information, medical information, and so forth. In one example, the speech recognition analyzer may operate in the background and may listen for one or more of the keywords received in an audible format via the interface coupled with the voice connection <NUM>. The speech recognition analyzer may utilize a speech recognition technique to translate received spoken words into text and compare the text to one or more keywords stored in memory. A detection occurs when a match occurs between a keyword and translated spoken word. The speech recognition analyzer may utilize techniques such as pattern matching, pattern and feature analysis, statistical analysis, and artificial neural networks. In one example, the speech recognition analyzer may receive the speech over the voice connection <NUM> and determine soundwave patterns and generate spectrograms (frequency patterns) by applying analog to digital conversion techniques and perform fast fourier transform processing. The speech recognition analyzer may determine a sequence of acoustic frames and generate "beads-on-a-string" by performing feature analysis and apply a phonetic dictionary. A hidden markov model may be built based on the sequence of acoustic frames and "bead-on-a-string" and the speech may be recognized.

The mobile device <NUM>, based on the request, may perform additional operations to provide the requested banking account information over the voice connection <NUM>, i.e., answer the request. In some instances, the mobile device <NUM> may perform one or more security operations. For example, the mobile device <NUM> may require a user to authenticate himself or herself to provide the sensitive information. For example, the mobile device <NUM> executes an authentication routine and requires the user of the mobile device <NUM> to enter one or more authenticating inputs, e.g., a password, a password pattern, a biometric, etc. In some instances, two-part authentication may be utilized, e.g., a password and email confirmation.

In one example, the mobile device <NUM> may require the user to enter their username and password to entering a banking app associated with the banking account information. The mobile device <NUM> may present a prompt on a display device for the user to enter their username and password to access a banking app, for example. The mobile device <NUM> may receive a user input via a user input device, from the user including a username entry and a password entry. The mobile device <NUM> may authenticate the user of the mobile device <NUM> as one of the one or more authorized users of the bank account when the username entry matches an authenticate username and the password entry matches an authenticate password. In another example, the mobile device <NUM> may receive, via an input device, a biometric input, and authenticate the user of the mobile device <NUM> as one of the one or more authorized user of the bank account when the biometric input matches an authentic biometric input. Embodiments are not limited to these examples.

In embodiments, the mobile device <NUM> may determine whether to communicate the banking account information to the telephone device <NUM> based on whether the user is authenticated by the mobile device <NUM>. If the user is not authenticated, the mobile device <NUM> may prevent the banking account information from being sent to the telephone device <NUM>. If the user is authenticated, the mobile device <NUM> may send the banking account information to the telephone device <NUM>. To send the information, the mobile device <NUM> may determine what banking account information to send to the telephone device <NUM> based on the received request. For example, the translated text output of the speech recognition analyzer may indicate the banking account information requested, e.g., banking account number, an expiration date, a CVV, or a combination thereof. The mobile device <NUM> may determine the banking account information requested and retrieve the information from memory or a storage device, which may be a secured storage or memory. In some instances, the mobile device <NUM> may communicate and perform a look up to retrieve the requested information in a database, which may be remote from the mobile device <NUM> and/or in a cloud-based system.

In embodiments, the mobile device <NUM> may generate speech data representing the banking account information requested. The speech data may be in an audible format capable of being played through a speaker of the receiving device, e.g., telephone device <NUM>. In one example, the mobile device <NUM> utilizes a speech synthesizer to generate the speech data. The speech synthesizer may be a standalone software application and/or implemented as part of a banking app. The requested information may be in a text format in storage, memory, and/or a database, and the mobile device <NUM> including the speech synthesizer may synthesize the text to convert into speech data that can audibly be heard by the user of device <NUM>.

In embodiments, the speech synthesizer may include a front-end component and a back-end component. The front-end component may convert the text into equivalent written-out words, e.g., text normalization, pre-processing, and tokenization. The front-end component may then assign phonetic transcriptions to each word and divide the text into units, such as phrases, clauses, and sentences. The back-end component may further process the text by converting the symbolic linguistic representations into sound, e.g., speech data. The mobile device <NUM> may cause the speech data to be communicated, via an interface coupled to the voice connection <NUM>, to the telephone device <NUM>.

In some instances, mobile device <NUM> may be configured to detect an error or issues with the speech data and repeat communication of the speech data. For example, the recipient of the speech data may not understand or may miss one or more words spoken on the telephone device <NUM>. The speech data may become inaudible due to interference during transmission or background noise may interfere with the recipient hearing the speech data. The mobile device <NUM> may detect the interference via noise detected on the communication link and/or the recipient may request a clarification and that the information to be repeated. For example, the mobile device <NUM> including the speech recognition analyzer may detect the request to repeat the banking account information and cause the speech data of the banking account information to be resent. In some instances, the recipient may request for specific banking account information to be repeated, e.g., the bank account number. The speech recognition analyzer may determine what information is being requested by performing speech-recognition and cause only the specific requested information may be sent to the telephone device <NUM>. Embodiments may also include regenerating and generating new speech data corresponding to the requested repeated information. In other instances, the mobile device <NUM> may resend the original speech data.

In some embodiments, the mobile device <NUM> may apply one or more security measures or usage restrictions when sharing the sensitive information with the telephone device <NUM>. For example, the mobile device <NUM> may apply a security measure to banking account information by generating and utilizing a virtual banking account number corresponding to the banking account number and providing the virtual bank account number to the telephone device <NUM>. More specifically, the mobile device <NUM> may generate the speech data include the virtual banking account number and send the speech data with the virtual banking account number to the telephone device <NUM>. Using the virtual banking account number may enable one or more restrictions to be applied for the transaction. For example, the mobile device <NUM> may apply a time limit restriction such that the virtual banking account number may only be used to perform transactions within a certain amount of time. Other restrictions may include an amount restriction limiting the total amount that can be charged against the virtual number and a location restriction limiting the range or area where a transaction may occur.

In some instances, the mobile device <NUM> may determine one or more of the restrictions based on information relating to the requestor and the telephone device <NUM>. For example, the mobile device <NUM> may determine an area to limit the transaction for shared banking account information based on an area associated with a phone number associated with the other phone device <NUM>. The mobile device may then apply a location restriction for the use of the shared information based on the determined area. The mobile device <NUM> may utilize phone number lookup techniques to determine the phone number.

In embodiments, the mobile device <NUM> may detect and/or receive a request to provide banking account information over a voice connection <NUM> and utilize a third-party system or banking system to provide the information. <FIG> illustrates one example of a communication system <NUM> in which a mobile device <NUM> may utilize a third-party system, such as a banking system <NUM> to provide the banking account information. The banking system <NUM> may include one or more computing devices, such as servers to answer calls, determine requested information, and provide the information over one or more voice connections <NUM>. In embodiments, the banking system <NUM> may include cloud-based computing resources, such as processing resources, memory resources, and storage resources. The banking system <NUM> may be operated by a bank and/or outsourced to an automated call-center utilized by a bank to handle calls. Embodiments are not limited in this manner.

In embodiments, a mobile device <NUM> may establish a voice connection <NUM> with the telephone device <NUM>, as similarly discussed above in <FIG>. However, in this example, the mobile device <NUM> may detect a request for the banking account information and initiate a three-way communication or connection between the mobile device <NUM>, the telephone device <NUM>, and the banking system <NUM> by establishing additional voice connections <NUM>. For example, the mobile device <NUM> may call a phone number associated with the banking system <NUM> and an automated answering system hosted by the banking system <NUM> may answer the call. The mobile device <NUM> may establish the three-way connection such that a user of the mobile device <NUM> and the telephone device <NUM> may hear the speech data from the banking system <NUM>. In embodiments, the three-way connection may be generated by the mobile device <NUM> using known three-way calling techniques, and the three-way connections may include one or more voice connections <NUM> over a cellular telephone system, a VOIP telephone system, a public switched telephone system, or combination thereof.

In the illustrated example of <FIG>, the mobile device <NUM> may detect the request to provide banking account information over a voice connection <NUM> between the mobile device <NUM> and the telephone device <NUM>. As discussed above, the mobile device <NUM> may automatically detect the request by utilizing a speech recognition analyzer. The mobile device <NUM>, based on the request, may establish a voice connection <NUM> between the mobile device <NUM> and the banking system <NUM>. In some instances, the mobile device <NUM> may first require the user to authenticate prior to establishing a connection. The mobile device <NUM> may utilize any type of authentication as previously discussed, username/password combo, password, secure pattern, biometric input, two-part authentication, and so forth. If the mobile device <NUM> does not authenticate the user, the mobile device <NUM> may not contact the banking system <NUM>. Alternatively, if the mobile device <NUM> does authenticate the user, the mobile device <NUM> may call the banking system <NUM> and generate a three-way call using a three-way calling technique. In some instances, the mobile device <NUM> may establish the connection and the banking system <NUM> may perform the authentication techniques. In instances, the three-way call may be halted when authentication fails.

The banking system <NUM> may perform one or more operations to provide the requested banking account information. In some instances, the banking system <NUM> may require the user of the telephone device <NUM> to repeat the request or state the request once the three-way communication is established, perform the speech recognition analysis on the request, and determine the requested information. In some instances, the mobile device <NUM> may determine and/or provide the information. For example, the mobile device <NUM> may provide a recording of the request to the banking system <NUM> in an audible format. In another example, the mobile device <NUM> may generate text data of the request using the speech recognition and provide the text data to the banking system <NUM> over a data connection (not shown). The text data may be the requested banking account information in a text format.

In embodiments, the banking system <NUM> may determine the banking account information to communicate to the telephone device <NUM> based on the request spoken by a user of the telephone device <NUM>, a recording of the request from the mobile device <NUM>, and/or a text data version of the request received from the mobile device <NUM>. For example, the banking system <NUM> may receive a request from a user of the telephone device <NUM> verbally and perform speech recognition analysis to translate the request to text. In another example, the banking system <NUM> may perform speech recognition on a recording of the request received from the mobile device <NUM> and generate text. In other instances, the banking system <NUM> may receive text from the mobile device <NUM>. The banking system <NUM> may utilize the text, either translated by the banking system <NUM> or received from the mobile device <NUM>, and determine the banking account information requested, e.g., banking account number, an expiration date, a CVV, or a combination thereof.

In embodiments, banking system <NUM> may perform a lookup in database or datastore stored in memory, storage, cloud-based storage, etc. to determine the requested banking account information requested and associated with a user of the mobile device <NUM>. For example, the banking system <NUM> may determine a telephone number associated with the mobile device <NUM> to determine the user and perform a lookup based on the telephone number. In other instances, the banking system <NUM> may receive data from the mobile device <NUM> indicating the user, e.g., a username or other identifier. The data may be communicated by the mobile device <NUM> to the banking system <NUM> over a data connection. Embodiments are not limited in this manner and any identifier lookup technique may be used to determine the banking account information associated with the user of the mobile device <NUM>.

The banking system <NUM> may retrieve the banking account information from a database, memory, storage, and so forth, and generate speech data representing the banking account information requested. The speech data may be in an audible format capable of being played through a speaker of the telephone device <NUM>. In one example, the banking system <NUM> may utilize a speech synthesizer to generate the speech data. For example, the banking system <NUM> may determine the banking account information requested, and retrieve the information from memory or a storage device. The requested bank account information may be in a text format, and the banking system <NUM> may synthesize the text to convert into speech data that can audibly be heard by the user of device <NUM>. The speech synthesizer may include a front-end component and a back-end component to convert the text into words, assign phonetic transcriptions, divide the text into units, and generate sound, as previously discussed. The banking system <NUM> may cause the speech data to be communicated, via an interface coupled to the voice connection <NUM>, to at least the telephone device <NUM>.

In some instance, the banking system <NUM> may detect instances when at least a portion of the speech data needs to be repeated. The banking system <NUM> may detect interference in communication of the speech data or may also be configured to process a request to clarify or repeat the sensitive information. For example, the banking system <NUM>, including a speech recognition analyzer, may detect the request to repeat the banking account information and cause the speech data of the banking account information to be resent. In some instances, the recipient may request for specific banking account information to be repeated. The speech recognition analyzer may determine the information being requested and cause only the specific requested information to be sent to the telephone device <NUM>. In some instances, the banking system <NUM> may change and/or apply one or more variations to the speech data before it is resent. The one or more variations may include an adjustment of pace of the speech data, an adjustment of volume of the speech data, an adjustment of tone of the speech data, an adjustment of dialect or accent of the speech data, or a combination thereof. Embodiments may also include regenerating and generating new speech data corresponding to the requested repeated information.

The banking system <NUM> may also utilize one or more security measures, such as using virtual banking account number and/or applying one or more usage restrictions to the sensitive information. For example, the banking system <NUM> may generate a virtual banking account number and apply one or more usage restrictions to the shared banking account information. More specifically, the banking system <NUM> may generate and utilize a virtual banking account number corresponding to the banking account number and provide the virtual bank account number to the telephone device <NUM>. The virtual banking account number may be a randomly generated one-time use value or token that may be associated with the banking account providing the funds. The banking system <NUM> may generate speech data including the virtual banking account number and send the speech data with the virtual banking account number to the telephone device <NUM>. The banking system <NUM> may also apply one or more usage restrictions to the shared bank account number (virtual or actual). For example, the mobile device <NUM> may apply a time limit restriction, an amount restriction, and/or a location.

In embodiments, the banking system <NUM> may provide the banking account information to the user of the telephone device <NUM>, and once confirmed, may disconnect from the three-way connection. In some instances, the mobile device <NUM> may perform the disconnection and embodiments are not limited in this manner. In some instances, a voice connection <NUM> between the mobile device <NUM> and the telephone device <NUM> may remain established such that the users may finalize the transaction and exchange any additional information.

<FIG>/<FIG> illustrates an example of a logic flow <NUM> to generate and provide sensitive information over a voice telephone connection. <FIG> illustrates an example of a logic flow <NUM> that may be representative of some or all of the operations executed by one or more embodiments and systems described herein, such as those discussed above with respect to a mobile device <NUM> in <FIG>. Moreover, the one or more operations may be performed by an app on a mobile device, such as a banking app executing on mobile device <NUM>, as similarly found in <FIG>.

In embodiments, the logic flow <NUM> includes detecting a request to provide sensitive information over a voice connection at block <NUM>. In one example, the request may be detected by a banking app, operating on a mobile device having a voice connection established with another device, such as a telephone device or mobile device. In embodiments, the request may be a verbal request or sound communicated by the user of the other device over the voice connection. The app may include one or more processes executing on the mobile device to detect one or more specific keywords or phrases, e.g., "Please provide me your credit card information. " In another example, the request may be a user input detected by the mobile device. For example, the user, being asked for credit card information, may invoke the banking app via a user input on the mobile device to provide the requested banking account information. The banking app may initiate operations and provide a user an interface to send speech data including the requested information to the user of the other phone device. For example, the user may interface with a graphical user interface (GUI) of the mobile device to select one or more of a bank account number, expiration date, CVV, or combination thereof to send to the other device.

At block <NUM>, the logic flow <NUM> includes identifying the sensitive information to send to the other device. For example, the banking app may include a speech recognition analyzer to automatically detected the requested banking account information. In another example, the banking app may determine the requested information based on one or more user inputs on the mobile device, as mentioned. The banking account information may include a banking account number, an expiration date, a card verification value, or a combination thereof.

The logic flow <NUM> includes performing an authentication operation to authenticate a user of the mobile device as one of one or more authorized users or owners of the sensitive information at block <NUM>. For example, the banking app may require the user to enter a username and password to authenticate the user to provide the banking or credit card account information. Other authentication methods may be utilized, e.g., biometric, pattern entry, and so forth.

In embodiments, if the authentication operation is unsuccessful, the logic flow <NUM> includes preventing communication of the sensitive information to the other phone device at block <NUM>. For example, the banking app may not provide the banking account information for communication over the voice connection. In some instances, the banking app may notify the user of the mobile device that the authentication failed and that the banking account information will not be provided. If the authentication operation is successful, the logic flow <NUM> includes generating speech data representing the sensitive information requested at block <NUM>. For example, the banking app may include a synthesizer to convert text data representing the banking account information into sound or speech data. The speech data may be in an audible format capable of being played through a speaker of the other phone device, for example. The speech data to communicate may be determined by the banking app or other software as previously discussed. At block <NUM>, the logic flow <NUM> further includes causing communication of the speech data to the other phone device via the communication interface on the voice connection if the authentication operation is successful.

<FIG> illustrates an example of a logic flow <NUM> to provide sensitive information over a three-way connection via a banking system. <FIG> illustrates an example of a logic flow <NUM> that may be representative of some or all of the operations executed by one or more embodiments and systems described herein, such as those discussed above in <FIG>. Moreover, one or more operations may be performed by an app, such as a banking app, executing on a mobile device, as similarly found in <FIG>.

At block <NUM>, the logic flow <NUM> includes detecting a request to provide sensitive information. In embodiments, the detection may be made over a voice connection established between a mobile device and another phone device. For example, a banking app may detect via speech-recognition analysis one or more keywords associated with requesting banking account information.

At block <NUM>, the logic flow <NUM> includes establishing a three-way voice connection between the mobile device, the other phone device, and a system. For example, a banking app on the mobile device may initiate a voice connection with a banking system and establish a three-way voice connection. The banking app may include a routine to initiate a call or may utilize another app on the mobile device to initiate the call. Embodiments are not limited in this manner.

In embodiments, the mobile device may communicate with the banking system an indication to provide the requested sensitive information. For example, the mobile device may send the request to the banking system. The request may be an audio sample format or text based on a voice-to-text conversion. In some instances, the banking system may instruct or having the user of the other phone device repeat the request. Embodiments are not limited in this manner. The banking system may provide the requested information over the voice connection between the mobile device, the other phone device, and the system. As previously discussed, the banking system may also perform authentication of the user of the mobile device prior to providing the requested information. If the user fails to authenticate, the banking system may provide an indication that the information cannot be provided.

At block <NUM>, the logic flow <NUM> includes determining the system provided the sensitive information over the three-way voice connection to the other phone device. For example, the banking app on the mobile device may receive an indication from the banking system that the information has been provided to the other phone device of a data connection. In another example, the banking app may "hear" the banking system provide the information to the other phone device over the three-way connection and confirm the transfer of the information is complete.

At block <NUM>, the logic flow <NUM> includes ending the three-way voice connection between the mobile device, the other phone device, and the banking system. In some instances, a voice connection may be maintained between the mobile device and the other phone device to finalize the transaction. A banking app may break the connection to the banking system while maintaining the connection with the other phone device, for example.

<FIG> illustrates an example of a logic flow <NUM> to provide sensitive information over a three-way connection. <FIG> illustrates an example of a logic flow <NUM> that may be representative of some or all of the operations executed by one or more embodiments and systems described herein, such as those discussed above in <FIG>. Moreover, the one or more operations may be performed by one or more software routines executing on a system, such as a banking system as similarly found in <FIG>.

At block <NUM>, the logic flow <NUM> includes receiving a request to establish a three-way connection between a mobile device, another phone device, and a server of the system. In one example, a banking system may be configured to provide speech data associated with sensitive information, such as banking account information. The banking system may be configured to receive and establish a voice connection (or three-way voice connection) from another device, such as a mobile device. For example, the banking system may receive a call from a mobile device, answer the call, and establish a connection with the mobile device and another phone device.

In embodiments, the logic flow <NUM> includes detecting a request to provide sensitive information over a three-way voice connection, wherein the three-way voice connection is established between the mobile device, the other telephone device, and the system at block <NUM>. In one example, the request may be detected by software or one or more routines executing on the banking system. The request may be a verbal request or sound communicated by the user of the other device over the voice connection. The software may include one or more processes executing on the banking system to detect one or more specific keywords or phrases. In another example, the banking system may receive data from the mobile device over a data connection indicating the request for the banking account information. The data may include a recording of the requested banking account information or the information a translated text format. In another example, the system may request the user of the other phone device, i.e., the requestor, to repeat the request over the voice connection.

At block <NUM>, the logic flow includes identifying the requested sensitive information. For example, if the request is not in a translated text format, the system may apply a speech-recognition analyzer to identify the sensitive information in the request. As mentioned, the sensitive information may include banking account information such as a banking account number, an expiration date, a card verification value, or a combination thereof.

In embodiments, the logic flow <NUM> includes generating speech data representing the sensitive information requested at block <NUM>. For example, the banking system may include a synthesizer to convert text data representing the sensitive information into sound or speech data. The speech data may be in an audible format capable of being played through a speaker of the other phone device. At block <NUM>, the logic flow <NUM> includes causing communication of the speech data to the other phone device via the communication interface over the three-way connection. In embodiments, the banking system may perform additional operations to provide the information, such as repeating one or more of the requested items. Once the information has been provided successfully to the other phone device, the three-way connection may be closed between the banking system, the mobile device, and the other phone device.

<FIG> illustrates a detailed view of a mobile device <NUM>, which may be similar to or the same as mobile device <NUM>. In the illustrated, the mobile device <NUM> includes processor <NUM>, memory <NUM>, interfaces <NUM>, and storage device <NUM>. The processor <NUM> may include one or more processing cores to process information and data. Moreover, a processor <NUM> can include one or more processing devices, such as a microprocessor manufactured by Intel™, AMD™, or any of various processors. The disclosed embodiments are not limited to any type of processor(s).

Coupled with the processor <NUM>, the mobile device <NUM> may also include memory <NUM>. The memory <NUM> can include one or more memory (volatile or non-volatile) devices configured to store instructions used by the processor <NUM> to perform one or more operations consistent with the disclosed embodiments. For example, memory <NUM> can be configured with one or more software instructions, such as programs and applications that can perform one or more operations when executed by the processor <NUM>. In embodiments, the memory <NUM> may store instructions and data on a temporary basis as they are about to be processed by the processor <NUM>.

In embodiments, the mobile device <NUM> may include interfaces <NUM> such as wireless and wired communication interfaces. The communication interfaces may operate in accordance with one or more standards, such as IEEE <NUM>, third, fourth, fifth (NG) generation cellular standards, LTE, CDMA, IEEE <NUM>, and so forth. Embodiments are not limited in this manner. The interfaces <NUM> may include one or more input devices, such as touch-screen inputs, button inputs, camera(s), microphone(s), or any other type of input device.

In embodiments, the mobile device <NUM> may further include a storage device <NUM> coupled with the processor <NUM> and memory <NUM>. The storage device <NUM> may include HDDs, flash memory devices, optical storage devices, floppy storage devices, etc. In some instances, the storage devices <NUM> may include cloud-based storage devices that may be accessed via a network interface. The storage device <NUM> may store one or more applications <NUM> that include instructions that may be executed by the processor <NUM>.

In embodiments, one or more applications <NUM> may include an operating system, such as Windows®, Chrome®, Linux®, Apple OS®, and so forth. An operating system may enable other software applications to access and communicate with hardware devices. An application, which may include one or more instructions, may be configured to interact with the hardware devices, collect data from the hardware devices, and communicate with other systems. The one or more applications may also include a web browser, such as Chrome®, Internet Explorer®, Safari®, Firefox®, and so forth. The web browser may be utilized by a user to surf or browse the websites of the Internet.

In embodiments, the mobile device <NUM> may include one or more dialing or phone apps configured to make voice telephone calls over voice connections. A phone app may be configured to make telephone calls over a WiFi connection, a cellular connection, or a combination thereof. For example, a phone app may be configured to initiate a phone call over a WiFi Connection and switch to a cellular connection, and vice versa. In embodiments, the phone app may be a native app provided with the operating system. Embodiments are not limited in this manner.

In embodiments, the one or more applications <NUM> may include a banking app configured to provide banking functions, such as accessing a user's banking account, depositing and withdrawing funds, checking balance, reviewing and/or modifying settings, and so forth. In embodiments, the banking is also configured to provide requested banking account information to another party, such as a person on the other end of a telephone call. As discussed, the banking app may detect requests for banking account information, generate an audible format of the requested information, and provide the information to the other person on the other device verbally. The banking app may provide the information to the other phone such that it's not played through a speaker of the mobile device <NUM> for other people to hear, e.g., out the speakerphone device of the mobile device <NUM>. In embodiments, the banking app may authenticate and/or verify a user of the mobile device <NUM>.

In some instances, the banking app may be configured to have a third-party provide the requested banking account information over a three-way voice connection. As discussed, the banking app may detect the request for the information and establish a call with a banking system and/or a call center system to provide the information. The mobile app may provide information to the third-party system, an indication of whether a user is authenticated, a recording of the request, a text version of the request, and so forth. The banking app is also configured to breakdown or disconnect from the third-party system once the information has been provided to the other party. The banking app may maintain a connection with the other party and phone device until the transaction is complete.

<FIG> illustrates a detailed view of a banking system <NUM>, which may be the same as banking system <NUM> illustrated in <FIG>. In embodiments, the banking system <NUM> includes one or more servers and/or cloud-based computing components. In one example, the components of the banking system <NUM> include processor <NUM>, memory <NUM>, interfaces <NUM>, and storage device <NUM>. The processor <NUM> may include one or more processing cores to process information and data. Moreover, a processor <NUM> can include one or more processing devices, such as a microprocessor manufactured by Intel™, AMD™, or any of various processors. In embodiments, the processor <NUM> may include cloud-based processing components that may be shared with other systems. The disclosed embodiments are not limited to any type of processor(s).

Coupled with the processor <NUM>, the banking system <NUM> may also include memory <NUM>. The memory <NUM> can include one or more memory (volatile or non-volatile) devices configured to store instructions used by the one or more processors <NUM> to perform one or more operations consistent with the disclosed embodiments. For example, memory <NUM> can be configured with one or more software instructions, such as programs and applications that can perform one or more operations when executed by the processor <NUM>. In embodiments, the memory <NUM> may store instructions and data on a temporary basis as they are about to be processed by the processor <NUM>. In embodiments, the memory <NUM> may be cloud-based memory resources.

In embodiments, the banking system may include interfaces <NUM> such as wireless and wired communication interfaces. The communication interfaces may operate in accordance with one or more standards, such as IEEE <NUM>, third, fourth, fifth (NG) generation cellular standards, LTE, CDMA, IEEE <NUM>, and so forth. Embodiments are not limited in this manner. The interfaces <NUM> may include one or more input devices, such as touch-screen inputs, button inputs, camera(s), microphone(s), or any other type of input device.

In embodiments, the banking system may further include a storage device <NUM> coupled with the processor <NUM> and memory <NUM>. The storage device <NUM> may include HDDs, flash memory devices, optical storage devices, floppy storage devices, etc. In some instances, the storage devices <NUM> may include cloud-based storage devices that may be accessed via a network interface. The storage device <NUM> may store one or more applications that include instructions that may be executed by the processor <NUM>.

In embodiments, one or more applications may include an operating system, such as Windows®, Chrome®, Linux®, Apple OS®, UNIX®, and so forth. In embodiments, the one or more application including one or more dialing or phone apps configured to make voice telephone calls over voice connections. For example, the banking system <NUM> may include a phone application capable of handling one or more calls for banking account information. In embodiments, the phone application of the banking system is capable of handling multiple simultaneous calls from any number of mobile devices.

In embodiments, the one or more applications software to provide the banking account information, e.g., speech-recognition analyzer, synthesizer, and so forth. The software may be configured to provide requested banking account information to another party, such as a person on the other end of a telephone call. As discussed, the software may be configured to detect requests for banking account information or process recorded or text requests from a mobile device, generate an audible format of the requested information, and provide the information to the other person on the other device verbally.

<FIG> illustrates an embodiment of an exemplary computing architecture <NUM> that may be suitable for implementing an apparatus, system, and/or method for performing operations associated with the implementation of one or more of the disclosed techniques. In various embodiments, the computing architecture <NUM> may comprise or be implemented as part of an electronic device and/or system discussed herein.

As used in this application, the terms "system" and "component" and "module" are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing architecture <NUM>. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Further, components may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

As shown in <FIG>, the computing architecture <NUM> comprises a processing unit <NUM>, a system memory <NUM> and a system bus <NUM>. The processing unit <NUM> can be any of various commercially available processors, including without limitation an AMD® Athlon®, Duron® and Opteron® processors; ARM® application, embedded and secure processors; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Intel® Celeron®, Core (<NUM>) Duo®, Itanium®, Pentium®, Xeon®, and XScale® processors; and similar processors. Dual microprocessors, multi-core processors, and other multi-processor architectures may also be employed as the processing unit <NUM>. In some embodiments, processing circuitry of processing unit <NUM> and/or other processing circuitry of computing architecture <NUM> may be operative to perform operations associated with the logic flows, and/or other operations associated with implementation of one or more of the disclosed techniques. In some embodiments, such processing circuitry may be coupled to a network interface of computing architecture <NUM>.

The computer <NUM> may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive (HDD) <NUM>, a magnetic floppy disk drive (FDD) <NUM> to read from or write to a removable magnetic disk <NUM>, and an optical disk drive <NUM> to read from or write to a removable optical disk <NUM> (e.g., a CD-ROM or DVD). The HDD <NUM>, FDD <NUM> and optical disk drive <NUM> can be connected to the system bus <NUM> by a HDD interface <NUM>, an FDD interface <NUM> and an optical drive interface <NUM>, respectively. The HDD interface <NUM> for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE <NUM> interface technologies.

The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives and memory units <NUM>, <NUM>, including an operating system <NUM>, one or more application programs <NUM>, other program modules <NUM>, and program data <NUM>.

A user can enter commands and information into the computer <NUM> through one or more wire/wireless input devices, for example, a keyboard <NUM> and a pointing device, such as a mouse <NUM>. Other input devices may include microphones, infra-red (IR) remote controls, radio-frequency (RF) remote controls, game pads, stylus pens, card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors, styluses, and the like. These and other input devices are often connected to the processing unit <NUM> through an input device interface <NUM> that is coupled to the system bus <NUM>, but can be connected by other interfaces such as a parallel port, IEEE <NUM> serial port, a game port, a USB port, an IR interface, and so forth.

When used in a WAN networking environment, the computer <NUM> can include a modem <NUM>, or is connected to a communications server on the WAN <NUM>, or has other means for establishing communications over the WAN <NUM>, such as by way of the Internet. The modem <NUM>, which can be internal or external and a wire and/or wireless device, connects to the system bus <NUM> via the input device interface <NUM>. In a networked environment, program modules depicted relative to the computer <NUM>, or portions thereof, can be stored in the remote memory/storage device <NUM>. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

The computer <NUM> is operable to communicate with wire and wireless devices or entities using the IEEE <NUM> family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE <NUM> over-the-air modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wireless technologies, among others. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies called IEEE <NUM>. 11x (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE <NUM>-related media and functions).

It is emphasized that the Abstract of the Disclosure is provided to comply with <NUM> C. § <NUM>(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, novel subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate preferred embodiment. In the appended claims, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein," respectively. Moreover, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

Claim 1:
A computer-implemented method, comprising:
generating, using at least one processor of a banking system (<NUM>), a virtual banking account number corresponding to a banking account of a user associated with a first device (<NUM>), the virtual banking account number being generated in response to receiving a request for providing the banking account from a second device (<NUM>) to perform a transaction;
associating, using the at least one processor, at least one restriction with the generated virtual banking account number, the at least one restriction including one or more usage restrictions applied to the generated virtual banking account number for the transaction;
converting, using the at least one processor, the generated virtual banking account number to an audible virtual banking account number;
authenticating, using the at least one processor, the user and transmitting, upon the authenticating of the user, via a voice connection established with the second device, the audible virtual banking account number to the second device; and
receiving, using the at least one processor, a confirmation from the second device confirming receipt of the audible virtual banking account number, wherein the transaction is finalized on a voice connection maintained between the first device and the second device. in accordance with the at least one restriction, upon receipt of the confirmation.