Patent Grant
9123337
1. Field of the Invention
The field of the invention is data processing, or, more specifically, methods, apparatus, and products for indexing digitized speech.
2. Description Of Related Art
User interaction with applications running on devices through a keyboard or stylus has become increasingly limited and cumbersome as those devices have become increasingly smaller, more mobile, and more complex. In particular, small handheld devices like mobile phones and PDAs serve many functions and contain sufficient processing power to support user interaction through multimodal access, that is, by interaction in non-voice modes as well as voice mode. Devices which support multimodal access combine multiple user input modes or channels in the same interaction allowing a user to interact with the applications on the device simultaneously through multiple input modes or channels. The methods of input include speech recognition, keyboard, touch screen, stylus, mouse, handwriting, and others. Multimodal input often makes using an automated device easier.
Analyzing audio data with a digital audio editor is tedious if one is analyzing human speech and interested in the location of words in the audio data. Multimodal digital audio editors, including multimodal digital audio editors, may be formed by sets of markup documents served up by web servers for display on multimodal browsers. A ‘multimodal browser,’ as the term is used in this specification, generally means a web browser capable of receiving multimodal input and interacting with users with multimodal output, where modes of the multimodal input and output include at least a speech mode. Multimodal browsers typically render web pages written in XHTML+Voice (‘X+V’). X+V provides a markup language that enables users to interact with an multimodal digital audio editor often running on a server through spoken dialog in addition to traditional means of input such as keyboard strokes and mouse pointer action. Visual markup tells a multimodal browser what the user interface is look like and how it is to behave when the user types, points, or clicks. Similarly, voice markup tells a multimodal browser what to do when the user speaks to it. For visual markup, the multimodal browser uses a graphics engine; for voice markup, the multimodal browser uses a speech engine. X+V adds spoken interaction to standard web content by integrating XHTML (eXtensible Hypertext Markup Language) and speech recognition vocabularies supported by VoiceXML. For visual markup, X+V includes the XHTML standard. For voice markup, X+V includes a subset of VoiceXML. For synchronizing the VoiceXML elements with corresponding visual interface elements, X+V uses events. XHTML includes voice modules that support speech synthesis, speech dialogs, command and control, and speech grammars. Voice handlers can be attached to XHTML elements and respond to specific events. Voice interaction features are integrated with XHTML and can consequently be used directly within XHTML content.
In addition to X+V, multimodal digital audio editors also may be implemented with Speech Application Tags (‘SALT’). SALT is a markup language developed by the Salt Forum. Both X+V and SALT are markup languages for creating applications that use voice input/speech recognition and voice output/speech synthesis. Both SALT applications and X+V applications use underlying speech recognition and synthesis technologies or ‘speech engines’ to do the work of recognizing and generating human speech. As markup languages, both X+V and SALT provide markup-based programming environments for using speech engines in an application's user interface. Both languages have language elements, markup tags, that specify what the speech-recognition engine should listen for and what the synthesis engine should ‘say.’ Whereas X+V combines XHTML, VoiceXML, and the XML Events standard to create multimodal digital audio editors, SALT does not provide a standard visual markup language or eventing model. Rather, it is a low-level set of tags for specifying voice interaction that can be embedded into other environments. In addition to X+V and SALT, multimodal digital audio editors may be implemented in Java™ with a Java speech framework, in C++, for example, and with other technologies and in other environments as well.
Current lightweight voice solutions require a developer to build a grammar and lexicon to limit the potential number of words that an automated speech recognition (‘ASR’) engine must recognize-as a means for increasing accuracy. Pervasive devices have limited interaction and input modalities due to the form factor of the device, and kiosk devices have limited interaction and input modalities by design. In both cases the use of speaker independent voice recognition is implemented to enhance the user experience and interaction with the device. The state of the art in speaker independent recognition allows for some sophisticated voice applications to be written as long as there is a limited vocabulary associated with each potential voice command. For example, if the user is prompted to speak the name of a city the system can, with a good level of confidence, recognize the name of the city spoken.
Methods, apparatus, and computer program products are described for indexing digitized speech with words represented in the digitized speech, implemented with a multimodal digital audio editor operating on a multimodal device supporting multiple modes of user interaction with the multimodal digital audio editor, the modes of user interaction including a voice mode and one or more non-voice modes, the multimodal digital audio editor operatively coupled to an ASR engine, including providing by the multimodal digital audio editor to the ASR engine digitized speech for recognition; receiving in the multimodal digital audio editor from the ASR engine recognized user speech including a recognized word, also including information indicating where, in the digitized speech, representation of the recognized word begins; and inserting by the multimodal digital audio editor the recognized word, in association with the information indicating where, in the digitized speech, representation of the recognized word begins, into a speech recognition grammar, the speech recognition grammar voice enabling user interface commands of the multimodal digital audio editor.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.
Exemplary methods, apparatus, and products for indexing digitized speech according to embodiments of the present invention are described with reference to the accompanying drawings, beginning with
Examples of off-the-shelf digital audio editors that may be improved for operation as a multimodal digital audio editor that indexes digitized speech according to embodiments of the present invention include:
A multimodal device (152) is automated computing machinery that supports multiple modes of user interaction with a multimodal digital audio editor including a voice mode and one or more non-voice modes of user interaction with the multimodal digital audio editor. The voice mode is represented here with audio output of voice prompts and responses (177) from the multimodal devices and audio input of speech for recognition (315) from a user (128). Non-voice modes are represented by input/output devices such as keyboards and display screens on the multimodal devices (152). The multimodal digital audio editor (195) is operatively coupled to an automatic speech recognition (‘ASR’) engine (150) in a speech engine (148). Such an operative coupling may be implemented with an application programming interface (‘API’), a voice service module, or a VOIP connection as explained in more detail below.
The system of
The system of
contains three rules named respectively <command>, <name>, and <when>. The elements <name> and <when> inside the <command> rule are references to the rules named <name> and <when>. Such rule references require that the referenced rules must be matched by an ASR engine in order for the referring rule to be matched. In this example, therefore, the <name> rule and the <when> rule must both be matched by an ASR engine with speech from a user utterance in order for the <command> rule to be matched.
A multimodal device is an automated device, that is, automated computing machinery or a computer program running on an automated device, that is capable of accepting from users more than one mode of input, keyboard, mouse, stylus, and so on, including speech input—and also displaying more than one mode of output, graphic, speech, and so on. A multimodal device is generally capable of accepting speech input from a user, digitizing the speech, and providing digitized speech to a speech engine for recognition. A multimodal device may be implemented, for example, as a voice-enabled browser on a laptop, a voice browser on a telephone handset, an online game implemented with Java on a personal computer, and with other combinations of hardware and software as may occur to those of skill in the art. Because multimodal digital audio editors may be implemented in markup languages (X+V, SALT), object-oriented languages (Java, C++), procedural languages (the C programming language), and in other kinds of computer languages as may occur to those of skill in the art, this specification uses the term ‘multimodal digital audio editor’ to refer to any software application for editing digital audio, server-oriented or client-oriented, thin client, thick client, stand-alone application, that administers more than one mode of user input and more than one mode of output to a user, where the modes include at least a visual mode and a speech mode.
The system of
Each of the example multimodal devices (152) in the system of
As mentioned, a multimodal device according to embodiments of the present invention is capable of providing digitized speech (510) to a speech engine (153) for recognition. A speech engine is a functional module, typically a software module, although it may include specialized hardware also, that does the work of recognizing and generating or ‘synthesizing’ human speech. The speech engine implements speech recognition by use of a further module referred to in this specification as a ASR engine, and the speech engine carries out speech synthesis by use of a further module referred to in this specification as a text-to-speech (‘TTS’) engine. As shown in
A multimodal digital audio editor (195) that is implemented partially or entirely in X+V may provide speech for recognition and text for speech synthesis to a speech engine through a VoiceXML interpreter. A VoiceXML interpreter is a software module of computer program instructions that accepts voice dialog instructions from a multimodal digital audio editor, typically in the form of a VoiceXML <form> element. The voice dialog instructions include one or more grammars, data input elements, event handlers, and so on, that advise the VoiceXML interpreter how to administer voice input from a user and voice prompts and responses to be presented to a user. The VoiceXML interpreter administers such dialogs by processing the dialog instructions sequentially in accordance with a VoiceXML Form Interpretation Algorithm (‘FIA’).
Just as a speech engine may be installed locally or remotely with respect to any particular multimodal device, so also a VoiceXML interpreter may be installed locally in the multimodal device itself, or a VoiceXML interpreter may be installed remotely with respect to the multimodal device, across a data communications network (100) in a voice server (151). In a thick client architecture, a multimodal device (152) with a multimodal digital audio editor implemented in X+V includes both its own speech engine and its own VoiceXML interpreter. The VoiceXML interpreter exposes an API to the multimodal digital audio editor for use in providing speech recognition and speech synthesis for the multimodal digital audio editor. The multimodal digital audio editor provides dialog instructions, VoiceXML <form> elements, grammars, input elements, event handlers, and so on, through the API to the VoiceXML interpreter, and the VoiceXML interpreter administers the speech engine on behalf of the multimodal digital audio editor. In a thick client architecture, VoiceXML dialogs are interpreted by a VoiceXML interpreter on the multimodal device. In a thin client architecture, VoiceXML dialogs are interpreted by a VoiceXML interpreter on a voice server (151) located remotely across a data communications network (100) from the multimodal device (107) running the multimodal digital audio editor (195).
A VoiceXML interpreter provides grammars, speech for recognition, and text prompts for speech synthesis to the speech engine, and the VoiceXML interpreter returns to the multimodal digital audio editor speech engine output in the form of recognized speech, semantic interpretation results, and digitized speech for voice prompts. In a thin client architecture, the VoiceXML interpreter is located remotely from the multimodal client device (107) in a voice server (151), the API for the VoiceXML interpreter is still implemented in the multimodal device, with the API modified to communicate voice dialog instructions, speech for recognition, and text and voice prompts to and from the VoiceXML interpreter on the voice server. Each of the example multimodal devices (152) in the system of
The system of
The system of
The system of
The arrangement of the multimodal devices (152), the web server (147), the voice server (151), and the data communications network (100) making up the exemplary system illustrated in
For further explanation of speech recognition grammars,
The chart of
A ‘terminal element’ is a leaf node in the tree structure of the grammar. ‘Pizza’ (208) is a non-optional leaf node; if the ‘order’ grammar is to be matched, the word ‘pizza’ must be matched with a user utterance. The vertical bars ‘|’ designate grammar elements as alternatives, the use of any one of which will match a grammar element. In the rule <pizza_toppings>, ‘cheese’ (214), ‘pepperoni’ (216), and ‘italian sausage’ (218) are non-optional, alternative terminal elements. If the ‘order’ grammar is to be matched, the user much speak one of ‘cheese,’ ‘pepperoni,’ or ‘italian sausage.’
The grammar terms in square brackets [ ] are optional. The square brackets in [<polite_phrase>] designate the ‘polite_phrase’ rule as an optional, non-terminal element, a branch node in the grammar tree. The terms of the <polite_phrase> (204) rule in square brackets therefore are ‘optional terminals,’ leaf nodes in the grammar tree which in this example form two optional alternative phrases (210, 212), each of which is composed of two optional alternative terminals or leaf nodes, respectively: [I] (220) [want] (222) and [give] (224) [me] (226).
Indexing digitized speech according to embodiments of the present invention in a thin client architecture may be implemented with one or more voice servers, computers, that is, automated computing machinery, that provide speech recognition and speech synthesis. For further explanation, therefore,
Stored in RAM (168) is a voice server application (188), a module of computer program instructions capable of operating a voice server in a system that is configured to carry out automatic speech recognition according to embodiments of the present invention. Voice server application (188) provides voice recognition services for multimodal devices by accepting requests for speech recognition and returning speech recognition results, including text representing recognized speech, text for use as variable values in dialogs, and text as string representations of scripts for semantic interpretation. Voice server application (188) also includes computer program instructions that provide text-to-speech (‘TTS’) conversion for voice prompts and voice responses to user input in multimodal digital audio editors such as, for example, X+V applications, SALT applications, or Java Speech applications.
The voice server application (188) may be implemented as a web server, implemented in Java, C++, or another language, that supports X+V, SALT, VoiceXML, or other multimodallanguages, by providing responses to HTTP requests from X+V clients, SALT clients, Java Speech clients, or other multimodal clients. Voice server application (188) may, for a further example, be implemented as a Java server that runs on a Java Virtual Machine (102) and supports a Java voice framework by providing responses to HTTP requests from Java client applications running on multimodal devices. The voice server application (188) also may be implemented as a VoiceXML service or a SALT service, in which case, the voice server (151) will also include a SALT interpreter (103) or a VoiceXML interpreter. In addition to Java VoiceXML, and SALT, voice server applications that support automatic speech recognition may be implemented in other ways as may occur to those of skill in the art, and all such ways are well within the scope of the present invention.
The voice server (151) in this example includes a speech engine (153). The speech engine is a functional module, typically a software module, although it may include specialized hardware also, that does the work of recognizing and generating human speech. The speech engine (153) includes an automated speech recognition (‘ASR’) engine (150) for speech recognition and a text-to-speech (‘TTS’) engine (194) for generating speech. The speech engine also includes a grammar (104), a lexicon (106), and a language-specific acoustic model (108). The language-specific acoustic model (108) is a data structure, a table or database, for example, that associates Speech Feature Vectors (‘SFVs’) with phonemes representing, to the extent that it is practically feasible to do so, all pronunciations of all the worcl'l in a human language. The lexicon (106) is an association of words in text form with phonemes representing pronunciations of each word; the lexicon effectively identifies words that are capable of recognition by an ASR engine. Also stored in RAM (168) is a Text To Speech (‘TTS’) Engine (194), a module of computer program instructions that accepts text as input and returns the same text in the form of digitally encoded speech, for use in providing speech as prompts for and responses to users of multimodal systems.
The grammar (104) communicates to the ASR engine (150) the words and sequences of words that currently may be recognized. For precise understanding, distinguish the purpose of the grammar and the purpose of the lexicon. The lexicon associates with phonemes all the words that the ASR engine can recognize. The grammar communicates the words currently eligible for recognition. The set of words currently eligible for recognition and the set of words capable of recognition may or may not be the same; the set of words in the grammar typically are a subset of the words in the lexicon.
Grammars for use in indexing digitized speech according to embodiments of the present invention may be expressed in any format supported by any ASR engine, including, for example, the Java Speech Grammar Format (‘JSGF’), the format of the W3C Speech Recognition Grammar Specification (‘SRGS’), the Augmented Backus-Naur Format (‘ABNF’) from the IETF's RFC2234, in the form of a stochastic grammar as described in the W3C's Stochastic Language Models (N-Gram) Specification, and in other grammar formats as may occur to those of skill in the art. Grammars typically operate as elements of dialogs, such as, for example, a VoiceXML <menu> or an X+V <form>. A grammar's definition may be expressed in-line in a dialog. Or the grammar may be implemented externally in a separate grammar document and referenced from with a dialog with a URI. Here is an example of a grammar expressed in JSFG:
In this example, the elements named <command>, <name>, and <when> are rules of the grammar. Rules are a combination of a rulename and an expansion of a rule that advises an ASR engine or a voice interpreter which words presently can be recognized. In this example, expansion includes conjunction and disjunction, and the vertical bars ‘l’ mean ‘or.’ An ASR engine or a voice interpreter processes the rules in sequence, first <command>, then <name>, then <when>. The <command> rule accepts for recognition ‘call’ or ‘phone’ or ‘telephone’ plus, that is, in conjunction with, whatever is returned from the <name> rule and the <when> rule. The <name> rule accepts ‘bob’ or ‘martha’ or ‘joe’ or ‘pete’ or ‘chris’ or ‘john’ or ‘artoush’, and the <when> rule accepts ‘today’ or ‘this afternoon’ or ‘tomorrow’ or ‘next week.’ The command grammar as a whole matches utterances like these, for example:
The voice server application (188) in this example is configured to receive, from a multimodal client, such as a multimodal digital audio editor, located remotely across a network from the voice server, digitized speech for recognition from a user and pass the speech along to the ASR engine (150) for recognition. ASR engine (150) is a module of computer program instructions, also stored in RAM in this example. In carrying out automated speech recognition, the ASR engine receives speech for recognition in the form of at least one digitized word and uses frequency components of the digitized word to derive a Speech Feature Vector (‘SFV’). An SFV may be defined, for example, by the first twelve or thirteen Fourier or frequency domain components of a sample of digitized speech. The ASR engine can use the SFV to infer phonemes for the word from the language-specific acoustic model (108). The ASR engine then uses the phonemes to find the word in the lexicon (106).
Also stored in RAM is a VoiceXML interpreter (192), a module of computer program instructions that processes VoiceXML grammars. VoiceXML input to VoiceXML interpreter (192) may originate, for example, from VoiceXML clients running remotely as multimodal digital audio editors on multimodal devices, from SALT clients running as multimodal digital audio editors on multimodal devices, or from Java client applications running as multimodal digital audio editors remotely on multimedia devices. In this example, VoiceXML interpreter (192) interprets and executes VoiceXML segments representing voice dialog instructions received from remote multimedia devices and provided to VoiceXML interpreter (192) through voice server application (188).
A multimodal digital audio editor (195) in a thin client architecture may provide voice dialog instructions, VoiceXML segments, VoiceXML <form> elements, and the like, to VoiceXML interpreter (149) through data communications across a network with multimodal digital audio editor (195). The voice dialog instructions include one or more grammars, data input elements, event handlers, and so on, that advise the VoiceXML interpreter how to administer voice input from a user and voice prompts and responses to be presented to a user. The VoiceXML interpreter administers such dialogs by processing the dialog instructions sequentially in accordance with a VoiceXML Form Interpretation Algorithm (‘FIA’). The VoiceXML interpreter interprets VoiceXML dialogs provided to the VoiceXML interpreter by a multimodal digital audio editor.
Also stored in RAM (168) is an operating system (154). Operating systems useful in voice servers according to embodiments of the present invention include UNIX™ Linux™, Microsoft NT™, AIX™, IBM's i5/0S™, and others as will occur to those of skill in the art. Operating system (154), voice server application (188), VoiceXML interpreter (192), ASR engine (150), NM (102), and TTS Engine (194) in the example of
Voice server (151) of
Voice server (151) of
The example voice server of
The exemplary voice server (151) of
For further explanation,
In addition to the multimodal sever application (188), the voice server (151) also has installed upon it a speech engine (153) with an ASR engine (150), a grammar (104), a lexicon (106), a language-specific acoustic model (108), and a TTS engine (194), as well as a NM (102), and a Voice XML interpreter (192). VoiceXML interpreter (192) interprets and executes VoiceXML dialog instructions received from the multimodal digital audio editor and provided to VoiceXML interpreter (192) through voice server application (188). VoiceXML input to VoiceXML interpreter (192) may originate from the multimodal digital audio editor (195) implemented as an X+V client running remotely on the multimodal device (152). As noted above, the multimodal digital audio editor (195) also may be implemented as a Java client application running remotely on the multimedia device (152), a SALT application running remotely on the multimedia device (152), and in other ways as may occur to those of skill in the art.
VOIP stands for ‘Voice Over Internet Protocol,’ a generic term for routing speech over an IP-based data communications network. The speech data flows over a general-purpose packet-switched data communications network, instead of traditional dedicated, circuit-switched voice transmission lines. Protocols used to carry voice signals over the IP data communications network are commonly referred to as ‘Voice over IP’ or ‘VOIP’ protocols. VOIP traffic may be deployed on any IP data communications network, including data communications networks lacking a connection to the rest of the Internet, for instance on a private building-wide local area data communications network or ‘LAN.’
Many protocols are used to effect VOIP. The two most popular types of VOIP are effected with the IETF's Session Initiation Protocol (‘SIP’) and the ITU's protocol known as ‘H.323.’ SIP clients use TCP and UDP port 5060 to connect to SIP servers. SIP itself is used to set up and tear down calls for speech transmission. VOIP with
SIP then uses RTP for transmitting the actual encoded speech. Similarly, H.323 is an umbrella recommendation from the standards branch of the International Telecommunications Union that defines protocols to provide audio-visual communication sessions on any packet data communications network.
The apparatus of
Voice server application (188) provides voice recognition services for multimodal devices by accepting dialog instructions, VoiceXML segments, and returning speech recognition results, including text representing recognized speech, text for use as variable values in dialogs, and output from execution of semantic interpretation scripts as well as voice prompts. Voice server application (188) includes computer program instructions that provide text-to-speech (‘TTS’) conversion for voice prompts and voice responses to user input in multimodal digital audio editors such as, for example, X+V applications, SALT applications, or Java Speech applications.
The voice server application (188) receives speech for recognition from a user and passes the speech through API calls to VoiceXML interpreter (192) which in turn uses an ASR engine (150) for speech recognition. The ASR engine receives digitized speech for recognition, uses frequency components of the digitized speech to derive an SFV, uses the SFV to infer phonemes for the word from the language-specific acoustic model (108), and uses the phonemes to find the speech in the lexicon (106). The ASR engine then compares speech found as words in the lexicon to words in a grammar (104) to determine whether words or phrases in speech are recognized by the ASR engine.
The apparatus of
The ASR engine (150) in this example is improved, not only to return recognized user speech (514) from digitized user speech (510), but, when recognizing a word in the digitized speech, also identifying information (518) indicating where, in the digitized speech, representation of the word begins. The digitized speech is represented by time domain amplitude values, sampled by an analog-to-digital converter from analog speech input from a user, that is, from user utterances, and organized according to a codec in sequential sets grouped frames. Each frame is characterized in sequence by a unique, cardinal frame identification number, and each frame contains the same number of time domain amplitude samples. The ASR engine then can convert the digitized speech (510) containing a word to the frequency domain beginning with one of the frames of time domain amplitude samples- and derive an index value indicating where, in the digitized speech, representation of the word begins by multiplying the one of the frame identification numbers by the number of amplitude samples in each frame. Conversion to the frequency domain may be carried out, for example, by the Fast Fourier Transform (‘FFT’). The index value (518) so derived is an example of information indicating where, in the digitized speech, representation of the word begins.
The multimodal digital audio editor (195) is operatively coupled to the ASR engine (150). In this example, the operative coupling between the multimodal digital audio editor and the ASR engine (150) is implemented with a VOIP connection (216) through a voice services module (130), then through the voice server application (188) and either NM (102), VoiceXML interpreter (192), or SALT interpreter (103), depending on whether the multimodal digital audio editor is implemented in X+V, Java, or SALT. The voice services module (130) is a thin layer of functionality, a module of computer program instructions, that presents an API (316) for use by an application level program in providing dialog instructions and speech for recognition to a voice server application (188) and receiving in response voice prompts and other responses. In this example, application level programs are represented by multimodal digital audio editor (195), NM (101), and multimodal browser (196).
The voice services module (130) provides data communications services through the VOIP connection and the voice server application (188) between the multimodal device (152) and the VoiceXML interpreter (192). The API (316) is the same API presented to applications by a VoiceXML interpreter when the VoiceXML interpreter is installed on the multimodal device in a thick client architecture (316 on
Indexing digitized speech according to embodiments of the present invention in thick client architectures is generally implemented with multimodal devices, that is, automated computing machinery or computers. In the system of
The example multimodal device (152) of
The speech engine (153) in this kind of embodiment, a thick client architecture, often is implemented as an embedded module in a small form factor device such as a handheld device, a mobile phone, PDA, and the like. An example of an embedded speech engine useful for indexing digitized speech according to embodiments of the present invention is IBM's Embedded ViaVoice Enterprise. The example multimodal device of
Also stored in RAM (168) in this example is a multimodal digital audio editor (195), a module of computer program instructions capable of operating a multimodal device as an apparatus that supports indexing digitized speech according to embodiments of the present invention. The multimodal digital audio editor (195) implements speech recognition by accepting speech for recognition from a user and sending the speech for recognition through API calls to the ASR engine (150). The multimodal digital audio editor (195) implements speech synthesis generally by sending words to be used as prompts for a user to the TTS engine (194). As an example of thick client architecture, the multimodal digital audio editor (195) in this example does not send speech for recognition across a network to a voice server for recognition, and the multimodal digital audio editor (195) in this example does not receive synthesized speech, TTS prompts and responses, across a network from a voice server. All grammar processing, voice recognition, and text to speech conversion in this example is performed in an embedded fashion in the multimodal device (152) itself.
More particularly, multimodal digital audio editor (195) in this example is a user-level, multimodal, client-side computer program that provides a speech interface through which a user may provide oral speech for recognition through microphone (176), have the speech digitized through an audio amplifier (185) and a coder/decoder (‘codec’) (183) of a sound card (174) and provide the digitized speech for recognition to ASR engine (150). The multimodal digital audio editor (195) may be implemented as a set or sequence of X+V documents executing in a multimodal browser (196) or microbrowser that passes VoiceXML grammars and digitized speech by calls through an API (316) directly to an embedded VoiceXML interpreter (192) for processing. The embedded VoiceXML interpreter (192) may in turn issue requests for speech recognition through API calls directly to the embedded ASR engine (150). Multimodal digital audio editor (195) also can provide speech synthesis, TTS conversion, by API calls to the embedded TTS engine (194) for voice prompts and voice responses to user input.
In a further class of exemplary embodiments, the multimodal digital audio editor (195) may be implemented as a Java voice application that executes on Java Virtual Machine (102) and issues calls through the VoiceXML API (316) for speech recognition and speech synthesis services. In further exemplary embodiments, the multimodal digital audio editor (195) may be implemented as a set or sequence of SALT documents executed on a multimodal browser (196) or microbrowser that issues calls through the VoiceXML API (316) for speech recognition and speech synthesis services. In addition to X+V, SALT, and Java implementations, multimodal digital audio editor (195) may be implemented in other technologies as will occur to those of skill in the art, and all such implementations are well within the scope of the present invention.
The multimodal device of
The ASR engine (150) in this example is improved, not only to return recognized user speech (514) from digitized user speech (510), but, when recognizing a word in the digitized speech, also identifying information (518) indicating where, in the digitized speech, representation of the word begins. The digitized speech is represented by time domain amplitude values, sampled by an analog-to-digital converter from analog speech input from a user, that is, from user utterances, and organized according to a codec in sequential sets grouped frames. Each frame is characterized in sequence by a unique, cardinal frame identification number, and each frame contains the same number of time domain amplitude samples. The ASR engine then can convert the digitized speech (510) containing a word to the frequency domain beginning with one of the frames of time domain amplitude samples—and derive an index value indicating where, in the digitized speech, representation of the word begins by multiplying the one of the frame identification numbers by the number of amplitude samples in each frame. Conversion to the frequency domain may be carried out, for example, by the Fast Fourier Transform (‘FFT’). The index value (518) so derived is an example of information indicating where, in the digitized speech, representation of the word begins.
The multimodal digital audio editor (195) is operatively coupled to the ASR engine (150). In this example, the operative coupling between the multimodal digital audio editor and the ASR engine (150) is implemented either with NM (102), VoiceXML interpreter (192), or SALT interpreter (103), depending on whether the multimodal digital audio editor is implemented in X+V, Java, or SALT. When the multimodal digital audio editor (195) is implemented in X+V, the operative coupling is effected through the multimodal browser (196), which provides an operating environment and an interpreter for the X+V application, and then through the VoiceXML interpreter, which passes grammars and voice utterances for recognition to the ASR engine. When the multimodal digital audio editor (195) is implemented in Java Speech, the operative coupling is effected through the NM (102), which provides an operating environment for the Java application and passes grammars and voice utterances for recognition to the ASR engine. When the multimodal digital audio editor (195) is implemented in SALT, the operative coupling is effected through the SALT interpreter (103), which provides an operating environment and an interpreter for the X+V application and passes grammars and voice utterances for recognition to the ASRengine.
The multimodal digital audio editor (195) in this example, running on a multimodal device (152) that contains its own VoiceXML interpreter (192) and its own speech engine (153) with no network or VOIP connection to a remote voice server containing a remote VoiceXML interpreter or a remote speech engine, is an example of a so-called ‘thick client architecture,’ so-called because all of the functionality for processing voice mode interactions between a user and the multimodal digital audio editor—as well as the functionality for indexing digitized speech with words represented in the digitized speech according to embodiments of the present invention—is implemented on the multimodal device itself.
For further explanation,
The multimodal digital audio editor is operatively coupled (524) to an ASR engine (150). The operative coupling (524) provides a data communications path (504) from the multimodal digital audio editor (195) to the ASR engine for speech recognition grammars. The operative coupling (524) provides a data communications path (506) from the ASR engine (150) to the multimodal digital audio editor (195) for recognized speech and semantic interpretation results. The operative coupling may be effected with a JVM (102 on
The method of
In the method of
The method of
In this example grammar, the words “car,” “bomb,” and “airplane” are words recognized by an ASR engine and inserted by a multimodal digital audio editor into a speech recognition grammar, as non-optional terminal grammar elements, in association with the following words representing user interface commands of the multimodal digital audio editor: “play” and “show.” In this example, moreover, the multimodal digital audio editor has inserted, as parts of a non-optional terminal grammar element, information indicating where, in digitized speech, representation of each recognized word begins, respectively, in this example, as digital sample sequence numbers 167243,298374, and 314325. These sequence numbers or indices in this example are associated with the recognized words “car,” “bomb,” and “airplane” in semantic interpretation scripts, so that when the words “car,” “bomb,” and “airplane” are subsequently recognized as part of user interface commands, the value of the semantic interpretation script, that is, the index into the digitized speech where representation of the word begins is returned by an ASR engine as part of the recognition results—advising the multimodal digital audio editor how to associated a recognized word with a particular location in playback, editing, or display of the digitized speech.
The method of
For further explanation,
Also in the method of
The ASR engine may, for example, convert time-domain digital amplitude samples to the frequency domain by Fast Fourier Transform (‘FFT’) on a set of several amplitudes in a frame identified by a frame number, where the frame numbers are cardinals that uniquely identify each frame. The frame number is a time-domain entity, so the location in the digitized speech of a recognized word is specified as a cardinal sample number by multiplying the frame number by the number of amplitude samples in each frame. Because of its function as an indicator of location, that is, the location where, in the digitized speech, representation of a recognized word begins, such a cardinal sample number is sometimes referred to in this specification as an “index” or “index value.”
For further explanation,
In this example grammar, the words “car,” “bomb,” and “airplane” are words recognized by an ASR engine and inserted by a multimodal digital audio editor into a speech recognition grammar, as non-optional terminal grammar elements, in association with the following words representing user interface commands of the multimodal digital audio editor: “play” and “show.” In this example, moreover, the multimodal digital audio editor has inserted, as parts of a non-optional terminal grammar element, information indicating where, in digitized speech, representation of each recognized word begins, respectively, in this example, as digital sample sequence numbers 167243,298374, and 314325. These sequence numbers or indices in this example are associated with the recognized words “car,” “bomb,” and “airplane” in semantic interpretation scripts, so that when the words “car,” “bomb,” and “airplane” are subsequently recognized as part of user interface commands, the value of the semantic interpretation script, that is, the index into the digitized speech where representation of the word begins is returned by an ASR engine as part of the recognition results-advising the multimodal digital audio editor how to associated a recognized word with a particular location in playback, editing, or display of the digitized speech. Without the indices in the grammar, the multimodal digital audio editor would need to use the recognized word to look up the index in a table or other data structure, a much more laborious procedure than including the index in the grammar and in the recognition results.
For further explanation,
The multimodal digital audio editor, having received the recognized words and their index values, inserted each recognized word, in association its index value into a speech recognition grammar that voice enables user interface commands of the multimodal digital audio editor, such as, this example grammar:
The example grammar enables the multimodal digital audio editor to accept and carry out voice commands such as, for example:
In addition to voice control, the example GUI of
The example GUI display of
The horizontal axis of the spectrogram display (740) represents time and the vertical axis represents frequency. Amplitude or sound intensity is indicated on the spectrogram display with color or with intensity on a gray scale, for example. The words “bomb,” “airplane,” and “subway,” are visually displayed (750, 752, 754) on the spectrogram display (740) as indices of where in the digitized speech the representation of each recognized word begins, with the left edge of “bomb” (750) aligned as an index with sample number 167243 (756), the left edge of “airplane” (752) aligned as an index with sample number 298374 (758), and the left edge of “subway” (754) aligned as an index with sample number 314325 (760).
In view of the explanations set forth above, readers will now recognized that the benefits of indexing digitized speech with words represented in the digitized speech according to embodiments of the present invention include greatly easing the process of analyzing human speech with a digital audio editor when the analyst is interest in locations of particular words in the audio data. A typical multimodal digital audio editor according to embodiments of the present invention, among other benefits that will occur to those of skill in the art, effectively combines recognized text with audio data so that the audio editor can annotate a graphical display of the audio data with the recognized words and enable manipulation of the display with voice commands.
Exemplary embodiments of the present invention are described largely in the context of a fully functional computer system for indexing digitized speech with words represented in the digitized speech. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed on computer-readable signal bearing media for use with any suitable data processing system. Such signal bearing media may be transmission media or recordable media for machine-readable information, including magnetic media, optical media, or other suitable media. Examples of recordable media include magnetic disks in hard drives or diskettes, compact disks for optical drives, magnetic tape, and others as will occur to those of skill in the art. Examples of transmission media include telephone networks for voice communications and digital data communications networks such as, for example, EthernetsrM and networks that communicate with the Internet Protocol and the World Wide Web. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a program product. Persons skilled in the art will recognize immediately that, although some of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.
This application is a continuation of co-pending U.S. application Ser. No. 13/961,792, entitled “INDEXING DIGITIZED SPEECH WITH WORDS REPRESENTED IN THE DIGITIZED SPEECH,” filed on Aug. 7, 2013, which is a continuation of U.S. application Ser. No. 11/688,331, entitled “INDEXING DIGITIZED SPEECH WITH WORDS REPRESENTED IN THE DIGITIZED SPEECH,” filed on Mar. 20, 2007, now U.S. Pat. No. 8,515,757, issued Aug. 20, 2013. Each of the documents listed above is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5577165 | Takebayashi et al. | Nov 1996 | A |
| 5584052 | Gulau et al. | Dec 1996 | A |
| 5649060 | Ellozy et al. | Jul 1997 | A |
| 5774628 | Hemphill | Jun 1998 | A |
| 5875429 | Douglas | Feb 1999 | A |
| 5875448 | Boys et al. | Feb 1999 | A |
| 5960447 | Holt et al. | Sep 1999 | A |
| 5969717 | Ikemoto | Oct 1999 | A |
| 6208972 | Grant et al. | Mar 2001 | B1 |
| 6243375 | Speicher | Jun 2001 | B1 |
| 6275806 | Pertrushin | Aug 2001 | B1 |
| 6301560 | Masters | Oct 2001 | B1 |
| 6513011 | Uwakubo | Jan 2003 | B1 |
| 6606599 | Grant et al. | Aug 2003 | B2 |
| 6728682 | Fasciano | Apr 2004 | B2 |
| 6856960 | Dragosh et al. | Feb 2005 | B1 |
| 6920425 | Will et al. | Jul 2005 | B1 |
| 6999930 | Roberts et al. | Feb 2006 | B1 |
| 7035805 | Miller | Apr 2006 | B1 |
| 7171243 | Watanabe et al. | Jan 2007 | B2 |
| 7188067 | Grant et al. | Mar 2007 | B2 |
| 7330890 | Partovi et al. | Feb 2008 | B1 |
| 7356472 | Cross et al. | Apr 2008 | B2 |
| 7376586 | Partovi et al. | May 2008 | B1 |
| 7401337 | Bou-Ghannam et al. | Jul 2008 | B2 |
| 7409690 | Bou-Ghannam et al. | Aug 2008 | B2 |
| 7487085 | Ativanichayaphong et al. | Feb 2009 | B2 |
| 7509260 | Cross, Jr. et al. | Mar 2009 | B2 |
| 7509659 | McArdle | Mar 2009 | B2 |
| 7548977 | Agapi et al. | Jun 2009 | B2 |
| 7650284 | Cross et al. | Jan 2010 | B2 |
| 7739117 | Ativanichayaphong et al. | Jun 2010 | B2 |
| 7925512 | Cross, Jr. et al. | Apr 2011 | B2 |
| 7966188 | Ativanichayaphong et al. | Jun 2011 | B2 |
| 8024194 | Cross, Jr. et al. | Sep 2011 | B2 |
| 8082148 | Agapi et al. | Dec 2011 | B2 |
| 8121837 | Agapi et al. | Feb 2012 | B2 |
| 8214242 | Agapi et al. | Jul 2012 | B2 |
| 8229081 | Agapi et al. | Jul 2012 | B2 |
| 8515757 | Cross, Jr. et al. | Aug 2013 | B2 |
| 20020009172 | Cornog et al. | Jan 2002 | A1 |
| 20020065944 | Hickey et al. | May 2002 | A1 |
| 20020092019 | Marcus | Jul 2002 | A1 |
| 20020095290 | Kahn et al. | Jul 2002 | A1 |
| 20020099553 | Brittan et al. | Jul 2002 | A1 |
| 20020120554 | Vega | Aug 2002 | A1 |
| 20020129057 | Spielberg | Sep 2002 | A1 |
| 20020143533 | Lucas et al. | Oct 2002 | A1 |
| 20020147593 | Lewis et al. | Oct 2002 | A1 |
| 20020184610 | Chong et al. | Dec 2002 | A1 |
| 20030039341 | Burg et al. | Feb 2003 | A1 |
| 20030046316 | Gergic et al. | Mar 2003 | A1 |
| 20030046346 | Mumick et al. | Mar 2003 | A1 |
| 20030101451 | Bentolila et al. | May 2003 | A1 |
| 20030125945 | Doyle | Jul 2003 | A1 |
| 20030179865 | Stillman et al. | Sep 2003 | A1 |
| 20030182622 | Sibal et al. | Sep 2003 | A1 |
| 20030195739 | Washio | Oct 2003 | A1 |
| 20030217161 | Balasuriya | Nov 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20030235282 | Sichelman et al. | Dec 2003 | A1 |
| 20040019487 | Kleindienst et al. | Jan 2004 | A1 |
| 20040025115 | Sienel et al. | Feb 2004 | A1 |
| 20040031058 | Reisman | Feb 2004 | A1 |
| 20040044516 | Kennewick et al. | Mar 2004 | A1 |
| 20040049388 | Roth et al. | Mar 2004 | A1 |
| 20040049390 | Brittan et al. | Mar 2004 | A1 |
| 20040059705 | Wittke et al. | Mar 2004 | A1 |
| 20040083109 | Halonen et al. | Apr 2004 | A1 |
| 20040120472 | Popay et al. | Jun 2004 | A1 |
| 20040120476 | Harrison et al. | Jun 2004 | A1 |
| 20040138890 | Ferrans et al. | Jul 2004 | A1 |
| 20040153323 | Charney et al. | Aug 2004 | A1 |
| 20040179038 | Blattner et al. | Sep 2004 | A1 |
| 20040216036 | Chu et al. | Oct 2004 | A1 |
| 20040236574 | Ativanichayaphong et al. | Nov 2004 | A1 |
| 20040260562 | Kujirai | Dec 2004 | A1 |
| 20050042591 | Bloom et al. | Feb 2005 | A1 |
| 20050075884 | Badt | Apr 2005 | A1 |
| 20050091059 | Lecoeuche | Apr 2005 | A1 |
| 20050131559 | Kahn et al. | Jun 2005 | A1 |
| 20050131701 | Cross et al. | Jun 2005 | A1 |
| 20050138219 | Bou-Ghannam et al. | Jun 2005 | A1 |
| 20050138647 | Bou-ghannam et al. | Jun 2005 | A1 |
| 20050154580 | Horowitz et al. | Jul 2005 | A1 |
| 20050159948 | Roth et al. | Jul 2005 | A1 |
| 20050160461 | Baumgartner et al. | Jul 2005 | A1 |
| 20050188412 | Dacosta | Aug 2005 | A1 |
| 20050203729 | Roth et al. | Sep 2005 | A1 |
| 20050203747 | Lecoeuche | Sep 2005 | A1 |
| 20050261908 | Cross et al. | Nov 2005 | A1 |
| 20050273769 | Eichenberger et al. | Dec 2005 | A1 |
| 20050283367 | Ativanichayaphong et al. | Dec 2005 | A1 |
| 20060047510 | Ativanichayaphong et al. | Mar 2006 | A1 |
| 20060064302 | Ativanichayaphong et al. | Mar 2006 | A1 |
| 20060069564 | Allison et al. | Mar 2006 | A1 |
| 20060074680 | Cross et al. | Apr 2006 | A1 |
| 20060075120 | Smit | Apr 2006 | A1 |
| 20060111906 | Cross et al. | May 2006 | A1 |
| 20060122836 | Cross et al. | Jun 2006 | A1 |
| 20060123358 | Lee et al. | Jun 2006 | A1 |
| 20060136222 | Cross et al. | Jun 2006 | A1 |
| 20060146728 | Engelsma et al. | Jul 2006 | A1 |
| 20060168095 | Sharma et al. | Jul 2006 | A1 |
| 20060168595 | McArdle | Jul 2006 | A1 |
| 20060184626 | Agapi et al. | Aug 2006 | A1 |
| 20060190264 | Jaramillo et al. | Aug 2006 | A1 |
| 20060218039 | Johnson | Sep 2006 | A1 |
| 20060229880 | White et al. | Oct 2006 | A1 |
| 20060235694 | Cross et al. | Oct 2006 | A1 |
| 20060287845 | Cross et al. | Dec 2006 | A1 |
| 20060287865 | Cross et al. | Dec 2006 | A1 |
| 20060287866 | Cross et al. | Dec 2006 | A1 |
| 20060288309 | Cross et al. | Dec 2006 | A1 |
| 20070265851 | Ben-David et al. | Nov 2007 | A1 |
| 20070274296 | Cross et al. | Nov 2007 | A1 |
| 20070274297 | Cross et al. | Nov 2007 | A1 |
| 20070288241 | Cross et al. | Dec 2007 | A1 |
| 20070294084 | Cross et al. | Dec 2007 | A1 |
| 20080065386 | Cross et al. | Mar 2008 | A1 |
| 20080065387 | Cross, Jr. et al. | Mar 2008 | A1 |
| 20080065388 | Cross et al. | Mar 2008 | A1 |
| 20080065389 | Cross et al. | Mar 2008 | A1 |
| 20080065390 | Ativanichayaphong et al. | Mar 2008 | A1 |
| 20080086564 | Putman et al. | Apr 2008 | A1 |
| 20080140410 | Ativanichayaphong et al. | Jun 2008 | A1 |
| 20080162136 | Agapi et al. | Jul 2008 | A1 |
| 20080177530 | Cross et al. | Jul 2008 | A1 |
| 20080195393 | Cross et al. | Aug 2008 | A1 |
| 20080208584 | Ativanichayaphong et al. | Aug 2008 | A1 |
| 20080208585 | Ativanichayaphong et al. | Aug 2008 | A1 |
| 20080208586 | Ativanichayaphong et al. | Aug 2008 | A1 |
| 20080208587 | Ben-David et al. | Aug 2008 | A1 |
| 20080208588 | Ativanichayaphong et al. | Aug 2008 | A1 |
| 20080208589 | Cross et al. | Aug 2008 | A1 |
| 20080208590 | Cross et al. | Aug 2008 | A1 |
| 20080208591 | Ativanichayaphong et al. | Aug 2008 | A1 |
| 20080208592 | Cross et al. | Aug 2008 | A1 |
| 20080208593 | Ativanichayaphong et al. | Aug 2008 | A1 |
| 20080208594 | Cross et al. | Aug 2008 | A1 |
| 20080228494 | Cross | Sep 2008 | A1 |
| 20080228495 | Cross, Jr. et al. | Sep 2008 | A1 |
| 20080235021 | Cross et al. | Sep 2008 | A1 |
| 20080235022 | Bergl et al. | Sep 2008 | A1 |
| 20080235027 | Cross | Sep 2008 | A1 |
| 20080235029 | Cross et al. | Sep 2008 | A1 |
| 20080249782 | Ativanichayaphong et al. | Oct 2008 | A1 |
| 20080255850 | Cross et al. | Oct 2008 | A1 |
| 20080255851 | Ativanichayaphong et al. | Oct 2008 | A1 |
| 20090268883 | Agapi et al. | Oct 2009 | A1 |
| 20090271188 | Agapi et al. | Oct 2009 | A1 |
| 20090271189 | Agapi et al. | Oct 2009 | A1 |
| 20090271199 | Agapi et al. | Oct 2009 | A1 |
| 20090271438 | Agapi et al. | Oct 2009 | A1 |
| 20140039899 | Cross, Jr. et al. | Feb 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1385783 | Dec 2002 | CN |
| 1564123 | Jan 2005 | CN |
| 0 794 670 | Sep 1997 | EP |
| 1 450 350 | Aug 2004 | EP |
| 0507148.5 | Apr 2005 | GB |
| 2000155529 | Jun 2000 | JP |
| 2003140672 | May 2003 | JP |
| WO 9948088 | Sep 1999 | WO |
| WO 0051106 | Aug 2000 | WO |
| WO 0232140 | Apr 2002 | WO |
| WO 2004062945 | Jul 2004 | WO |
| WO 2006108795 | Oct 2006 | WO |
| Entry |
|---|
| Audacity user manual, [online], http://audacity.sourceforge.net , release 1.2, releasing date Mar. 1, 2004. |
| Axelsson, et al.; “XFITML+Voice Profile 1.2” Internet, [Online] Mar. 16, 2004, pp. 1-53, XP002484188 Retrieved from the Internet: URL:http://www.voicexml.org/specs/mutlimodal/x+v/12/spec.html [retrieved on Jun. 12, 2008]. |
| Didier Guillevic, et al.,Robust Semantic Confidence Scoring ICSLP 2002: 7 th International Conference on Spoken Language Processing. Denver Colorado, Sep. 16-20, 2002 International Conference on Spoken Language Processing (ICSLP), Adelaide: Causal Productions, AI, Sep. 16, 2002, p. 853, XP007011561 ISBN:9788-1-876346-40-9. |
| Gauvain et al. “Transcribing broadcast news for audio and video indexing”, Communication of the ACM, Feb. 2000. |
| Nuance Speech Recognition System, Version 8.0, “Grammar Developer's Guide”, Nuance Communications, Inc., 2001. |
| PCT Search Report, Jun. 18, 2008; PCT Application No. PCT/EP2008/051363. |
| PCT Search Report, Jun. 25, 2008; PCT Application No. PCT/EP2008/051358. |
| Taiwanese Office Action for TW Application No. 097107352 mailed Apr. 17, 2013. |
| Chinese Office Action for CN Application No. 101271689 mailed Jun. 3, 2010. |
| Chinese Office Action for CN Application No. 101271689 mailed Dec. 16, 2010. |
| Chinese Office Action for CN Application No. 101271689 mailed Mar. 18, 2011. |
| Chinese Office Action for CN Application No. 101271689 mailed Jul. 29, 2011. |
| Chinese Office Action for CN Application No. 101271689 mailed Oct. 31, 2011. |
| W3C: “Voice Extensible Markup Language (VoiceXML) 2.1, W3C Candidate Recommendation Jun. 13, 2005” Internet, [Online] Jun. 13, 2005, pp. 1-34, XP002484189 Retrieved from the Internet: URL:http://www.w3.orgaR/2005/CR-voicexm121-20050613/ [retrieved on Jun. 121, 2008. |
| W3C: “Voice Extensible Markup Language (VoiceXML) Version 2.0” Internet Citation, [Online] XP002248286 Retrieved from the Internet: URL:http://www.w3.orgITR/voicexml20 [retrieved on Jul. 18, 2003]. |
| Number | Date | Country | |
|---|---|---|---|
| 20140278422 A1 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13961792 | Aug 2013 | US |
| Child | 14204544 | US | |
| Parent | 11688331 | Mar 2007 | US |
| Child | 13961792 | US |
