US20030055884A1 - Method for automated harvesting of data from a Web site using a voice portal system - Google Patents

Method for automated harvesting of data from a Web site using a voice portal system Download PDF

Info

Publication number
US20030055884A1
US20030055884A1 US10/190,077 US19007702A US2003055884A1 US 20030055884 A1 US20030055884 A1 US 20030055884A1 US 19007702 A US19007702 A US 19007702A US 2003055884 A1 US2003055884 A1 US 2003055884A1
Authority
US
United States
Prior art keywords
voice
dialog
application
data
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/190,077
Inventor
Michael Yuen
Leo Chiu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apptera Inc
Original Assignee
FONELET TECHNOLOGY Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by FONELET TECHNOLOGY Inc filed Critical FONELET TECHNOLOGY Inc
Priority to US10/190,077 priority Critical patent/US20030055884A1/en
Assigned to FONELET TECHNOLOGY, INC. reassignment FONELET TECHNOLOGY, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHIU, LEO, YUEN, MICHAEL S.
Publication of US20030055884A1 publication Critical patent/US20030055884A1/en
Priority to US11/036,293 priority patent/US20050149331A1/en
Assigned to APPTERA, INC. reassignment APPTERA, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: FONELET TECHNOLOGY, INC.
Priority to US12/490,177 priority patent/US20100057885A1/en
Priority to US12/490,194 priority patent/US20100050150A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/487Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H04M3/4938Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals comprising a voice browser which renders and interprets, e.g. VoiceXML
    • GPHYSICS
    • G10MUSICAL INSTRUMENTS; ACOUSTICS
    • G10LSPEECH ANALYSIS OR SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING; SPEECH OR AUDIO CODING OR DECODING
    • G10L15/00Speech recognition
    • G10L15/28Constructional details of speech recognition systems
    • G10L15/30Distributed recognition, e.g. in client-server systems, for mobile phones or network applications
    • GPHYSICS
    • G10MUSICAL INSTRUMENTS; ACOUSTICS
    • G10LSPEECH ANALYSIS OR SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING; SPEECH OR AUDIO CODING OR DECODING
    • G10L15/00Speech recognition
    • G10L15/22Procedures used during a speech recognition process, e.g. man-machine dialogue
    • G10L2015/226Procedures used during a speech recognition process, e.g. man-machine dialogue using non-speech characteristics
    • G10L2015/228Procedures used during a speech recognition process, e.g. man-machine dialogue using non-speech characteristics of application context

