Unified messaging state machine

• US 8,074,199 B2
• Filed: 09/24/2007
• Issued: 12/06/2011
• Est. Priority Date: 09/24/2007
• Status: Active Grant

• Current Assignee: Zhigu Holdings Limited
• Original Assignee: Microsoft Corporation
• Inventors: Millett, Thomas W., Manda, Srinivasa
• Primary Examiner(s): Zhen, Li
• Assistant Examiner(s): COYER, RYAN D
• Application Number:
  US11/860,028
• Publication Number:
  US 20090083709A1
• Time in Patent Office: 1,534 Days
• Field of Search: 717/100
• US Class Current: 717/100
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A unified messaging (UM) application benefits from platform independence and human intelligibility of eXtended Markup Language (XML). A finite state machine (FSM) of the UM application is created utilizing an XML feature to create a valid menu state based upon a UM software component. For a UM software component that is a context or setting of the UM application, an XML conditional attribute conditions a prompt, transition or grammar node of the UM FSM. For a UM software component that is an XML snippet, an XML importation element replicates the XML snippet upon compilation, avoiding time-consuming and error prone requirements for manual code duplication. For a UM software component such as an external method, function, variable or action, a function wrapping XML tool validates the existence of such external UM software components at build time and captures version information to verify the availability of the same version upon execution.

Claims

1. A computer-implemented system for programming a unified messaging (UM) application, comprising:

a user interface;

a programming environment operating on at least one computing device and accessed via the user interface for composing in an eXtensible Markup Language (XML) a UM finite state machine (FSM) comprising menu states defined by a plurality of user prompts and transitions between user prompts, each transition defined by a particular user response to a prompt;

a UM software component including an external software component called by the UM FSM;

an XML feature utilized by the programming environment to create a valid menu state based upon the UM software component, wherein the XML feature includes a function wrapper that is used by the programming environment to validate the external software component during a compilation phase when the external software component is present and generate a binary UM FSM, and to generate an error when the external software component is absent during the compilation phase; and

a verification tool invoked during execution of the binary UM FSM that confirms that a version of the external software component present during a compilation phase is the same as a version of the external software component available at execution.

2. The computer-implemented system of claim 1, wherein the UM software component comprises a setting of the UM application, the XML feature comprises a conditional attribute predetermining a transition of the UM FSM.

3. The computer-implemented system of claim 2, wherein the conditional attribute comprises an attribute composed of a context variable.

4. The computer-implemented system of claim 3, wherein the conditional attribute comprises an attribute composed of a plurality of context variables combined by at least one logical operator suitable for parsing into a parse tree.

5. The computer-implemented system of claim 2, wherein the UM software component comprises a grammar node, the XML feature comprises a conditional element attribute making a command grammar selectively active.

6. The computer-implemented system of claim 1, wherein the UM software component comprises an XML snippet, the XML feature comprising an importation element utilized by the programming environment to replicate the XML snippet upon compilation.

7. The computer-implemented system of claim 6, wherein the XML snippet comprises a speech menu defining prompts and transitions in response to a nonresponsive user utterance.

8. The computer-implemented system of claim 7, wherein the nonresponsive user utterance is one or more responses selected from a group consisting of a silence, a mumble, and a word not applicable in current context.

9. The computer-implemented system of claim 1, wherein the external software component is one of a group consisting of a method, function, variable and action.

10. The computer-implemented system of claim 1, further comprising an automated speech recognition menu for defining a semantic event as one of a plurality of user responses semantically equivalent to the user prompts, the transitions dependent upon a particular semantic event.

11. The computer-implemented system of claim 1, further comprising a dial tone multi frequency (DTMF) interface that defines a semantic event as a DTMF keypad input.

12. A method for developing a user interface to a unified messaging (UM) system, comprising:

generating a finite state machine with at least one computing device, the finite state machine composed of menu states prompting a user and transitions to a next menu state in accordance with a user response; and

generating a valid menu state based upon an existing external UM software component by employing an eXtensible Markup Language (XML) feature, wherein creating a valid menu state comprises;

generating a function wrapper for the XML feature;

during a compilation phase, using the function wrapper to validate the external UM software component when the external UM software component is present and generating a binary of the UM finite state machine; and

during execution of the binary of the UM finite state machine, confirming that a version of the external UM software component present during the compilation phase is the same as a version of the external UM software component available at execution; and

generating the valid menu state of the user interface including at least one user prompt.

13. The method of claim 12, wherein creating the valid menu state is based upon an XML snippet duplicated in the finite state machine by an XML importation element.

14. The method of claim 12, wherein creating a valid menu state is based upon a context variable referenced by an XML conditional attribute of an XML element defining a prompt or transition.

15. The method of claim 12, wherein creating a valid menu state is validated by wrapping called actions and variables of the finite state machine that reference in an external UM software component and creating a build time error if not locatable.

16. The method of claim 15, further comprising verifying that an external UM software component referenced by a compiled version of the finite state machine is identical upon execution as when validated.