US 6,948,129 B1Grant
Multi-modal, multi-path user interface for simultaneous access to internet data over multiple media
Issue Date:2005-09-20
•20 Claims
•3 Drawing Sheets
Abstract
A method for simultaneous multi-path, multi-modal, and multi-user interface to users is discussed, where multiple inputs during the same user session arriving from different devices are handled properly. Each input is assigned a unique identifier, clocked with a counter and associated with an address. Other inputs that attempt to arrive at the same location are discarded.
Metadata
Inventor
- Masoud S Loghmani
Application Information
Application Number:US 10/067,985
Filing Date:2002-02-08
Priority Date:2001-02-08
Art Unit:2173
Patent Drawings (3 sheets)
Description
[0001] This application claims the benefit of U.S. provisional application Ser. No. 60/267,206, filed Feb. 8, 2001.
Field of the Invention
[0002] The present invention relates to a method and apparatus for providing simultaneous multi-path inputs in a system with multiple simultaneous input and output modes such as voice and display/keyboard, or system where many users may interact with the same sessions, such as a remote learning session where multiple students attend a given class. The present invention resolves the issue of two or more input values from multiple different devices or users attempting to occupy the same location.
Background of the Invention
[0003] Various services now provide voice and non-voice access to Internet data. A caller may access a “Voice Portal” or “Voice Site” by simply dialing a number advertised by the company providing the Voice Access service. The caller will hear a greeting that requests the caller to “speak” or “enter” specific commands. As an example, a caller may ask the system to provide him/her with the latest weather information by simply speaking a command, or pressing a DTMF button on the phone. The information provided to the user may be pre-recorded and accessed from a database, or it may be accessed from a page similar to those available on the Internet. The mark-up language used to code the page may be VoiceXML or any other type of XML-based coding language. Some legacy systems may use proprietary or less commonly used methods for connecting the system to back-end data servers.
[0004] However, in all existing systems, users interact with data only through one interface, that is, either a voice interface (e.g., a telephone) or a data interface (e.g. an Internet browser). This single mode interaction causes limitations on delivery of services to users. As an example, a user who is driving a car may ask for address information between point A and point B by issuing voice commands, and hear back the directions read to him via a speaker in the car. However, the same navigation information would not be available in graphical format. Another example is a user who is using a data-enabled mobile phone to review his investment portfolio. The user may wish to see the data, but input the queries by simply speaking them into the phone. Current systems do not allow for such capability.
[0005] Another limitation of existing systems is that they do not allow more than one user to interact with an application in one session. The present invention makes this possible. One example of where this may be required is a cooperative form filling application where two users need to be logged onto the same session, and each answers specific questions as they are presented. The present invention makes it possible for the two attendants to call into the system, and interact with the same application through a single session, thereby filling one form by two users.
[0006] The problem that arises in multi-modal or multi-user interaction with a single session (as in the above examples) is that multiple input values may be received for the same query through different channels. A simple solution would be to accept the first chronologically arriving input value, and discard the subsequent ones. This solution, however, fails when there are many rounds of query-input in the same application. Consider the case of a query A followed by two inputs a-1 and a-2. Input a-1 is accepted, but before input a-2 arrives in the system, another query B is made. Now input a-2 arrives in the system followed by a valid input b-1. The system would accept false input a-2, and discard valid input b-1. FIG. 1 illustrates when “Accept First Input” fails in the case of multiple queries and inputs. Throughout the FIGS. 1 , 2 and 3, the sunburst symbol 12 represents an accepted input, and the crossed-out symbol 14 represents an incorrectly accepted input or an incorrectly discarded input, for illustrative purposes.
[0007] The solution to this problem is to identify every input with the name of the query that it is attempting to address. In this case, the system would know that the second a-2 input is not intended for query B, would discard it, and would accept the valid input b-1.
[0008] However, this solution also falls short when the same dialog is repetitively used. For example if the system makes a query A for the first time (designated as A1). Two responses a1-1 and a1-2 are sent back. Response a-1 is accepted as valid, but before response a1-2 arrives, the system repeats the same dialog, repeating query A (designated as A2). User(s) reply with a response a2-1. However, false response a1-2 arrives first, is accepted as valid, and valid input a2-1 is discarded as invalid. FIG. 2 “Accept Tagged Input” fails when the same dialog is repeated.
Summary of the Invention
[0009] The present invention resolves the above-described problem by adding a query turn indicator (invocation counter) to each input name, and then accepting only those response values whose tag and turn indicator match the expected input. For example, when query A is made for the first time, the system registers an open slot for input values matching query A-1. User inputs are all tagged in the same fashion so that all inputs in response to query A-1 would be tagged as A-1-n (n being the path identifier). FIG. 3 illustrates how “Accept Tagged Input with Turn Indicator” accepts only the proper input. As seen in FIG. 3 , this method allows the system to properly identify the response values, and discard the false ones.
[0010] The present invention is a gateway for simultaneous multi-path, multi-modal, and multi-user access to data and applications via non-voice and voice devices. It takes into account the issue of processing inputs collected from multiple users or multiple devices when they are all interacting with the same single application in the same single session. It also resolves the issue of simultaneous inputs made in response to consecutive queries in different states.
[0011] The method of simultaneous, multi-path inputs of the present invention enables inputs to be made via any voice interface or data interface devices (e.g. phone, Keyboard, PDA, etc.) used during the same session. The inputs are fed to the session object, and given unique identifiers, or unique “tickets” for each input. An invocation counter in turn tracks when the inputs are made. The inputs and their associated identifiers are stored in the memory of the session object.
[0012] Each time an input is received in response to a query, the gateway checks to see whether the input ticket matches that of the most recent query. If so, the input is accepted, otherwise, the input is discarded.
Brief Description of Drawings
[0013] The various aspects, advantages and novel features of the present invention will be more readily comprehended from the following detailed description when read in conjunction with the appended drawings, in which:
[0014] FIG. 1 illustrates when a conventional “Accept First Input” fails in the case of two consecutive queries and two nearly simultaneous responses to the first query, and how the second input (made in response to the first query) may be accepted by mistake as a valid response to the second query;
[0015] FIG. 2 illustrates when a conventional “Accept Tagged Input” fails when the same dialog is repeated, and that, if the input data is tagged to the dialog alone, a problem occurs if the same dialog is repeated twice, and the second input (made in response to the first query) is accepted by mistake as a valid response to the second query;
[0016] FIG. 3 illustrates when “Accept Tagged Input with Turn Indicator” accepts only the proper input in accordance with an embodiment of the present invention; and
[0017] FIG. 4 illustrates how Inputs A and B are made simultaneously, and how Input B attempts to occupy the same location as Input A but is discarded in accordance with an embodiment of the present invention.
Detailed Description of Preferred Embodiments
[0018] With reference to FIG. 4 , a software method is provided in accordance with the present invention to allow one or more users to interact with data and applications in using multiple modes of interaction (voice, data, etc.) simultaneously. The solution comprises four main components, that is,
-
- [0019] a Session Management Gateway (7) capable of interacting with an application (9) via the Internet (6) from the one side (i.e., using standard Internet protocols for connection to Internet-based applications) and multiple client interfaces such as a Telephone Interface (3) or a Data Device interface (5) from the other side, and also capable of maintaining the transaction session with the Application (9) separate from interaction sessions with client devices, and capable of maintaining the interaction session with the application (9) in a database (8) even if no client device is connected at that moment to the session pertaining to the said transaction.
- [0020] a Data Device Interface (5) capable of interacting with data devices (4) equipped with display, keyboard, sound interface, location sensor, and so on. Data device (4) may have any combination of one or more human or machine data sources which can relay user input (e.g., a keyboard) or produce data automatically (e.g., a location sensor), as well as modules which can present data (e.g., a display that shows the data to a human, or a relay that uses the data to control an engine).
- [0021] a Telephony Interface (3) that allows callers to access their sessions using any type of voice interface devices (e.g. a mobile phone (1)), via a network such as a public switched telephone network (PSTN) (2) and is capable of presenting the data to the user in audible fashion, and also capable of collecting input from the user in spoken fashion (spoken commands) as well as other forms such as DTMF input.
- [0022] A Database (8) which maintains transaction sessions controlled by Session Management Gateway (7).
[0023] With reference to FIG. 4 , a software system for voice and non-voice access to data and application for simultaneous multi-path user access is shown that uses a ticketing mechanism to track the order of the inputs in accordance with the present invention. Voice devices can include telephone-based devices as well as microphone access to an Internet system. Non-voice devices can include keyboard, Personal Digital Assistant (PDA). As shown in FIG. 4 , Inputs A and B are made simultaneously. Input B tries to occupy the same location as Input A, but is discarded.
[0024] A simultaneous input session involves concurrent inputs from multiple devices. In FIG. 4 , the application in the backend (9) issues Query 1 to the Session Management Gateway (7). Query 1 is formatted for each client, and is assigned a unique identifier and an invocation counter identifying how many times the same exact query in this dialog has been visited in this session. The resulting query is then sent to all client interfaces currently logged to the transaction session pertaining to this interaction. In response to Query 1, user makes an utterance in the mobile phone (1), which is taken as Input A. Each client interface will attach the proper identifier and invocation counter to the input phrases arriving from the client interface, and sends that to Session Management Gateway (7).
[0025] It is obvious to those trained in the art that the same string could contain the unique identifier and the invocation counter.
[0026] For example, the user is using the system to order food. The user has both voice and keyboard access. When asked what kind of cuisine is desired, the user types, “Chinese” (Input A). Because the user is anxious, she simultaneously says into the microphone “Chinese” (Input B) during a system delay. The system then prompts, “You want to order Chinese food?” The user changes her mind and says, “No.” When the system returns to the menu, the voice input, “Chinese,” arrives (delayed) but is denied because it was made during an earlier invocation.
[0027] Although the present invention has been described with reference to a preferred embodiment thereof, it will be understood that the invention is not limited to the details thereof. Various modifications and substitutions have been suggested in the foregoing description, and others will occur to those of ordinary skill in the art. All such substitutions are intended to be embraced within the scope of the invention as defined in the appended claims.
[0028] A method and system for providing a simultaneous, multi-path, multi-modal, and multi-user interface to users is discussed, where multiple inputs during the same user session arriving from different devices are handled properly. Each input is assigned a unique identifier, clocked with a counter and associated with an address. Other inputs that attempt to arrive at the same location are discarded.
Claims
1. A system that allows multiple devices to access the same transaction session at the same time, the system comprising:
a session management gateway connected to an application with which the transaction session is established and to the multiple devices; and
a memory device;
wherein the session management gateway is programmable to process a query from the application for transmission to the multiple devices and to process simultaneous inputs from the multiple devices in response to the query during the transaction session by assigning a unique identifier to the query and providing a query turn indicator, the unique identifier and the query turn indicator being stored in the memory device, transmitted with the query to the multiple devices logged to the transaction session and attached by the multiple devices receiving the query to the inputs generated via the multiple devices, the session management gateway being operable to compare the unique identifier and the query turn indicator received with the inputs with the unique identifier and the query turn indicator corresponding to the query and stored in the memory device to process the inputs received from all of the multiple devices in response to the query properly by accepting the corresponding one of the inputs when a match is determined, and discarding the inputs responding to the query that are identified as subsequently received via their respective query turn indicators.
2. A system as claimed in claim 1, wherein the session management gateway is configured to allow multiple users to access the same transaction session and concurrently interact with that transaction session via different multiple devices.
3. A system as claimed in claim 1, wherein the session management gateway is configured to allow for inputs from devices selected from the group consisting of a computer keyboard, a microphone, a phone, other data input device, and other voice input device at the same time while responding with the appropriate outputs.
4. A system as claimed in claim 1, wherein different types of inputs can be received concurrently and processed during the transaction session, the different types of inputs being spoken inputs and keypad inputs.
5. A system as claimed in claim 1, wherein the session management gateway is programmable to format the query for use by different types of the multiple devices requiring different formats.
6. A system as claimed in claim 1, wherein the session management gateway is programmable to indicate the unique identifier as invalid in the memory device to prevent incorrect inputs from being accepted by the session management gateway as valid when query is repeated.
7. A system as claimed in claim 1, wherein the session management gateway comprises a counter and operates the counter as an invocation counter for the query turn indicator to track when the inputs are made.
8. A system as claimed in claim 1, wherein the query turn indicator identifies how many times the session management gateway has sent queries to the multiple devices.
9. A system as claimed in claim 1, further comprising a database connected to the session management gateway for storing data relating to the transaction session.
10. A system as claimed in claim 9, wherein the session management gateway is programmable to maintain data relating to said transaction session with the application in the database separate from interaction sessions with the multiple devices and interaction sessions with the application.
11. A system as claimed in claim 10, wherein the interaction session with the application is maintained in the database even if none of the multiple devices are connected to the transaction session.
12. A method for managing concurrent inputs from multiple devices in response to a query, the multiple devices interacting with the same application in the same transaction session, the method comprising the steps of:
assigning a unique identifier to the query;
providing a query turn indicator;
storing the unique identifier and the query turn indicator in a memory device;
transmitting the unique identifier and the query turn indicator with the query to the multiple devices logged to the transaction session;
attaching the unique identifier and the query turn indicator to the inputs generated via the multiple devices,
receiving transmitted ones of the inputs;
comparing the unique identifier and the query turn indicator received with the inputs with the unique identifier and the query turn indicator corresponding to the query and stored in the memory device;
accepting the corresponding one of the inputs when a match is determined, and
discarding the inputs responding to the query that are identified as subsequently received via their respective query turn indicators.
13. A method as claimed in claim 12, wherein the inputs can be different types of inputs selected from the group consisting of spoken inputs and keypad inputs.
14. A method as claimed in claim 12, further comprising the step of format the query for use by different types of the multiple devices requiring different formats.
15. A method as claimed in claim 12, further comprising the step of indicating the unique identifier as invalid in the memory device to prevent incorrect inputs from being accepted as valid when query is repeated.
16. A method as claimed in claim 12, wherein providing step comprises operating a counter provided to each of the inputs as an invocation counter for the query turn indicator to track when the inputs are made.
17. A method as claimed in claim 12, wherein the query turn indicator identifies how many times the session management gateway has sent queries to the multiple devices.
18. A method as claimed in claim 12, further comprising the step of storing data relating to the transaction session.
19. A method as claimed in claim 18, wherein the storing step for storing data relating to the transaction session comprises the step of maintaining data relating to said transaction session with the application separate from interaction sessions with the multiple devices and interaction sessions with the application.
20. A method as claimed in claim 19, wherein data relating to the interaction session with the application is stored even if none of the multiple devices are connected to the transaction session.
Patent Citations (34)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5291583(A) | 1994-03-01 | Bapat | Applicant |
| US5594859(A) | 1997-01-01 | Palmer et al. | Examiner |
| US5715314(A) | 1998-02-01 | Payne et al. | Applicant |
| US5745681(A) | 1998-04-01 | Levine et al. | Applicant |
| US5745754(A) | 1998-04-01 | Lagarde et al. | Applicant |
| US5761280(A) | 1998-06-01 | Noonen et al. | Applicant |
| US5799278(A) | 1998-08-01 | Cobbett et al. | Applicant |
| US5802526(A) | 1998-09-01 | Fawcett et al. | Applicant |
| US5806030(A) | 1998-09-01 | Junqua | Applicant |
| US5806033(A) | 1998-09-01 | Lyberg | Applicant |
| US5809462(A) | 1998-09-01 | Nussbaum | Applicant |
| US5867816(A) | 1999-02-01 | Nussbaum | Applicant |
| US5884262(A) | 1999-03-01 | Wise et al. | Applicant |
| US5913196(A) | 1999-06-01 | Talmor et al. | Applicant |
| US5915001(A) | 1999-06-01 | Uppaluru | Applicant |
| US5953392(A) | 1999-09-01 | Rhie et al. | Applicant |
| US5991712(A) | 1999-11-01 | Martin | Applicant |
| US6101473(A) | 2000-08-01 | Scott et al. | Applicant |
| US6134235(A) | 2000-10-01 | Goldman et al. | Applicant |
| US6167376(A) | 2000-12-01 | Ditzik | Applicant |
| US6201859(B1) | 2001-03-01 | Memhard et al. | Examiner |
| US6215784(B1) | 2001-04-01 | Petras et al. | Applicant |
| US6240448(B1) | 2001-05-01 | Imielinski et al. | Applicant |
| US6269336(B1) | 2001-07-01 | Ladd et al. | Applicant |
| US6335928(B1) | 2002-01-01 | Herrmann et al. | Applicant |
| US6346952(B1) | 2002-02-01 | Shtivelman | Examiner |
| US6377927(B1) | 2002-04-01 | Loghmani et al. | Applicant |
| US6560456(B1) | 2003-05-01 | Lohtia et al. | Applicant |
| US6604129(B2) | 2003-08-01 | Slutsman et al. | Examiner |
| US6748420(B1) | 2004-06-01 | Quatrano et al. | Examiner |
| US6751453(B2) | 2004-06-01 | Schemers et al. | Applicant |
| US6801763(B2) | 2004-10-01 | Elsey et al. | Applicant |
| US2001/0033564(A1) | 2001-10-01 | Hickman | Applicant |
| GB2317070 | 1998-03-01 | Applicant |