Definitions

  • the present invention is a continuation in part of a U.S. patent application, Attorney docket No. P8100 entitled “Method and Apparatus for Development and Deployment of a Voice Software Application for Distribution to one or more Application Consumers” filed on Jun. 14, 2002, disclosure of which is included herein in its entirety by reference.
  • the parent case filed on Jun. 14, 2002 claimed priority to provisional application Serial No. 60/302,736 filed on Jul. 3, 2001, and incorporates all disclosure of that provisional application.
  • the present application therefore claims priority to both of the applications described above in this paragraph.
  • the present invention is in the area of software application development and pertains particularly to methods and apparatus for auto harvesting template-based web content using a VXML-enabled voice portal system.
  • a speech application is one of the most challenging applications to develop, deploy and maintain in a communications (typically telephony) environment.
  • Expertise required for developing and deploying a viable application includes expertise in computer telephony integration (CTI) hardware and software, voice recognition software, text-to-speech software, and speech application logic.
  • CTI computer telephony integration
  • VXML voice extensive markup language
  • the expertise require to develop a speech solution has been reduced somewhat.
  • VXML is a language that enables a software developer to focus on the application logic of the voice application without being required to configuring underlying telephony components.
  • the developed voice application is run on a VXML interpreter that resides on and executes on the associated telephony system to deliver the solution.
  • FIG. 1A a typical architecture of a VXML-compliant telephony system comprises a voice application server ( 110 ) and a VXML-compliant telephony server ( 130 ). Typical steps for development and deployment of a VXML enabled IVR solutions are briefly described below using the elements of FIG. 1A.
  • a new application database ( 113 ) is created or an existing one is modified to support VXML.
  • Application logic 112 is designed in terms of workflow and adapted to handle the routing operations of the IVR system.
  • VXML pages which are results of functioning application logic, are rendered by a VXML rendering engine ( 111 ) based on a specified generation sequence.
  • an object facade to server 130 is created comprising the corresponding VXML pages and is sent to server 130 over a network ( 120 ), which can be the Internet, an Intranet, or an Ethernet network.
  • the VXML pages are integrated into rendering engine 111 such that they can be displayed according to set workflow at server 110 .
  • the VXML-telephony server 130 is configured to enable proper retrieval of specific VXML pages from rendering engine 111 within server 110 .
  • a triggering mechanism is provided to server 110 so that when a triggering event occurs, an appropriate outbound call is placed from server 110 .
  • a VXML interpreter ( 131 ), a voice recognition text-to-speech engine ( 132 ), and the telephony hardware/software ( 133 ) are provided within server 130 and comprise server function.
  • the telephony hardware/software 130 along with the VXML interpreter 131 are packaged as an off-the-shelf IVR-enabling technology.
  • the application server 110 the application logic ( 112 ) is typically written in a programming language such as Java and packaged as an enterprise Java Bean archive.
  • the presentation logic required is handled by rendering engine 111 and is written in JSP or PERL.
  • An enhanced voice application system is known to the inventor and disclosed in the U.S. patent application entitled “Method and Apparatus for Development and Deployment of a Voice Software Application for Distribution to one or more Application Consumers” to which this application claims priority.
  • That system uses a voice application server that is connected to a data network for storing and serving voice applications.
  • the voice application server has a data connection to a network communications server connected to a communications network such as the well-known PSTN network.
  • the communication server routes the created voice applications to their intended recipients.
  • a computer station is provided as part of the system and is connected to the data network and has access to the voice application server.
  • a client software application is hosted on the computer station for the purpose of enabling users to create applications and manage their states.
  • the user operates the client software hosted on the computer station in order to create voice applications through object modeling and linking.
  • the applications, once created, are then stored in the application server for deployment.
  • the user can control and manage deployment and state of deployed applications including scheduled deployment and repeat deployments in terms of intended recipients.
  • the system described above is quite advantageous in that a developer using the system need not be highly skilled in VXML language compilation, database programming, or advanced server design. Moreover, the system substantially reduces the amount of time allotted to project development. Still further, the system supports changes or modifications performed by anyone other than the developer without having to depend on the original author (because of his or her experience) to debug or make changes.
  • Web data from Web sites should be a target data set for harvesting and conversion into a voice application that could then be routed to one or more users.
  • a system for developing and deploying a voice application using Web-based data as source data over a communications network to one or more recipients comprising a voice application server connected to a data network for storing and serving voice applications, the voice application server capable of accessing a network server and Website hosted therein, a network communications server connected to the data network and to the communications network for routing the voice applications to their intended recipients, a computer station connected to the data network having control access to at least the voice application server, the computer station capable of accessing the network server and Website hosted therein, and a software application running on the computer station for creating applications and managing their states.
  • the system is characterized in that a developer operating the software application from the computer station accesses the target server and Website and creates at least one template for holding Web data according to logical order of site construction and links the templates to voice applications created by object modeling and linking, whereupon according to a triggering event, the triggered voice application accesses the intended Website and retrieves refreshed data from the site into the template and renders the retrieved data as voice delivered to intended recipients.
  • the data network is the Internet network.
  • the voice application is delivered over a public-switched-telephony-network to a voice portal accessed by the intended recipients.
  • the security protocol used by the accessed Website is transferred as a voice access mechanism to the intended recipients.
  • the data network connections of the computer station and of the voice application server are separate data network connections.
  • the voice applications are scheduled for delivery at a specific time delivery made by outbound dialing and connection to a telephone of the intended recipient. The voice applications may be accessed by the intended recipients in real time.
  • a voice application server for rendering voice dialog using Web-based data as source data, comprising an instance of voice application development software, a database resource adapter, an instance of application logic;
  • a data rendering engine and a network access line and software application for accessing servers and Websites hosted therein for the purpose of harvesting data there from for use in voice application creation and deployment.
  • the server is characterized in that according to a trigger, the voice application server navigates to one or more servers and one or more Websites and obtains refreshed data there from converting the data to voice dialog and delivering the dialog to a voice portal accessible to an intended recipient.
  • the network is the Internet network.
  • the voice application is delivered over a public-switched-telephony-network to a voice portal accessed by the intended recipients.
  • the security protocol used by the accessed Website is transferred as a voice access mechanism to the intended recipients.
  • the voice applications are scheduled for delivery at a specific time delivery made by outbound dialing and connection to a telephone of the intended recipient. The applications may be accessed by the intended recipients in real time.
  • a template is created for storing field and source data from a Website and the template is used in voice rendering in the server.
  • the software for network access may be a browser application.
  • Embodiments of the invention taught in enabling detail below provide new and enhanced functionality for rendering information into audio form.
  • FIG. 1A is a block diagram illustrating a basic architecture of a VXML-enabled IVR development and deployment environment according to prior-art.
  • FIG. 1B is a block diagram illustrating the basic architecture of FIG. 1A enhanced to practice the present invention.
  • FIG. 2 is a process flow diagram illustrating steps for creating a voice application shell or container for a VXML voice application according to an embodiment of the present invention.
  • FIG. 3 is a block diagram illustrating a simple voice application container according to an embodiment of the present invention.
  • FIG. 4 is a block diagram illustrating a dialog object model according to an embodiment of the present invention.
  • FIG. 5 is a process flow diagram illustrating steps for voice dialog creation for a VXML-enabled voice application according to an embodiment of the present invention.
  • FIG. 6 is a block diagram illustrating a dialog transition flow after initial connection with a consumer according to an embodiment of the present invention.
  • FIG. 7 is a plan view of a developer's frame containing a developer's login screen of according to an embodiment of the present invention.
  • FIG. 8 is a plan view of a developer's frame containing a screen shot of a home page of the developer's platform interface of FIG. 7.
  • FIG. 9 is a plan view of a developer's frame containing a screen shot of an address book 911 accessible through interaction with the option Address in section 803 of the previous frame of FIG. 8.
  • FIG. 10 is a plan view of a developer's frame displaying a screen 1001 for creating a new voice application.
  • FIG. 11 is a plan view of a developer's frame illustrating screen of FIG. 10 showing further options as a result of scrolling down.
  • FIG. 12 is a screen shot of a dialog configuration window illustrating a dialog configuration page according to an embodiment of the invention.
  • FIG. 13 is a screen shot 1300 of dialog design panel of FIG. 12 illustrating progression of dialog state to a subsequent contact.
  • FIG. 14 is a screen shot of a thesaurus configuration window activated from the example of FIG. 13 according to a preferred embodiment.
  • FIG. 15 is a plan view of a developer's frame illustrating a screen for managing created modules according to an embodiment of the present invention.
  • FIG. 16 is a block diagram of the dialog transition flow of FIG. 6 enhanced for Web harvesting according to an embodiment of the present invention.
  • FIG. 17 is a block diagram of the voice application distribution environment of FIG. 1B illustrating added components for automated Web harvesting and data rendering according to an embodiment of the present invention.
  • the inventor teaches herein, in an enabling fashion, a novel system for developing and deploying real-time dynamic or static voice applications in an object-oriented way that enables inbound or outbound delivery of IVR and other interactive voice solutions in supported communications environments.
  • FIG. 1A is a block diagram illustrating a basic architecture of a VXML-enabled IVR development and deployment environment according to prior art.
  • the prior-art architecture of this example is known to and available to the inventor. Developing and deploying voice applications for the illustrated environment, which in this case is a telephony environment, requires a very high level of skill in the art. Elements of this prior-art example that have already been introduced with respect to the background section of this specification shall not be re-introduced.
  • voice application server 110 utilizes database/resource adapter 113 for accessing a database or other resources for content.
  • Application logic 112 comprising VXML script, business rules, and underlying telephony logic must be carefully developed and tested before single applications can be rendered by rendering engine 111 .
  • voice applications Once voice applications are complete and servable from server 110 , they can be deployed through data network 120 to telephony server 130 where interpreter 131 and text-to speech engine 132 are utilized to formulate and deliver the voice application in useable or playable format for telephony software and hardware 133 .
  • the applications are accessible to a receiving device, illustrated herein as device 135 , a telephone, through the prevailing network 134 , which is in this case a public-switched-telephone-network (PSTN) linking the telephony server to the consumer (device 135 ) generally through a telephony switch (not shown).
  • PSTN public-switched-telephone-network
  • Improvements to this prior-art example in embodiments of the present invention concern and are focused in the capabilities of application server 110 with respect to development and deployment issues and with respect to overall enhancement to response capabilities and options in interaction dialog that is bi-directional.
  • the inventor herein describes additional components that are not shown in the prior-art example of FIG. 1A, but are illustrated in a novel version of the example represented herein by FIG. 1B.
  • FIG. 1B is a block diagram illustrating the basic architecture of FIG. 1A enhanced to illustrate an embodiment of the present invention. Elements of the prior-art example of FIG. 1A that are also illustrated in FIG. 1B retain their original element numbers and are not re-introduced. For reference purposes an entity (a person) that develops a voice application shall be referred to hereinafter in this specification as either a producer or developer.
  • a developer or producer of a voice application operates preferably from a remote computerized workstation illustrated herein as station 140 .
  • Station 140 is essentially a network-connected computer station.
  • Station 140 may be housed within the physical domain also housing application server 110 .
  • station 140 and application server 110 may reside in the same machine.
  • a developer may operate station 140 from his or her home office or from any network-accessible location including any wireless location.
  • Station 140 is equipped with a client software tool (CL) 141 , which is adapted to enable the developer to create and deploy voice applications across the prevailing system represented by servers 110 , 130 , and by receiving device 135 .
  • CL 141 is a Web interface application similar to or incorporated with a Web browser application in this example, however other network situations may apply instead.
  • CL 141 contains the software tools required for the developer to enable enhancements according to embodiments of the invention.
  • Station 140 is connected to a voice portal 143 that is maintained either on the data network (Internet, Ethernet, Intranet, etc.) and/or within telephony network 134 . In this example portal 143 is illustrated logically in both networks.
  • Voice portal 143 is adapted to enable a developer or a voice application consumer to call in and perform functional operations (such as access, monitor, modify) on selected voice applications.
  • voice application development server 142 adapted in conjunction with the existing components 111 - 113 to provide dynamic voice application development and deployment according to embodiments of the invention.
  • Portal 143 is accessible via network connection to station 140 and via a network bridge to a voice application consumer through telephony network 134 .
  • portal 143 is maintained as part of application server 110 .
  • Portal 143 is, in addition to an access point for consumers is chiefly adapted as a developer's interface server.
  • Portal 143 is enabled by a SW instance 144 adapted as a server instance to CL 141 .
  • portal 143 may be an interactive voice response (IVR) unit.
  • IVR interactive voice response
  • the producer or developer of a voice application accesses application server 110 through portal 143 and data network 120 using remote station 140 as a “Web interface” and first creates a list of contacts.
  • station 140 has direct access to application server 110 through a network interface. Contacts are analogous to consumers of created voice applications.
  • CL 141 displays, upon request and in order of need, all of the required interactive interfaces for designing, modifying, instantiating, and executing completed voice applications to launch from application server 110 and to be delivered by server 130 .
  • the software of the present invention enables voice applications to be modeled as a set of dialog objects having business and telephony (or other communication delivery/access system) rules as parameters without requiring the developer to perform complicated coding operations.
  • a dialog template is provided for modeling dialog states. The dialog template creates the actual speech dialog, specifies the voice application consumer (recipient) of the dialog, captures the response from the voice application consumer and performs any follow-up actions based upon system interpretation of the consumer response.
  • a dialog is a reusable component and can be linked to a new dialog or to an existing (stored) dialog.
  • a voice application is a set of dialogs inter-linked by a set of business rules defined by the voice application producer. Once the voice application is completed, it is deployed by server 110 and is eventually accessible to the authorized party (device 135 ) through telephony server 130 .
  • the voice applications are in a preferred embodiment in the form of VXML to run on VXML-compliant telephony server 130 .
  • This process is enabled through VXML rendering engine 111 .
  • Engine 111 interacts directly with server 130 , locates the voice application at issue, retrieves its voice application logic, and dynamically creates the presentation in VXML and forwards it to server 130 for processing and delivery.
  • interpreter 131 interprets the VXML presentation it is sent to or accessible to device 135 in the form of an interactive dialog (in this case an IVR dialog). Any response from device 135 follows the same path back to application server 110 for interpretation by engine 111 .
  • Server 110 retrieves the voice application profile from the database accessible through adapter 113 and determines the next business rule to execute locally.
  • VXML presentation is then forwarded to rendering engine 111 , which in turn dynamically generates the next VXML page for interpretation, processing and deployment at server 130 .
  • rendering engine 111 This two-way interaction between the VXML-compliant telephony server ( 130 ) and the voice application server ( 110 ) continues in the form of an automated logical sequence of VXML dialogs until the voice application finally reaches its termination state.
  • a voice application (set of one or more dialogs) can be delivered to the consumer (target audience) in outbound or inbound fashion.
  • a voice application consumer calls in to voice portal 143 to access the inbound voice application served from server 130 .
  • the voice portal can be mapped to a phone number directly or as an extension to a central phone number.
  • the voice portal also serves as a community forum where voice application producers can put their voice applications into groups for easy access and perform operational activities such as voice application linking, reporting, and text-to-speech recording and so on.
  • server 110 For on-demand outbound applications server 110 generates an outbound call as soon as the voice application producer issues an outbound command associated with the application. The outbound call is made to the target audience and upon the receipt of the call the voice application is launched from server 130 .
  • the schedule server (not shown within server 110 ) launches the voice application as soon as the producer-specified date and time has arrived.
  • both on-demand and scheduled outbound application deployment functions support unicast, multicast and broadcast delivery schemes.
  • a voice application created by application server 110 consists of one or more dialogs.
  • the contents of each dialog can be static or dynamic.
  • Static content is content sourcing from the voice application producer. The producer creates the contents when the voice application is created.
  • a developers tool contains an interactive dialog design panel (described in detail later) wherein a producer inputs a reference link in the form of eXtensible Markup Language (XML) to the dialog description or response field.
  • XML eXtensible Markup Language
  • the reference link invokes a resource Application-Program-Interface (API) that is registered in resource adapter 113 .
  • API goes out in real time and retrieves the requested data and integrates the returned data into the existing dialog.
  • the resulting and subsequent VXML page being generated has the dynamic data embedded onto it.
  • One object of the present invention is a highly dynamic, real time IVR system that tailors itself automatically to the application developer's specified data source requirement. Another object of the present invention is to enable rapid development and deployment of a voice application without requirement of any prior knowledge of VXML or any other programming technologies. A further object of the present invention is to reduce the typical voice application production cycle and drastically reduce the cost of production.
  • FIG. 2 is a process flow diagram illustrating steps for creating a voice application shell or container for a VXML voice application according to an embodiment of the present invention.
  • a developer utilizing a client application known as a thin client analogous to CL 141 on station 140 described with reference to FIG. 1 b creates a voice application shell or voice application container.
  • the developer logs in to the system at a login page.
  • the developer creates a contact list of application consumers. Typically a greeting or welcome page would be displayed before step 202 .
  • An application consumer is an audience of one or more entities that would have access to and interact with a voice application.
  • a contact list is first created so that all of the intended contacts are available during voice application creation if call routing logic is required later on.
  • the contact list can either be entered individually in the event of more than one contact by the producer or may be imported as a set list from some organizer/planner software, such as Microsoft OutlookTM or perhaps a PDATM organizer.
  • the contact list may reside on an external device accessed by a provided connector (not shown) that is configured properly and adapted for the purpose of accessing and retrieving the list.
  • a provided connector not shown
  • This approach may be used, for example, if a large, existing customer database is used. Rather than create a copy, the needed data is extracted from the original and provided to the application.
  • a voice application header is populated.
  • a voice application header is simply a title field for the application. The field contains a name for the application and a description of the application.
  • the developer assigns either and inbound or outbound state for the voice application. An outbound application is delivered through an outbound call while the consumer accesses an inbound voice application.
  • step 205 the system sets a default addressee for inbound communications.
  • the developer selects a dialog from a configured list in step 206 . It is assumed in this example that the dialogs have already been created.
  • step 207 the developer executes the dialog and it is deployed automatically.
  • step 208 the developer chooses a launch type in step 208 .
  • a launch type can be either an on-demand type or a scheduled type. If the choice made by the developer in step 208 is scheduled, then in step 209 , the developer enters all of the appropriate time and date parameters for the launch including parameters for recurring launches of the same application. In the case of an on demand selection for application launch in step 208 , then in step 210 the developer selects one or more contacts from the contact list established in step 202 . It is noted herein that step 210 is also undertaken by the developer after step 209 in the case of a scheduled launch.
  • the dialog is created. In this step a list of probable dialog responses for a voice application wherein interaction is intended may also be created and stored for use.
  • a developer creates a voice application and integrates the application with a backend data source or, optionally, any third party resources and deploys the voice application.
  • the application consumer then consumes the voice application and optionally, the system analyzes any consumer feedback collected by the voice application for further interaction if appropriate.
  • the steps of this example pertain to generating and launching a voice application from “building blocks” that are already in place.
  • FIG. 3 is a block diagram illustrating a simple voice application container 300 according to an embodiment of the present invention.
  • Application container 300 is a logical container or “voice application object” 300 . Also termed a shell, container 300 is logically illustrated as a possible result of the process of FIG. 2 above.
  • Container 300 contains one or more dialog states illustrated herein as dialogs 301 a - n labeled in this example as dialogs 1-4. Dialogs 301 a - n are objects and therefore container 300 is a logical grouping of the set of dialog objects 301 a - n.
  • the represented set of dialog objects 301 a - n is interlinked by business rules labeled rules 1-4 in this example.
  • Rules 1-4 are defined by the developer and are rule objects. It is noted herein that that there may be many more or fewer dialog objects 301 a - n as well as interlinking business rule objects 1-4 comprising container object 300 without departing from the spirit and scope of the present invention.
  • the inventor illustrates 4 of each entity and deems the representation sufficient for the purpose of explaining the present invention.
  • voice application shell 300 includes a plurality of settings options.
  • basic settings options are tabled for reference and given the element number 305 a - c illustrating 3 listed settings options.
  • the choices for launch type 305 a are inbound or outbound.
  • a launch type may be defined by a third party and be defined in some other pattern than inbound or outbound.
  • Outbound launch designation binds a voice application to one or more addressees (consumers).
  • the addressee may be a single contact or a group of contacts represented by the contact list or distribution list also described with reference to FIG. 2 above (step 202 ).
  • the outbound voice application is launched in this case, it is delivered to the addressee designated on a voice application outbound contact field (not shown). All addressees designated receive a copy of the outbound voice application and have equal opportunity to interact (if allowed) with the voice application dialog and the corresponding backend data resources if they are used in the particular application.
  • inbound voice application designation for launch type 305 a
  • the system instructs the application to assume a ready stand-by mode.
  • the application is launched when the designated voice application consumer actively makes a request to access the voice application.
  • a typical call center IVR system assumes this type of inbound application.
  • Launch time setting ( 305 b ) is only enabled as an option if the voice application launch type setting 305 a is set to outbound.
  • the launch time setting is set to instruct a novel scheduling engine, which may be assumed to be part of the application server function described with reference to FIG. 1B.
  • the scheduling engine controls the parameter of when to deliver of when to deliver the voice application to the designated addressees.
  • the time setting may reflect on-demand, scheduled launch, or any third-party-defined patterns.
  • On-demand gives the developer full control over the launch time of the voice application.
  • the on-demand feature also allows any third-party system to issue a trigger event to launch the voice application. It is noted herein that in the case of third-party control the voice application interaction may transcend more than one communications system and or network.
  • Property setting 305 c defines essentially how the voice application should behave in general. Possible state options for setting 305 c are public, persistent, or sharable. A public state setting indicates that the voice application should be accessible to anyone within the voice portal domain so that all consumers with minimum privilege can access the application. A persistent state setting for property 305 c ensures that only one copy of the voice application is ever active regardless of how many consumers are attempting to access the application. An example of such a scenario would be that of a task-allocation voice application. For example, in a task-allocation scenario there are only a number of time slots available for a user to access the application.
  • the task is a request from a pool of contacts such as perhaps customer-support technicians to lead a scheduled chat session, then whenever a time slot has been selected, the other technicians can only select the slots that are remaining. Therefore if there is only one copy of the voice application circulating within the pool of technicians, the application captures the technician's response on a first-come first-serve basis.
  • a sharable application state setting for property 305 a enables the consumer to “see” the responses of other technicians in the dialog at issue, regardless of whether the voice application is persistent or not.
  • the producer can then create the first dialog of the voice application as described with reference to FIG. 2 step 207 . It is reminded herein that shell 300 is modeled using a remote and preferably a desktop client that will be described in more detail later in this specification.
  • FIG. 4 is a block diagram illustrating a dialog object model 400 according to an embodiment of the present invention.
  • Dialog object model 400 is analogous to any of dialog objects 301 a - n described with reference to FIG. 3 above.
  • Object 400 models a dialog and all of its properties.
  • a properties object illustrated within dialog object 400 and labeled Object Properties ( 410 ) contains the dialog type and properties including behavior states and business rules that apply to the dialog.
  • Every dialog has a route-to property illustrated in the example as Route To property ( 411 ).
  • Property 411 maps to and identifies the source of the dialog.
  • every dialog has a route-from property illustrated herein as Route From property ( 412 ).
  • Route from property 412 maps to and identifies the recipient contact of the dialog or the dialog consumer.
  • Dialog type 413 may include but is not limited to the following types of dialogs:
  • Radio Dialog A radio dialog allows a voice application consumer to interactively select one of available options from an option list after hearing the dialog description.
  • a bulletin dialog allows a voice application consumer to interact with a bulletin board-like forum where multiple consumers can share voice messages in an asynchronous manner.
  • Statement Dialog A statement dialog plays out a statement to a voice application consumer without expecting any responses from the consumer.
  • Open Entry Dialog An open entry dialog allows a voice application consumer to record a message of a pre-defined length after hearing the dialog description.
  • Third Party Dialog A third party dialog is a modular container structure that allows the developer to create a custom-made dialog type with its own properties and behaviors. An example would be Nuance's SpeechObjectTM.
  • Each dialog type has one or more associated business rules tagged to it enabling determination of a next step in response to a perceived state.
  • a rule compares the application consumer response with an operand defined by the application developer using an operational code such as less than, greater than, equal to, or not equal to.
  • the parameters surrounding a rule are as follows:
  • exception handling rules are encapsulated into three different events:
  • An application consumer designated to receive the voice application rejects a request for interacting with the voice application.
  • An application consumer has a busy connection at the time of launch of the voice application, for example, a telephone busy signal.
  • An application consumer's connection is answered by or is redirected to a non-human device, for example, a telephone answering machine.
  • FIG. 5 is a process flow diagram illustrating steps for voice dialog creation for a VXML-enabled voice application according to an embodiment of the present invention. All dialogs can be reused for subsequent dialog routing. There is, as previously described, a set of business rules for every dialog and contact pair. A dialog be active and be able to transit from one dialog state to another only when it is rule enabled.
  • a developer populates a dialog description field with a dialog description.
  • a dialog description may also contain reference to XML tags as will be described further below.
  • parameters of the dialog type are entered based on the assigned type of dialog. Examples of the available parameters were described with reference to FIG. 4 above.
  • step 503 the developer configures the applicable business rules for the dialog type covering, as well, follow up routines.
  • rules configuration at step 503 resolves to step 505 for determining follow-up routines based on the applied rules.
  • the developer may select at step 505 , one of three types of transfers.
  • the developer may configure for a live transfer as illustrated by step 506 ; transfer to a next dialog for creation as illustrated by step 507 ; or the developer may configure for dialog completion as illustrated by step 508 .
  • step 504 If the developer does not branch off into configuring sub-routines 506 , 507 , or 508 from step 505 , but rather continues from step 503 to step 504 wherein inbound or outbound designation for the dialog is system assigned, then the process must branch from step 504 to either step 508 or 509 , depending on whether the dialog is inbound or outbound. If at step 504 , the dialog is inbound, then at step 508 the dialog is completed. If the assignment at step 504 is outbound, then at step 509 to configure call exception business rules.
  • step 510 the developer configures at least one follow-up action for system handling of exceptions. If no follow-up actions are required to be specified at step 510 , then the process resolves to step 508 for dialog completion. If an action or actions are configured at step 510 , then at step 511 the action or actions are executed such as a system re-dial, which the illustrated action for step 511 .
  • a voice portal is a voice interface for accessing a selected number of functions of the voice application server described with reference to FIG. 1B above.
  • a voice portal may be a connection-oriented-switched-telephony (COST) enabled portal or a data-network-telephony (DNT) enabled portal.
  • COST connection-oriented-switched-telephony
  • DNT data-network-telephony
  • the application consumer receives the voice application through an incoming call to the consumer originated from the voice application server.
  • the outbound call can be either COST based or DNT based depending on the communications environment supported.
  • FIG. 6 is a block diagram illustrating a dialog transition flow after initial connection with a consumer according to an embodiment of the present invention.
  • Some of the elements illustrated in this example were previously introduced with respect to the example of FIG. 1B above and therefore shall retain their original element numbers.
  • an application consumer is logically illustrated as Application Consumer 600 that is actively engaged in interaction with a dialog 601 hosted by telephony server 130 .
  • Server 130 is, as previously described a VMXL compliant telephony server as is so labeled.
  • Application server 110 is also actively engaged in the interaction sequence and has the capability to provide dynamic content to consumer 600 .
  • voice application server 110 monitors the situation.
  • each dialog processed and sent to server 130 for delivery to or access by consumer 600 is an atomic unit of the particular voice application being deployed and executed. Therefore dialog 601 may logically represent more than one single dialog.
  • dialog 601 is responsible during interaction for acquiring a response from consumer 600 .
  • Arrows labeled Send and Respond represent the described interaction.
  • the response is sent back along the same original path to VXML rendering engine 111 , which interprets the response and forwards the interpreted version to a provided dialog controller 604 .
  • Controller 604 is part of application logic 112 in server 110 described with reference to FIG. 1B.
  • Dialog controller 604 is a module that has the ability to perform table lookups, data retrieve and data write functions based on established rules and configured response parameters.
  • dialog controller 604 When dialog controller 604 receives a dialog response, it stores the response corresponding to the dialog at issue ( 601 ) to a provided data source 602 for data mining operations and workflow monitoring. Controller 604 then issues a request to a provided rules engine 603 to look-up the business rule or rules that correspond to the stored response. Once the correct business rule has been located for the response, the dialog controller starts interpretation. If the business rule accessed requires reference to a third-party data source (not shown), controller 604 makes the necessary data fetch from the source. Any data returned by controller 604 is integrated into the dialog context and passed onward VXML rendering engine 111 for dialog page generation of a next dialog 601 . The process repeats until dialog 601 is terminates.
  • the business rule accessed by controller 604 as a result of a received response from consumer 600 carries a dialog transition state other than back to the current application consumer.
  • controller 604 spawns an outbound call from application server 110 to deliver the next or “generated dialog” to the designated target application consumer.
  • the current consumer has his/her dialog state completed as described with reference to FIG. 5 step 508 according to predefined logic specified in the business rule.
  • a dialog can contain dynamic content by enabling controller 604 to have access to data source 602 according to rules served by rule engine 603 .
  • dynamic content there are generally two types of dynamic content. Both types are, in preferred embodiments, structured in the form of XML and are embedded directly into the next generated dialog page.
  • the first of the 2 types of dynamic content is classified as non-recurring. Non-recurring content makes a relative reference to a non-recurring resource label in a resource adapter registry within a resource adapter analogous to adapter 113 of voice application server 110 described with reference to FIG. 1B.
  • dialog controller 604 interprets the dialog, it first scans for any resource label. If a match is found, it looks up the resource adapter registry and invokes the corresponding resource API to fetch the required data into the new dialog context. Once the raw data is returned from the third-party data source, it passes the raw data to a corresponding resource filter for further processing. When completed in terms of processing by the filter, the dialog resource label or tag is replaced with the filtered data and is integrated transparently into the new dialog.
  • the second type of dynamic content is recurring.
  • Recurring content usually returns more than one set of a name and value pair.
  • An example would be a list of stocks in an application consumer's stock portfolio.
  • a dialog that enables consumer 600 to parrot a specific stock and have the subsequent quote returned through another dialog state is made to use recurring dynamic content to achieve the desired result.
  • Recurring content makes a relative reference to a recurring resource label in the resource adapter registry of voice application server 110 .
  • controller 604 interprets the dialog, it handles the resource in an identical manner to handling of non-recurring content. However, instead of simply returning the filtered data back to the dialog context, it loops through the data list and configures each listed item as a grammar-enabled keyword.
  • consumer 600 can parrot one of the items (separate stocks) in the list played in the first dialog and have the response captured and processed for return in the next dialog state.
  • the stock-quote example presented below illustrates possible dialog/response interactions from the viewpoint of consumer 600 .
  • the first dialog plays out the statement “Good morning Leo, what stock quote do you want?”
  • the dialog is followed by a waiting state that listens for keywords such as Oracle, Sun, Microsoft, etc.
  • the statement consists of two dynamic non-recurring resource labels. The first one is the time in day: Good morning, good afternoon, or good evening.
  • the second dynamic content is the name of the application consumer. In this case, the name of the consumer is internal to the voice application server, thus the type of the resource label is SYSTEM. In the actual dialog description field, it may look something like this:
  • the dialog type is radio dialog
  • the expected response property of the radio dialog is
  • This XML resource label tells dialog controller 604 to look for a resource label named stock_list and to invoke the corresponding API with target_contact_id as the parameter.
  • the list of stocks is integrated into the dialog as part of the grammars. And whatever the user responds to in terms of stock identification is matched against the grammars at issue (stocks in portfolio) and assigned the grammar return value to the dialog response, which can then forward it to the next dialog as resource of DIALOG type.
  • the second dialog illustrated above plays out the quote of the stock selected from the first dialog, then returns the flow back to the first dialog.
  • the dialog type in this case is a statement dialog.
  • the dialog's follow-up action is simply to forward the flow back to the first dialog.
  • the dialog can also take in other resource types such as SOUND and SCRIPT.
  • FIGS. 7 - 15 illustrate various displayed Browser frames of a developer platform interface analogous to CL 141 of station 140 of FIG. 1B. Description of the following interface frames and frame contents assumes existence of a desktop computer host analogous to station 140 of FIG. 1B wherein interaction is enabled in HTTP request/response format as would be the case of developing over the Internet network for example. However, the following description should not limit the method and apparatus of the invention in any way as differing protocols, networks, interface designs and scope of operation can vary.
  • FIG. 7 is a plan view of a developer's frame containing a developer's login screen of 700 according to an embodiment of the present invention.
  • Frame 700 is presented to a developer in the form of a Web browser container according to one embodiment of the invention.
  • Commercial Web browsers are well known and any suitable Web browser will support the platform.
  • Frame 700 has all of the traditional Web options associated with most Web browser frames including back, forward, Go, File, Edit, View, and so on.
  • a navigation tool bar is visible in this example.
  • Screen 710 is a login page.
  • the developer may, in one embodiment, have a developer's account. In another case, more than one developer may share a single account. There are many possibilities.
  • Screen 710 has a field for inserting a login ID and a field for inserting a login personal identification number (PIN). Once login parameters are entered the developer submits the data by clicking on a button labeled Login. Screen 710 may be adapted for display on a desktop computer or any one of a number of other network capable devices following specified formats for display used on those particular devices.
  • PIN personal identification number
  • FIG. 8 is a plan view of a developer's frame 800 containing a screen shot of a home page of the developer's platform interface of FIG. 7.
  • Frame 800 contains a sectioned screen comprising a welcome section 801 , a product identification section 802 and a navigation section 803 combined to fill the total screen or display area.
  • a commercial name for a voice application developer's platform that is coined by the inventor is the name Fonelet.
  • Navigation section 803 is provided to display on the “home page” and on subsequent frames of the software tool.
  • Navigation section 803 contains, reading from top to bottom, a plurality of useful links. Starting with a link to home followed by a link to an address book. A link for creating a new Fonelet (voice application) is labeled Create New. A link to “My” Fonelets is provided as well as a link to “Options”. A standard Help link is illustrated along with a link to Logout. An additional “Options Menu” is the last illustrated link in section 803 . Section 803 may have additional links that are visible by scrolling down with the provided scroll bar traditional to the type of display of this example.
  • FIG. 9 is a plan view of a developer's frame 900 containing a screen shot of an address book 911 accessible through interaction with the option Address in section 803 of the previous frame of FIG. 8.
  • Screen 911 as an interactive option for listing individual contacts and for listing contact lists.
  • a contact list is a list of voice application consumers and a single contact represents one consumer in this example. However, in other embodiments a single contact may-mean more than one entity.
  • Navigation screen 803 is displayed on the left of screen 911 .
  • contacts are listed by First Name followed by Last Name, followed by a telephone number and an e-mail address.
  • Other contact parameters may also be included or excluded without departing from the spirit and scope of the invention.
  • the Web site of a contact may be listed and may also be the interface for receiving a voice application.
  • To the left of the listed contacts are interactive selection boxes used for selection and configuration purposes.
  • Interactive options are displayed in the form of Web buttons and adapted to enable a developer to add or delete contacts.
  • FIG. 10 is a plan view of a developer's frame 1000 displaying a screen 1001 for creating a new voice application.
  • Screen 1001 initiates creation of a new voice application termed a Fonelet by the inventor.
  • a name field 1002 is provided in screen 1001 for inputting a name for the application.
  • a description field 1003 is provided for the purpose of entering the applications description.
  • a property section 1004 is illustrated and adapted to enable a developer to select from available options listed as Public, Persistent, and Shareable by clicking on the appropriate check boxes.
  • a Dialog Flow Setup section is provided and contains a dialog type section field 1005 and a subsequent field for selecting a contact or contact group 1006 . After the required information is correctly populated into the appropriate fields, a developer may “create” the dialog by clicking on an interactive option 1007 labeled Create.
  • FIG. 11 is a plan view of a developer's frame 1100 illustrating screen 1001 of FIG. 10 showing further options as a result of scrolling down.
  • a calling schedule configuration section 1101 is illustrated and provides the interactive options of On Demand or Scheduled. As was previously described, selecting On Demand enables application deployment at the will of the developer while selecting scheduled initiates configuration for a scheduled deployment according to time/date parameters.
  • a grouping of entry fields 1102 is provided for configuring Time Zone and Month of launch.
  • a subsequent grouping of entry fields 1103 is provided for configuring the Day of Week and the Day of Month for the scheduled launch.
  • a subsequent grouping of entry fields 1104 is provided for configuring the hour and minute of the scheduled launch. It is noted herein that the options enable a repetitive launch of the same application. Once the developer finishes specifying the voice application shell, he or she can click a Create Dialog button labeled Create to spawn an overlying browser window for dialog creation.
  • FIG. 12 is a screen shot of a dialog configuration window 1200 illustrating a dialog configuration page according to an embodiment of the invention.
  • a developer configures the first dialog that the voice application or Fonelet will link to.
  • a dialog identification section 1201 is provided for the purpose of identifying and describing the dialog to be created.
  • a text entry field for entering a dialog name and a text entry field for entering dialog description are provided.
  • an XML resource tag (not shown) is inserted which for example, may refer to a resource label machine code registered with a resource adapter within the application server analogous to adapter 113 and application server 110 described with reference to FIG. 1B.
  • a section 1202 is provided within screen 1200 and adapted to enable a developer to configure for expected responses.
  • the type of dialog is a Radio Dialog.
  • Section 1202 serves as the business rule logic control for multiple choice-like dialogs.
  • Section 1202 contains a selection option for Response of Yes or No. It is noted herein that there may be more and different expected responses in addition to a simple yes or no response.
  • An adjacent section is provided within section 1202 for configuring any Follow-Up Action to occur as the result of an actual response to the dialog. For example, an option of selecting No Action is provided for each expected response of Yes and No. In the case of a follow-up action, an option for Connect is provided for each expected response. Adjacent to each illustrated Connect option, a Select field is provided for selecting a follow-up action, which may include fetching data.
  • a Send option is provided for enabling Send of the selected follow-up action including any embedded data.
  • a follow-up action may be any type of configured response such as send a new radio dialog, send a machine repair request, and so on.
  • a send to option and an associated select option is provided for identifying a recipient of a follow-up action and enabling automated send of the action to the recipient. For example, if a first dialog is a request for machine repair service sent to a plurality of internal repair technicians, then a follow-up might be to send the same dialog to the next available contact in the event the first contact refused to accept the job or was not available at the time of deployment.
  • the dialog may propagate from contact to contact down a list until one of the contacts is available and chooses to interact with the dialog by accepting the job.
  • a follow-up in this case may be to send a new dialog to the accepting contact detailing the parameters of which machine to repair including the diagnostic data of the problem and when the repair should take place.
  • an option for showing details is provide for developer review purposes.
  • interactive options for creating new or additional responses and for deleting existing responses from the system are provided. It is noted herein that once a dialog and dialog responses are created then they are reusable over the whole of the voice application and in any specified sequence in a voice application.
  • a section 1203 is provided within screen 1201 and adapted for handling Route-To Connection Exceptions.
  • This section enables a developer to configure what to de in case of possible connection states experience in application deployment. For example, for a Caller Reject, Line Busy, or connection to Voice Mail there are options for No Action and for Redial illustrated. It is noted herein that there may be more Exceptions as well as Follow-up action types than are illustrated in this example without departing from the spirit and scope of the present invention.
  • a Send option is provided for each type of exception for re-sending the same or any other dialog that may be selected from an adjacent drop down menu. For example if the first dialog is a request for repair services and all of the initial contacts are busy for example, the dialog may be sent back around to all of the contacts until one becomes available by first moving to a next contact for send after each busy signal and then beginning at the top of the list again on re-dial. In this case John Doe represents a next recipient after a precious contact rejects the dialog, is bust, or re-directs to voice mail because of unavailability. Section 1203 is only enabled when the voice application is set to outbound. Once the first dialog is created and enabled by the developer then a second dialog may be created if desired by clicking on one of the available buttons labeled detail. Also provided are interactive buttons for Save Dialog, Save and Close, and Undo Changes.
  • FIG. 13 is a screen shot 1300 of dialog design panel 1200 of FIG. 12 illustrating progression of dialog state to a subsequent contact.
  • the dialog state configured in the example of FIG. 12 is now transmitted from a contact listed in Route From to a contact listed in Route To in section 1301 , which is analogous to section 1201 of FIG. 12.
  • the contacts involved are John Doe and Jane Doe.
  • the dialog name and description are the same because the dialog is being re-used.
  • the developer does not have to re-enter any of the dialog context. However, because each dialog has a unique relationship with a recipient the developer must configure the corresponding business rules.
  • Sections 1302 and 1303 of this example are analogous to sections 1202 and 1203 of the previous example of FIG. 12.
  • John Doe says no to the request for machine repair then the system carries out a bridge transfer to Jane Doe.
  • Route-To Connection Exceptions region 1303 all the events are directed to a redialing routine.
  • the developer can create a custom thesaurus by clicking on a provided thesaurus icon not shown in this example. All the created vocabulary in a thesaurus can later be re-used throughout any voice applications the developer creates.
  • FIG. 14 is a screen shot of a thesaurus configuration window 1400 activated from the example of FIG. 13 according to a preferred embodiment.
  • Thesaurus window 1400 has a section 1401 containing a field for labeling a vocabulary word and an associated field for listing synonyms for the labeled word.
  • the word no is associated with probable responses no, nope, and the phrase “I can not make it”. In this way voice recognition regimens can be trained in a personalized fashion to accommodate for varieties in a response that might carry a same meaning.
  • a vocabulary section 1402 is provided and adapted to list all of the created vocabulary words for a voice application and a selection mechanism (a selection bar in this case) for selecting one of the listed words.
  • An option for creating a new word and synonym pair is also provided within section 1402 .
  • a control panel section 1403 is provided within window 1400 and adapted with the controls Select From Thesaurus; Update Thesaurus; Delete From Thesaurus; and Exit Thesaurus.
  • FIG. 15 is a plan view of a developer's frame 1500 illustrating a screen 1502 for managing created modules according to an embodiment of the present invention.
  • Screen 1502 displays as a result of clicking on the option “My” or My Fonelet in frame 803 .
  • Screen 1502 lists all voice applications that are already created and usable. In the list, each voice application has a check box adjacent thereto, which can be selected to change state of the particular application.
  • a column labeled Status is provided within screen 1502 and located adjacent to the application list applications already created.
  • the Status column lists the changeable state of each voice application. Available status options include but are not limited to listed states of Inactive, Activated and Inbound.
  • a column labeled Direct Access ID is provided adjacent to the Status column and is adapted to enable the developer to access a voice application directly through a voice interface in a PSTN network or in one embodiment from a DNT voice interface. In a PSTN embodiment, direct access ID capability serves as an extension of a central phone number.
  • a next column labeled Action is provided adjacent to the direct access ID column and is adapted to enable a developer to select and apply a specific action regarding state of a voice application.
  • FSC Field Support Center
  • the on-demand request is queued for dispatching through the system's outbound application server. For example, John Doe then receives a call originating from the voice application server ( 110 ) that asks if John wants to take the call. If John responds “Yes,” the voice application is executed.
  • the actual call flow follows:
  • System Carry out the bridge transfer between Jane Doe and Jeff Doe. When the conversation is completed, terminate the connection with Jeff and record the call flow to the data source.
  • the default textual content of the voice application is being generated by the text-to-speech engine hosted on the telephony or DNT server.
  • the voice application producer can access the voice portal through the PSTN or DNT server and record his/her voice over any existing prompts in the voice application.
  • the method and apparatus of the present invention may be practiced in conjunction with a CTI-enabled telephony environment wherein developer access to for application development is enabled through a client application running on a computerized station connected to a data network also having connectivity to the server spawning the application and telephony components.
  • the method and apparatus of the invention may also be practiced in a system that is DNT-based wherein the telephony server and application server are both connected to a data network such as the well-known Internet network.
  • There are applications for all mixes of communications environments including any suitable multi-tier system enabled for VXML and or other applicable mark-up languages that may serve similar purpose.
  • one or more Websites can be automatically harvested for data to be rendered by a VXML engine for generating a voice response accessible by users operating through a PSTN-based portal. Such an enhancement is described immediately below.
  • FIG. 16 is a block diagram illustrating the dialog transition flow of FIG. 6 enhanced for Web harvesting according to an embodiment of the present invention.
  • Dialog controller 604 is enhanced in this embodiment to access and harvest data from an HTML, WML, or other data source such as would be the case of data hosted on a Website.
  • An example scenario for this embodiment is that of a banking institution allowing all of its customers to access their Web site through a voice portal.
  • a Website 1600 is illustrated in this embodiment and is accessible to dialog controller 604 via a network access line 1601 illustrated herein as two directional lines of communication.
  • the first line is labeled Store/Fetch/Input leading from controller 604 into site 1600 .
  • the second (return) line is labeled Data Return/Source Field.
  • the separately illustrated communication lines are intended to be analogous to a bi-directional Internet or other network access line.
  • An internal data source ( 602 ) previously described with reference to FIG. 6 above is replaced in FIG. 16 by Website 1600 for explanatory purpose only. It should be noted that multiple data sources both internal to server 110 and external from server 110 could be simultaneously accessible to dialog controller 604 .
  • Website 1600 provides at least one electronic information page (Web page) that is formatted according to the existing rules for the mark-up language that is used for its creation and maintenance.
  • Site 1600 may be one site hosting many information pages, some of which are inter-related and accessible through subsequent navigation actions.
  • Controller 604 in this embodiment is enhanced for Website navigation at the direction of a user's voice inputs enabled by rule accessible by accessing rule engine 603 .
  • a data template (not shown) is provided for use by dialog controller 604 to facilitate logical data population from site 1600 .
  • Dialog controller 604 analyzes both Website source codes and data fields as return data and uses the information to generate a VXML page for rendering engine 111 .
  • FIG. 17 is a block diagram of the voice application distribution environment of FIG. 1B illustrating added components for automated Web harvesting and data rendering according to an embodiment of the present invention.
  • workstation 140 running client software 141 has direct access to a network server 1701 hosting the target Website 1600 .
  • Access is provided by way of an Internet access line 1704 .
  • a database store 1702 is provided in this example and illustrated as connected to server 1701 for the purpose of storing data.
  • Data store 1702 may be an optical storage, magnetic storage, a hard disk, or other forms suitable for storing data accessible online.
  • data store 1702 is a relational database management system (RDBMS) wherein a single access may involve one or more connected sub servers also storing data for access.
  • RDBMS relational database management system
  • client application 141 workstation 140 , server 1702 , Website 1600 , and database 1702 connected by network 1704 enables Websites analogous to site 1600 to be culled or harvested.
  • Application 141 can read and retrieve all of the default responses that exist for each HTML script or scripts of another mark-up language. These default responses are embedded into application logic 112 and VXML rendering engine 111 . Once the content of a Web page has been culled and used in client 141 to create the rendering, then VXML engine 111 can access the Website successfully in combination with application logic 112 and database/resource adaptor 113 by way of a separate access network 1703 .
  • Website 1600 For example, if a user (not shown) accesses Website 1600 through voice portal 143 from receiving device 135 (telephone), then he or she would be voice prompted for a password to gain access to the site. Subsequently, a voice rendering of the data on the site accessed would be recited to him or her over telephone 135 .
  • connection 1703 between server 110 and server 1701 enables the security environment practiced between communicating machines such a secure socket layer (SSL), firewall, etc to be applied in the created voice solution for a customer.
  • SSL secure socket layer
  • the security is no different than that of a call-in line allowing banking services in terms of wiretap possibilities etc.
  • the method and apparatus of the invention can be practiced in conjunction with the Internet, an Ethernet, or any other suitable networks.
  • Markup languages supported include HTML, SHTML, WML, VHTML, XML, VXML and so on.
  • the Websites accessed may be accessed automatically wherein the password information for a user is kept at the site itself. There are many possible scenarios.

