International Business Machines Corporation

Christopher Hyland

Martin J Hirzel

Nicolas Changhai Ke

William M Quinn

Steven I Ross

Jeffrey G MacAllister

Marijane M Zeller

Kathleen A Howard

Andrew M Ortwein

Christopher D Price

Aseel Aziz-Gomez

Ron E Pontrich

Ramya Sethuraman

William Michael Quinn

Ronald Eugene Pontrich

A method and system are provided. The method includes separating a predicate that specifies a set of events into a temporal part and a non-temporal part. The method further includes comparing the temporal part of the predicate against a predicate of a known window type. The method also includes determining whether the temporal part of the predicate matches the predicate of the known window type. The method additionally includes replacing (i) the non-temporal part of the predicate by a filter, and (ii) the temporal part of the predicate by an instance of the known window type, responsive to the temporal part of the temporal predicate matching the predicate of the known window type. The instance is parameterized with substitutions used to match the temporal part of the predicate to the predicate of the known window type.

Discovering windows in temporal predicates

A system for providing resource-based synchronization between clients in a Web-based real-time collaboration, in which a session front end on the server layers a transaction history on top of all session resources. HTTP operations are issued by client systems to request changes to session resources and to request session updates. The HTTP resource change requests include hierarchical pointers containing session identifiers and resource identifiers within a URL. The client generated resource change request operations may be HTTP PUT, HTTP DELETE, and HTTP POST commands. The HTTP session update request operations may be HTTP GET commands. A session front end stores each received resource change request operation in a resource-specific transaction history of change request operations received from all client systems. The session front end maintains a current session state indicating the number of resource change request operations stored for each session resource. A last session state for each client system indicates the number of change request operations that client system has previously received for each session resource. For a session update, the session front end compares the last client session state for the requesting client with the current session state and determines the change request operations that need to be forwarded to the requesting client system to bring it up to date. The session front end removes negating change request operations from the change request operations forwarded to the requesting client system.

Resource-based synchronization between endpoints in a web-based real time collaboration

An initial browser window establishes itself as a 'master' window for an associated server. A master window 'cookie' data structure is created by the master window to share state among the windows for the server. Through the initially created master window cookie, all subsequently created browser windows detect that a master window is currently active, determine the master window's window name, and then establish themselves as slave windows through the master window. Slave windows call into the master window to request server updates/events, and provide the master window with their respective window names for future reference, e.g. when the master window distributes updates/events received from the server to the slave windows. The master window uses only a single HTTP GET command to fetch and dispatch updates/events associated with itself and all slave windows for the server.

Dispatching events to multiple browser windows/tabs using a single connection

A dialog management system functions to manage the dialog between a user of a computer system and one or more speech enabled software applications. The user provides spoken input to a microphone connected to the computer system, and hears responses from one or more applications through a speaker connected to the computer system. The dialog management system includes a dialog manager, a turn manager, a speak queue, dialog contexts, and dialog state. The dialog manager provides top-level control of the dialog and stores responses based on the user's spoken input in a speak queue for later output to the user. The turn manager controls delivery of the responses to the user based on the dialog context and the dialog state, to provide a polite asynchronous dialog with the user that enables the user to be in control of the dialog. The dialog context provides information about each dialog. The dialog state provides information about whose turn it is (computer or user) to speak.

Method and Apparatus for managing dialog management in a computer conversation

A dialog management system functions to manage the dialog between a user of a computer system and one or more speech enabled software applications. The user provides spoken input to a microphone connected to the computer system, and hears responses from one or more applications through a speaker connected to the computer system. The dialog management system includes a dialog manager, a turn manager, a speak queue, dialog contexts, and dialog state. The dialog manager provides top-level control of the dialog and stores responses based on the user's spoken input in a speak queue for later output to the user. The turn manager controls delivery of the responses to the user based on the dialog context and the dialog state, to provide a polite dialog with the user that enables the user to be in control of the dialog. The dialog context provides information about each dialog. The dialog state provides information about whose turn it is (computer or user) to speak.

Method and apparatus for performing dialog management in a computer conversational interface

Growing community of inventors

Foxboro, MA, United States of America

Christopher Hyland