System for Factoring Synchronization Strategies From Multimodal Programming Model Runtimes

• US 20090013035A1
• Filed: 05/15/2008
• Published: 01/08/2009
• Est. Priority Date: 07/30/2004
• Status: Abandoned Application

• Current Assignee: Charles Wiecha, Jaroslav Gergic, Naikeung Thomas Ling, Rafah A. Hosn
• Original Assignee: Charles Wiecha, Jaroslav Gergic, Naikeung Thomas Ling, Rafah A. Hosn
• Inventors: Ling, Naikeung Thomas, Gergic, Jaroslav, Wiecha, Charles, Hosn, Rafah A.
• Application Number:
  US12/121,525
• Publication Number:
  US 20090013035A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A factored multimodal interaction architecture for a distributed computing system is disclosed. The distributed computing system includes a plurality of clients and at least one application server that can interact with the clients via a plurality of interaction modalities. The factored architecture includes an interaction manager with a multimodal interface, wherein the interaction manager can receive a client request for a multimodal application in one interaction modality and transmit the client request in another modality, a browser adapter for each client browser, where each browser adapter includes the multimodal interface, and one or more pluggable synchronization modules. Each synchronization module implements one of the plurality of interaction modalities between one of the plurality of clients and the server such that the synchronization module for an interaction modality mediates communication between the multimodal interface of the client browser adapter and the multimodal interface of the interaction manager.

Claims

1. A factored multimodal interaction architecture for a distributed computing system, said distributed computing system including a plurality of client browsers and at least one multimodal application server that can interact with said clients by means of a plurality of interaction modalities, said architecture comprising:

an interaction manager with a multimodal interface, wherein said interaction manager can receive a client request for a multimodal application in one interaction modality and transmit said client request in another modality; and

one or more pluggable synchronization modules, wherein each synchronization module implements one of the plurality of interaction modalities between one of the plurality of clients and the server so that a synchronization module for an interaction modality mediates communication between the client and the multimodal interface of the interaction manager.

2. The architecture of claim 1, further comprising a servlet filter that can intercept a client request for a multimodal application, and can pass that client request and a library of synchronization modules to the interaction manager, wherein the interaction manager can select a synchronization module appropriate for the client request from the library of synchronization modules.

3. The architecture of claim 1, further comprising a browser adapter for each client browser, each said browser adapter including the multimodal interface, wherein each multimodal interface of a client browser adapter and the multimodal interface of the interaction manager can communicate via a plurality of multimodal messages, and wherein a synchronization module for an interaction modality is instantiated by the interaction manager upon receiving a client request for that interaction modality, and wherein the synchronization module implements an exchange of multimodal messages between the multimodal interface of the client browser adapter and the multimodal interface of the interaction manager.

4. The architecture of claim 3, further comprising a synchronization proxy for each client for encoding said multimodal messages in an internet communication protocol.

5. The architecture of claim 3, wherein the multimodal messages include multimodal events and multimodal signals.

6. The architecture of claim 1, wherein the interaction manager is a state machine having an associated state, a loaded state, a ready state, and a not-associated state;

the client browser adapter is a state machine having an associated state, a loading state, a loaded state, and a ready state; and

a synchronization module is a state machine having an instantiated state, a loaded state, a ready state, and a stale state.

7. The architecture of claim 6, wherein the client browser adapter enters the associated state when a connection to either the interaction manager or another client has been established;

the client browser adapter enters the loading state when it is loading a document;

the client browser adapter enters the loaded state when it has completed loading the document; and

the client browser adapter enters the ready state when it is ready for multimodal interaction.

8. The architecture of claim 6, wherein the synchronization module enters the instantiated state when it has been instantiated but has no document to process;

the synchronization module enters the loaded state when it has been given a document to process but is waiting for a loaded signal from a client;

the synchronization module enters the ready state when it is ready to receive events and send synchronization commands; and

the synchronization module enters the stale state when the document being handled is no longer in view for the client.

9. The architecture of claim 6, wherein the interaction manager enters the associated state when any non-stale synchronization module is in the instantiated state;

the interaction manager enters the loaded state if any non-stale synchronization module is in the loaded state;

the interaction manager enters the ready state if all non-stale synchronization modules are in the ready state; and

the interaction manager enters the not-associated state when there is no client session associated with it.

10. The architecture of claim 1, further comprising an event control interface, by which a client browser adapter or the interaction manager can register or remove an event listener, or dispatch an event to another client browser adapter or to the interaction manager;

a command control interface by which a client browser adapter or the interaction manager can modify the state of another a client browser adapter by issuing a synchronization command; and

an event listener interface that can provide an event handler to a client browser adapter or the interaction manager.

11. A factored multimodal interaction architecture for a distributed computing system, said distributed computing system including a plurality of clients and at least one application server that can interact with said clients by means of a plurality of interaction modalities, said architecture comprising:

a servlet filter that can intercept a client request for a multimodal application;

an interaction manager with a multimodal interface, wherein said interaction manager can receive said client request for a multimodal application in one interaction modality and transmit said client request in another modality;

