Patent Application
20080208586
1. Field of the Invention
The field of the invention is data processing, or, more specifically, methods, apparatus, and products for enabling natural language understanding using an X+V page of a multimodal application.
2. Description of Related Art
User interaction with applications running on small devices through a keyboard or stylus has become increasingly limited and cumbersome as those devices have become increasingly smaller. 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 a small device easier.
Multimodal applications are often 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 application 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 applications 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 applications, 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 applications 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 multimodal applications implemented in X+V typically model the expected voice input from a user by employing finite state grammars. Finite state grammars, however, only recognize input uttered by a user that matches one of a fixed set of phrases explicitly contained in the grammar. For example, a multimodal application employing a finite state grammar may recognize the following utterances:
Another drawback with current multimodal applications that implement finite state grammars is that these multimodal applications must specify the logic for processing each individual phrase recognized by the grammar. Often, however, multiple phrases recognizable using a finite state grammar may require the same processing logic. For example, both the phrases “I want coffee” and “Please give me some coffee” require the multimodal application to perform the same task—provide the user with coffee. In such an example, the multimodal application implementing a finite state grammar must specify the same processing logic twice—the first for handling user input of “I want coffee,” and the second for handling user input of “Please give me some coffee.” Designing current multimodal applications to handle a variety of user input phrases that specify the same action, therefore, makes programming cumbersome and time consuming. As such, readers will appreciate that room for improvement exists in enabling natural language understanding using an X+V page of a multimodal application.
Enabling natural language understanding using an X+V page of a multimodal application implemented with a statistical language model (‘SLM’) grammar of the multimodal application in an automatic speech recognition (‘ASR’) engine, with the multimodal application operating in a multimodal browser on a multimodal device supporting multiple modes of interaction including a voice mode and one or more non-voice modes, the multimodal application operatively coupled to the ASR engine through a VoiceXML interpreter, including: receiving, in the ASR engine from the multimodal application, a voice utterance; generating, by the ASR engine according to the SLM grammar, at least one recognition result for the voice utterance; determining, by an action classifier for the VoiceXML interpreter, an action identifier in dependence upon the recognition result, the action identifier specifying an action to be performed by the multimodal application; and interpreting, by the VoiceXML interpreter, the multimodal application in dependence upon the action identifier.
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 enabling natural language understanding using an X+V page of a multimodal application according to embodiments of the present invention are described with reference to the accompanying drawings, beginning with
Enabling natural language understanding using an X+V page (124) in this example is further implemented with a statistical language model (‘SLM’) grammar (104) of the multimodal application (105) in an automatic speech recognition engine (150). The system of
The SLM grammar (104) in the example of
The ASR engine may estimate the probability of each word sequence by measuring the occurrence of the word order in a set of training data. Using the combination ‘I am here,’ for example, the ASR engine may compute both the number of times ‘am’ is preceded by ‘I’ and the number of times ‘here’ is preceded by ‘I am.’ Based on the probabilities assigned to each sequence of words, the ASR engine may return the recognition result as ‘I am here’ because this combination of words has the highest probability based on the set of training data specified by the SLM grammar (104). Because estimating the probability for every possible word sequence is not practically feasible, a SLM grammar may assign each word to a part of speech, such as, for example noun, verb, adjective, adverb, preposition, and so on. An ASR engine may then estimate the probability of each possible result by measuring the occurrence of the order in which the parts of speech appear in a set of test data.
SLM grammars for use in enabling natural language understanding using an X+V page of a multimodal application according to embodiments of the present invention may be expressed in any format supported by an ASR engine. An exemplary format may include the Stochastic Language Models (N-Gram) Specification promulgated by the W3C. Using the SLM grammar (104) for speech recognition advantageously allows the multimodal application (195) to recognize an unlimited number of word combinations, thus enabling natural language understanding using an X+V page of a multimodal application according to embodiments of the present invention.
In the example of
The ‘src’ attribute specifics the URI of the definition of the exemplary SLM grammar, while the ‘type’ attribute specifies the preferred media type of the grammar. In this exemplary case, ‘x-ibmlmvocabset’ specifies the preferred media type is a grammar compiled by IBM's Embedded ViaVoice platform. Although the above example illustrates how a SLM grammar may be referenced externally, a SLM grammar's definition also may be expressed in-line in an X+V page according to any stochastic or statistical language model grammar specification as will occur to those of skill in the art such as, for example, W3C's Stochastic Language Models (N-Gram) Specification.
The system of
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 applications 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 application’ to refer to any software application, server-oriented or client-oriented, thin client or thick client, that administers more than one mode of input and more than one mode of output, typically including visual and speech modes.
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 speech to a speech engine for recognition. The speech engine (153) of
A multimodal application (195) in this example provides speech for recognition and text for speech synthesis to a speech engine through a VoiceXML interpreter (192). A VoiceXML interpreter is a software module of computer program instructions that accepts voice dialog instructions from a multimodal application, 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 (192) how to administer voice input from a user and voice prompts and responses to be presented to a user, including vocal help prompts. The VoiceXML interpreter (192) administers such dialogs by processing the dialog instructions sequentially in accordance with a VoiceXML Form Interpretation Algorithm (‘FIA’).
As shown in
The VoiceXML interpreter (192) provides grammars, speech for recognition, and text prompts for speech synthesis to the speech engine (153), and the VoiceXML interpreter (192) returns to the multimodal application speech engine (153) output in the form of recognized speech, semantic interpretation results, and digitized speech for voice prompts. In a thin client architecture, the VoiceXML interpreter (192) is located remotely from the multimodal client device in a voice server (151), the API for the VoiceXML interpreter is still implemented in the multimodal device (152), 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 (151). For ease of explanation, only one (107) of the multimodal devices (152) in the system of
The use of these four example multimodal devices (152) is for explanation only, not for limitation of the invention. Any automated computing machinery capable of accepting speech from a user, providing the speech digitized to an ASR engine through a VoiceXML interpreter, and receiving and playing speech prompts and responses from the VoiceXML interpreter may be improved to function as a multimodal device for enabling natural language understanding using an X+V page according to embodiments of the present invention.
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
Enabling natural language understanding using an X+V page 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,
The voice server (151) of
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 enable dynamic VoiceXML in an X+V page 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 applications such as, for example, X+V applications, SALT applications, or Java Speech applications. Voice server application (188) may be implemented as a web server, implemented in Java, C++, or another language, that supports enabling natural language understanding using an X+V page according embodiments 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 (153) also includes a statistical language model 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 SFVs with phonemes representing, to the extent that it is practically feasible to do so, all pronunciations of all the words 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.
In the example of
The voice server application (188) in this example is configured to receive, from a multimodal client 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 enabling natural language understanding using an X+V page, the ASR engine (150) 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 an action classifier (132). The action classifier (132) is a software component that specifies an action to be performed by the multimodal application (195) based on the recognition results generated by the ASR engine (150). The action classifier (132) specifies an action to be performed by the multimodal application (195) using an action identifier. Actions to be performed by the multimodal application (195) may include, for example, receiving user input, providing user output, system administration, and so on. Using the action classifier (132) to determine an action identifier in dependence upon a recognition result provided by an ASR engine advantageously simplifies processing logic in the multimodal application (195) because the task of transforming voice utterances into actions to be performed by the multimodal application (195) may be handled by processing logic external to the multimodal application (195)
Also stored in RAM is a VoiceXML interpreter (192), a module of computer program instructions operating according to embodiments of the present invention that interprets VoiceXML segments of the multimodal application in dependence upon the action identifier. VoiceXML input to VoiceXML interpreter (192) may originate, for example, from VoiceXML clients running remotely on multimodal devices, from X+V clients running remotely on multimodal 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 application in a thin client architecture may provide voice dialog instructions, VoiceXML segments, VoiceXML <form> elements, and the like, to VoiceXML interpreter (192) through data communications across a network with multimodal application. The voice dialog instructions include one or more SLM 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, including vocal help prompts. The VoiceXML interpreter administers such dialogs by processing the dialog instructions sequentially in accordance with a VoiceXML Form Interpretation Algorithm (‘FIA’) (193). In this example, the VoiceXML interpreter contains a VoiceXML dialog (522), where the dialog has been provided to the VoiceXML interpreter by a multimodal application to be interpreted by the VoiceXML interpreter.
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™, IBM's AIX™, IBM's i5/OS™, 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), 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,
The multimodal device (152) supports multiple modes of interaction including a voice mode and one or more non-voice modes. The example multimodal device (152) of
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 SLM grammar (104), a lexicon (106), a language-specific acoustic model (108), and a TTS engine (194), as well as a Voice XML interpreter (192) that include a form interpretation algorithm (193). VoiceXML interpreter (192) interprets and executes VoiceXML dialog instructions received from the multimodal application and provided to VoiceXML interpreter (192) through voice server application (188). VoiceXML input to VoiceXML interpreter (192) may originate from the multimodal application (195) implemented as an X+V client running remotely on the multimodal device (152).
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 applications providing responses to HTTP requests from multimodal browsers running on multimodal devices.
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 multimodal application (195) is operatively coupled to the ASR engine (150) through a VoiceXML interpreter (192). In this example, the operative coupling to the ASR engine (150) through a VoiceXML interpreter (192) is implemented with a VOIP connection (216) through a voice services module (130). The voice services module 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 (522) and speech for recognition to a VoiceXML interpreter and receiving in response voice prompts and other responses, including action identifiers according to embodiments of the present invention. The VoiceXML interpreter, in turn, utilizes the speech engine for speech recognition and generation services and utilizes the action classifier (132) to determine action identifiers in dependence upon the recognition results generated by the ASR engine.
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. So from the point of view of an application calling the API (316), the application is calling the VoiceXML interpreter directly. The data communications functions of the voice services module (130) are transparent to applications that call the API (316). At the application level, calls to the API (316) may be issued from the multimodal browser (196), which provides an execution environment for the multimodal application (195) implemented with X+V.
The system of
Enabling natural language understanding using an X+V page of a multimodal application 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 enabling natural language understanding using an X+V page 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 application (195), a module of computer program instructions capable of operating a multimodal device as an apparatus that supports enabling natural language understanding using an X+V page according to embodiments of the present invention. The multimodal application (195) implements speech recognition by accepting speech utterances for recognition from a user and sending the utterance for recognition through API calls to the ASR engine (150). The multimodal application (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 application (195) in this example does not send speech for recognition across a network to a voice server for recognition, and the multimodal application (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 application (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 application (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). The embedded VoiceXML interpreter (192) may then issue requests to the action classifier (132) to determine an action identifier in dependence upon the recognized result provided by the ASR engine (150). Multimodal application (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.
The multimodal application (195) is operatively coupled to the ASR engine (150) through a VoiceXML interpreter (192). In this example, the operative coupling through the VoiceXML interpreter is implemented using a VoiceXML interpreter API. The VoiceXML interpreter API is a module of computer program instructions for use by an application level program in providing dialog instructions and speech for recognition to a VoiceXML interpreter and receiving in response voice prompts and other responses. The VoiceXML interpreter API presents the same application interface as is presented by the API of the voice service module (130 on
The multimodal application (195) in this example, running in a multimodal browser (196) 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 application—as well as all or most of the functionality for enabling natural language understanding using an X+V page of a multimodal application according to embodiments of the present invention—is implemented on the multimodal device itself.
The multimodal device (152) in this example is configured to enable natural language understanding using an X+V page (124) of a multimodal application (195) by receiving, in the ASR engine (150) from the multimodal application (195), a voice utterance; generating, by the ASR engine (150) according to the SLM grammar (104), at least one recognition result for the voice utterance; determining, by an action classifier (132) for the VoiceXML interpreter (192), an action identifier in dependence upon the recognition result, the action identifier specifying an action to be performed by the multimodal application (195); and interpreting, by the VoiceXML interpreter (192), the multimodal application (195) in dependence upon the action identifier.
For further explanation,
The multimodal application is operatively coupled to the ASR engine (150) through a VoiceXML interpreter (192). The operative coupling provides a data communications path from the multimodal application (195) to the ASR engine (150) for SLM grammars, speech for recognition, and other input. The operative coupling also provides a data communications path from the ASR engine (150) to the multimodal application (195) for recognized speech, semantic interpretation results, and other results. The operative coupling may be effected with a VoiceXML interpreter (192 on
The method of
Enabling natural language understanding using an X+V page (124) of a multimodal application (195) according to the method of
The ‘src’ attribute specifics the URI of the definition of the exemplary SLM grammar, while the ‘type’ attribute specifies the preferred media type of the grammar. In this exemplary case, ‘x-ibmlmvocabset’ specifies the preferred media type is a grammar compiled by IBM's Embedded ViaVoice platform. Although the above example illustrates how a SLM grammar may be referenced externally, a SLM grammar's definition also may be expressed in-line in an X+V page.
The method of
The ASR engine (150) may generate (506) at least one recognition result (508) for the voice utterance (504) according to the method of
The ASR engine (150) may estimate the probability of each word sequence by measuring the occurrence of the word order in a set of training data. Using the combination ‘I am here,’ for example, the ASR engine may compute both the number of times ‘am’ is preceded by ‘I’ and the number of times ‘here’ is preceded by ‘I am.’ The ASR engine (150) may then generate (506) at least one recognition result (508) for the voice utterance (504) according to the SLM grammar (104) by selecting the combination of matched words having the highest probability of being correct based on the training data for the language in the SLM grammar (104). Readers will note that generating (506) a recognition result (508) for the voice utterance (504) according to the SLM grammar (104) advantageously allows the ASR engine (150) to recognize the user's utterance without requiring the utterance to conform to a limited sets of phrases as is often required in finite state grammars.
In VoiceXML, the recognition result (508) may be represented as an ECMAScript data structure such as, for example, the ‘application.lastresult$’ array. ECMAScript data structures represent objects in the Document Object Model (‘DOM’) at the scripting level in the X+V page. The DOM is created by a multimodal browser when the X+V page of the multimodal application is loaded. The ‘application.lastresult$’ array holds information about the last recognition generated by the ASR engine (150) for the multimodal application (195). The ‘application.lastresult$’ is an array of elements where each element, application.lastresult$[i], represents a possible result through the following shadow variables:
Using the shadow variables above, the ASR engine (150) may generate the recognition result (508) according to the method of
The method of
The action classifier (132) may determine (510) an action identifier (514) according to the method of
Further consider that the recognition result generated by the ASR engine (150) is “answer the phone.” Using the exemplary recognition-action repository above, the action classifier (132) may retrieve the action class identifiers ‘voice’ and ‘answer,’ and combine the action class identifiers with periods to form the action identifier ‘voice.answer.’ Although the recognition-action repository (511) of
Similar to the recognition result (508) of
In the method of
The shadow variable ‘ac’ is an ECMAScript object used to store the chain of ECMAScript objects representing the action identifier ‘voice.answer.’
The method of
In the method of
which specifies two actions using the VoiceXML <filled> element and associates each action with a different action identifier using the ‘slot’ attribute of the VoiceXML <field> element. In the example above, the action ‘<return event=“goto.vVoiceDialMenu”/>’ instructs the FIA of a VoiceXML interpreter to end execution of the ‘vMainMenu’ dialog and throw the ‘goto.vVoiceDialMenu’ event—resulting in a Voice Dial menu being presented to the user. The action ‘<return event=“goto.vVoiceAnswerMenu”/>’ instructs the FIA of a VoiceXML interpreter to end execution of the ‘vMainMenu’ dialog and throw the ‘goto.vVoiceAnswerMenu’ event—resulting in a Voice Answer menu being presented to the user.
To further understand how the VoiceXML interpreter (192) performs a particular action specified in the multimodal application, readers will note that each of the exemplary <filled> elements above is only executed by the VoiceXML interpreter (192) when the VoiceXML interpreter (192) is able to fill the field specified by the parent <field> element with a value. For example, the VoiceXML interpreter (192) will execute the ‘<return event=“goto.vVoiceDialMenu”/>’ action when the field ‘f1’ is filled with a value from the recognition result ‘application.lastresult$.’ Readers will further note that the value used by the VoiceXML interpreter (192) to fill the field specified by the <field> element is the value for the ECMAScript object specified by the ‘slot’ attribute of the <field> element. For example, when the <field> element has a ‘slot’ value of ‘ac.voice.answer,’ the VoiceXML interpreter (192) fills the value for the field with the value specified in the ‘application.lastresult$.ac.voice.answer’ ECMAScript data structure. However, if the ECMAScript object specified by the ‘slot’ attribute of the <field> element does not exist, the VoiceXML interpreter (192) will not fill the field specified by the <field> element with a value, and therefore will not perform the action specified in the <filled> child element of the <field> element.
Continuing with the segment from an exemplary X+V page above, if the action classifier (132) determines the action identifier (514) to be ‘voice.answer,’ then the action classifier (132) links (512) the ECMAScript data structure representing the ‘voice.answer’ action identifier to the ECMAScript date structure ‘application.lastresult$’ representing the recognition result (508), yielding:
When the VoiceXML interpreter (192) interprets the exemplary segment above, field ‘f2’ is filled with a value contained in the ECMAScript structure application.lastresult$.ac.voice.answer. Field ‘f1,’ however, is not filled with a value and remains undefined because the ECMAScript data structure ‘application.lastresult$.ac.voice.dial’ does not exist because the action classifier (132) did not determine that the action identifier ‘voice.dial’ corresponded to the recognition result (508) generated by the ASR engine (506).
In addition to performing a particular action specified in the multimodal application for an action identifier, a VoiceXML interpreter may perform a particular action based on identifier attributes that specify characteristics for the action identifier. For further explanation,
Enabling natural language understanding using an X+V page (124) of a multimodal application (195) according to the method of
The method of
The method of
The identifier attributes (602) of
Using the exemplary data structure above, the action classifier (132) may determine (600) an identifier attribute (602) for the action identifier (514) according to the method of
In the example of
For further explanation of performing (604) the particular action (500) in dependence upon the identifier attributes (602), consider the following segment of an exemplary X+V page,
which specifies an action ‘<return event=“goto.vVoiceDialMenu”/>’ based on an identifier attribute ‘confidence.’ As explained above with reference to
Exemplary embodiments of the present invention are described largely in the context of a fully functional computer system for enabling natural language understanding using an X+V page. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed on 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, Ethernets™ 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.