Abstract

A system is provided for developing and deploying a voice application using Web-based data as source data over a communications network to one or more recipients. The system has a voice application server capable of accessing a network server and Website hosted therein, a network communications server for routing the voice applications to their intended recipients, and a computer station running voice application software having control access to at least the voice application server, the computer station capable of accessing the network server and Website. An operator of the computer station creates and provides templates for the voice application server to use in data-to-voice rendering.

Description

    CROSS-REFERENCE TO RELATED DOCUMENTS
  • The present invention is a continuation in part of a U.S. patent application, Attorney docket No. P8100 entitled “Method and Apparatus for Development and Deployment of a Voice Software Application for Distribution to one or more Application Consumers” filed on Jun. 14, 2002, disclosure of which is included herein in its entirety by reference. The parent case filed on Jun. 14, 2002 claimed priority to provisional application Serial No. 60/302,736 filed on Jul. 3, 2001, and incorporates all disclosure of that provisional application. The present application therefore claims priority to both of the applications described above in this paragraph.[0001]
  • FIELD OF THE INVENTION
  • The present invention is in the area of software application development and pertains particularly to methods and apparatus for auto harvesting template-based web content using a VXML-enabled voice portal system. [0002]
  • BACKGROUND OF THE INVENTION
  • A speech application is one of the most challenging applications to develop, deploy and maintain in a communications (typically telephony) environment. Expertise required for developing and deploying a viable application includes expertise in computer telephony integration (CTI) hardware and software, voice recognition software, text-to-speech software, and speech application logic. [0003]
  • With the relatively recent advent of voice extensive markup language (VXML) the expertise require to develop a speech solution has been reduced somewhat. VXML is a language that enables a software developer to focus on the application logic of the voice application without being required to configuring underlying telephony components. Typically, the developed voice application is run on a VXML interpreter that resides on and executes on the associated telephony system to deliver the solution. [0004]
  • As is shown in FIG. 1A (prior art) a typical architecture of a VXML-compliant telephony system comprises a voice application server ([0005] 110) and a VXML-compliant telephony server (130). Typical steps for development and deployment of a VXML enabled IVR solutions are briefly described below using the elements of FIG. 1A.
  • Firstly, a new application database ([0006] 113) is created or an existing one is modified to support VXML. Application logic 112 is designed in terms of workflow and adapted to handle the routing operations of the IVR system. VXML pages, which are results of functioning application logic, are rendered by a VXML rendering engine (111) based on a specified generation sequence.
  • Secondly, an object facade to [0007] server 130 is created comprising the corresponding VXML pages and is sent to server 130 over a network (120), which can be the Internet, an Intranet, or an Ethernet network. The VXML pages are integrated into rendering engine 111 such that they can be displayed according to set workflow at server 110.
  • Thirdly, the VXML-[0008] telephony server 130 is configured to enable proper retrieval of specific VXML pages from rendering engine 111 within server 110. A triggering mechanism is provided to server 110 so that when a triggering event occurs, an appropriate outbound call is placed from server 110.
  • A VXML interpreter ([0009] 131), a voice recognition text-to-speech engine (132), and the telephony hardware/software (133) are provided within server 130 and comprise server function. In prior art, the telephony hardware/software 130 along with the VXML interpreter 131 are packaged as an off-the-shelf IVR-enabling technology. Arguably the most important feature, however, of the entire system is the application server 110. The application logic (112) is typically written in a programming language such as Java and packaged as an enterprise Java Bean archive. The presentation logic required is handled by rendering engine 111 and is written in JSP or PERL.
  • An enhanced voice application system is known to the inventor and disclosed in the U.S. patent application entitled “Method and Apparatus for Development and Deployment of a Voice Software Application for Distribution to one or more Application Consumers” to which this application claims priority. That system uses a voice application server that is connected to a data network for storing and serving voice applications. The voice application server has a data connection to a network communications server connected to a communications network such as the well-known PSTN network. The communication server routes the created voice applications to their intended recipients. [0010]
  • A computer station is provided as part of the system and is connected to the data network and has access to the voice application server. A client software application is hosted on the computer station for the purpose of enabling users to create applications and manage their states. In this system, the user operates the client software hosted on the computer station in order to create voice applications through object modeling and linking. The applications, once created, are then stored in the application server for deployment. The user can control and manage deployment and state of deployed applications including scheduled deployment and repeat deployments in terms of intended recipients. [0011]
  • The system described above is quite advantageous in that a developer using the system need not be highly skilled in VXML language compilation, database programming, or advanced server design. Moreover, the system substantially reduces the amount of time allotted to project development. Still further, the system supports changes or modifications performed by anyone other than the developer without having to depend on the original author (because of his or her experience) to debug or make changes. [0012]
  • With the advent of the well known Internet network and growing technology to bridge two disparate networks such as the Internet and a PSTN network, the present inventors have concluded that Web data from Web sites should be a target data set for harvesting and conversion into a voice application that could then be routed to one or more users. [0013]
  • What is therefore clearly needed is a VMXL interface to a Web server that is capable of harvesting data from individual Web sites hosted on the server. [0014]
  • SUMMARY OF THE INVENTION
  • In a preferred embodiment of the present invention a system for developing and deploying a voice application using Web-based data as source data over a communications network to one or more recipients is provided, comprising a voice application server connected to a data network for storing and serving voice applications, the voice application server capable of accessing a network server and Website hosted therein, a network communications server connected to the data network and to the communications network for routing the voice applications to their intended recipients, a computer station connected to the data network having control access to at least the voice application server, the computer station capable of accessing the network server and Website hosted therein, and a software application running on the computer station for creating applications and managing their states. The system is characterized in that a developer operating the software application from the computer station accesses the target server and Website and creates at least one template for holding Web data according to logical order of site construction and links the templates to voice applications created by object modeling and linking, whereupon according to a triggering event, the triggered voice application accesses the intended Website and retrieves refreshed data from the site into the template and renders the retrieved data as voice delivered to intended recipients. [0015]
  • In a preferred embodiment the data network is the Internet network. Also in a preferred embodiment the voice application is delivered over a public-switched-telephony-network to a voice portal accessed by the intended recipients. [0016]
  • In some embodiments the security protocol used by the accessed Website is transferred as a voice access mechanism to the intended recipients. Also in some embodiments the data network connections of the computer station and of the voice application server are separate data network connections. In some cases the voice applications are scheduled for delivery at a specific time delivery made by outbound dialing and connection to a telephone of the intended recipient. The voice applications may be accessed by the intended recipients in real time. [0017]
  • In another aspect of the invention a voice application server for rendering voice dialog using Web-based data as source data is provided, comprising an instance of voice application development software, a database resource adapter, an instance of application logic; [0018]
  • a data rendering engine, and a network access line and software application for accessing servers and Websites hosted therein for the purpose of harvesting data there from for use in voice application creation and deployment. The server is characterized in that according to a trigger, the voice application server navigates to one or more servers and one or more Websites and obtains refreshed data there from converting the data to voice dialog and delivering the dialog to a voice portal accessible to an intended recipient. [0019]
  • In many preferred embodiments the network is the Internet network. Also in some preferred embodiments the voice application is delivered over a public-switched-telephony-network to a voice portal accessed by the intended recipients. In some cases the security protocol used by the accessed Website is transferred as a voice access mechanism to the intended recipients. Also in some cases the voice applications are scheduled for delivery at a specific time delivery made by outbound dialing and connection to a telephone of the intended recipient. The applications may be accessed by the intended recipients in real time. [0020]
  • In some embodiments of the invention a template is created for storing field and source data from a Website and the template is used in voice rendering in the server. The software for network access may be a browser application. [0021]
  • Embodiments of the invention taught in enabling detail below provide new and enhanced functionality for rendering information into audio form.[0022]
  • BRIEF DESCRIPTION OF THE DRAWING FIGURES
  • FIG. 1A is a block diagram illustrating a basic architecture of a VXML-enabled IVR development and deployment environment according to prior-art. [0023]
  • FIG. 1B is a block diagram illustrating the basic architecture of FIG. 1A enhanced to practice the present invention. [0024]
  • FIG. 2 is a process flow diagram illustrating steps for creating a voice application shell or container for a VXML voice application according to an embodiment of the present invention. [0025]
  • FIG. 3 is a block diagram illustrating a simple voice application container according to an embodiment of the present invention. [0026]
  • FIG. 4 is a block diagram illustrating a dialog object model according to an embodiment of the present invention. [0027]
  • FIG. 5 is a process flow diagram illustrating steps for voice dialog creation for a VXML-enabled voice application according to an embodiment of the present invention. [0028]
  • FIG. 6 is a block diagram illustrating a dialog transition flow after initial connection with a consumer according to an embodiment of the present invention. [0029]
  • FIG. 7 is a plan view of a developer's frame containing a developer's login screen of according to an embodiment of the present invention. [0030]
  • FIG. 8 is a plan view of a developer's frame containing a screen shot of a home page of the developer's platform interface of FIG. 7. [0031]
  • FIG. 9 is a plan view of a developer's frame containing a screen shot of an [0032] address book 911 accessible through interaction with the option Address in section 803 of the previous frame of FIG. 8.
  • FIG. 10 is a plan view of a developer's frame displaying a [0033] screen 1001 for creating a new voice application.
  • FIG. 11 is a plan view of a developer's frame illustrating screen of FIG. 10 showing further options as a result of scrolling down. [0034]
  • FIG. 12 is a screen shot of a dialog configuration window illustrating a dialog configuration page according to an embodiment of the invention. [0035]
  • FIG. 13 is a [0036] screen shot 1300 of dialog design panel of FIG. 12 illustrating progression of dialog state to a subsequent contact.
  • FIG. 14 is a screen shot of a thesaurus configuration window activated from the example of FIG. 13 according to a preferred embodiment. [0037]
  • FIG. 15 is a plan view of a developer's frame illustrating a screen for managing created modules according to an embodiment of the present invention. [0038]
  • FIG. 16 is a block diagram of the dialog transition flow of FIG. 6 enhanced for Web harvesting according to an embodiment of the present invention. [0039]
  • FIG. 17 is a block diagram of the voice application distribution environment of FIG. 1B illustrating added components for automated Web harvesting and data rendering according to an embodiment of the present invention. [0040]
  • DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • According to preferred embodiments of the present invention, the inventor teaches herein, in an enabling fashion, a novel system for developing and deploying real-time dynamic or static voice applications in an object-oriented way that enables inbound or outbound delivery of IVR and other interactive voice solutions in supported communications environments. [0041]
  • FIG. 1A is a block diagram illustrating a basic architecture of a VXML-enabled IVR development and deployment environment according to prior art. As described with reference to the background section, the prior-art architecture of this example is known to and available to the inventor. Developing and deploying voice applications for the illustrated environment, which in this case is a telephony environment, requires a very high level of skill in the art. Elements of this prior-art example that have already been introduced with respect to the background section of this specification shall not be re-introduced. [0042]
  • In this simplified scenario, [0043] voice application server 110 utilizes database/resource adapter 113 for accessing a database or other resources for content. Application logic 112 comprising VXML script, business rules, and underlying telephony logic must be carefully developed and tested before single applications can be rendered by rendering engine 111. Once voice applications are complete and servable from server 110, they can be deployed through data network 120 to telephony server 130 where interpreter 131 and text-to speech engine 132 are utilized to formulate and deliver the voice application in useable or playable format for telephony software and hardware 133. The applications are accessible to a receiving device, illustrated herein as device 135, a telephone, through the prevailing network 134, which is in this case a public-switched-telephone-network (PSTN) linking the telephony server to the consumer (device 135) generally through a telephony switch (not shown).
  • Improvements to this prior-art example in embodiments of the present invention concern and are focused in the capabilities of [0044] application server 110 with respect to development and deployment issues and with respect to overall enhancement to response capabilities and options in interaction dialog that is bi-directional. Using the description of existing architecture deemed state-of-art architecture, the inventor herein describes additional components that are not shown in the prior-art example of FIG. 1A, but are illustrated in a novel version of the example represented herein by FIG. 1B.
  • FIG. 1B is a block diagram illustrating the basic architecture of FIG. 1A enhanced to illustrate an embodiment of the present invention. Elements of the prior-art example of FIG. 1A that are also illustrated in FIG. 1B retain their original element numbers and are not re-introduced. For reference purposes an entity (a person) that develops a voice application shall be referred to hereinafter in this specification as either a producer or developer. [0045]
  • A developer or producer of a voice application according to an embodiment of the present invention operates preferably from a remote computerized workstation illustrated herein as [0046] station 140. Station 140 is essentially a network-connected computer station. Station 140 may be housed within the physical domain also housing application server 110. In another embodiment, station 140 and application server 110 may reside in the same machine. In yet another embodiment, a developer may operate station 140 from his or her home office or from any network-accessible location including any wireless location.
  • [0047] Station 140 is equipped with a client software tool (CL) 141, which is adapted to enable the developer to create and deploy voice applications across the prevailing system represented by servers 110, 130, and by receiving device 135. CL 141 is a Web interface application similar to or incorporated with a Web browser application in this example, however other network situations may apply instead. CL 141 contains the software tools required for the developer to enable enhancements according to embodiments of the invention. Station 140 is connected to a voice portal 143 that is maintained either on the data network (Internet, Ethernet, Intranet, etc.) and/or within telephony network 134. In this example portal 143 is illustrated logically in both networks. Voice portal 143 is adapted to enable a developer or a voice application consumer to call in and perform functional operations (such as access, monitor, modify) on selected voice applications.
  • Within [0048] application server 110 there is an instance of voice application development server 142 adapted in conjunction with the existing components 111-113 to provide dynamic voice application development and deployment according to embodiments of the invention.
  • [0049] Portal 143 is accessible via network connection to station 140 and via a network bridge to a voice application consumer through telephony network 134. In one example, portal 143 is maintained as part of application server 110. Portal 143 is, in addition to an access point for consumers is chiefly adapted as a developer's interface server. Portal 143 is enabled by a SW instance 144 adapted as a server instance to CL 141. In a telephony embodiment, portal 143 may be an interactive voice response (IVR) unit.
  • In a preferred embodiment, the producer or developer of a voice application accesses [0050] application server 110 through portal 143 and data network 120 using remote station 140 as a “Web interface” and first creates a list of contacts. In an alternative embodiment, station 140 has direct access to application server 110 through a network interface. Contacts are analogous to consumers of created voice applications. CL 141 displays, upon request and in order of need, all of the required interactive interfaces for designing, modifying, instantiating, and executing completed voice applications to launch from application server 110 and to be delivered by server 130.
  • The software of the present invention enables voice applications to be modeled as a set of dialog objects having business and telephony (or other communication delivery/access system) rules as parameters without requiring the developer to perform complicated coding operations. A dialog template is provided for modeling dialog states. The dialog template creates the actual speech dialog, specifies the voice application consumer (recipient) of the dialog, captures the response from the voice application consumer and performs any follow-up actions based upon system interpretation of the consumer response. A dialog is a reusable component and can be linked to a new dialog or to an existing (stored) dialog. A voice application is a set of dialogs inter-linked by a set of business rules defined by the voice application producer. Once the voice application is completed, it is deployed by [0051] server 110 and is eventually accessible to the authorized party (device 135) through telephony server 130.
  • The voice applications are in a preferred embodiment in the form of VXML to run on VXML-[0052] compliant telephony server 130. This process is enabled through VXML rendering engine 111. Engine 111 interacts directly with server 130, locates the voice application at issue, retrieves its voice application logic, and dynamically creates the presentation in VXML and forwards it to server 130 for processing and delivery. Once interpreter 131 interprets the VXML presentation it is sent to or accessible to device 135 in the form of an interactive dialog (in this case an IVR dialog). Any response from device 135 follows the same path back to application server 110 for interpretation by engine 111. Server 110 then retrieves the voice application profile from the database accessible through adapter 113 and determines the next business rule to execute locally. Based upon the determination a corresponding operation associated with the rule is taken. A next (if required) VXML presentation is then forwarded to rendering engine 111, which in turn dynamically generates the next VXML page for interpretation, processing and deployment at server 130. This two-way interaction between the VXML-compliant telephony server (130) and the voice application server (110) continues in the form of an automated logical sequence of VXML dialogs until the voice application finally reaches its termination state.
  • A voice application (set of one or more dialogs) can be delivered to the consumer (target audience) in outbound or inbound fashion. For an inbound voice application, a voice application consumer calls in to voice portal [0053] 143 to access the inbound voice application served from server 130. The voice portal can be mapped to a phone number directly or as an extension to a central phone number. In a preferred embodiment the voice portal also serves as a community forum where voice application producers can put their voice applications into groups for easy access and perform operational activities such as voice application linking, reporting, and text-to-speech recording and so on.
  • For an outbound voice application there are two sub-types. These are on-demand outbound applications and scheduled outbound applications. [0054]
  • For on-demand [0055] outbound applications server 110 generates an outbound call as soon as the voice application producer issues an outbound command associated with the application. The outbound call is made to the target audience and upon the receipt of the call the voice application is launched from server 130. For scheduled outbound applications, the schedule server (not shown within server 110) launches the voice application as soon as the producer-specified date and time has arrived. In a preferred embodiment both on-demand and scheduled outbound application deployment functions support unicast, multicast and broadcast delivery schemes.
  • As described above, a voice application created by [0056] application server 110 consists of one or more dialogs. The contents of each dialog can be static or dynamic. Static content is content sourcing from the voice application producer. The producer creates the contents when the voice application is created. Dynamic content sources from a third-party data source.
  • In a preferred embodiment a developers tool contains an interactive dialog design panel (described in detail later) wherein a producer inputs a reference link in the form of eXtensible Markup Language (XML) to the dialog description or response field. When a dialog response is executed and interpreted by [0057] application server 110, the reference link invokes a resource Application-Program-Interface (API) that is registered in resource adapter 113. The API goes out in real time and retrieves the requested data and integrates the returned data into the existing dialog. The resulting and subsequent VXML page being generated has the dynamic data embedded onto it.
  • One object of the present invention is a highly dynamic, real time IVR system that tailors itself automatically to the application developer's specified data source requirement. Another object of the present invention is to enable rapid development and deployment of a voice application without requirement of any prior knowledge of VXML or any other programming technologies. A further object of the present invention is to reduce the typical voice application production cycle and drastically reduce the cost of production. [0058]
  • FIG. 2 is a process flow diagram illustrating steps for creating a voice application shell or container for a VXML voice application according to an embodiment of the present invention. A developer utilizing a client application known as a thin client analogous to [0059] CL 141 on station 140 described with reference to FIG. 1b, creates a voice application shell or voice application container. At step 201 the developer logs in to the system at a login page. At step 202 the developer creates a contact list of application consumers. Typically a greeting or welcome page would be displayed before step 202. An application consumer is an audience of one or more entities that would have access to and interact with a voice application. A contact list is first created so that all of the intended contacts are available during voice application creation if call routing logic is required later on.
  • The contact list can either be entered individually in the event of more than one contact by the producer or may be imported as a set list from some organizer/planner software, such as Microsoft Outlook™ or perhaps a PDA™ organizer. [0060]
  • In one embodiment of the present invention the contact list may reside on an external device accessed by a provided connector (not shown) that is configured properly and adapted for the purpose of accessing and retrieving the list. This approach may be used, for example, if a large, existing customer database is used. Rather than create a copy, the needed data is extracted from the original and provided to the application. [0061]
  • At [0062] step 203, a voice application header is populated. A voice application header is simply a title field for the application. The field contains a name for the application and a description of the application. At step 204, the developer assigns either and inbound or outbound state for the voice application. An outbound application is delivered through an outbound call while the consumer accesses an inbound voice application.
  • In the case of the inbound application, in [0063] step 205 the system sets a default addressee for inbound communications. The developer selects a dialog from a configured list in step 206. It is assumed in this example that the dialogs have already been created. At step 207, the developer executes the dialog and it is deployed automatically.
  • In the case of an outbound designation in [0064] step 204, the developer chooses a launch type in step 208. A launch type can be either an on-demand type or a scheduled type. If the choice made by the developer in step 208 is scheduled, then in step 209, the developer enters all of the appropriate time and date parameters for the launch including parameters for recurring launches of the same application. In the case of an on demand selection for application launch in step 208, then in step 210 the developer selects one or more contacts from the contact list established in step 202. It is noted herein that step 210 is also undertaken by the developer after step 209 in the case of a scheduled launch. At step 207, the dialog is created. In this step a list of probable dialog responses for a voice application wherein interaction is intended may also be created and stored for use.
  • In general sequence, a developer creates a voice application and integrates the application with a backend data source or, optionally, any third party resources and deploys the voice application. The application consumer then consumes the voice application and optionally, the system analyzes any consumer feedback collected by the voice application for further interaction if appropriate. The steps of this example pertain to generating and launching a voice application from “building blocks” that are already in place. [0065]
  • FIG. 3 is a block diagram illustrating a simple [0066] voice application container 300 according to an embodiment of the present invention. Application container 300 is a logical container or “voice application object” 300. Also termed a shell, container 300 is logically illustrated as a possible result of the process of FIG. 2 above. Container 300 contains one or more dialog states illustrated herein as dialogs 301 a-n labeled in this example as dialogs 1-4. Dialogs 301 a-n are objects and therefore container 300 is a logical grouping of the set of dialog objects 301 a-n.
  • The represented set of dialog objects [0067] 301 a-n is interlinked by business rules labeled rules 1-4 in this example. Rules 1-4 are defined by the developer and are rule objects. It is noted herein that that there may be many more or fewer dialog objects 301 a-n as well as interlinking business rule objects 1-4 comprising container object 300 without departing from the spirit and scope of the present invention. The inventor illustrates 4 of each entity and deems the representation sufficient for the purpose of explaining the present invention.
  • In addition to the represented objects, [0068] voice application shell 300 includes a plurality of settings options. In this example, basic settings options are tabled for reference and given the element number 305 a-c illustrating 3 listed settings options. Reading in the table from top to bottom, a first setting launch type (305 a) defines an initial entry point for voice application 300 into the communications system. As described above with reference to FIG. 2 step 204, the choices for launch type 305 a are inbound or outbound. In an alternative embodiment, a launch type may be defined by a third party and be defined in some other pattern than inbound or outbound.
  • Outbound launch designation binds a voice application to one or more addressees (consumers). The addressee may be a single contact or a group of contacts represented by the contact list or distribution list also described with reference to FIG. 2 above (step [0069] 202). When the outbound voice application is launched in this case, it is delivered to the addressee designated on a voice application outbound contact field (not shown). All addressees designated receive a copy of the outbound voice application and have equal opportunity to interact (if allowed) with the voice application dialog and the corresponding backend data resources if they are used in the particular application.
  • In the case of an inbound voice application designation for [0070] launch type 305 a, the system instructs the application to assume a ready stand-by mode. The application is launched when the designated voice application consumer actively makes a request to access the voice application. A typical call center IVR system assumes this type of inbound application.
  • Launch time setting ([0071] 305 b) is only enabled as an option if the voice application launch type setting 305 a is set to outbound. The launch time setting is set to instruct a novel scheduling engine, which may be assumed to be part of the application server function described with reference to FIG. 1B. The scheduling engine controls the parameter of when to deliver of when to deliver the voice application to the designated addressees. The time setting may reflect on-demand, scheduled launch, or any third-party-defined patterns.
  • On-demand gives the developer full control over the launch time of the voice application. The on-demand feature also allows any third-party system to issue a trigger event to launch the voice application. It is noted herein that in the case of third-party control the voice application interaction may transcend more than one communications system and or network. [0072]
  • Property setting [0073] 305 c defines essentially how the voice application should behave in general. Possible state options for setting 305 c are public, persistent, or sharable. A public state setting indicates that the voice application should be accessible to anyone within the voice portal domain so that all consumers with minimum privilege can access the application. A persistent state setting for property 305 c ensures that only one copy of the voice application is ever active regardless of how many consumers are attempting to access the application. An example of such a scenario would be that of a task-allocation voice application. For example, in a task-allocation scenario there are only a number of time slots available for a user to access the application. If the task is a request from a pool of contacts such as perhaps customer-support technicians to lead a scheduled chat session, then whenever a time slot has been selected, the other technicians can only select the slots that are remaining. Therefore if there is only one copy of the voice application circulating within the pool of technicians, the application captures the technician's response on a first-come first-serve basis.
  • A sharable application state setting for [0074] property 305 a enables the consumer to “see” the responses of other technicians in the dialog at issue, regardless of whether the voice application is persistent or not. Once the voice application shell is created, the producer can then create the first dialog of the voice application as described with reference to FIG. 2 step 207. It is reminded herein that shell 300 is modeled using a remote and preferably a desktop client that will be described in more detail later in this specification.
  • FIG. 4 is a block diagram illustrating a [0075] dialog object model 400 according to an embodiment of the present invention. Dialog object model 400 is analogous to any of dialog objects 301 a-n described with reference to FIG. 3 above. Object 400 models a dialog and all of its properties. A properties object illustrated within dialog object 400 and labeled Object Properties (410) contains the dialog type and properties including behavior states and business rules that apply to the dialog.
  • For example, every dialog has a route-to property illustrated in the example as Route To property ([0076] 411). Property 411 maps to and identifies the source of the dialog. Similarly, every dialog has a route-from property illustrated herein as Route From property (412). Route from property 412 maps to and identifies the recipient contact of the dialog or the dialog consumer.
  • Every dialog falls under a dialog type illustrated in this example by a property labeled Dialog Type and given the [0077] element number 413. Dialog type 413 may include but is not limited to the following types of dialogs:
  • 1. Radio Dialog: A radio dialog allows a voice application consumer to interactively select one of available options from an option list after hearing the dialog description. [0078]
  • 2. Bulletin Dialog: A bulletin dialog allows a voice application consumer to interact with a bulletin board-like forum where multiple consumers can share voice messages in an asynchronous manner. [0079]
  • 3. Statement Dialog: A statement dialog plays out a statement to a voice application consumer without expecting any responses from the consumer. [0080]
  • 4. Open Entry Dialog: An open entry dialog allows a voice application consumer to record a message of a pre-defined length after hearing the dialog description. [0081]
  • 5. Third Party Dialog: A third party dialog is a modular container structure that allows the developer to create a custom-made dialog type with its own properties and behaviors. An example would be Nuance's SpeechObject™. [0082]
  • Each dialog type has one or more associated business rules tagged to it enabling determination of a next step in response to a perceived state. A rule compares the application consumer response with an operand defined by the application developer using an operational code such as less than, greater than, equal to, or not equal to. In a preferred embodiment of the invention the parameters surrounding a rule are as follows: [0083]
  • If user response is equal to the predefined value, then perform one of the following: [0084]
  • A. Do nothing and terminate the dialog state. [0085]
  • B. Do a live bridge transfer to the contact specified. Or, [0086]
  • C. Send another dialog to another contact. [0087]
  • In the case of an outbound voice application, there are likely to be exception-handling business rules associated with perceived states. In a preferred embodiment of the present invention, exception handling rules are encapsulated into three different events: [0088]
  • 1. An application consumer designated to receive the voice application rejects a request for interacting with the voice application. [0089]
  • 2. An application consumer has a busy connection at the time of launch of the voice application, for example, a telephone busy signal. And, [0090]
  • 3. An application consumer's connection is answered by or is redirected to a non-human device, for example, a telephone answering machine. [0091]
  • For each of the events above, any one of the three follow-up actions are possible according to perceived state: [0092]
  • 1. Do nothing and terminate the dialog state. [0093]
  • 2. Redial the number. [0094]
  • 3. Send another dialog to another contact. [0095]
  • FIG. 5 is a process flow diagram illustrating steps for voice dialog creation for a VXML-enabled voice application according to an embodiment of the present invention. All dialogs can be reused for subsequent dialog routing. There is, as previously described, a set of business rules for every dialog and contact pair. A dialog be active and be able to transit from one dialog state to another only when it is rule enabled. [0096]
  • At step [0097] 501 a developer populates a dialog description field with a dialog description. A dialog description may also contain reference to XML tags as will be described further below. At step 502, parameters of the dialog type are entered based on the assigned type of dialog. Examples of the available parameters were described with reference to FIG. 4 above.
  • At [0098] step 503 the developer configures the applicable business rules for the dialog type covering, as well, follow up routines. In one embodiment rules configuration at step 503 resolves to step 505 for determining follow-up routines based on the applied rules. For example, the developer may select at step 505, one of three types of transfers. For example, the developer may configure for a live transfer as illustrated by step 506; transfer to a next dialog for creation as illustrated by step 507; or the developer may configure for dialog completion as illustrated by step 508.
  • If the developer does not branch off into configuring [0099] sub-routines 506, 507, or 508 from step 505, but rather continues from step 503 to step 504 wherein inbound or outbound designation for the dialog is system assigned, then the process must branch from step 504 to either step 508 or 509, depending on whether the dialog is inbound or outbound. If at step 504, the dialog is inbound, then at step 508 the dialog is completed. If the assignment at step 504 is outbound, then at step 509 to configure call exception business rules.
  • At [0100] step 510, the developer configures at least one follow-up action for system handling of exceptions. If no follow-up actions are required to be specified at step 510, then the process resolves to step 508 for dialog completion. If an action or actions are configured at step 510, then at step 511 the action or actions are executed such as a system re-dial, which the illustrated action for step 511.
  • In a preferred embodiment, once the voice application has been created, it can be deployed and accessed through the telephone. The method of access, of course, depends on the assignment configured at [0101] step 504. For example, if the application is inbound, the application consumer accesses a voice portal to access the application. As described further above, a voice portal is a voice interface for accessing a selected number of functions of the voice application server described with reference to FIG. 1B above. A voice portal may be a connection-oriented-switched-telephony (COST) enabled portal or a data-network-telephony (DNT) enabled portal. In the case of an outbound designation at step 504, the application consumer receives the voice application through an incoming call to the consumer originated from the voice application server. In a preferred embodiment, the outbound call can be either COST based or DNT based depending on the communications environment supported.
  • FIG. 6 is a block diagram illustrating a dialog transition flow after initial connection with a consumer according to an embodiment of the present invention. Some of the elements illustrated in this example were previously introduced with respect to the example of FIG. 1B above and therefore shall retain their original element numbers. In this example, an application consumer is logically illustrated as [0102] Application Consumer 600 that is actively engaged in interaction with a dialog 601 hosted by telephony server 130. Server 130 is, as previously described a VMXL compliant telephony server as is so labeled.
  • [0103] Application server 110 is also actively engaged in the interaction sequence and has the capability to provide dynamic content to consumer 600. As application consumer 600 begins to interact with the voice application represented herein by dialog 600 within telephony server 130, voice application server 110 monitors the situation. In actual practice, each dialog processed and sent to server 130 for delivery to or access by consumer 600 is an atomic unit of the particular voice application being deployed and executed. Therefore dialog 601 may logically represent more than one single dialog.
  • In this example, assuming more than one dialog, [0104] dialog 601 is responsible during interaction for acquiring a response from consumer 600. Arrows labeled Send and Respond represent the described interaction. When consumer 600 responds to dialog content, the response is sent back along the same original path to VXML rendering engine 111, which interprets the response and forwards the interpreted version to a provided dialog controller 604. Controller 604 is part of application logic 112 in server 110 described with reference to FIG. 1B. Dialog controller 604 is a module that has the ability to perform table lookups, data retrieve and data write functions based on established rules and configured response parameters.
  • When [0105] dialog controller 604 receives a dialog response, it stores the response corresponding to the dialog at issue (601) to a provided data source 602 for data mining operations and workflow monitoring. Controller 604 then issues a request to a provided rules engine 603 to look-up the business rule or rules that correspond to the stored response. Once the correct business rule has been located for the response, the dialog controller starts interpretation. If the business rule accessed requires reference to a third-party data source (not shown), controller 604 makes the necessary data fetch from the source. Any data returned by controller 604 is integrated into the dialog context and passed onward VXML rendering engine 111 for dialog page generation of a next dialog 601. The process repeats until dialog 601 is terminates.
  • In one embodiment, the business rule accessed by [0106] controller 604 as a result of a received response from consumer 600 carries a dialog transition state other than back to the current application consumer. In this case controller 604 spawns an outbound call from application server 110 to deliver the next or “generated dialog” to the designated target application consumer. At the same time, the current consumer has his/her dialog state completed as described with reference to FIG. 5 step 508 according to predefined logic specified in the business rule.
  • It will be apparent to one with skill in the art that a dialog can contain dynamic content by enabling [0107] controller 604 to have access to data source 602 according to rules served by rule engine 603. In most embodiments there are generally two types of dynamic content. Both types are, in preferred embodiments, structured in the form of XML and are embedded directly into the next generated dialog page. The first of the 2 types of dynamic content is classified as non-recurring. Non-recurring content makes a relative reference to a non-recurring resource label in a resource adapter registry within a resource adapter analogous to adapter 113 of voice application server 110 described with reference to FIG. 1B.
  • In the above case, when [0108] dialog controller 604 interprets the dialog, it first scans for any resource label. If a match is found, it looks up the resource adapter registry and invokes the corresponding resource API to fetch the required data into the new dialog context. Once the raw data is returned from the third-party data source, it passes the raw data to a corresponding resource filter for further processing. When completed in terms of processing by the filter, the dialog resource label or tag is replaced with the filtered data and is integrated transparently into the new dialog.
  • The second type of dynamic content is recurring. Recurring content usually returns more than one set of a name and value pair. An example would be a list of stocks in an application consumer's stock portfolio. For example, a dialog that enables [0109] consumer 600 to parrot a specific stock and have the subsequent quote returned through another dialog state is made to use recurring dynamic content to achieve the desired result. Recurring content makes a relative reference to a recurring resource label in the resource adapter registry of voice application server 110. When controller 604 interprets the dialog, it handles the resource in an identical manner to handling of non-recurring content. However, instead of simply returning the filtered data back to the dialog context, it loops through the data list and configures each listed item as a grammar-enabled keyword. In so doing, consumer 600 can parrot one of the items (separate stocks) in the list played in the first dialog and have the response captured and processed for return in the next dialog state. The stock-quote example presented below illustrates possible dialog/response interactions from the viewpoint of consumer 600.
  • Voice Application: “Good morning Leo, what stock quote do you want?”[0110]
  • Application Consumer: “Oracle”[0111]
  • Voice Application: “Oracle is at seventeen dollars.”[0112]
  • Voice Application: “Good morning Leo, what stock quote do you want?”[0113]
  • This particular example consists of two dialogs. [0114]
  • The first dialog plays out the statement “Good morning Leo, what stock quote do you want?” The dialog is followed by a waiting state that listens for keywords such as Oracle, Sun, Microsoft, etc. The statement consists of two dynamic non-recurring resource labels. The first one is the time in day: Good morning, good afternoon, or good evening. The second dynamic content is the name of the application consumer. In this case, the name of the consumer is internal to the voice application server, thus the type of the resource label is SYSTEM. In the actual dialog description field, it may look something like this: [0115]
  • <resource type=‘ADAPTER’ name=‘time greeting’/><resource type=‘SYSTEM’ name=‘target_contact’/>, what stock quote do you want?[0116]
  • Because the dialog is expecting the consumer to say a stock out of his/her existing portfolio, the dialog type is radio dialog, and the expected response property of the radio dialog is [0117]
  • <resource type=‘ADAPTER’ name=‘stock_list’>[0118]
  • <param>[0119]
  • <resource type=‘SYSTEM’ name=‘target_contact_id’/>[0120]
  • </param>[0121]
  • </resource>[0122]
  • This XML resource label tells [0123] dialog controller 604 to look for a resource label named stock_list and to invoke the corresponding API with target_contact_id as the parameter. Upon completion of the data fetching, the list of stocks is integrated into the dialog as part of the grammars. And whatever the user responds to in terms of stock identification is matched against the grammars at issue (stocks in portfolio) and assigned the grammar return value to the dialog response, which can then forward it to the next dialog as resource of DIALOG type.
  • The producer can make reference to any dialog return values in any subsequent dialog by using <resource type=‘DIALOG’ name=‘dialog_name’/>. This rule enables the producer to play out the options the application consumer selected previously in any follow-up dialogs. [0124]
  • The second dialog illustrated above plays out the quote of the stock selected from the first dialog, then returns the flow back to the first dialog. Because no extra branching logic is involved in this dialog, the dialog type in this case is a statement dialog. The dialog's follow-up action is simply to forward the flow back to the first dialog. In such a case, the dialog statement is: <resource type=‘DIALOG’ name=‘select stock dialog’/>[0125]
  • <resource type=‘ADAPTER’ name=‘get_stock_quote’>[0126]
  • <param>[0127]
  • <resource type=‘DIALOG’ name=‘select stock dialog’/>[0128]
  • </param>[0129]
  • </resource>[0130]
  • Besides making reference to ADAPTER, DIALOG and SYSTEM type, the dialog can also take in other resource types such as SOUND and SCRIPT. SOUND can be used to impersonate the dialog description by inserting a sound clip into the dialog description. For example, to play a sound after the stock quote, the producer inserts <resource type=‘SOUND’ name=‘beep’/> right after the ADAPTER resource tag. [0131]
  • The producer can add a custom-made VXML script into the dialog description by using <resource type=‘RESOURCE’ name=‘confirm’/> so that in the preferred embodiment, any VXML can be integrated into the dialog context transparently with maximum flexibility and expandability. [0132]
  • It will be apparent to one with skill in the art that while the example cited herein use VXML and XML as the mark-up languages and tags, it is noted herein that other suitable markup languages can be utilized in place of or integrated with the mentioned conventions without departing from the spirit and scope of the invention. It will also be apparent to the skilled artisan that while the initial description of the invention is made in terms of a voice application server having interface to a telephony server using generally HTTP requests and responses, it should be noted that the present invention can be practiced in any system that is capable of handling well-defined requests and responses across any distributed network. [0133]
  • FIGS. [0134] 7-15 illustrate various displayed Browser frames of a developer platform interface analogous to CL 141 of station 140 of FIG. 1B. Description of the following interface frames and frame contents assumes existence of a desktop computer host analogous to station 140 of FIG. 1B wherein interaction is enabled in HTTP request/response format as would be the case of developing over the Internet network for example. However, the following description should not limit the method and apparatus of the invention in any way as differing protocols, networks, interface designs and scope of operation can vary.
  • FIG. 7 is a plan view of a developer's frame containing a developer's login screen of [0135] 700 according to an embodiment of the present invention. Frame 700 is presented to a developer in the form of a Web browser container according to one embodiment of the invention. Commercial Web browsers are well known and any suitable Web browser will support the platform. Frame 700 has all of the traditional Web options associated with most Web browser frames including back, forward, Go, File, Edit, View, and so on. A navigation tool bar is visible in this example. Screen 710 is a login page. The developer may, in one embodiment, have a developer's account. In another case, more than one developer may share a single account. There are many possibilities.
  • [0136] Screen 710 has a field for inserting a login ID and a field for inserting a login personal identification number (PIN). Once login parameters are entered the developer submits the data by clicking on a button labeled Login. Screen 710 may be adapted for display on a desktop computer or any one of a number of other network capable devices following specified formats for display used on those particular devices.
  • FIG. 8 is a plan view of a developer's [0137] frame 800 containing a screen shot of a home page of the developer's platform interface of FIG. 7. Frame 800 contains a sectioned screen comprising a welcome section 801, a product identification section 802 and a navigation section 803 combined to fill the total screen or display area. A commercial name for a voice application developer's platform that is coined by the inventor is the name Fonelet. Navigation section 803 is provided to display on the “home page” and on subsequent frames of the software tool.
  • [0138] Navigation section 803 contains, reading from top to bottom, a plurality of useful links. Starting with a link to home followed by a link to an address book. A link for creating a new Fonelet (voice application) is labeled Create New. A link to “My” Fonelets is provided as well as a link to “Options”. A standard Help link is illustrated along with a link to Logout. An additional “Options Menu” is the last illustrated link in section 803. Section 803 may have additional links that are visible by scrolling down with the provided scroll bar traditional to the type of display of this example.
  • FIG. 9 is a plan view of a developer's [0139] frame 900 containing a screen shot of an address book 911 accessible through interaction with the option Address in section 803 of the previous frame of FIG. 8. Screen 911 as an interactive option for listing individual contacts and for listing contact lists. A contact list is a list of voice application consumers and a single contact represents one consumer in this example. However, in other embodiments a single contact may-mean more than one entity. Navigation screen 803 is displayed on the left of screen 911. In this example, contacts are listed by First Name followed by Last Name, followed by a telephone number and an e-mail address. Other contact parameters may also be included or excluded without departing from the spirit and scope of the invention. For example the Web site of a contact may be listed and may also be the interface for receiving a voice application. To the left of the listed contacts are interactive selection boxes used for selection and configuration purposes. Interactive options are displayed in the form of Web buttons and adapted to enable a developer to add or delete contacts.
  • FIG. 10 is a plan view of a developer's [0140] frame 1000 displaying a screen 1001 for creating a new voice application. Screen 1001 initiates creation of a new voice application termed a Fonelet by the inventor. A name field 1002 is provided in screen 1001 for inputting a name for the application. A description field 1003 is provided for the purpose of entering the applications description. A property section 1004 is illustrated and adapted to enable a developer to select from available options listed as Public, Persistent, and Shareable by clicking on the appropriate check boxes.
  • A Dialog Flow Setup section is provided and contains a dialog [0141] type section field 1005 and a subsequent field for selecting a contact or contact group 1006. After the required information is correctly populated into the appropriate fields, a developer may “create” the dialog by clicking on an interactive option 1007 labeled Create.
  • FIG. 11 is a plan view of a developer's [0142] frame 1100 illustrating screen 1001 of FIG. 10 showing further options as a result of scrolling down. A calling schedule configuration section 1101 is illustrated and provides the interactive options of On Demand or Scheduled. As was previously described, selecting On Demand enables application deployment at the will of the developer while selecting scheduled initiates configuration for a scheduled deployment according to time/date parameters. A grouping of entry fields 1102 is provided for configuring Time Zone and Month of launch. A subsequent grouping of entry fields 1103 is provided for configuring the Day of Week and the Day of Month for the scheduled launch. A subsequent grouping of entry fields 1104 is provided for configuring the hour and minute of the scheduled launch. It is noted herein that the options enable a repetitive launch of the same application. Once the developer finishes specifying the voice application shell, he or she can click a Create Dialog button labeled Create to spawn an overlying browser window for dialog creation.
  • FIG. 12 is a screen shot of a [0143] dialog configuration window 1200 illustrating a dialog configuration page according to an embodiment of the invention. In this window a developer configures the first dialog that the voice application or Fonelet will link to. A dialog identification section 1201 is provided for the purpose of identifying and describing the dialog to be created. A text entry field for entering a dialog name and a text entry field for entering dialog description are provided. Within the dialog description field, an XML resource tag (not shown) is inserted which for example, may refer to a resource label machine code registered with a resource adapter within the application server analogous to adapter 113 and application server 110 described with reference to FIG. 1B.
  • [0144] A section 1202 is provided within screen 1200 and adapted to enable a developer to configure for expected responses. In this case the type of dialog is a Radio Dialog. Section 1202 serves as the business rule logic control for multiple choice-like dialogs. Section 1202 contains a selection option for Response of Yes or No. It is noted herein that there may be more and different expected responses in addition to a simple yes or no response.
  • An adjacent section is provided within [0145] section 1202 for configuring any Follow-Up Action to occur as the result of an actual response to the dialog. For example, an option of selecting No Action is provided for each expected response of Yes and No. In the case of a follow-up action, an option for Connect is provided for each expected response. Adjacent to each illustrated Connect option, a Select field is provided for selecting a follow-up action, which may include fetching data.
  • A Send option is provided for enabling Send of the selected follow-up action including any embedded data. A follow-up action may be any type of configured response such as send a new radio dialog, send a machine repair request, and so on. A send to option and an associated select option is provided for identifying a recipient of a follow-up action and enabling automated send of the action to the recipient. For example, if a first dialog is a request for machine repair service sent to a plurality of internal repair technicians, then a follow-up might be to send the same dialog to the next available contact in the event the first contact refused to accept the job or was not available at the time of deployment. [0146]
  • In the above case, the dialog may propagate from contact to contact down a list until one of the contacts is available and chooses to interact with the dialog by accepting the job. A follow-up in this case may be to send a new dialog to the accepting contact detailing the parameters of which machine to repair including the diagnostic data of the problem and when the repair should take place. In this example, an option for showing details is provide for developer review purposes. Also interactive options for creating new or additional responses and for deleting existing responses from the system are provided. It is noted herein that once a dialog and dialog responses are created then they are reusable over the whole of the voice application and in any specified sequence in a voice application. [0147]
  • [0148] A section 1203 is provided within screen 1201 and adapted for handling Route-To Connection Exceptions. This section enables a developer to configure what to de in case of possible connection states experience in application deployment. For example, for a Caller Reject, Line Busy, or connection to Voice Mail there are options for No Action and for Redial illustrated. It is noted herein that there may be more Exceptions as well as Follow-up action types than are illustrated in this example without departing from the spirit and scope of the present invention.
  • A Send option is provided for each type of exception for re-sending the same or any other dialog that may be selected from an adjacent drop down menu. For example if the first dialog is a request for repair services and all of the initial contacts are busy for example, the dialog may be sent back around to all of the contacts until one becomes available by first moving to a next contact for send after each busy signal and then beginning at the top of the list again on re-dial. In this case John Doe represents a next recipient after a precious contact rejects the dialog, is bust, or re-directs to voice mail because of unavailability. [0149] Section 1203 is only enabled when the voice application is set to outbound. Once the first dialog is created and enabled by the developer then a second dialog may be created if desired by clicking on one of the available buttons labeled detail. Also provided are interactive buttons for Save Dialog, Save and Close, and Undo Changes.
  • FIG. 13 is a [0150] screen shot 1300 of dialog design panel 1200 of FIG. 12 illustrating progression of dialog state to a subsequent contact. The dialog state configured in the example of FIG. 12 is now transmitted from a contact listed in Route From to a contact listed in Route To in section 1301, which is analogous to section 1201 of FIG. 12. In this case, the contacts involved are John Doe and Jane Doe. In this case, the dialog name and description are the same because the dialog is being re-used. The developer does not have to re-enter any of the dialog context. However, because each dialog has a unique relationship with a recipient the developer must configure the corresponding business rules.
  • [0151] Sections 1302 and 1303 of this example are analogous to sections 1202 and 1203 of the previous example of FIG. 12. In this case if John Doe says no to the request for machine repair then the system carries out a bridge transfer to Jane Doe. In the case of exceptions, shown in Route-To Connection Exceptions region 1303, all the events are directed to a redialing routine. In addition to inserting keywords such as “Yes” or “No” in the response field 1302, the developer can create a custom thesaurus by clicking on a provided thesaurus icon not shown in this example. All the created vocabulary in a thesaurus can later be re-used throughout any voice applications the developer creates.
  • FIG. 14 is a screen shot of a [0152] thesaurus configuration window 1400 activated from the example of FIG. 13 according to a preferred embodiment. Thesaurus window 1400 has a section 1401 containing a field for labeling a vocabulary word and an associated field for listing synonyms for the labeled word. In this example, the word no is associated with probable responses no, nope, and the phrase “I can not make it”. In this way voice recognition regimens can be trained in a personalized fashion to accommodate for varieties in a response that might carry a same meaning.
  • A [0153] vocabulary section 1402 is provided and adapted to list all of the created vocabulary words for a voice application and a selection mechanism (a selection bar in this case) for selecting one of the listed words. An option for creating a new word and synonym pair is also provided within section 1402. A control panel section 1403 is provided within window 1400 and adapted with the controls Select From Thesaurus; Update Thesaurus; Delete From Thesaurus; and Exit Thesaurus.
  • FIG. 15 is a plan view of a developer's [0154] frame 1500 illustrating a screen 1502 for managing created modules according to an embodiment of the present invention.
  • After closing all [0155] dialog windows frame 1500 displays screen or page 1502 for module management options. Menu section 803 is again visible.
  • [0156] Screen 1502 displays as a result of clicking on the option “My” or My Fonelet in frame 803. Screen 1502 lists all voice applications that are already created and usable. In the list, each voice application has a check box adjacent thereto, which can be selected to change state of the particular application. A column labeled Status is provided within screen 1502 and located adjacent to the application list applications already created.
  • The Status column lists the changeable state of each voice application. Available status options include but are not limited to listed states of Inactive, Activated and Inbound. A column labeled Direct Access ID is provided adjacent to the Status column and is adapted to enable the developer to access a voice application directly through a voice interface in a PSTN network or in one embodiment from a DNT voice interface. In a PSTN embodiment, direct access ID capability serves as an extension of a central phone number. A next column labeled Action is provided adjacent to the direct access ID column and is adapted to enable a developer to select and apply a specific action regarding state of a voice application. [0157]
  • For example, assume that a developer has just finished the voice application identified as Field Support Center (FSC) listed at the top of the application identification list. Currently, the listed state of FSC is Inactive. The developer now activates the associated Action drop down menu and selects Activate to launch the application FSC on demand. In the case of a scheduled launch, the voice application is activated automatically according to the settings defined in the voice application shell. [0158]
  • As soon as the Activate command has been issued, the on-demand request is queued for dispatching through the system's outbound application server. For example, John Doe then receives a call originating from the voice application server ([0159] 110) that asks if John wants to take the call. If John responds “Yes,” the voice application is executed. The actual call flow follows:
  • System: “Hello John, you received a fonelet from Jim Doe, would you like to take this call?”[0160]
  • John: “Yes.”[0161]
  • System: “Machine number 008 is broken, are you available to fix it?”[0162]
  • John: “No.”[0163]
  • System: “Thanks for using fonelet. Goodbye!”[0164]
  • System: Terminate the connection with John, record the call flow to the data source, and spawn a new call to Jane Doe. [0165]
  • System: “Hello Jane, you received a fonelet from Jim Doe, would you like to take this call?”[0166]
  • Jane: “Yes.”[0167]
  • System: “Machine number [0168] 008 is broken, are you available to fix it?”
  • Jane: “I cannot make it.”[0169]
  • System: “Please wait while fonelet transfers you to Jeff Doe.”[0170]
  • System: Carry out the bridge transfer between Jane Doe and Jeff Doe. When the conversation is completed, terminate the connection with Jeff and record the call flow to the data source. [0171]
  • The default textual content of the voice application is being generated by the text-to-speech engine hosted on the telephony or DNT server. However, the voice application producer can access the voice portal through the PSTN or DNT server and record his/her voice over any existing prompts in the voice application. [0172]
  • It will be apparent to one with skill in the art the method and apparatus of the present invention may be practiced in conjunction with a CTI-enabled telephony environment wherein developer access to for application development is enabled through a client application running on a computerized station connected to a data network also having connectivity to the server spawning the application and telephony components. The method and apparatus of the invention may also be practiced in a system that is DNT-based wherein the telephony server and application server are both connected to a data network such as the well-known Internet network. There are applications for all mixes of communications environments including any suitable multi-tier system enabled for VXML and or other applicable mark-up languages that may serve similar purpose. It will also be apparent to one with skill in the art that modeling voice applications including individual dialogs and responses enables any developer to create a limitless variety of voice application quickly by reusing existing objects in modular fashion thereby enabling a wide range of useful applications from an existing store of objects. [0173]
  • Auto-Harvesting Web Data [0174]
  • In one embodiment of the present invention one or more Websites can be automatically harvested for data to be rendered by a VXML engine for generating a voice response accessible by users operating through a PSTN-based portal. Such an enhancement is described immediately below. [0175]
  • FIG. 16 is a block diagram illustrating the dialog transition flow of FIG. 6 enhanced for Web harvesting according to an embodiment of the present invention. [0176] Dialog controller 604 is enhanced in this embodiment to access and harvest data from an HTML, WML, or other data source such as would be the case of data hosted on a Website. An example scenario for this embodiment is that of a banking institution allowing all of its customers to access their Web site through a voice portal.
  • A [0177] Website 1600 is illustrated in this embodiment and is accessible to dialog controller 604 via a network access line 1601 illustrated herein as two directional lines of communication. The first line is labeled Store/Fetch/Input leading from controller 604 into site 1600. The second (return) line is labeled Data Return/Source Field. The separately illustrated communication lines are intended to be analogous to a bi-directional Internet or other network access line. An internal data source (602) previously described with reference to FIG. 6 above is replaced in FIG. 16 by Website 1600 for explanatory purpose only. It should be noted that multiple data sources both internal to server 110 and external from server 110 could be simultaneously accessible to dialog controller 604.
  • [0178] Website 1600 provides at least one electronic information page (Web page) that is formatted according to the existing rules for the mark-up language that is used for its creation and maintenance. Site 1600 may be one site hosting many information pages, some of which are inter-related and accessible through subsequent navigation actions. Controller 604 in this embodiment is enhanced for Website navigation at the direction of a user's voice inputs enabled by rule accessible by accessing rule engine 603. A data template (not shown) is provided for use by dialog controller 604 to facilitate logical data population from site 1600. Dialog controller 604 analyzes both Website source codes and data fields as return data and uses the information to generate a VXML page for rendering engine 111.
  • It is noted herein that all of the security and access mechanisms used at the site for normal Internet access are inferred upon the customer so that the customer may be granted access by providing a voice rendering (response) containing the security access information. This enables the customer to keep the same security password and/or personal identification number (PIN) for voice transactions through a portal as well as for normal Web access to [0179] site 1600 from a network-connected computer.
  • FIG. 17 is a block diagram of the voice application distribution environment of FIG. 1B illustrating added components for automated Web harvesting and data rendering according to an embodiment of the present invention. In this example, [0180] workstation 140 running client software 141 has direct access to a network server 1701 hosting the target Website 1600. Access is provided by way of an Internet access line 1704.
  • It is noted herein that there may be [0181] many servers 1701 as well as many hosted Websites of one or more pages in this embodiment without departing from the spirit and scope of the present invention. A database store 1702 is provided in this example and illustrated as connected to server 1701 for the purpose of storing data. Data store 1702 may be an optical storage, magnetic storage, a hard disk, or other forms suitable for storing data accessible online. In one embodiment, data store 1702 is a relational database management system (RDBMS) wherein a single access may involve one or more connected sub servers also storing data for access.
  • The configuration of [0182] client application 141, workstation 140, server 1702, Website 1600, and database 1702 connected by network 1704 enables Websites analogous to site 1600 to be culled or harvested. Application 141 can read and retrieve all of the default responses that exist for each HTML script or scripts of another mark-up language. These default responses are embedded into application logic 112 and VXML rendering engine 111. Once the content of a Web page has been culled and used in client 141 to create the rendering, then VXML engine 111 can access the Website successfully in combination with application logic 112 and database/resource adaptor 113 by way of a separate access network 1703. For example, if a user (not shown) accesses Website 1600 through voice portal 143 from receiving device 135 (telephone), then he or she would be voice prompted for a password to gain access to the site. Subsequently, a voice rendering of the data on the site accessed would be recited to him or her over telephone 135.
  • Generally speaking, the development process for a voice portal would be the same as was described above with references to FIGS. [0183] 9-15 above. Some additional scripting or input of dialog is performed using client application 141. Rather that requiring that the application developer populate all of the fields from scratch, or re-apply previously entered options, fields used by the business logic as discussed earlier in FIGS. 9 through 15 may be created from information harvested from site 1600 in this case. For that purpose, a software adapter (not shown) is added to client software 141 that allows it to communicate with Web site 1600 and harvest the information, both from the source code comprising fields and labels, etc. as well as from data parameters and data variables.
  • It is noted herein that the process for data access, retrieval and voice rendering is essentially the same with respect to the processes of FIGS. [0184] 2-5 above except that a Website connection would be established before any other options are selected.
  • In one embodiment, provision of [0185] connection 1703 between server 110 and server 1701 enables the security environment practiced between communicating machines such a secure socket layer (SSL), firewall, etc to be applied in the created voice solution for a customer. On the analog side, the security is no different than that of a call-in line allowing banking services in terms of wiretap possibilities etc.
  • It will be apparent to one with skill in the art that the method and apparatus of the invention can be practiced in conjunction with the Internet, an Ethernet, or any other suitable networks. Markup languages supported include HTML, SHTML, WML, VHTML, XML, VXML and so on. In one embodiment, the Websites accessed may be accessed automatically wherein the password information for a user is kept at the site itself. There are many possible scenarios. [0186]
  • The method and apparatus of the invention should be afforded to broadest interpretation under examination in view of the many possible embodiments and uses. The spirit and scope of the invention is limited only be the claims that follow. [0187]