a browser adapter for each client browser, each said browser adapter including the multimodal interface, wherein the multimodal interface of a client browser adapter and the multimodal interface of the interaction manager can communicate via a plurality of multimodal messages, and wherein each browser adapter includes a synchronization proxy for encoding said multimodal messages in an internet communication protocol; and

one or more pluggable synchronization modules, wherein each synchronization module implements one of the plurality of interaction modalities between one of the plurality of clients and the server so that a synchronization module can receive events and send commands over an interaction modality channel between the multimodal interface of the client browser adapter and the multimodal interface of the interaction manager,

wherein said servlet filter can pass a library of synchronization modules to the interaction manager, wherein the interaction manager can select and instantiate a synchronization module appropriate for the client request from the library of synchronization modules to implement an exchange of multimodal messages between the multimodal interface of the client browser adapter and the multimodal interface of the interaction manager.

12. The architecture of claim 11, wherein the client browser adapter is a state machine having an associated state when a connection to either the interaction manager or another client has been established;

a loading state when it is loading a document;

a loaded state when it has completed loading the document; and

a ready state when it is ready form multimodal interaction.

13. The architecture of claim 12, wherein the synchronization module is a state machine having an instantiated state when it has been instantiated but has no document to process;

a loaded state when it has been given a document to process but is waiting for a loaded signal from a client;

a ready state when it is ready to receive events and send synchronization commands; and

a stale state when the document being handled is no longer in view for the client.

14. The architecture of claim 13, wherein the interaction manager is a state machine having an associated state when any non-stale synchronization module is in the instantiated state;

a loaded state when any non-stale synchronization module is in the loaded state;

a ready state if all non-stale synchronization modules are in the ready state; and

a not-associated state when there is no client session associated with it.

15. The architecture of claim 11, further comprising an event control interface, by which a client browser adapter or the interaction manager can register or remove an event listener, or dispatch an event to another client browser adapter or to the interaction manager;

a command control interface by which a client browser adapter or the interaction manager can modify the state of another a client browser adapter by issuing a synchronization command; and

an event listener interface that can provide an event handler to a client browser adapter or the interaction manager.

16. A factored multimodal interaction architecture for a distributed computing system, said distributed computing system including a plurality of clients and at least one application server that can interact with said clients by means of a plurality of interaction modalities, said architecture comprising:

a servlet filter that can intercept a client request for a multimodal application;

an interaction manager with a multimodal interface, wherein said interaction manager can receive said client request for a multimodal application in one interaction modality and transmit said client request in another modality, said interaction manager being a state machine having an associated state, a loaded state, a ready state, and a not-associated state;

a browser adapter for each client browser, each said browser adapter including the multimodal interface, wherein the multimodal interface of a client browser adapter and the multimodal interface of the interaction manager can communicate via a plurality of multimodal messages, and wherein each browser adapter includes a synchronization proxy for encoding said multimodal messages in an internet communication protocol, said client browser adapter being a state machine having an associated state, a loading state, a loaded state, and a ready state;

one or more pluggable synchronization modules, wherein each synchronization module implements one of the plurality of interaction modalities between one of the plurality of clients and the server so that a synchronization module can receive events and send commands over an interaction modality channel between the multimodal interface of the client browser adapter and the multimodal interface of the interaction manager, each said synchronization module being a state machine having an instantiated state, a loaded state, a ready state, and a stale state;

an event control interface, by which a client browser adapter or the interaction manager can register or remove an event listener, or dispatch an event to another client browser adapter or to the interaction manager;

a command control interface by which a client browser adapter or the interaction manager can modify the state of another a client browser adapter by issuing a synchronization command; and

an event listener interface that can provide an event handler to a client browser adapter or the interaction manager,

wherein said servlet filter can pass a library of synchronization modules to the interaction manager, wherein the interaction manager can select and instantiate a synchronization module appropriate for the client request from the library of synchronization modules to implement an exchange of multimodal messages between the multimodal interface of the client browser adapter and the multimodal interface of the interaction manager.

17. The architecture of claim 16, wherein the client browser adapter enters the associated state when a connection to either the interaction manager or another client has been established;

the client browser adapter enters the loading state when it is loading a document;

the client browser adapter enters the loaded state when it has completed loading the document; and

the client browser adapter enters the ready state when it is ready form multimodal interaction.

18. The architecture of claim 16, wherein the synchronization module enters the instantiated state when it has been instantiated but has no document to process;

the synchronization module enters the loaded state when it has been given a document to process but is waiting for a loaded signal from a client;

the synchronization module enters the ready state when it is ready to receive events and send synchronization commands; and

the synchronization module enters the stale state when the document being handled is no longer in view for the client.

19. The architecture of claim 16, wherein the interaction manager enters the associated state when any non-stale synchronization module is in the instantiated state;

the interaction manager enters the loaded state if any non-stale synchronization module is in the loaded state;

the interaction manager enters the ready state if all non-stale synchronization modules are in the ready state; and

the interaction manager enters the not-associated state when there is no client session associated with it.