Method for developing a dialog manager using modular spoken-dialog components

• US 8,630,859 B2
• Filed: 03/14/2008
• Issued: 01/14/2014
• Est. Priority Date: 03/01/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: AT&T Intellectual Property II LP (AT&T, Inc.)
• Inventors: DiFabbrizio, Giuseppe, Lewis, Charles Alfred
• Primary Examiner(s): Desir, Pierre-Louis
• Assistant Examiner(s): KOVACEK, DAVID M
• Application Number:
  US12/048,394
• Publication Number:
  US 20080184164A1
• Time in Patent Office: 2,132 Days
• Field of Search: 704/231, 704/246, 704251-258, 704270-278, 706/11, 706 45- 50, 706/55, 706/62
• US Class Current: 704/275
• CPC Class Codes: G06F 3/167 Audio in a user interface, e.g. using voice commands for navigating, audio feedback
• CPC Class Codes: G10L 15/22 Procedures used during a speech recognition process, e.g. man-machine dialogue

Abstract

A method of developing a dialog manager for a spoken dialog service is disclosed. The method comprises selecting a top level flow controller based on application type, selecting available reusable subdialogs for each application part, developing a subdialog for each application part not having an available subdialog and testing and deploying the spoken dialog service using the selected top level flow controller, selected reusable subdialogs and developed subdialogs. The method enables a developer to create a dialog manager that has individual reusable dialog modules that operate independent of the dialog model of the other modules. Application dependencies and context shifts are defined independent of the subdialogs to enable them to be reusable. The spoken dialog server manages context shifts in the spoken dialog by transitioning between dialog modules and subdialog modules.

Claims

1. A method comprising:

selecting a recursive transition network top level flow controller to yield a selected recursive transition network top level flow controller;

selecting available reusable subdialogs below the selected recursive transition network top level flow controller to yield a selected reusable subdialogs;

developing a subdialog for each application part not having an available subdialog, to yield developed subdialogs; and

testing and deploying (1) a spoken dialog service using the selected recursive transition network top level flow controller, (2) the selected reusable subdialogs, and (3) the developed subdialogs.

2. The method of claim 1, wherein the selected reusable subdialogs are isolated from application dependencies.

3. The method of claim 1, wherein the selected recursive transition network top level flow controller, the selected reusable subdialogs, and the developed subdialogs interact independent of their decision model.

4. The method of claim 1, wherein the available reusable subdialogs are selected from a group comprising:

telephone number, social security number, account number, address, e-mail address, and name.

5. The method of claim 1, wherein the reusable subdialogs manage mixed-initiative conversations with a user.

6. The method of claim 1, wherein an available reusable subdialog is an input subdialog.

7. The method of claim 6, wherein the available reusable subdialog further comprises a confirmation component.

8. The method of claim 6, wherein the reusable input subdialog handles silence, rejection, low confidence natural language understanding scores and explicit information in an input dialog with a user.

9. The method of claim 1, wherein the selected recursive transition network top level flow controller is a finite state model.

10. The method of claim 9, wherein the available reusable subdialogs are recursive transition network flow controllers.

11. The method of claim 9, wherein the available reusable subdialogs are rule-based flow controllers.

12. The method of claim 1, wherein a state in the selected recursive transition network flow controller has a subdialog attribute that is a name of a flow controller invoked as the subdialog.

13. The method of claim 12, wherein the state in the selected recursive transition network flow controller having the subdialog attribute that invokes a subdialog further comprises a set of instructions that retrieve values from a parent dialog and set values in the subdialog.

14. The method of claim 1, further comprising implementing a local context within a dialog data file associated with the spoken dialog service.

15. A method comprising:

selecting a recursive transition network top level dialog flow controller to yield a selected recursive transition network top level flow controller;

incorporating a context shift component;

selecting available reusable subdialogs for being invoked by the selected recursive transition network top level flow controller to yield selected reusable subdialogs; and

testing and deploying a spoken dialog service using the recursive transition network top level flow controller and selected reusable subdialogs, wherein when a user of the spoken dialog service changes a context of a spoken dialog while in a reusable subdialog, to yield a context shift, wherein the context shift causes a parent dialog of a subdialog to be set to a state described by the context shift.

16. The method of claim 15, wherein the reusable subdialogs are isolated from application dependencies.

17. The method of claim 15, wherein during the spoken dialog, when the subdialog is invoked by the parent dialog, the context shift causes the subdialog to inherit the context shift of the parent dialog.

18. The method of claim 17, wherein the context shift further returns a message to the parent dialog of the reusable subdialog that the context shift has occurred.

19. The method of claim 15, wherein the context shift is triggered by user input and generates a state name where the context shift goes.

20. The method of claim 15, wherein the application dependencies are part of the selected recursive transition network top level flow controller.

21. The method of claim 20, wherein the selected recursive transition network top level flow controller and the available reusable subdialogs interact independent of their decision models.

22. The method of claim 15, wherein the spoken dialog service supports chronological shifts in a dialog.

23. The method of claim 15, wherein the spoken dialog service supports digression in a dialog.