Claims (15)

What is claimed is:
1. A system for developing and deploying a voice application using Web-based data as source data over a communications network to one or more recipients, comprising:
a voice application server connected to a data network for storing and serving voice applications, the voice application server capable of accessing a network server and Website hosted therein;
a network communications server connected to the data network and to the communications network for routing the voice applications to their intended recipients;
a computer station connected to the data network having control access to at least the voice application server, the computer station capable of accessing the network server and Website hosted therein; and
a software application running on the computer station for creating applications and managing their states;
characterized in that a developer operating the software application from the computer station accesses the target server and Website and creates at least one template for holding Web data according to logical order of site construction and links the templates to voice applications created by object modeling and linking, whereupon according to a triggering event, the triggered voice application accesses the intended Website and retrieves refreshed data from the site into the template and renders the retrieved data as voice delivered to intended recipients.
2. The system of claim 1 wherein the data network is the Internet network.
3. The system of claim 1 wherein the voice application is delivered over a public-switched-telephony-network to a voice portal accessed by the intended recipients.
4. The system of claim 1 wherein the security protocol used by the accessed Website is transferred as a voice access mechanism to the intended recipients.
5. The system of claim 1 wherein the data network connections of the computer station and of the voice application server are separate data network connections.
6. The system of claim 3 wherein the voice applications are scheduled for delivery at a specific time delivery made by outbound dialing and connection to a telephone of the intended recipient.
7. The system of claim 3 wherein the voice applications are accessed by the intended recipients in real time.
8. A voice application server for rendering voice dialog using Web-based data as source data comprising:
an instance of voice application development software;
a database resource adapter;
an instance of application logic;
a data rendering engine; and
a network access line and software application for accessing servers and Websites hosted therein for the purpose of harvesting data there from for use in voice application creation and deployment;
characterized in that according to a trigger, the voice application server navigates to one or more servers and one or more Websites and obtains refreshed data there from converting the data to voice dialog and delivering the dialog to a voice portal accessible to an intended recipient.
9. The voice application server of claim 8 wherein the network is the Internet network.
10. The voice application server of claim 8 wherein the voice application is delivered over a public-switched-telephony-network to a voice portal accessed by the intended recipients.
11. The voice application server of claim 8 wherein the security protocol used by the accessed Website is transferred as a voice access mechanism to the intended recipients.
12. The voice application server of claim 10 wherein the voice applications are scheduled for delivery at a specific time delivery made by outbound dialing and connection to a telephone of the intended recipient.
13. The voice application server of claim 10 wherein the voice applications are accessed by the intended recipients in real time.
14. The voice application server of claim 8 wherein a template is created for storing field and source data from a Website, the template used in voice rendering in the server.
15. The voice application server of claim 8 wherein the software for network access is a browser application.
US10/190,077 2001-07-03 2002-07-02 Method for automated harvesting of data from a Web site using a voice portal system Abandoned US20030055884A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US10/190,077 US20030055884A1 (en) 2001-07-03 2002-07-02 Method for automated harvesting of data from a Web site using a voice portal system
US11/036,293 US20050149331A1 (en) 2002-06-14 2005-01-13 Method and system for developing speech applications
US12/490,177 US20100057885A1 (en) 2001-07-03 2009-06-23 Method for Automated Harvesting of Data from A Web site using a Voice Portal System
US12/490,194 US20100050150A1 (en) 2002-06-14 2009-06-23 Method and System for Developing Speech Applications

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US30273601P 2001-07-03 2001-07-03
US10/173,333 US20030007609A1 (en) 2001-07-03 2002-06-14 Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers
US10/190,077 US20030055884A1 (en) 2001-07-03 2002-07-02 Method for automated harvesting of data from a Web site using a voice portal system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/173,333 Continuation-In-Part US20030007609A1 (en) 2001-07-03 2002-06-14 Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US11/036,293 Continuation US20050149331A1 (en) 2002-06-14 2005-01-13 Method and system for developing speech applications
US12/490,177 Continuation US20100057885A1 (en) 2001-07-03 2009-06-23 Method for Automated Harvesting of Data from A Web site using a Voice Portal System

