US 7,486,780 B2Grant
System and method for the creation and automatic deployment of personalized, dynamic and interactive voice services, with telephone-based service utilization and control
Issue Date:2009-02-03
•11 Claims
•19 Drawing Sheets
Abstract
A method and system for telephone-based service utilization and control in conjunction with interactive, real-time, voice transmission of information to a user is disclosed. A voice service system provides creation and automatic deployment of personalized, dynamic and interactive voice services, including information derived from on-line analytical processing (OLAP) systems and other data repositories. In conjunction with such services, a user may use a telephone to control such services. For example, the user may subscribe and unsubscribe to a service using the telephone, be notified of new services via the telephone, and retrieve sound files via the telephone.
Metadata
Assignee
- MicroStrategy, Incorporated
Inventors
- Michael Zirngibl
- Anurag Patnaik
- Bodo Maass
- Hannes Eberle
Application Information
Application Number:US 11/005,507
Filing Date:2004-12-07
Priority Date:1999-09-13
Art Unit:2614
Classifications
IPC:
H04M1/64
Patent Drawings (19 sheets)
Description
Related Applications
[0001] This application is a continuation of U.S. application Ser. No. 09/496,356, filed 2 Feb. 2000, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, WITH TELEPHONE-BASED SERVICE UTILIZATION AND CONTROL,” now U.S. Pat. No. 6,829,334, issued 7 Dec. 2004, which claims priority from U.S. Provisional Application Ser. No. 60/153,222, filed 13 Sep. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES.” This application is also related by subject matter to the following U.S. Patent Applications: U.S. application Ser. No. 09/454,602, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES,” now U.S. Pat. No. 6,850,603, issued 1 Feb. 2005; U.S. application Ser. No. 10/073,331, filed 13 Feb. 2002, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, WITH CLOSED LOOP TRANSACTION PROCESSING,” which is a continuation of U.S. application Ser. No. 09/455,525, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, WITH CLOSED LOOP TRANSACTION PROCESSiNG,” now abandoned; U.S. application Ser. No. 10/951,475, filed 27 Sep. 2004, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES WITH REAL-TIME DATABASE QUERIES,” which is a continuation of U.S. application Ser. No. 09/455,533, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES WITH REAL-TIME DATABASE QUERIES,” now U.S. Pat. No. 6,798,867, issued 28 Sep. 2004; U.S. application Ser. No. 10/430,265, filed 7 May 2003, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES WITH REAL-TIME DRILLING VIA TELEPHONE,” which is a continuation of U.S. application Ser. No. 09/455,529, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES WITH REAL-TIME DRILLING VIA TELEPHONE,” now U.S. Pat. No. 6,587,547, issued 1 Jul. 2003; U.S. application Ser. No. 09/661,188, filed 13 Sep. 2000, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES INCLUDING MODULE FOR GENERATING AND FORMATTING VOICE SERVICES;” U.S. application Ser. No. 10/072,898, filed 12 Feb. 2002, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES WITH CUSTOMIZED MESSAGE DEPENDING ON RECIPIENT,” which is a continuation of U.S. application Ser. No. 09/455,527, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES WITH CUSTOMIZED MESSAGE DEPENDING ON RECIPIENT,” now abandoned; U.S. application Ser. No. 09/661,377, filed 13 Sep. 2000, entitled “SYSTEM AND METHOD FOR CREATING VOICE SERVICES FOR INTERACTIVE VOICE BROADCASTING;” U.S. application Ser. No. 09/661,375, filed 13 Sep. 2000, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, WITH SYSTEM AND METHOD THAT ENABLE ON-THE-FLY CONTENT AND SPEECH GENERATION;” U.S. application Ser. No. 09/496,357, filed 2 Feb. 2000, entitled “SYSTEM AND METHOD FOR PERSONALIZING INTERACTIVE VOICE BROADCASTS;” U.S. application Ser. No. 09/661,471, filed 13 Sep. 2000, entitled “SYSTEM AND METHOD FOR THIE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES INCLUDING A MARKUP LANGUAGE FOR CREATING VOICE SERVICES,” now abandoned; U.S. application Ser. No. 09/454,604, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR VOICE SERVICE BUREAU,” now U.S. Pat. No. 6,263,051, issued 17 Jul. 2001; U.S. application Ser. No. 11/020,675, filed 27 Dec. 2004, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR INFORMATION RELATED TO EXISTING TRAVEL SCHEDULE,” which is a continuation of U.S. application Ser. No. 09/455,523, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR INFORMATION RELATED TO EXISTING TRAVEL SCHEDULE,” now U.S. Pat. No. 6,836,537, issued 28 Dec. 2004; U.S. application Ser. No. 09/454,601, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR INVENTORY-RELATED INFORMATION;” U.S. application Ser. No. 09/454,597, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR CORPORATE-ANALYSIS RELATED INFORMATION;” U.S. application Ser. No. 09/455,524, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR INVESTMENT-RELATED INFORMATION;” U.S. application Ser. No. 09/454,603, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR ENTERTAINMENT-RELATED INFORMATION;” U.S. application Ser. No. 09/455,532, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR PROPERTY-RELATED INFORMATION,” now U.S. Pat. No. 6,768,788, issued 27 Jul. 2004; U.S. application Ser. No. 09/454,599, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR RETAIL-RELATED INFORMATION;” U.S. application Ser. No. 09/455,530, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED, DYNAMIC, INTERACTIVE VOICE SERVICES FOR BOOK-RELATED INFORMATION,” now U.S. Pat. No. 6,788,768, issued 7 Sep. 2004; U.S. application Ser. No. 10/440,361, filed 19 May 2003, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED DYNAMIC, INTERACTIVE VOICE SERVICES FOR TRAVEL AVAILABILITY INFORMATION,” which is a continuation of U.S. application Ser. No. 09/455,526, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR REAL-TIME, PERSONALIZED DYNAMIC, INTERACTIVE VOICE SERVICES FOR TRAVEL AVAILABILITY INFORMATION,” now U.S. Pat. No. 6,658,093, issued 2 Dec. 2003; U.S. Application Ser. No. 09/661,189, filed 13 Sep. 2000, entitled “SYSTEM AND METHOD FOR VOICE-ENABLED INPUT FOR USE IN THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC, AND INTERACTIVE VOICE SERVICES;” U.S. application Ser. No. 09/455,534, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, WITH INTEGRATED IN BOUND AND OUTBOUND VOICE SERVICES;” U.S. application Ser. No. 09/496,425, filed 2 Feb. 2000, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, WITH THE DIRECT DELIVERY OF VOICE SERVICES TO NETWORKED VOICE MESSAGING SYSTEMS,” now U.S. Pat. No. 6,765,997, issued 20 Jul. 2004; U.S. application Ser. No. 09/454,598, filed 7 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, INCLUDING DEPLOYMENT THROUGH DIGITAL SOUND FILES,” now U.S. Pat. No. 6,606,596, issued 12 Aug. 2003; U.S. application Ser. No. 09/454,600, filed 07 Dec. 1999, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, INCLUDING DEPLOYMENT THROUGH PERSONALIZED BROADCASTS;” and U.S. application Ser. No. 09/661,191, filed 13 Sep. 2000, entitled “SYSTEM AND METHOD FOR THE CREATION AND AUTOMATIC DEPLOYMENT OF PERSONALIZED, DYNAMIC AND INTERACTIVE VOICE SERVICES, WITH REAL-TIME INTERACTIVE VOICE DATABASE QUERIES.”
Field of the Invention
[0002] This invention relates to a system and method for creation and automatic deployment of personalized, dynamic and interactive voice services, including information derived from on-line analytical processing (OLAP) systems, where the system and method includes the ability to control service selections and utilization via telephone.
Background of the Invention
[0003] Although various user interfaces have been developed to enable users to access the content of data warehouses (for example, OLAP systems), through server systems, many such systems experience significant drawbacks. All of these systems require that the user connect via a computer system to the server system to initiate reports and view the contents of the reports.
[0004] Moreover, in order for users to have access to database and other computer or service related system, the user has to be authorized. In order for a user to be authorized they typically must sign up. These systems also require that the user connect via a computer system to a sign-up.
[0005] These and other drawbacks exist with current OLAP interface systems.
Summary of the Invention
[0006] An object of the invention is to overcome these and other drawbacks in existing systems.
[0007] It is another object of the invention to provide a system and method for the creation and automatic deployment of personalized, dynamic and interactive voice services, including information derived from on-line analytical processing (OLAP) systems and other data repositories, where the system and method includes the ability to control service selections and utilization via telephone.
[0008] One embodiment of the invention relates to a system and method for creation and automatic deployment of personalized, dynamic and interactive voice services, including information derived from on-line analytical processing (OLAP) systems and other data repositories. The system and method enables the ability to capture user selections to facilitate closed-loop transaction processing and processing of other requests such as requests to subscribe to new services and requests for additional information. One aspect of the invention relates to an interactive voice broadcasting system and method that enables analytical reporting and advanced transactional services via the telephone or other voice-enabled terminal device.
[0009] One advantage of the invention is that a user may subscribe and unsubscribe to services without utilizing a computer or similar interface. Another advantage of the invention is that a voice service may leverage the power of OLAP or other data repository systems and provide critical information to the user, in a timely fashion, by phone. Another advantage of this method and system is that it provides a user with the opportunity to immediately act upon information received during an interactive voice broadcast (IVB).
[0010] A voice service is created and can have many users subscribed to the voice service. Each user can specify personal preferences for the content and presentation of the contents for a voice service. The specification of the elements of a voice service may be done using a set of interfaces (such as GUIs) that take the form of a voice service wizard.
[0011] A voice service includes one or more Dialog elements. Dialog elements may include one or more of Speech elements, Input elements and Error elements. An Input element may include a Prompt element and/or an Option element. An Input element enables the system to request input from the user, capture the input and direct the call flow based on the user's input. An Option element associates a key (e.g., on a telephone touch pad dial) with a destination Dialog that is executed when that number is pressed by a user during an interactive voice broadcast. A Prompt requests a user to enter numeric or other information. An Input element may enable a user to request, during an interactive voice broadcast, a transaction, a service or other requests. The term transactions, services and requests are to be interpreted broadly.
[0012] According to one embodiment, the user's responses to Input elements are stored during an interactive voice broadcast and, during or after the voice broadcast, the stored information is processed by the system or is passed to another system or application for processing. The transaction (or other request) processing can be accomplished either in real-time, during the voice broadcast, or after the interactive voice broadcast is completed. The results or confirmation of a transaction or other request can be provided to the user during the call or subsequently.
[0013] Once a voice service is created, the system monitors predetermined conditions to determine when the voice service should be executed. Each voice service is executed when one or more predetermined conditions are met as specified during creation of the voice service. For example, a voice service may be executed according to a predetermined schedule (time-based) or based on a triggering event (e.g. one or more conditions are met based on the output of an OLAP or other report).
[0014] When the predetermined condition is satisfied, the voice service is executed. Executing a voice service, includes the steps of generating the content specified by the voice service and the user preferences. Some users may have identical personalization options and, thus, a single call structure may be generated for a group of users with identical personalization options. The content of the voice service includes the information that is to be delivered to users of that voice service, and the Input to be requested from the user, among other things. The content may include, for example, static text messages, dynamic content (e.g. text based on information output from an OLAP report, other database or other sources). The static and dynamic content may be blended together.
[0015] This and other content along with a users personalization preferences are formatted in an Active Voice Page (AVP). An AVP contains the call structure and data, voice style parameters for the user and personal identification information designated for the user. The AVP contains data at various hierarchical levels that are defined by the Dialog elements defined for each voice service. The active voice pages are used to help govern the interaction between the call server and the user during an IVB. According to one embodiment, the content is formatted, into an AVP using XSL stylesheets so the AVP is in an XML-based language. According to one embodiment, the XML-based language used is a novel language referred to as TML (discussed below). The AVP is sent to a call server along with style properties for each user. The style properties of a user help determine the behavior of the call server during an interactive voice broadcast. A unique AVP is generated for each user scheduled to receive a voice service.
[0016] When a user is called by the call server, information is passed through a text-to-speech (T-T-S) engine and delivered to the user through a voice-enabled terminal device. Preferably, the structure of each call is dynamic, driven by current data values and is personalized based on a user profile established during subscription to a voice service. During a typical interactive voice broadcast, a synthesized, natural sounding voice greets the recipient by name, identifies itself, provides information relevant to the user and enables a user to provide input back to the system.
[0017] An IVB is a voice-enabled interaction with a user having a dynamic structure controlled by the AVP for the particular user. The IVB may be delivered using real-time, on-the-fly speech generation. During an IVB, information is exchanged between the call server and a user according to the AVP. The system executes dialogs by reading messages to the user and, eliciting input from the user. For example, the user may press buttons on a telephone touch pad dial to select an option or to provide numeric or alphanumeric input. Each response provided by a user may transfer control of the IVB to a different part of the AVP.
[0018] During or after the IVB, the user's responses may be processed by the system or other applications. The AVP may contain pointers to other applications and embedded statements such that when a user exercises an option, the system performs a requested operation and returns the results to the user during the IVB. For example, by exercising an option, a user may request that a real-time database query be performed. When the user selects such an option, control is shifted to a portion of the AVP that contains an embedded SQL statement that is made against a database.
[0019] When a user has worked through selected dialogs of the AVP, the IVB is terminated. That is, a user likely will not work through all of the available dialogs during an IVB. Rather, the user's inputs and option selections determine which the available dialogs are encountered during any given IVB.
[0020] Other objects and advantages of the present invention will be apparent to one of ordinary skill in the art upon reviewing the detailed description of the present invention.
Brief Description of the Drawings
[0021] FIG. 1 a is a flow chart of a method in accordance with an embodiment of the present invention.
[0022] FIG. 1 b is a flow chart indicating a method of generating a voice service according to one embodiment of the present invention.
[0023] FIG. 1 c is a flow chart indicating a method for interactive voice broadcasting according to an embodiment of the present invention.
[0024] FIG. 2 is a flow chart that schematically indicates call flow according to one embodiment of the present invention.
[0025] FIG. 3 a is a schematic block diagram of a system in accordance with an embodiment of the present invention.
[0026] FIG. 3 b is a schematic block diagram of an intelligence server according to an embodiment of the present invention.
[0027] FIG. 3 c is a schematic block diagram of call server according to an embodiment of the present invention.
[0028] FIG. 4 is a schematic block diagram of a commercial transaction processing system according to an embodiment of the present invention.
[0029] FIG. 5 is a flow chart of a method of using a voice service bureau according to an embodiment of the present invention.
[0030] FIG. 6 a is a schematic block diagram of a voice service system incorporating a voice service bureau according to one embodiment of the present invention.
[0031] FIG. 6 b is block diagram of a primary voice bureau according to one embodiment of the present invention.
[0032] FIG. 6 c is a block diagram of a backup voice bureau according to another embodiment of the present invention.
[0033] FIG. 7 is a flow chart illustrating a method for integrating inbound and outbound voice services.
[0034] FIG. 8 is a block diagram of a call server configured to provide integrated inbound and outbound voice services.
[0035] FIG. 9 is flow chart illustrating a method for accessing an AVP to control services according to one embodiment of the present invention.
[0036] FIG. 10 is flow chart illustrating a method for navigating through an AVP to adjust voice services according to one embodiment of the present invention.
[0037] FIG. 11 is flow chart illustrating a method for accessing an AVP to listen to sound files according to one embodiment of the present invention.
[0038] FIG. 12 is flow chart illustrating a method for navigating through an AVP to listen to sound files according to one embodiment of the present invention.
Detailed Description of the Preferred Embodiments
[0039] According to one embodiment of the present invention, a system and method that enable a user to control voice service selection through telephone using an AVP are provided. An interactive voice broadcast may present the user with a number of options or request information from the user. An option comprises a number of choices from which the user may chose using the telephone keypad. A request for information comprises a prompt for the user to enter a response, for example, a number or a name, using the telephone keypad.
[0040] A method for controlling voice service selection according to one embodiment is shown in FIG. 9 . The method of FIG. 9 will be explained in conjunction with a particular method of enabling control of a user's subscription to voice services. It is understood that the method of FIG. 9 could be used to utilize other particular voice services.
[0041] In step 910, a call is initiated to a user. According to one embodiment, a user is called by a voice service system and provided with a voice service. In one particular embodiment, a user is called by the system and informed of new voice service offerings. According to another embodiment, a user accesses the system through an inbound calling facility as discussed below in conjunction with FIGS. 12 and 13 .
[0042] According to one embodiment, the appropriate AVP is located in step 920. The appropriate AVP may comprise an AVP configured to enable a user to subscribe and unsubscribe to services is located. According to one embodiment, the AVP enables a user to turn off existing subscriptions, subscribe to new voice services, change subscription criteria, e.g., telephone address, and retrieve additional subscription information, e.g., expiration dates and billing information. According to a particular embodiment, each of these capabilities is associated with an option in the active voice page.
[0043] There are various ways that the appropriate AVP may be located. According to one embodiment, an interactive voice broadcast to a user is initiated utilizing the appropriate AVP. In particular, a user is called by a voice service system and presented with information regarding new voice services and presented with an option to either subscribe or unsubscribe to voice services. According to another embodiment, a user places an inbound call to a voice service system to adjust the user's subscription to voice services. According to this embodiment, after the user is identified and authorized to access the system as explained in conjunction with FIGS. 7 and 8 below, the user searches for the appropriate AVP that is specifically configured to enable a user to subscribe and unsubscribe to voice services. According to another embodiment, an inbound caller is automatically placed into an active voice page that presents the user with a number of options including an option to subscribe or unsubscribe to services. According to still another embodiment, the user is allowed to search for the appropriate AVP by content using the telephone keys to enter a search term. For example, the user might use the search term “subscribe” to locate the appropriate AVP. According to another embodiment, a user may locate the appropriate AVP at any time during an interactive voice broadcast by entering a particular key combination. According to another embodiment, a pre-recorded voice menu is used in order to gain access to the appropriate AVP.
[0044] The method is also useful for subscribing new users to voice services. In this situation, according to one embodiment, a user (potential subscriber) calls into the system and is presented with an option to sign up for voice services. If the user exercises this option, they are placed into an AVP that prompts them for a credit card number. Upon entering the credit card number, the user may proceed with navigating through an AVP that will enable them to sign up for voice services. A user profile may be built by accessing information from the credit card number and by using user entered information.
[0045] A user navigates the AVP in step 930. That is, as described in more detail below, a user is able to navigate through an AVP to accomplish the desired goal. According to one particular embodiment, the user navigates through an active voice page by exercising options that enable cancellation of existing subscriptions, subscription to new voice services, changing subscription criteria, e.g., telephone address, and retrieving additional subscription information, e.g., expiration dates and billing information.
[0046] FIG. 10 is flow chart illustrating one embodiment of a user navigating through an AVP. In an initial step (1010) a user is presented with information. According to one embodiment, a user is presented with information concerning the users subscription or concerning the availability of new services. According to another embodiment, the user is presented with a number of options that enable a user to choose a particular operation to be performed, e.g., canceling existing voice service subscriptions.
[0047] During the interactive voice broadcast, a user requests the desired operation or function (step 1020). According to one embodiment, the user request comprises a request to subscribe or unsubscribe to services. According to one particular embodiment, the user requests one of a plurality of functions such as cancellation of existing subscriptions, subscription to new voice services, changing subscription criteria, e.g., telephone address, and retrieving additional subscription information, e.g., expiration dates and billing information. Other function are possible.
[0048] Once the user requests a particular function, control is transferred to an active voice page that enables the user to perform the requested function. The requested function may also be performed by choosing from a menu of options. For example, if a user chooses to subscribe to a new voice service, the active voice page may present the user with a list of voice services that they may subscribe to. As another example, if a user chooses to cancel their subscription to a voice service, the active voice page may present the user with a list of all the voice services they are subscribed to.
[0049] The request for a particular operation may comprise a user response to a set of options and/or input of information through a telephone keypad or other input mechanism. Alternatively, the request may comprise a spoken, natural language request for information by the user. Other types of requests are possible.
[0050] According to one embodiment, the user responses and input are written to a response collection, which along with other information stored in the voice page, can be used to accomplish the requested function, e.g., subscription to a new voice service. According to one embodiment, tokens are used to manage user inputs during the interactive voice broadcast. A token is a temporary variable that can hold different values during an interactive voice broadcast. When a user enters input, it is stored as a token. If the user input relates to a query, the token value will then be used to complete a query as described above. According to one embodiment, the system maintains a running list of tokens, or a response collection, during a broadcast.
[0051] The user's request is processed in step 1030. According to one embodiment, the user is subscribed or unsubscribed to services based on the request. There are a number of ways in which a user's response may be processed.
[0052] According to one embodiment, the users request is processed using an embedded statement in the AVP. In the case where the user exercises an option, the user's input may be stored as a token and used to complete an embedded request in the active voice page. For example, to subscribe to a new service, the embedded statement comprises a request that is sent to the service administrator to sign up for a new service. According to this embodiment, the embedded statement may cause an email to be sent to the system administrator requesting subscription to the new service. According to another embodiment, the embedded statement may trigger an API call to subscriber API 203 that will adjust the user's service subscription as requested.
[0053] In the system of FIGS. 1-7 , the TML parsing engine in the call server includes the functionality necessary to process a user request using an embedded statement as described above. For example, in connection with the embodiment described above, the TML parsing engine shown in FIG. 6 reads the active voice pages. When the TML parsing engine reads an option statement that includes and embedded statement, it stores the statement, defines a variable and a variable location. When the user exercises that option, the user's input is received by the TML parsing engine and placed at the defined memory location to complete the embedded statement. According to another embodiment, an option may be associated with a URL. The URL location may comprises, e.g., an embedded request, additional markup language, text or sound files that are used to complete the user's request. A user's responses may be used to define parameters of the URL.
[0054] According to another embodiment, where the user's request is made via a natural language, voice request, the request may be processed in a number of ways. According to one embodiment, speech recognition technology is used to translate the user's response into text. The text is then used to complete an embedded statement as described above. According to another embodiment, speech recognition software is used to translate the request to text. The text is then converted to a statement or query that accomplishes the user's request.
[0055] The user's request is confirmed or the requested information is conveyed in step 1040. According to one embodiment, the user receives a confirmation that the user has been subscribed or unsubscribed to a particular voice service. In the context of the interactive voice service system shown and described in FIGS. 1-7 , a predefined confirmation statement is included in the AVP. This statement is accessed by TML parsing engine 1812 and conveyed to the user after being converted to speech in text-to-speech engine 1814. According to another embodiment, the user is presented with the information requested. For example, if the user has requested subscription information, that information is presented to the user.
[0056] According to one embodiment, this feedback, i.e., the confirmation or requested information, is provided in real-time. According to one embodiment used in conjunction with web-based transactions, the user is provided with this real-time feedback by using get and post methods with an active server page. Other scripting languages may be used. According to this embodiment, the data to be transferred (e.g., the subscription request) is bundled and posted to a script that translates the request. According to another embodiment, a transaction engine is used to communicate with appropriate transaction servers, e.g., a stock trading server if the user is signing up for a service related to their stock portfolio.
[0057] According to another embodiment of the present invention, a system and method that enable a user to access sound files over the telephone using an AVP are provided. An interactive voice broadcast may present the user with a number of options or request information from the user. An option comprises a number of choices from which the user may chose using the telephone keypad. A request for information comprises a prompt for the user to enter a response, for example, a number or a name, using the telephone keypad.
[0058] A method for accessing sound files according to one embodiment is shown in FIG. 11 . The method of FIG. 11 begins at step 1110, with initiation of a call to a user. According to one embodiment, a user is called by a voice service system and provided with a voice service. In one particular embodiment, while the voice service is being delivered, the user is informed of the availability of certain sound files to review. The sound files may comprise, for example, news broadcasts, music clips, or sports highlights. According to another embodiment, a user accesses the system through an inbound calling facility as discussed below in conjunction with FIGS. 7 and 8 .
[0059] According to one embodiment, a particular AVP is located in step 1120. According to one embodiment, an AVP configured to enable a user to access one or more sound files is located. According to one embodiment, a user accesses the desired active voice page by exercising an option during the interactive voice broadcast. According to another embodiment, a user places an inbound call to a voice service system in order to access particular sound files. According to this embodiment, after the user is identified and authorized to access the system as explained in conjunction with FIGS. 7 and 8 below, the user searches for an AVP that is specifically configured to enable a user to access sound files.
[0060] A user navigates the AVP in step 1130. That is, as described in more detail below, a user is able to navigate through an AVP to access the desired sound files. The AVP may comprise a hierarchically arranged series of options that allow the user to chose progressively narrower categories of sound files until the user arrives at the desired sound file.
[0061] FIG. 12 is flow chart illustrating one embodiment of a user navigating through an AVP. In an initial step (1210) a user is presented with information. According to one embodiment, a user is presented with information concerning the availability of sound files to review.
[0062] During the interactive voice broadcast, a user requests one or more sound files (step 1220). According to one embodiment, the user request comprises a request to have one or more sound files played over the telephone. The request may comprise a user response to a set of options and/or input of information through a telephone keypad or other input mechanism. Alternatively, the request may comprise a spoken, natural language request for information by the user. Other types of requests are possible.
[0063] According to one embodiment, the user responses and input are written to a response collection, which along with other information stored in the voice page, can be used to retrieve the requested information. According to one embodiment, tokens are used to manage user inputs during the interactive voice broadcast. A token is a temporary variable that can hold different values during an interactive voice broadcast. When a user enters input, it is stored as a token. If the user input relates to a query, the token value will then be used to complete a query as described above. According to one embodiment, the system maintains a running list of tokens, or a response collection, during a broadcast.
[0064] The requested sound file is retrieved in step 1230. There are a number of ways that the sound file may be retrieved. According to one embodiment, the sound file is retrieved using an embedded statement in the AVP. In the case where the user exercises an option, the user's input may be stored as a token and used to complete an embedded request in the active voice page. For example, to access a particular sound file, the embedded statement comprises a search query formulated to access the sound file from a sound file database.
[0065] In the system of FIGS. 1-3 , the TML parsing engine in the call server includes the functionality necessary to retrieve a requested sound file using an embedded statement or query as described above. For example, in connection with the embodiment described above, the TML parsing engine shown in FIG. 3 reads the active voice pages. When the TML parsing engine reads an option statement that includes and embedded statement, it stores the statement, defines a variable and a variable location. When the user exercises that option, the user's input is received by the TML parsing engine and placed at the defined memory location to complete the embedded statement. According to another embodiment, an option may be associated with a URL. The URL location may comprises, e.g., an embedded request, additional markup language, text or sound files that are used to complete the user's request. A user's input may be used to define parameters of the URL.
[0066] According to another embodiment, where the user's request is made via a natural language, voice request, the request may be processed in a number of ways. According to one embodiment, speech recognition technology is used to translate the user's response into text. The text is then used to complete an embedded statement as described above. According to another embodiment, speech recognition software is used to translate the request to text. The text is then converted to a query that accesses the requested sound file.
[0067] The requested sound file is conveyed to the user in step 1240. According to one embodiment, the requested sound file is played for the user. According to one particular embodiment, a sound file may be played for the user using RealPlayer. According to other embodiments, other players are used.
[0068] According to one embodiment, the method and system described in conjunction with FIGS. 9-12 may be advantageously employed in conjunction with the system shown in FIGS. 1-7 . For example, subscribers may be called by the system, and have content delivered audibly over the telephone or other voice-enabled terminal device. During the IVB, information may be exchanged between the system and a subscriber. The system conveys content to the subscriber and, the subscriber may respond by pressing one or more buttons on a telephone touch pad dial (or other input mechanism) to hear more information, to exercise options, or to provide other responses, e.g., to subscribe or un-subscribe to voice services. This interaction shapes the structure of a basic exchange between the system and the subscriber. During or after the call is terminated, the subscriber's responses may be stored and processed (e.g., by other applications).
[0069] According to one embodiment of the present invention, a method for automatic, interactive, real-time, voice transmission of OLAP output to one or more subscribers is provided. FIG. 1 a depicts a flow chart of a method for automatic, interactive, real-time, voice transmission of OLAP output according to one embodiment. The method begins in step 110 with the creation of a voice service (e.g., by a system administrator or user). A voice service is created using, for example, a voice service wizard which may comprise a series of interfaces. One embodiment of a method for creating a voice service is explained in more detail below in conjunction with FIG. 1 b. One embodiment of a voice service wizard is explained below in conjunction with FIG. 3 b.
[0070] After a voice service is created, users may subscribe or be subscribed to the voice service (step 120), for example, by using a subscription interface. According to one embodiment, users may subscribe to an existing voice service over the telephone or by web-based subscription. A user may also be subscribed programmatically. In other embodiments, a user may subscribe to a voice service via electronic mail. Not every voice service created in step 110 is available for subscription. More specifically, according to another embodiment, only a user with appropriate access, such as the creator of the service, is allowed to subscribe himself or others to a service. Such a security feature may be set when the voice service is created.
[0071] In step 130, a scheduling condition or other predetermined condition for the voice services is monitored to determine when they are to be executed. That is, when a voice service is created or subscribed to, the creator or user specifies when the voice service is to be executed. A user may schedule a voice service to execute according to the date, the time of day, the day of the week, etc. and thus, the scheduling condition will be a date, a time, or a day of the week, either one time or on a recurring basis. In the case of an alert service, discussed in more detail below, the scheduling condition will depend on satisfaction of one or more conditions. According to one embodiment, the condition(s) to be satisfied is an additional scheduling condition. According to another embodiment, to another embodiment, a service may be executed “on command” either through an administrator or programmatically through an API. Scheduling of voice services is discussed in more detail below.
[0072] The method continues monitoring the scheduling condition for voice services until a scheduling condition is met. When a scheduling condition is met, that voice service is executed as illustrated in, for example, step 140. The execution of a voice service involves, inter alia, generating the content for the voice service, and structuring the voice service to be telecast through a call server. The execution of a voice service is explained in detail in conjunction with FIG. 1 c.
[0073] An example of a telecast is as follows.
[0074] Personalized Greeting
[0075] Hello Joe, this is your stock update.
[0076] Pin Verification
[0077] Please enter your six digit PIN number
[0078] (Joe enters his PIN, using the keypad dial on his telephone.)
[0079] Menu Options
[0080] Your portfolio was up by $1000 today.
[0081] Please select:
[0082] 1. To get a portfolio stock update
[0083] 2. To conduct a transaction
[0084] (Joe presses 2)
[0085] Sub Menu
[0086] Thank you, Joe! Please select a ticker.
[0087] 1. PQT
[0088] 2. TQP
[0089] 3. Listen to options again
[0090] 4. Return to main menu
[0091] (Joe presses 1.)
[0092] Sub Menu
[0093] Would you like to buy or sell stock? Please press:
[0094] 1. To sell stock
[0095] 2. To buy stock
[0096] (Joe presses 1.)
[0097] Sub Menu
[0098] How many shares of PQT would you like to sell today? Please press:
[0099] 1. To sell 50 shares
[0100] 2. To sell 100 shares
[0101] 3. To sell 200 shares
[0102] 4. To sell another quantity
[0103] (Joe presses 2.)
[0104] Sub Menu
[0105] You selected 2. You want to sell 100 shares of PQT. Please press:
[0106] 1. If this is correct
[0107] 2. If this is incorrect
[0108] 3. If you want to change the number of shares you want to buy.
[0109] (Joe presses 1.)
[0110] End Voice Service/Terminate Telecast
[0111] Thank you for using our voice interactive broadcasting service, Joe. We will call you back when your transaction is completed. Good-bye.
As can be seen from the above sample during an IVB, the user is presented with information, e.g., the status of his portfolio, and is presented options related to that report, e.g., the option to buy or sell stock.
[0112] According to one embodiment, a voice service is constructed using service wizard. A voice service is constructed using several basic building blocks, or elements, to organize the content and structure of a call. According to one embodiment, the building blocks of a voice service comprise elements of a markup language. According to one particular embodiment, elements of a novel markup language based on XML (TML) are used to construct voice services. Before explaining how a telecast is constructed, it will be helpful to define these elements.
[0113] The DIALOG element is used to define a unit of interaction between the user and the system and it typically contains one or more of the other elements. A DIALOG can not be contained in another element.
[0114] The SPEECH element is used to define text to be read to a user.
[0115] The INPUT element is used to define a section of a DIALOG that contains interactive elements, i.e., those elements that relate to a response expected from a user and its validation. An INPUT element may contain OPTION, PROMPT and ERROR elements.
[0116] An OPTION element identifies a predefined user selection that is associated with a particular input. According to one embodiment, OPTION elements are used to associate one or more choices available to a user with telephone keys.
[0117] A PROMPT element defines a particular input that is expected. According to one embodiment, a PROMPT element defines that a sequence or number of key presses from a telephone keypad is expected as input. Unlike an OPTION Element, a PROMPT Element is not associated with predefined user selections.
[0118] The PROMPT and OPTION elements may also be used to request user input using natural language. According to one embodiment, speech recognition technology is used to enable a user to respond to a PROMPT element or to select an OPTION element verbally by saying a number, e.g., “one.”. The verbal response is recognized and used just as a keypress would be used. According to another embodiment, the user may provide a free form verbal input. For example, a PROMPT element may request that a user enter, e.g., the name of a business. In response the user speaks the name of a business. That spoken name is then resolved against predetermined standards to arrive at the input. Word spotting and slot filling may also be used in conjunction with such a PROMPT to determine the user input. For example, a PROMPT may request that the user speak a date and time, e.g., to choose an airline flight or to make a restaurant reservation. The user's spoken response may be resolved against known date and time formats to determine the input. According to another embodiment, a PROMPT is used to request input using natural language. For instance, in conjunction with a voice service to be used to make travel plans, instead of having separate PROMPT elements request input for flight arrival, departure dates and locations, a single natural language PROMPT may ask, “Please state your travel plan.” In response, the user states 'I'd like to go from Washington D.C. to New York city on the 3rd of January and return on the 3rd of February. This request would be processed using speech recognition and pattern matching technology to derive the user's input.
[0119] The ERROR element is used to define the behavior of the system if a user makes an invalid response such as touching a number that has not been associated with an OPTION element, or entering input that does not meet the criteria of a PROMPT element. A SYS-ERROR element defines a handler for certain events, such as expiration of the waiting time for a user response.
[0120] The FOR-EACH element is used to direct the system to loop through a list of variables e.g., variables contained in a database report, or variables from a user input, to dynamically generate speech from data.
[0121] In addition to the elements described above, there are two features that maximize an administrator's ability to design voice services. Call Flow Reports enable an administrator to generate the structure of a call based on the content of an report e.g., from an OLAP system or other data repository. For example, the options presented to a user in a PROMPT element may be made to correspond to the row of a data report. According to one embodiment, report data is converted into options by application of an XSL (extensible style sheet language) style sheet. The result of this application is inserted into the static call structure when the voice service is executed.
[0122] The use of an XSL style sheet is a feature that maximizes an administrator's voice service building ability. As discussed above, they are used to create dynamic call structure that depends on data report output. They may also be used to generate a text string that comprises the message to be read to a user at any point in a call.
[0123] A method for creating a voice service according to one embodiment will now be explained in conjunction with FIG. 2 . The method begins in step 210 by naming the voice service. Then, in step 220 various scheduling parameters of the voice service are defined. In step 250 the service content is defined. And, in step 260, the personalization modes, or style properties are selected for the voice service.
[0124] According to one embodiment, in step 210, a voice service is named and a description of the voice service provided. By providing a name and description, a voice service may be uniquely identified. An interface is provided for prompting input of the name of the service to be created or edited. An input may also be provided for a written description. An open typing field would be one option for providing the description input. According to another embodiment, if an existing call service has been selected to edit, the service name field may not be present or may not allow modification.
[0125] In step 220, conditions for initiating the service are selected. This may include selecting and defining a service type. At least two types of services may be provided based on how the services are triggered. A first type of service is run according to a predetermined schedule and output is generated each time the service is run. A second type of service, an alert service, is one that is run periodically as well, however, output is only generated when certain criteria is satisfied. Other service types may be possible as well. In one embodiment the administrator is prompted to choose between a scheduled service or an alert service. An interface may provide an appropriate prompt and some means for selecting between a scheduled service and an alert service. One option for providing the input might be an interface with a two element toggle list.
[0126] In one embodiment, a set of alert conditions is specified to allow the system to evaluate when the service should be initiated if an alert type service has been selected. In one embodiment, a report or a template/filter combination upon which the alert is based is specified. Reports and template/filter combinations may be predefined by other objects in the system including an agent module or object creation module. According to one embodiment, an agent module, such as DSS agent™ offered by MicroStrategy, may be used to create and define reports with filters and template combinations, and to establish the alert criteria for an alert service. According to another embodiment, an interface is be provided which includes a listing of any alert conditions presently selected for the voice service. According to this embodiment, the interface may comprise a display window. A browse feature may take the user to a special browsing interface configured to select a report or filter-template combination. One embodiment of an interface for selecting reports and filter-template combinations is described below. Once a report or filter and template combination is chosen, the alerts contained in the report or filter and template combination may be listed in the display window of the interface.
[0127] In step 240, the schedule for the service is also selected. According to one embodiment, predefined schedules for voice services may be provided or a customized schedule for the voice service may be created. If a new schedule is to be created, a module may be opened to enable the schedule name and parameters to be set. Schedules may be run on a several-minute, hourly, daily, monthly, semi-annual, annual or other bases, depending upon what frequency is desired. According to one embodiment, an interface is provided that allows the administrator to browse through existing schedules and select an appropriate one. The interface may provide a browsing window for finding existing schedule files and a “new schedule” feature which initiates the schedule generating module. In one embodiment, schedules may not be set for alert type services. However, in some embodiments, a schedule for evaluating whether alert conditions have been met may be established in a similar manner.
[0128] In step 230, the duration of the service is also set. Service duration indicates the starting and stopping dates for the service. Setting a service duration may be appropriate regardless of whether a scheduled service or alert type service has been selected. The start date is the base line for the scheduled calculation, while the end date indicates when the voice service will no longer be sent. The service may start immediately or at some later time. According to one embodiment, the interface is provided to allow the administrator to input start and end dates. The interface may also allow the administrator to indicate that the service should start immediately or run indefinitely. Various calendar features may be provided to facilitate selection of start and stop dates. For example, a calendar that specifies a date with pull-down menus that allow selection of a day, month and year may be provided according to known methods of selecting dates in such programs as electronic calendar programs and scheduling programs used in other software products. One specific aid that may be provided is to provide a calendar with a red circle indicating the present date and a blue ellipse around the current numerical date in each subsequent month to more easily allow the user to identify monthly intervals. Other methods may also be used.
[0129] In step 220, a voice service may also be designated as a mid-tier slicing service. In one embodiment, mid-tier slicing services generate content and a dynamic subscriber list in a single query to an OLAP system. According to one embodiment, in a mid-tier slicing service a single database query is performed for all subscribers to the service. The result set developed by that query is organized in a table that contains a column that indicates one or more users that each row of data is applicable to.
[0130] In step 250, the content of the voice service is defined. Defining the content of the voice service may include selecting the speech to be delivered during the voice service broadcast (content), the structure of dialogs, menus, inputs, and the background procedures which generate both content and structure. In one embodiment, defining voice service content establishes the procedures performed by the vss server to assemble one or more active voice pages in response to initiation of the voice service. According to one embodiment, defining service content involves establishing a hierarchical structure of TML elements which define the structure and content of a voice service. All of the elements in a given service may be contained within a container.
[0131] The personalization type is selected in step 260. Personalization type defines the options that the administrator will have in applying personalization filters to a voice service. According to one embodiment, a personalization filter is a set of style properties that can be used to determine what content generated by the service will be delivered to the individual user and in what format it will be delivered. In one embodiment, personalizing the delivery format may include selection of style properties that determine the sex of the voice, the speed of the voice, the number of call back attempts, etc. Personalization filters may exist for individual users, groups of users, or types of users. According to one embodiment, personalization filters may be created independent of the voice service. According to this embodiment, a voice service specifies what filters are used when generating IVBs. Some personalization type options may include: allowing no personalization filters; allowing personalization filters for some users, but not requiring them; and requiring personalization filters for all interactive voice broadcasts made using the service.
[0132] According to one embodiment, specifying personalization type is accomplished by administrator input through an interface. The interface may offer a toggle list with the three options: required personalization, optional personalization, and no personalization.
[0133] The voice service may be stored in a database structure to enable users to retrieve predefined voice services and to subscribe to these services, for example, through subscription interfaces explained in conjunction FIGS. 3 a-3c or otherwise. An interface informing the administrator that creation of the voice service is complete may also be provided.
[0134] According to one embodiment, the method of FIG. 1 b also comprises an error condition step. An error condition step may be used to enable administrators to specify “error” conditions and the handling of those conditions. For example, an “error” condition may comprise a notification that a server is “down” or that there is no data to be returned. An administrator may specify particular actions to be performed by the system in response to one or more error conditions. For example, an administrator may specify an “addressing” error (e.g., disconnected number) and indicate a particular action to be performed in response to an “addressing” error (e.g., notify system administrator). Other error conditions might include: an alert report encountering an error and returning no data; a subscriber lacking the required personalization filter for the service; errors occurring in the generation of one or more reports; or reports returning no data. Various other conditions and actions may be specified. Certain error conditions may be predetermined for the system, but an administrator may have reasons for supplementing or diverging from the predetermined error conditions. According to one particular embodiment, error conditions are specified using the ERROR and SYS-ERROR elements.
[0135] In one embodiment, setting error conditions may be accomplished using an error handling interface. The interface may allow the administrator to select either default error handling, or to customize error handling using a module for defining error handling. If default handling is selected, the system uses established settings. If customized handling is chosen, the user may use a feature to access the appropriate interface for the error handling module.
[0136] Servers may have limited capacity to perform all of the actions required of them simultaneously, the method of FIG. 1 b comprises a step for prioritizing the execution and delivery of voice services. Prioritization may establish the order in which the voice service system allocates resources for processing voice service and delivering the IVB. According to one embodiment, assigning priority to a voice service establishes priority for queries to the database system, formatting the voice service, or IVBs. Any criteria may be used for establishing priority. According to one embodiment, priority is established based on service content. According to another embodiment, priority is based on service destination. According to another embodiment, priority may be established based on the type of voice service, i.e., alert v. scheduled. Any number of procedures or criteria for denoting relative importance of service delivery may be established.
[0137] In one embodiment, an interface is provided for defining the priority of the voice service being created or edited. According to one embodiment, the interface comprises a screen including option boxes with pull down menus listing the number of different prioritization options.
[0138] Another aspect of the invention relates to a method for executing a voice service. FIG. 1 c depicts one example of a flow chart for executing a voice service. In step 310, the content of a voice service is generated. In step 320, the call structure of a telecast is created via Active Voice Pages. In step 330, the AVPs are put in a call database for processing e.g., in a call queue. In step 340, the call request is processed and an interactive voice broadcast with the user is implemented. In step 350, user's responses are written back to the voice service system (e.g., the Active Voice Page). Each of these steps will be explained in more detail below.
[0139] According to one embodiment, content is created in step 310 as follows. A voice service execution begins by running scheduled reports, queries or by taking other action to determine whether the service should be sent. The subscribers for the service are then resolved. Datasets are generated for each group of subscribers that has unique personalization criteria.
[0140] Call structure may be created (step 320) as follows. An AVP contains data at various hierarchical content levels (nodes) that can be either static text or dynamic content. Static text can be generated e.g., by typing or by incorporating a text file. Dynamic content may be generated e.g., by inserting data from a data report using a grid an/or an XSL stylesheet. Moreover, content is not limited to text based information. Other media, such as, sound files, may be incorporated into the AVP. The call data (for example, at a particular level) may be the text that is converted to speech and played when the recipient encounters the node.
[0141] According to another embodiment, call content may include “standard” active voice pages that are generated and inserted into a database or Web Server where the pages are periodically refreshed. According to one particular embodiment, the active voice page that is generated for a user contains links to these standard active voice pages. The links may be followed using a process similar to web page links.
[0142] The call structure may comprise either a static structure that is defined in the voice service interfaces e.g., by typing text into a text box and/or a dynamic structure generated by grid/XSL combinations. The dynamic structure is merged with static structure during the service execution. A single call structure is created for each group of users that have identical personalization properties across all projects because such a group will receive the same content.
[0143] After a call structure is generated, in step 330, it is sent to a call database e.g., call database 1811 shown in FIG. 3 c along with the addresses and style properties of the users. The style properties govern the behavior of a call server 18 in various aspects of the dialog with a user. Call server 18 queries call database 1811 for current call requests and places new call requests in its queue.
[0144] In step 340, a call request is processed. A call is implemented on call server 18 using one of several ports that are configured to handle telephone communication. When a port becomes available, the call request is removed from the queue and the call is made to the user. As the user navigates through an active voice page, e.g., by entering input using the key pad or by speaking responses, call/content is presented by converting text to speech in text-to-speech engine 1814. User input during the call may be stored for processing. According to another embodiment, user responses and other input may also be used to follow links to other active voice pages. For example, as explained above, “standard” active voice pages may be generated and inserted into a database or Web Server. Then, when a user's voice service is delivered, that voice service may contain links to information that may be accessed by a user. A user may access those standard active voice pages by entering input in response to OPTION or PROMPT elements.
[0145] In step 350, user responses are stored by the system. According to one embodiment, user responses are stored in a response collection defined by the active voice page. A voice service may specify that a subscriber return information during an IVB so that another application may process the data. For instance, a user may be prompted to purchase a commodity and be asked to enter or speak the number of units for the transaction. During or after an IVB, the subscriber's responses are written to a location from which they can be retrieved for processing (e.g., by an external application).
[0146] FIG. 2 is an example of an IVB with interactive call flow. An IVB usually contains a greeting message that addresses the targeted user, identifies the name of the calling application, and states the purpose of the call and/or presents summary metrics. The voice service system can also implement a PIN verification protocol, if this layer of security is required. The main menu structure of an IVB can contain a number of options that lead to sub-menu structures. A menu can also contain prompts for the user to enter numerical information using a telephone touch pad dial. A node along the hierarchical menu structure may have options to return the user to a higher level.
[0147] FIG. 3 a depicts an embodiment of a system according to one embodiment of the present invention. Preferably, the system comprises database system 12, a DSS server 14, voice service server 16, a call server 18, subscription interface 20, and other out input/files 24.
[0148] Database system 12 and DSS server 14 comprise an OLAP system that generates user-specified reports from data maintained by database system 12. Database system 12 may comprise any data warehouse or data mart as is known in the art, including a relational database management system (“RDBMS”), a multidimensional database management system (“MDDBMS”) or a hybrid system. DSS server 14 may comprise an OLAP server system for accessing and managing data stored in database system 12. DSS server 14 may comprise a ROLAP engine, MOLAP engine or a HOLAP engine according to different embodiments. Specifically, DSS server 14 may comprise a multithreaded server for performing analysis directly against database system 12. According to one embodiment, DSS server 14 comprises a ROLAP engine known as DSS Server™ offered by MicroStrategy.
[0149] Voice service server (VSS) 16, call server 18 and subscription interface 20 comprise a system through which subscribers request data and reports e.g., OLAP reports through a variety of ways and are verbally provided with their results through an IVB. During an IVB, subscribers receive their requested information and may make follow-up requests and receive responses in real-time as described above. Although the system is shown, and will be explained, as being comprised of separate components and modules, it should be understood that the components and modules may be combined or further separated. Various functions and features may be combined or separated.
[0150] Subscription interface 20 enables users or administrators of the system to monitor and update subscriptions to various services provided through VSS 16. Subscription interface 20 includes a world wide web (WWW) interface 201, a telephone interface 202, other interfaces as desired and a subscriber API 203. WWW interface 201 and telephone interface 202 enable system 100 to be accessed, for example, to subscribe to voice services or to modify existing voice services. Other interfaces may be used. Subscriber API 203 provides communication between subscription interface 20 and VSS 16 so that information entered through subscription interface 20 is passed through to VSS 16.
[0151] Subscription interface 20 is also used to create a subscriber list by adding one or more subscribers to a service. Users or system administrators having access to VSS 16 may add multiple types of subscribers to a service such as a subscriber from either a static recipient list (SRL) (e.g., addresses and groups) or a dynamic recipient list (DRL) (described in further detail below). The subscribers may be identified, for example, individually, in groups, or as dynamic subscribers in a DRL. Subscription interface 20 permits a user to specify particular criteria (e.g., filters, metrics, etc.) by accessing database system 12 and providing the user with a list of available filters, metrics, etc. The user may then select the criteria desired to be used for the service. Metadata may be used to increase the efficiency of the system.
[0152] A SRL is a list of manually entered names of subscribers of a particular service. The list may be entered using subscription interface 20 or administrator console 161. SRL entries may be personalized such that for any service, a personalization filter (other than a default filter) may be specified. A SRL enables different personalizations to apply for a login alias as well. For example, a login alias may be created using personalization engine 1632. Personalization engine 1632 enables subscribers to set preferred formats, arrangements, etc. for receiving content. The login alias may be used to determine a subscriber's preferences and generate service content according to the subscriber's preferences when generating service content for a particular subscriber.
[0153] A DRL may be a report which returns lists of valid user names based on predetermined criteria that are applied to the contents of a database such as database system 12. Providing a DRL as a report enables the DRL to incorporate any filtering criteria desired, thereby allowing a list of subscribers to be derived by an application of a filter to the data in database system 12. In this manner, subscribers of a service may be altered simply by changing the filter criteria so that different user names are returned for the DRL. Similarly, subscription lists may be changed by manipulating the filter without requiring interaction with administrator console 161. Additionally, categorization of each subscriber may be performed in numerous ways. For example, subscribers may be grouped via agent filters. In one specific embodiment, a DRL is created using DSS Agent™ offered by MicroStrategy.
[0154] VSS 16 is shown in more detail in FIG. 3 b. According to one embodiment, VSS 16 comprises administrator console 161, voice service API 162 and backend server 163. Administrator console 161 is the main interface of system 100 and is used to view and organize objects used for voice broadcasting. Administrator console 161 provides access to a hierarchy of additional interfaces through which a system administrator can utilize and maintain system 100. Administrator console 161 comprises system administrator module 1611, scheduling module 1612, exceptions module 1613, call settings module 1614, address handling module 1615, and service wizard 1616.
[0155] System administrator module 1611 comprises a number of interfaces that enable selection and control of the parameters of system 100. For example, system administrator module 1611 enables an administrator to specify and/or modify an email system, supporting servers and a repository server with which system 100 is to be used. System administrator 1611 also enables overall control of system 100. For example, system administrator module is also used to control the installation process and to start, stop or idle system 100. According to one embodiment, system administrator 1611 comprises one or more graphical user interfaces (GUIs).
[0156] Scheduling module 1612 comprises a number of interfaces that enable scheduling of voice services. Voice services may be scheduled according to any suitable methodology, such as according to scheduled times or when a predetermined condition is met. For example, the predetermined condition may be a scheduled event (time-based) including, day, date and/or time, or if certain conditions are met. In any event, when a predetermined condition is met for a given service, system 100 automatically initiates a call to the subscribers of that service. According to one embodiment, scheduling module 1612 comprises one or more GUIs.
[0157] Exceptions module 1613 comprises one or more interfaces that enable the system administrator to define one or more exceptions, triggers or other conditions. According to one embodiment, exceptions module 1613 comprises one or more GUIs.
[0158] Call settings module 1614 comprises one or more interfaces that enable the system administrator to select a set of style properties for a particular user or group of users. Each particular user may have different options for delivery of voice services depending on the hardware over which their voice services are to be delivered and depending on their own preferences. As an example of how the delivery of voice services depends on a user's hardware, the system may deliver voice services differently depending on whether the user's terminal device has voice mail or not. As an example of how the delivery of voice services depends on a user's preferences, a user may chose to have the pitch of the voice, the speed of the voice or the sex of the voice varied depending on their personal preferences. According to one embodiment, call settings module 1614 comprises one or more GUIs.
[0159] Address handling module 1615 comprises one or more interface that enable a system administrator to control the address (e.g., the telephone number) where voice services content is to be delivered. The may be set by the system administrator using address handling module 1615. According to one embodiment, address handling module 1615 comprises one or more GUIs.
[0160] Voice service wizard module 1616 comprises a collection of interfaces that enable a system administrator to create and/or modify voice services. According to one embodiment, service wizard module 1616 comprises a collection of interfaces that enable a system administrator to define a series of dialogs that contain messages and inputs and determine the call flow between these dialogs based on selections made by the user. The arrangement of the messages and prompts and the flow between them comprises the structure of a voice service. The substance of the messages and prompts is the content of a voice service. The structure and content are defined using service wizard module 1616.
[0161] Voice service API 162 (e.g., MicroStrategy Telecaster Server API) provides communication between administrator console 161 and backend server 163. Voice Service API 162 thus enables information entered through administrator console 161 to be accessed by backend server 163 (e.g., MicroStrategy Telecaster Server).
[0162] Backend server 163 utilizes the information input through administrator console 161 to initiate and construct voice services for delivery to a user. Backend server 163 comprises report formatter 1631, personalization engine 1632, scheduler 1633 and SQL engine 1634. According to one embodiment, backend server 163 comprises MicroStrategy Broadcast Server. Report formatter 1631, personalization engine 1632, and scheduler 1633 operate together, utilizing the parameters entered through administrator console 161, to initiate and assemble voice services for transmission through call server 18. Specifically, scheduler 1633 monitors the voice service schedules and initiates voice services at the appropriate time. Personalization engine 1632 and report formatter 1631 use information entered through service wizard 1616, exceptions module 1613, call settings module 1614, and address module 1615, and output provided by DSS server 14 to assemble and address personalized reports that can be sent to call server 18 for transmission. According to one embodiment, report formatter 1631 includes an XML based markup language engine to assemble the voice services. In a particular embodiment, report formatter includes a Telecaster Markup Language engine offered by MicroStrategy Inc. to assemble the call content and structure for call server 18.
[0163] SQL engine 1634 is used to make queries against a database when generating reports. More specifically, SQL engine 1634 converts requests for information into SQL statements to query a database.
[0164] Repository 164 may be a group of relational tables stored in a database. Repository 164 stores objects which are needed by system 100 to function correctly. More than one repository can exist, but preferably the system 100 is connected to only one repository at a time.
[0165] According to one embodiment, a call server 18 is used to accomplish transmission of the voice services over standard telephone lines. Call server 18 is shown in more detail in FIG. 3 c. According to one embodiment, call server 18 comprises software components 181 and hardware components 182. Software components 181 comprise call database 1811, mark-up language parsing engine 1812, call builder 1813, text-to-speech engine 1814, response storage device 1815 and statistic accumulator 1816.
[0166] Call database 1811 comprises storage for voice services that have been assembled in VSS 16 and are awaiting transmission by call server 18. These voice services may include those awaiting an initial attempt at transmission and those that were unsuccessfully transmitted (e.g., because of a busy signal) and are awaiting re-transmission. According to one embodiment, call database 1811 comprises any type of relational database having the size sufficient to store an outgoing voice service queue depending on the application. Call database 1811 also comprises storage space for a log of calls that have been completed.
[0167] Voice services stored in call database 1811 are preferably stored in a mark-up language. Mark-up language parsing engine 1812 accepts these stored voice services and separates the voice services into parts. That is, the mark-up language version of these voice services comprises call content elements, call structure elements and mark-up language instructions. Mark-up language parsing engine 1812 extracts the content and structure from the mark-up language and passes them to call builder 1813.
[0168] Call builder 1813 is the module that initiates and conducts the telephone call to a user. More specifically, call builder dials and establishes a connection with a user and passes user input through to markup language parsing engine 1812. In one embodiment, call builder 1813 comprises “Call Builder” software available from Call Technologies Inc. Call builder 1813 may be used for device detection, line monitoring for user input, call session management, potentially transfer of call to another line, termination of a call, and other functions.
[0169] Text-to-speech engine 1814 works in conjunction with mark-up language parsing engine 1812 and call builder 1813 to provide verbal communication with a user. Specifically, after call builder 1813 establishes a connection with a user, text-to-speech engine 1814 dynamically converts the content from mark-up language parsing engine 1812 to speech in real time.
[0170] A voice recognition module may be used to provide voice recognition functionality for call server 181. Voice recognition functionality may be used to identify the user at the beginning of a call to help ensure that voice services are not presented to an unauthorized user or to identify if a human or machine answers the call. This module may be a part of call builder 1813. This module may also be used to recognize spoken input (say “one” instead of press “1”), enhanced command execution (user could say “transfer money from my checking to savings”), enhanced filtering (instead of typing stock symbols, a user would say “MSTR”), enhanced prompting, (saying numeral values).
[0171] User response module 1815 comprises a module that stores user responses and passes them back to intelligence server 16. Preferably, this is done within an AVP. During a telephone call, a user may be prompted to make choices in response to prompts by the system. Depending on the nature of the call, these responses may comprise, for example, instructions to buy or sell stock, to replenish inventory, or to buy or rebook an airline flight. User response module 1815 comprises a database to store these responses along with an identification of the call in which they were given. The identification of the call in which they were given is important to determining what should be done with these responses after the call is terminated. User responses may be passed back to intelligence server 16 after the call is complete. The responses may be processed during or after the call, by the system or by being passed to another application.
[0172] Statistics accumulator 1816 comprises a module that accumulates statistics regarding calls placed by call builder 1813. These statistics including, for example, the number of times a particular call has been attempted, the number of times a particular call has resulted in voice mail, the number of times a user responds to a call and other statistics, can be used to modify future call attempts to a particular user or the structure of a voice service provided to a particular user. For example, according to one embodiment, statistics accumulator 1816 accumulates the number of times a call has been unsuccessfully attempted by call builder 1813. This type of information is then used by call server 18 to determine whether or not the call should be attempted again, and whether or not a voice mail should be left.
[0173] Call server 18 also comprises certain hardware components 182. As shown in FIG. 3 c, hardware components 182 comprise processor 1821 and computer telephone module 1822. According to one embodiment, processor 1821 comprises a Pentium II processor, available from Intel, Inc. Module 1822 provides voice synthesis functionality that is used in conjunction with Text to Speech engine 1814 to communicate the content of voice services to a user. Module 1822 preferably comprises voice boards available from Dialogic, Inc. Other processors and voice synthesizers meeting system requirements may be used.
[0174] The system and method of the present invention may form an integral part of an overall commercial transaction processing system.
[0175] According to one embodiment of the present invention, a system and method that enable closed-loop transaction processing are provided. The method begins with the deployment of an IVB by executing a service. As detailed above, this includes generating the content and combining this with personalization information to create an active voice page. Call server 18 places a call to the user. During the call, information is delivered to the user through a voice-enabled terminal device (e.g., a telephone or cellular phone). Phone lines 183 may be used for communication purposes.
[0176] During the IVB, a user may request a transaction, service, further information from the database or other request, e.g., based on options presented to the user. These will generically be referred to as transactions. The request may be, but is not necessarily, based on or related to information that was delivered to the user. According to one embodiment, the request comprises a user response to a set of options and/or input of information through a telephone keypad, voice input or other input mechanism. According to another embodiment, the request can be made by a user by speaking the request. Other types of requests are possible.
[0177] According to one embodiment, the user responses are written to a response collection, which along with information stored in the active voice page, can be used to cause a selected transaction to be executed. According to one embodiment, the active voice page comprises an XML-based document that includes embedded, generic requests, e.g., a request for a transaction, or a request for additional information (a database query). These embedded requests are linked with, for example option statements or prompts so that when a user enters information, the information is entered into the generic request and thus completes a specific transaction request. For example, in the example if a user exercises an option to buy a particular stock, that stock's ticker symbol is used to complete a generic “stock buy” that was embedded in the active voice page.
[0178] According to one embodiment, tokens are used to manage user inputs during the IVB. A token is a temporary variable that can hold different values during an IVB. When a user enters input, it is stored as a token. The token value is used to complete a transaction request as described above. According to one embodiment, the system maintains a running list of tokens, or a response collection, during an IVB.
[0179] In order to complete the requested transaction, the user responses (and other information from the active voice page) may need to be converted to a particular format. The format will depend, for example, on the nature and type of transaction requested and the system or application that will execute the transaction. For example, a request to purchase goods through a web-site may require the information to be in HTML/HTTP format. A request for additional information may require and SQL statement. A telephone-based transaction may require another format.
[0180] Therefore, the transaction request is formatted. According to one embodiment, the transaction is formatted to be made against a web-based transaction system. According to another embodiment, the transaction request is formatted to be made against a database. According to another embodiment, the transaction is formatted to be made against a telephone-based transaction system. According to another embodiment, the transaction is formatted to be made via e-mail or EDI. Other embodiments are possible.
[0181] In one embodiment, the formatted transaction request comprises an embedded transaction request. The system described in connection with FIGS. 1-3 provides interactive voice services using TML, a markup language based on XML. Using TML active voice pages are constructed that contain the structure and content for a interactive voice broadcast including, inter alia, presenting the user with options and prompting the user for information. Moreover in connection with OPTION and PROMPT elements, active voice pages also can include embedded statements such as transaction requests. Therefore, the formatting for the transaction request can be accomplished ahead of time based on the particular types of transactions the user may select.
[0182] For example, in connection with an exemplary stock purchase, an active voice page can include an embedded transaction request to sell stock in the format necessary for a particular preferred brokerage. The embedded statement would include predefined variables for the name of the stock, the number of shares, the type of order (market or limit, etc.), and other variables. When the user chooses to exercise the option to buy or sell stock, the predefined variables are replaced with information entered by the user in response to OPTION or PROMPT elements. Thus, a properly formatted transaction request is completed.
[0183] In the system of FIGS. 1-3 , TML parsing engine in call server 18 includes the functionality necessary to generate the properly formatted transaction request as described above. For example, in connection with the embodiment described above, the TML parsing engine shown in FIG. 3 c reads the active voice pages. When the TML parsing engine reads an OPTION element that includes and embedded transaction request, it stores the transaction request, and defines the necessary variables and variable locations. When the user exercises that OPTION, the user's input is received by the TML parsing engine and placed at the memory locations to complete the transaction request This technique could be used, for example, to generate a formatted transaction request for web-site.
[0184] According to another embodiment, where the transaction request is made via a natural language, voice request, a formatted transaction request can be generated in a number of ways. According to one embodiment, speech recognition technology is used to translate the user's request into text and parse out the response information. The text is then used to complete an embedded transaction request as described above. According to another embodiment, speech recognition software is used to translate the request to text. The text is then converted to a formatted request based on a set of known preferences.
[0185] A connection is established with the transaction processing system. This can be accomplished during, or after the IVB. According to one embodiment, the transaction processing system comprises a remotely located telephone-based transaction site. For example, in the system shown in FIGS. 1-3 , call server 18, through the TML parsing engine 1812, establishes a connection with a telephone-based transaction processing site.
[0186] According to another embodiment, the transaction processing system comprises a remotely based web-site. According to this embodiment, the formatted request includes a URL to locate the web-site and the system accesses the site through a web connection using the formatted request. Alternatively, the formatted request includes an e-mail address and the system uses any known email program to generate an e-mail request for the transaction.
[0187] After the connection is established, the transaction is processed by the transaction processing site and the user is notified of the status of the transaction. If the transaction is completed in real-time, the user may be immediately notified. If the transaction is executed after the IVB, the user may be called again by the system, sent an e-mail, or otherwise notified when the transaction has been completed.
[0188] According to one particular embodiment, the system comprises the interactive voice broadcasting system shown and described in FIGS. 1-3 and the transaction is accomplished in real-time. In this embodiment, confirmation of the transaction is returned to TML parsing engine 1812 shown in FIG. 3 and translated to speech in text-to-speech engine 1814 and presented to the user during the IVB. More specifically, and similar to the process described with respect to embedded formatted transaction requests, TML also enables embedding of a response statement. Thus, when the transaction is processed and confirmation of the transaction is returned to the system, an embedded confirmation statement is conveyed to the user through TML parsing engine 1812 after being converted to speech in text-to-speech engine 1814.
[0189] FIG. 4 schematically depicts one example of how the system and method of the present invention would fit into such a commercial transaction processing system. Working from left to right in FIG. 4 , the system begins and ends with information stored in relational databases. One of the primary purposes of information is in making decisions. Thus, the information in the databases is most useful if provided to someone who desires it in a timely fashion.
[0190] A voice service system is provided to enable access to the information in the databases. The voice service system utilizes personalization information and personalized menus to construct AVPs pages that enable the information to be delivered to a user verbally. Moreover, the AVPs pages, not only enable information to be presented to the user. But, they also enable the user to provide information back to the voice service system for additional processing.
[0191] According to the embodiment shown in FIG. 4 , once the AVPs are constructed by voice service system, they are processed and the content is delivered to a user verbally in an IVB. Thus, call processing and text-to-speech technology are used to establish a telephone connection with a user and convert the active voice pages to speech for presentation to the user. As shown in FIG. 4 , the IVB may be delivered to a user in many devices, including a telephone, a mobile phone, voice mail, an answering machine or any other voice-enabled device.
[0192] During the IVB, depending on the content that is being delivered, control may be passed to an e-commerce application for the user to complete a transaction based on the information presented. For example, if the user has requested information about sales on a particular brand of merchandise, the user may be connected with a particular retailer in order to complete a transaction to buy a particular good or service. Information about this transaction is then added to the databases and thus may be advantageously accessed by other users.
[0193] It may not be economical for some potential users of a voice broadcasting system to buy and/or maintain their own telephony hardware and software as embodied in call server 18. In such a case, a voice service bureau may be maintained at a remote location to service users voice service requests. A voice service bureau and a method of using a voice service bureau according to various embodiments of the present invention is described in conjunction with FIGS. 5-6 .
[0194] In one embodiment, a voice service bureau may comprise one or more call servers and call databases that are centrally located and enable other voice service systems to generate a call request and pass the call request to the VSB to execute a call. In this way the other voice service systems do not need to invest in acquiring and maintaining call data bases, call servers, additional telephone lines and other equipment or software. Moreover, the VSB facilitates weeding out usage of illegal numbers and spamming by number checking implemented through its web server.
[0195] A voice service bureau and a method of using a voice service bureau according to one embodiment are described in conjunction with FIGS. 5-6 . FIG. 5 depicts a method of utilizing a voice service bureau according to one embodiment of the present invention. The method begins in step 810 with a request to place one or more telephone calls received through a computer network.
[0196] According to one embodiment, the voice service bureau is maintained at a location distant from the voice service system. Therefore, in order for a voice service to be processed by the voice service bureau, in step 810 the voice service is sent to the voice services bureau, preferably over some secure line of communication. According to one embodiment, the request is sent to the voice service bureau through the Internet using secure HTTPS. HTTPS provides a secure exchange of data between clients and the voice service bureau using asymmetric encryption keys based on secure server certificates. In another embodiment, SSL HTTP protocol is used to send a call request to the voice service bureau. Both of these protocols help ensure that a secure channel of communication is maintained between the voice service system and the voice service bureau. Other security techniques may be used.
[0197] When a request for a call or telecast is received, by the VSB, the request is authenticated by the voice service bureau in step 820. According to one embodiment, the authenticity of the request is determined in at least two ways. First, it is determined whether or not the request was submitted from a server having a valid, active server certificate. More specifically, requests may be typically received via a stream of HTTPS data. Each such request originating from a server with a valid server certificate will include an embedded code (i.e., server certificate) that indicates the request is authentic. In addition to the use of server certificates, each request may also be authenticated using an identification number and password. Therefore, if the request submitted does not include a valid server certificate and does not identify a valid I.D./password combination, the request will not be processed. The step of authenticating also comprises performing any necessary decryption. According to one embodiment, any errors that are encountered in the process of decrypting or authenticating the call request are logged an error system and may be sent back to the administrator of the sending system. Other methods of authenticating the request are possible.
[0198] Each properly authenticated request is sent to a call server (step 830) and processed (step 840). According to one embodiment, the voice service bureau comprises a number of call servers. According to one embodiment, the calls are sent to a call database, and processed as set forth herein in conjunction with the explanation of call server 18.
[0199] One embodiment of a voice service bureau will now be explained in conjunction with FIGS. 6 a-6c. FIG. 6 a depicts a system comprising a plurality of client side installations 91, a primary voice bureau 92, a system administrator 93, a backup voice service bureau 94, and a plurality of users 95. Client side installations 91 communicate with voice service bureau 92 through a computer network. Voice service bureau 92 communicates with users 95 through a voice network. According to one embodiment, the computer network comprises the internet and client side installations 91 communicate with voice service bureau 92 using HTTPS as described above, and the voice network comprises a public telephone network.
[0200] According to one embodiment, client side installations 91 are substantially identical to the system shown in FIG. 4 except for the elimination of call server 18. In the system of FIG. 6 a, the functionality of call server 18 is performed by VSB 92. As shown in this embodiment, VSB 92 can service multiple client side installations 91l to 91n. According to another embodiment, client-side installation functionality may be included within VSB 92. According to this embodiment VSB 92 constitutes a fully functional voice service that is accessible through email, telephone or other interfaces.
[0201] According to this embodiment, when voice services have been assembled by intelligence server 16, a request to have the voice services transmitted is sent via a secure network connection through the computer network shown to primary voice bureau 92 and backup voice service bureau 94 as described above. According to one embodiment, the request comprises a mark-up language string that contains the voice service structure and content and personal style properties and other information. As described above, voice bureau 92 authenticates the request, queues the voice services and sends telecasts to users 95 through the voice network.
[0202] A block diagram of one embodiment of primary voice bureau 92 is shown in FIG. 6 b. According to this embodiment, primary voice bureau comprises routers 921, dual-homed servers 922, database servers 923, call database 924, backup storage 925, call servers 926, internal switch 927, and system administrator 93. Routers 921 receive call requests via a computer network and pass them along to one of the two dual-homed servers 922. Router 921 monitors activity on servers 922 and forwards call requests to one of the two depending on availability.
[0203] Dual-homed servers 922 comprise servers configured to receive and send HTTPS email. As part of their receiving function, dual-homed servers 922 are configured to perform the authentication processing described above. According to one embodiment, dual-homed servers 922 determine whether the incoming request originated from a server with an active server certificate and also determine if the request contains a valid I.D./password combination. Once dual-homed servers 922 have authenticated the incoming request, they forward the request to be queued in call database 924. As part of their sending function, dual-homed servers 922 are configured to format and send HTTPS email. As discussed above, during a telecast a user may request that further information be accessed from a database or that some transaction be performed. According to one embodiment, these user requests are forwarded back to the originating system via HTTPS email by dual-homed servers 922. Dual-homed servers 922 are load balanced to facilitate optimal performance and handling of incoming call requests.
[0204] Database servers 923, call database 924, and backup storage 925 together comprise a call request queuing system. Primary voice bureau 92 is configured to handle a large number of call requests. It may not be possible to process call requests as they arrive. Therefore, call requests are queued in call database 924. According to one embodiment, call database 924 comprises a relational database that maintains a queue of all call requests that need to be processed as well as logs of calls that have been processed. According to another embodiment, primary VSB 92 may include a failover measure that enables another system server to become the call database if call database 924 should fail.
[0205] Database servers 923 are configured to control access to call database 924. According to one embodiment, database servers may be optimized to generate SQL statements to access entries in call database at high speed. Database servers 923 also control storage of call requests and call logs in call database 924.
[0206] Call servers 926 each are configured to format and send telecasts. According to one embodiment, each of call servers 926 is substantially identical to call server 18 shown in FIG. 3 c. More specifically, each of call servers 926 receives requests for telecasts, parses the call content from the mark-language, establishes a connection with the user through phone lines 929, and receives user responses. According to one embodiment, call servers 926 comprise a clustered architecture that facilitates message recovery in the event of server failure.
[0207] Primary voice bureau 92 is controlled by system administrator 93 and internal switch 927. System administrator controls switch 927 and thus controls the flow of call requests to call database 924 from dual homed servers 922 and to call servers 926 from call database 924.
[0208] System administrator 93 is also configured to perform a number of other services for primary voice bureau 92. According to one embodiment, system administrator 93 also comprises a billing module, a statistics module, a service module and a security module. The billing modules tabulates the number of voice service requests that come from a particular user and considers the billing plan that the customer uses so that the user may be appropriately billed for the use of voice bureau 92. The statistics module determines and maintains statistics about the number of call requests that are processed by voice bureau 92 and statistics regarding call completion such as, e.g., success, failed due to busy signal and failed due to invalid number. These statistics may be used, for example, to evaluate hardware requirements and modify pricing schemes. The security module monitors activity on voice bureau 92 to determine whether or not any unauthorized user has accessed or attempted to access the system. The service module provides an interface through which primary voice bureau 92 may be monitored, for example, to determine the status of call requests. Other service modules are possible. Moreover, although these services are described as distinct modules, their functionality could be combined and provided in a single module.
[0209] Backup voice service bureau 94 receives a redundant request for voice services. Backup voice service bureau 94 processes the requests only when primary voice service bureau is offline or busy. One embodiment of backup voice service bureau 94 is shown in FIG. 6 c. Backup voice bureau 94 comprises routers 941, HTTP server 942, database server 943, call server 946 and routers 947. Each of these components performs a function identical to the corresponding element in primary voice bureau 92. Router 947 replaces switch 927. Communication lines 949 may replace phone lines 929. Router 947 controls the forwarding of call requests to database server 943 for queuing in an internal database, and the forwarding of call requests to call server 946 from database server 943.
[0210] The systems and methods discussed above are directed to outbound broadcasting of voice services. Nevertheless, in certain situations, for example when the out bound telecast is missed, it is desirable to for a voice service system to enable inbound calling. According to another embodiment, a method and system for providing integrated inbound and outbound voice services is disclosed.
[0211] A method for providing inbound access to voice services according to one embodiment of the present invention is shown in FIG. 7 . According to FIG. 7 , the method begins with receipt of a call requesting voice services in step 1210. To help ensure system integrity and to prevent unauthorized access, a call request is authenticated in step 1220. According to one embodiment, each incoming caller is automatically prompted to enter a login identifier and a PIN. According to another embodiment, an automatic number identification system is used, in addition to a login identifier and PIN system, to determine whether or not the user is calling from an authorized device. According to another embodiment, speaker recognition technology is utilized to identify a caller. According to this embodiment, voice prints for each user of the voice service system are stored as identifiers. When an inbound call is connected, pattern matching techniques are used verify the user's speech against the previously stored voice prints. Other security measures are possible.
[0212] In step 1230, a voice page is located. As explained above, a telecast of a voice service is driven by an active voice page. Accordingly, a user calling in to access voice services locates the desired active voice page. According to one embodiment, the user is automatically placed into an active voice page of a voice service that the user missed. That is, the system chooses an active voice page that it was unable to deliver. According to this embodiment, when a call is undeliverable (e.g., when an answering machine picks up), the active voice page for that call is placed in memory in a “voice site” table or as an active voice page on a web site and addressed using the user's identification. When the user calls in to retrieve the voice service, after the user logs in, the table or web site will be searched for an active voice page that corresponds to their identification. If such a page exists, it is executed by the call server.
[0213] Other possibilities exist for accessing active voice pages through inbound calling. According to another embodiment, the system maintains a log of all voice services sent and provides an inbound user an option to select one of their previous voice services. According to another embodiment, an inbound caller is automatically placed into an active voice page that presents the user with an option to select one of that user's most frequently used services. According to still another embodiment, the user is allowed to search for past active voice pages by date or content. For example, the user may be prompted to enter a date on or near which the desired voice page was executed. According to another embodiment, the user may use the telephone keys to enter a search term and search the content of any previously executed active voice page that they are authorized to access or that is not secure.
[0214] Once an active voice page is located, the user navigates through the active voice page in step 1240. As described above, a user navigates through an active voice by exercising options, responding to prompts and otherwise entering input to the system. An inbound calling system would thus have access to the full functionality of the voice service system described in conjunction with FIGS. 1-6 .
[0215] FIG. 8 depicts a block diagram of a call server 18a that enables integrated inbound and outbound calling. In addition to the modules depicted in call server 18 of FIG. 3 , call server 18a comprises call receiver module 1817, security module 1818 and search module 1819. Moreover, in the system for permitting inbound and outbound calling, call database 1811 has been replaced with an enhanced call database 1811a.
[0216] In order to receive inbound calls, call server 18a comprises call receiver module 1817. Although, call server 18 discussed above contains hardware permitting reception of calls as well as transmission of calls, it is not set up to receive calls. Call receiver module 1817 enables call server 18a to receive calls and routes the incoming calls to security module 1818. According to one embodiment, call receiver module comprises a software component designed to configure call server 18a to receive calls. Other embodiments are possible.
[0217] Received calls are forwarded to security module 1818 for authentication. According to one embodiment discussed above, incoming calls are authenticated using login I.D.'s and passwords. According to another embodiment, automatic number identification software is used to identify and authenticate callers. According to another embodiment, speech recognition and pattern matching techniques are used to identify a caller.
[0218] Authenticated calls may search for an active voice page using search module 1819. According to one embodiment, search module 1819 comprises a search engine designed specifically to search active voice pages. According to one embodiment discussed above, active voice pages utilize an XML-based language and search module 1819 comprises an XML-based search engine. According to another embodiment, search module 1819 comprises a SQL engine designed to make queries against a relational or other type of database.
[0219] The active voice pages that are being search are stored in enhanced call database 1811a. In addition to its facilities to queue and log calls, enhanced call database 1811 includes facilities to catalog active voice pages. According to one embodiment, enhanced call database comprises a relational or other type of database. According to this embodiment, enhanced call database is used to store and categorize active voice pages and corresponding parameters, such as expiration dates for active voice pages. Other storage facilities are possible.
[0220] Various features and functions of the present invention extend the capabilities of previously known information delivery systems. One such system is MicroStrategy's Broadcaster version 5.6. The features and functions of the present invention are usable in conjunction with Broadcaster and other information delivery systems or alone. Other products may be used with the various features and functions of the invention including, but not limited to, MicroStrategy's known product suite.
[0221] Other embodiments and uses of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The specification and examples should be considered exemplary only. The scope of the invention is only limited by the claims appended hereto.
Claims
What is claimed is:
1. A system for controlling voice service subscriptions, comprising:
a first system for generating at least one markup document personalized for at least one subscriber of at least one voice service;
a call server comprising:
a storage device for storing the at least one markup document;
a call builder operative to initiate an outbound voice-enabled communication to the at least one subscriber using the at least one markup document; and
a call receiver operative to accept an inbound voice-enabled communication from the at least one subscriber;
wherein the call server accesses the at least one markup document for dynamically interacting with the at least one subscriber during either outbound or inbound voice-enabled communications, to control the at least one subscriber's subscription, wherein the at least one markup document comprises one or more input elements that enable the user to perform at least one of un-subscribing to the at least one voice service, changing one or more subscription criteria, or subscribing to one or more additional voice services.
2. The system of claim 1, wherein the call server further comprises an authentication module operative to authenticate an inbound voice-enabled communication.
3. The system of claim 1, wherein the call server further comprises:
a parser operative to extract text from the at least one markup document; and
a text-to-speech engine for converting the extracted text into speech.
4. The system of claim 1, wherein the call server further comprises a search module operative to search markup documents stored in the storage device.
5. The system of claim 4, wherein the search module comprises an SQL engine operative to query the storage device.
6. The system of claim 1, wherein the storage device comprises a relational database.
7. The system of claim 1, wherein the at least one markup document comprises at least one extensible markup language (XML) document.
8. The system of claim 1, wherein the at least one markup document comprises at least one active voice page.
9. The system of claim 1, wherein the at least one markup document comprises information accessed from an on-line analytical processing (OLAP) system.
10. A method for controlling voice service subscriptions, comprising:
enabling a user to subscribe to at least one voice service that can output personalized information to the user during an interactive voice broadcast;
generating at least one active voice page personalized for the user;
initiating an outbound call to the user, using the at least one active voice page, to commence an interactive voice broadcast with the user; and
dynamically interacting with the user in real-time during the interactive voice broadcast using the at least one active voice page generated for the user, to control the user's subscription, wherein the at least one active voice page comprises one or more input elements that enable the user to perform at least one of un-subscribing to the at least one voice service, changing one or more subscription criteria, or subscribing to one or more additional voice services.
11. A system for controlling voice service subscriptions, comprising:
means for enabling a user to subscribe to at least one voice service that can output personalized information to the user during an interactive voice broadcast;
means for generating at least one active voice page personalized for the user;
means for initiating an outbound call to the user, using the at least one active voice page, to commence an interactive voice broadcast with the user; and
means for dynamically interacting with the user in real-time during the interactive voice broadcast using the at least one active voice page generated for the user, to control the user's subscription, wherein the at least one active voice page comprises one or more input elements that enable the user to perform at least one of un-subscribing to the at least one voice service, changing one or more subscription criteria, or subscribing to one or more additional voice services.
Patent Citations (423)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4156868(A) | 1979-05-01 | Levinson | Applicant |
| US4554418(A) | 1985-11-01 | Toy | Applicant |
| US4757525(A) | 1988-07-01 | Matthews et al. | Applicant |
| US4775936(A) | 1988-10-01 | Jung | Applicant |
| US4785408(A) | 1988-11-01 | Britton et al. | Applicant |
| US4788643(A) | 1988-11-01 | Trippe et al. | Applicant |
| US4811379(A) | 1989-03-01 | Grandfield | Applicant |
| US4812843(A) | 1989-03-01 | Champion, III et al. | Applicant |
| US4837798(A) | 1989-06-01 | Cohen et al. | Applicant |
| US4868866(A) | 1989-09-01 | Williams, Jr. | Applicant |
| US4931932(A) | 1990-06-01 | Dalnekoff et al. | Applicant |
| US4941168(A) | 1990-07-01 | Kelly, Jr. | Applicant |
| US4942616(A) | 1990-07-01 | Linstroth et al. | Applicant |
| US4953085(A) | 1990-08-01 | Atkins | Applicant |
| US4972504(A) | 1990-11-01 | Daniel, Jr. et al. | Applicant |
| US4974252(A) | 1990-11-01 | Osborne | Applicant |
| US4989141(A) | 1991-01-01 | Lyons et al. | Applicant |
| US5021953(A) | 1991-06-01 | Webber et al. | Applicant |
| US5101352(A) | 1992-03-01 | Rembert | Applicant |
| US5128861(A) | 1992-07-01 | Kagami et al. | Applicant |
| US5131020(A) | 1992-07-01 | Liebesny et al. | Examiner |
| US5168445(A) | 1992-12-01 | Kawashima et al. | Applicant |
| US5187735(A) | 1993-02-01 | Herrero Garcia et al. | Applicant |
| US5189608(A) | 1993-02-01 | Lyons et al. | Applicant |
| US5195086(A) | 1993-03-01 | Baumgartner et al. | Applicant |
| US5204821(A) | 1993-04-01 | Inui et al. | Applicant |
| US5214689(A) | 1993-05-01 | O'Sullivan | Applicant |
| US5235680(A) | 1993-08-01 | Bijnagte | Applicant |
| US5237499(A) | 1993-08-01 | Garback | Applicant |
| US5255184(A) | 1993-10-01 | Hornick et al. | Applicant |
| US5270922(A) | 1993-12-01 | Higgins | Applicant |
| US5272638(A) | 1993-12-01 | Martin et al. | Applicant |
| US5283731(A) | 1994-02-01 | Lalonde et al. | Examiner |
| US5323452(A) | 1994-06-01 | Dickman et al. | Applicant |
| US5331546(A) | 1994-07-01 | Webber et al. | Applicant |
| US5333180(A) | 1994-07-01 | Brown et al. | Applicant |
| US5347632(A) | 1994-09-01 | Filepp et al. | Applicant |
| US5371787(A) | 1994-12-01 | Hamilton | Applicant |
| US5404400(A) | 1995-04-01 | Hamilton | Applicant |
| US5406626(A) | 1995-04-01 | Ryan | Applicant |
| US5422809(A) | 1995-06-01 | Griffin et al. | Applicant |
| US5444768(A) | 1995-08-01 | Lemaire et al. | Applicant |
| US5452341(A) | 1995-09-01 | Sattar | Applicant |
| US5457904(A) | 1995-10-01 | Colvin | Applicant |
| US5479491(A) | 1995-12-01 | Herrero Garcia et al. | Applicant |
| US5493606(A) | 1996-02-01 | Osder et al. | Applicant |
| US5500793(A) | 1996-03-01 | Deming, Jr. et al. | Applicant |
| US5502637(A) | 1996-03-01 | Beaulieu et al. | Applicant |
| US5524051(A) | 1996-06-01 | Ryan | Applicant |
| US5539808(A) | 1996-07-01 | Inniss et al. | Applicant |
| US5555403(A) | 1996-09-01 | Cambot et al. | Applicant |
| US5572643(A) | 1996-11-01 | Judson | Applicant |
| US5572644(A) | 1996-11-01 | Liaw et al. | Applicant |
| US5576951(A) | 1996-11-01 | Lockwood | Applicant |
| US5577165(A) | 1996-11-01 | Takebayashi et al. | Applicant |
| US5583922(A) | 1996-12-01 | Davis et al. | Applicant |
| US5590181(A) | 1996-12-01 | Hogan et al. | Applicant |
| US5594791(A) | 1997-01-01 | Szlam et al. | Applicant |
| US5604528(A) | 1997-02-01 | Edwards et al. | Applicant |
| US5610910(A) | 1997-03-01 | Focsaneanu et al. | Applicant |
| US5630060(A) | 1997-05-01 | Tang et al. | Applicant |
| US5638424(A) | 1997-06-01 | Denio et al. | Applicant |
| US5638425(A) | 1997-06-01 | Meador, III et al. | Applicant |
| US5644624(A) | 1997-07-01 | Caldwell | Applicant |
| US5652789(A) | 1997-07-01 | Miner et al. | Applicant |
| US5664115(A) | 1997-09-01 | Fraser | Applicant |
| US5684992(A) | 1997-11-01 | Abrams et al. | Applicant |
| US5689650(A) | 1997-11-01 | McClelland et al. | Applicant |
| US5692181(A) | 1997-11-01 | Anand et al. | Applicant |
| US5694459(A) | 1997-12-01 | Backaus et al. | Examiner |
| US5701451(A) | 1997-12-01 | Rogers et al. | Applicant |
| US5706442(A) | 1998-01-01 | Anderson et al. | Applicant |
| US5710889(A) | 1998-01-01 | Clark et al. | Applicant |
| US5712901(A) | 1998-01-01 | Meermans | Applicant |
| US5715370(A) | 1998-02-01 | Luther et al. | Applicant |
| US5717923(A) | 1998-02-01 | Dedrick | Applicant |
| US5721827(A) | 1998-02-01 | Logan et al. | Applicant |
| US5724410(A) | 1998-03-01 | Parvulescu et al. | Applicant |
| US5724420(A) | 1998-03-01 | Torgrim | Applicant |
| US5724520(A) | 1998-03-01 | Goheen | Applicant |
| US5724525(A) | 1998-03-01 | Beyers, II et al. | Applicant |
| US5732216(A) | 1998-03-01 | Logan et al. | Applicant |
| US5732398(A) | 1998-03-01 | Tagawa | Applicant |
| US5737393(A) | 1998-04-01 | Wolf | Applicant |
| US5740429(A) | 1998-04-01 | Wang et al. | Applicant |
| US5740829(A) | 1998-04-01 | Jacobs et al. | Applicant |
| US5742775(A) | 1998-04-01 | King | Applicant |
| US5748959(A) | 1998-05-01 | Reynolds | Applicant |
| US5751790(A) | 1998-05-01 | Makihata | Applicant |
| US5751806(A) | 1998-05-01 | Ryan | Applicant |
| US5754858(A) | 1998-05-01 | Broman et al. | Applicant |
| US5754939(A) | 1998-05-01 | Herz et al. | Applicant |
| US5757644(A) | 1998-05-01 | Jorgensen et al. | Applicant |
| US5758088(A) | 1998-05-01 | Bezaire et al. | Applicant |
| US5758351(A) | 1998-05-01 | Gibson et al. | Applicant |
| US5761432(A) | 1998-06-01 | Bergholm et al. | Applicant |
| US5764736(A) | 1998-06-01 | Shachar et al. | Applicant |
| US5765028(A) | 1998-06-01 | Gladden | Applicant |
| US5765143(A) | 1998-06-01 | Sheldon et al. | Applicant |
| US5771172(A) | 1998-06-01 | Yamamoto et al. | Applicant |
| US5771276(A) | 1998-06-01 | Wolf | Applicant |
| US5781735(A) | 1998-07-01 | Southard | Applicant |
| US5781886(A) | 1998-07-01 | Tsujiuchi | Applicant |
| US5787151(A) | 1998-07-01 | Nakatsu et al. | Applicant |
| US5787278(A) | 1998-07-01 | Barton et al. | Applicant |
| USH1743(H) | 1998-08-01 | Graves et al. | Applicant |
| US5790936(A) | 1998-08-01 | Dinkins | Applicant |
| US5793980(A) | 1998-08-01 | Glaser et al. | Applicant |
| US5794207(A) | 1998-08-01 | Walker et al. | Applicant |
| US5794246(A) | 1998-08-01 | Sankaran et al. | Applicant |
| US5797124(A) | 1998-08-01 | Walsh et al. | Applicant |
| US5799063(A) | 1998-08-01 | Krane | Applicant |
| US5799156(A) | 1998-08-01 | Hogan et al. | Applicant |
| US5802488(A) | 1998-09-01 | Edatsune | Applicant |
| US5802526(A) | 1998-09-01 | Fawcett et al. | Applicant |
| US5806050(A) | 1998-09-01 | Shinn et al. | Applicant |
| US5809113(A) | 1998-09-01 | Lieuwen | Applicant |
| US5809415(A) | 1998-09-01 | Rossmann | Applicant |
| US5809483(A) | 1998-09-01 | Broka et al. | Applicant |
| US5812987(A) | 1998-09-01 | Luskin et al. | Applicant |
| US5819220(A) | 1998-10-01 | Sarukkai et al. | Applicant |
| US5819293(A) | 1998-10-01 | Comer et al. | Applicant |
| US5822405(A) | 1998-10-01 | Astarabadi | Applicant |
| US5825856(A) | 1998-10-01 | Porter et al. | Applicant |
| US5832451(A) | 1998-11-01 | Flake et al. | Applicant |
| US5838252(A) | 1998-11-01 | Kikinis | Applicant |
| US5838768(A) | 1998-11-01 | Sumar et al. | Applicant |
| US5848396(A) | 1998-12-01 | Gerace | Applicant |
| US5848397(A) | 1998-12-01 | Marsh et al. | Applicant |
| US5850433(A) | 1998-12-01 | Rondeau | Applicant |
| US5852811(A) | 1998-12-01 | Atkins | Applicant |
| US5852819(A) | 1998-12-01 | Beller | Applicant |
| US5854746(A) | 1998-12-01 | Yamamoto et al. | Applicant |
| US5857191(A) | 1999-01-01 | Blackwell, Jr. et al. | Applicant |
| US5864605(A) | 1999-01-01 | Keshav | Applicant |
| US5864827(A) | 1999-01-01 | Wilson | Applicant |
| US5864828(A) | 1999-01-01 | Atkins | Applicant |
| US5867153(A) | 1999-02-01 | Grandcolas et al. | Applicant |
| US5870454(A) | 1999-02-01 | Dahlen | Applicant |
| US5870724(A) | 1999-02-01 | Lawlor et al. | Applicant |
| US5870746(A) | 1999-02-01 | Knutson et al. | Applicant |
| US5872921(A) | 1999-02-01 | Zahariev et al. | Applicant |
| US5872926(A) | 1999-02-01 | Levac et al. | Applicant |
| US5878403(A) | 1999-03-01 | DeFrancesco et al. | Applicant |
| US5880726(A) | 1999-03-01 | Takiguchi et al. | Applicant |
| US5884262(A) | 1999-03-01 | Wise et al. | Applicant |
| US5884266(A) | 1999-03-01 | Dvorak | Applicant |
| US5884285(A) | 1999-03-01 | Atkins | Applicant |
| US5884312(A) | 1999-03-01 | Dustan et al. | Applicant |
| US5890140(A) | 1999-03-01 | Clark et al. | Applicant |
| US5893079(A) | 1999-04-01 | Cwenar | Applicant |
| US5893905(A) | 1999-04-01 | Main et al. | Applicant |
| US5897620(A) | 1999-04-01 | Walker et al. | Applicant |
| US5907598(A) | 1999-05-01 | Mandalia et al. | Applicant |
| US5907837(A) | 1999-05-01 | Ferrel et al. | Applicant |
| US5911135(A) | 1999-06-01 | Atkins | Applicant |
| US5911136(A) | 1999-06-01 | Atkins | Applicant |
| US5913195(A) | 1999-06-01 | Weeren et al. | Applicant |
| US5913202(A) | 1999-06-01 | Motoyama | Applicant |
| US5914878(A) | 1999-06-01 | Yamamoto et al. | Applicant |
| US5915001(A) | 1999-06-01 | Uppaluru | Examiner |
| US5915238(A) | 1999-06-01 | Tjaden | Applicant |
| US5918213(A) | 1999-06-01 | Bernard et al. | Applicant |
| US5918217(A) | 1999-06-01 | Maggioncalda et al. | Applicant |
| US5918225(A) | 1999-06-01 | White et al. | Applicant |
| US5918232(A) | 1999-06-01 | Pouschine et al. | Applicant |
| US5920848(A) | 1999-07-01 | Schutzer et al. | Applicant |
| US5923736(A) | 1999-07-01 | Shachar | Applicant |
| US5924068(A) | 1999-07-01 | Richard et al. | Applicant |
| US5926789(A) | 1999-07-01 | Barbara et al. | Applicant |
| US5931900(A) | 1999-08-01 | Notani et al. | Applicant |
| US5931908(A) | 1999-08-01 | Gerba et al. | Applicant |
| US5933816(A) | 1999-08-01 | Zeanah et al. | Applicant |
| US5940818(A) | 1999-08-01 | Malloy et al. | Applicant |
| US5943395(A) | 1999-08-01 | Hansen | Applicant |
| US5943399(A) | 1999-08-01 | Bannister et al. | Applicant |
| US5943410(A) | 1999-08-01 | Shaffer et al. | Applicant |
| US5943677(A) | 1999-08-01 | Hicks | Applicant |
| US5945989(A) | 1999-08-01 | Freishtat et al. | Applicant |
| US5946485(A) | 1999-08-01 | Weeren et al. | Applicant |
| US5946666(A) | 1999-08-01 | Nevo et al. | Applicant |
| US5946711(A) | 1999-08-01 | Donnelly | Applicant |
| US5948040(A) | 1999-09-01 | DeLorme et al. | Applicant |
| US5950165(A) | 1999-09-01 | Shaffer et al. | Applicant |
| US5953392(A) | 1999-09-01 | Rhie et al. | Applicant |
| US5953406(A) | 1999-09-01 | LaRue et al. | Applicant |
| US5956693(A) | 1999-09-01 | Geerlings | Applicant |
| US5960437(A) | 1999-09-01 | Krawchuk et al. | Applicant |
| US5963641(A) | 1999-10-01 | Crandall et al. | Applicant |
| US5970122(A) | 1999-10-01 | LaPorta et al. | Applicant |
| US5970124(A) | 1999-10-01 | Csaszar et al. | Applicant |
| US5974398(A) | 1999-10-01 | Hanson et al. | Applicant |
| US5974406(A) | 1999-10-01 | Bisdikian et al. | Applicant |
| US5974441(A) | 1999-10-01 | Rogers et al. | Applicant |
| US5978766(A) | 1999-11-01 | Luciw | Applicant |
| US5978796(A) | 1999-11-01 | Malloy et al. | Applicant |
| US5983184(A) | 1999-11-01 | Noguchi | Applicant |
| US5987586(A) | 1999-11-01 | Byers | Applicant |
| US5990885(A) | 1999-11-01 | Gopinath | Applicant |
| US5991365(A) | 1999-11-01 | Pizano et al. | Applicant |
| US5995945(A) | 1999-11-01 | Notani et al. | Applicant |
| US5996006(A) | 1999-11-01 | Speicher | Applicant |
| US5999526(A) | 1999-12-01 | Garland et al. | Applicant |
| US6002394(A) | 1999-12-01 | Schein et al. | Applicant |
| US6003009(A) | 1999-12-01 | Nishimura | Applicant |
| US6006225(A) | 1999-12-01 | Bowman et al. | Applicant |
| US6009383(A) | 1999-12-01 | Mony | Applicant |
| US6009410(A) | 1999-12-01 | LeMole et al. | Applicant |
| US6011579(A) | 2000-01-01 | Newlin | Applicant |
| US6011844(A) | 2000-01-01 | Uppaluru et al. | Applicant |
| US6012045(A) | 2000-01-01 | Barzilai et al. | Applicant |
| US6012066(A) | 2000-01-01 | Discount et al. | Applicant |
| US6012083(A) | 2000-01-01 | Savitzky et al. | Applicant |
| US6014427(A) | 2000-01-01 | Hanson et al. | Applicant |
| US6014428(A) | 2000-01-01 | Wolf | Applicant |
| US6014429(A) | 2000-01-01 | LaPorta et al. | Applicant |
| US6016335(A) | 2000-01-01 | Lacy et al. | Applicant |
| US6016336(A) | 2000-01-01 | Hanson | Applicant |
| US6016478(A) | 2000-01-01 | Zhang et al. | Applicant |
| US6018710(A) | 2000-01-01 | Wynblatt et al. | Applicant |
| US6018715(A) | 2000-01-01 | Lynch et al. | Applicant |
| US6021181(A) | 2000-02-01 | Miner et al. | Applicant |
| US6021397(A) | 2000-02-01 | Jones et al. | Applicant |
| US6023714(A) | 2000-02-01 | Hill et al. | Applicant |
| US6026087(A) | 2000-02-01 | Mirashrafi et al. | Applicant |
| US6029195(A) | 2000-02-01 | Herz | Applicant |
| US6031836(A) | 2000-02-01 | Haserodt | Applicant |
| US6035336(A) | 2000-03-01 | Lu et al. | Applicant |
| US6038561(A) | 2000-03-01 | Snyder et al. | Applicant |
| US6044134(A) | 2000-03-01 | De La Huerga | Applicant |
| US6047264(A) | 2000-04-01 | Fisher et al. | Applicant |
| US6047327(A) | 2000-04-01 | Tso et al. | Applicant |
| US6055513(A) | 2000-04-01 | Katz et al. | Applicant |
| US6055514(A) | 2000-04-01 | Wren | Applicant |
| US6058166(A) | 2000-05-01 | Osder et al. | Applicant |
| US6061433(A) | 2000-05-01 | Polcyn et al. | Applicant |
| US6064980(A) | 2000-05-01 | Jacobi et al. | Applicant |
| US6067348(A) | 2000-05-01 | Hibbeler | Applicant |
| US6067535(A) | 2000-05-01 | Hobson et al. | Applicant |
| US6078924(A) | 2000-06-01 | Ainsbury et al. | Examiner |
| US6078994(A) | 2000-06-01 | Carey | Applicant |
| US6081815(A) | 2000-06-01 | Spitznagel et al. | Applicant |
| US6094651(A) | 2000-07-01 | Agrawal et al. | Applicant |
| US6094655(A) | 2000-07-01 | Rogers et al. | Applicant |
| US6101241(A) | 2000-08-01 | Boyce et al. | Applicant |
| US6101443(A) | 2000-08-01 | Kato et al. | Applicant |
| US6101473(A) | 2000-08-01 | Scott et al. | Applicant |
| US6108686(A) | 2000-08-01 | Williams, Jr. | Applicant |
| US6115686(A) | 2000-09-01 | Chung et al. | Applicant |
| US6115693(A) | 2000-09-01 | McDonough et al. | Applicant |
| US6119095(A) | 2000-09-01 | Morita | Applicant |
| US6122628(A) | 2000-09-01 | Castelli et al. | Applicant |
| US6122636(A) | 2000-09-01 | Malloy et al. | Applicant |
| US6125376(A) | 2000-09-01 | Klarlund et al. | Applicant |
| US6131184(A) | 2000-10-01 | Weeren et al. | Applicant |
| US6134563(A) | 2000-10-01 | Clancey et al. | Applicant |
| US6144848(A) | 2000-11-01 | Walsh et al. | Applicant |
| US6151582(A) | 2000-11-01 | Huang et al. | Applicant |
| US6151601(A) | 2000-11-01 | Papierniak et al. | Applicant |
| US6154527(A) | 2000-11-01 | Porter et al. | Applicant |
| US6154766(A) | 2000-11-01 | Yost et al. | Applicant |
| US6157705(A) | 2000-12-01 | Perrone | Applicant |
| US6163774(A) | 2000-12-01 | Lore et al. | Applicant |
| US6167379(A) | 2000-12-01 | Dean et al. | Applicant |
| US6167383(A) | 2000-12-01 | Henson | Applicant |
| US6173266(B1) | 2001-01-01 | Marx et al. | Applicant |
| US6173310(B1) | 2001-01-01 | Yost et al. | Applicant |
| US6173316(B1) | 2001-01-01 | De Boor et al. | Applicant |
| US6178446(B1) | 2001-01-01 | Gerszberg et al. | Applicant |
| US6181935(B1) | 2001-01-01 | Gossman et al. | Applicant |
| US6182052(B1) | 2001-01-01 | Fulton et al. | Applicant |
| US6182053(B1) | 2001-01-01 | Rauber et al. | Applicant |
| US6182153(B1) | 2001-01-01 | Hollberg et al. | Applicant |
| US6185558(B1) | 2001-02-01 | Bowman et al. | Applicant |
| US6189008(B1) | 2001-02-01 | Easty et al. | Applicant |
| US6192050(B1) | 2001-02-01 | Stovall | Applicant |
| US6199082(B1) | 2001-03-01 | Ferrel et al. | Applicant |
| US6201948(B1) | 2001-03-01 | Cook et al. | Applicant |
| US6203192(B1) | 2001-03-01 | Fortman | Applicant |
| US6209026(B1) | 2001-03-01 | Ran et al. | Applicant |
| US6215858(B1) | 2001-04-01 | Bartholomew et al. | Applicant |
| US6219643(B1) | 2001-04-01 | Cohen et al. | Applicant |
| US6223983(B1) | 2001-05-01 | Kjonaas et al. | Applicant |
| US6226360(B1) | 2001-05-01 | Goldberg et al. | Applicant |
| US6233609(B1) | 2001-05-01 | Mittal | Applicant |
| US6236977(B1) | 2001-05-01 | Verba et al. | Applicant |
| US6240391(B1) | 2001-05-01 | Ball et al. | Applicant |
| US6243092(B1) | 2001-06-01 | Okita et al. | Applicant |
| US6243445(B1) | 2001-06-01 | Begeja et al. | Applicant |
| US6246672(B1) | 2001-06-01 | Lumelsky | Applicant |
| US6246981(B1) | 2001-06-01 | Papineni et al. | Applicant |
| US6253062(B1) | 2001-06-01 | Leyendecker | Examiner |
| US6253146(B1) | 2001-06-01 | Hanson et al. | Applicant |
| US6256659(B1) | 2001-07-01 | McLain, Jr. et al. | Applicant |
| US6259443(B1) | 2001-07-01 | Williams, Jr. | Applicant |
| US6260050(B1) | 2001-07-01 | Yost et al. | Applicant |
| US6263051(B1) | 2001-07-01 | Saylor et al. | Applicant |
| US6269151(B1) | 2001-07-01 | Hanson | Applicant |
| US6269336(B1) | 2001-07-01 | Ladd et al. | Applicant |
| US6269393(B1) | 2001-07-01 | Yost et al. | Applicant |
| US6275746(B1) | 2001-08-01 | Leatherman et al. | Applicant |
| US6279000(B1) | 2001-08-01 | Suda et al. | Applicant |
| US6279033(B1) | 2001-08-01 | Selvarajan et al. | Applicant |
| US6279038(B1) | 2001-08-01 | Hogan et al. | Applicant |
| US6286030(B1) | 2001-09-01 | Wenig et al. | Applicant |
| US6289352(B1) | 2001-09-01 | Proctor | Applicant |
| US6292811(B1) | 2001-09-01 | Clancey et al. | Applicant |
| US6301590(B1) | 2001-10-01 | Siow et al. | Applicant |
| US6304850(B1) | 2001-10-01 | Keller et al. | Applicant |
| US6311178(B1) | 2001-10-01 | Bi et al. | Applicant |
| US6313734(B1) | 2001-11-01 | Weiss et al. | Applicant |
| US6314094(B1) | 2001-11-01 | Boys | Applicant |
| US6314402(B1) | 2001-11-01 | Monaco et al. | Applicant |
| US6314533(B1) | 2001-11-01 | Novik et al. | Applicant |
| US6317750(B1) | 2001-11-01 | Tortolani et al. | Applicant |
| US6321190(B1) | 2001-11-01 | Bernardes et al. | Applicant |
| US6321198(B1) | 2001-11-01 | Hank et al. | Applicant |
| US6321221(B1) | 2001-11-01 | Bieganski | Applicant |
| US6327343(B1) | 2001-12-01 | Epstein et al. | Applicant |
| US6336124(B1) | 2002-01-01 | Alam et al. | Applicant |
| US6341271(B1) | 2002-01-01 | Salvo et al. | Applicant |
| US6349290(B1) | 2002-02-01 | Horowitz et al. | Applicant |
| US6360139(B1) | 2002-03-01 | Jacobs | Applicant |
| US6363393(B1) | 2002-03-01 | Ribitzky | Applicant |
| US6366298(B1) | 2002-04-01 | Haitsuka et al. | Applicant |
| US6385191(B1) | 2002-05-01 | Coffman et al. | Applicant |
| US6385301(B1) | 2002-05-01 | Nolting et al. | Applicant |
| US6385583(B1) | 2002-05-01 | Ladd et al. | Examiner |
| US6389398(B1) | 2002-05-01 | Lustgarten et al. | Applicant |
| US6397387(B1) | 2002-05-01 | Rosin et al. | Applicant |
| US6400804(B1) | 2002-06-01 | Bilder | Applicant |
| US6404858(B1) | 2002-06-01 | Farris et al. | Applicant |
| US6404877(B1) | 2002-06-01 | Bolduc et al. | Applicant |
| US6405171(B1) | 2002-06-01 | Kelley | Applicant |
| US6411685(B1) | 2002-06-01 | O'Neal | Applicant |
| US6412012(B1) | 2002-06-01 | Bieganski et al. | Applicant |
| US6415269(B1) | 2002-07-01 | Dinwoodie | Applicant |
| US6430545(B1) | 2002-08-01 | Honarvar et al. | Applicant |
| US6434524(B1) | 2002-08-01 | Weber | Applicant |
| US6438217(B1) | 2002-08-01 | Huna | Applicant |
| US6442560(B1) | 2002-08-01 | Berger et al. | Applicant |
| US6442598(B1) | 2002-08-01 | Wright et al. | Applicant |
| US6445694(B1) | 2002-09-01 | Swartz | Applicant |
| US6456699(B1) | 2002-09-01 | Burg et al. | Applicant |
| US6456974(B1) | 2002-09-01 | Baker et al. | Applicant |
| US6459427(B1) | 2002-10-01 | Mao et al. | Applicant |
| US6459774(B1) | 2002-10-01 | Ball et al. | Applicant |
| US6466654(B1) | 2002-10-01 | Cooper et al. | Applicant |
| US6473612(B1) | 2002-10-01 | Cox et al. | Applicant |
| US6477549(B1) | 2002-11-01 | Hishida et al. | Applicant |
| US6480842(B1) | 2002-11-01 | Agassi et al. | Applicant |
| US6482156(B2) | 2002-11-01 | Iliff | Applicant |
| US6487277(B2) | 2002-11-01 | Beyda et al. | Applicant |
| US6487533(B2) | 2002-11-01 | Hyde-Thomson et al. | Applicant |
| US6490564(B1) | 2002-12-01 | Dodrill et al. | Applicant |
| US6490593(B2) | 2002-12-01 | Proctor | Applicant |
| US6493685(B1) | 2002-12-01 | Ensel et al. | Applicant |
| US6496568(B1) | 2002-12-01 | Nelson | Applicant |
| US6501832(B1) | 2002-12-01 | Saylor et al. | Applicant |
| US6507817(B1) | 2003-01-01 | Wolfe et al. | Applicant |
| US6513019(B2) | 2003-01-01 | Lewis | Applicant |
| US6539359(B1) | 2003-03-01 | Ladd et al. | Applicant |
| US6549612(B2) | 2003-04-01 | Gifford et al. | Applicant |
| US6567796(B1) | 2003-05-01 | Yost et al. | Applicant |
| US6571281(B1) | 2003-05-01 | Nickerson | Applicant |
| US6578000(B1) | 2003-06-01 | Dodrill et al. | Applicant |
| US6587547(B1) | 2003-07-01 | Zirngibl et al. | Applicant |
| US6587822(B2) | 2003-07-01 | Brown et al. | Applicant |
| US6591263(B1) | 2003-07-01 | Becker et al. | Examiner |
| US6594682(B2) | 2003-07-01 | Peterson et al. | Applicant |
| US6600736(B1) | 2003-07-01 | Ball et al. | Applicant |
| US6604135(B1) | 2003-08-01 | Rogers et al. | Applicant |
| US6606596(B1) | 2003-08-01 | Zirngibl et al. | Applicant |
| US6658093(B1) | 2003-12-01 | Langseth et al. | Applicant |
| US6658432(B1) | 2003-12-01 | Alavi et al. | Applicant |
| US6671716(B1) | 2003-12-01 | Diedrichsen et al. | Applicant |
| US6697824(B1) | 2004-02-01 | Bowman-Amuah | Applicant |
| US6697964(B1) | 2004-02-01 | Dodrill et al. | Applicant |
| US6707889(B1) | 2004-03-01 | Saylor et al. | Applicant |
| US6741967(B1) | 2004-05-01 | Wu et al. | Applicant |
| US6741995(B1) | 2004-05-01 | Chen et al. | Applicant |
| US6760412(B1) | 2004-07-01 | Loucks | Applicant |
| US6763300(B2) | 2004-07-01 | Jones | Applicant |
| US6765997(B1) | 2004-07-01 | Zirngibl et al. | Applicant |
| US6768788(B1) | 2004-07-01 | Langseth et al. | Applicant |
| US6785592(B1) | 2004-08-01 | Smith et al. | Applicant |
| US6788768(B1) | 2004-09-01 | Saylor et al. | Applicant |
| US6792086(B1) | 2004-09-01 | Saylor et al. | Applicant |
| US6798867(B1) | 2004-09-01 | Zirngibl et al. | Applicant |
| US6829334(B1) | 2004-12-01 | Zirngibl et al. | Applicant |
| US6836537(B1) | 2004-12-01 | Zirngibl et al. | Applicant |
| US6850603(B1) | 2005-02-01 | Eberle et al. | Applicant |
| US6873693(B1) | 2005-03-01 | Langseth et al. | Applicant |
| US6885734(B1) | 2005-04-01 | Eberle et al. | Applicant |
| US6888929(B1) | 2005-05-01 | Saylor et al. | Applicant |
| US6895084(B1) | 2005-05-01 | Saylor et al. | Applicant |
| US6940953(B1) | 2005-09-01 | Eberle et al. | Applicant |
| US6964012(B1) | 2005-11-01 | Zirngibl et al. | Applicant |
| US6977992(B2) | 2005-12-01 | Zirngibl et al. | Applicant |
| US6993476(B1) | 2006-01-01 | Dutta et al. | Applicant |
| US7020251(B2) | 2006-03-01 | Zirngibl et al. | Applicant |
| US7065188(B1) | 2006-06-01 | Mei et al. | Applicant |
| US7082422(B1) | 2006-07-01 | Zirngibl et al. | Applicant |
| US7197461(B1) | 2007-03-01 | Eberle et al. | Applicant |
| US7266181(B1) | 2007-09-01 | Zirngibl et al. | Applicant |
| US7272212(B2) | 2007-09-01 | Eberle et al. | Applicant |
| US7330847(B2) | 2008-02-01 | Saylor et al. | Applicant |
| US7340040(B1) | 2008-03-01 | Saylor et al. | Applicant |
| US7428302(B2) | 2008-09-01 | Zirngibl et al. | Applicant |
| US2001/0012335(A1) | 2001-08-01 | Kaufman et al. | Applicant |
| US2002/0006126(A1) | 2002-01-01 | Johnson et al. | Applicant |
| US2002/0059373(A1) | 2002-05-01 | Boys | Applicant |
| US2002/0065752(A1) | 2002-05-01 | Lewis | Applicant |
| US2003/0088872(A1) | 2003-05-01 | Maissel et al. | Applicant |
| US2003/0101201(A1) | 2003-05-01 | Saylor et al. | Applicant |
| US2004/0128514(A1) | 2004-07-01 | Rhoads | Applicant |
| US2004/0133907(A1) | 2004-07-01 | Rodriguez et al. | Applicant |
| US2006/0129499(A1) | 2006-06-01 | Combar et al. | Applicant |
| US2006/0282408(A1) | 2006-12-01 | Wisely et al. | Applicant |
| CA2153096 | 1996-12-01 | Applicant | |
| EP878948 | 1998-11-01 | Applicant | |
| EP889627 | 1999-01-01 | Applicant | |
| WO94/15294 | 1994-07-01 | Examiner |
Non-Patent Literature (170)
- MSTR149—Intrepid Systems: “Intrepid Systems to Integrate DSS Broadcaster with Its “DecisionMaster” Decision Support Solution; Non-PC Users Benefit from Receiving High-Impact, Mission Critical Information”, Business Wire, Aug. 11, 1998, Proquest #32760823.Applicant
- MSTR150—MicroStrategy: “MicroStrategy's DSS Broadcaster Supports Personal Digital Assistants and Advanced Wireless Data Devices”, Business Wire, Sep. 8, 1998, Proquest #33719588.Applicant
- MSTR151—Mills, Mike, “Putting the Internet in Your Hand; Nokia's Phone/Palmtop Computer Offers a Glimpse of the Future”, The Wasington Post, Jun. 29, 1998, Proquest #30839088.Applicant
- MSTR161—MicroStrategy: “MicroStrategy Customers Embrace DSS Broadcaster”, Business Wire, Aug. 11, 1998, 4 pages, Proquest #32763756.Applicant
- MSTR162—MicroStrategy: “MicroStrategy Introduces DSS StockMarket”, Business Wire, Jun. 16, 1998, 3 pages, Dialog File 20 #01940188.Applicant
- MSTR163—Lucent: Gohring, Nancy: “Text-to-Speech Moves Along”, Telephone, Aug. 24, 1998, v235n8pg56, 3 pages, Proquest #33418136.Applicant
- MSTR164—Lucent: “Lucent Technologies Unviels Powerful New Speech Software”, Business Wire, Aug. 24, 1998, 3 pages, Proquest #33311728.Applicant
- MSTR165—Vergito Delivers an Unprecedented Level of Personalized Webcasting with I-Casting, Business Wire, Mar. 10, 1997, 3 pages.Applicant
- MSTR166—MicroStrategy: MicroStrategy to Launch DSS Broadcaster, M2 Presswire, Feb. 27, 1998, 2 pages.Applicant
- MSTR001—Advertisement for Progressive Telecommunications Corporation's OPUS, date unknown.Applicant
- MSTR002—KnowledgeX Workgroup Edition Publication, date unknown.Applicant
- MSTR003—Relational OLAP Server, MicroStrategy; DSS Server Brochure, 1996.Applicant
- MSTR004—Relational OLAP Interface for the Web, 1996.Applicant
- MSTR005—“Andyne Introduces Greater Flexibility for Database Queries; New Query Management Option Provides Enhanced Management for Enterprise-Wide Queries,”Business Wire, Jan. 3, 1996. Available from the Dow Jones Interactive Web Site http://Ptg.djnr.com.Applicant
- MSTR006—Catalano, Carla, “OLAP, Scheduling, Tuning for DBMSs” Computer World, Apr. 1, 1996. Available in Dow Jones Interactive, http://www.dowjonesinteractive.com.Applicant
- MSTR007—Andyne's Intranet Strategy Brings DSS to the Web; Company Aims to Dramatically Broaden Scope of Reporting, Online Analysis, PR Newswire, Sep. 18, 1996. Available from the Dow Jones Interactive Web Site http://Ptg.djnr.com.Applicant
- MSTR008—Sachs et al., “A First Step on the Path to Automated Flight Reservations,” Interactive Voice Technology for Telecommunications, 1996.Applicant
- MSTR009—Bennacef et al., “Dialog in the RAILTEL Telephone-Based System,” Spoken Language, 1996.Applicant
- MSTR010—Brooks, Peter, “Targeting Customer,” DMBS, v9, n13, Dec. 1996, pp. 54-58.Applicant
- MSTR011—“Sterling Software Announces Alliance with Thinking Machines,” Business Wire, Dec. 16, 1996. Available from the Dow Jones Interactive Web Site http://Ptg.djnr.com.Applicant
- MSTR012—Gupta et al., “Index Selection for OLAP,” Proceedings of the 13th International Conference on Data Engineering, © 1997.Applicant
- MSTR013—Ho et al., “Partial-Sum Queries in OLAP Data Cubes Using Covering Codes,” PODS'97 Tuscon, AZ USA.Applicant
- MSTR014—Kilmartin et al., “Real Time Stock Price Distribution Utilising the GSM Short Messaging Service,” 1997 IEEE International Conference on Personal Wireless, 1997, Abstract.Applicant
- MSTR015—Data Warehousing: Data Access and Delivery, Infobase Technology Database, 1997, http://www.dbaint.com/oldinfobase/dwaccdel.html.Applicant
- MSTR016—Gardner, Dana Marie, “Cashing in With Data Warehouses and the Web,” Data Based Advisor, v15, n2, Feb. 1997, pp. 60-63.Applicant
- MSTR017—Intrepid Systems Announces General Availability of DecisionMaster 4.1; Retailing's Premier Decision Support Software Enhancements Automate Information Delivery, Business Wire, May 27, 1997. Available in Dow Jones Interactive, http://www.dowjonesinteractive.com.Applicant
- MSTR018—Blue Isle Software InTouch/2000 Product Overview, Blue Isle Software, Inc. (archived Jul. 7, 1997), http://www.blueisle.com. Available in Internet Archive Waybackmachine http://www.archive.org.Applicant
- MSTR019—“Blue Isle Software Teams with Arbor Software to Deliver Automated Systems Management Capabilities for Arbor Essbase,” Business Wire, Oct. 29, 1997. Available in Lexis, Nexis Library, ALLNWS file.Applicant
- MSTR020—“Early Warning: Compulogic's Dynamic Query Messenger,” Software Futures, Nov. 1, 1997. Available in Lexis, Nexis Library, ALLNWS file.Applicant
- MSTR021—Kilmartin et al., “Development of an Interactive Voice Response System for a GSM SMS Based Share Price Server,” DSP '97 Conference Proceedings, Dec. 1997, Abstract.Applicant
- MSTR022—Avnur et al., “Control: Continuous Output and Navigation Technology with Refinement On-Line,” © 1998.Applicant
- MSTR023—Liang et al., “Computing Multidimensional Aggregates in Parallel,” 1998 International Conference on Parallel and Distributed Systems, IEEE.Applicant
- MSTR024—Friel et al., An Automated Stock Price Delivery System Based on the GSM Short Message Service, ICC'98 1998 IEEE International Conference on Communications, 1998, Abstract.Applicant
- MSTR025—Microstrategy Products and Services, 1998.Applicant
- MSTR026—Personalized Information Broadcast Server, 1998.Applicant
- MSTR027—“Information Advantage Wins Product of the Year Award for Knowledge Management,” Business Wire, Mar. 4, 1998. Available in Lexis, Nexis Library, ALLNWS file.Applicant
- MSTR028—Emigh, Jacqueline, “Information Builders, Inc. Launches WebFocus Suit,” Newbytes, Mar. 10, 1998. Available in Northern Light, http://www.northernlight.com, Doc. ID BS19980311010000172.Applicant
- MSTR029—Microstrategy: DSS Broadcaster—The Industry's First Information Broadcast Server, M2 Presswire, Mar. 20, 1998. Available in Dow Jones Interactive http://www.djinteractive.com.Applicant
- MSTR030—Microstrategy Introduces DSS Broadcaster—The Industry's First Information Broadcast Server, Mar. 23, 1998. http://strategy.com/newsandevent/New/Press/Release/1998/broadcaster.htm.Applicant
- MSTR031—Microstrategy Introduces DSS Broadcaster—The Industry's First Information Broadcast Server, Mar. 23, 1998. http://www.strategy.com/newsandevents/News/PressReleases/1998/broadcaster.htm.Applicant
- MSTR032—“MSNBC on the Internet Launches New Traffic Section; MSNBC.com and Sidewalk.com Team with TrafficStation for Production of Comprehensive Site for Drivers,” Financial News, Redmond, Wash., Apr. 15, 1998.Applicant
- MSTR033—Prospectus—4,000,000 Shares Microstrategy Class A Common Stock, Jun. 11, 1998.Applicant
- MSTR034—“System for Telephone Access to Internet Applications—Uses Dial Tones and/or Voice with Interactive Voice Response Unit to Pass Request to Processor that Converts Requests to Communication Protocol Command Set,” IBM, Patent No. RD 98412088. Jul. 20, 1998, Abstract.Applicant
- MSTR035—Relational OLAP Interface, Programmer's Reference and SDK Guide, Version 5.0, Aug. 1998.Applicant
- MSTR036—Data Warehouse Dossier, Fall 1998.Applicant
- MSTR037—“Microstrategy Announces Enhanced Version of DSS Web and DSS Server,” Oct. 26, 1998, http://www.strategy.com/NewsandEvents/news/pressreleases/1998/server5.5.htm.Applicant
- MSTR038—System Guide DSS Web Version 5.5, Feb. 1999.Applicant
- MSTR039—Developer Guide DSS Web Version 5.5, Feb. 1999.Applicant
- MSTR040—Media Output Book, v2.0, Feb. 16, 1999.Applicant
- MSTR041—Computer Telephony, from www.telecomlibrary.com—Sep. 9, 1999.Applicant
- MSTR042—Frequently Asked Questions About DSS Web, printed Feb. 23, 1999, http://www.strategy.com/products/Web/faq.htm.Applicant
- MSTR043—“Traffic Station Extends Service to Six New Markets in North America, Reaching its Goal of 20 Markets by the New Millennium,” Business Editors/Multimedia & Transportation Writers, Los Angeles, Dec. 23, 1999.Applicant
- MSTR044—Traffic Station Corporate Information, http://www.trafficstation.com/home/corporate.html, Jan. 10, 2001.Applicant
- MSTR045—Newswire, “Net Phones to Outsell Laptops by 2002”, Dec. 2, 1998, Dialog File #03635692.Applicant
- MSTR046—RCR Radio Communications Report, “Comverse Developing Unified Applications for GSM Smartphone Marketplace”, Feb. 23, 1998, V. 17, No. 8, p. 106, Dialog File #02078693.Applicant
- MSTR0047—America's Network, “Wireless Web Browsing: How Long Will Deployment Take? (There Will be 22 Mil Devices Other than PCs Accessing the Internet by 2000)”, Dec. 15, 1996, vol. 100, No. 24, p. 30+, Dialog File #01708089.Applicant
- MSTR048—Adali et al., “Query Caching and Optimization in Distributed Mediator Systems”, SIGMOD '96, Jun. 1996, Montreal, Canada, pp. 137-148.Applicant
- MSTR049—Alur et al., “Directory-Driven Information Delivery”, DataBase Associates Int'l, Jul. 1996, printed from http://web.archive.org on Jan. 7, 2002, 12 pages.Applicant
- MSTR050—Chawathe et al., “Representing and Querying Changes in Semistructured Data”, Proceedings of the 14th International Conference on Data Engineering, IEEE, Feb. 23-27, 1998, pp. 4-13.Applicant
- MSTR051—Codd et al., “Providing OLAP (On-line Analytical Processing) to User-Analysts; an IT Mandate”, San Jose, California, Codd and Date, 1993, 1 page.Applicant
- MSTR052—Flohr, “Using Web-Based Applications to Perform On-Line Analytical Processing Builds of the Strengths of Both Technologies”, OLAP by Web, Sep. 1997, 8 pages.Applicant
- MSTR053—Gesmann et al., “A Remote Cooperation System Supporting Interoperability in Heterogeneous Environments”, Proceedings of the Third International Workshop on Research Issued in Data Engineering, IEEE, Apr. 19-20, 1993, pp. 152-160.Applicant
- MSTR054—Hackathorn, “Solutions to Overworked Networks and Unruly Software Distribution are Just Part of P&S.”, Publish or Perish, Sep. 1997, 21 pages.Applicant
- MSTR055—Liscano et al., “Integrating Multi-Modal Messages across Heterogeneous Networks”, IEEE, 1997, pp. 45-53, Abstract.Applicant
- MSTR056—Liu et al., “Differential Evaluation of Continual Queries”, Proceedings of the 16th International Conference on Distributed Computing Systems, IEEE, May 27-30, 1996, pp. 458-465.Applicant
- MSTR057—Newing, “Relational Databases Are Not Suitable for Management Information Systems: And That's Official!”, Management Accounting, London, vol. 72, No. 8, Sep. 1994, 4 pages.Applicant
- MSTR058—Raden, “Teraforming the Data Warehouse”, Archer Decision Sciences, printed from http://www.archer-decision.com on Jan. 16, 2002, 13 pages.Applicant
- MSTR059—Schreier et al., Alert: An Architecture for Transforming a Passive DBMS into an Active DBMS, Proceedings of the 17th International Conference on Very Large Data Bases, Sep. 3-6, 1991, pp. 469-478.Applicant
- MSTR060—Schultz, “ADEPT—The Advanced Database Environment for Planning and Tracking”, Bell Labs Technical Journal, Jul.-Sep. 1998, pp. 3-9.Applicant
- MSTR061—Spofford, “Attack of the Killer APIs”, Intelligent Enterprise's Database Online Programming and Design, printed from http://www.dbpd.com on Dec. 21, 2001, 10 pages.Applicant
- MSTR062—Stonebraker et al., “On Rules, Procedures, Caching and Views in Data Base Systems”, Proceedings of the 1990 ACM SIGMOD International Conference on Management of Data, May 23-25, 1990, pp. 281-290.Applicant
- MSTR063—Terry et al., “Continuous Queries over Append-Only Databases”, Proceedings of the 1992 ACM SIGMOD International Conference on Management of Data, Jun. 2-5, 1992, pp. 321-330.Applicant
- MSTR064—Search Results from Internet Archive Wayback Machine, searched for http://www.infoadvan.com, printed from http://web.archive.org on Dec. 19, 2001, 40 pages.Applicant
- MSTR065—Search Results from Internet Archive Wayback Machine, searched for http://www.platinum.com, printed from http://web.archive.org on Dec. 21, 2001, 17 pages.Applicant
- MSTR066—ROLAP Case Studies, 30 pages (no earlier than Sep. 1997).Applicant
- MSTR067—“Fast and Flexible Access to Databases”, Byte, Aug. 1997, pp. 53-54.Applicant
- MSTR068—“Distributed Application Development with PowerBuilder 6.0”, Manning Publications Co., printed from http://www.manning.com on Jan. 15, 2002, 12 pages.Applicant
- MSTR069—“PowerBuilder 6.0 Questions & Answers”, Manning Publications Co., printed from http://www.manning.com on Jan. 15, 2002, 13 pages.Applicant
- MSTR070—“PowerBuilder 6.0 Questions & Answers”, Manning Publications Co., printed from http://www.manning.com on Jan. 17, 2002, 2 pages.Applicant
- MSTR071—Cheshire, “Product News—A Sea of Opportunity”, Intelligent Enterprise's Database Online Programming and Design, printed from http://www.dbpd.com on Jan. 17, 2002, 6 pages.Applicant
- MSTR072—“Information Advantage—Business Intelligence”, “Live Information Respository . . . ”, printed from http://www.infoadvan.com, on Dec. 19, 2001, 5 pages.Applicant
- MSTR073—“Objective Data Inc.—Computer Software Consultants”, Client List, printed from http://objectivedata.com/clients.htm on Jan. 15, 2002, 5 pages.Applicant
- MSTR074—“Online Analytical Processing”, printed from http://searchdatabase.techtarget.com on Jan. 18, 2002, 3 pages.Applicant
- MSTR075—“Seagate Crystal Reports 8”, printed from http://www.crystaluser.com on Dec. 28, 2001, 6 pages.Applicant
- MSTR076—“Andyne Delivers Personal OLAP with PaBLO 4.0”, Press Release, Mar. 31, 1997, Andyne Computing Limited, 5 pages.Applicant
- MSTR077—“Andyne Announces Support for Microsoft's OLE DB for OLAP”, Press Release, Sep. 10, 1997, Andyne Computing Limited 4 pages.Applicant
- MSTR078—“Andyne QMO—Manage Data Access”, Andyne Computing, printed from http://web.archive.org on Jan. 3, 2002, 5 pages.Applicant
- MSTR079—“The Andyne Vision—On the Road to the Integrated Solution”, Andyne Computing, printed from http://web.archive.org on Dec. 3, 2002, 11 pages.Applicant
- MSTR080—“Visual Information Access for Multidimensional Companies . . . ”, Andyne Corporate Profile, 2 pages, © 1996.Applicant
- MSTR081—“MicroStrategy Announces DSS Web 5.0; DSS Web Introduces the Web-Cast of Decision Support”, MicroStrategy, Jan. 5, 1998, printed Dec. 10, 2001, 2 pages.Applicant
- MSTR082—“MicroStrategy Introduces DSS Web Standard Edition; Web Interface Provides powerful, Easy-to-Use DSS Tool for Mainstream End-User Market”, MicroStrategy, Apr. 27, 1998, printed Dec. 10, 2001, 2 pages.Applicant
- MSTR083—“MicroStrategy Advantages: Proven Multi-Tier Architecture”, printed from http://web.archive.org, 4 pages, © 1995.Applicant
- MSTR084—“MicroStrategy ‘Consumerizes’ the Data Warehouse with Its New 4.0 Product Line”, Press Release, Jun. 24, 1996, MicroStrategy, printed from http://web.archive.org on Dec. 8, 2001, 7 pages.Applicant
- MSTR085—“MicroStrategy Announces DSS Server 3.0”, Press Release, Aug. 8, 1995, MicroStrategy, printed from http://web.archive.org on Dec. 8, 2001, 5 pages.Applicant
- MSTR086—“MicroStrategy Announces True Relational OLAP Product Line”, Press Release, Aug. 8, 1995, MicroStrategy, printed from http://web.archive.org on Dec. 8, 2001, 5 pages.Applicant
- MSTR087—“DSS Administrator Features Overview”, MicroStrategy, No. 05090297, 2 pages, © 1996, 1997.Applicant
- MSTR088—“DSS Agent Features Overview”, MicroStrategy, No. 05100896, 2 pages, © 1996.Applicant
- MSTR089—“DSS Server Features Overview”, MicroStrategy, No. 05140896, 2 pages, © 1996.Applicant
- MSTR090—“Relational OLAP Interface”, DSS Agent, MicroStrategy, 22 pages and 20 pages (no earlier than 1996).Applicant
- MSTR091—“Relational OLAP Interface for the Web”, MicroStrategy DSS Web Brochure, 4 pages, © 1995.Applicant
- MSTR092—“Data Warehouse and DSS Management Tools”, DSS Administrator, MicroStrategy, 16 pages, © 1996, 1997.Applicant
- MSTR093—“OLE API for Custom Application Development”, DSS Objects, MicroStrategy, 4 pages, © 1996.Applicant
- MSTR094—“Arbor Software OLAP Products”, Brochure, Arbor Software, 12 pages, © 1998.Applicant
- MSTR095—“InfoTrac OneFile”, Database Programming & Design, vol. 11, No. 7, Jul. 1998, 12 pages.Applicant
- MSTR096—“Andyne GQL Version 3.3.2 Available Jul. 17th ; Featuring Multi-Pass Reporting, Time Governors and Scripting”, Business Wire, Jun. 26, 1995, Andyne Computing Limited, 4 pages.Applicant
- MSTR097—“MicroStrategy Announces DSS Server 3.0; Three-Tier Architecture Results in Exceptional Performance and Scalability for DSS Applications”, Business Wire, Aug. 8, 1995, MicroStrategy, 3 pages.Applicant
- MSTR098—“Information Advantage Ships DecisionSuite 3.0 Business Analysis Applications for Data Warehouses”, Business Wire, Nov. 9, 1995, 3 pages.Applicant
- MSTR099—“Information Advantage Announces WebOLAP; First Structured Content analysis Server for the World Wide Web”, Business Wire, Feb. 5, 1996, 3 pages.Applicant
- MSTR100—“Andyne Delivers Second Stage of the Andyne Integrated Solution”, Canada NewsWire, May 13, 1996, 3 pages.Applicant
- MSTR101—“Andyne Computing Ltd is Shipping Version 3.3.2 of Its GQL Decision Support System”, CommunicationsWeek, No. 566, Jul. 17, 1995, p. 16.Applicant
- MSTR102—“Andyne Computing Introduces New Query Management Option as Companion Product to Andyne's GQL Product”, CommunicationsWeek, No. 592, Jan. 15, 1996, p. 16.Applicant
- MSTR103—“Andyne Hopes to Benefit from Current Data Warehousing Hype with GQL Query Language”, Computergram International, No. 2798, Nov. 22, 1995, 1 page.Applicant
- MSTR104—“Andyne's GQL Makes It Easier—New Version of Reporting, Analysis Tool Unveiled”, Computer Reseller News, No. 685, May 27, 1996, p. 79.Applicant
- MSTR105—“The Right Tools”, Computer Weekly, Aug. 29, 1996, 4 pages.Applicant
- MSTR106—“4 OLAP Tools; The Common Thread is that OLAP Tools Drain Too Much Time and Energy Before You Get What You Need”, Computerworld, Dec. 2, 1996, 4 pages.Applicant
- MSTR107—“GQL”, Data Management Review (DM Review), vol. 6, No. 5, May 1996, p. 47.Applicant
- MSTR108—“DB2 Today Newsletter”, Jun. 1999, 2 pages.Applicant
- MSTR109—“GQL 3.2”, DBMS, vol. 8, No. 1, Jan. 1995, 2 pages.Applicant
- MSTR110—“Everything's Coming Up Warehouse”, DBMS, Oct. 1, 1995, 3 pages.Applicant
- MSTR111—“Query, Reporting, and Analysis Tools”, DBMS, vol. 9, No. 6, Jun. 15, 1996, 14 pages.Applicant
- MSTR112—Brooks, “MCI Leverages Data Warehouse Technology to Strengthen its Marketing Campaigns”, DBMS, Dec. 1996, 7 pages.Applicant
- MSTR113—Dobson, “Data Binding in Dynamic HTML”, DBMS, Mar. 1998, 12 pages.Applicant
- MSTR114—Dodd, “Native is as Native Does”, HP Professional, vol. 12, No. 12, Feb. 1998, 1 page.Applicant
- MSTR115—“Banking's New Payoff: Speed”, InformationWeek, Jan. 17, 1994, 3 pages.Applicant
- MSTR116—“Nailing Down More Query Tools”, InformationWeek, vol. 523, Apr. 17, 1995, 7 pages.Applicant
- MSTR117—Raden, “Data, Data Everywhere”, Information Week, Oct. 30, 1995, pp. 60-65.Applicant
- MSTR118—“Back-to-Back Upgrades—Vendors Introduce Reporting, Query Tools”, InformationWeek, No. 598, Sep. 23, 1996, 1 page.Applicant
- MSTR119—“Desktop OLAP Tools—If the Tool Fits, Use it—Online Analytical Processing Tools Offer Ease of Use for Data Retrieval and Analysis with Minimal User Training”, InformationWeek, No. 605, Nov. 11, 1996, 3 pages.Applicant
- MSTR120—“Pilot Gets Serious About OLAP”, Information Week, Jul. 20, 1998, pp. 55-59.Applicant
- MSTR121—“Oracle Announces Next Generation Oracle Express Server 6.0”, M2 Presswire, Aug. 7, 1996, 5 pages.Applicant
- MSTR122—“Andyne Updates GQL”, Newsbytes, Jul. 12, 1994, 1 page.Applicant
- MSTR123—“Andyne Computing Has Released Version 3.2.2 of Its GQL Query Software for Macintosh, Windows and Unix Platforms”, Newsbytes News Network, Jul. 12, 1994, 4 pages.Applicant
- MSTR124—“Data Access is Key to Warehousing Success”, Open Systems Today, Oct. 3, 1994, 2 pages.Applicant
- MSTR125—Phillips, “Crystal Eyes OLAP Engine”, PC Week, vol. 13, No. 4, Jan. 29, 1996, 3 pages.Applicant
- MSTR126—Dyck, “New Report Writer Spruces Up GQL”, PC Week, vol. 14, No. 3, Jan. 20, 1997, 1 page.Applicant
- MSTR127—“New Decision Suite 3.0 From Information Advantage Raises the Bar for Enterprise Decision Support”, Newswire, Aug. 8, 1995, 3 pages.Applicant
- MSTR128—“Andyne's Intranet Strategy Brings DSS to the Web; Company Aims to Dramatically Broaden Scope of Reporting, Online Analysis”, PR Newswire, Sep. 18, 1996, 11 pages.Applicant
- MSTR129—“NCR Adds OLAP Services to Extend and Expand Decision Support Capabilities of Teradata Database”, PR Newswire, May 28, 1998, 3 pages.Applicant
- MSTR130—“DecisionSuite 3.5”, SoftBase, Sep. 12, 1996, 2 pages.Applicant
- MSTR131—“IBM Acquires ITI's KnowledgeX Technology to Enhance Business Intelligence Solutions”, Software News, Jul. 23, 1998, 1 page.Applicant
- MSTR132—“Microstrategy Talks Crystal Balls”, Software Futures, Apr. 1, 1997, 4 pages.Applicant
- MSTR133—“Document Agent Administrator's Guide”, Revision 3, BusinessObjects, Version 4.0, pp. 1-29, © 1996.Applicant
- MSTR134—“Document Agent Server Administrator's Guide”, Revision 4, BusinessObjects, Version 4.1, pp. 1-33, © 1996, 1997.Applicant
- MSTR135—“Getting Started with Reports”, Revision 2, BusinessObjects, Version 4.0, pp. 1-53, © 1996.Applicant
- MSTR136—“Getting Started with Reports”, Revision 3, BusinessObjects, Version 4.1, pp. 1-53, © 1997.Applicant
- MSTR137—“User's Guide”, Revision 3, BusinessObjects, Version 4.0, pp. 1-251, © 1996.Applicant
- MSTR138—“User's Guide”, Revision 4, BusinessObjects, Version 4.1, pp. 1-287, © 1997.Applicant
- MSTR139—“United EasyUpdate”, United Airlines, printed from http://www.ual.com/page/article/1,1360,1974,00.html, printed Nov. 30, 2002, 4 pages.Applicant
- MSTR140—General Magic, Inc. website, printed from http://www.genmagic.com, printed Nov. 30, 2002, 16 pages.Applicant
- MSTR142—Lehner, Wolfgang, “Modeling Large Scale OLAP Scenarios”, University of Erlangen-Nuremberg, Dept. of Database Systems, Germany, 1998, pp. 1-15.Applicant
- MSTR143—“Sybase Announces General Availability of Warehouse Studio”, PR Newswire, New York, Jun. 23, 1998, two pages.Applicant
- MSTR144—Schmandt, Chris, “Phoneshell: the Telephone as Computer Terminal”, Proceedings of ACM Multimedia '93, New York, Aug. 1993, pp. 373-382.Applicant
- MSTR145—Roy, Deb. K., et al., “NewsComm: A Hand-Held Interface for Interactive Access to Structured Audio”, CHI '96 Conference Proceedings, Vancouver, Canada, Apr. 1996, pp. 173-180.Applicant
- MSTR146—Roy, Deb Kumar, “NewsComm: A Hand-Held Device for Interactive Access to Structured Audio”, Masters Thesis, MIT Media Laboratory, 1995.Applicant
- MSTR147—Emnett, Keith, et al., “Synthetic News Radio”, IBM Systems Journal, vol. 39, Nos. 3 & 4, 2000, pp. 646-659.Applicant
- MSTR148—MicroStrategy: “MicroStrategy Announces the General Availability of DSS Broadcaster”, Business Wire, Aug. 11, 1998, Proquest #32759243.Applicant
- MSTR152—Spyglass Prism Concepts and Applications, 1997, Spyglass, Inc., pp. 1-8.Applicant
- MSTR153—Spyglass White Paper; Spyglass Product Strategy: Making Devices work with the Web, 1997, Spyglass, Inc., pp. 1-9.Applicant
- MSTR154—Kane, Margaret, “Microsoft Acquires Hotmail”, ZDNet News, Dec. 30, 1997, 2 pages.Applicant
- MSTR155—Emnett, Keith, et al., “Synthetic Audio Newscast”, The MIT Media Laboratory, alleged date: Dec. 1998, pp. 1-2.Applicant
- MSTR156—KylÅnpÅÅ, Markku, “Mobile Multimedia White Paper”, http://www.vtt.fi/tte/projects/mobmulti/mobmulti.html, last modified Oct. 12, 1998, 8 pages.Applicant
- MSTR157—Ewen, Edward F., et al., “Data Warehousing in an Integrated Health System; Building the Business Case”, Proceedings of the ACM First International Workshop on Data Warehousing and OLAP, 1998, pp. 47-53.Applicant
- MSTR158—Zaiane, Osmar R., et al., “Discovering Web Access Patterns and Trends by Applying OLAP and Data Mining Technology on Web Logs”, IEEE International Forum on Research and Technology Advances in Digital Libraries, date unavailable, pp. 19-29.Applicant
- MSTR159—Kurz, Andreas, et al., “Data Warehousing within Intranet: Prototype of a Web-Based Executive Information System”, Proceedings of the 8th International Workshop on Database and Expert Systems Applications, 1997, pp. 627-632.Applicant
- MSTR160—Lehn, Rémi, et al., “Data Warehousing Tool's Architecture: From Multidimensional Analysis to Data Mining”, IEEE Database and Expert Systems Applications, date unavailable, pp. 636-643.Applicant
- MSTR167—Wikipedia, definition of “Push Technology”, printed from http://en.wikipedia.org/wiki/Push—technology, printed on Jan. 17, 2006, 1 page.Applicant
- MSTR168—“Travelocity.com-airline tickets, hotel accommodations and car reservation online” [online], Feb. 9, 1999 [retrieved on Jan. 10, 2006]. Retrieved from the Internet: <URL:http://web.archive.org/web/19990209191411/www2.travelocity.com/ttools/freqtrav.html.Applicant
- MSTR169—Elkins, Steven B., “Open OLAP”, DBMS, Apr. 1998, Available at http://dbmsmag.com/9804d14.html, 7 pages.Applicant
- MSTR170—Chaudhuri, Surajit, et al., “An Overview of Data Warehousing and OLAP Technology”, ACM SIGMOD Records, vol. 26, Issue 1, Mar. 1997, pp. 65-74, 21 pages.Applicant
- MSTR171—“Southwest Airlines Home Gate” [online], Apr. 16, 1999 [retrieved on Oct. 3, 2006]. Retrieved from the Internet: <URL:http://web.archive.org/web/19990418061835/southwest.com/luvhome.html>, 19 pages.Applicant