VoiceXML browser and supporting components for mobile devices

1. A mobile device, comprising:

components supporting a VoiceXML browser, the components resident and executing on the mobile device and comprising at least one of:

a Resource Manager operable to serve one of locally stored files and files accessible via a network connection utilizing at least one of wireless and mobile broadband capabilities of the mobile device,

a Call Data Manager operable to communicate call-specific data to at least one of an application's system of origin and another configured target system,

a MRCP Gateway Client operable to provide the VoiceXML browser with access to media resources via a MRCP Gateway Server; and

a mobile voice self service (MVSS) bootstrap application and an XML-based MVSS configuration file, both resident and executing on the mobile device and both separate from the VoiceXML browser, wherein the bootstrap application configures the at least one of the supporting components and launches a voice application on the at least one of the components, and wherein the configuration file contains configuration settings for the at least one of the supporting components, defines session data and credentials for the voice application, and provides an initial URI to access the voice application.

2. The mobile device as claimed in claim 1 , wherein the mobile device launches an MVSS application when a user of the mobile device follows a link that provides MVSS content.

3. The mobile device as claimed in claim 1 , wherein at least one of the supporting components is operable to communicate via Application Programming Interfaces (APIs) open to other applications running on the mobile device and wherein a call to the APIs must pass an ID that was returned as a response to a configuration request.

4. The mobile device as claimed in claim 1 , wherein MVSS enables a VoiceXML browser to be deployed as a mobile application and implemented on the mobile device, further enabling a VoiceXML application to be processed directly on the mobile device.

5. The mobile device as claimed in claim 1 , wherein the mobile device is a mobile telephone.

6. The mobile device as claimed in claim 1 , wherein the mobile device further provides access to call flow data, enabling user-define bookmarks in a VoiceXML application.

7. The mobile device as claimed in claim 1 , wherein the VoiceXML browser is operable to at least one of suspend and resume execution of a VoiceXML application.

8. The mobile device as claimed in claim 7 , wherein at least one of the mobile device, a user of the mobile device, and a call to Application Programming Interfaces (APIs) of the VoiceXML browser initiates the at least one of suspending and resuming of the VoiceXML application.

9. The mobile device as claimed in claim 1 , wherein the VoiceXML browser is operable to display alternative text and user responses for a voice application on-screen as a log of the user's interaction with the voice application.

10. The mobile device as claimed in claim 1 , wherein the VoiceXML browser is operable to display VoiceXML menu tags from a voice application as an on-screen graphical menu.

11. The mobile device as claimed in claim 1 , wherein the VoiceXML browser is operable to report status and application information to at least one of other components and applications on the mobile device.

12. A method, comprising:

supporting operation of a VoiceXML browser executing locally on a mobile device with supporting components including at least one of a Resource Manager, a Call Data Manager, and a MRCP Gateway Client, the at least one of the supporting components resident and executing on the mobile device;

serving one of locally stored files and files accessible via a network connection utilizing at least one of wireless and mobile broadband capabilities of the mobile device, when the mobile device includes the Resource Manager;

communicating call-specific data to at least one of an application's system of origin and another configured target system, when the mobile device includes the Call Data Manager;

providing the VoiceXML browser with access to media resources via a MRCP Gateway Server, when the mobile device includes the MRCP Gateway Client; and

executing a mobile voice self service (MVSS) bootstrap application and an MVSS configuration file resident on the mobile device wherein the bootstrap application configures the at least one of the supporting components and launches a voice application on the at least one of the components, and wherein the configuration file contains configuration settings for the at least one of the supporting components, defines session data and credentials for the voice application, and provides an initial URI to access the voice application.

13. The method as claimed in claim 12 , further comprising launching an MVSS application when a user of the mobile device follows a link that provides MVSS content.

14. The method as claimed in claim 12 , wherein the at least one of the supporting components is operable to communicate via Application Programming Interfaces (APIs) open to other applications running on the mobile device, wherein when a call to the APIs is made, the method further comprises passing an ID that was returned as a response to a configuration request.

15. The method as claimed in claim 12 , further comprising providing direct access to call flow data, and enabling user-defined bookmarks via a VoiceXML application.

16. The method as claimed in claim 12 , further comprising initiating at least one of suspending and resuming execution of a VoiceXML application via at least one of the mobile device, a user of the mobile device, and a call to Application Programming Interfaces (APIs) of the VoiceXML browser.

17. The method as claimed in 12 , further comprising displaying alternative text and user responses for the voice application on-screen as a log of the user interaction with the voice application.

18. The method as claimed in claim 12 , further comprising displaying VoiceXML menu tags from the voice application as an on-screen graphical menu.

19. The method as claimed in claim 12 , further comprising reporting status and application information to at least one of other components and applications on the mobile device.

20. A non-transitory machine readable storage medium comprising instructions for:

supporting operation of a VoiceXML browser executing locally on a mobile device with supporting components including at least one of a Resource Manager, a Call Data Manager, and a MRCP Gateway Client wherein the at least one of the supporting components reside on the mobile device;

serving one of locally stored files and files accessible via a network connection utilizing at least one of wireless and mobile broadband capabilities of the mobile device, when the mobile device includes the Resource Manager;

communicating call-specific data to at least one of an application's system of origin and another configured target system, when the mobile device includes the Call Data Manager;

providing the VoiceXML browser with access to media resources via a MRCP Gateway Server, when the mobile device includes the MRCP Gateway Client; and

executing a mobile voice self service (MVSS) bootstrap application and an MVSS configuration file resident on the mobile device wherein the bootstrap application configures the at least one of the supporting components and launches a voice application on the at least one of the components, and wherein the configuration file contains configuration settings for the at least one of the supporting components, defines session data and credentials for the voice application, and provides an initial URI to access the voice application.