Publications (1)

Publication Number Publication Date
US20030055884A1 true US20030055884A1 (en) 2003-03-20

Family

ID=26869030

Family Applications (11)

Application Number Title Priority Date Filing Date
US10/173,333 Abandoned US20030007609A1 (en) 2001-07-03 2002-06-14 Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers
US10/190,080 Expired - Lifetime US7643998B2 (en) 2001-07-03 2002-07-02 Method and apparatus for improving voice recognition performance in a voice application distribution system
US10/190,077 Abandoned US20030055884A1 (en) 2001-07-03 2002-07-02 Method for automated harvesting of data from a Web site using a voice portal system
US10/190,104 Abandoned US20030018476A1 (en) 2001-07-03 2002-07-02 Method and apparatus for configuring harvested web data for use by a VXML rendering engine for distribution to users accessing a voice portal system
US10/190,413 Abandoned US20030014670A1 (en) 2001-07-03 2002-07-03 Method and apparatus for enhancing security between a Web server and a PSTN-based voice portal
US12/490,177 Abandoned US20100057885A1 (en) 2001-07-03 2009-06-23 Method for Automated Harvesting of Data from A Web site using a Voice Portal System
US12/542,510 Abandoned US20100050265A1 (en) 2001-07-03 2009-08-17 Method and Apparatus for Enhancing Security Between a Web Server and a PSTN-based Voice Portal
US12/643,858 Abandoned US20100114578A1 (en) 2001-07-03 2009-12-21 Method and Apparatus for Improving Voice recognition performance in a voice application distribution system
US12/756,133 Abandoned US20100318365A1 (en) 2001-07-03 2010-04-07 Method and Apparatus for Configuring Web-based data for Distribution to Users Accessing a Voice Portal System
US12/777,138 Abandoned US20110123006A1 (en) 2001-07-03 2010-05-10 Method and Apparatus for Development, Deployment, and Maintenance of a Voice Software Application for Distribution to One or More Consumers
US13/616,863 Abandoned US20130013299A1 (en) 2001-07-03 2012-09-14 Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10/173,333 Abandoned US20030007609A1 (en) 2001-07-03 2002-06-14 Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers
US10/190,080 Expired - Lifetime US7643998B2 (en) 2001-07-03 2002-07-02 Method and apparatus for improving voice recognition performance in a voice application distribution system

