US2013013299A1PendingUtilityA1

Method and apparatus for development, deployment, and maintenance of a voice software application for distribution to one or more consumers

54
Assignee: APPTERA INCPriority: Jul 3, 2001Filed: Sep 14, 2012Published: Jan 10, 2013
Est. expiryJul 3, 2021(expired)· nominal 20-yr term from priority
H04M 3/4938G10L 15/30G10L 2015/228
54
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system for developing, deploying and maintaining a voice application over a communications network to one or more recipients has a voice application server connected to a data network for storing and serving voice applications, 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, 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 creates voice applications through object modeling and linking, stores them for deployment in the application server, and manages deployment and state of deployed applications including scheduled deployment and repeat deployments in terms of intended recipients.

Claims

exact text as granted — not AI-modified
1 . A system for developing and deploying a voice application over a communications network to one or more recipients, the system comprising:
 a voice application server connected to a data network for storing and serving voice applications;   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; 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 creates voice applications through object modeling and linking, stores them for deployment in the application server, and manages deployment and state of deployed applications including scheduled deployment and repeat deployments in terms of intended recipients.   
     
     
         2 . The system of  claim 1  wherein the communications network is a telephony network accessible to the data network. 
     
     
         3 . The system of  claim 1  wherein the voice application server serves voice applications through the data network to the network communications server. 
     
     
         4 . The system of  claim 1  wherein the network communications server is a telephony server that is VXML compliant and is connected to a telephony network. 
     
     
         5 . The system of  claim 4  wherein the telephony network is a PSTN network. 
     
     
         6 . The system of  claim 1  wherein the computer station and the voice application server share the same physical domain. 
     
     
         7 . The system of  claim 1  wherein the communications server is an Internet server enabled for voice using VXML. 
     
     
         8 . The system of  claim 1  wherein the one or more recipients use one of a telephone and a computer to access the voice application. 
     
     
         9 . The system of  claim 1  further comprising a dialog controller within the voice application server, the dialog controller adapted to access business rules and to access stored data according to interpretation of dialog responses received. 
     
     
         10 . A software application for designing and deploying voice applications over a communications network, the software application comprising:
 a client interface for creating and managing contacts for receiving voice applications;   a client interface for designing dialogs including responses of a voice application;   a client interface for creating and managing actions related to dialog deployment based on call exception handling; and   a client interface for integrating dialogs and data fetch and send operations to form a complete executable voice application;   characterized in that the operations configured and executed are parameters of dialog objects integrated to form the voice application and wherein execution of a first dialog object results in at least one of an expected state including interaction resulting in subsequent execution of further dialog objects and or configured actions including data fetch and send operations associated with the objects and with interaction with the dialogs.   
     
     
         11 . The software application of  claim 10  wherein the communications network is a telephony network accessible to a data network. 
     
     
         12 . The software application of  claim 10  adapted to run on a computer station. 
     
     
         13 . The software application of  claim 10  wherein the client interface is platform independent. 
     
     
         14 . A method for developing an interactive voice application using an object oriented software application, the method comprising:
 (a) naming and describing a voice application under development;   (b) identifying contacts for receiving the voice application;   (c) creating at least one executable dialog defining the voice application;   (d) applying business rules and exception handling rules for each dialog created;   (e) configuring the state of execution of the voice application; and   (d) deploying the voice application for launch according to type.   
     
     
         15 . The method of  claim 14  wherein in step (c) the dialog is configured for one of inbound deployment or outbound deployment. 
     
     
         16 . The method of  claim 14  wherein in step (d) the exceptions are telephony events. 
     
     
         17 . The method of  claim 14  wherein in step (e) the configuring includes scheduling parameters.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.