Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Programming Interface to Enable a Voice Platform Porting Layer for the Implementation of a VoiceXML Browser or Interpreter

IP.com Disclosure Number: IPCOM000029512D
Original Publication Date: 2004-Jul-02
Included in the Prior Art Database: 2004-Jul-02
Document File: 2 page(s) / 32K

Publishing Venue

IBM

Abstract

A library that provides a programming interface, along with a protocol for using the API, that enables a Voice browser or interpreter to be built independently of the underlying speech and telephony technology. The interface is a technology independent abstraction of audio, speech, and telephony services.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

Programming Interface to Enable a Voice Platform Porting Layer for the Implementation of a VoiceXML Browser or Interpreter

VoiceXML browsers are typcially monolithic applications that are tightly bound to the underlying speech and telephony technology. For many reasons, it is often neccesary to replace the speech technology used by the browser. Reasons for this include needing to support ASR and TTS implementations from different speech vendors or providing different types of speech technology. An example of the later could be replacing a traditional command/control speech engine with one supporting NLU. By developing a speech/telephony abstraction, it is possible to build a VoiceXML browser or interpreter that is independent from the underlying speech and telephony technology.

A different protocol has been introduced by competing speech vendors in the Internet Engineering Task Force (IETF) called "Media Resource Control Protocol." Our solution is more powerful and flexible in part because it has independent audio and telephony interfaces. In contrast, the IETF proposal only has ASR and TTS interfaces, requiring audio playback and record to go through the speech engines. Please see the IETF's documents at http://www.ietf.org/internet-drafts/draft-ietf-speechsc-protocol-eval-02.txt and http://www.ietf.org/internet-drafts/draft-ietf-speechsc-mrcpv2-00.txt.

The library provides a programming interface, along with a protocol for using the API, that enables a Voice browser or interpreter to be built independently of the underlying speech and telephony technology. The interface is a technology independent abstraction of audio, speech, and telephony services.

Applications using the Speech and Audio Services library use the following protocol:

All Services

1. Create an instance of a service.
2. Set service error listeners.
3....