Family Applications After (8)

Application Number Title Priority Date Filing Date
US10/190,104 Abandoned US20030018476A1 (en) 2001-07-03 2002-07-02 Method and apparatus for configuring harvested web data for use by a VXML rendering engine for distribution to users accessing a voice portal system
US10/190,413 Abandoned US20030014670A1 (en) 2001-07-03 2002-07-03 Method and apparatus for enhancing security between a Web server and a PSTN-based voice portal
US12/490,177 Abandoned US20100057885A1 (en) 2001-07-03 2009-06-23 Method for Automated Harvesting of Data from A Web site using a Voice Portal System
US12/542,510 Abandoned US20100050265A1 (en) 2001-07-03 2009-08-17 Method and Apparatus for Enhancing Security Between a Web Server and a PSTN-based Voice Portal
US12/643,858 Abandoned US20100114578A1 (en) 2001-07-03 2009-12-21 Method and Apparatus for Improving Voice recognition performance in a voice application distribution system
US12/756,133 Abandoned US20100318365A1 (en) 2001-07-03 2010-04-07 Method and Apparatus for Configuring Web-based data for Distribution to Users Accessing a Voice Portal System
US12/777,138 Abandoned US20110123006A1 (en) 2001-07-03 2010-05-10 Method and Apparatus for Development, Deployment, and Maintenance of a Voice Software Application for Distribution to One or More Consumers
US13/616,863 Abandoned US20130013299A1 (en) 2001-07-03 2012-09-14 Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers

Country Status (5)

Country Link
US (11) US20030007609A1 (en)
EP (1) EP1428203A4 (en)
CN (1) CN1522432A (en)
CA (1) CA2450887A1 (en)
WO (1) WO2003005340A2 (en)

Cited By (57)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040019638A1 (en) * 1998-09-11 2004-01-29 Petr Makagon Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US20040027379A1 (en) * 2002-08-08 2004-02-12 Hong Huey Anna Onon Integrated visual development system for creating computer-implemented dialog scripts
US20040125937A1 (en) * 2002-12-31 2004-07-01 Turcan Diane Brown Computer telephony integration (CTI) complete customer contact center
EP1473916A1 (en) * 2003-04-29 2004-11-03 Intervoice Limited Partnership Web service call flow speech components
US6957256B1 (en) * 1999-03-02 2005-10-18 Cisco Technology, Inc. Linking external applications to a network management system
US20050261908A1 (en) * 2004-05-19 2005-11-24 International Business Machines Corporation Method, system, and apparatus for a voice markup language interpreter and voice browser
US20060111911A1 (en) * 2004-11-22 2006-05-25 Morford Timothy B Method and apparatus to generate audio versions of web pages
US20070133511A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Composite services delivery utilizing lightweight messaging
US20070133773A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Composite services delivery
US20070136436A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Selective view synchronization for composite services delivery
US20070133508A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Auto-establishment of a voice channel of access to a session for a composite service from a visual channel of access to the session for the composite service
US20070136449A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Update notification for peer views in a composite services delivery environment
US20070136421A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Synchronized view state for composite services delivery
US20070132834A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Speech disambiguation in a composite services enablement environment
US20070133510A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Managing concurrent data updates in a composite services delivery system
US20070133512A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Composite services enablement of visual navigation into a call center
US20070136420A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Visual channel refresh rate control for composite services delivery
US20070133769A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Voice navigation of a visual view for a session in a composite services enablement environment
US20070133513A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation View coordination for callers in a composite services enablement environment
US20070136448A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Channel presence in a composite services enablement environment
US20070133509A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Initiating voice access to a session from a visual access channel to the session in a composite services delivery system
US20070136793A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Secure access to a common session in a composite services delivery environment
US20070133507A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Model autocompletion for composite services synchronization
US20070136442A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Seamless reflection of model updates in a visual page for a visual channel in a composite services delivery system
US20070143485A1 (en) * 2005-12-08 2007-06-21 International Business Machines Corporation Solution for adding context to a text exchange modality during interactions with a composite services application
US20070147355A1 (en) * 2005-12-08 2007-06-28 International Business Machines Corporation Composite services generation tool
US20080152121A1 (en) * 2006-12-22 2008-06-26 International Business Machines Corporation Enhancing contact centers with dialog contracts
US20080205628A1 (en) * 2007-02-28 2008-08-28 International Business Machines Corporation Skills based routing in a standards based contact center using a presence server and expertise specific watchers
US20080205625A1 (en) * 2007-02-28 2008-08-28 International Business Machines Corporation Extending a standardized presence document to include contact center specific elements
US20080205624A1 (en) * 2007-02-28 2008-08-28 International Business Machines Corporation Identifying contact center agents based upon biometric characteristics of an agent's speech
US20080219429A1 (en) * 2007-02-28 2008-09-11 International Business Machines Corporation Implementing a contact center using open standards and non-proprietary components
US20080320443A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Wiki application development tool that uses specialized blogs to publish wiki development content in an organized/searchable fashion
US20080319760A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Creating and editing web 2.0 entries including voice enabled ones using a voice only interface
US20080319758A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Speech-enabled application that uses web 2.0 concepts to interface with speech engines
US20080319759A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Integrating a voice browser into a web 2.0 environment
US20080319761A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Speech processing method based upon a representational state transfer (rest) architecture that uses web 2.0 concepts for speech resource interfaces
US20080319742A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation System and method for posting to a blog or wiki using a telephone
US20080319762A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Using a wiki editor to create speech-enabled applications
US20080320079A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Customizing web 2.0 application behavior based on relationships between a content creator and a content requester
US20080320168A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Providing user customization of web 2.0 applications
US20100050150A1 (en) * 2002-06-14 2010-02-25 Apptera, Inc. Method and System for Developing Speech Applications
US7861223B1 (en) * 2004-09-27 2010-12-28 Rockwell Automation Technologies, Inc. Systems and methods that employ an extensible architecture to define configuration functionality
US20110099016A1 (en) * 2003-11-17 2011-04-28 Apptera, Inc. Multi-Tenant Self-Service VXML Portal
US20110161927A1 (en) * 2006-09-01 2011-06-30 Verizon Patent And Licensing Inc. Generating voice extensible markup language (vxml) documents
US20130013299A1 (en) * 2001-07-03 2013-01-10 Apptera, Inc. Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers
US8971216B2 (en) 1998-09-11 2015-03-03 Alcatel Lucent Method for routing transactions between internal and external partners in a communication center
US9002920B2 (en) 1998-09-11 2015-04-07 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US9008075B2 (en) 2005-12-22 2015-04-14 Genesys Telecommunications Laboratories, Inc. System and methods for improving interaction routing performance
USRE45583E1 (en) 1999-12-01 2015-06-23 Genesys Telecommunications Laboratories, Inc. Method and apparatus for providing enhanced communication capability for mobile devices on a virtual private network
USRE45606E1 (en) 1997-02-10 2015-07-07 Genesys Telecommunications Laboratories, Inc. Call and data correspondence in a call-in center employing virtual restructuring for computer telephony integrated functionality
USRE46060E1 (en) 1997-02-10 2016-07-05 Genesys Telecommunications Laboratories, Inc. In-band signaling for routing
USRE46153E1 (en) * 1998-09-11 2016-09-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US9516171B2 (en) 1997-02-10 2016-12-06 Genesys Telecommunications Laboratories, Inc. Personal desktop router
US9553755B2 (en) 1998-02-17 2017-01-24 Genesys Telecommunications Laboratories, Inc. Method for implementing and executing communication center routing strategies represented in extensible markup language
USRE46438E1 (en) 1999-09-24 2017-06-13 Genesys Telecommunications Laboratories, Inc. Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure
USRE46528E1 (en) 1997-11-14 2017-08-29 Genesys Telecommunications Laboratories, Inc. Implementation of call-center outbound dialing capability at a telephony network level
US11093898B2 (en) 2005-12-08 2021-08-17 International Business Machines Corporation Solution for adding context to a text exchange modality during interactions with a composite services application

