US 8,352,272 B2Grant
Systems and methods for text to speech synthesis
Issue Date:2013-01-08
•21 Claims
•10 Drawing Sheets
Abstract
Algorithms for synthesizing speech used to identify media assets are provided. Speech may be selectively synthesized form text strings associated with media assets. A text string may be normalized and its native language determined for obtaining a target phoneme for providing human-sounding speech in a language (e.g., dialect or accent) that is familiar to a user. The algorithms may be implemented on a system including several dedicated render engines. The system may be part of a back end coupled to a front end including storage for media assets and associated synthesized speech, and a request processor for receiving and processing requests that result in providing the synthesized speech. The front end may communicate media assets and associated synthesized speech content over a network to host devices coupled to portable electronic devices on which the media assets and synthesized speech are played back.
Metadata
Assignee
- Apple Inc.
Inventors
- Matthew Rogers
- Kim Silverman
- Devang Naik
- Kevin Lenzo
- Benjamin Rottler
Application Information
Application Number:US 12/240,404
Filing Date:2008-09-29
Priority Date:2008-09-29
Art Unit:2626
Classifications
IPC:
G10L13/08
Patent Drawings (10 sheets)
Description
Field of the Invention
[0001] This relates to systems and methods for synthesizing audible speech from text.
Background of the Disclosure
[0002] Today, many popular electronic devices, such as personal digital assistants (“PDAs”) and hand-held media players or portable electronic devices (“PEDs”), are battery powered and include various user interface components. Conventionally, such portable electronic devices include buttons, dials, or touchpads to control the media devices and to allow users to navigate through media assets, including, e.g., music, speech, or other audio, movies, photographs, interactive art, text, etc., resident on (or accessible through) the media devices, to select media assets to be played or displayed, and/or to set user preferences for use by the media devices. The functionality supported by such portable electronic devices is increasing. At the same time, these media devices continue to get smaller and more portable. Consequently, as such devices get smaller while supporting robust functionality, there are increasing difficulties in providing adequate user interfaces for the portable electronic devices.
[0003] Some user interfaces have taken the form of graphical user interfaces or displays which, when coupled with other interface components on the device, allow users to navigate and select media assets and/or set user preferences. However, such graphical user interfaces or displays may be inconvenient, small, or unusable. Other devices have completely done away with a graphical user display.
[0004] One problem encountered by users of portable devices that lack a graphical display relates to difficulty in identifying the audio content being presented via the device. This problem may also be encountered by users of portable electronic devices that have a graphical display, for example, when the display is small, poorly illuminated, or otherwise unviewable.
[0005] Thus, there is a need to provide users of portable electronic devices with non-visual identification of media content delivered on such devices.
Summary of the Disclosure
[0006] Embodiments of the invention provide audible human speech that may be used to identify media content delivered on a portable electronic device, and that may be combined with the media content such that it is presented during display or playback of the media content. Such speech content may be based on data associated with, and identifying, the media content by recording the identifying information and combining it with the media content. For such speech content to be appealing and useful for a particular user, it may be desirable for it to sound as if it were spoken in normal human language, in an accent that is familiar to the user.
[0007] One way to provide such a solution may involve use of speech content that is a recording of an actual person's reading of the identifying information. However, in addition to being prone to human error, this approach would require significant resources in terms of dedicated man-hours, and may be too impractical for use in connection with distributing media files whose numbers can exceed hundreds of thousands, millions, or even billions. This is especially true for new songs, podcasts, movies, television shows, and other media items that are all made available for downloading in huge quantities every second of every day across the entire globe.
[0008] Accordingly, processors may alternatively be used to synthesize speech content by automatically extracting the data associated with, and identifying, the media content and converting it into speech. However, most media assets are typically fixed in content (i.e., existing personal media players do not typically operate to allow mixing of additional audio while playing content from the media assets). Moreover, existing portable electronic devices are not capable of synthesizing such natural-sounding high-quality speech. Although one may contemplate modifying such media devices so as to be capable of synthesizing and mixing speech with an original media file, such modification would include adding circuitry, which would increase the size and power consumption of the device, as well as negatively impact the device's ability to instantaneously playback media files.
[0009] Thus, other resources that are separate from the media devices may be contemplated in order to extract data identifying media content, synthesize it into speech, and mix the speech content with the original media file. For example, a computer that is used to load media content onto the device, or any other processor that may be connected to the device, may be used to perform the speech synthesis operation.
[0010] This may be implemented through software that utilizes processing capabilities to convert text data into synthetic speech. For example, such software may configure a remote server, a host computer, a computer that is synchronized with the media player, or any other device having processing capabilities, to convert data identifying the media content and output the resulting speech. This technique efficiently leverages the processing resources of a computer or other device to convert text strings into audio files that may be played back on any device. The computing device performs the processor intensive text-to-speech conversion so that the media player only needs to perform the less intensive task of playing the media file. These techniques are described in commonly-owned, co-pending patent application Ser. No. 10/981,993, filed on Nov. 4, 2004 (now U.S. Published Patent Application No. 2006/0095848), which is hereby incorporated by reference herein in its entirety.
[0011] However, techniques that rely on automated processor operations for converting text to speech are far from perfect, especially if the goal is to render accurate, high quality, normal human language sounding speech at fast rates. This is because text can be misinterpreted, characters can be falsely recognized, and the process of providing such rendering of high quality speech is resource intensive.
[0012] Moreover, users who download media content are nationals of all countries, and thus speak in different languages, dialects, or accents. Thus, speech based on a specific piece of text that identifies media content may be articulated to sound in what is almost an infinite number of different ways, depending on the native tongue of a speaker who is being emulated during the text-to-speech conversion. Making speech available in languages, dialects, or accents that sound familiar to any user across the globe is desirable if the product or service that is being offered is to be considered truly international. However, this adds to the challenges in designing automated text-to-speech synthesizers without sacrificing accuracy, quality, and speed.
[0013] Accordingly, an embodiment of the invention may provide a user of portable electronic devices with an audible recording for identifying media content that may be accessible through such devices. The audible recording may be provided for an existing device without having to modify the device, and may be provided at high and variable rates of speed. The audible recording may be provided in an automated fashion that does not require human recording of identifying information. The audible recording may also be provided to users across the globe in languages, dialects, and accents that sound familiar to these users.
[0014] Embodiments of the invention may be achieved using systems and methods for synthesizing text to speech that helps identify content in media assets using sophisticated text-to-speech algorithms. Speech may be selectively synthesized from text strings that are typically associated with, and that identify, the media assets. Portions of these strings may be normalized by substituting certain non-alphabetical characters with their most likely counterparts using, for example, (i) handwritten heuristics derived from a domain-script's knowledge, (ii) text-rewrite rules that are automatically or semi-automatically generated using ‘machine learning’ algorithms, or (iii) statistically trained probabilistic methods, so that they are more easily converted into human sounding speech. Such text strings may also originate in one or more native languages and may need to be converted into one or more other target languages that are familiar to certain users. In order to do so, the text's native language may be determined automatically from an analysis of the text. One way to do this is using N-gram analysis at the word and/or character levels. A first set of phonemes corresponding to the text string in its native language may then be obtained and converted into a second set of phonemes in the target language. Such conversion may be implemented using tables that map phonemes in one language to another according to a set of predetermined rules that may be context sensitive. Once the target phonemes are obtained, they may be used as a basis for providing a high quality, human-sounding rendering of the text string that is spoken in an accent or dialect that is familiar to a user, no matter the native language of the text or the user.
[0015] In order to produce such sophisticated speech at high rates and provide it to users of existing portable electronic devices, the above text-to-speech algorithms may be implemented on a server farm system. Such a system may include several rendering servers having render engines that are dedicated to implement the above algorithms in an efficient manner. The server farm system may be part of a front end that includes storage on which several media assets and their associated synthesized speech are stored, as well as a request processor for receiving and processing one or more requests that result in providing such synthesized speech. The front end may communicate media assets and associated synthesized speech content over a network to host devices that are coupled to portable electronic devices on which the media assets and the synthesized speech may be played back.
[0016] An embodiment is provided for a voice synthesis server farm system comprising: a plurality of rendering servers, wherein each of the plurality of rendering servers comprises at least one render engine that is operable to convert text associated with a media asset into audio, wherein the audio comprises a human-sounding rendering of the text that is spoken in a language of a user regardless of a language in which the text originated.
[0017] Another embodiment is provided for a method for synthesizing speech from content related to a media asset, the method comprising: receiving a request for a rendering of text related to the media asset; and converting the text associated with the media asset into audio, the audio comprising a human-sounding rendering of the text that is spoken in a language of a user regardless of a language in which the text originated.
[0018] Another embodiment is provided for a method for processing requests for synthesized speech, the method comprising: receiving a request for a media asset or a request for speech content identifying the media asset; if a rendering of speech content is available, retrieving and providing the rendering; and if a rendering of speech content is not available, converting text associated with the media asset into audio, the audio comprising a human-sounding rendering of the text that is spoken in a native language of a user regardless of a language in which the text originated.
[0019] Another embodiment is provided for a method for requesting synthesized speech from content related to a media asset, the method comprising: generating a request for a media asset or a request for speech content identifying the media asset; and receiving, in response to the generated request a rendering of speech content, the rendering comprising text associated with the media asset, whereby the text is converted into audio, the audio comprising a human-sounding rendering of the text that is spoken in a language of a user regardless of a language in which the text originated.
Brief Description of the Drawings
[0020] The above and other embodiments of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
[0021] FIG. 1 is an illustrative schematic view of a text-to-speech system in accordance with certain embodiments of the invention;
[0022] FIG. 2 is a flowchart of an illustrative process for generally providing text-to-speech synthesis in accordance with certain embodiments of the invention;
[0023] FIG. 2A is a flowchart of an illustrative process for analyzing and modifying a text string in accordance with certain embodiments of the invention;
[0024] FIG. 3 is a flowchart of an illustrative process for determining the native language of text strings in accordance with certain embodiments of the invention;
[0025] FIG. 4 is a flowchart of an illustrative process for normalizing text strings in accordance with certain embodiments of the invention;
[0026] FIG. 5 is a flowchart of an illustrative process for providing phonemes that may be used to synthesize speech from text strings in accordance with certain embodiments of the invention;
[0027] FIG. 6 is an illustrative block diagram of a render engine in accordance with certain embodiments of the invention;
[0028] FIG. 7 is a flowchart of an illustrative process for providing concatenation of words in a text string in accordance with certain embodiments of the invention; and
[0029] FIG. 8 is a flowchart of an illustrative process for modifying delivery of speech synthesis in accordance with certain embodiments of the invention.
Detailed Description of the Disclosure
[0030] The invention relates to systems and methods for providing speech content that identifies a media asset through speech synthesis. The media asset may be an audio item such a music file, and the speech content may be an audio file that is combined with the media asset and presented before or together with the media asset during playback. The speech content may be generated by extracting metadata associated with and identifying the media asset, and by converting it into speech using sophisticated text-to-speech algorithms that are described below.
[0031] Speech content may be provided by user interaction with an on-line media store where media assets can be browsed, searched, purchased and/or acquired via a computer network. Alternatively, the media assets may be obtained via other sources, such as local copying of a media asset, such as a CD or DVD, a live recording to local memory, a user composition, shared media assets from other sources, radio recordings, or other media assets sources. In the case of a music file, the speech content may include information identifying the artist, performer, composer, title of song/composition, genre, personal preference rating, playlist name, name of album or compilation to which the song/composition pertains, or any combination thereof or of any other metadata that is associated with media content. For example, when the song is played on the media device, the title and/or artist information can be announced in an accent that is familiar to the user before the song begins. The invention may be implemented in numerous ways, including, but not limited to systems, methods, and/or computer readable media.
[0032] Several embodiments of the invention are discussed below with reference to FIGS. 1-8 . However, those skilled in the art will readily appreciate that the detailed description provided herein with respect to these figures is for explanatory purposes and that the invention extends beyond these limited embodiments. For clarity, dotted lines and boxes in these figures represent events or steps that may occur under certain circumstances.
[0033] FIG. 1 is a block diagram of a media system 100 that supports text-to-speech synthesis and speech content provision according to some embodiments of the invention. Media system 100 may include several host devices 102, back end 107, front end 104, and network 106. Each host device 102 may be associated with a user and coupled to one or more portable electronic devices (“PEDs”) 108. PED 108 may be coupled directly or indirectly to the network 106.
[0034] The user of host device 102 may access front end 104 (and optionally back end 107) through network 106. Upon accessing front end 104, the user may be able to acquire digital media assets from front end 104 and request that such media be provided to host device 102. Here, the user can request the digital media assets in order to purchase, preview, or otherwise obtain limited rights to them.
[0035] Front end 104 may include request processor 114, which can receive and process user requests for media assets, as well as storage 124. Storage 124 may include a database in which several media assets are stored, along with synthesized speech content identifying these assets. A media asset and speech content associated with that particular asset may be stored as part of or otherwise associated with the same file. Back end 107 may include rendering farm 126, which functions may include synthesizing speech from the data (e.g., metadata) associated with and identifying the media asset. Rendering farm 126 may also mix the synthesized speech with the media asset so that the combined content may be sent to storage 124. Rendering farm 126 may include one or more rendering servers 136, each of which may include one or multiple instances of render engines 146, details of which are shown in FIG. 6 and discussed further below.
[0036] Host device 102 may interconnect with front end 104 and back end 107 via network 106. Network 106 may be, for example, a data network, such as a global computer network (e.g., the World Wide Web). Network 106 may be a wireless network, a wired network, or any combination of the same.
[0037] Any suitable circuitry, device, system, or combination of these (e.g., a wireless communications infrastructure including communications towers and telecommunications servers) operative to create a communications network may be used to create network 106. Network 106 may be capable of providing communications using any suitable communications protocol. In some embodiments, network 106 may support, for example, traditional telephone lines, cable television, Wi-Fi™ (e.g., an 802.11 protocol), Ethernet, Bluetooth™, high frequency systems (e.g., 900 MHz, 2.4 GHz, and 5.6 GHz communication systems), infrared, transmission control protocol/internet protocol (“TCP/IP”) (e.g., any of the protocols used in each of the TCP/IP layers), hypertext transfer protocol (“HTTP”), BitTorrent™, file transfer protocol (“FTP”), real-time transport protocol (“RTP”), real-time streaming protocol (“RTSP”), secure shell protocol (“SSH”), any other communications protocol, or any combination thereof.
[0038] In some embodiments of the invention, network 106 may support protocols used by wireless and cellular telephones and personal e-mail devices (e.g., an iPhone™ available by Apple Inc. of Cupertino, Calif.). Such protocols can include, for example, GSM, GSM plus EDGE, CDMA, quadband, and other cellular protocols. In another example, a long range communications protocol can include Wi-Fi™ and protocols for placing or receiving calls using voice-over-internet protocols (“VOIP”) or local area network (“LAN”) protocols. In other embodiments, network 106 may support protocols used in wired telephone networks. Host devices 102 may connect to network 106 through a wired and/or wireless manner using bidirectional communications paths 103 and 105.
[0039] Portable electronic device 108 may be coupled to host device 102 in order to provide digital media assets that are present on host device 102 to portable electronic device 108. Portable electronic device 108 can couple to host device 102 over link 110. Link 110 may be a wired link or a wireless link. In certain embodiments, portable electronic device 108 may be a portable media player. The portable media player may be battery-powered and handheld and may be able to play music and/or video content. For example, portable electronic device 108 may be a media player such as any personal digital assistant (“PDA”), music player (e.g., an iPod™ Shuffle, an iPod™ Nano, or an iPod™ Touch available by Apple Inc. of Cupertino, Calif.), a cellular telephone (e.g., an iPhone™), a landline telephone, a personal e-mail or messaging device, or combinations thereof.
[0040] Host device 102 may be any communications and processing device that is capable of storing media that may be accessed through media device 108. For example, host device 102 may be a desktop computer, a laptop computer, a personal computer, or a pocket-sized computer.
[0041] A user can request a digital media asset from front end 104. The user may do so using iTunes™ available from Apple Inc., or any other software that may be run on host device 102 and that can communicate user requests to front end 104 through network 106 using links 103 and 105. In doing so, the request that is communicated may include metadata associated with the desired media asset and from which speech content may be synthesized using front end 104. Alternatively, the user can merely request from front end 104 speech content associated with the media asset. Such a request may be in the form of an explicit request for speech content or may be automatically triggered by a user playing or performing another operation on a media asset that is already stored on host device 102.
[0042] Once request processor 114 receives a request for a media asset or associated speech content, request processor 114 may verify whether the requested media asset and/or associated speech content is available in storage 124. If the requested content is available in storage 124, the media asset and/or associated speech content may be sent to request processor 114, which may relay the requested content to host device 102 through network 106 using links 105 and 103 or to a PED 108 directly. Such an arrangement may avoid duplicative operation and minimize the time that a user has to wait before receiving the desired content.
[0043] If the request was originally for the media asset, then the asset and speech content may be sent as part of a single file, or a package of files associated with each other, whereby the speech content can be mixed into the media content. If the request was originally for only the speech content, then the speech content may be sent through the same path described above. As such, the speech content may be stored together with (i.e., mixed into) the media asset as discussed herein, or it may be merely associated with the media asset (i.e., without being mixed into it) in the database on storage 124.
[0044] As described above, the speech and media contents may be kept separate in certain embodiments (i.e., the speech content may be transmitted in a separate file from the media asset). This arrangement may be desirable when the media asset is readily available on host device 102 and the request made to front end 104 is a request for associated speech content. The speech content may be mixed into the media content as described in commonly-owned, co-pending patent application Ser. No. 11/369,480, filed on Mar. 6, 2006 (now U.S. Published Patent Application No. 2006-0168150), which is hereby incorporated herein in its entirety.
[0045] Mixing the speech and media contents, if such an operation is to occur at all, may take place anywhere within front end 104, on host computer 102, or on portable electronic device 108. Whether or not the speech content is mixed into the media content, the speech content may be in the form of an audio file that is uncompressed (e.g., raw audio). This results in high-quality audio being stored in front end 104 of FIG. 1 . A lossless compression scheme may then be used to transmit the speech content over network 106. The received audio may then be uncompressed at the user end (e.g., on host device 102 or portable electronic device 108). Alternatively, the resulting audio may be stored in a format similar to that used for the media file with which it is associated.
[0046] If the speech content associated with the requested media asset is not available in storage 124, request processor 114 may send the metadata associated with the requested media asset to rendering farm 126 so that rendering farm 126 can synthesize speech therefrom. Once the speech content is synthesized from the metadata in rendering farm 126, the synthesized speech content may be mixed with the corresponding media asset. Such mixing may occur in rendering farm 126 or using other components (not shown) available in front end 104. In this case, request processor 114 may obtain the asset from storage 124 and communicate it to rendering farm or to whatever component is charged with mixing the asset with the synthesized speech content. Alternatively, rendering farm 126, or an other component, may communicate directly with storage 124 in order to obtain the asset with which the synthesized speech is to be mixed. In other embodiments, request processor 114 may be charged with such mixing.
[0047] From the above, it may be seen that speech synthesis may be initiated in response to a specific request from request processor 114 in response to a request received from host device 102. On the other hand, speech synthesis may be initiated in response to continuous addition of media assets onto storage 124 or in response to a request from the operator of front end 104. Such an arrangement may ensure that the resources of rendering farm 126 do not go unused. Moreover, having multiple rendering servers 136 with multiple render engines 146 may avoid any delays in providing synthesized speech content should additional resources be needed in case multiple requests for synthesized speech content are initiated simultaneously. This is especially true as new requests are preferably diverted to low-load servers or engines. In other embodiments of the invention, speech synthesis, or any portion thereof as shown in FIGS. 2-5 and 7-8 or as described further in connection with any of the processes below, may occur at any other device in network 106, on host device 102, or on portable electronic device 108, assuming these devices are equipped with the proper resources to handle such functions. For example, any or all portions shown in FIG. 6 may be incorporated into these devices.
[0048] To ensure that storage 124 does not overflow with content, appropriate techniques may be used to prioritize what content is deleted first and when such content is deleted. For example, content can be deleted on a first-in-first-out basis, or based on the popularity of content, whereby content that is requested with higher frequency may be assigned a higher priority or remain on storage 124 for longer periods of time than content that is requested with less frequency. Such functionality may be implemented using fading memories and time-stamping mechanisms, for example.
[0049] The following figures and description provide additional details, embodiments, and implementations of text-to-speech processes and operations that may be performed on text (e.g., titles, authors, performers, composers, etc.) associated with media assets (e.g., songs, podcasts, movies, television shows, audio books, etc.). Often, the media assets may include audio content, such as a song, and the associated text from which speech may be synthesized may include a title, author, performer, composers, genre, beats per minute, and the like. Nevertheless, as described above, it should be understood that neither the media asset nor the associated text is limited to audio data, and that like processing and operations can be used with other time-varying media types besides music such as podcasts, movies, television shows, and the like, as well as static media such as photographs, electronic mail messages, text documents, and other applications that run on the PED 108 or that may be available via an application store.
[0050] FIG. 2 is a flow diagram of a full text-to-speech conversion process 200 that may be implemented in accordance with certain embodiments of the invention. Each one of the steps in process 200 is described and illustrated in further detail in the description and other figures herein.
[0051] The first step in process 200 is the receipt of the text string to be sythesized into speech starting at step 201. Similarly, at step 203, the target language which represents the language or dialect in which the text string will be vocalized is received. The target language may be determined based on the request by the user for the media content and/or the associated speech content. The target language may or may not be utilized until step 208. For example, the target language may influence how text is normalized at step 204, as discussed further below in connection with FIG. 4 .
[0052] As described above in connection with FIG. 1 , the request that is communicated to rendering farm 126 (from either a user of host device 102 or the operator of front end 104) may include the text string (to be converted or synthesized to speech), which can be in the form of metadata. The same request may also include information from which the target language may be derived. For example, the user may enter the target language as part of the request. Alternatively, the language in which host device 102 (or the specific software and/or servers that handle media requests, such as iTunes™) is configured may be communicated to request processor 114 software. As another example, the target language may be set by the user through preference settings and communicated to front end 104. Alternatively, the target language may be fixed by front end 104 depending on what geographic location is designated to be serviced by front end 104 (i.e., where the request for the media or speech content is generated or received). For example, if a user is interacting with a German store front, request processor 114 may set the target language to be German.
[0053] At step 202 of process 200, the native language of the text string (i.e., the language in which the text string has originated) may be determined. For example, the native language of a text string such as “La Vie En Rose,” which refers to the title of a song, may be determined to be French. Further details on step 202 are provided below in connection with FIG. 3 . At step 204, the text string may be normalized in order to, for example, expand abbreviations so that the text string is more easily synthesized into human sounding speech. For example, text such as “U2,” which refers to the name of an artist (rock music band), would be normalized to be “you two.” Further details on step 204 are provided below in connection with FIG. 4 . Steps 202 and 204 may be performed using any one of render engines 146 of FIG. 1 . More specifically, pre-processor 602 of FIG. 6 may be specifically dedicated to performing steps 202 and/or 204.
[0054] With respect to FIG. 2 , step 202 may occur before step 204. Alternatively, process 200 may begin with step 204, whereby step 202 occurs thereafter. Portions of process 200 may be iterative as denoted by the dotted line arrow, in conjunction with the solid line arrow, between steps 202 and 204. More specifically, steps 202 and 204 may occur several times, one after the other in a cyclical, repetitive manner until the desired result is obtained. The combination of steps 202 and 204 may result in a normalized text string having a known native language or language of origin.
[0055] After steps 202 and 204 of process 200 have occurred, the normalized text string may be used to determine a pronunciation of the text string in the target language at steps 206 and 208. This determination may be implemented using a technique that may be referred to as phoneme mapping, which may be used in conjunction with a table look up. Using this technique, one or more phonemes corresponding to the normalized text may be obtained in the text's native language at step 206. Those obtained phonemes are used to provide pronunciation of the phonemes in the target language at step 208. A phoneme is a minimal sound unit of speech that, when contrasted with another phoneme, affects the naming of words in a particular language. It is typically the smallest unit of sound that, when contrasted with another phoneme, affects the naming of words in a language. For example, the sound of the character “r” in the words “red,” “bring,” or “round” is a phoneme. Further details on steps 206 and 208 are provided below in connection with FIG. 5 .
[0056] It should be noted that certain normalized texts need not need a pronunciation change from one language to another, as indicated by the dotted line arrow bypassing steps 206 and 208. This may be true for text having a native language that corresponds to the target language. Alternatively, a user may wish to always hear text spoken in its native language, or may want to hear text spoken in its native language under certain conditions (e.g., if the native language is a language that is recognized by the user because it is either common or merely a different dialect of the user's native language). Otherwise, the user may specify conditions under which he or she would like to hear a version of the text pronounced in a certain language, accent, dialect, etc. These and other conditions may be specified by the user through preference settings and communicated to front end 104 of FIG. 1 . In situations where a pronunciation change need not take place, steps 202 through 208 may be entirely skipped.
[0057] Other situations may exist in which certain portions of text strings may be recognized by the system and may not, as a result, undergo some or all of steps 202 through 208. Instead, certain programmed rules may dictate how these recognized portions of text ought to be spoken such that when these portions are present, the same speech is rendered without having to undergo natural language detection, normalization, and/or phoneme mapping under certain conditions. For example, rendering farm 126 of FIG. 1 may be programmed to recognize certain text strings that correspond to names of artists/composers, such as “Ce Ce Peniston” and may instruct a composer component 606 of FIG. 6 to output speech according to the correct (or commonly-known) pronunciation of this name. Similarly, with respect to song titles, certain prefixes or suffixes such as “Dance Remix,” “Live,” “Acoustic,” “Version,” and the like may also be recognized and rendered according to predefined rules. This may be one form of selective text-to-speech synthesis. The composer component 606, further described herein, may be a component of render engine 146 (FIG. 1 ) used to output actual speech based on a text string and phonemes, as described herein.
[0058] There may be other forms of selective text-to-speech synthesis that are implemented according to certain embodiments of the invention. For example, certain texts associated with media assets may be lengthy and users may not be interested in hearing a rendering of the entire string. Thus, only selected potions of texts may be synthesized based on certain rules. For example, pre-processor 602 of FIG. 6 may parse through text strings and select certain subsets of text to be synthesized or not to be synthesized. Thus, certain programmed rules may dictate which strings are selected or rejected. Alternatively, such selection may be manually implemented (i.e., such that individuals known as scrubbers may go through strings associated with media assets and decide, while possibly rewriting portions of, the text strings to be synthesized). This may be especially true for subsets of which may be small in nature, such as classical music, when compared to other genres.
[0059] One embodiment of selective text to speech synthesis may be provided for classical music (or other genres of) media assets that filters associated text and/or provides substitutions for certain fields of information. Classical music may be particularly relevant for this embodiment because composer information, which may be classical music's most identifiable aspect, is typically omitted in associated text. As with other types of media assets, classical music is typically associated with name and artist information, however, the name and artist information in the classical music genre is often irrelevant and uninformative.
[0060] The methods and techniques discussed herein with respect to classical music may also be broadly applied to other genres, for example, in the context of selecting certain associated text for use in speech synthesis, identifying or highlighting certain associated text, and other uses. For example, in a hip hop media asset, more than one artist may be listed in its associated text. Techniques described herein may be used to select one or more of the listed artists to be highlighted in a text string for speech synthesis. In another example, for a live music recording, techniques described herein may be used to identify a concert date, concert location, or other information that may be added or substituted in a text string for speech synthesis. Obviously, other genres and combinations of selected information may also use these techniques.
[0061] In a more specific example, a classical music recording may be identified using the following name: “Organ Concerto in B-Flat Major Op. 7, No. 1 (HWV 306): IV. Adagio ad libitum (from Harpsichord Sonata in G minor HHA IV, 17 No. 22, Larghetto).” A second classical music recording may be identified with the following artist: “Bavarian Radio Chorus, Dresden Philharmonic Childrens Chorus, Jan-Hendrik Rootering, June Anderson, Klaus Knig, Leningrad Members of the Kirov Orchestra, Leonard Bernstein, Members of the Berlin Radio Chorus, Members Of The New York Philharmonic, Members of the London Symphony Orchestra, Members of the Orchestre de Paris, Members of the Staatskapelle Dresden, Sarah Walker, Symphonieorchester des Bayerischen Rundfunks & Wolfgang Seeliger.” Although the lengthy name and artist information could be synthesized to speech, it would not be useful to a listener because it provides too much irrelevant information and fails to provide the most useful identifying information (i.e., the composer). In some instances, composer information for classical music media assets is available as associated text. In this case the composer information could be used instead of, or in addition to, name and artist information, for text to speech synthesis. In other scenarios, composer information may be swapped in the field for artist information, or the composer information may simply not be available. In these cases, associated text may be filtered and substituted with other identifying information for use in text to speech synthesis. More particularly, artist and name information may be filtered and substituted with composer information, as shown in process flow 220 of FIG. 2A .
[0062] Process 220 may use an original text string communicated to rendering farm 126 (FIG. 1 ) and processed using a pre-processor 602 (FIG. 6 ) of render engine 146 (FIG. 6 ) to provide a modified text string to synthesizer 604 (FIG. 6 ) and composer component 606 (FIG. 6 ). In some embodiments, process 220 may include selection and filtering criteria based on user preferences, and, in other embodiments, standard algorithms may be applied.
[0063] Turning to FIG. 2A , at step 225, abbreviations in a text string may be normalized and expanded. In particular, name and artist information abbreviations may be expanded. Typical classical music abbreviations include: No., Var., Op., and others. In processing the name in the above example, “Organ Concerto in B-Flat Major Op. 7, No. 1 (HWV 306): IV. Adagio ad libitum (from Harpsichord Sonata in G minor HHA IV, 17 No. 22, Larghetto),” at step 225, the abbreviation for “Op.” may be expanded to “Opus,” and the abbreviations for “No.” may be expanded to “number.” Abbreviation expansion may also involve identifying and expanding numerals in the text string. In addition, normalization of numbers or other abbreviations, or other text may be provided in a target language pronunciation. For example, “No.” may be expanded to number, nombre, numero, etc. Certain numerals may be indicative of a movement. In this case, the number may be expanded to its relevant ordinal and followed by the word “movement.” At step 230, details of the text string may be filtered. Some of the details filtered at step 230 may be considered uninformative or irrelevant details, such as, tempo indications, opus, catalog, or other information may be removed.
[0064] An analysis of the text in the expanded and filtered text string remaining after step 230 may be performed to identify certain relevant details at step 235. For example, the text string may be analyzed to determine an associated composer name. This analysis may be performed by comparing the words in the text string to a list of composers in a look up table. Such a table may be stored in a memory (not shown) located remotely or anywhere in front end 104 (e.g., in one or more render engines 146, rendering servers 136, or anywhere else on rendering farm 126). The table may be routinely updated to include new composers or other details. Identification of a composer or other detail may be provided by comparing a part of, or the entire text string with a list of all or many common works. Such a list may be provided in the table. Comparison of the text string with the list may require a match of some portion of the words in the text string.
[0065] If only one composer is identified as being potentially relevant to the text string, confidence of its accuracy may be determined to be relatively high at step 240. On the other hand, if more than one composer is identified as being potentially relevant, confidence of each identified composer may be determined at step 240 by considering one or more factors. Some of the confidence factors may be based on correlations between composers and titles, other relevant information such as time of creation, location, source, and relative volume of works, or other factors. A specified confidence threshold may be used to evaluate at step 245 whether an identified composer is likely to be accurate. If the confidence of the identified composer exceeds the threshold, a new text string is created at step 250 using the composer information. Composer information may be used in addition to the original text string, or substituted with other text string information, such as name, artist, title, or other information. If the confidence of the identified composer does not meet the threshold at step 245, the original or standard text string may be used at step 255. The text string obtained using process 220 may be used in steps 206 (FIG. 2) and 208 (FIG. 5 ) for speech synthesis.
[0066] Steps 206 and 208 may be performed using any one of render engines 146 of FIG. 1 . More specifically, synthesizer 604 of FIG. 6 may be specifically dedicated to performing steps 206 and/or 208. Synthesizer 604 may be an off-the-shelf synthesizer or may be customized to perform steps 206 and 208. At step 210 of FIG. 2 , the desired speech may be derived from the target phonemes. Step 210 may be performed using any one of render engines 146 of FIG. 1 . More specifically, composer component 606 of FIG. 6 may be specifically dedicated to performing step 210. Alternatively, synthesized speech may be provided at step 210 based on the normalized text, the native phonemes, the target phonemes, or any combination thereof.
[0067] Turning to FIG. 3 , a flow diagram for determining the native language of a text string in accordance with certain embodiments of the invention is shown. FIG. 3 shows in more detail the steps that may be undertaken to complete step 202 of FIG. 2 . Steps 302 through 306 may be performed using any one of render engines 146 of FIG. 1 . More specifically, pre-processor 602 of FIG. 6 may perform one or more of these steps.
[0068] At step 302 of FIG. 3 , the text string may be separated into distinct words. This may be achieved by detecting certain characters that are predefined as boundary points. For example, if a space or a “_” character occurs before or after a specific character sequence, pre-processor 602 may conclude that a particular word that includes the character sequence has begun or ended with the character occurring after or before the space or “_,” thereby treating the specific set as a distinct word. Applying step 302 to the text string “La Vie En Rose” that was mentioned above may result in separating the string into the following words “La,” “Vie,” “En,” and “Rose.”
[0069] In some embodiments, at optional step 304, for each word that is identified in step 302 from the text string, a decision may be made as to whether the word is in vocabulary (i.e., recognized as a known word by the rendering farm). To implement this step, a table that includes a list of words, unigrams, N-grams, character sets or ranges, etc., known in all known languages may be consulted. Such a table may be stored in a memory (not shown) located remotely or anywhere in front end 104 (e.g., in one or more render engines 146, rendering servers 136, or anywhere else on rendering farm 126). The table may be routinely updated to include new words, N-grams, etc.
[0070] If all the words are recognized (i.e., found in the table), then process 202 transitions to step 306 without undergoing N-gram analysis at the character level. Otherwise, an N-gram analysis at the character level may occur at step 304 for each word that is not found in the table. Once step 304 is completed, an N-gram analysis at the word level may occur at step 306. In certain embodiments of the invention, step 304 may be omitted, or step 306 may start before step 304. If a word is not recognized at step 306, an N-gram analysis according to step 304 may be undertaken for that word, before the process of step 306 may continue, for example.
[0071] As can be seen, steps 304 and 306 may involve what may be referred to as an N-gram analysis, which is a process that may be used to deduce the language of origin for a particular word or character sequence using probability-based calculations. Before discussing these steps further, an explanation of what is meant by the term N-gram in the context of the invention is warranted.
[0072] An N-gram is a sequence of words or characters having a length N, where N is an integer (e.g., 1, 2, 3, etc.). If N=1, the N-gram may be referred to as a unigram. If N=2, the N-gram may be referred to as a bigram. If N=3, the N-gram may be referred to as a trigram. N-grams may be considered on a word level or on a character level. On a word level, an N-gram may be a sequence of N words. On a character level, an N-gram may be a sequence of N characters.
[0073] Considering the text string “La Vie En Rose” on a word level, each one of the words “La,” “Vie,” “En,” and “Rose” may be referred to as a unigram. Similarly, each one of groupings “La Vie,” “Vie En,” and “En Rose” may be referred to as a bigram. Finally, each one of groupings “La Vie En” and “Vie En Rose” may be referred to as a trigram. Looking at the same text string on a character level, each one of “V,” “i,” and “e” within the word “Vie” may be referred to as a unigram. Similarly, each one of groupings “Vi” and “ie” may be referred to as a bigram. Finally, “Vie” may be referred to as a trigram.
[0074] At step 304, an N-gram analysis may be conducted on a character level for each word that is not in the aforementioned table. For a particular word that is not in the table, the probability of occurrence of the N-grams that pertain to the word may be determined in each known language. Preferably, a second table that includes probabilities of occurrence of any N-gram in all known languages may be consulted. The table may include letters from alphabets of all known languages and may be separate from, or part of, the first table mentioned above. For each language, the probabilities of occurrence of all possible N-grams making up the word may be summed in order to calculate a score that may be associated with that language. The score calculated for each language may be used as the probability of occurrence of the word in a particular language in step 306. Alternatively, the language that is associated with the highest calculated score may be the one that is determined to be the native language of the word. The latter is especially true if the text string consists of a single word.
[0075] For example, if one were to assume that the first table does not include the word “vie,” then the probability of occurrence of all possible unigrams, bigrams, and trigrams pertaining to the word and/or any combination of the same may be calculated for English, French, and any or all other known languages. The following demonstrates such a calculation. However, the following uses probabilities that are completely fabricated for the sake of demonstration. For example, assuming that the probabilities of occurrence of trigram “vie” in English and in French are 0.2 and 0.4, respectively, then it may be determined that the probability of occurrence of the word “vie” in English is 0.2 and that the probability of occurrence of the word “vie” in French is 0.4 in order to proceed with step 306 under a first scenario. Alternatively, it may be preliminarily deduced that the native language of the word “vie” is French because the probability in French is higher than in English under a second scenario.
[0076] Similarly, assuming that the probabilities of occurrence of bigrams “vi” and “ie” in English are 0.2 and 0.15, respectively, and that the probabilities of occurrence of those same bigrams in French are 0.1 and 0.3, respectively, then it may be determined that the probability of occurrence of the word “vie” in English is the sum, the average, or any other weighted combination, of 0.2 and 0.15, and that the probability of occurrence of the word “vie” in French is the sum, the average, or any other weighted combination, of 0.1 and 0.3 in order to proceed with step 306 under a first scenario. Alternatively, it may be preliminarily deduced that the native language of the word “vie” is French because the sum of the probabilities in French (i.e., 0.4) is higher than the sum of the probabilities in English (i.e., 0.35) under a second scenario.
[0077] Similarly, assuming that the probabilities of occurrence of unigrams “v,” “i,” and “e” in English are 0.05, 0.6, and 0.75, respectively, and that the probabilities of occurrence of those same unigrams in French are 0.1, 0.6, and 0.6, respectively, then it may be determined that the probability of occurrence of the word “vie” in English is the sum, the average, or any other weighted combination, of 0.05, 0.6, and 0.75, and that the probability of occurrence of the word “vie” in French is the sum, the average, or any other weighted combination, of 0.1, 0.6, and 0.6 in order to proceed with step 306 under a first scenario. Alternatively, it may be preliminarily deduced that the native language of the word “vie” is English because the sum of the probabilities in English (i.e., 1.4) is higher than the sum of the probabilities in French (i.e., 1.3) under a second scenario.
[0078] Instead of conducting a single N-gram analysis (i.e., either a unigram, a bigram, or a trigram analysis), two or more N-gram analyses may be conducted and the results may be combined in order to deduce the probabilities of occurrence in certain languages (under the first scenario) or the native language (under the second scenario). More specifically, if a unigram analysis, a bigram analysis, and a trigram analysis are all conducted, each of these N-gram sums yield a particular score for a particular language. These scores may be added, averaged, or weighted for each language. Under the first scenario, the final score for each language may be considered to be the probability of occurrence of the word in that language. Under the second scenario, the language corresponding to the highest final score may be deduced as being the native language for the word. The following exemplifies and details this process.
[0079] In the above example, the scores yielded using a trigram analysis of the word “vie” are 0.2 and 0.4 for English and French, respectively. Similarly, the scores yielded using a bigram analysis of the same word are 0.35 (i.e., 0.2+0.15) and 0.4 (i.e., 0.1+0.3) for English and French, respectively. Finally, the scores yielded using a unigram analysis of the same word are 1.4 (i.e., 0.05+0.6+0.75) and 1.3 (i.e., 0.1+0.6+0.6) for English and French, respectively. Thus, the final score associated with English may be determined to be 1.95 (i.e., 0.2+0.35+1.4), whereas the final score associated with French may be determined to be 2.1 (i.e., 0.4+0.4+1.3) if the scores are simply added. Alternatively, if a particular N-gram analysis is considered to be more reliable, then the individual scores may be weighted in favor of the score calculated using that N-gram.
[0080] Similarly, to come to a final determination regarding native language under any one of the second scenarios, the more common preliminary deduction may be adopted. In the above example, it may deduced that the native language of the word “vie” may be French because two preliminary deductions have favored French while only one preliminary deduction has favored English under the second scenarios. Alternatively, the scores calculated for each language from each N-gram analysis under the second scenarios may be weighted and added such that the language with the highest weighted score may be chosen. As yet another alternative, a single N-gram analysis, such as a bigram or a trigram analysis, may be used and the language with the highest score may be adopted as the language of origin.
[0081] At step 306, N-gram analysis may be conducted on a word level. In order to analyze the text string at step 306 on a word level, the first table that is consulted at step 304 may also be consulted at step 306. In addition to including a list of known words, the first table may also include the probability of occurrence of each of these words in each known language. As discussed above in connection with the first scenarios that may be adopted at step 304, in case a word is not found in the first table, the calculated probabilities of occurrence of a word in several languages may be used in connection with the N-gram analysis of step 306.
[0082] In order to determine the native language of the text string “La Vie En Rose” at step 306, the probability of occurrence of some or all possible unigrams, bigrams, trigrams, and/or any combination of the same may be calculated for English, French, and any or all other known languages on a word level. The following demonstrates such a calculation in order to determine the native language of the text string “La Vie En Rose.” However, the following uses probabilities that are completely fabricated for the sake of demonstration. For example, assuming that the probabilities of occurrence of trigram “La Vie En” in English and in French are 0.01 and 0.7 respectively, then it may be preliminarily deduced that the native language of the text string “La Vie En Rose” is French because the probability in French is higher than in English.
[0083] Similarly, assuming that the probabilities of occurrence of bigrams “La Vie,” “Vie En,” and “En Rose” in English are 0.02, 0.01, and 0.1, respectively, and that the probabilities of occurrence of those same bigrams in French are 0.4, 0.3, and 0.5, respectively, then it may be preliminarily deduced that the native language of the text string “La Vie En Rose” is French because the sum of the probabilities in French (i.e., 1.2) is higher than the sum of the probabilities in English (i.e., 0.13).
[0084] Similarly, assuming that the probabilities of occurrence of unigrams “La,” “Vie,” “En,” and “Rose” in English are 0.1, 0.2, 0.05, and 0.6, respectively, and that the probabilities of occurrence of those same unigrams in French are 0.6, 0.3, 0.2, and 0.4, respectively, then it may be preliminarily deduced that the native language of the text string “La Vie En Rose” is French because the sum of the probabilities in French (i.e., 1.5) is higher than the sum of the probabilities in English (i.e., 0.95).
[0085] In order to come to a final determination regarding native language at step 306, the more common preliminary deduction may be adopted. In the above example, it may deduced that the native language of the text string “La Vie En Rose” may be French because all three preliminary deductions have favored French. Alternatively, a single N-gram analysis such as a unigram, a bigram, or a trigram analysis may be used and the language with the highest score may be adopted as the native language. As yet another alternative, the scores calculated for each language from each N-gram analysis may be weighted and added such that the language with the highest weighted score may be chosen. In other words, instead of conducting a single N-gram analysis (i.e., either a unigram, a bigram, or a trigram analysis), two or more N-gram analyses may be conducted and the results may be combined in order to deduce the natural language. More specifically, if a unigram analysis, a bigram analysis, and a trigram analysis are all conducted, each of these N-gram sums yield a particular score for a particular language. These scores may be added, averaged, or weighted for each language, and the language corresponding to the highest final score may be deduced as being the natural language for the text string. The following exemplifies and details this process.
[0086] In the above example, the scores yielded using a trigram analysis of the text string “La Vie En Rose” are 0.01 and 0.7 for English and French, respectively. Similarly, the scores yielded using a bigram analysis of the same text string are 0.13 (i.e., 0.02+0.01+0.1) and 1.2 (i.e., 0.4+0.3+0.5) for English and French, respectively. Finally, the scores yielded using a unigram analysis of the same text string are 0.95 (i.e., 0.1+0.2+0.05+0.6) and 1.5 (i.e., 0.6+0.3+0.2+0.4) for English and French, respectively. Thus, the final score associated with English may be determined to be 1.09 (i.e., 0.01+0.13+0.95), whereas the final score associated with French may be determined to be 3.4 (i.e., 0.7+1.2+1.5) if the scores are simply added. Therefore, it may be finally deduced that the natural language of the text string “La Vie En Rose” is French because the final score in French is higher than the final score in English.
[0087] Alternatively, if a particular N-gram analysis is considered to be more reliable, then the individual scores may be weighted in favor of the score calculated using that N-gram. Optimum weights may be generated and routinely updated. For example, if trigrams are weighed twice as much as unigrams and bigrams, then the final score associated with English may be determined to be 1.1 (i.e., 2*0.01+0.13+0.95), whereas the final score associated with French may be determined to be 4.1 (i.e., 2*0.7+1.2+1.5). Again, it may therefore be finally deduced that the natural language of the text string “La Vie En Rose” is French because the final score in French is higher than the final score in English.
[0088] Depending on the nature or category of the text string, the probabilities of occurrence of N-grams used in the calculations of steps 304 and 306 may vary. For example, if the text string pertains to a music file, there may be a particular set of probabilities to be used if the text string represents a song/composition title. This set may be different than another set that is used if the text string represents the artist, performer, or composer. Thus the probability set used during N-gram analysis may depend on the type of metadata associated with media content.
[0089] Language may also be determined by analysis of a character set or range of characters in a text string, for example, when there are multiple languages in a text string.
[0090] Turning to FIG. 4 , a flow diagram for normalizing the text string in accordance with certain embodiments of the invention is shown. Text normalization may be implemented so that the text string may be more easily converted into human sounding speech. For example, text string normalization may be used to expand abbreviations. FIG. 4 shows in more detail the steps that may be undertaken to complete step 204 of FIG. 2 . Steps 402 through 410 may be performed using any one of render engines 146 of FIG. 1 . More specifically, pre-processor 602 of FIG. 6 may perform these steps.
[0091] At step 402 of FIG. 4 , the text string may be analyzed in order to determine whether characters other than alphabetical characters exist in the text string. Such characters, which may be referred to as non-alphabetical characters, may be numeric characters or any other characters, such as punctuation marks or symbols that are not recognized as letters in any alphabet of the known languages. Step 402 may also include separating the text string into distinct words as specified in connection with step 302 of FIG. 3 .
[0092] For each non-alphabetical character identified at step 402, a determination may be made at step 404 as to what potential alphabetical character or string of characters may correspond to the non-alphabetical character. To do this, a lookup table that includes a list of non-alphabetical characters may be consulted. Such a table may include a list of alphabetical characters or string of characters that are known to potentially correspond to each non-alphabetical character. Such a table may be stored in a memory (not shown) located remotely or anywhere in front end 104 (e.g., in one or more render engines 146, rendering servers 136, or anywhere else on rendering farm 126). The table may be routinely updated to include new alphabetical character(s) that potentially correspond to non-alphabetic characters. In addition, a context-sensitive analysis for non-alphabetical characters may be used. For example, a dollar sign “$” in “$0.99” and “$hort” may be associated with the term “dollar(s)” when used with numbers, or with “S” when used in conjunction with letters. A table look up may be used for such context-sensitive analysis, or algorithms, or other methods.
[0093] Each alphabetical character or set of characters that are identified as potentially corresponding to the non-alphabetical character identified at step 402 may be tested at step 406. More specifically, the non-alphabetical character identified in a word at step 402 may be substituted for one corresponding alphabetical character or set of characters. A decision may be made as to whether the modified word (or test word) that now includes only alphabetical characters may be found in a vocabulary list at step 407. To implement step 407, a table such as the table discussed in connection with step 302, or any other appropriate table, may be consulted in order to determine whether the modified word is recognized as a known word in any known language. If there is one match of the test word with the vocabulary list, the matched word may be used in place of the original word.
[0094] If the test word matches more than one word in the vocabulary list, the table may also include probabilities of occurrence of known words in each known language. The substitute character(s) that yield a modified word having the highest probability of occurrence in any language may be chosen at step 408 as the most likely alphabetical character(s) that correspond to the non-alphabetical character identified at step 402. In other words, the test string having the highest probability of occurrence may be substituted for the original text string. If the unmodified word contains more than one non-alphabetical character, then all possible combinations of alphabetical characters corresponding to the one or more non-alphabetical characters may be tested at step 406 by substituting all non-alphabetical characters in a word, and the most likely substitute characters may be determined at step 408 based on which resulting modified word has the highest probability of occurrence.
[0095] In some instances, a test word or the modified text string may not match any words in the vocabulary at step 407. When this occurs, agglomeration and/or concatenation techniques may be used to identify the word. More specifically, at step 412, the test word may be analyzed to determine whether it matches any combination of words, such as a pair of words, in the vocabulary list. If a match is found, a determination of the likelihood of the match may be made at step 408. If more than one match is found, the table may be consulted for data indicating highest probability of occurrence of the words individually or in combination at step 408. At step 410, the most likely alphabetical character or set of characters may be substituted for the non-alphabetical character in the text string at step 410. The phonemes for the matched words may be substituted as described at step 208. Techniques for selectively stressing the phonemes and words may be used, such as those described in connection with process 700 (FIG. 7 ), as appropriate.
[0096] If no match is found at step 412 between the test word and any agglomeration or concatenation of terms in the vocabulary list, at step 414, the original text string may be used, or the non-alphabetical character word may be removed. This may result in the original text string being synthesized into speech pronouncing the symbol or non-alphabetical character, or having a silent segment.
[0097] In some embodiments of the invention, the native language of the text string, as determined at step 202 may influence which substitute character(s) are selected at step 408. Similarly, the target language may additionally or alternatively influence which substitute character(s) may be picked at step 408. For example, if a word such as “n.” (e.g., which may be known to correspond to an abbreviation of a number) is found in a text string, characters “umber” or “umero” may be identified at step 404 as likely substitute characters in order to yield the word “number” in English or the word “numero” in Italian. The substitute characters that are ultimately selected at step 408 may be based on whether the native or target language is determined to be English or Italian. As another example, if a numerical character such as “3” is found in a text string, characters “three,” “drei,” “trois,” and “tres” may be identified at step 404 as likely substitute characters in English, German, French, and Spanish, respectively. The substitute characters that are ultimately selected at step 408 may be based on whether the native or target language is any one of these languages.
[0098] At step 410, the non-alphabetical character identified at step 402 may be replaced with the substitute character(s) chosen at step 408. Steps 402 through 410 may be repeated until there are no more non-alphabetical characters remaining in the text string. Some non-alphabetical characters may be unique to certain languages and, as such, may have a single character or set of alphabetical characters in the table that are known to correspond to the particular non-alphabetical character. In such a situation, steps 406 and 408 may be skipped and the single character or set of characters may be substituted for the non-alphabetical character at step 410.
[0099] The following is an example that demonstrates how the text string “P!NK” may be normalized in accordance with process 204 as follows. Non-alphabetical character “!” may be detected at step 402. At step 404, a lookup table operation may yield two potential alphabetical characters “I” and “L” as corresponding to non-alphabetical character “!”—and at steps 406-408, testing each of the potential corresponding characters may reveal that the word “PINK” has a higher likelihood of occurrence than the word “PLNK” in a known language. Thus, the most likely alphabetical character(s) that correspond to non-alphabetical character “!” is chosen as “I,” and the text string “P!NK” may be replaced by text string “PINK” for further processing. If a non-alphabetical character is not recognized at step 404 (e.g., there is no entry corresponding to the character in the table), it may be replaced with some character which, when synthesized into speech, is of a short duration, as opposed to replaced with nothing, which may result in a segment of silence.
[0100] In another example, the text string “H8PRIUS” may be normalized in accordance with process 204 as follows. Non-alphabetical character “8” may be detected at step 402. At step 404, a lookup table operation may yield two potential alphabetical characters “ATE” and “EIGHT” as corresponding to non-alphabetical character “8”—and at steps 406 and 407, testing each of the potential corresponding characters “HATEPRIUS” and “HEIGHTPRIUS” may reveal that neither word is found in the vocabulary list. At step 412, agglomeration and/or concatenation techniques are applied to the test strings “HATEPRIUS” and “HEIGHTPRIUS” to determine whether the test strings match any combination of words in the vocabulary list. This may be accomplished by splitting the test string into multiple segments to find a match, such as “HA TEPRIUS,” “HAT EPRIUS,” “HATE PRIUS,” “HATEP RIUS,” “HAT EPRI US,” “HATEP RIUS,” “HE IGHT PRIUS,” etc. Other techniques may also be used. Matches may be found in the vocabulary list for “HATE PRIUS” and “HEIGHT PRIUS.” At step 408, the word pairs “HATE PRIUS” and “HEIGHT PRIUS” may be analyzed to determine the likelihood of correspondence of those words alone or in combination with the original text string by consulting a table. For example, a comparison of the sound of the number “8” may be made with the words “HATE” and “HEIGHT” to identify a likelihood of correspondence. Since “HATE” rhymes with “8,” the agglomeration of words “HATE PRIUS” may be determined to be the most likely word pair to correspond to “H8PRIUS.” The words (and phonemes for) “HATE PRIUS” may then be substituted at step 410 for “H8PRIUS.”
[0101] It is worth noting that, for the particular example provided above, it may be more logical to implement normalization step 204 before natural language detection step 202 in process 200. However, in other instances, it may be more logical to undergo step 202 before step 204. In yet other instances, process 200 may step through steps 202 and 204 before again going through step 202. This may help demonstrate why process 200 may be iterative in part, as mentioned above.
[0102] Turning to FIG. 5 , a flow diagram for performing a process 208, which may be referred to as phoneme mapping, is shown. Obtaining the native phonemes is one of the steps required to implement phoneme mapping. As discussed in connection with FIG. 2 , the one or more phonemes that correspond to the text string in the text's native language may be obtained at step 206. More specifically, at step 502 of FIG. 5 , which may correspond to step 206 of FIG. 2 , a first native phoneme may be obtained for the text string. A pronunciation for that phoneme is subsequently mapped into a pronunciation for a phoneme in the target language through steps 504 and 506 according to certain embodiments of the invention. Alternatively, a pronunciation for phonemes may be associated and obtained via a look up table. Steps 504 and 506 of FIG. 5 show in more detail the different processes that may be undertaken to complete step 208 of FIG. 2 , for example. In other words, steps 504 and 506 may correspond to step 208. Steps 502 through 506 may be performed using any one of render engines 146 of FIG. 1 . More specifically, synthesizer 604 of FIG. 6 may perform these steps.
[0103] At step 502 of FIG. 5 , a first native phoneme corresponding to the text string may be obtained in the text's native language. As process 208 is repeated, all native phonemes of the text string may be obtained. As specified above, a phoneme is a minimal sound unit of speech that, when contrasted with another phoneme, affects the naming of words in a particular language. For example, if the native language of text string “schul” is determined to be German, then the phonemes obtained at step 206 may be “Sh,” “UH,” and “LX.” Thus, the phonemes obtained at each instance of step 502 may be first phoneme “Sh,” second phoneme “UH,” and third phoneme “LX.”
[0104] In addition to the actual phonemes that may be obtained for the text string, markup information related to the text string may also be obtained at step 502. Such markup information may include syllable boundaries, stress (i.e., pitch accent), prosodic annotation or part of speech, and the like. Such information may be used to guide the mapping of phonemes between languages as discussed further below.
[0105] For the native phoneme obtained at step 502, a determination may be made at step 504 as to what potential phoneme(s) in the target language may correspond to it. To do this, a lookup table mapping phonemes in the native language to phonemes in the target language according to certain rules may be consulted. One table may exist for any given pair of languages or dialects. For the purposes of the invention, a different dialect of the same language may be treated as a separate language. For example, while there may be a table mapping English phonemes (e.g., phonemes in American English) to Italian phonemes and vice versa, other tables may exist mapping British English phonemes to American English phonemes and vice versa. All such tables may be stored in a database on a memory (not shown) located remotely or anywhere in front end 104 (e.g., in one or more render engines 146, rendering servers 136, or anywhere else on rendering farm 126). These table may be routinely updated to include new phonemes in all languages.
[0106] An exemplary table for a given pair of languages may include a list of all phonemes known in a first language under a first column, as well as a list of all phonemes known in a second language under a second column. Each phoneme from the first column may map to one or more phonemes from the second column according to certain rules. Choosing the first language as the native language and the second language as the target language may call up a table from which any phoneme from the first column in the native language may be mapped to one or more phonemes from the second column in the target language.
[0107] For example, if it is desired to synthesize the text string “schul” (whose native language was determined to be German) such that the resulting speech is vocalized in English (i.e., the target language is set to English), then a table mapping German phonemes to English phonemes may be called up at step 504. The German phoneme “UH” obtained for this text string, for example, may map to a single English phoneme “UW” at step 504.
[0108] If only one target phoneme is identified at step 504, then that sole target phoneme may be selected as the target phoneme corresponding to the native phoneme obtained at step 502. Otherwise, if there is more than one target phoneme to which the native phoneme may map, then the most likely target phoneme may be identified at step 506 and selected as the target phoneme that corresponds to the native phoneme obtained at step 502.
[0109] In certain embodiments, the most likely target phoneme may be selected based on the rules discussed above that govern how phonemes in one language may map to phonemes in other language within a table. Such rules may be based on the placement of the native phoneme within a syllable, word, or neighboring words within the text string as shown in 516, the word or syllable stress related to the phoneme as shown in 526, any other markup information obtained at step 502, or any combination of the same. Alternatively, statistical analysis may be used to map to the target phoneme as shown in 536, heuristics may be used to correct an output for exceptions, such as idioms or special cases, or using any other appropriate method. If a target phoneme is not found at step 504, then the closest phoneme may be picked from the table. Alternatively, phoneme mapping at step 506 may be implemented as described in commonly-owned U.S. Pat. Nos. 6,122,616, 5,878,396, and 5,860,064, issued on Sep. 19, 2000, Mar. 2, 1999, and Jan. 12, 1999, respectively, each of which are hereby incorporated by reference herein in their entireties.
[0110] Repeating steps 502 through 506 for the entire text string (e.g., for each word in the text string) may yield target phonemes that can dictate how the text string is to be vocalized in the target language. This output may be fed to composer component 606 of FIG. 6 , which in turn may provide the actual speech as if it were spoken by a person whose native language is the target language. Additional processing to make the speech sound more authentic or have it be perceived as more pleasant by users, or, alternatively, to blend it better with the media content, may be implemented. Such processing may include dynamics compression, reverberation, de-essing, level matching, equalizing, and/or adding any other suitable effects. Such speech may be stored in a format and provided to users through the system described in conjunction with FIG. 1 . The synthesized speech may be provided in accordance with the techniques described in commonly-owned, co-pending patent application Ser. No. 10/981,993, filed on Nov. 4, 2004 (now U.S. Published Patent Application No. 2006/0095848), and in commonly-owned, co-pending patent application Ser. No. 11/369,480, filed on Mar. 6, 2006 (now U.S. Published Patent Application No. 2006-0168150), each of which is mentioned above.
[0111] Additional processing for speech synthesis may also be provided by render engine 146 (FIG. 6 ) according to the process 700 shown in FIG. 7 . Process 700 may be designed to enhance synthesized speech flow so that a concatenation of words, or phrases may be synthesized with a connector to have a natural flow. For example, associated content for a media asset song “1979” by the “Smashing Pumpkins” may be synthesized to speech to include the song title “1979” and “Smashing Pumpkins.” The connectors words “by the” may be inserted between the song and artist. In another example, associated content for “Borderline” by “Madonna” may be synthesized using the connector term “by.” In addition, the connector word “by” may be synthesized in a selected manner that enhances speech flow between the concatenated words and phrases.
[0112] Process 700 may be performed using processing of associated text via pre-processor 602 (FIG. 6 ). Processed text may be synthesized to speech using synthesizer 604 (FIG. 6 ) and composer component 606 (FIG. 6 ). Optionally, functions provided by synthesizer 604 (FIG. 6 ) and composer component 606 (FIG. 6 ) are provided by one integrated component. In some embodiments, process 700 may be performed prior to step 210 (FIG. 2 ) so that a complete text string is synthesized. In other embodiments, process 700 may be provided after step 210 to connect elements of synthesized speech.
[0113] Turning to FIG. 7 , a phoneme for a text string of at least two words to be concatenated may be obtained at step 720. For example, phonemes for associated text of a media asset name and artist may be obtained for concatenation in delivery as synthesized speech. To select a connector term for insertion between the name and artist word(s), a last letter (or last syllable) of the phoneme for the song name may be identified at step 730. Also at step 730, a first letter (or first syllable) of the phoneme for the artist may be identified. Using the example above, for the song name “1979,” the last letter “E” (or syllable) for the phoneme for the last word “nine” is identified, together with the first letter “S” (or first syllable) for the artist “Smashing Pumpkins.”
[0114] One or more connector terms may be selected at step 740 based on the identified letters (or syllables) by consulting a table and comparing the letters to a list of letters and associated phonemes in the table. Such a table may be stored in a memory (not shown) located remotely or anywhere in front end 104 (e.g., in one or more render engines 146, rendering servers 136, or anywhere else on rendering farm 126). The table may be routinely updated to include new information or other details. In addition, a version of the selected connector term may be identified by consulting the table. For example, “by” may be pronounced in several ways, one of which may sound more natural when inserted between the concatenated terms.
[0115] The connector term and relevant version of the connector term may be inserted in a modified text string at step 750 between the concatenated words. The modified text string may be delivered to the composer component 606 (FIG. 6 ) for speech synthesis.
[0116] The systems and methods described herein may be used to provide text to speech synthesis for delivering information about media assets to a user. In use, the speech synthesis may be provided in addition to, or instead of, visual content information that may be provided using a graphical user interface in a portable electronic device. Delivery of the synthesized speech may be customized according to a user's preference, and may also be provided according to certain rules. For example, a user may select user preferences that may be related to certain fields of information to be delivered (e.g., artist information only), rate of delivery, language, voice type, skipping repeating words, and other preferences. Such selection may be made by the user via the PED 108 (FIG. 1 ) directly, or via a host device 102 (FIG. 1 ). Such types of selections may also be automatically matched and configured to a particular user according to the process 800 shown in FIG. 8 .
[0117] Process 800 may be implemented on a PED 108 using programming and processors on the PED. As shown, a speech synthesis segment may be obtained at step 820 by PED 108. The speech synthesis segment may be obtained via delivery from the front end 104 (FIG. 1 ) to the PED 108 (FIG. 1 ) via network 106 (FIG. 1 ) and in some instances, from host device 102 (FIG. 1 ). In general, speech synthesis segments may be associated with a media asset that may be concurrently delivered to the PED 108 (FIG. 1 ).
[0118] The PED may include programming capable of determining whether its user is listening to speech synthesis at step 830. For example, the PED may determine that selections are made by a user to listen to speech synthesis. In particular, a user may actively select speech synthesis delivery, or not actively omit speech synthesis delivery. User inputs may also be determined at step 840. User inputs may include, for example, skipping speech synthesis, fast forwarding through speech synthesis, or any other input. These inputs may be used to determine an appropriate segment delivery type. For example, if a user is fast forwarding through speech synthesized information, the rate of the delivery of speech synthesis may be increased. Increasing a rate of delivery may be performed using faster speech rates, shortening breaks or spaces between words, truncating phrases, or other techniques. In other embodiments, if the user fast forwards through speech synthesized information, it may be omitted for subsequent media items, or the next time the particular media item is presented to the user.
[0119] At step 850 repetitive text may be identified in the segment. For example, if a word has been used recently (such as in a prior or preceding artist in a collection of songs by the artist), the repeated word may be identified. In some embodiments, repeated words may be omitted from a segment delivered to a user. In other embodiments, a repeated word may be presented in a segment at a higher rate of speech, for example, using faster speech patterns and/or shorter breaks between words. In another embodiment, repeated phrases may be truncated.
[0120] Based on the user's use of speech synthesis identified at step 830, user's inputs determined at step 840, and repetitive text identified at step 850, a customized segment may be delivered to a user at step 860. User-customized segments may include a delivered segment that omits repeated words, changes a rate of delivery or playback of the segment, truncating phrases, or other changes. Combinations of changes may be made based on the user's use and inputs and segment terms, as appropriate.
[0121] As can be seen from the above, a number of systems and methods may be used alone or in combination for synthesizing speech from text using sophisticated text-to-speech algorithms. In the context of media content, such text may be any metadata associated with the media content that may be requested by users. The synthesized speech may therefore act as audible means that may help identify the media content to users. In addition, such speech may be rendered in high quality such that it sounds as if it were spoken in normal human language in an accent or dialect that is familiar to a user, no matter the native language of the text or the user. Not only are these algorithms efficient, they may be implemented on a server farm so as to be able to synthesize speech at high rates and provide them to users of existing portable electronic devices without having to modify these devices. Thus, the rate at which synthesized speech may be provided can be about one-twentieth of real time (i.e., a fraction of the length of the time a normal speaker would take to read the text that is desired to be converted).
[0122] Various configurations described herein may be combined without departing from the invention. The above-described embodiments of the invention are presented for purposes of illustration and not of limitation. The invention also can take many forms other than those explicitly described herein, and can be improved to render more accurate speech. For example, users may be given the opportunity to provide feedback to enable the server farm or front end operator to provide more accurate rendering of speech. For example, users may be able to provide feedback regarding what they believe to be the language of origin of particular text, the correct expansion of certain abbreviations in the text, and the desired pronunciation of certain words or characters in the text. Such feedback may be used to populate the various tables discussed above, override the different rules or steps described, and the like.
[0123] Accordingly, it is emphasized that the invention is not limited to the explicitly disclosed systems and methods, but is intended to include variations to and modifications thereof which are within the spirit of the following claims.
Claims
What is claimed is:
1. A method for synthesizing speech from content related to a media asset, the method comprising:
receiving a request for a rendering of text associated with the media asset; and
converting the text associated with the media asset into speech, the speech comprising a rendering of the text that is spoken in a native language of the text and customized with an accent associated with a user, wherein converting the text associated with the media asset into speech further comprises:
obtaining a plurality of native phonemes of the text;
determining the accent associated the user;
mapping the plurality of native phonemes to a plurality of target phonemes associated with the accent; and
generating the speech using the plurality of target phonemes.
2. The method of claim 1 wherein the text comprises metadata related to the media asset.
3. The method of claim 1 wherein the media asset is a music file, and wherein the text comprises any combination of artist, performer, composer, title, playlist name, name of album or compilation, and audio book chapter.
4. The method of claim 1, further comprising:
determining the native language of the text based on metadata associated with the media asset.
5. The method of claim 1, further comprising:
combining the speech with the media asset in a single media file; and
providing the single media file to a client device.
6. The method of claim 1, further comprising:
substituting each of one or more non-alphabet characters in the text with respective one or more alphabet characters before the converting.
7. The method of claim 1, further comprising:
extracting portions of the text from metadata associated with the media asset; and
before the converting, inserting one or more connector terms into the extracted portions to obtain the text associated with the media asset.
8. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors, cause the one or more processors to:
receive a request for a rendering of text associated with a media asset; and
convert the text associated with the media asset into speech, the speech comprising a rendering of the text that is spoken in a native language of the text and customized with an accent associated with a user, wherein converting the text associated with the media asset into speech further comprises:
obtaining a plurality of native phonemes of the text;
determining the accent associated the user;
mapping the plurality of native phonemes to a plurality of target phonemes associated with the accent; and
generating the speech using the plurality of target phonemes.
9. The non-transitory computer-readable storage medium of claim 8 wherein the text comprises metadata related to the media asset.
10. The non-transitory computer-readable storage medium of claim 8 wherein the media asset is a music file, and wherein the text comprises any combination of artist, performer, composer, title, playlist name, name of album or compilation, and audio book chapter.
11. The non-transitory computer-readable storage medium of claim 8, wherein the instructions further cause the one or more processors to:
determine the native language of the text based on metadata associated with the media asset.
12. The non-transitory computer-readable storage medium of claim 8, wherein the instructions further cause the one or more processors to:
combine the speech with the media asset in a single media file; and
provide the single media file to a client device.
13. The non-transitory computer-readable storage medium of claim 8, wherein the instructions further cause the one or more processors to:
substitute each of one or more non-alphabet characters in the text with respective one or more alphabet characters before the converting.
14. The non-transitory computer-readable storage medium of claim 8, wherein the instructions further cause the one or more processors to:
extract portions of the text from metadata associated with the media asset; and
before the converting, insert one or more connector terms into the extracted portions to obtain the text associated with the media asset.
15. A system, comprising:
one or more processors; and
memory, the memory storing one or more programs, the one or more programs comprising instructions, which when executed by the one or more processors, cause the one or more processors to:
receive a request for a rendering of text associated with a media asset; and
convert the text associated with the media asset into speech, the speech comprising a rendering of the text that is spoken in a native language of the text and customized with an accent associated with a user, wherein converting the text associated with the media asset into speech further comprises:
obtaining a plurality of native phonemes of the text;
determining the accent associated the user;
mapping the plurality of native phonemes to a plurality of target phonemes associated with the accent; and
generating the speech using the plurality of target phonemes.
16. The system of claim 15 wherein the text comprises metadata related to the media asset.
17. The system of claim 15 wherein the media asset is a music file, and wherein the text comprises any combination of artist, performer, composer, title, playlist name, name of album or compilation, and audio book chapter.
18. The system of claim 15, wherein the instructions further cause the one or more processors to:
determine the native language of the text based on metadata associated with the media asset.
19. The system of claim 15, wherein the instructions further cause the one or more processors to:
combine the speech with the media asset in a single media file; and
provide the single media file to a client device.
20. The system of claim 15, wherein the instructions further cause the one or more processors to:
substitute each of one or more non-alphabet characters in the text with respective one or more alphabet characters before the converting.
21. The system of claim 15, wherein the instructions further cause the one or more processors to:
extract portions of the text from metadata associated with the media asset; and
before the converting, insert one or more connector terms into the extracted portions to obtain the text associated with the media asset.
Patent Citations (336)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4513435(A) | 1985-04-01 | Sakoe et al. | Applicant |
| US4974191(A) | 1990-11-01 | Amirghodsi et al. | Applicant |
| US5128672(A) | 1992-07-01 | Kaehler | Applicant |
| US5282265(A) | 1994-01-01 | Rohra Suda et al. | Applicant |
| US5325462(A) | 1994-06-01 | Farrett | Applicant |
| US5386556(A) | 1995-01-01 | Hedin et al. | Applicant |
| US5434777(A) | 1995-07-01 | Luciw | Applicant |
| US5479488(A) | 1995-12-01 | Lenning et al. | Applicant |
| US5490234(A) | 1996-02-01 | Narayan | Applicant |
| US5577241(A) | 1996-11-01 | Spencer | Applicant |
| US5608624(A) | 1997-03-01 | Luciw | Applicant |
| US5682539(A) | 1997-10-01 | Conrad et al. | Applicant |
| US5727950(A) | 1998-03-01 | Cook et al. | Applicant |
| US5748974(A) | 1998-05-01 | Johnson | Applicant |
| US5794050(A) | 1998-08-01 | Dahlgren et al. | Applicant |
| US5826261(A) | 1998-10-01 | Spencer | Applicant |
| US5860064(A) | 1999-01-01 | Henton | Applicant |
| US5878393(A) | 1999-03-01 | Hata et al. | Applicant |
| US5878396(A) | 1999-03-01 | Henton | Applicant |
| US5895466(A) | 1999-04-01 | Goldberg et al. | Applicant |
| US5899972(A) | 1999-05-01 | Miyazawa et al. | Applicant |
| US5915249(A) | 1999-06-01 | Spencer | Applicant |
| US5987404(A) | 1999-11-01 | Della Pietra et al. | Applicant |
| US6052656(A) | 2000-04-01 | Suda et al. | Applicant |
| US6076060(A) | 2000-06-01 | Lin et al. | Applicant |
| US6081750(A) | 2000-06-01 | Hoffberg et al. | Applicant |
| US6088731(A) | 2000-07-01 | Kiraly et al. | Applicant |
| US6122616(A) | 2000-09-01 | Henton | Applicant |
| US6144938(A) | 2000-11-01 | Surace et al. | Applicant |
| US6188999(B1) | 2001-02-01 | Moody | Applicant |
| US6233559(B1) | 2001-05-01 | Balakrishnan | Applicant |
| US6246981(B1) | 2001-06-01 | Papineni et al. | Applicant |
| US6317594(B1) | 2001-11-01 | Gossman et al. | Applicant |
| US6317831(B1) | 2001-11-01 | King | Applicant |
| US6321092(B1) | 2001-11-01 | Fitch et al. | Applicant |
| US6334103(B1) | 2001-12-01 | Surace et al. | Applicant |
| US6385586(B1) | 2002-05-01 | Dietz | Examiner |
| US6411932(B1) | 2002-06-01 | Molnar et al. | Applicant |
| US6421672(B1) | 2002-07-01 | McAllister et al. | Applicant |
| US6434524(B1) | 2002-08-01 | Weber | Applicant |
| US6446076(B1) | 2002-09-01 | Burkey et al. | Applicant |
| US6453292(B2) | 2002-09-01 | Ramaswamy et al. | Applicant |
| US6466654(B1) | 2002-10-01 | Cooper et al. | Applicant |
| US6499013(B1) | 2002-12-01 | Weber | Applicant |
| US6501937(B1) | 2002-12-01 | Ho et al. | Applicant |
| US6513063(B1) | 2003-01-01 | Julia et al. | Applicant |
| US6523061(B1) | 2003-02-01 | Halverson et al. | Applicant |
| US6526395(B1) | 2003-02-01 | Morris | Applicant |
| US6532444(B1) | 2003-03-01 | Weber | Applicant |
| US6532446(B1) | 2003-03-01 | King | Applicant |
| US6598039(B1) | 2003-07-01 | Livowsky | Applicant |
| US6601026(B2) | 2003-07-01 | Appelt et al. | Applicant |
| US6615172(B1) | 2003-09-01 | Bennett et al. | Applicant |
| US6633846(B1) | 2003-10-01 | Bennett et al. | Applicant |
| US6647260(B2) | 2003-11-01 | Dusse et al. | Applicant |
| US6650735(B2) | 2003-11-01 | Burton et al. | Applicant |
| US6665639(B2) | 2003-12-01 | Mozer et al. | Applicant |
| US6665640(B1) | 2003-12-01 | Bennett et al. | Applicant |
| US6691111(B2) | 2004-02-01 | Lazaridis et al. | Applicant |
| US6691151(B1) | 2004-02-01 | Cheyer et al. | Applicant |
| US6694297(B2) | 2004-02-01 | Sato | Examiner |
| US6735632(B1) | 2004-05-01 | Kiraly et al. | Applicant |
| US6742021(B1) | 2004-05-01 | Halverson et al. | Applicant |
| US6757362(B1) | 2004-06-01 | Cooper et al. | Applicant |
| US6757653(B2) | 2004-06-01 | Buth et al. | Applicant |
| US6757718(B1) | 2004-06-01 | Halverson et al. | Applicant |
| US6760700(B2) | 2004-07-01 | Lewis et al. | Examiner |
| US6778951(B1) | 2004-08-01 | Contractor | Applicant |
| US6792082(B1) | 2004-09-01 | Levine | Applicant |
| US6807574(B1) | 2004-10-01 | Partovi et al. | Applicant |
| US6810379(B1) | 2004-10-01 | Vermeulen et al. | Applicant |
| US6813491(B1) | 2004-11-01 | McKinney | Applicant |
| US6820055(B2) | 2004-11-01 | Saindon et al. | Applicant |
| US6832194(B1) | 2004-12-01 | Mozer et al. | Applicant |
| US6842767(B1) | 2005-01-01 | Partovi et al. | Applicant |
| US6851115(B1) | 2005-02-01 | Cheyer et al. | Applicant |
| US6859931(B1) | 2005-02-01 | Cheyer et al. | Applicant |
| US6895380(B2) | 2005-05-01 | Sepe, Jr. | Applicant |
| US6895558(B1) | 2005-05-01 | Loveland | Applicant |
| US6928614(B1) | 2005-08-01 | Everhart | Applicant |
| US6937975(B1) | 2005-08-01 | Elworthy | Applicant |
| US6964023(B2) | 2005-11-01 | Maes et al. | Applicant |
| US6980949(B2) | 2005-12-01 | Ford | Applicant |
| US6996531(B2) | 2006-02-01 | Korall et al. | Applicant |
| US6999927(B2) | 2006-02-01 | Mozer et al. | Applicant |
| US7020685(B1) | 2006-03-01 | Chen et al. | Applicant |
| US7027974(B1) | 2006-04-01 | Busch et al. | Applicant |
| US7036128(B1) | 2006-04-01 | Julia et al. | Applicant |
| US7039588(B2) | 2006-05-01 | Okutani et al. | Applicant |
| US7050977(B1) | 2006-05-01 | Bennett | Applicant |
| US7062428(B2) | 2006-06-01 | Hogenhout et al. | Applicant |
| US7069560(B1) | 2006-06-01 | Cheyer et al. | Applicant |
| US7092887(B2) | 2006-08-01 | Mozer et al. | Applicant |
| US7092928(B1) | 2006-08-01 | Elad et al. | Applicant |
| US7127046(B1) | 2006-10-01 | Smith et al. | Applicant |
| US7136710(B1) | 2006-11-01 | Hoffberg et al. | Applicant |
| US7137126(B1) | 2006-11-01 | Coffman et al. | Applicant |
| US7139714(B2) | 2006-11-01 | Bennett et al. | Applicant |
| US7177798(B2) | 2007-02-01 | Hsu et al. | Applicant |
| US7197460(B1) | 2007-03-01 | Gupta et al. | Applicant |
| US7200559(B2) | 2007-04-01 | Wang | Applicant |
| US7203646(B2) | 2007-04-01 | Bennett | Applicant |
| US7216073(B2) | 2007-05-01 | Lavi et al. | Applicant |
| US7216080(B2) | 2007-05-01 | Tsiao et al. | Applicant |
| US7225125(B2) | 2007-05-01 | Bennett et al. | Applicant |
| US7233790(B2) | 2007-06-01 | Kjellberg et al. | Applicant |
| US7233904(B2) | 2007-06-01 | Luisi | Applicant |
| US7236932(B1) | 2007-06-01 | Grajski | Examiner |
| US7266496(B2) | 2007-09-01 | Wang et al. | Applicant |
| US7277854(B2) | 2007-10-01 | Bennett et al. | Applicant |
| US7290039(B1) | 2007-10-01 | Lisitsa et al. | Applicant |
| US7299033(B2) | 2007-11-01 | Kjellberg et al. | Applicant |
| US7308408(B1) | 2007-12-01 | Stifelman et al. | Examiner |
| US7310600(B1) | 2007-12-01 | Garner et al. | Applicant |
| US7310605(B2) | 2007-12-01 | Janakiraman et al. | Examiner |
| US7324947(B2) | 2008-01-01 | Jordan et al. | Applicant |
| US7349953(B2) | 2008-03-01 | Lisitsa et al. | Applicant |
| US7365260(B2) | 2008-04-01 | Kawashima | Examiner |
| US7376556(B2) | 2008-05-01 | Bennett | Applicant |
| US7376645(B2) | 2008-05-01 | Bernard | Applicant |
| US7379874(B2) | 2008-05-01 | Schmid et al. | Applicant |
| US7386449(B2) | 2008-06-01 | Sun et al. | Applicant |
| US7392185(B2) | 2008-06-01 | Bennett | Applicant |
| US7398209(B2) | 2008-07-01 | Kennewick et al. | Applicant |
| US7403938(B2) | 2008-07-01 | Harrison et al. | Applicant |
| US7409337(B1) | 2008-08-01 | Potter et al. | Applicant |
| US7415100(B2) | 2008-08-01 | Cooper et al. | Applicant |
| US7418392(B1) | 2008-08-01 | Mozer et al. | Applicant |
| US7426467(B2) | 2008-09-01 | Nashida et al. | Applicant |
| US7447635(B1) | 2008-11-01 | Konopka et al. | Applicant |
| US7454351(B2) | 2008-11-01 | Jeschke et al. | Applicant |
| US7467087(B1) | 2008-12-01 | Gillick et al. | Applicant |
| US7472061(B1) | 2008-12-01 | Alewine et al. | Applicant |
| US7475010(B2) | 2009-01-01 | Chao | Applicant |
| US7483894(B2) | 2009-01-01 | Cao | Applicant |
| US7487089(B2) | 2009-02-01 | Mozer | Applicant |
| US7496498(B2) | 2009-02-01 | Chu et al. | Examiner |
| US7502738(B2) | 2009-03-01 | Kennewick et al. | Applicant |
| US7522927(B2) | 2009-04-01 | Fitch et al. | Applicant |
| US7523108(B2) | 2009-04-01 | Cao | Applicant |
| US7526466(B2) | 2009-04-01 | Au | Applicant |
| US7539656(B2) | 2009-05-01 | Fratkina et al. | Applicant |
| US7542967(B2) | 2009-06-01 | Hurst-Hiller et al. | Examiner |
| US7546382(B2) | 2009-06-01 | Healey et al. | Applicant |
| US7548895(B2) | 2009-06-01 | Pulsipher | Applicant |
| US7555431(B2) | 2009-06-01 | Bennett | Applicant |
| US7571106(B2) | 2009-08-01 | Cao et al. | Applicant |
| US7599918(B2) | 2009-10-01 | Shen et al. | Applicant |
| US7620549(B2) | 2009-11-01 | Di Cristo et al. | Applicant |
| US7624007(B2) | 2009-11-01 | Bennett | Applicant |
| US7634409(B2) | 2009-12-01 | Kennewick et al. | Applicant |
| US7640160(B2) | 2009-12-01 | Di Cristo et al. | Applicant |
| US7647225(B2) | 2010-01-01 | Bennett et al. | Applicant |
| US7657424(B2) | 2010-02-01 | Bennett | Applicant |
| US7672841(B2) | 2010-03-01 | Bennett | Applicant |
| US7676026(B1) | 2010-03-01 | Baxter, Jr. | Applicant |
| US7684985(B2) | 2010-03-01 | Dominach et al. | Applicant |
| US7684991(B2) | 2010-03-01 | Stohr et al. | Examiner |
| US7693720(B2) | 2010-04-01 | Kennewick et al. | Applicant |
| US7698131(B2) | 2010-04-01 | Bennett | Applicant |
| US7702500(B2) | 2010-04-01 | Blaedow | Applicant |
| US7702508(B2) | 2010-04-01 | Bennett | Applicant |
| US7707027(B2) | 2010-04-01 | Balchandran et al. | Applicant |
| US7707032(B2) | 2010-04-01 | Wang et al. | Applicant |
| US7707267(B2) | 2010-04-01 | Lisitsa et al. | Applicant |
| US7711672(B2) | 2010-05-01 | Au | Applicant |
| US7716056(B2) | 2010-05-01 | Weng et al. | Applicant |
| US7720674(B2) | 2010-05-01 | Kaiser et al. | Applicant |
| US7720683(B1) | 2010-05-01 | Vermeulen et al. | Applicant |
| US7725307(B2) | 2010-05-01 | Bennett | Applicant |
| US7725318(B2) | 2010-05-01 | Gavalda et al. | Applicant |
| US7725320(B2) | 2010-05-01 | Bennett | Applicant |
| US7725321(B2) | 2010-05-01 | Bennett | Applicant |
| US7729904(B2) | 2010-06-01 | Bennett | Applicant |
| US7729916(B2) | 2010-06-01 | Coffman et al. | Applicant |
| US7734461(B2) | 2010-06-01 | Kwak et al. | Applicant |
| US7752152(B2) | 2010-07-01 | Paek et al. | Applicant |
| US7774204(B2) | 2010-08-01 | Mozer et al. | Applicant |
| US7783486(B2) | 2010-08-01 | Rosser et al. | Applicant |
| US7801729(B2) | 2010-09-01 | Mozer | Applicant |
| US7809570(B2) | 2010-10-01 | Kennewick et al. | Applicant |
| US7809610(B2) | 2010-10-01 | Cao | Applicant |
| US7818176(B2) | 2010-10-01 | Freeman et al. | Applicant |
| US7822608(B2) | 2010-10-01 | Cross, Jr. et al. | Applicant |
| US7831426(B2) | 2010-11-01 | Bennett | Applicant |
| US7840400(B2) | 2010-11-01 | Lavi et al. | Applicant |
| US7840447(B2) | 2010-11-01 | Kleinrock et al. | Applicant |
| US7873519(B2) | 2011-01-01 | Bennett | Applicant |
| US7873654(B2) | 2011-01-01 | Bernard | Applicant |
| US7881936(B2) | 2011-02-01 | Longé et al. | Applicant |
| US7912702(B2) | 2011-03-01 | Bennett | Applicant |
| US7917367(B2) | 2011-03-01 | Di Cristo et al. | Applicant |
| US7917497(B2) | 2011-03-01 | Harrison et al. | Applicant |
| US7920678(B2) | 2011-04-01 | Cooper et al. | Applicant |
| US7930168(B2) | 2011-04-01 | Weng et al. | Applicant |
| US7949529(B2) | 2011-05-01 | Weider et al. | Applicant |
| US7974844(B2) | 2011-07-01 | Sumita | Applicant |
| US7974972(B2) | 2011-07-01 | Cao | Applicant |
| US7983915(B2) | 2011-07-01 | Knight et al. | Applicant |
| US7983917(B2) | 2011-07-01 | Kennewick et al. | Applicant |
| US7983919(B2) | 2011-07-01 | Conkie | Applicant |
| US7983997(B2) | 2011-07-01 | Allen et al. | Applicant |
| US7987151(B2) | 2011-07-01 | Schott et al. | Applicant |
| US8000453(B2) | 2011-08-01 | Cooper et al. | Applicant |
| US8005679(B2) | 2011-08-01 | Jordan et al. | Applicant |
| US8015006(B2) | 2011-09-01 | Kennewick et al. | Applicant |
| US8024195(B2) | 2011-09-01 | Mozer et al. | Applicant |
| US8036901(B2) | 2011-10-01 | Mozer | Applicant |
| US8041570(B2) | 2011-10-01 | Mirkovic et al. | Applicant |
| US8041611(B2) | 2011-10-01 | Kleinrock et al. | Applicant |
| US8055708(B2) | 2011-11-01 | Chitsaz et al. | Applicant |
| US8069046(B2) | 2011-11-01 | Kennewick et al. | Applicant |
| US8073681(B2) | 2011-12-01 | Baldwin et al. | Applicant |
| US8082153(B2) | 2011-12-01 | Coffman et al. | Applicant |
| US8095364(B2) | 2012-01-01 | LongÉ et al. | Applicant |
| US8099289(B2) | 2012-01-01 | Mozer et al. | Applicant |
| US8107401(B2) | 2012-01-01 | John et al. | Applicant |
| US8112275(B2) | 2012-02-01 | Kennewick et al. | Applicant |
| US8112280(B2) | 2012-02-01 | Lu | Applicant |
| US8140335(B2) | 2012-03-01 | Kennewick et al. | Applicant |
| US8165886(B1) | 2012-04-01 | Gagnon et al. | Applicant |
| US8195467(B2) | 2012-06-01 | Mozer et al. | Applicant |
| US8204238(B2) | 2012-06-01 | Mozer | Applicant |
| US2001/0056342(A1) | 2001-12-01 | Piehn et al. | Examiner |
| US2002/0103646(A1) | 2002-08-01 | Kochanski et al. | Applicant |
| US2004/0054534(A1) | 2004-03-01 | Junqua | Examiner |
| US2004/0073428(A1) | 2004-04-01 | Zlokarnik et al. | Applicant |
| US2004/0124583(A1) | 2004-07-01 | Landis | Applicant |
| US2005/0071332(A1) | 2005-03-01 | Ortega et al. | Applicant |
| US2005/0080625(A1) | 2005-04-01 | Bennett et al. | Applicant |
| US2005/0119897(A1) | 2005-06-01 | Bennett et al. | Applicant |
| US2006/0095848(A1) | 2006-05-01 | Naik | Applicant |
| US2006/0122834(A1) | 2006-06-01 | Bennett | Applicant |
| US2006/0143007(A1) | 2006-06-01 | Koh et al. | Applicant |
| US2006/0168150(A1) | 2006-07-01 | Naik et al. | Applicant |
| US2007/0055529(A1) | 2007-03-01 | Kanevsky et al. | Applicant |
| US2007/0088556(A1) | 2007-04-01 | Andrew | Applicant |
| US2007/0100790(A1) | 2007-05-01 | Cheyer et al. | Applicant |
| US2007/0155346(A1) | 2007-07-01 | Mijatovic et al. | Applicant |
| US2007/0174188(A1) | 2007-07-01 | Fish | Applicant |
| US2007/0185917(A1) | 2007-08-01 | Prahlad et al. | Applicant |
| US2007/0282595(A1) | 2007-12-01 | Tunning et al. | Applicant |
| US2008/0015864(A1) | 2008-01-01 | Ross et al. | Applicant |
| US2008/0021708(A1) | 2008-01-01 | Bennett et al. | Applicant |
| US2008/0034032(A1) | 2008-02-01 | Healey et al. | Applicant |
| US2008/0052063(A1) | 2008-02-01 | Bennett et al. | Applicant |
| US2008/0052077(A1) | 2008-02-01 | Bennett et al. | Applicant |
| US2008/0059200(A1) | 2008-03-01 | Puli | Applicant |
| US2008/0120112(A1) | 2008-05-01 | Jordan et al. | Applicant |
| US2008/0140657(A1) | 2008-06-01 | Azvine et al. | Applicant |
| US2008/0221903(A1) | 2008-09-01 | Kanevsky et al. | Applicant |
| US2008/0228485(A1) | 2008-09-01 | Owen | Applicant |
| US2008/0228496(A1) | 2008-09-01 | Yu et al. | Applicant |
| US2008/0247519(A1) | 2008-10-01 | Abella et al. | Applicant |
| US2008/0300878(A1) | 2008-12-01 | Bennett | Applicant |
| US2009/0006097(A1) | 2009-01-01 | Etezadi et al. | Applicant |
| US2009/0006343(A1) | 2009-01-01 | Platt et al. | Applicant |
| US2009/0030800(A1) | 2009-01-01 | Grois | Applicant |
| US2009/0048821(A1) | 2009-02-01 | Yam et al. | Applicant |
| US2009/0058823(A1) | 2009-03-01 | Kocienda | Applicant |
| US2009/0076796(A1) | 2009-03-01 | Daraselia | Applicant |
| US2009/0100049(A1) | 2009-04-01 | Cao | Applicant |
| US2009/0150156(A1) | 2009-06-01 | Kennewick et al. | Applicant |
| US2009/0157401(A1) | 2009-06-01 | Bennett | Applicant |
| US2009/0164441(A1) | 2009-06-01 | Cheyer | Applicant |
| US2009/0171664(A1) | 2009-07-01 | Kennewick et al. | Applicant |
| US2009/0299745(A1) | 2009-12-01 | Kennewick et al. | Applicant |
| US2009/0299849(A1) | 2009-12-01 | Cao et al. | Applicant |
| US2010/0005081(A1) | 2010-01-01 | Bennett | Applicant |
| US2010/0023320(A1) | 2010-01-01 | Di Cristo et al. | Applicant |
| US2010/0036660(A1) | 2010-02-01 | Bennett | Applicant |
| US2010/0042400(A1) | 2010-02-01 | Block et al. | Applicant |
| US2010/0145700(A1) | 2010-06-01 | Kennewick et al. | Applicant |
| US2010/0204986(A1) | 2010-08-01 | Kennewick et al. | Applicant |
| US2010/0217604(A1) | 2010-08-01 | Baldwin et al. | Applicant |
| US2010/0228540(A1) | 2010-09-01 | Bennett | Applicant |
| US2010/0235341(A1) | 2010-09-01 | Bennett | Applicant |
| US2010/0257160(A1) | 2010-10-01 | Cao | Applicant |
| US2010/0277579(A1) | 2010-11-01 | Cho et al. | Applicant |
| US2010/0280983(A1) | 2010-11-01 | Cho et al. | Applicant |
| US2010/0286985(A1) | 2010-11-01 | Kennewick et al. | Applicant |
| US2010/0299142(A1) | 2010-11-01 | Freeman et al. | Applicant |
| US2010/0312547(A1) | 2010-12-01 | van Os et al. | Applicant |
| US2010/0318576(A1) | 2010-12-01 | Kim | Applicant |
| US2010/0332235(A1) | 2010-12-01 | David | Applicant |
| US2010/0332348(A1) | 2010-12-01 | Cao | Applicant |
| US2011/0082688(A1) | 2011-04-01 | Kim et al. | Applicant |
| US2011/0112827(A1) | 2011-05-01 | Kennewick et al. | Applicant |
| US2011/0112921(A1) | 2011-05-01 | Kennewick et al. | Applicant |
| US2011/0119049(A1) | 2011-05-01 | Ylonen | Applicant |
| US2011/0125540(A1) | 2011-05-01 | Jang et al. | Applicant |
| US2011/0131036(A1) | 2011-06-01 | Di Cristo et al. | Applicant |
| US2011/0131045(A1) | 2011-06-01 | Cristo et al. | Applicant |
| US2011/0144999(A1) | 2011-06-01 | Jang et al. | Applicant |
| US2011/0161076(A1) | 2011-06-01 | Davis et al. | Applicant |
| US2011/0175810(A1) | 2011-07-01 | Markovic et al. | Applicant |
| US2011/0184730(A1) | 2011-07-01 | LeBeau et al. | Applicant |
| US2011/0218855(A1) | 2011-09-01 | Cao et al. | Applicant |
| US2011/0231182(A1) | 2011-09-01 | Weider et al. | Applicant |
| US2011/0231188(A1) | 2011-09-01 | Kennewick et al. | Applicant |
| US2011/0264643(A1) | 2011-10-01 | Cao | Applicant |
| US2011/0279368(A1) | 2011-11-01 | Klein et al. | Applicant |
| US2011/0306426(A1) | 2011-12-01 | Novak et al. | Applicant |
| US2012/0002820(A1) | 2012-01-01 | Leichter | Applicant |
| US2012/0016678(A1) | 2012-01-01 | Gruber et al. | Applicant |
| US2012/0020490(A1) | 2012-01-01 | Leichter | Applicant |
| US2012/0022787(A1) | 2012-01-01 | LeBeau et al. | Applicant |
| US2012/0022857(A1) | 2012-01-01 | Baldwin et al. | Applicant |
| US2012/0022860(A1) | 2012-01-01 | Lloyd et al. | Applicant |
| US2012/0022868(A1) | 2012-01-01 | LeBeau et al. | Applicant |
| US2012/0022869(A1) | 2012-01-01 | Lloyd et al. | Applicant |
| US2012/0022870(A1) | 2012-01-01 | Kristjansson et al. | Applicant |
| US2012/0022874(A1) | 2012-01-01 | Lloyd et al. | Applicant |
| US2012/0022876(A1) | 2012-01-01 | LeBeau et al. | Applicant |
| US2012/0023088(A1) | 2012-01-01 | Cheng et al. | Applicant |
| US2012/0034904(A1) | 2012-02-01 | LeBeau et al. | Applicant |
| US2012/0035908(A1) | 2012-02-01 | LeBeau et al. | Applicant |
| US2012/0035924(A1) | 2012-02-01 | Jitkoff et al. | Applicant |
| US2012/0035931(A1) | 2012-02-01 | LeBeau et al. | Applicant |
| US2012/0035932(A1) | 2012-02-01 | Jitkoff et al. | Applicant |
| US2012/0042343(A1) | 2012-02-01 | Laligand et al. | Applicant |
| EP1245023(A1) | 2002-10-01 | Applicant | |
| JP6019965 | 1994-01-01 | Applicant | |
| JP2001125896 | 2001-05-01 | Applicant | |
| JP2002024212 | 2002-01-01 | Applicant | |
| JP2003517158(A) | 2003-05-01 | Applicant | |
| JP2009036999 | 2009-02-01 | Applicant | |
| KR10-0776800(B1) | 2007-11-01 | Applicant | |
| KR10-0810500(B1) | 2008-03-01 | Applicant | |
| KR102008109322(A) | 2008-12-01 | Applicant | |
| KR102009086805(A) | 2009-08-01 | Applicant | |
| KR10-0920267(B1) | 2009-10-01 | Applicant | |
| KR1020110113414(A) | 2011-10-01 | Applicant | |
| WO2005/034085(A1) | 2005-04-01 | Applicant | |
| WO2006/129967(A1) | 2006-12-01 | Applicant | |
| WO2011088053(A2) | 2011-07-01 | Applicant |
Non-Patent Literature (94)
- Mark Wilson, “New iPod Shuffle Moves Buttons to Headphones, Adds Text to Speech” Mar. 11, 2009, http://gizmodo.com/5167946/new-ipod-shiffle-moves-buttons-to-deadphones-adds-text-to-speech, retrieved Apr. 24, 2009.Applicant
- Alfred App, 2011, http://www.alfredapp.com/, 5 pages.Applicant
- Ambite, JL., et al., “Design and Implementation of the CALO Query Manager,” Copyright© 2006, American Association for Artificial Intelligence, (www.aaai.org), 8 pages.Applicant
- Ambite, JL., et al., “Integration of Heterogeneous Knowledge Sources in the CALO Query Manager,” 2005, The 4th International Conference on Ontologies, DataBases, and Applications of Semantics (ODBASE), Agia Napa, Cyprus, ttp://www.isi.edu/people/ambite/publications/integration—heterogeneous—knowledge—sources—calo—query—manager, 18 pages.Applicant
- Belvin, R. et al., “Development of the HRL Route Navigation Dialogue System,” 2001, In Proceedings of the First International Conference on Human Language Technology Research, Paper, Copyright © 2001 HRL Laboratories, LLC, http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.10.6538, 5 pages.Applicant
- Berry, P. M., et al. “PTIME: Personalized Assistance for Calendaring,” ACM Transactions on Intelligent Systems and Technology, vol. 2, No. 4, Article 40, Publication date: Jul. 2011, 40:1-22, 22 pages.Applicant
- Butcher, M., “EVI arrives in town to go toe-to-toe with Siri,” Jan. 23, 2012, http://techcrunch.com/2012/01/23/evi-arrives-in-town-to-go-toe-to-toe-with-siri/, 2 pages.Applicant
- Chen, Y., “Multimedia Siri Finds and Plays Whatever You Ask For,” Feb. 9, 2012, http://www.psfk.com/2012/02/multimedia-siri.html, 9 pages.Applicant
- Cheyer, A. et al., “Spoken Language and Multimodal Applications for Electronic Realties,” © Springer-Verlag London Ltd, Virtual Reality 1999, 3:1-15, 15 pages.Applicant
- Cutkosky, M. R. et al., “PACT: An Experiment in Integrating Concurrent Engineering Systems,” Journal, Computer, vol. 26 Issue 1, Jan. 1993, IEEE Computer Society Press Los Alamitos, CA, USA, http://dl.acm.org/citation.cfm?id=165320, 14 pages.Applicant
- Ericsson, S. et al., “Software illustrating a unified approach to multimodality and multilinguality in the in-home domain,” Dec. 22, 2006, Talk and Look: Tools for Ambient Linguistic Knowledge, http://www.talk-project.eurice.eu/fileadmin/talk/publications—public/deliverables—public/D1—6.pdf, 127 pages.Applicant
- Evi, “Meet Evi: the one mobile app that provides solutions for your everyday problems,” Feb. 8, 2012, http://www.evi.com/, 3 pages.Applicant
- Feigenbaum, E., et al., “Computer-assisted Semantic Annotation of Scientific Life Works,” 2007, http://tomgruber.org/writing/stanford-cs300.pdf, 22 pages.Applicant
- Gannes, L., “Alfred App Gives Personalized Restaurant Recommendations,” allthingsd.com, Jul. 18, 2011, http://allthingsd.com/20110718/alfred-app-gives-personalized-restaurant-recommendations/, 3 pages.Applicant
- Gautier, P. O., et al. “Generating Explanations of Device Behavior Using Compositional Modeling and Causal Ordering,” 1993, http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.42.8394, 9 pages.Applicant
- Gervasio, M. T., et al., Active Preference Learning for Personalized Calendar Scheduling Assistancae, Copyright © 2005, http://www.ai.sri.com/˜gervasio/pubs/gervasio-iui05.pdf, 8 pages.Applicant
- Glass, A., “Explaining Preference Learning,” 2006, http://cs229.stanford.edu/proj2006/Glass-ExplainingPreferenceLearning.pdf, 5 pages.Applicant
- Gruber, T. R., et al., “An Ontology for Engineering Mathematics,” In Jon Doyle, Piero Torasso, & Erik Sandewall, Eds., Fourth International Conference on Principles of Knowledge Representation and Reasoning, Gustav Stresemann Institut, Bonn, Germany, Morgan Kaufmann, 1994, http://www-ksl.stanford.edu/knowledge-sharing/papers/engmath.html, 22 pages.Applicant
- Gruber, T. R., “A Translation Approach to Portable Ontology Specifications,” Knowledge Systems Laboratory, Stanford University, Sep. 1992, Technical Report KSL 92-71, Revised Apr. 1993, 27 pages.Applicant
- Gruber, T. R., “Automated Knowledge Acquisition for Strategic Knowledge,” Knowledge Systems Laboratory, Machine Learning, 4, 293-336 (1989), 44 pages.Applicant
- Gruber, T. R., “(Avoiding) the Travesty of the Commons,” Presentation at NPUC 2006, New Paradigms for User Computing, IBM Almaden Research Center, Jul. 24, 2006. http://tomgruber.org/writing/avoiding-travestry.htm, 52 pages.Applicant
- Gruber, T. R., “Big Think Small Screen: How semantic computing in the cloud will revolutionize the consumer experience on the phone,” Keynote presentation at Web 3.0 conference, Jan. 27, 2010, http://tomgruber.org/writing/web30jan2010.htm, 41 pages.Applicant
- Gruber, T. R., “Collaborating around Shared Content on the WWW,” W3C Workshop on WWW and Collaboration, Cambridge, MA, Sep. 11, 1995, http://www.w3.org/Collaboration/Workshop/Proceedings/P9.html, 1 page.Applicant
- Gruber, T. R., “Collective Knowledge Systems: Where the Social Web meets the Semantic Web,” Web Semantics: Science, Services and Agents on the World Wide Web (2007), doi:10.1016/j.websem.2007.11.011, keynote presentation given at the 5th International Semantic Web Conference, Nov. 7, 2006, 19 pages.Applicant
- Gruber, T. R., “Where the Social Web meets the Semantic Web,” Presentation at the 5th International Semantic Web Conference, Nov. 7, 2006, 38 pages.Applicant
- Gruber, T. R., “Despite our Best Efforts, Ontologies are not the Problem,” AAAI Spring Symposium, Mar. 2008, http://tomgruber.org/writing/aaai-ss08.htm, 40 pages.Applicant
- Gruber, T. R., “Enterprise Collaboration Management with Intraspect,” Intraspect Software, Inc., Instraspect Technical White Paper Jul. 2001, 24 pages.Applicant
- Gruber, T. R., “Every ontology is a treaty—a social agreement—among people with some common motive in sharing,” Interview by Dr. Miltiadis D. Lytras, Official Quarterly Bulletin of AIS Special Interest Group on Semantic Web and Information Systems, vol. 1, Issue 3, 2004, http://www.sigsernis.org 1, 5 pages.Applicant
- Gruber, T. R., et al., “Generative Design Rationale: Beyond the Record and Replay Paradigm,” Knowledge Systems Laboratory, Stanford University, Dec. 1991, Technical Report KSL 92-59, Updated Feb. 1993, 24 pages.Applicant
- Gruber, T. R., “Helping Organizations Collaborate, Communicate, and Learn,” Presentation to NASA Ames Research, Mountain View, CA, Mar. 2003, http://tomgruber.org/writing/organizational-intelligence-talk.htm, 30 pages.Applicant
- Gruber, T. R., “Intelligence at the Interface: Semantic Technology and the Consumer Internet Experience,” Presentation at Semantic Technologies conference (SemTech08), May 20, 2008, http://tomgruber.org/writing.htm, 40 pages.Applicant
- Gruber, T. R., Interactive Acquisition of Justifications: Learning “Why” by Being Told “What” Knowledge Systems Laboratory, Stanford University, Oct. 1990, Technical Report KSL 91-17, Revised Feb. 1991, 24 pages.Applicant
- Gruber, T. R., “It Is What It Does: The Pragmatics of Ontology for Knowledge Sharing,” (c) 2000, 2003, http://www.cidoc-crm.org/docs/symposium—presentations/gruber—cidoc-ontology-2003.pdf, 21 pages.Applicant
- Gruber, T. R., et al., “Machine-generated Explanations of Engineering Models: A Compositional Modeling Approach,” (1993) In Proc. International Joint Conference on Artificial Intelligence, http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.34.930, 7 pages.Applicant
- Gruber, T. R., “2021: Mass Collaboration and the Really New Economy,” TNTY Futures, the newsletter of The Next Twenty Years series, vol. 1, Issue 6, Aug. 2001, http://www.tnty.com/newsletter/futures/archive/v01-05business.html, 5 pages.Applicant
- Gruber, T. R., et al., “NIKE: A National Infrastructure for Knowledge Exchange,” Oct. 1994, http://www.eit.com/papers/nike/nike.html and nike.ps, 10 pages.Applicant
- Gruber, T. R., “Ontologies, Web 2.0 and Beyond,” Apr. 24, 2007, Ontology Summit 2007, http://tomgruber.org/writing/ontolog-social-web-keynote.pdf, 17 pages.Applicant
- Gruber, T. R., “Ontology of Folksonomy: A Mash-up of Apples and Oranges,” Originally published to the web in 2005, Int'l Journal on Semantic Web & Information Systems, 3(2), 2007, 7 pages.Applicant
- Gruber, T. R., “Siri, a Virtual Personal Assistant—Bringing Intelligence to the Interface,” Jun. 16, 2009, Keynote presentation at Semantic Technologies conference, Jun. 2009. http://tomgruber.org/writing/semtech09.htm, 22 pages.Applicant
- Gruber, T. R., “TagOntology,” Presentation to Tag Camp, www.tagcamp.org, Oct. 29, 2005, 20 pages.Applicant
- Gruber, T. R., et al., “Toward a Knowledge Medium for Collaborative Product Development,” In Artificial Intelligence in Design 1992, from Proceedings of the Second International Conference on Artificial Intelligence in Design, Pittsburgh, USA, Jun. 22-25, 1992, 19 pages.Applicant
- Gruber, T. R., “Toward Principles for the Design of Ontologies Used for Knowledge Sharing,” In International Journal Human-Computer Studies 43, p. 907-928, substantial revision of paper presented at the International Workshop on Formal Ontology, Mar., 1993, Padova, Italy, available as Technical Report KSL 93-04, Knowledge Systems Laboratory, Stanford University, further revised Aug. 23, 1993, 23 pages.Applicant
- Guzzoni, D., et al., “Active, a Platform for Building Intelligent Operating Rooms,” Surgetica 2007 Computer-Aided Medical Interventions: tools and applications, pp. 191-198, Paris, 2007, Sauramps Médical, http://lsro.epfl.ch/page-68384-en.html, 8 pages.Applicant
- Guzzoni, D., et al., “Active, A Tool for Building Intelligent User Interfaces,” ASC 2007, Palma de Mallorca, http://lsro.epfl.ch/page-34241.html, 6 pages.Applicant
- Guzzoni, D., et al., “Modeling Human-Agent Interaction with Active Ontologies,” 2007, AAAI Spring Symposium, Interaction Challenges for Intelligent Assistants, Stanford University, Palo Alto, California, 8 pages.Applicant
- Hardawar, D., “Driving app Waze builds its own Siri for hands-free voice control,” Feb. 9, 2012, http://venturebeat.com/2012/02/09/driving-app-waze-builds-its-own-siri-for-hands-freevoice-control/, 4 pages.Applicant
- Intraspect Software, “The Intraspect Knowledge Management Solution: Technical Overview,” http://tomgruber.org/writing/intraspect-whitepaper-1998.pdf, 18 pages.Applicant
- Julia, L., et al., Un éditeur interactif de tableaux dessinés à main levée (An Interactive Editor for Hand-Sketched Tables), Traitement du Signal 1995, vol. 12, No. 6, 8 pages. No English Translation Available.Applicant
- Karp, P. D., “A Generic Knowledge-Base Access Protocol,” May 12, 1994, http://lecture.cs.buu.ac.th/˜f50353/Document/gfp.pdf, 66 pages.Applicant
- Lemon, O., et al., “Multithreaded Context for Robust Conversational Interfaces: Context-Sensitive Speech Recognition and Interpretation of Corrective Fragments,” Sep. 2004, ACM Transactions on Computer-Human Interaction, vol. 11, No. 3, 27 pages.Applicant
- Leong, L., et al., “CASIS: A Context-Aware Speech Interface System,” IUI'05, Jan. 9-12, 2005, Proceedings of the 10th international conference on Intelligent user interfaces, San Diego, California, USA, 8 pages.Applicant
- Lieberman, H., et al., “Out of context: Computer systems that adapt to, and learn from, context,” 2000, IBM Systems Journal, vol. 39, Nos. 3/4, 2000, 16 pages.Applicant
- Lin, B., et al., “A Distributed Architecture for Cooperative Spoken Dialogue Agents with Coherent Dialogue State and History,” 1999, http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.42.272, 4 pages.Applicant
- McGuire, J., et al., “SHADE: Technology for Knowledge-Based Collaborative Engineering,” 1993, Journal of Concurrent Engineering: Applications and Research (CERA), 18 pages.Applicant
- Milward, D., et al., “D2.2: Dynamic Multimodal Interface Reconfiguration,” Talk and Look: Tools for Ambient Linguistic Knowledge, Aug. 8, 2006, http://www.ihmc.us/users/nblaylock/Pubs/Files/talk—d2.2.pdf, 69 pages.Applicant
- Mitra, P., et al., “A Graph-Oriented Model for Articulation of Ontology Interdependencies,” 2000, http://ilpubs.stanford.edu:8090/442/1/2000-20.pdf, 15 pages.Applicant
- Moran, D. B., et al., “Multimodal User Interfaces in the Open Agent Architecture,” Proc. of the 1997 International Conference on Intelligent User Interfaces (IUI97), 8 pages.Applicant
- Mozer, M., “An Intelligent Environment Must be Adaptive,” Mar./Apr. 1999, IEEE Intelligent Systems, 3 pages.Applicant
- Mühlhäuser, M., “Context Aware Voice User Interfaces for Workflow Support,” Darmstadt 2007, http://tuprints.ulb.tu-darmstadt.de/876/1/PhD.pdf, 254 pages.Applicant
- Naone, E., “TR10: Intelligent Software Assistant,” Mar.-Apr. 2009, Technology Review, http://www.technologyreview.com/printer—friendly—article.aspx?id=22117, 2 pages.Applicant
- Neches, R., “Enabling Technology for Knowledge Sharing,” Fall 1991, Al Magazine, pp. 37-56, (21 pages).Applicant
- Nöth, E., et al., “Verbmobil: The Use of Prosody in the Linguistic Components of a Speech Understanding System,” IEEE Transactions on Speech and Audio Processing, vol. 8, No. 5, Sep. 2000, 14 pages.Applicant
- Rice, J., et al., “Monthly Program: Nov. 14, 1995,” The San Francisco Bay Area Chapter of ACM SIGCHI, http://www.baychi.org/calendar/19951114/, 2 pages.Applicant
- Rivlin, Z., et al., “Maestro: Conductor of Multimedia Analysis Technologies,” 1999 SRI International, Communications of the Association for Computing Machinery (CACM), 7 pages.Applicant
- Sheth, a., et al., “Relationships at the Heart of Semantic Web: Modeling, Discovering, and Exploiting Complex Semantic Relationships,” Oct. 13, 2002, Enhancing the Power of the Internet: Studies in Fuzziness and Soft Computing, SpringerVerlag, 38 pages.Applicant
- Simonite, T., “One Easy Way to Make Siri Smarter,” Oct. 18, 2011, Technology Review, http:// www.technologyreview.com/printer—friendly—article.aspx?id=38915, 2 pages.Applicant
- Stent, A., et al., “The CommandTalk Spoken Dialogue System,” 1999, http://acl.idc.upenn.edu/P/P99/P99-1024.pdf, 8 pages.Applicant
- Tofel, K., et al., “SpeakTolt: A personal assistant for older iPhones, iPads,” Feb. 9, 2012, http://gigaom.com/apple/speaktoit-siri-for-older-iphones-ipads/, 7 pages.Applicant
- Tucker, J., “Too lazy to grab your TV remote? Use Sid instead,” Nov. 30, 2011, http://www.engadget.com/2011/11/30/too-lazy-to-grab-your-tv-remote-use-siri-instead/, 8 pages.Applicant
- Tur, G., et al., “The CALO Meeting Speech Recognition and Understanding System,” 2008, Proc. IEEE Spoken Language Technology Workshop, 4 pages.Applicant
- Tur, G., et al., “The-CALO-Meeting-Assistant System,” IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 6, Aug. 2010, 11 pages.Applicant
- Vlingo, “Vlingo Launches Voice Enablement Application on Apple App Store,” Vlingo press release dated Dec. 3, 2008, 2 pages.Applicant
- YouTube, “Knowledge Navigator,” 5:34 minute video uploaded to YouTube by Knownav on Apr. 29, 2008, http://www.youtube.com/watch?v=QRH8eimU—20on Aug. 3, 2006, 1 page.Applicant
- YouTube, “Send Text, Listen to and Send E-Mail ‘By Voice’ www.voiceassist.com,” 2:11 minute video uploaded to YouTube by VoiceAssist on Jul. 30, 2009, http://www.youtube.com/watch?v=0tEU61nHHA4, 1 page.Applicant
- YouTube, “Text'nDrive App Demo—Listen and Reply to your Messages by Voice while Driving!,” 1:57 minute video uploaded to YouTube by TextnDrive on Apr. 27, 2010, http://www.youtube.conn/watch?v=WaGfzoHsAMw, 1 page.Applicant
- YouTube, “Voice on the Go (BlackBerry),” 2:51 minute video uploaded to YouTube by VoiceOnTheGo on Jul. 27, 2009, http://www.youtube.com/watch?v=pJqpWgQS98w, 1 page.Applicant
- International Search Report and Written Opinion dated Nov. 29, 2011, received in International Application No. PCT/US2011/20861, which corresponds to U.S. Appl. No.12/987,982, 15 pages. (Thomas Robert Gruber).Applicant
- Glass, J., et al., “Multilingual Spoken-Language Understanding in the MIT Voyager System,” Aug. 1995, http://groups.csail.mit.edu/sls/publications/1995/speechcomm95-voyager.pdf, 29 pages.Applicant
- Goddeau, D., et al., “A Form-Based Dialogue Manager for Spoken Language Applications,” Oct. 1996, http://phasedance.com/pdf/icslp96.pdf, 4 pages.Applicant
- Goddeau, D., et al., “Galaxy: A Human-Language Interface to On-Line Travel Information,” 1994 International Conference on Spoken Language Processing, Sep. 18-22, 1994, Pacific Convention Plaza Yokohama, Japan, 6 pages.Applicant
- Meng, H., et al., “Wheels: A Conversational System in the Automobile Classified Domain,” Oct. 1996, httphttp://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.16.3022, 4 pages.Applicant
- Phoenix Solutions, Inc. v. West Interactive Corp., Document 40, Declaration of Christopher Schmandt Regarding the MIT Galaxy System dated Jul. 2, 2010, 162 pages.Applicant
- Seneff, S., et al., “A New Restaurant Guide Conversational System: Issues in Rapid Prototyping for Specialized Domains,” Oct. 1996, citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.16 . . . rep . . . , 4 pages.Applicant
- Vlingo InCar, “Distracted Driving Solution with Vlingo InCar,” 2:38 minute video uploaded to YouTube by Vlingo Voice on Oct. 6, 2010, http://www.youtube.com/watch?v=Vqs8XfXxgz4, 2 pages.Applicant
- Zue, V., “Conversational Interfaces: Advances and Challenges,” Sep. 1997, http://www.cs.cmu.edu/˜dod/papers/zue97.pdf, 10 pages.Applicant
- Zue, V. W., “Toward Systems that Understand Spoken Language,” Feb. 1994, ARPA Strategic Computing Institute, © 1994 IEEE, 9 pages.Applicant
- Bussler, C., et al., “Web Service Execution Environment (WSMX),” Jun. 3, 2005, W3C Member Submission, http://www.w3.org/Submission/WSMX, 29 pages.Applicant
- Cheyer, A., “About Adam Cheyer,” Sep. 17, 2012, http://www.adam.cheyer.com/about.html, 2 pages.Applicant
- Cheyer, a., “A Perspective on Al & Agent Technologies for SCM,” VerticalNet, 2001 presentation, 22 pages.Applicant
- Domingue, J., et al., “Web Service Modeling Ontology (WSMO)—An Ontology for Semantic Web Services,” Jun. 9-10, 2005, position paper at the W3C Workshop on Frameworks for Semantics in Web Services, Innsbruck, Austria, 6 pages.Applicant
- Guzzoni, D., et al., “A Unified Platform for Building Intelligent Web Interaction Assistants,” Proceedings of the 2006 IEEE/WIC/ACM International Conference on Web Intelligence and Intelligent Agent Technology, Computer Society, 4 pages.Applicant
- Roddy, D., et al., “Communication and Collaboration in a Landscape of B2B eMarketplaces,” VerticalNet Solutions, white paper, Jun. 15, 2000, 23 pages.Applicant
- Elio, R. et al., “On Abstract Task Models and Conversation Policies,” http://webdocs.cs.ualberta.ca/˜ree/publications/papers2/ATS.AA99.pdf, May 1999, 10 pages. (Previously submitted on May 31, 2012—publication date was missing).Applicant
- Rice, J., et al., “Using the Web Instead of a Window System,” Knowledge Systems Laboratory, Stanford University, (http://tomgruber.org/writing/ks1-95-69.pdf, Sep. 1995.) CHI '96 Proceedings: Conference on Human Factors in Computing Systems, Apr. 13-18, 1996, Vancouver, BC, Canada, 14 pages. (Previously submitted on May 31, 2012—publication date was missing).Applicant