Families Citing this family (119)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60040536D1 (en) 1999-06-11 2008-11-27 Telstra Corp Ltd PROCESS FOR DEVELOPING AN INTERACTIVE SYSTEM
US7140004B1 (en) * 2000-06-13 2006-11-21 Tellme Networks, Inc. Method and apparatus for zero-footprint phone application development
US7242752B2 (en) * 2001-07-03 2007-07-10 Apptera, Inc. Behavioral adaptation engine for discerning behavioral characteristics of callers interacting with an VXML-compliant voice application
US7609829B2 (en) * 2001-07-03 2009-10-27 Apptera, Inc. Multi-platform capable inference engine and universal grammar language adapter for intelligent voice application execution
US20050234727A1 (en) * 2001-07-03 2005-10-20 Leo Chiu Method and apparatus for adapting a voice extensible markup language-enabled voice system for natural speech recognition and system response
US7406418B2 (en) * 2001-07-03 2008-07-29 Apptera, Inc. Method and apparatus for reducing data traffic in a voice XML application distribution system through cache optimization
US7133830B1 (en) * 2001-11-13 2006-11-07 Sr2, Inc. System and method for supporting platform independent speech applications
DE10202095A1 (en) * 2002-01-21 2003-07-24 Siemens Ag Electric device
US20030216923A1 (en) * 2002-05-15 2003-11-20 Gilmore Jeffrey A. Dynamic content generation for voice messages
US20040042593A1 (en) * 2002-05-17 2004-03-04 Suren Gulrajani Web-based telephony services creation, deployment and maintenance method and system
AU2002950336A0 (en) 2002-07-24 2002-09-12 Telstra New Wave Pty Ltd System and process for developing a voice application
US7966184B2 (en) * 2006-03-06 2011-06-21 Audioeye, Inc. System and method for audible web site navigation
US7216287B2 (en) * 2002-08-02 2007-05-08 International Business Machines Corporation Personal voice portal service
AU2002951244A0 (en) * 2002-09-06 2002-09-19 Telstra New Wave Pty Ltd A development system for a dialog system
JP3930022B2 (en) * 2002-09-27 2007-06-13 株式会社ギンガネット Distance learning system, attendance confirmation method and attendance confirmation program
US7177817B1 (en) * 2002-12-12 2007-02-13 Tuvox Incorporated Automatic generation of voice content for a voice response system
US7336771B2 (en) 2003-01-16 2008-02-26 At&T Knowledge Ventures, L.P. Voice extensible markup language enhancements of intelligent network services
US7340043B2 (en) 2003-01-16 2008-03-04 At&T Knowledge Ventures, L.P. Voice extensible markup language-based announcements for use with intelligent network services
AU2003900584A0 (en) * 2003-02-11 2003-02-27 Telstra New Wave Pty Ltd System for predicting speech recognition accuracy and development for a dialog system
JP4484713B2 (en) * 2003-02-27 2010-06-16 幸男 久保 Call system and server and reception relay device used therefor
DE10311581A1 (en) * 2003-03-10 2004-09-23 Deutsche Telekom Ag Process and system for the automated creation of vocabulary
US7698435B1 (en) 2003-04-15 2010-04-13 Sprint Spectrum L.P. Distributed interactive media system and method
AU2003902020A0 (en) * 2003-04-29 2003-05-15 Telstra New Wave Pty Ltd A process for grammatical inference
US7366777B2 (en) 2003-05-15 2008-04-29 Sap Aktiengesellschaft Web application router
US20050010415A1 (en) * 2003-05-24 2005-01-13 Hagen David A. Artificial intelligence dialogue processor
WO2005020106A1 (en) 2003-08-18 2005-03-03 Sap Aktiengesellschaft Method and system for selecting a search engine and executing a search
US20050108303A1 (en) * 2003-10-31 2005-05-19 Carter Richard D. Remote backup and restore technique
US7697673B2 (en) 2003-11-17 2010-04-13 Apptera Inc. System for advertisement selection, placement and delivery within a multiple-tenant voice interaction service system
US20050119892A1 (en) 2003-12-02 2005-06-02 International Business Machines Corporation Method and arrangement for managing grammar options in a graphical callflow builder
US7401024B2 (en) 2003-12-02 2008-07-15 International Business Machines Corporation Automatic and usability-optimized aggregation of voice portlets into a speech portal menu
GB2409561A (en) * 2003-12-23 2005-06-29 Canon Kk A method of correcting errors in a speech recognition system
US20050171780A1 (en) * 2004-02-03 2005-08-04 Microsoft Corporation Speech-related object model and interface in managed code system
US20050229048A1 (en) * 2004-03-30 2005-10-13 International Business Machines Corporation Caching operational code in a voice markup interpreter
US7751535B2 (en) * 2004-04-28 2010-07-06 Nuance Communications, Inc. Voice browser implemented as a distributable component
US7389513B2 (en) * 2004-04-28 2008-06-17 International Business Machines Corporation Pooling stateful session enterprise Java beans for reuse
US8768711B2 (en) * 2004-06-17 2014-07-01 Nuance Communications, Inc. Method and apparatus for voice-enabling an application
US7580837B2 (en) 2004-08-12 2009-08-25 At&T Intellectual Property I, L.P. System and method for targeted tuning module of a speech recognition system
US20060047511A1 (en) * 2004-09-01 2006-03-02 Electronic Data Systems Corporation System, method, and computer program product for content delivery in a push-to-talk communication system
US7242751B2 (en) 2004-12-06 2007-07-10 Sbc Knowledge Ventures, L.P. System and method for speech recognition-enabled automatic call routing
US8838454B1 (en) 2004-12-10 2014-09-16 Sprint Spectrum L.P. Transferring voice command platform (VCP) functions and/or grammar together with a call from one VCP to another
US8676862B2 (en) 2004-12-31 2014-03-18 Emc Corporation Information management
US8260753B2 (en) * 2004-12-31 2012-09-04 Emc Corporation Backup information management
US8185399B2 (en) 2005-01-05 2012-05-22 At&T Intellectual Property Ii, L.P. System and method of providing an automated data-collection in spoken dialog systems
US20060149553A1 (en) * 2005-01-05 2006-07-06 At&T Corp. System and method for using a library to interactively design natural language spoken dialog systems
US8478589B2 (en) 2005-01-05 2013-07-02 At&T Intellectual Property Ii, L.P. Library of existing spoken dialog data for use in generating new natural language spoken dialog systems
US7751551B2 (en) 2005-01-10 2010-07-06 At&T Intellectual Property I, L.P. System and method for speech-enabled call routing
US7627096B2 (en) * 2005-01-14 2009-12-01 At&T Intellectual Property I, L.P. System and method for independently recognizing and selecting actions and objects in a speech recognition system
US20060159241A1 (en) * 2005-01-20 2006-07-20 Sbc Knowledge Ventures L.P. System and method for providing an interactive voice recognition system
US7574358B2 (en) 2005-02-28 2009-08-11 International Business Machines Corporation Natural language system and method based on unisolated performance metric
US7657020B2 (en) * 2005-06-03 2010-02-02 At&T Intellectual Property I, Lp Call routing system and method of using the same
EP1750253B1 (en) * 2005-08-04 2012-03-21 Nuance Communications, Inc. Speech dialog system
US7716171B2 (en) * 2005-08-18 2010-05-11 Emc Corporation Snapshot indexing
US9026512B2 (en) * 2005-08-18 2015-05-05 Emc Corporation Data object search and retrieval
GB0517542D0 (en) * 2005-08-27 2005-10-05 Ibm Method and apparatus for a voice portal server
US9253301B2 (en) * 2005-09-01 2016-02-02 Xtone Networks, Inc. System and method for announcing and routing incoming telephone calls using a distributed voice application execution system architecture
US9313307B2 (en) * 2005-09-01 2016-04-12 Xtone Networks, Inc. System and method for verifying the identity of a user by voiceprint analysis
CA2620931A1 (en) 2005-09-01 2007-03-08 Vishal Dhawan Voice application network platform
US11102342B2 (en) 2005-09-01 2021-08-24 Xtone, Inc. System and method for displaying the history of a user's interaction with a voice application
US9456068B2 (en) 2005-09-01 2016-09-27 Xtone, Inc. System and method for connecting a user to business services
US20100166161A1 (en) * 2005-09-01 2010-07-01 Vishal Dhawan System and methods for providing voice messaging services
US9799039B2 (en) * 2005-09-01 2017-10-24 Xtone, Inc. System and method for providing television programming recommendations and for automated tuning and recordation of television programs
US11153425B2 (en) * 2005-09-01 2021-10-19 Xtone, Inc. System and method for providing interactive services
US20100158217A1 (en) 2005-09-01 2010-06-24 Vishal Dhawan System and method for placing telephone calls using a distributed voice application execution system architecture
US8964960B2 (en) * 2005-09-01 2015-02-24 Xtone Networks, Inc. System and method for interacting with a user via a variable volume and variable tone audio prompt
US9426269B2 (en) * 2005-09-01 2016-08-23 Xtone Networks, Inc. System and method for performing certain actions based upon a dialed telephone number
US8661411B2 (en) * 2005-12-02 2014-02-25 Nuance Communications, Inc. Method and system for testing sections of large speech applications
US8612229B2 (en) 2005-12-15 2013-12-17 Nuance Communications, Inc. Method and system for conveying an example in a natural language understanding application
US7885958B2 (en) * 2006-02-27 2011-02-08 International Business Machines Corporation Method, apparatus and computer program product for organizing hierarchical information
US20070271104A1 (en) * 2006-05-19 2007-11-22 Mckay Martin Streaming speech with synchronized highlighting generated by a server
US8588399B2 (en) * 2006-07-28 2013-11-19 Paras & Associates Call routing method: routing to out-of-network representative having ability to speak specific language, if interpreter of network and interpreter of entity are not available to take call
US8144699B2 (en) * 2006-11-21 2012-03-27 Cisco Technology, Inc. Auto-provisioning of network services over an ethernet access link
US20080140469A1 (en) * 2006-12-06 2008-06-12 International Business Machines Corporation Method, system and program product for determining an optimal configuration and operational costs for implementing a capacity management service
US8056070B2 (en) * 2007-01-10 2011-11-08 Goller Michael D System and method for modifying and updating a speech recognition program
US8650030B2 (en) 2007-04-02 2014-02-11 Google Inc. Location based responses to telephone requests
US8503665B1 (en) * 2007-04-18 2013-08-06 William S. Meisel System and method of writing and using scripts in automated, speech-based caller interactions
US9794348B2 (en) 2007-06-04 2017-10-17 Todd R. Smith Using voice commands from a mobile device to remotely access and control a computer
KR20090003533A (en) * 2007-06-15 2009-01-12 엘지전자 주식회사 Method and system for creating and operating user generated contents and personal portable device using thereof
US9264483B2 (en) 2007-07-18 2016-02-16 Hammond Development International, Inc. Method and system for enabling a communication device to remotely execute an application
US8635069B2 (en) 2007-08-16 2014-01-21 Crimson Corporation Scripting support for data identifiers, voice recognition and speech in a telnet session
JP3139277U (en) * 2007-11-26 2008-02-07 株式会社Srj Virtual school system and school city system
US20100042409A1 (en) * 2008-08-13 2010-02-18 Harold Hutchinson Automated voice system and method
US9201965B1 (en) * 2009-09-30 2015-12-01 Cisco Technology, Inc. System and method for providing speech recognition using personal vocabulary in a network environment
WO2011089450A2 (en) 2010-01-25 2011-07-28 Andrew Peter Nelson Jerram Apparatuses, methods and systems for a digital conversation management platform
US8571870B2 (en) * 2010-02-12 2013-10-29 Nuance Communications, Inc. Method and apparatus for generating synthetic speech with contrastive stress
US8949128B2 (en) * 2010-02-12 2015-02-03 Nuance Communications, Inc. Method and apparatus for providing speech output for speech-enabled applications
US8447610B2 (en) 2010-02-12 2013-05-21 Nuance Communications, Inc. Method and apparatus for generating synthetic speech with contrastive stress
WO2011149087A1 (en) * 2010-05-27 2011-12-01 株式会社東芝 Magnetic resonance imaging device
CN102271194B (en) * 2010-06-04 2014-12-10 中兴通讯股份有限公司 Interactive voice response service development method and system
US10104230B2 (en) * 2011-02-25 2018-10-16 International Business Machines Corporation Systems and methods for availing multiple input channels in a voice application
US8670984B2 (en) * 2011-02-25 2014-03-11 Nuance Communications, Inc. Automatically generating audible representations of data content based on user preferences
US9329832B2 (en) * 2011-05-09 2016-05-03 Robert Allen Blaisch Voice internet system and method
US8909624B2 (en) 2011-05-31 2014-12-09 Cisco Technology, Inc. System and method for evaluating results of a search query in a network environment
WO2014043416A1 (en) * 2012-09-12 2014-03-20 Genesys Telecommunications Laboratories, Inc. System and method for dynamic configuration of contact centers via templates
US9148499B2 (en) 2013-01-22 2015-09-29 Blackberry Limited Method and system for automatically identifying voice tags through user operation
US9330659B2 (en) * 2013-02-25 2016-05-03 Microsoft Technology Licensing, Llc Facilitating development of a spoken natural language interface
US9786296B2 (en) * 2013-07-08 2017-10-10 Qualcomm Incorporated Method and apparatus for assigning keyword model to voice operated function
US9495359B1 (en) 2013-08-21 2016-11-15 Athena Ann Smyros Textual geographical location processing
US10199034B2 (en) 2014-08-18 2019-02-05 At&T Intellectual Property I, L.P. System and method for unified normalization in text-to-speech and automatic speech recognition
US10033797B1 (en) 2014-08-20 2018-07-24 Ivanti, Inc. Terminal emulation over HTML
CN105744090A (en) 2014-12-09 2016-07-06 阿里巴巴集团控股有限公司 Voice information processing method and device
US20170026720A1 (en) * 2015-05-28 2017-01-26 Hashplay Inc. Systems and method for providing multimedia content in a network
US10325590B2 (en) * 2015-06-26 2019-06-18 Intel Corporation Language model modification for local speech recognition systems using remote sources
TW201719453A (en) * 2015-11-25 2017-06-01 Fubon Securities Co Ltd Method for operating financial software through voice and mobile device and computer readable recording medium which extracts a word and a characteristic value from texts obtained from a voice input and identify a corresponding financial product for automatic entry into an operation screen
US10423709B1 (en) 2018-08-16 2019-09-24 Audioeye, Inc. Systems, devices, and methods for automated and programmatic creation and deployment of remediations to non-compliant web pages or user interfaces
US10444934B2 (en) 2016-03-18 2019-10-15 Audioeye, Inc. Modular systems and methods for selectively enabling cloud-based assistive technologies
US10867120B1 (en) 2016-03-18 2020-12-15 Audioeye, Inc. Modular systems and methods for selectively enabling cloud-based assistive technologies
US11727195B2 (en) 2016-03-18 2023-08-15 Audioeye, Inc. Modular systems and methods for selectively enabling cloud-based assistive technologies
US10896286B2 (en) 2016-03-18 2021-01-19 Audioeye, Inc. Modular systems and methods for selectively enabling cloud-based assistive technologies
CN107545892B (en) * 2016-06-24 2021-07-30 中兴通讯股份有限公司 Equipment control method, device and system
US11100278B2 (en) 2016-07-28 2021-08-24 Ivanti, Inc. Systems and methods for presentation of a terminal application screen
US10621984B2 (en) * 2017-10-04 2020-04-14 Google Llc User-configured and customized interactive dialog application
US11468885B2 (en) * 2018-02-15 2022-10-11 DMAI, Inc. System and method for conversational agent via adaptive caching of dialogue tree
WO2019161241A1 (en) 2018-02-15 2019-08-22 DMAI, Inc. System and method for identifying a point of interest based on intersecting visual trajectories
US11017779B2 (en) 2018-02-15 2021-05-25 DMAI, Inc. System and method for speech understanding via integrated audio and visual based speech recognition
US10701003B2 (en) 2018-05-21 2020-06-30 Slack Technologies, Inc. Systems and methods for initiating external actions via a group-based communication system
US10991370B2 (en) * 2019-04-16 2021-04-27 International Business Machines Corporation Speech to text conversion engine for non-standard speech
CN111176622B (en) * 2019-12-30 2022-07-08 思必驰科技股份有限公司 Implementation method, management system and management method for unified management of voice skills of solution
CN111339767B (en) * 2020-02-21 2023-07-21 百度在线网络技术(北京)有限公司 Dialogue source data processing method and device, electronic equipment and computer readable medium
CN112289314A (en) * 2020-09-28 2021-01-29 珠海大横琴科技发展有限公司 Voice processing method and device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020015480A1 (en) * 1998-12-08 2002-02-07 Neil Daswani Flexible multi-network voice/data aggregation system architecture
US20020198719A1 (en) * 2000-12-04 2002-12-26 International Business Machines Corporation Reusable voiceXML dialog components, subdialogs and beans
US7092370B2 (en) * 2000-08-17 2006-08-15 Roamware, Inc. Method and system for wireless voice channel/data channel integration
US20060209797A1 (en) * 1998-02-17 2006-09-21 Nikolay Anisimov Method for implementing and executing communication center routing strategies represented in extensible markup language
US7140004B1 (en) * 2000-06-13 2006-11-21 Tellme Networks, Inc. Method and apparatus for zero-footprint phone application development
US7143042B1 (en) * 1999-10-04 2006-11-28 Nuance Communications Tool for graphically defining dialog flows and for establishing operational links between speech applications and hypermedia content in an interactive voice response environment

Family Cites Families (123)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5434777A (en) * 1992-05-27 1995-07-18 Apple Computer, Inc. Method and apparatus for processing natural language
US5983179A (en) * 1992-11-13 1999-11-09 Dragon Systems, Inc. Speech recognition system which turns its voice response on for confirmation when it has been turned off without confirmation
EP0618565A3 (en) * 1993-04-02 1996-06-26 Ibm Interactive dynamic grammar constraint in speech recognition.
US5615296A (en) * 1993-11-12 1997-03-25 International Business Machines Corporation Continuous speech recognition and voice response system and method to enable conversational dialogues with microprocessors
JPH07219590A (en) * 1994-01-31 1995-08-18 Canon Inc Speech information retrieval device and method
JPH0869470A (en) * 1994-06-21 1996-03-12 Canon Inc Natural language processing device and method
US6198977B1 (en) * 1995-01-09 2001-03-06 Qwest Communication International Inc. Electronic classified advertising interface method and instructions with ad replay options
US6965864B1 (en) * 1995-04-10 2005-11-15 Texas Instruments Incorporated Voice activated hypermedia systems using grammatical metadata
US5774628A (en) * 1995-04-10 1998-06-30 Texas Instruments Incorporated Speaker-independent dynamic vocabulary and grammar in speech recognition
US6199082B1 (en) * 1995-07-17 2001-03-06 Microsoft Corporation Method for delivering separate design and content in a multimedia publishing system
DE19533541C1 (en) * 1995-09-11 1997-03-27 Daimler Benz Aerospace Ag Method for the automatic control of one or more devices by voice commands or by voice dialog in real time and device for executing the method
US5719941A (en) * 1996-01-12 1998-02-17 Microsoft Corporation Method for changing passwords on a remote computer
US5884262A (en) * 1996-03-28 1999-03-16 Bell Atlantic Network Services, Inc. Computer network audio access and conversion system
US5915001A (en) * 1996-11-14 1999-06-22 Vois Corporation System and method for providing and using universally accessible voice and speech data files
US6064666A (en) * 1996-11-15 2000-05-16 International Business Machines Corporation Cross service common user image association
US6285987B1 (en) * 1997-01-22 2001-09-04 Engage, Inc. Internet advertising system
US6014437A (en) * 1997-02-03 2000-01-11 International Business Machines Corporation Multi service platform architecture for telephone networks
US6125376A (en) 1997-04-10 2000-09-26 At&T Corp Method and apparatus for voice interaction over a network using parameterized interaction definitions
US6856960B1 (en) * 1997-04-14 2005-02-15 At & T Corp. System and method for providing remote automatic speech recognition and text-to-speech services via a packet network
US6101472A (en) * 1997-04-16 2000-08-08 International Business Machines Corporation Data processing system and method for navigating a network using a voice command
WO1998050907A1 (en) * 1997-05-06 1998-11-12 Speechworks International, Inc. System and method for developing interactive speech applications
US5953700A (en) * 1997-06-11 1999-09-14 International Business Machines Corporation Portable acoustic interface for remote access to automatic speech/speaker recognition server
US5974413A (en) 1997-07-03 1999-10-26 Activeword Systems, Inc. Semantic user interface
US6192338B1 (en) * 1997-08-12 2001-02-20 At&T Corp. Natural language knowledge servers as network resources
US5960384A (en) * 1997-09-03 1999-09-28 Brash; Douglas E. Method and device for parsing natural language sentences and other sequential symbolic expressions
US6240184B1 (en) * 1997-09-05 2001-05-29 Rsa Security Inc. Password synchronization
US6363411B1 (en) * 1998-08-05 2002-03-26 Mci Worldcom, Inc. Intelligent network
GB9723813D0 (en) * 1997-11-11 1998-01-07 Mitel Corp Call routing based on caller's mood
US6182038B1 (en) * 1997-12-01 2001-01-30 Motorola, Inc. Context dependent phoneme networks for encoding speech information
US20010012335A1 (en) * 1998-02-06 2001-08-09 Lance Kaufman Preference based telecommunication information service
US6985478B2 (en) * 1998-02-17 2006-01-10 Genesys Telecommunications Laboratories, Inc. Using XML expressed primitives for platform and system-independent call modeling
US6298072B1 (en) * 1998-02-19 2001-10-02 Mci Communications Corporation Real-time transaction synchronization among peer authentication systems in a telecommunications network environment
US6216104B1 (en) * 1998-02-20 2001-04-10 Philips Electronics North America Corporation Computer-based patient record and message delivery system
US6269336B1 (en) 1998-07-24 2001-07-31 Motorola, Inc. Voice browser for interactive services and methods thereof
US6539359B1 (en) * 1998-10-02 2003-03-25 Motorola, Inc. Markup language for interactive services and methods thereof
US6587822B2 (en) * 1998-10-06 2003-07-01 Lucent Technologies Inc. Web-based platform for interactive voice response (IVR)
US6185535B1 (en) * 1998-10-16 2001-02-06 Telefonaktiebolaget Lm Ericsson (Publ) Voice control of a user interface to service applications
IL127293A0 (en) * 1998-11-26 1999-09-22 Creator Ltd Script development systems and methods useful therefor
US7082397B2 (en) * 1998-12-01 2006-07-25 Nuance Communications, Inc. System for and method of creating and browsing a voice web
US6195636B1 (en) * 1999-02-19 2001-02-27 Texas Instruments Incorporated Speech recognition over packet networks
US7055042B1 (en) * 1999-03-25 2006-05-30 Electronics Data Systems Corporation System and method for synchronizing a user password between mainframe and alternative computer operating environments
US6600736B1 (en) * 1999-03-31 2003-07-29 Lucent Technologies Inc. Method of providing transfer capability on web-based interactive voice response services
US6907034B1 (en) * 1999-04-08 2005-06-14 Intel Corporation Out-of-band signaling for network based computer session synchronization
US6636831B1 (en) * 1999-04-09 2003-10-21 Inroad, Inc. System and process for voice-controlled information retrieval
US6847969B1 (en) * 1999-05-03 2005-01-25 Streetspace, Inc. Method and system for providing personalized online services and advertisements in public spaces
US20020032564A1 (en) * 2000-04-19 2002-03-14 Farzad Ehsani Phrase-based dialogue modeling with particular application to creating a recognition grammar for a voice-controlled user interface
US6312378B1 (en) * 1999-06-03 2001-11-06 Cardiac Intelligence Corporation System and method for automated collection and analysis of patient information retrieved from an implantable medical device for remote patient care
US6501832B1 (en) 1999-08-24 2002-12-31 Microstrategy, Inc. Voice code registration system and method for registering voice codes for voice pages in a voice network access provider system
US6587547B1 (en) * 1999-09-13 2003-07-01 Microstrategy, Incorporated System and method for the creation and automatic deployment of personalized, dynamic and interactive voice services, with real-time drilling via telephone
US6940953B1 (en) * 1999-09-13 2005-09-06 Microstrategy, Inc. System and method for the creation and automatic deployment of personalized, dynamic and interactive voice services including module for generating and formatting voice services
US6970915B1 (en) * 1999-11-01 2005-11-29 Tellme Networks, Inc. Streaming content over a telephone interface
US7174506B1 (en) * 1999-11-05 2007-02-06 International Business Machines Corporation Method and system for producing dynamic web pages
US6526382B1 (en) * 1999-12-07 2003-02-25 Comverse, Inc. Language-oriented user interfaces for voice activated services
US6424945B1 (en) * 1999-12-15 2002-07-23 Nokia Corporation Voice packet data network browsing for mobile terminals system and method using a dual-mode wireless connection
US7116765B2 (en) * 1999-12-16 2006-10-03 Intellisync Corporation Mapping an internet document to be accessed over a telephone system
US6606525B1 (en) * 1999-12-27 2003-08-12 Motorola, Inc. System and method of merging static data in web pages
US20010043234A1 (en) * 2000-01-03 2001-11-22 Mallik Kotamarti Incorporating non-native user interface mechanisms into a user interface
US7054819B1 (en) * 2000-02-11 2006-05-30 Microsoft Corporation Voice print access to computer resources
US7392281B1 (en) * 2000-02-25 2008-06-24 Navic Systems, Inc. System and method for providing guaranteed delivery of messages to embedded devices over a data network
US6466654B1 (en) * 2000-03-06 2002-10-15 Avaya Technology Corp. Personal virtual assistant with semantic tagging
US6757362B1 (en) * 2000-03-06 2004-06-29 Avaya Technology Corp. Personal virtual assistant
US6662163B1 (en) 2000-03-30 2003-12-09 Voxware, Inc. System and method for programming portable devices from a remote computer system
CN101493919B (en) * 2000-03-31 2019-01-04 乐威指南公司 The system and method for meta-data-linked advertisements
US20010037405A1 (en) * 2000-04-07 2001-11-01 Sideek Sinnathambi Mohamed Wireless web generation from conventional web sites by pattern identification and dynamic content extraction
US7072984B1 (en) * 2000-04-26 2006-07-04 Novarra, Inc. System and method for accessing customized information over the internet using a browser for a plurality of electronic devices
US6785653B1 (en) * 2000-05-01 2004-08-31 Nuance Communications Distributed voice web architecture and associated components and methods
US20020010626A1 (en) * 2000-05-22 2002-01-24 Eyal Agmoni Internert advertising and information delivery system
US20020019881A1 (en) * 2000-06-16 2002-02-14 Bokhari Wasiq M. System, method and computer program product for habitat-based universal application of functions to network data
US7376740B1 (en) * 2000-06-13 2008-05-20 Microsoft Corporation Phone application state management mechanism
US7093129B1 (en) * 2000-06-19 2006-08-15 International Business Machines Corporation Secured encrypted communications in a voice browser
US6874018B2 (en) * 2000-08-07 2005-03-29 Networks Associates Technology, Inc. Method and system for playing associated audible advertisement simultaneously with the display of requested content on handheld devices and sending a visual warning when the audio channel is off
US7653748B2 (en) * 2000-08-10 2010-01-26 Simplexity, Llc Systems, methods and computer program products for integrating advertising within web content
US20020045437A1 (en) * 2000-08-18 2002-04-18 Alexander Kesler Tracing a location of a mobile device
AU2001283579A1 (en) * 2000-08-21 2002-03-04 Yahoo, Inc. Method and system of interpreting and presenting web content using a voice browser
US6922411B1 (en) * 2000-09-29 2005-07-26 Voxeo Corporation Networked computer telephony system driven by web-based applications
US20020077823A1 (en) * 2000-10-13 2002-06-20 Andrew Fox Software development systems and methods
US6757365B1 (en) * 2000-10-16 2004-06-29 Tellme Networks, Inc. Instant messaging via telephone interfaces
US6501956B1 (en) 2000-10-17 2002-12-31 Intervoice Limited Partnership Providing blended interface for wireless information services
US6983250B2 (en) * 2000-10-25 2006-01-03 Nms Communications Corporation Method and system for enabling a user to obtain information from a text-based web site in audio form
US6795808B1 (en) * 2000-10-30 2004-09-21 Koninklijke Philips Electronics N.V. User interface/entertainment device that simulates personal interaction and charges external database with relevant data
KR100398711B1 (en) * 2000-11-08 2003-09-19 주식회사 와이즈엔진 Content publication system for supporting real-time integration and processing of multimedia contents including dynamic data and method thereof
US7028306B2 (en) * 2000-12-04 2006-04-11 International Business Machines Corporation Systems and methods for implementing modular DOM (Document Object Model)-based multi-modal browsers
US7016847B1 (en) * 2000-12-08 2006-03-21 Ben Franklin Patent Holdings L.L.C. Open architecture for a voice user interface
US7917888B2 (en) * 2001-01-22 2011-03-29 Symbol Technologies, Inc. System and method for building multi-modal and multi-channel applications
US20020111855A1 (en) * 2001-01-23 2002-08-15 Hammerstad Diane R. Delivery of time significant advertising
US20020156905A1 (en) * 2001-02-21 2002-10-24 Boris Weissman System for logging on to servers through a portal computer
US6658414B2 (en) * 2001-03-06 2003-12-02 Topic Radio, Inc. Methods, systems, and computer program products for generating and providing access to end-user-definable voice portals
US20020193997A1 (en) * 2001-03-09 2002-12-19 Fitzpatrick John E. System, method and computer program product for dynamic billing using tags in a speech recognition framework
US7174297B2 (en) * 2001-03-09 2007-02-06 Bevocal, Inc. System, method and computer program product for a dynamically configurable voice portal
US6870913B2 (en) * 2001-03-15 2005-03-22 Voxiva, Inc. System and method for collecting, disseminating and managing information using a voice and data base system
US20030032409A1 (en) * 2001-03-16 2003-02-13 Hutcheson Stewart Douglas Method and system for distributing content over a wireless communications system
US6832196B2 (en) * 2001-03-30 2004-12-14 International Business Machines Corporation Speech driven data selection in a voice-enabled program
US20030046316A1 (en) * 2001-04-18 2003-03-06 Jaroslav Gergic Systems and methods for providing conversational computing via javaserver pages and javabeans
US20020156815A1 (en) * 2001-04-19 2002-10-24 International Business Machines Corporation Method and apparatus for the separation of web layout, logic, and data when used in server-side scripting languages
US20030177175A1 (en) * 2001-04-26 2003-09-18 Worley Dale R. Method and system for display of web pages
US6621502B1 (en) * 2001-05-02 2003-09-16 Awa, Inc. Method and system for decoupled audio and video presentation
US20050028085A1 (en) * 2001-05-04 2005-02-03 Irwin James S. Dynamic generation of voice application information from a web server
US7020841B2 (en) * 2001-06-07 2006-03-28 International Business Machines Corporation System and method for generating and presenting multi-modal applications from intent-based markup scripts
US6801604B2 (en) * 2001-06-25 2004-10-05 International Business Machines Corporation Universal IP-based and scalable architectures across conversational applications using web services for speech and audio processing resources
US7054939B2 (en) * 2001-06-28 2006-05-30 Bellsouth Intellectual Property Corportion Simultaneous visual and telephonic access to interactive information delivery
US7151763B2 (en) * 2001-06-29 2006-12-19 Bellsouth Intellectual Property Corporation Retrieving voice-based content in conjunction with wireless application protocol browsing
US7242752B2 (en) * 2001-07-03 2007-07-10 Apptera, Inc. Behavioral adaptation engine for discerning behavioral characteristics of callers interacting with an VXML-compliant voice application
US20030007609A1 (en) * 2001-07-03 2003-01-09 Yuen Michael S. Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers
US7286985B2 (en) * 2001-07-03 2007-10-23 Apptera, Inc. Method and apparatus for preprocessing text-to-speech files in a voice XML application distribution system using industry specific, social and regional expression rules
US20020010715A1 (en) * 2001-07-26 2002-01-24 Garry Chinn System and method for browsing using a limited display device
US6941512B2 (en) * 2001-09-10 2005-09-06 Hewlett-Packard Development Company, L.P. Dynamic web content unfolding in wireless information gateways
US7769823B2 (en) * 2001-09-28 2010-08-03 F5 Networks, Inc. Method and system for distributing requests for content
US6813342B1 (en) * 2001-10-17 2004-11-02 Bevocal, Inc. Implicit area code determination during voice activated dialing
US20030093467A1 (en) * 2001-11-01 2003-05-15 Flying Wireless, Inc. Server for remote file access system
US7158936B2 (en) * 2001-11-01 2007-01-02 Comverse, Inc. Method and system for providing a voice application bookmark
US6891932B2 (en) * 2001-12-11 2005-05-10 Cisco Technology, Inc. System and methodology for voice activated access to multiple data sources and voice repositories in a single session
US20030115066A1 (en) * 2001-12-17 2003-06-19 Seeley Albert R. Method of using automated speech recognition (ASR) for web-based voice applications
US8126722B2 (en) * 2001-12-20 2012-02-28 Verizon Business Global Llc Application infrastructure platform (AIP)
US6885856B2 (en) * 2002-01-10 2005-04-26 Chang-Sheng, Inc. Telephone bridging method
US6978129B1 (en) 2002-03-28 2005-12-20 Bellsouth Intellectual Property Corporation Telephone with dynamically programmable push buttons for access to advanced applications
US9137324B2 (en) * 2002-04-10 2015-09-15 International Business Machines Corporation Capacity on-demand in distributed computing environments
US7436947B2 (en) * 2002-05-14 2008-10-14 Avaya Inc. Method and apparatus for automatic notification and response based on communication flow expressions
US7343396B2 (en) * 2002-06-20 2008-03-11 Fineground Networks Precomputation of web documents
SE0202058D0 (en) * 2002-07-02 2002-07-02 Ericsson Telefon Ab L M Voice browsing architecture based on adaptive keyword spotting
US7210682B2 (en) * 2002-09-06 2007-05-01 Fujifilm Corporation Sheet distributor, image recorder, and a sheet distributing method
US7697673B2 (en) * 2003-11-17 2010-04-13 Apptera Inc. System for advertisement selection, placement and delivery within a multiple-tenant voice interaction service system
US7206391B2 (en) * 2003-12-23 2007-04-17 Apptera Inc. Method for creating and deploying system changes in a voice application system
US20050283764A1 (en) * 2004-04-28 2005-12-22 Leo Chiu Method and apparatus for validating a voice application

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060209797A1 (en) * 1998-02-17 2006-09-21 Nikolay Anisimov Method for implementing and executing communication center routing strategies represented in extensible markup language
US20020015480A1 (en) * 1998-12-08 2002-02-07 Neil Daswani Flexible multi-network voice/data aggregation system architecture
US7143042B1 (en) * 1999-10-04 2006-11-28 Nuance Communications Tool for graphically defining dialog flows and for establishing operational links between speech applications and hypermedia content in an interactive voice response environment
US7140004B1 (en) * 2000-06-13 2006-11-21 Tellme Networks, Inc. Method and apparatus for zero-footprint phone application development
US7092370B2 (en) * 2000-08-17 2006-08-15 Roamware, Inc. Method and system for wireless voice channel/data channel integration
US20020198719A1 (en) * 2000-12-04 2002-12-26 International Business Machines Corporation Reusable voiceXML dialog components, subdialogs and beans

Cited By (96)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
USRE45606E1 (en) 1997-02-10 2015-07-07 Genesys Telecommunications Laboratories, Inc. Call and data correspondence in a call-in center employing virtual restructuring for computer telephony integrated functionality
USRE46060E1 (en) 1997-02-10 2016-07-05 Genesys Telecommunications Laboratories, Inc. In-band signaling for routing
US9516171B2 (en) 1997-02-10 2016-12-06 Genesys Telecommunications Laboratories, Inc. Personal desktop router
USRE46243E1 (en) 1997-02-10 2016-12-20 Genesys Telecommunications Laboratories, Inc. In-band signaling for routing
USRE46521E1 (en) 1997-09-30 2017-08-22 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
USRE46528E1 (en) 1997-11-14 2017-08-29 Genesys Telecommunications Laboratories, Inc. Implementation of call-center outbound dialing capability at a telephony network level
US9553755B2 (en) 1998-02-17 2017-01-24 Genesys Telecommunications Laboratories, Inc. Method for implementing and executing communication center routing strategies represented in extensible markup language
US20040019638A1 (en) * 1998-09-11 2004-01-29 Petr Makagon Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US9002920B2 (en) 1998-09-11 2015-04-07 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US7222301B2 (en) * 1998-09-11 2007-05-22 Genesys Telecommunications Laboratories, Inc. Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US10218848B2 (en) 1998-09-11 2019-02-26 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US8971216B2 (en) 1998-09-11 2015-03-03 Alcatel Lucent Method for routing transactions between internal and external partners in a communication center
US20060095568A1 (en) * 1998-09-11 2006-05-04 Petr Makagon Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US9350808B2 (en) 1998-09-11 2016-05-24 Alcatel Lucent Method for routing transactions between internal and external partners in a communication center
USRE46153E1 (en) * 1998-09-11 2016-09-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
USRE46387E1 (en) 1998-09-11 2017-05-02 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US6957256B1 (en) * 1999-03-02 2005-10-18 Cisco Technology, Inc. Linking external applications to a network management system
USRE46438E1 (en) 1999-09-24 2017-06-13 Genesys Telecommunications Laboratories, Inc. Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure
USRE46457E1 (en) 1999-09-24 2017-06-27 Genesys Telecommunications Laboratories, Inc. Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure
USRE45583E1 (en) 1999-12-01 2015-06-23 Genesys Telecommunications Laboratories, Inc. Method and apparatus for providing enhanced communication capability for mobile devices on a virtual private network
US20130013299A1 (en) * 2001-07-03 2013-01-10 Apptera, Inc. Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers
US20100050150A1 (en) * 2002-06-14 2010-02-25 Apptera, Inc. Method and System for Developing Speech Applications
US20040027379A1 (en) * 2002-08-08 2004-02-12 Hong Huey Anna Onon Integrated visual development system for creating computer-implemented dialog scripts
USRE46538E1 (en) 2002-10-10 2017-09-05 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US20040125937A1 (en) * 2002-12-31 2004-07-01 Turcan Diane Brown Computer telephony integration (CTI) complete customer contact center
EP1473916A1 (en) * 2003-04-29 2004-11-03 Intervoice Limited Partnership Web service call flow speech components
US20040220810A1 (en) * 2003-04-29 2004-11-04 Leask Gary M. Web service call flow speech components
US7269562B2 (en) 2003-04-29 2007-09-11 Intervoice Limited Partnership Web service call flow speech components
US20110099016A1 (en) * 2003-11-17 2011-04-28 Apptera, Inc. Multi-Tenant Self-Service VXML Portal
US20050261908A1 (en) * 2004-05-19 2005-11-24 International Business Machines Corporation Method, system, and apparatus for a voice markup language interpreter and voice browser
US7925512B2 (en) * 2004-05-19 2011-04-12 Nuance Communications, Inc. Method, system, and apparatus for a voice markup language interpreter and voice browser
US7861223B1 (en) * 2004-09-27 2010-12-28 Rockwell Automation Technologies, Inc. Systems and methods that employ an extensible architecture to define configuration functionality
US20060111911A1 (en) * 2004-11-22 2006-05-25 Morford Timothy B Method and apparatus to generate audio versions of web pages
US8838673B2 (en) 2004-11-22 2014-09-16 Timothy B. Morford Method and apparatus to generate audio versions of web pages
US20070136793A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Secure access to a common session in a composite services delivery environment
US20070133513A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation View coordination for callers in a composite services enablement environment
US11093898B2 (en) 2005-12-08 2021-08-17 International Business Machines Corporation Solution for adding context to a text exchange modality during interactions with a composite services application
US10332071B2 (en) * 2005-12-08 2019-06-25 International Business Machines Corporation Solution for adding context to a text exchange modality during interactions with a composite services application
US20070133511A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Composite services delivery utilizing lightweight messaging
US20070133773A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Composite services delivery
US20070136436A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Selective view synchronization for composite services delivery
US20070133508A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Auto-establishment of a voice channel of access to a session for a composite service from a visual channel of access to the session for the composite service
US20070136449A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Update notification for peer views in a composite services delivery environment
US20070136421A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Synchronized view state for composite services delivery
US20070132834A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Speech disambiguation in a composite services enablement environment
US20070133510A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Managing concurrent data updates in a composite services delivery system
US20070133512A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Composite services enablement of visual navigation into a call center
US20070136420A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Visual channel refresh rate control for composite services delivery
US7792971B2 (en) 2005-12-08 2010-09-07 International Business Machines Corporation Visual channel refresh rate control for composite services delivery
US7809838B2 (en) 2005-12-08 2010-10-05 International Business Machines Corporation Managing concurrent data updates in a composite services delivery system
US7818432B2 (en) 2005-12-08 2010-10-19 International Business Machines Corporation Seamless reflection of model updates in a visual page for a visual channel in a composite services delivery system
US7827288B2 (en) 2005-12-08 2010-11-02 International Business Machines Corporation Model autocompletion for composite services synchronization
US20070133769A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Voice navigation of a visual view for a session in a composite services enablement environment
US7877486B2 (en) 2005-12-08 2011-01-25 International Business Machines Corporation Auto-establishment of a voice channel of access to a session for a composite service from a visual channel of access to the session for the composite service
US7890635B2 (en) 2005-12-08 2011-02-15 International Business Machines Corporation Selective view synchronization for composite services delivery
US20070136448A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Channel presence in a composite services enablement environment
US7921158B2 (en) 2005-12-08 2011-04-05 International Business Machines Corporation Using a list management server for conferencing in an IMS environment
US20070133509A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Initiating voice access to a session from a visual access channel to the session in a composite services delivery system
US20070133507A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Model autocompletion for composite services synchronization
US20070136442A1 (en) * 2005-12-08 2007-06-14 International Business Machines Corporation Seamless reflection of model updates in a visual page for a visual channel in a composite services delivery system
US20070143485A1 (en) * 2005-12-08 2007-06-21 International Business Machines Corporation Solution for adding context to a text exchange modality during interactions with a composite services application
US8005934B2 (en) 2005-12-08 2011-08-23 International Business Machines Corporation Channel presence in a composite services enablement environment
US20070147355A1 (en) * 2005-12-08 2007-06-28 International Business Machines Corporation Composite services generation tool
US20070185957A1 (en) * 2005-12-08 2007-08-09 International Business Machines Corporation Using a list management server for conferencing in an ims environment
US8189563B2 (en) 2005-12-08 2012-05-29 International Business Machines Corporation View coordination for callers in a composite services enablement environment
US9854006B2 (en) 2005-12-22 2017-12-26 Genesys Telecommunications Laboratories, Inc. System and methods for improving interaction routing performance
US9008075B2 (en) 2005-12-22 2015-04-14 Genesys Telecommunications Laboratories, Inc. System and methods for improving interaction routing performance
US20110161927A1 (en) * 2006-09-01 2011-06-30 Verizon Patent And Licensing Inc. Generating voice extensible markup language (vxml) documents
US8594305B2 (en) 2006-12-22 2013-11-26 International Business Machines Corporation Enhancing contact centers with dialog contracts
US20080152121A1 (en) * 2006-12-22 2008-06-26 International Business Machines Corporation Enhancing contact centers with dialog contracts
US20080205628A1 (en) * 2007-02-28 2008-08-28 International Business Machines Corporation Skills based routing in a standards based contact center using a presence server and expertise specific watchers
US20080205624A1 (en) * 2007-02-28 2008-08-28 International Business Machines Corporation Identifying contact center agents based upon biometric characteristics of an agent's speech
US8259923B2 (en) 2007-02-28 2012-09-04 International Business Machines Corporation Implementing a contact center using open standards and non-proprietary components
US20080205625A1 (en) * 2007-02-28 2008-08-28 International Business Machines Corporation Extending a standardized presence document to include contact center specific elements
US20080219429A1 (en) * 2007-02-28 2008-09-11 International Business Machines Corporation Implementing a contact center using open standards and non-proprietary components
US9247056B2 (en) 2007-02-28 2016-01-26 International Business Machines Corporation Identifying contact center agents based upon biometric characteristics of an agent's speech
US9055150B2 (en) 2007-02-28 2015-06-09 International Business Machines Corporation Skills based routing in a standards based contact center using a presence server and expertise specific watchers
US9311420B2 (en) 2007-06-20 2016-04-12 International Business Machines Corporation Customizing web 2.0 application behavior based on relationships between a content creator and a content requester
US20080320079A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Customizing web 2.0 application behavior based on relationships between a content creator and a content requester
US8074202B2 (en) 2007-06-20 2011-12-06 International Business Machines Corporation WIKI application development tool that uses specialized blogs to publish WIKI development content in an organized/searchable fashion
US7890333B2 (en) 2007-06-20 2011-02-15 International Business Machines Corporation Using a WIKI editor to create speech-enabled applications
US8032379B2 (en) 2007-06-20 2011-10-04 International Business Machines Corporation Creating and editing web 2.0 entries including voice enabled ones using a voice only interface
US8041572B2 (en) 2007-06-20 2011-10-18 International Business Machines Corporation Speech processing method based upon a representational state transfer (REST) architecture that uses web 2.0 concepts for speech resource interfaces
US8041573B2 (en) 2007-06-20 2011-10-18 International Business Machines Corporation Integrating a voice browser into a Web 2.0 environment
US7631104B2 (en) 2007-06-20 2009-12-08 International Business Machines Corporation Providing user customization of web 2.0 applications
US20080320168A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Providing user customization of web 2.0 applications
US7996229B2 (en) 2007-06-20 2011-08-09 International Business Machines Corporation System and method for creating and posting voice-based web 2.0 entries via a telephone interface
US20080319757A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Speech processing system based upon a representational state transfer (rest) architecture that uses web 2.0 concepts for speech resource interfaces
US20080319762A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Using a wiki editor to create speech-enabled applications
US20080319742A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation System and method for posting to a blog or wiki using a telephone
US20080319761A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Speech processing method based upon a representational state transfer (rest) architecture that uses web 2.0 concepts for speech resource interfaces
US20080319759A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Integrating a voice browser into a web 2.0 environment
US8086460B2 (en) 2007-06-20 2011-12-27 International Business Machines Corporation Speech-enabled application that uses web 2.0 concepts to interface with speech engines
US20080319758A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Speech-enabled application that uses web 2.0 concepts to interface with speech engines
US20080319760A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Creating and editing web 2.0 entries including voice enabled ones using a voice only interface
US20080320443A1 (en) * 2007-06-20 2008-12-25 International Business Machines Corporation Wiki application development tool that uses specialized blogs to publish wiki development content in an organized/searchable fashion

Also Published As

Publication number Publication date
US20030009339A1 (en) 2003-01-09
US20030007609A1 (en) 2003-01-09
US20100057885A1 (en) 2010-03-04
US20100114578A1 (en) 2010-05-06
US20030018476A1 (en) 2003-01-23
WO2003005340A2 (en) 2003-01-16
CA2450887A1 (en) 2003-01-16
US20100050265A1 (en) 2010-02-25
US20130013299A1 (en) 2013-01-10
US20100318365A1 (en) 2010-12-16
US20030014670A1 (en) 2003-01-16
CN1522432A (en) 2004-08-18
US20110123006A1 (en) 2011-05-26
WO2003005340A3 (en) 2003-04-10
US7643998B2 (en) 2010-01-05
EP1428203A2 (en) 2004-06-16
EP1428203A4 (en) 2005-11-02

Similar Documents

Publication Publication Date Title
US20030055884A1 (en) Method for automated harvesting of data from a Web site using a voice portal system
US7406418B2 (en) Method and apparatus for reducing data traffic in a voice XML application distribution system through cache optimization
US7286985B2 (en) Method and apparatus for preprocessing text-to-speech files in a voice XML application distribution system using industry specific, social and regional expression rules
US20090144131A1 (en) Advertising method and apparatus
US7242752B2 (en) Behavioral adaptation engine for discerning behavioral characteristics of callers interacting with an VXML-compliant voice application
US7609829B2 (en) Multi-platform capable inference engine and universal grammar language adapter for intelligent voice application execution
US20110106527A1 (en) Method and Apparatus for Adapting a Voice Extensible Markup Language-enabled Voice System for Natural Speech Recognition and System Response
EP1486054B1 (en) System and method for providing a message-based communications infrastructure for automated call center operation
US20050152344A1 (en) System and methods for dynamic integration of a voice application with one or more Web services
US20050033582A1 (en) Spoken language interface
US20050027536A1 (en) System and method for enabling automated dialogs
AU2002354791A1 (en) Method and apparatus for improving voice recognition performance in a voice application distribution system

Legal Events

Date Code Title Description
AS Assignment

Owner name: FONELET TECHNOLOGY, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YUEN, MICHAEL S.;CHIU, LEO;REEL/FRAME:013300/0576

Effective date: 20020829

AS Assignment

Owner name: APPTERA, INC., CALIFORNIA

Free format text: CHANGE OF NAME;ASSIGNOR:FONELET TECHNOLOGY, INC.;REEL/FRAME:017407/0541

Effective date: 20030331

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION