Voice commerce

Information

  • Patent Grant
  • 9626703
  • Patent Number
    9,626,703
  • Date Filed
    Tuesday, September 15, 2015
    9 years ago
  • Date Issued
    Tuesday, April 18, 2017
    7 years ago
Abstract
In certain implementations, a system for facilitating voice commerce is provided. A user input comprising a natural language utterance related to a product or service to be purchased may be received. A first product or service that is to be purchased may be determined based on the utterance. First payment information that is to be used to purchase the first product or service may be obtained. First shipping information that is to be used to deliver the first product or service may be obtained. A purchase transaction for the first product or service may completed based on the first payment information and the first shipping information without further user input, after the receipt of utterance, that identifies a product or service type or a product or service, seller information, payment information, shipping information, or other information related to purchasing the first product or service.
Description
FIELD OF THE INVENTION

The invention relates to systems and methods for providing voice commerce. More particularly, the invention relates to systems and methods for preparing and/or completing checkout of product or service purchases via a single utterance.


BACKGROUND OF THE INVENTION

Mobile electronic devices have emerged to become nearly ubiquitous in the everyday lives of many people. One of the reasons for this increased use is the convenience of performing tasks with a mobile electronic device. One task that has seen significant growth is online shopping. During an online shopping session, a user browses a website to locate a product or service for purchase. After the product or service has been located, the user makes payment through the mobile electronic device and has the purchased product or service delivered.


One difficulty in online shopping via a mobile electronic device is that the user must search a website in order to locate a product or service to be purchased and fill out numerous payment and shipping forms to complete checkout (or a purchase transaction). Mobile electronic devices typically contain small screens and keyboards, making it hard for the user to search for the product or service to purchase and input payment and shipping information. While some online shopping applications assist the user in filling out payment and shipping forms, the foregoing applications are often limited to the amount of information that can be provided. Further, some online shopping applications include a “one-click” purchase option. However, this still requires the user to browse the website to locate product or services which they wish to purchase. These and other drawbacks exist.


SUMMARY OF THE INVENTION

The invention relates to systems and methods for preparing and/or completing checkout of product or service purchases via a single utterance. More particularly, the systems and methods may process a single utterance of a user to determine a product or service that is to be purchased, payment information that is to be used to pay for the product or service, shipping information that is to be used to deliver the product or service, and/or other information that is thereafter utilized to prepare and/or complete a purchase transaction for the product or service. In some implementations, the preparation and/or completion of the purchase transaction may be performed without further user input after receipt of the utterance (with which the determination of the product or service, the payment information, or shipping information is based).


In an implementation, the system may receive and process a user input comprising a natural language utterance to determine a product or service to be purchased on behalf of a user. As an example, one or more words associated with the natural language utterance may be indicative of a product or service type, product name, seller name, etc., which can be used to determine the product or service that is to be purchased. Without further user input after the receipt of the user input (or the natural language utterance), the system may obtain payment information that is to be used to pay for the product or service, shipping information that is to be used to deliver the product or service, or other information that is to be used to complete a purchase transaction for the product or service.


In an implementation, upon receipt of a natural language utterance of a user, and without further user input after the receipt of the utterance, the system may process the utterance to determine a product or service, and complete a purchase transaction for the product or service based on payment information associated with the user, shipping information indicating who, where, when, and/or how the product or service is to be delivered, or other information. In a further implementation, after the purchase transaction is completed, the user may be provided with an option to modify one or more aspects related to the product or service purchase (e.g., modify payment information, shipping information, seller from which the product or service is purchased, etc.). As an example, the initial product or service purchase may be cancelled (and result in refund of the payment provided for the completed purchase transaction) in response to the user's modification, and a new purchase transaction may be initiated in accordance with the user's modification. Of course, in some implementations, such after-transaction-completion modifications may be limited to avoid fraud or other issues (e.g., limited to a predefined time period after the transaction completion, limited to certain types of modifications, etc.). In this way, users can experience the convenience of a purchase transaction being completed with reduced actions (e.g., single utterance) without fear of inaccuracies that might be associated with the purchase transaction.


In an implementation, upon receipt of a natural language utterance of a user, and without further user input after the receipt of the utterance, the system may process the utterance to determine a product or service to be purchased, and present a request for user confirmation (or user approval) of the product or service to be purchased, payment information that is to be used to pay for the product or service, shipping information that is to be used to deliver the product or service, or other information that is to be used to complete a purchase transaction for the product or service. Upon receipt of the requested confirmation from the user, a purchase transaction for the product or service may be completed without further user input after the receipt of the requested confirmation. As an example, after the user has provided the utterance, the user may be presented with a prompt that: (i) identifies the product or service, the cost(s) associated with the purchase/delivery of the product or service, the payment information, and the shipping information; and (ii) solicits the user's approval to complete checkout of the product or service using a particular payment method (specified by the payment information to pay for the associated cost(s)), a particular shipping method (specified by the shipping information), along with a name and address (specified by the shipping information) to which the product or service is to be delivered. The user may respond by providing a subsequent natural language utterance. If it is determined (upon receiving and processing the subsequent utterance) that the user provided his/her approval, checkout of the product or service purchase may be completed (e.g., without further user input after receipt of the utterance other than the subsequent utterance). In this way, the confirmation may be used to ensure that that the information utilized to complete checkout of the product or service checkout is accurate and acceptable to the user.


Various other aspects of the invention will be apparent through the detailed description of the invention and the drawings attached hereto. It is also to be understood that both the foregoing general description and the following detailed description are exemplary and not restrictive of the scope of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. In addition, as used in the specification and the claims, the term “or” means “and/or” unless the context clearly dictates otherwise.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a system for providing voice commerce, according to an implementation of the invention.



FIG. 2 illustrates a system for facilitating natural language processing, according to an implementation of the invention.



FIG. 3 illustrates a flow diagram of a process for providing voice commerce, according to an implementation of the invention.



FIG. 4 illustrates a flow diagram of another process for providing voice commerce, according to an implementation of the invention.



FIG. 5 illustrates a screenshot of a user interface which facilitates voice commerce, according to an implementation of the invention.



FIGS. 6A and 6B illustrate screenshots of a user interface which facilitates voice commerce, according to an implementation of the invention.



FIGS. 7A and 7B illustrate screenshots of a user interface which facilitates management of profile information, according to an implementation of the invention.





DETAILED DESCRIPTION OF THE INVENTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the implementations of the invention. It will be appreciated, however, by those having skill in the art that the implementations of the invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the implementations of the invention.



FIG. 1 illustrates a system 100 for providing voice commerce to a user, according to an implementation of the invention. In an implementation, the system 100 may prepare and/or complete checkout of product or service purchases related to one or more user inputs. The user inputs may comprise an auditory input (e.g., received via a microphone), a visual input (e.g., received via a camera), a tactile input (e.g., received via a touch sensor device), a keyboard input, a mouse input, or other user input that is recognizable by the system 100. As an example, a natural language utterance may be received from a user and processed to prepare and/or complete checkout of product or service purchases.


In an implementation, system 100 may receive and process a single utterance of a user to determine a product or service that is to be purchased, payment information that is to be used to pay for the product or service, shipping information that is to be used to deliver the product or service, and/or other information that is thereafter utilized to prepare and/or complete the purchase of the product or service.


In one use case, if the user input is a natural language utterance spoken by a user, the natural language utterance may be processed by a speech recognition engine to recognize one or more words of the natural language utterance. The recognized words may then be processed, along with context information associated with the user, by a natural language processing engine to determine one or more products or services and/or other information (e.g., payment information, shipping information, seller information, associated cost information, etc.) that can be used to prepare and/or complete one or more purchase transactions for the products or services. Upon determination of such information, for example, the natural language processing engine may provide the information to one or more applications that then utilize the information to prepare and/or complete the purchase transactions.


As an example, when a user speaks the utterance “Send flowers to my mother,” the user's mother may be identified as the recipient of a product that the user intends to purchase (e.g., based on the words “send,” “my”, and “mother”), and flowers may be identified as the type of product that the user intends to have purchased and delivered to the user's mother (e.g., based on the words “send” and “flowers”). Without necessarily receiving any further input from the user, the system 100 may automatically determine the name and address of the user's mother, a payment method associated with the user, a seller from which flowers are to be purchased, a particular item (e.g., a particular flower purchase order) to be purchased from the seller, and the costs associated with the purchase/delivery of the purchase item. Such information may then be utilized to initiate and/or complete a purchase transaction for the purchase item. The name and address of the user's mother may, for example, be determined by querying the user's profile information, the user's address book(s) or contact list(s), the user's social network(s), one or more people search databases, etc. The payment method associated with the user may be determined by querying the user's profile information. The seller from which flowers are to be purchased or the purchase item from the seller may be determined based on a set of preferred merchants indicated by a service provider (e.g., a company associated with the system 100), preference information associated with the user that identifies merchants approved by the user (e.g., the user's profile information may identify a predefined set of merchants from which the user has approved the system 100 to purchase products or services on behalf of the user), or similar criteria. For example, system 100 may determine which flowers are to be purchased from the merchant's range of offerings based on the user's profile information including the types of items a user likes, qualities of items the user likes, the categories of items a user likes, minimum item rating requirements, item pricing requirements, user location and context information, shipping requirements, etc. The associated costs may be determined based on information regarding the seller, the purchase item, the mother's address, the delivery method (e.g., different fees associated with one-day shipping, two-day shipping, etc.), the payment method (e.g., different fees associated with different payment methods), or other information.


It should be noted that while, in some implementations, a purchase transaction for a product or service may be completed without further user input after receiving a natural language utterance (from which the product or service is determined), user input may be solicited (or received unsolicited) from a user in other implementations to determine payment information, shipping information, seller information, or other information that is to be used to complete the purchase transaction.


In an implementation, upon receipt of a natural language utterance of a user, and without further user input after the receipt of the utterance, the system 100 may process the utterance to determine a product or service to be purchased, and present (e.g., via a graphical user interface, via an auditory user interface, etc.) a request for user confirmation (or user approval) of the product or service, shipping information that is to be used to deliver the product or service, payment information that is to be used to pay for the product or service, and/or other information to ensure that such information is correct and accepted by the user for use with purchasing the product or service. Upon receipt of the requested confirmation from the user, a purchase transaction for the product or service may be completed without further user input after the receipt of the requested confirmation.


As an example, with respect to the above “Send flowers to my mother” utterance scenario, the following information may be presented to the user as part of the user confirmation request: (i) the name and address of the user's mother; (ii) a payment method associated with the user; (iii) a seller from which flowers are to be purchased; (iv) a particular item (e.g., a particular flower purchase order) to be purchased from the seller; and (v) the costs associated with the purchase/delivery of the purchase item. As a further example, the user may provide any of the following utterances—“That's fine,” “The information is correct,” “Go ahead and purchase the flowers,” “Order the flowers,” or other utterance—to indicate the user's confirmation to complete the purchase transaction. As such, based on the confirmation, the purchase transaction for the purchase item (e.g., a particular flower purchase order) may be completed (e.g., without further user input after the receipt of the utterance “Send flowers to my mother” other than the confirmation utterance).


In an implementation, user profile information (e.g., name, payment information, shipping information, preferences, etc.) may be pre-stored so that the user profile information may be utilized by system 100 for preparing and/or completing checkout of product or service purchases. In an implementation, defaults associated with the user profile information, such as default payment information, default shipping information, etc., may be automatically or manually pre-set for preparing and/or completing checkout of product or service purchases.


In an implementation, preferred sellers, brands, style, size, or other parameters related to products or services may be automatically or manually pre-set as profile information. As an example, preferred sellers from which products or services are to be purchased and preferred brands of such products or services may be automatically pre-set by the system (e.g., pre-set to system preferred sellers and brands) until the preferences are manually modified by the user. The preferred store, brand, style, size, or other parameters may be obtained (e.g., in response to a natural language utterance indicating a product or service without further user input after the receipt of the utterance) to prepare and/or complete checkout of a product or service purchase unless the utterance (or other information) specifies otherwise. In another implementation, the profile information may include information relating to the general likes or dislikes of the user utilized to select the product or service to be purchased including the types of items a user likes, qualities of items the user likes, the categories of items a user likes, minimum item rating requirements, item pricing requirements, user location and context information, shipping requirements, etc.


In an implementation, preparation and/or completion of checkout of product or service purchases may be limited to certain categories of products or services (e.g., no automobiles), a particular price range (e.g., no more than $100), etc., to reduce the number or severity of purchases related to fraud. The categories of product or services and/or the price ranges may, for instance, be automatically or manually pre-set (e.g., automatically preset by the system, manually pre-set by the user).


Other uses of system 100 are described herein and still others will be apparent to those having skill in the art. Having described a high level overview of some of the system functions, attention will now be turned to various system components that facilitate these and other functions.


System Components


System 100 may include a computer system 104, one or more databases 132, one or more remote information sources 142, 144, 164, and/or other components.


To facilitate these and other functions, computer system 104 may include one or more computing devices 110. Each computing device 110 may include one or more processors 112, one or more storage devices 114, and/or other components.


Processor(s) 112 may be programmed by one or more computer program instructions, which may be stored in storage device(s) 114. The one or more computer program instructions may include, without limitation, voice commerce application 120. Voice commerce application 120 may itself include different sets of instructions that each program the processor(s) 112 (and therefore computer system 104) to perform one or more operations described herein. For example, voice commerce application 120 may include user input processing instructions 122, transaction preparation instructions 124, checkout management instructions 126, profile management instructions 128, user interface instructions 129, and/or other instructions 130 that program computer system 104. Other applications may, of course, include one or more of the instructions 120-130 to perform one or more operations as described herein. As used herein, for convenience, the various instructions will be described as performing an operation, when, in fact, the various instructions program computer system 104 to perform the operation.


In some implementations, a given user device 160 may comprise a given computer device 110. As such, the given user device 160 may comprise processor(s) 112 that are programmed with one or more computer program instructions, such as voice commerce instructions 120, user input processing instructions 122, transaction preparation instructions 124, checkout management instructions 126, profile management instructions 128, user interface instructions 129, and/or other instructions 130.


As used hereinafter, for convenience, the foregoing instructions will be described as performing an operation, when, in fact, the various instructions may program processor(s) 112 (and thereafter computer system 104) to perform the operation.


Registering User Information and Providing Voice Commerce


In an implementation, voice commerce application 120 may register a user to use the system. For example, during registration of a user, voice commerce application 120 may obtain profile information of the user that includes user settings. Information obtained during registration (or registration information) may include, for example, user identification information, payment information, shipping information, user preferences, and/or other information. The registration information may also include preferred sellers, brands, style, size, or other parameters related to products or services as well as limits on the purchase of particular product and service categories and particular price ranges for products or services. In another implementation, the registration information may also include limitations of certain categories of products or services to be purchased and/or particular price ranges of the products or services to be purchased. The registration information may be stored as profile information associated with the user in one or more databases, such as a database 132.


In an implementation, the voice commerce application 120 may process one or more user inputs to prepare and/or complete checkout of product or service purchases related to the one or more user inputs. The user inputs may comprise an auditory input (e.g., received via a microphone), a visual input (e.g., received via a camera), a tactile input (e.g., received via a touch sensor device), an olfactory input, a gustatory input, a keyboard input, a mouse input, or other user input. As an example, a natural language utterance, a natural language gesture, or other natural language user input may be received from a user, and processed to determine the meaning of the user input (and corresponding actions, if any, to be taken) with respect to preparation and completion of a purchase transaction. It should be noted that while, in some implementations, the receipt of a natural language utterance may trigger preparation and/or completion of a purchase transaction with further user input after the receipt of the utterance, the receipt of a natural language input of another type (e.g., gestures or other non-verbal communication) may, in other implementations, trigger preparation and/or completion of a purchase transaction with further user input after the receipt of the input of the other type. As such, to the extent possible, one or more operations described herein as based on a natural language utterance may, in other implementations, instead be based on a natural language input of another type.


The voice commerce application 120 may utilize instructions associated with one or more speech recognition engines, one or more natural language processing engines, or other components for processing user inputs to determine user requests related to the user inputs. For example, voice commerce application 120 may process a single utterance of a user to determine a product or service that is to be purchased, payment information that is to be used to pay for the product or service, shipping information that is to be used to deliver the product or service, and/or other information that is thereafter utilized to prepare and/or complete the purchase of the product or service.


In an implementation, voice commerce application 120 may process a user input (e.g., a natural language utterance) to determine one or more words associated with the user input, and initiate one or more user requests (e.g., queries, commands, etc.) based on the determined words, context information associated with the user (e.g., a current location of the user, the time at which the user spoke the utterance, a product or service recently discussed by the user, or other context), user profile information, or other information. As an example, a user may speak the utterance “Order a pizza for delivery,” and the voice commerce application 120 may interpret the utterance and determine that the user's intent is to purchase a pizza for delivery to the user. In one use case, without further user input after receiving the utterance, the voice commerce application 120 may initiate and complete a purchase transaction for the pizza to be delivered. If, for instance, the voice commerce application 120 determines that the user is currently at home, it may complete a purchase transaction with a pizza restaurant from which the user has previously ordered pizza to have the previously ordered pizza delivered to the user's house.


In an implementation, voice commerce application 120 may utilize a user input (e.g., a natural language utterance) to determine a product or service that is to be purchased by searching one or more databases associated with one or more sellers (e.g., partners, third party retailers, service providers, etc.). Results obtained from the search may include one or more products and/or services related to the user input. Each set of results may be individually grouped according to its source or product/service category. The voice commerce application 120 may automatically select the product/service to be purchased from the set of results. As an example, a single utterance may automatically result in the selection of a seller (e.g., a third party retailer) and the selection of a product related to the utterance that is available for purchase via the seller.


In an implementation, the voice commerce application 120 may prepare and/or complete checkout of a product or service purchase related to one or more user inputs. The voice commerce application 120 may determine payment information that is to be used to pay for the product or service, shipping information that is to be used to deliver the product or service, and/or other information that is thereafter utilized to prepare and/or complete the purchase of the product or service. In one implementation, the voice commerce application 120 may automatically complete the checkout of the product or service purchase related to the one or more user inputs. As an example, a single utterance from the user may result in the preparation and/or completion of the checkout of the product or service without further input from the user. In another implementation, the voice commerce application 120 may provide a request for confirmation of the determined product or service, shipping information, payment information, and/or other information to the user to solicit a confirmation from the user to complete the checkout of the product or service purchase.


In an implementation, the voice commerce application 120 may utilize user profile information to prepare and/or complete checkout of product or service purchases via a user input. In an implementation, the voice commerce application 120 may utilize defaults associated with the user profile information, such as default payment information, default shipping information, etc., for preparing and/or completing checkout of product or service purchases. In another implementation, the voice commerce application 120 may utilize product and/or service preferences including preferred sellers, brands, style, size, or other parameters related to products or services for preparing and/or completing checkout of product or service purchases. In another embodiment, the voice commerce application 120 may limit checkout of product or service purchases to certain categories of products or services, a particular price range, etc., to reduce the number or severity of purchases related to fraud. In another implementation, the profile information may determine a product or service to be purchased based from profile information relating to the general likes or dislikes of the user including the types of items a user likes, qualities of items the user likes, the categories of items a user likes, minimum item rating requirements, item pricing requirements, user location and context information, shipping requirements, etc.


Having described high level functions and operations of voice commerce application 120, attention will now be turned to particular functions and operations of voice commerce application 120 as illustrated through its various instructions. The various instructions (e.g., user input processing instructions 122, transaction preparation instructions 124, checkout management instructions 126, profile management instructions 128, user interface instructions 129, and/or other instructions 130) of voice commerce application 120 are described individually as discreet sets of instructions by way of illustration and not limitation, as two or more of the instructions may be combined.


User Input Processing


In an implementation, the user input processing instructions 122 may process one or more user inputs of a user to prepare and/or complete checkout of product or service purchases related to the one or more user inputs. The user inputs may comprise an auditory input (e.g., received via a microphone), a visual input (e.g., received via a camera), a tactile input (e.g., received via a touch sensor device), a keyboard input, a mouse input, or other user input. As described herein elsewhere, user input processing instructions 122 may comprise instructions associated with one or more speech recognition engines (e.g., speech recognition engine(s) 220 of FIG. 2), one or more natural language processing engines (e.g., natural language processing engine(s) 230 of FIG. 2), or other components for processing user inputs to determine user requests related to the user inputs. For example, user input processing instructions 122 may process a natural language utterance of a user to determine a product or service that is to be purchased, payment information that is to be used to pay for the product or service, shipping information that is to be used to deliver the product or service, and/or other information that is thereafter utilized to prepare and/or complete the purchase of the product or service.


In one use case, if the user input is a natural language utterance spoken by a user, the natural language utterance may be processed by a speech recognition engine to recognize one or more words of the natural language utterance. The recognized words may then be processed, along with context information associated with the user, by a natural language processing engine to determine one or more products or services and/or other information (e.g., payment information, shipping information, seller information, associated cost information, etc.) that can be used to prepare and/or complete checkout of product or service purchases when the user provided the natural language utterance.


In an implementation, the user input processing instructions 122 may utilize one or more previous user inputs (e.g., related to a product or service) in processing a particular user input to determine one or more products or services and/or other information (e.g., payment information, shipping information, seller information, associated cost information, etc.) that can be used to prepare and/or complete one or more checkout of product or service purchases.


As an example, a first user input (that occurs prior to a second user input) may be indicative of a user's intent to make a purchase (e.g., without necessarily identifying a product or service type or a product or service), and the second user input may be indicative of a particular product or service type and/or a particular product or service (e.g., without necessarily being indicative of the user's intent to make a purchase). In one use case, for example, a user may provide the utterance “I'm looking to buy something” as the first user input, after which an automated personal assistant (of a related application) may ask the user what the user would like to buy. The user may respond with the second user input by saying “Flowers for my mom.” The word “buy” may be recognized when speech recognition is performed on the first user input, and the word “flowers” may be recognized when speech recognition is performed on the second user input. Further processing on the word “buy” may indicate the user's intent to purchase, and further processing on the word “flowers” may indicate the particular product type of a product that the user would like to purchase.


As another example, a first user input (that occurs prior to a second user input) may be indicative of a particular product or service type and/or a particular product or service (e.g., without necessarily being indicative of the user's intent to make a purchase), and the second user input may be indicative of a user's intent to make a purchase (e.g., without necessarily identifying a product or service type or a product or service). In one scenario, for example, the user may provide the utterance “Those are beautiful flowers” while viewing photographs on a friend's social networking page. Subsequently, the user may provide the utterance “I'd like to buy some.” The words “those” and “flowers” may be recognized when speech recognition is performed on the first user input, and the words “buy” and some” may be recognized when speech recognition is performed on the second user input. Further processing on the words “those” and “flowers” may indicate the flowers in the photographs that the user viewed on the friend's social networking page, and further processing on the words “buy” and “some” may indicate the user's intent to make a purchase.



FIG. 2 illustrates a system 200 for facilitating natural language processing, according to an implementation of the invention. As shown in FIG. 2, system 200 may comprise input device(s) 210, speech recognition engine(s) 220, natural language processing engine(s) 230, application(s) 240, output device(s) 250, database(s) 132, or other components.


In an implementation, one or more components of system 200 may comprise one or more computer program instructions of FIG. 1 and/or processor(s) 112 programmed with the computer program instructions of FIG. 1. As an example, speech recognition engine(s) 220 and/or natural language processing engine(s) 230 may comprise user input processing instructions 122, transaction preparation instructions 124, checkout management instructions 126, profile management instructions 128, or other instructions.


Input device(s) 210 may comprise an auditory input device (e.g., microphone), a keyboard, a mouse, or other input devices. Input received at input device(s) 210 may be provided to speech recognition engine(s) 220 and/or natural language processing engine(s) 230.


Speech recognition engine(s) 220 may process one or more inputs received from input device(s) 210 to recognize one or more words represented by the received inputs. As an example, with respect to auditory input, speech recognition engine(s) 220 may process an audio stream captured by an auditory input device to isolate segments of sound of the audio stream. The sound segments (or a representation of the sound segments) are then processed with one or more speech models (e.g., acoustic model, lexicon list, language model, etc.) to recognize one or more words of the received inputs. Upon recognition of the words of received inputs, the recognized words may then be provided to natural language processing engine(s) 230 for further processing. In other examples, natural language processing engine(s) 230 may process one or more other types of inputs (e.g., visual input representing sign language communication, gestures, or other forms of communication) to recognize one or more words represented by the other types of inputs.


Natural language processing engine(s) 230 may receive one or more inputs from input device(s) 210, speech recognition engine(s) 220, application(s) 240, database(s) 132, or other components. As an example, natural language processing engine(s) 230 may process inputs received from input device(s) 210, such as user inputs (e.g., voice, non-voice, etc.), location-based inputs (e.g., GPS data, cell ID, etc.), other sensor data input, or other inputs to determine context information associated with one or more user inputs. As another example, natural language processing engine(s) 230 may obtain profile information, context information, or other information from database(s) 132. The obtained information (or context information determined based on inputs from input device(s) 210) may be processed to determine one or more user inputs of a user. In yet another example, natural language processing engine(s) 230 may process one or more recognized words from speech recognition engine(s) 220 and other information (e.g., information from input device(s) 210, application(s) 240, and/or database(s) 132) to determine one or more user inputs.


In an implementation, natural language processing engine(s) 230, application(s) 240, or other components may store information in database(s) 132 for later use by natural language processing engine(s) 230, application(s) 240, or other components. As an example, as described in further detail elsewhere herein, natural language processing engine(s) 230 may store information regarding user inputs in database(s) 132 and/or update profile information, or other information in database(s) 132 based on the information regarding the user inputs.


Transaction Preparation and Search for Products or Services


In an implementation, transaction preparation instructions 124 may utilize information from a processing of the user inputs (e.g., one or more recognized words, product or service type, product name, seller name, etc.) to determine a product or service that is to be purchased. Transaction preparation instructions 124 may utilize such information to search one or more databases associated with one or more sellers (e.g., partners, third party retailers, service providers, etc.). Results obtained from the search may include one or more products and/or services related to the user input. The results are then utilized by the transaction preparation instructions 124 to select the product or service to be purchased by the user. As an example, a single utterance may automatically result in the selection of a seller (e.g., a third party retailer) and the selection of a product or service related to the utterance that is available for purchase via the seller.


In an implementation, transaction preparation instructions 124 may obtain product or service results related to the user input that are available from a remote information source 140. Remote information sources 140 may include information sources that are accessible to computer system 104 via a remote or external network connection (e.g., outside of a firewall), such as the Internet. For example, as illustrated in FIG. 1, remote information source(s) 140 may include, without limitation, a third party search engine 142 (e.g., GOOGLE, BING, YAHOO, etc.), third party retailers 144, including online retailers and offline retailers having an online presence (e.g., AMAZON, GROUPON, EBAY, EXPEDIA, BESTBUY, etc.), third party service providers 146 (e.g., weather services, calendar/scheduling services, etc.), and/or other information source that is remotely accessible to computer system 104. In another implementation, the transaction preparation instructions 124 may select the product or service (that is to be purchased) from one or more predetermined sets of products or services stored in database 132. For example, system 200 may store one or more sets of predetermined products or services that may be selected by the transaction preparation instructions 124 or included in the product or service results.


In an implementation, transaction preparation instructions 124 may provide a set of product and service results for the search. The transaction preparation instructions 124 may utilize the set of results to select the product or service that is to be purchased. In an implementation, the transaction preparation instructions 124 may select the product or service (that is to be purchased) according to a set of predefined rules. For example, the product or service (that is to be purchased) may be selected based on the user input, location of the user, cost comparison of sellers (e.g., partners, third party retailers, third party service providers, etc.), shipping date comparison of the sellers, or other criteria. In another implementation, the results of the search are presented for selection by the user. In another implementation, the profile information may include information relating to the general likes or dislikes of the user t to determine the product or service to be purchased including the types of items a user likes, qualities of items the user likes, the categories of items a user likes, minimum item rating requirements, item pricing requirements, user location and context information, shipping requirements, etc.


In an implementation, transaction preparation instructions 124 may utilize context information associated with the user to determine the product or service to be purchased. Based on the context information, the transaction preparation instructions 124 may refine the search for products or services to be purchased. In one embodiment, the context information may include personal data associated with the user, data from a database associated with the user, data describing an event, data describing an acoustic environment in which the spoken input is received, location, local time, etc. For example, the transaction preparation instructions 124 may utilize the time of the user input to further define the availability of product or service to be purchased.


Continuing the foregoing examples, a user input related to “lawnmower” may cause transaction preparation instructions 124 to cause a search on a third party search engine 142 to be initiated using the search term “lawnmower.” In an implementation, depending on the context (e.g., indicating that the user intends to buy a lawnmower), transaction preparation instructions 124 may add additional search terms such as “purchase” or “sale.” Transaction preparation instructions 124 may search (in addition to or instead of) other remote information sources 140 as well (e.g., retail related to “lawnmower” from one or more third party retailers 144, landscaping services related to “lawnmower” from one or more third party service providers 146, and/or other information related to “lawnmower” from one or more other remote information sources 140).


In another embodiment, the transaction preparation instructions 124 may utilize user inputs such as location-based inputs (e.g., GPS data, cell ID, etc.) to further refine the search for products or services to be purchased. The transaction preparation instructions 124 may utilize the location-based input to further refine the geographic area in which the products or services are offered. For example, if the user utters “Please buy a pizza,” the transaction preparation instructions 124 utilize the location-based inputs to determine the closest pizzeria in relation to the user. In an implementation, the transaction preparation instructions 124 may utilize website browsing information to refine the search for products or services to be purchased. For example, if the user utters “buy this” while browsing a retailing website, the transaction preparation instructions 124 may utilize website browsing information to determine the product or service the user is viewing. It should be contemplated that the transaction preparation instructions 124 prepares and/or completes checkout of the determined product or service directly from the website (or the seller associated with the website) or from another seller that may not be associated with the website.


In an implementation, the transaction preparation instructions 124 may utilize the profile information to select the product or service and/or the sellers from which the product or service is to be purchased. As described below, the profile information may include preferred sellers, brands, style, size, or other parameters related to products or services that may be automatically or manually pre-set. The profile information may also include the types of items a user likes, qualities of terms the user likes, the categories of items a user likes, minimum item rating requirements, item pricing requirements, user location and context information, shipping requirements, etc. The transaction preparation instructions 124 may select the product or service and the sellers (from which the product or service is to be purchased) based on the profile information. As an example, preferred retailers from which products or services is to be purchased and preferred brands of such products or services may be automatically pre-set by the system (e.g., pre-set to system preferred sellers and brands) until the defaults are manually modified by users. The default store, brand, style, size, or other parameters may be obtained (in response to an utterance indicative of a user's intent to purchase a product or service) to prepare and/or complete checkout of a product or service purchase unless the single utterance (or other information) specifies otherwise.


In an implementation, selection of the product or service purchases by the transaction preparation instructions 124 may be limited to certain categories of products or services (e.g., no automobiles), a particular price range (e.g., no more than $100), etc., to reduce the number or severity of purchases related to fraud. The categories of product or services and/or the price ranges may, for instance, be automatically or manually pre-set (e.g., automatically preset by the system, manually pre-set by the user) and stored in the profile information.


In one implementation, the transaction preparation instructions 124 may provide prospective transactions or offers to the user based on the user's profile information. For example, the transaction preparation instructions 124 may prepare a transaction for the user without any input from the user. In one implementation, the transaction preparation instructions 124 may analyze the user's profile information to determine any potential transaction opportunities, and provide a prospective transaction or offer related to the potential transaction opportunity. For example, in the case that voice commerce application 120 determines an upcoming anniversary of the user, the transaction preparation instructions 124 may prepare a prospective purchase for the user related to the anniversary. In another implementation, the transaction preparation instructions 124 may provide offers to the user related to purchases for the potential transaction opportunity.


In an implementation, an administrator of the system 100 (or a subsystem thereof) may manage a set of predetermined sellers from whose inventories are searched for available products or services in response to a user input indicative of a user's intent to purchase. As an example, the administrator may specify a set of sellers that have priority over other sellers in having their products or services offered to users. Thus, a seller from which a product or service is to be purchased may be selected from the predetermined set of sellers specified by the administrator. Other criteria may, of course, be considered when selecting a seller with which a user is to complete a purchase transaction for a product or service.


Checkout Management


In an implementation, the checkout management instructions 126 may prepare and/or complete checkout of selected product or service purchases related to one or more user inputs. The checkout management instructions 126 may determine payment information that is to be used to pay for a selected product or service, shipping information that is to be used to deliver the selected product or service, and/or other information that is thereafter utilized to prepare and/or complete the purchase of the selected product or service. For example, the checkout management instructions 126 may utilize default payment information stored in the profile information for preparing or completing checkout of the selected product or service. Likewise, the checkout management instructions 126 may utilize default shipping information stored in the profile information for preparing or completing checkout of the selected product or service. In another implementation, the checkout management instructions 126 utilize an address book or contact list of the user stored in the profile information to provide shipping information for checkout of products or services for individuals other than the user. For example, a user input may reference an individual, other than the user, that is recognized by the user input processing instructions 122 (e.g., “Send flowers to my mom” wherein the user's mom is recognized as the intended recipient of the flowers). The checkout management instructions 126 may utilize the address book or contact list of the user to determine if the referenced individual's address is available for input as the shipping information.


In one implementation, the checkout management instructions 126 automatically complete the checkout of the product or service purchase. As an example, a single utterance from the user may result in the completion of checkout of the product or service without further input or approval from the user. In another implementation, the checkout management instructions 126 may present a request for confirmation of the determined product or service, shipping information, payment information, and/or other information to the user to solicit a confirmation from the user to complete the checkout of the product or service purchase. For example, the checkout management instructions 126 may prepare all of the aspects (e.g., payment information, shipping information, etc.) of checkout of the product or service purchase but wait until confirmation from the user to complete checkout.


In an implementation, the checkout management instructions 126 may utilize user profile information for preparing and/or completing checkout of product or service purchases via a user input. In an implementation, the checkout management instructions 126 may utilize defaults associated with the user profile information, such as default payment information, default shipping information, etc., for preparing and/or completing checkout of product or service purchases. In another implementation, the checkout management instructions 126 utilize an address book or contact list of the user stored in the profile information to provide shipping information for checkout of products or services for individuals other than the user.


Profile Management


In an implementation, stored user profile information (e.g., name, payment information, shipping information, preferences, etc.) may be utilized by voice commerce application 120 for preparing and/or completing checkout of product or service purchases. In an implementation, profile management instructions 128 may automatically set defaults associated with the user profile information, such as default payment information, default shipping information, etc. In another implementation, profile management instructions 128 may automatically or manually pre-set profile information for preparing and/or completing checkout of product or service purchases. In an implementation, profile management instructions 128 enable the user to set profile information including default payment and shipping information utilized by the voice commerce application 120.


In an implementation, profile management instructions 128 may automatically or pre-set preferred sellers, brands, style, size, or other parameters related to products or services. As an example, preferred retailers or service providers from which products or services are to be purchased and preferred brands of such products or services may be automatically pre-set by the profile management instructions 128 (e.g., pre-set to system preferred sellers and brands) until the preferences are manually modified by users. The preferred store, brand, style, size, or other parameters may be obtained (in response to a single utterance) to prepare and/or complete checkout of a product or service purchase unless the single utterance (or other information) specifies otherwise. In an implementation, profile management instructions 128 enable the user to set preferred sellers, brands, style, size, or other parameters related to products or services utilized by the voice commerce application 120. The profile management instructions 128 may automatically or pre-set information relating to the general likes or dislikes of the user to determine a product or service to be purchased including the types of items a user likes, qualities of items the user likes, the categories of items a user likes, minimum item rating requirements, item pricing requirements, user location and context information, shipping requirements, etc.


In an implementation, profile management instructions 128 may automatically or pre-set limits of checkout of product or service purchases to certain categories of products or services (e.g., no automobiles), a particular price range (e.g., no more than $100), etc., to reduce the number or severity of purchases related to fraud. The categories of product or services and/or the price ranges may, for instance, be automatically or manually pre-set (e.g., automatically preset by the system, manually pre-set by the user). In an implementation, profile management instructions 128 enable the user to set limits of checkout of product or service purchases to certain categories of products or services (e.g., no automobiles), a particular price range (e.g., no more than $100), or other criteria.


In another implementation, profile management instructions 128 may store profile information relating to the user's personal information. For example, the profile information may include the user's address book or contact list, calendar, and other information which assist the voice commerce application 120 in determining products or services to be purchased. In one implementation, the user's personal information may be pre-stored based on the registration information or otherwise set by the user.


User Interface


In an implementation, user interface instructions 129 may generate a voice commerce interface. The voice commerce interface may provide status information relating to the preparation and/or completion of checkout of product or service purchases. For example, the voice commerce interface may indicate to a user when checkout of product or service purchases is completed. In one implementation, the user interface instructions 129 may also provide the user with a request for confirmation to complete checkout of a product or service purchase. Examples of the voice commerce interface are illustrated with respect to FIGS. 5, 6A, and 5B.


In an implementation, user interface instructions 129 may generate a profile information management interface. The profile management interface may allow the user to set profile information related to the purchase of products or services. For example, the profile management interface enables the user to set default payment and shipping information. The profile management interface may also enable the user to set preferred sellers, brands, style, size, or other parameters related to products or services as well as limits of certain categories of products or services and particular price ranges.


Examples of System Architectures and Configurations


Different system architectures may be used. For example, all or a portion of voice commerce application 120 may be executed on a user device. In other words, computing device 110 as illustrated may include a user device operated by the user. In implementations where all or a portion of voice commerce application 120 is executed on the user device, the user device may search remote information sources, prepare or complete checkout of product or service purchases, generate the interface, and/or perform other functions/operations of voice commerce application 120.


All or a portion of voice commerce application 120 may be executed on a server device. In other words, computing device 110 as illustrated may include a server device that obtains a user request from a user device operated by the user. In implementations where all or a portion of voice commerce application 120 is executed on the server device, the server device may search remote information sources 140, obtain sets of results, prepare or complete checkout of product or service purchases, provide the interface to a user device, and/or perform other functions/operations of voice commerce application 120.


Although illustrated in FIG. 1 as a single component, computer system 104 may include a plurality of individual components (e.g., computer devices) each programmed with at least some of the functions described herein. In this manner, some components of computer system 104 may perform some functions while other components may perform other functions, as would be appreciated. The one or more processors 112 may each include one or more physical processors that are programmed by computer program instructions. The various instructions described herein are exemplary only. Other configurations and numbers of instructions may be used, so long as the processor(s) 112 are programmed to perform the functions described herein.


It should be appreciated that although the various instructions are illustrated in FIG. 1 as being co-located within a single computing device 110, one or more instructions may be executed remotely from the other instructions. For example, some computing devices 110 of computer system 104 may be programmed by some instructions while other computing devices 110 may be programmed by other instructions, as would be appreciated. Furthermore, the various instructions described herein are exemplary only. Other configurations and numbers of instructions may be used, so long as processor(s) 112 are programmed to perform the functions described herein.


The description of the functionality provided by the different instructions described herein is for illustrative purposes, and is not intended to be limiting, as any of instructions may provide more or less functionality than is described. For example, one or more of the instructions may be eliminated, and some or all of its functionality may be provided by other ones of the instructions. As another example, processor(s) 112 may be programmed by one or more additional instructions that may perform some or all of the functionality attributed herein to one of the instructions.


The various instructions described herein may be stored in a storage device 114, which may comprise random access memory (RAM), read only memory (ROM), and/or other memory. The storage device may store the computer program instructions (e.g., the aforementioned instructions) to be executed by processor(s) 112 as well as data that may be manipulated by processor(s) 112. The storage device may comprise floppy disks, hard disks, optical disks, tapes, or other storage media for storing computer-executable instructions and/or data.


The various components illustrated in FIG. 1 may be coupled to at least one other component via a network 102, which may include any one or more of, for instance, the Internet, an intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a SAN (Storage Area Network), a MAN (Metropolitan Area Network), a wireless network, a cellular communications network, a Public Switched Telephone Network, and/or other network. In FIG. 1 and other drawing Figures, different numbers of entities than depicted may be used. Furthermore, according to various implementations, the components described herein may be implemented in hardware and/or software that configure hardware.


User device(s) may include a device that can interact with computer system 104 through network 102. Such user device(s) may include, without limitation, a tablet computing device, a smartphone, a laptop computing device, a desktop computing device, a network-enabled appliance such as a “Smart” television, a vehicle computing device, and/or other device that may interact with computer system 104.


The various databases 132 described herein may be, include, or interface to, for example, an Oracle™ relational database sold commercially by Oracle Corporation. Other databases, such as Informix™, DB2 (Database 2) or other data storage, including file-based (e.g., comma or tab separated files), or query formats, platforms, or resources such as OLAP (On Line Analytical Processing), SQL (Structured Query Language), a SAN (storage area network), Microsoft Access™, MySQL, PostgreSQL, HSpace, Apache Cassandra, MongoDB, Apache CouchDB™, or others may also be used, incorporated, or accessed. The database may comprise one or more such databases that reside in one or more physical devices and in one or more physical locations. The database may store a plurality of types of data and/or files and associated data or file descriptions, administrative information, or any other data. The database(s) 132 may be stored in storage device 114 and/or other storage that is accessible to computer system 104.


Example Flow Diagrams


The following flow diagrams describe operations that may be accomplished using some or all of the system components described in detail above and, in some implementations, various operations may be performed in different sequences and various operations may be omitted. Additional operations may be performed along with some or all of the operations shown in the depicted flow diagrams. One or more operations may be performed simultaneously. Accordingly, the operations as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting.



FIG. 3 depicts a data flow diagram for a process 300 for providing voice commerce, according to an implementation of the invention. The various processing operations and/or data flows depicted in FIG. 3 (and in the other drawing figures) are described in greater detail herein. The described operations may be accomplished using some or all of the system components described in detail above and, in some implementations, various operations may be performed in different sequences and various operations may be omitted. Additional operations may be performed along with some or all of the operations shown in the depicted flow diagrams. One or more operations may be performed simultaneously. Accordingly, the operations as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting.


In an operation 302, a natural language utterance of a user may be received. As an example, upon receipt, the natural language utterance may be processed by a speech recognition engine to recognize one or more words of the natural language utterance. The recognized words may then be processed, along with context information associated with the user, by a natural language processing engine to determine one or more products or services and/or other information (e.g., payment information, shipping information, seller information, associated cost information, etc.) that can be used to prepare and/or complete checkout of product or service purchases.


In an operation 304, a product or service to be purchased on behalf of the user may be determined based on the natural language utterance. As an example, upon recognition of one or more words associated with the natural language utterance that are related to at least one product or service, the product/service-related words may be utilized to search one or more databases associated with one or more third party retailers and/or service providers, and obtain results indicating one or more products or services. The results may then be processed, along with context information associated with the user, to select the most relevant product or service as the product or service that is to be purchased on behalf of the user.


As illustrated by FIG. 3, in one implementation, the product or service that is to be purchased may be determined without any further user input after the receipt of the natural language utterance (from which the determination of the product or service to be purchased is based). In another implementation, the product or service that is to be purchased may be determined without further user input identifying the product or service after the receipt of the natural language utterance.


In an operation 306, payment information that is to be used to pay for the product or service may be retrieved. As an example, default payment information associated with the user (e.g., for paying for product or services on behalf of the user) may be stored as profile information associated with the user. Such default payment may, for example, be retrieved from one or more databases storing the user's profile information, and utilized to pay for the product or service.


In an operation 308, shipping information that is to be used to deliver the product or service may be retrieved. As an example, default shipping information associated with the user (e.g., for delivering products or services on behalf of the user) may be stored as profile information associated with the user. Such default shipping information may, for instance, retrieved from one or more databases storing the user's profile information, and be utilized to deliver the product or service.


In an operation 310, a purchase transaction for the product or service may be completed based on the payment information and the shipping information.


As illustrated by FIG. 3, in one implementation, the purchase transaction may be completed without any further user input after the receipt of the natural language utterance (from which the determination of the product or service to be purchased is based). In another implementation, the product or service that is to be purchased may be determined without further user input identifying the product or service, identifying the payment information, or identifying the shipping information after the receipt of the natural language utterance.



FIG. 4 depicts a data flow diagram for another process 400 for providing voice commerce, according to an implementation of the invention. The various processing operations and/or data flows depicted in FIG. 4 (and in the other drawing figures) are described in greater detail herein. The described operations may be accomplished using some or all of the system components described in detail above and, in some implementations, various operations may be performed in different sequences and various operations may be omitted. Additional operations may be performed along with some or all of the operations shown in the depicted flow diagrams. One or more operations may be performed simultaneously. Accordingly, the operations as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting.


As illustrated by FIG. 3, a natural language utterance of a user may be received, and a product or service that is to be purchased on behalf of the user may be determined based on the natural language utterance without further user input after the receipt of the natural language utterance. Payment information that is to be used to pay for the product or service, and shipping information that is to be used to deliver the product or service, may also be retrieved.


Referring back to FIG. 4, in an operation 402, a seller from which the product or service is to be purchased may be selected. As an example, the user may have specified a set of sellers from which the user prefers to purchase products or services. As such, the seller may be selected from the predetermined set of sellers specified by the user. As another example, an administrator of the system 100 (or of a subsystem of the system 100) may have specified a set of sellers that have priority over other sellers in having their products or services offered to users. Thus, the seller may be selected from the predetermined set of sellers specified by the administrator. As yet another example, a database of sellers may be queried to determine which seller has the product or service available for purchase. The sellers that have the product or service available for purchase may then be compared against one another to determine, for example, which seller has the lower price (or overall lower total purchase costs) for the product or service, which sellers has the highest customer rating, or other criteria in selecting the seller from which the product or service is to be purchased.


In an operation 404, seller information associated with the selected seller may be retrieved. As an example, seller information may comprise a name of the seller, contact information associated with the seller, a price at which the seller will sell the product or service to the user, individual or overall costs involved with purchase of the product or service from the seller, a refund policy of the seller for the product or service, or other information.


In an operation 406, a request for user confirmation (to purchase the product or service from the seller and to use the payment information and the shipping information for a purchase transaction for the product or service) may be provided without further user input after the receipt of the utterance.


In an operation 408, it may be determined that the user has confirmed purchasing of the product or service from the seller and use of the payment information and the shipping information for the purchase transaction. As such, in an operation 410, the purchase transaction may be completed based on the seller information, the payment information, and the shipping information without further user input after the receipt of the utterance other than a user confirmation with respect to the confirmation request.


Example Screenshots



FIG. 5 illustrates a screenshot 502 of a user interface which facilitates voice commerce, according to an implementation of the invention. The described screenshots may be accomplished using some or all of the system components described in detail above. As shown in screenshot 502 of FIG. 5, a voice commerce application may enable the user to complete checkout of product or service purchases via a single utterance. As depicted in screenshot 502, the user may say “Send flowers to Betsy.” In response to receiving the utterance from the user, the voice commerce application may determine that flowers are to be purchased, and select a third party retailer from which to purchase the flowers. As an example, the user may have purchased a particular kind of flower (e.g., red roses) for Betsy numerous times in the past. As such, the particular kind of flower may be determined as the particular product that is to be purchased on behalf of the user for Betsy. The selection of the product may, for example, be performed without further user input identifying the product type (e.g., flowers) after the receipt of the utterance, without any further user input after the receipt of the utterance, etc.


The voice commerce application may also determine the payment information to be used to pay for the flowers. Because the utterance indicates that the flowers are to be sent to Betsy, the voice commerce application may determine Betsy's address from the user's address book or contact list and provide Betsy's shipping information to the retailer. The voice commerce application may then, for example, complete a purchase transaction using seller information associated with the third party retailer, the payment information, the shipping information, or other information without further user input from the user. Upon completing the purchase transaction for the flowers, the voice commerce application may indicate that checkout for the flowers has been completed. In an implementation, the product to be purchased, a seller from which the product is to be purchased, payment information, shipping information, or other information may be displayed to the user.



FIGS. 6A and 6B illustrate screenshots 602 and 604 of another user interface which facilitates voice commerce, according to an implementation of the invention. The described screenshots may be accomplished using some or all of the system components described in detail above. As shown in screenshot 602 of FIG. 6A, a voice commerce application may solicit a user confirmation from a user with respect to a product purchase before completing checkout of the product purchase. As depicted in screenshot 602, the user may say “Send flowers to Betsy.” In response to receiving the single utterance from the user, the voice commerce application may determine that flowers are to be purchased, and select a third party retailer from which to purchase the flowers. The voice commerce application may also determine the payment information to be used to pay for the flowers. Because the utterance indicates that the flowers are be sent to Betsy, the voice commerce application may determine Betsy's address from the user's address book or contact list and provide Betsy's shipping information to the retailer. The voice commerce application may then present a request for user confirmation of the purchase to the user (e.g., without further user input after the receipt of the utterance). As shown in screenshot 604, the user may confirm purchase of the flowers by saying “Yes.” Upon confirmation of the purchase, the voice commerce application may indicate that checkout for the flowers has been completed.



FIG. 7A illustrates a screenshot 702 of a user interface which facilitates management of user profile information, according to an implementation of the invention. The described screenshots may be accomplished using some or all of the system components described in detail above. As shown in screenshot 702, the user profile information interface includes the user name, default payment information, and default shipping information. The user may edit any data fields associated with the user name, default payment information, and default shipping information.



FIG. 7B illustrates a screenshot 704 of another user interface which facilitates management of user profile information, according to an implementation of the invention. The described screenshots may be accomplished using some or all of the system components described in detail above. As shown in screenshot 704, the user profile information interface may enable the user to pre-set preferences of different products and/or services to be purchased. The profile information interface includes a product/service category that may be selected by the user. For each product/service category, the user may select preferred sellers, preferred brands, preferred styles, preferred sizes, and other parameters related to the products/services to be selected. The user may also limit certain categories of products or services to a particular price range. The user may edit any data field associated with product/service category to include preferred retail stores/service providers, preferred brands, preferred styles, preferred sizes, and price ranges.


Other implementations, uses and advantages 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 should be considered exemplary only, and the scope of the invention is accordingly intended to be limited only by the following claims.

Claims
  • 1. A method for providing voice commerce, the method being implemented on a computer system having one or more physical processors programmed with computer program instructions which, when executed, perform the method, the method comprising: receiving, by the computer system, a user input comprising a natural language utterance;providing, by the computer system, the natural language utterance as an input to a speech recognition engine;obtaining, by the computer system, one or more words or phrases recognized from the natural language utterance as an output of the speech recognition engine;determining, by the computer system, a context based at least on the one or more words or phrases;identifying, by the computer system, without further user input after the receipt of the user input, a product or service to be purchased on behalf of a user based at least on the determined context;obtaining, by the computer system, payment information with which to pay for the product or service;obtaining, by the computer system, without further user input after the receipt of the user input, shipping information with which to deliver the product or service, wherein the shipping information specifies a name or address of a recipient to which the product or service is to be delivered after the product or service is purchased; andcompleting, by the computer system, without further user input after the receipt of the user input, a purchase transaction for the product or service based on the payment information and shipping information.
  • 2. The method of claim 1, further comprising: selecting, by the computer system, a seller from which the product or service is to be purchased; andobtaining, by the computer system, seller information associated with the seller, wherein completing the purchase transaction comprises completing, without further user input after the receipt of the user input, the purchase transaction based on the seller information, the payment information, and the shipping information.
  • 3. The method of claim 2, wherein the seller information comprises a price at which the seller will sell the product or service, and wherein completing the purchase transaction comprises completing, without further user input after the receipt of the user input, the purchase transaction based on the price, the payment information, and the shipping information.
  • 4. The method of claim 2, wherein selecting the seller comprises selecting the seller based on the price at which the seller will sell the product or service.
  • 5. The method of claim 2, further comprising: obtaining, by the computer system, user profile information associated with the user, wherein the user profile information indicates a predetermined set of sellers specified by the user,wherein selecting the seller comprises selecting the seller from the predetermined set of user-specified sellers indicated by the user profile information.
  • 6. The method of claim 2, further comprising: obtaining, by the computer system, a predetermined set of sellers specified by an administrator of the system that is different than the user,wherein selecting the seller comprises selecting the seller from the predetermined set of administrator-specified sellers.
  • 7. The method of claim 1, further comprising: obtaining, by the computer system, user profile information associated with the user, wherein the user profile information comprises at least one of default payment information that is to be used to pay for products or services on behalf of the user or default shipping information that is to be used to delivery products or services on behalf of the user,wherein at least one of: (i) obtaining the payment information comprises selecting the default payment information to pay for the product or service; or (ii) obtaining the shipping information comprises selecting the default shipping information to deliver the product or service, andwherein completing the purchase transaction comprises completing, without further user input after the receipt of the user input, the purchase transaction based on at least one of the default payment information or the default shipping information.
  • 8. The method of claim 1, further comprising: receiving, at the computer system, a previous user input prior to the receipt of the user input, wherein the previous user input is related to the product or service; andstoring, by the computer system, context information associated with the user based on information related to the previous user input,wherein determining the product or service as at least one product or service to be purchased on behalf of the user comprises determining, without further user input after the receipt of the user input, the product or service based on the natural language utterance and the context information related to the previous user input.
  • 9. The method of claim 8, further comprising: performing, by the computer system, speech recognition on the previous user input to recognize one or more words associated with the previous user input; andidentifying, by the computer system, the product or service as at least one product or service related to the previous user input based on the one or more recognized words,wherein storing the context information comprises storing product information identifying the product or service based on the identification of the product or service as related to the previous user input such that the context information comprises the product information, andwherein determining the product or service as at least one product or service to be purchased on behalf of the user comprises determining, without further user input after the receipt of the user input, the product or service based on the natural language utterance and the product information.
  • 10. The method of claim 1, wherein the one or more words or phrases identify at least one of the product or service or a product or service type.
  • 11. The method of claim 1, wherein the one or more words or phrases by themselves do not indicate the product or service or a product or service type.
  • 12. The method of claim 11, further comprising: receiving, at the computer system, a previous user input prior to the receipt of the user input, wherein the previous user input is related to the product or service,wherein determining the product or service as at least one product or service to be purchased on behalf of the user comprises determining, based on the previous user input, without further user input after the receipt of the user input, the product or service as at least one product or service to be purchased on behalf of the user.
  • 13. The method of claim 1, further comprising: obtaining, by the computer system, user profile information associated with the user, wherein the user profile information indicates one or more pre-approved categories of products or services;determining whether the product or service is associated with at least one of the one or more pre-approved categories;wherein completing the purchase transaction comprises completing, without further user input after the receipt of the user input, the purchase transaction based on the payment information, the shipping information, and a determination that the product or service is associated with at least one of the one or more pre-approved categories.
  • 14. The method of claim 1, further comprising: obtaining, by the computer system, user profile information associated with the user, wherein the user profile information indicates a pre-approved cost threshold;determining whether a cost related to purchasing the product or service satisfies the pre-approved cost threshold;wherein completing the purchase transaction comprises completing, without further user input after the receipt of the user input, the purchase transaction based on the payment information, the shipping information, and a determination that the cost related to purchasing product or service satisfies the pre-approved cost threshold.
  • 15. A system for providing voice commerce, the system comprising: one or more physical processors programmed with computer program instructions which, when executed, cause the one or more physical processors to: receive a user input comprising a natural language utterance;provide the natural language utterance as an input to a speech recognition engine;obtain one or more words or phrases recognized from the natural language utterance as an output of the speech recognition engine;determine a context based at least on the one or more words or phrases;identify, without further user input after the receipt of the user input, a product or service to be purchased on behalf of a user based at least on the determined context;obtain payment information with which to pay for the product or service;obtain, without further user input after the receipt of the user input, shipping information with which to deliver the product or service, wherein the shipping information specifies a name or address of a recipient to which the product or service is to be delivered after the product or service is purchased; andcomplete, without further user input after the receipt of the user input, a purchase transaction for the product or service based on the payment information and shipping information.
  • 16. The system of claim 15, wherein the one or more physical processors are further caused to: select a seller from which the product or service is to be purchased; andobtain seller information associated with the seller,wherein to complete the purchase transaction, the one or more physical processors are further caused to: complete, without further user input after the receipt of the user input, the purchase transaction based on the seller information, the payment information, and the shipping information.
  • 17. The system of claim 16, wherein the seller information comprises a price at which the seller will sell the product or service, and wherein to complete the purchase transaction, the one or more physical processors are further caused to: complete, without further user input after the receipt of the user input, the purchase transaction based on the price, the payment information, and the shipping information.
  • 18. The system of claim 16, wherein selecting the seller comprises selecting the seller based on the price at which the seller will sell the product or service.
  • 19. The system of claim 16, wherein the one or more physical processors are further caused to: obtain user profile information associated with the user, wherein the user profile information indicates a predetermined set of sellers specified by the user,wherein to select the seller, the one or more physical processors are further caused to: select the seller from the predetermined set of user-specified sellers indicated by the user profile information.
  • 20. The system of claim 16, wherein the one or more physical processors are further caused to: obtain a predetermined set of sellers specified by an administrator of the system that is different than the user,wherein to select the seller, the one or more physical processors are further caused to: select the seller from the predetermined set of administrator-specified sellers.
  • 21. The system of claim 15, wherein the one or more physical processors are further caused to: receive a previous user input prior to the receipt of the user input, wherein the previous user input is related to the product or service; andstore context information associated with the user based on information related to the previous user input,wherein to identify the product or service as at least one product or service to be purchased on behalf of the user, the one or more physical processors are further caused to: determine, without further user input after the receipt of the user input, the product or service based on the natural language utterance and the context information related to the previous user input.
  • 22. The system of claim 21, wherein the one or more physical processors are further caused to: perform speech recognition on the previous user input to recognize one or more words associated with the previous user input; andidentify the product or service as at least one product or service related to the previous user input based on the one or more recognized words,wherein to store the context information, the one or more physical processors are further caused to: store product information identifying the product or service based on the identification of the product or service as related to the previous user input such that the context information comprises the product information, and wherein to determine the product or service as at least one product or service to be purchased on behalf of the user, the one or more physical processors are further caused to: determine, without further user input after the receipt of the user input, the product or service based on the natural language utterance and the product information.
  • 23. The system of claim 15, wherein the one or more words or phrases by themselves do not indicate the product or service or a product or service type.
  • 24. The system of claim 23, wherein the one or more physical processors are further caused to: receive a previous user input prior to the receipt of the user input, wherein the previous user input is related to the product or service,wherein to identify the product or service as at least one product or service to be purchased on behalf of the user, the one or more physical processors are further caused to: determine, based on the previous user input, without further user input after the receipt of the user input, the product or service as at least one product or service to be purchased on behalf of the user.
  • 25. A system for providing voice commerce, the system comprising: one or more physical processors programmed with computer program instructions which, when executed, cause the one or more physical processors to: receive a user input comprising a natural language utterance;provide, without further user input after the receipt of the user input, the natural language utterance as an input to a speech recognition engine;obtain, without further user input after the receipt of the user input, one or more words or phrases recognized from the natural language utterance as an output of the speech recognition engine;determine, without further user input after the receipt of the user input, a context based at least on the one or more words or phrases;identify, without further user input after the receipt of the user input, the product or service to be purchased on behalf of the user based at least on the determined context;obtain payment information with which to pay for the product or service;obtain, without further user input after the receipt of the user input, shipping information with which to deliver the product or service, wherein the shipping information specifies a name or address of a recipient to which the product or service is to be delivered after the product or service is purchased; andprovide, without further user input after the receipt of the user input, a request for user confirmation to use the payment information and the shipping information for a purchase transaction for the product or service.
  • 26. The system of claim 25, wherein the one or more physical processors are further caused to: determine whether the user has confirmed use of the payment information and the shipping information for the purchase transaction; andcomplete, without further user input after the receipt of the user input other than a user confirmation with respect to the confirmation request, the purchase transaction based on the payment information, the shipping information, and a determination that the user has confirmed use of the payment information and the shipping information.
  • 27. The system of claim 25, wherein the one or more physical processors are further caused to: select a seller from which the product or service is to be purchased; andobtain seller information associated with the seller,wherein to provide the confirmation request, the one or more physical processors are further caused to: provide, without further user input after the receipt of the user input, a request for user confirmation to purchase the product or service from the seller and to use the payment information and the shipping information for the purchase transaction.
  • 28. The system of claim 25, wherein the one or more physical processors are further caused to: receive a previous user input prior to the receipt of the user input, wherein the previous user input is related to the product or service; andstore context information associated with the user based on information related to the previous user input,wherein to identify the product or service as at least one product or service to be purchased on behalf of the user, the one or more physical processors are further caused to: identify, without further user input after the receipt of the user input, the product or service based on the natural language utterance and the context information related to the previous user input.
  • 29. The system of claim 28, wherein the one or more physical processors are further caused to: perform speech recognition on the previous user input to recognize one or more words associated with the previous user input; andidentify the product or service as at least one product or service related to the previous user input based on the one or more recognized words,wherein to store the context information, the one or more physical processors are further caused to: store product information identifying the product or service based on the identification of the product or service as related to the previous user input such that the context information comprises the product information, andwherein to identify the product or service as at least one product or service to be purchased on behalf of the user, the one or more physical processors are further caused to: determine, without further user input after the receipt of the user input, the product or service based on the natural language utterance and the product information.
  • 30. A system for providing voice commerce, the system comprising: one or more physical processors programmed with computer program instructions which, when executed, cause the one or more physical processors to: receive a user input comprising a natural language utterance;provide, without further user input after the receipt of the user input, the natural language utterance as an input to a speech recognition engine;obtain, without further user input after the receipt of the user input, one or more words or phrases recognized from the natural language utterance as an output of the speech recognition engine;identify, without further user input after the receipt of the user input, a context based at least on the one or more words or phrases;determine, without further user input identifying a product or service after the receipt of the user input, a first product or service to be purchased on behalf of a user based at least on the determined context;obtain, without further user input identifying payment information after the receipt of the user input, first payment information with which to pay for the product or service;obtain, without further user input identifying shipping information after the receipt of the user input, first shipping information with which to deliver the product or service, wherein the first shipping information specifies a name or address of a recipient to which the product or service is to be delivered after the product or service is purchased; andcomplete, without further user input identifying a product or service, payment information, or shipping information after the receipt of the user input, a purchase transaction for the first product or service based on the first payment information and the first shipping information.
  • 31. The method of claim 1, the method further comprising: identifying, by the computer system, a recipient of the product or service based on the one or more words or phrases, and wherein obtaining the shipping information comprises:obtaining, by the computer system, an address of the recipient.
  • 32. The method of claim 31, wherein identifying the recipient comprises: associating, by the computer system, at least one word, other than a name of the recipient, from among the one or more words or phrases, that identifies the recipient.
  • 33. The method of claim 31, wherein obtaining the address of the recipient comprises: accessing, by the computer system, an address book of the user, wherein the address book comprises an identification of the recipient and the address.
CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 62/051,273 filed Sep. 16, 2014 entitled “VOICE COMMERCE”, the entirety of which is incorporated herein by reference.

US Referenced Citations (814)
Number Name Date Kind
4430669 Cheung Feb 1984 A
4821027 Mallory Apr 1989 A
4829423 Tennant May 1989 A
4887212 Zamora Dec 1989 A
4910784 Doddington Mar 1990 A
5027406 Roberts Jun 1991 A
5155743 Jacobs Oct 1992 A
5164904 Sumner Nov 1992 A
5208748 Flores May 1993 A
5265065 Turtle Nov 1993 A
5274560 LaRue Dec 1993 A
5357596 Takebayashi Oct 1994 A
5369575 Lamberti Nov 1994 A
5377350 Skinner Dec 1994 A
5386556 Hedin Jan 1995 A
5424947 Nagao Jun 1995 A
5471318 Ahuja Nov 1995 A
5475733 Eisdorfer Dec 1995 A
5479563 Yamaguchi Dec 1995 A
5488652 Bielby Jan 1996 A
5499289 Bruno Mar 1996 A
5500920 Kupiec Mar 1996 A
5517560 Greenspan May 1996 A
5533108 Harris Jul 1996 A
5537436 Bottoms Jul 1996 A
5539744 Chu Jul 1996 A
5557667 Bruno Sep 1996 A
5559864 Kennedy, Jr. Sep 1996 A
5563937 Bruno Oct 1996 A
5577165 Takebayashi Nov 1996 A
5590039 Ikeda Dec 1996 A
5608635 Tamai Mar 1997 A
5617407 Bareis Apr 1997 A
5633922 August May 1997 A
5634086 Rtischev May 1997 A
5652570 Lepkofker Jul 1997 A
5675629 Raffel Oct 1997 A
5696965 Dedrick Dec 1997 A
5708422 Blonder Jan 1998 A
5721938 Stuckey Feb 1998 A
5722084 Chakrin Feb 1998 A
5740256 CastelloDaCosta Apr 1998 A
5742763 Jones Apr 1998 A
5748841 Morin May 1998 A
5748974 Johnson May 1998 A
5752052 Richardson May 1998 A
5754784 Garland May 1998 A
5761631 Nasukawa Jun 1998 A
5774841 Salazar Jun 1998 A
5774859 Houser Jun 1998 A
5794050 Dahlgren Aug 1998 A
5794196 Yegnanarayanan Aug 1998 A
5797112 Komatsu Aug 1998 A
5799276 Komissarchik Aug 1998 A
5802510 Jones Sep 1998 A
5829000 Huang Oct 1998 A
5832221 Jones Nov 1998 A
5839107 Gupta Nov 1998 A
5848396 Gerace Dec 1998 A
5855000 Waibel Dec 1998 A
5867817 Catallo Feb 1999 A
5878385 Bralich Mar 1999 A
5878386 Coughlin Mar 1999 A
5892813 Morin Apr 1999 A
5892900 Ginter Apr 1999 A
5895464 Bhandari Apr 1999 A
5895466 Goldberg Apr 1999 A
5897613 Chan Apr 1999 A
5902347 Backman May 1999 A
5911120 Jarett Jun 1999 A
5918222 Fukui Jun 1999 A
5926784 Richardson Jul 1999 A
5933822 Braden-Harder Aug 1999 A
5950167 Yaker Sep 1999 A
5953393 Culbreth Sep 1999 A
5960384 Brash Sep 1999 A
5960397 Rahim Sep 1999 A
5960399 Barclay Sep 1999 A
5960447 Holt Sep 1999 A
5963894 Richardson Oct 1999 A
5963940 Liddy Oct 1999 A
5983190 Trower, II Nov 1999 A
5987404 DellaPietra Nov 1999 A
5991721 Asano Nov 1999 A
5995119 Cosatto Nov 1999 A
5995928 Nguyen Nov 1999 A
5995943 Bull Nov 1999 A
6009382 Martino Dec 1999 A
6014559 Amin Jan 2000 A
6018708 Dahan Jan 2000 A
6021384 Gorin Feb 2000 A
6028514 Lemelson Feb 2000 A
6035267 Watanabe Mar 2000 A
6044347 Abella Mar 2000 A
6049602 Foladare Apr 2000 A
6049607 Marash Apr 2000 A
6058187 Chen May 2000 A
6067513 Ishimitsu May 2000 A
6073098 Buchsbaum Jun 2000 A
6076059 Glickman Jun 2000 A
6078886 Dragosh Jun 2000 A
6081774 deHita Jun 2000 A
6085186 Christianson Jul 2000 A
6101241 Boyce Aug 2000 A
6108631 Ruhl Aug 2000 A
6119087 Kuhn Sep 2000 A
6119101 Peckover Sep 2000 A
6122613 Baker Sep 2000 A
6134235 Goldman Oct 2000 A
6144667 Doshi Nov 2000 A
6144938 Surace Nov 2000 A
6154526 Dahlke Nov 2000 A
6160883 Jackson Dec 2000 A
6167377 Gillick Dec 2000 A
6173266 Marx Jan 2001 B1
6173279 Levin Jan 2001 B1
6175858 Bulfer Jan 2001 B1
6185535 Hedin Feb 2001 B1
6188982 Chiang Feb 2001 B1
6192110 Abella Feb 2001 B1
6192338 Haszto Feb 2001 B1
6195634 Dudemaine Feb 2001 B1
6195651 Handel Feb 2001 B1
6199043 Happ Mar 2001 B1
6208964 Sabourin Mar 2001 B1
6208972 Grant Mar 2001 B1
6219346 Maxemchuk Apr 2001 B1
6219643 Cohen Apr 2001 B1
6226612 Srenger May 2001 B1
6233556 Teunen May 2001 B1
6233559 Balakrishnan May 2001 B1
6233561 Junqua May 2001 B1
6236968 Kanevsky May 2001 B1
6246981 Papineni Jun 2001 B1
6246990 Happ Jun 2001 B1
6266636 Kosaka Jul 2001 B1
6269336 Ladd Jul 2001 B1
6272455 Hoshen Aug 2001 B1
6275231 Obradovich Aug 2001 B1
6278377 DeLine Aug 2001 B1
6278968 Franz Aug 2001 B1
6286002 Axaopoulos Sep 2001 B1
6288319 Catona Sep 2001 B1
6292767 Jackson Sep 2001 B1
6301560 Masters Oct 2001 B1
6308151 Smith Oct 2001 B1
6311159 VanTichelen Oct 2001 B1
6314402 Monaco Nov 2001 B1
6321196 Franceschi Nov 2001 B1
6356869 Chapados Mar 2002 B1
6362748 Huang Mar 2002 B1
6366882 Bijl Apr 2002 B1
6366886 Dragosh Apr 2002 B1
6374214 Friedland Apr 2002 B1
6377913 Coffman Apr 2002 B1
6381535 Durocher Apr 2002 B1
6385596 Wiser May 2002 B1
6385646 Brown May 2002 B1
6393403 Majaniemi May 2002 B1
6393428 Miller May 2002 B1
6397181 Li May 2002 B1
6404878 Jackson Jun 2002 B1
6405170 Phillips Jun 2002 B1
6408272 White Jun 2002 B1
6411810 Maxemchuk Jun 2002 B1
6411893 Ruhl Jun 2002 B2
6415257 Junqua Jul 2002 B1
6418210 Sayko Jul 2002 B1
6420975 DeLine Jul 2002 B1
6429813 Feigen Aug 2002 B2
6430285 Bauer Aug 2002 B1
6430531 Polish Aug 2002 B1
6434523 Monaco Aug 2002 B1
6434524 Weber Aug 2002 B1
6434529 Walker Aug 2002 B1
6442522 Carberry Aug 2002 B1
6446114 Bulfer Sep 2002 B1
6453153 Bowker Sep 2002 B1
6453292 Ramaswamy Sep 2002 B2
6456711 Cheung Sep 2002 B1
6456974 Baker Sep 2002 B1
6466654 Cooper Oct 2002 B1
6466899 Yano Oct 2002 B1
6470315 Netsch Oct 2002 B1
6487494 Odinak Nov 2002 B2
6487495 Gale Nov 2002 B1
6498797 Anerousis Dec 2002 B1
6499013 Weber Dec 2002 B1
6501833 Phillips Dec 2002 B2
6501834 Milewski Dec 2002 B1
6505155 Vanbuskirk Jan 2003 B1
6510417 Woods Jan 2003 B1
6513006 Howard Jan 2003 B2
6522746 Marchok Feb 2003 B1
6523061 Halverson Feb 2003 B1
6532444 Weber Mar 2003 B1
6539348 Bond Mar 2003 B1
6549629 Finn Apr 2003 B2
6553372 Brassell Apr 2003 B1
6556970 Sasaki Apr 2003 B1
6556973 Lewin Apr 2003 B1
6560576 Cohen May 2003 B1
6560590 Shwe May 2003 B1
6567778 ChaoChang May 2003 B1
6567797 Schuetze May 2003 B1
6567805 Johnson May 2003 B1
6570555 Prevost May 2003 B1
6570964 Murveit May 2003 B1
6571279 Herz May 2003 B1
6574597 Mohri Jun 2003 B1
6574624 Johnson Jun 2003 B1
6578022 Foulger Jun 2003 B1
6581103 Dengler Jun 2003 B1
6584439 Geilhufe Jun 2003 B1
6587858 Strazza Jul 2003 B1
6591239 McCall Jul 2003 B1
6594257 Doshi Jul 2003 B1
6594367 Marash Jul 2003 B1
6598018 Junqua Jul 2003 B1
6601026 Appelt Jul 2003 B2
6604075 Brown Aug 2003 B1
6604077 Dragosh Aug 2003 B2
6606598 Holthouse Aug 2003 B1
6611692 Raffel Aug 2003 B2
6614773 Maxemchuk Sep 2003 B1
6615172 Bennett Sep 2003 B1
6622119 Ramaswamy Sep 2003 B1
6629066 Jackson Sep 2003 B1
6631346 Karaorman Oct 2003 B1
6631351 Ramachandran Oct 2003 B1
6633846 Bennett Oct 2003 B1
6636790 Lightner Oct 2003 B1
6643620 Contolini Nov 2003 B1
6647363 Claassen Nov 2003 B2
6650747 Bala Nov 2003 B1
6658388 Kleindienst Dec 2003 B1
6678680 Woo Jan 2004 B1
6681206 Gorin Jan 2004 B1
6691151 Cheyer Feb 2004 B1
6701294 Ball Mar 2004 B1
6704396 Parolkar Mar 2004 B2
6704576 Brachman Mar 2004 B1
6704708 Pickering Mar 2004 B1
6707421 Drury Mar 2004 B1
6708150 Hirayama Mar 2004 B1
6721001 Berstis Apr 2004 B1
6721633 Funk Apr 2004 B2
6721706 Strubbe Apr 2004 B1
6726636 DerGhazarian Apr 2004 B2
6735592 Neumann May 2004 B1
6739556 Langston May 2004 B1
6741931 Kohut May 2004 B1
6742021 Halverson May 2004 B1
6745161 Arnold Jun 2004 B1
6751591 Gorin Jun 2004 B1
6751612 Schuetze Jun 2004 B1
6754485 Obradovich Jun 2004 B1
6754627 Woodward Jun 2004 B2
6757544 Rangarajan Jun 2004 B2
6757718 Halverson Jun 2004 B1
6795808 Strubbe Sep 2004 B1
6801604 Maes Oct 2004 B2
6801893 Backfried Oct 2004 B1
6810375 Ejerhed Oct 2004 B1
6813341 Mahoney Nov 2004 B1
6816830 Kempe Nov 2004 B1
6829603 Chai Dec 2004 B1
6832230 Zilliacus Dec 2004 B1
6833848 Wolff Dec 2004 B1
6850603 Eberle Feb 2005 B1
6856990 Barile Feb 2005 B2
6865481 Kawazoe Mar 2005 B2
6868380 Kroeker Mar 2005 B2
6868385 Gerson Mar 2005 B1
6871179 Kist Mar 2005 B1
6873837 Yoshioka Mar 2005 B1
6877001 Wolf Apr 2005 B2
6877134 Fuller Apr 2005 B1
6901366 Kuhn May 2005 B1
6910003 Arnold Jun 2005 B1
6912498 Stevens Jun 2005 B2
6915126 Mazzara, Jr. Jul 2005 B2
6928614 Everhart Aug 2005 B1
6934756 Maes Aug 2005 B2
6937977 Gerson Aug 2005 B2
6937982 Kitaoka Aug 2005 B2
6941266 Gorin Sep 2005 B1
6944594 Busayapongchai Sep 2005 B2
6950821 Faybishenko Sep 2005 B2
6954755 Reisman Oct 2005 B2
6959276 Droppo Oct 2005 B2
6961700 Mitchell Nov 2005 B2
6963759 Gerson Nov 2005 B1
6964023 Maes Nov 2005 B2
6968311 Knockeart Nov 2005 B2
6973387 Masclet Dec 2005 B2
6975993 Keiller Dec 2005 B1
6980092 Turnbull Dec 2005 B2
6983055 Luo Jan 2006 B2
6990513 Belfiore Jan 2006 B2
6996531 Korall Feb 2006 B2
7003463 Maes Feb 2006 B1
7016849 Arnold Mar 2006 B2
7020609 Thrift Mar 2006 B2
7024364 Guerra Apr 2006 B2
7027586 Bushey Apr 2006 B2
7027974 Busch Apr 2006 B1
7027975 Pazandak Apr 2006 B1
7035415 Belt Apr 2006 B2
7036128 Julia Apr 2006 B1
7043425 Pao May 2006 B2
7054817 Shao May 2006 B2
7058890 George Jun 2006 B2
7062488 Reisman Jun 2006 B1
7069220 Coffman Jun 2006 B2
7072834 Zhou Jul 2006 B2
7076362 Ohtsuji Jul 2006 B2
7082469 Gold Jul 2006 B2
7085708 Manson Aug 2006 B2
7092928 Elad Aug 2006 B1
7107210 Deng Sep 2006 B2
7107218 Preston Sep 2006 B1
7110951 Lemelson Sep 2006 B1
7127395 Gorin Oct 2006 B1
7127400 Koch Oct 2006 B2
7130390 Abburi Oct 2006 B2
7136875 Anderson Nov 2006 B2
7137126 Coffman Nov 2006 B1
7143037 Chestnut Nov 2006 B1
7143039 Stifelman Nov 2006 B1
7146319 Hunt Dec 2006 B2
7149696 Shimizu Dec 2006 B2
7165028 Gong Jan 2007 B2
7170993 Anderson Jan 2007 B2
7171291 Obradovich Jan 2007 B2
7174300 Bush Feb 2007 B2
7177798 Hsu Feb 2007 B2
7184957 Brookes Feb 2007 B2
7190770 Ando Mar 2007 B2
7197069 Agazzi Mar 2007 B2
7197460 Gupta Mar 2007 B1
7203644 Anderson Apr 2007 B2
7206418 Yang Apr 2007 B2
7207011 Mulvey Apr 2007 B2
7215941 Beckmann May 2007 B2
7228276 Omote Jun 2007 B2
7231343 Treadgold Jun 2007 B1
7236923 Gupta Jun 2007 B1
7254482 Kawasaki Aug 2007 B2
7272212 Eberle Sep 2007 B2
7277854 Bennett Oct 2007 B2
7283829 Christenson Oct 2007 B2
7283951 Marchisio Oct 2007 B2
7289606 Sibal Oct 2007 B2
7299186 Kuzunuki Nov 2007 B2
7301093 Sater Nov 2007 B2
7305381 Poppink Dec 2007 B1
7321850 Wakita Jan 2008 B2
7328155 Endo Feb 2008 B2
7337116 Charlesworth Feb 2008 B2
7340040 Saylor Mar 2008 B1
7366285 Parolkar Apr 2008 B2
7366669 Nishitani Apr 2008 B2
7376645 Bernard May 2008 B2
7386443 Parthasarathy Jun 2008 B1
7398209 Kennewick Jul 2008 B2
7406421 Odinak Jul 2008 B2
7415100 Cooper Aug 2008 B2
7415414 Azara Aug 2008 B2
7421393 DiFabbrizio Sep 2008 B1
7424431 Greene Sep 2008 B2
7447635 Konopka Nov 2008 B1
7451088 Ehlen Nov 2008 B1
7454368 Stillman Nov 2008 B2
7454608 Gopalakrishnan Nov 2008 B2
7461059 Richardson Dec 2008 B2
7472020 Brulle-Drews Dec 2008 B2
7472060 Gorin Dec 2008 B1
7472075 Odinak Dec 2008 B2
7477909 Roth Jan 2009 B2
7478036 Shen Jan 2009 B2
7487088 Gorin Feb 2009 B1
7487110 Bennett Feb 2009 B2
7493259 Jones Feb 2009 B2
7493559 Wolff Feb 2009 B1
7502672 Kolls Mar 2009 B1
7502738 Kennewick Mar 2009 B2
7516076 Walker Apr 2009 B2
7529675 Maes May 2009 B2
7536297 Byrd May 2009 B2
7536374 Au May 2009 B2
7542894 Murata Jun 2009 B2
7546382 Healey Jun 2009 B2
7548491 Macfarlane Jun 2009 B2
7552054 Stifelman Jun 2009 B1
7558730 Davis Jul 2009 B2
7574362 Walker Aug 2009 B2
7577244 Taschereau Aug 2009 B2
7606708 Hwang Oct 2009 B2
7620549 DiCristo Nov 2009 B2
7634409 Kennewick Dec 2009 B2
7640006 Portman Dec 2009 B2
7640160 DiCristo Dec 2009 B2
7640272 Mahajan Dec 2009 B2
7672931 Hurst-Hiller Mar 2010 B2
7676365 Hwang Mar 2010 B2
7676369 Fujimoto Mar 2010 B2
7684977 Morikawa Mar 2010 B2
7693720 Kennewick Apr 2010 B2
7697673 Chiu Apr 2010 B2
7706616 Kristensson Apr 2010 B2
7729916 Coffman Jun 2010 B2
7729918 Walker Jun 2010 B2
7729920 Chaar Jun 2010 B2
7734287 Ying Jun 2010 B2
7748021 Obradovich Jun 2010 B2
7788084 Brun Aug 2010 B2
7792257 Vanier Sep 2010 B1
7801731 Odinak Sep 2010 B2
7809570 Kennewick Oct 2010 B2
7818176 Freeman Oct 2010 B2
7831426 Bennett Nov 2010 B2
7831433 Belvin Nov 2010 B1
7856358 Ho Dec 2010 B2
7873519 Bennett Jan 2011 B2
7873523 Potter Jan 2011 B2
7873654 Bernard Jan 2011 B2
7881936 Longe Feb 2011 B2
7890324 Bangalore Feb 2011 B2
7894849 Kass Feb 2011 B2
7902969 Obradovich Mar 2011 B2
7917367 DiCristo Mar 2011 B2
7920682 Byrne Apr 2011 B2
7949529 Weider May 2011 B2
7949537 Walker May 2011 B2
7953732 Frank May 2011 B2
7974875 Quilici Jul 2011 B1
7983917 Kennewick Jul 2011 B2
7984287 Gopalakrishnan Jul 2011 B2
8005683 Tessel Aug 2011 B2
8015006 Kennewick Sep 2011 B2
8027965 Takehara Sep 2011 B2
8032383 Bhardwaj Oct 2011 B1
8060367 Keaveney Nov 2011 B2
8069046 Kennewick Nov 2011 B2
8073681 Baldwin Dec 2011 B2
8077975 Ma Dec 2011 B2
8082153 Coffman Dec 2011 B2
8086463 Ativanichayaphong Dec 2011 B2
8103510 Sato Jan 2012 B2
8112275 Kennewick Feb 2012 B2
8140327 Kennewick Mar 2012 B2
8140335 Kennewick Mar 2012 B2
8145489 Freeman Mar 2012 B2
8150694 Kennewick Apr 2012 B2
8155962 Kennewick Apr 2012 B2
8170867 Germain May 2012 B2
8180037 Delker May 2012 B1
8195468 Weider Jun 2012 B2
8200485 Lee Jun 2012 B1
8219399 Lutz Jul 2012 B2
8219599 Tunstall-Pedoe Jul 2012 B2
8224652 Wang Jul 2012 B2
8255224 Singleton Aug 2012 B2
8326627 Kennewick Dec 2012 B2
8326634 DiCristo Dec 2012 B2
8326637 Baldwin Dec 2012 B2
8332224 DiCristo Dec 2012 B2
8340975 Rosenberger Dec 2012 B1
8346563 Hjelm Jan 2013 B1
8370147 Kennewick Feb 2013 B2
8447607 Weider May 2013 B2
8447651 Scholl May 2013 B1
8452598 Kennewick May 2013 B2
8503995 Ramer Aug 2013 B2
8509403 Chiu Aug 2013 B2
8515765 Baldwin Aug 2013 B2
8527274 Freeman Sep 2013 B2
8577671 Barve Nov 2013 B1
8589161 Kennewick Nov 2013 B2
8620659 DiCristo Dec 2013 B2
8719005 Lee May 2014 B1
8719009 Baldwin May 2014 B2
8719026 Kennewick May 2014 B2
8731929 Kennewick May 2014 B2
8738380 Baldwin May 2014 B2
8849652 Weider Sep 2014 B2
8849670 DiCristo Sep 2014 B2
8849696 Pansari Sep 2014 B2
8849791 Hertschuh Sep 2014 B1
8886536 Freeman Nov 2014 B2
8972243 Strom Mar 2015 B1
8983839 Kennewick Mar 2015 B2
9009046 Stewart Apr 2015 B1
9015049 Baldwin Apr 2015 B2
9037455 Faaborg May 2015 B1
9070366 Mathias Jun 2015 B1
9105266 Baldwin Aug 2015 B2
9171541 Kennewick Oct 2015 B2
9269097 Freeman Feb 2016 B2
9305548 Kennewick Apr 2016 B2
9308445 Merzenich Apr 2016 B1
9406078 Freeman Aug 2016 B2
9502025 Kennewick Nov 2016 B2
20010039492 Nemoto Nov 2001 A1
20010041980 Howard Nov 2001 A1
20010049601 Kroeker Dec 2001 A1
20010054087 Flom Dec 2001 A1
20020010584 Schultz Jan 2002 A1
20020015500 Belt Feb 2002 A1
20020022927 Lemelson Feb 2002 A1
20020022956 Ukrainczyk Feb 2002 A1
20020029186 Roth Mar 2002 A1
20020029261 Shibata Mar 2002 A1
20020032752 Gold Mar 2002 A1
20020035501 Handel Mar 2002 A1
20020040297 Tsiao Apr 2002 A1
20020049535 Rigo Apr 2002 A1
20020049805 Yamada Apr 2002 A1
20020059068 Rose May 2002 A1
20020065568 Silfvast May 2002 A1
20020067839 Heinrich Jun 2002 A1
20020069059 Smith Jun 2002 A1
20020069071 Knockeart Jun 2002 A1
20020073176 Ikeda Jun 2002 A1
20020082911 Dunn Jun 2002 A1
20020087312 Lee Jul 2002 A1
20020087326 Lee Jul 2002 A1
20020087525 Abbott Jul 2002 A1
20020107694 Lerg Aug 2002 A1
20020120609 Lang Aug 2002 A1
20020124050 Middeljans Sep 2002 A1
20020133354 Ross Sep 2002 A1
20020133402 Faber Sep 2002 A1
20020135618 Maes Sep 2002 A1
20020138248 Corston-Oliver Sep 2002 A1
20020143532 McLean Oct 2002 A1
20020143535 Kist Oct 2002 A1
20020152260 Chen Oct 2002 A1
20020161646 Gailey Oct 2002 A1
20020161647 Gailey Oct 2002 A1
20020173333 Buchholz Nov 2002 A1
20020173961 Guerra Nov 2002 A1
20020184373 Maes Dec 2002 A1
20020188602 Stubler Dec 2002 A1
20020198714 Zhou Dec 2002 A1
20030014261 Kageyama Jan 2003 A1
20030016835 Elko Jan 2003 A1
20030046346 Mumick Mar 2003 A1
20030064709 Gailey Apr 2003 A1
20030065427 Funk Apr 2003 A1
20030069734 Everhart Apr 2003 A1
20030088421 Maes May 2003 A1
20030093419 Bangalore May 2003 A1
20030097249 Walker May 2003 A1
20030110037 Walker Jun 2003 A1
20030112267 Belrose Jun 2003 A1
20030115062 Walker Jun 2003 A1
20030120493 Gupta Jun 2003 A1
20030135488 Amir Jul 2003 A1
20030144846 Denenberg Jul 2003 A1
20030158731 Falcon Aug 2003 A1
20030161448 Parolkar Aug 2003 A1
20030174155 Weng Sep 2003 A1
20030182132 Niemoeller Sep 2003 A1
20030187643 VanThong Oct 2003 A1
20030204492 Wolf Oct 2003 A1
20030206640 Malvar Nov 2003 A1
20030212550 Ubale Nov 2003 A1
20030212558 Matula Nov 2003 A1
20030212562 Patel Nov 2003 A1
20030225825 Healey Dec 2003 A1
20030236664 Sharma Dec 2003 A1
20040006475 Ehlen Jan 2004 A1
20040010358 Oesterling Jan 2004 A1
20040025115 Sienel Feb 2004 A1
20040030741 Wolton Feb 2004 A1
20040036601 Obradovich Feb 2004 A1
20040044516 Kennewick Mar 2004 A1
20040098245 Walker May 2004 A1
20040117179 Balasuriya Jun 2004 A1
20040117804 Scahill Jun 2004 A1
20040122674 Bangalore Jun 2004 A1
20040133793 Ginter Jul 2004 A1
20040140989 Papageorge Jul 2004 A1
20040148154 Acero Jul 2004 A1
20040148170 Acero Jul 2004 A1
20040158555 Seedman Aug 2004 A1
20040166832 Portman Aug 2004 A1
20040167771 Duan Aug 2004 A1
20040172247 Yoon Sep 2004 A1
20040172258 Dominach Sep 2004 A1
20040189697 Fukuoka Sep 2004 A1
20040193408 Hunt Sep 2004 A1
20040193420 Kennewick Sep 2004 A1
20040199375 Ehsani Oct 2004 A1
20040205671 Sukehiro Oct 2004 A1
20040243417 Pitts Dec 2004 A9
20040247092 Timmins Dec 2004 A1
20050015256 Kargman Jan 2005 A1
20050021331 Huang Jan 2005 A1
20050021334 Iwahashi Jan 2005 A1
20050021470 Martin Jan 2005 A1
20050021826 Kumar Jan 2005 A1
20050033574 Kim Feb 2005 A1
20050033582 Gadd Feb 2005 A1
20050043940 Elder Feb 2005 A1
20050080632 Endo Apr 2005 A1
20050114116 Fiedler May 2005 A1
20050125232 Gadd Jun 2005 A1
20050131673 Koizumi Jun 2005 A1
20050137850 Odell Jun 2005 A1
20050137877 Oesterling Jun 2005 A1
20050143994 Mori Jun 2005 A1
20050144013 Fujimoto Jun 2005 A1
20050144187 Che Jun 2005 A1
20050149319 Honda Jul 2005 A1
20050216254 Gupta Sep 2005 A1
20050234727 Chiu Oct 2005 A1
20050246174 DeGolia Nov 2005 A1
20050283364 Longe Dec 2005 A1
20050283752 Fruchter Dec 2005 A1
20060041431 Maes Feb 2006 A1
20060047509 Ding Mar 2006 A1
20060072738 Louis Apr 2006 A1
20060074671 Farmaner Apr 2006 A1
20060100851 Schonebeck May 2006 A1
20060130002 Hirayama Jun 2006 A1
20060182085 Sweeney Aug 2006 A1
20060206310 Ravikumar Sep 2006 A1
20060217133 Christenson Sep 2006 A1
20060242017 Libes Oct 2006 A1
20060253281 Letzt Nov 2006 A1
20060285662 Yin Dec 2006 A1
20070033005 Cristo Feb 2007 A1
20070033020 Francois Feb 2007 A1
20070033526 Thompson Feb 2007 A1
20070038436 Cristo Feb 2007 A1
20070038445 Helbing Feb 2007 A1
20070043569 Potter Feb 2007 A1
20070043574 Coffman Feb 2007 A1
20070043868 Kumar Feb 2007 A1
20070050191 Weider Mar 2007 A1
20070055525 Kennewick Mar 2007 A1
20070061067 Zeinstra Mar 2007 A1
20070061735 Hoffberg Mar 2007 A1
20070073544 Millett Mar 2007 A1
20070078708 Yu Apr 2007 A1
20070078709 Rajaram Apr 2007 A1
20070078814 Flowers Apr 2007 A1
20070094003 Huang Apr 2007 A1
20070112555 Lavi May 2007 A1
20070112630 Lau May 2007 A1
20070118357 Kasravi May 2007 A1
20070124057 Prieto May 2007 A1
20070135101 Ramati Jun 2007 A1
20070146833 Satomi Jun 2007 A1
20070162296 Altberg Jul 2007 A1
20070174258 Jones Jul 2007 A1
20070179778 Gong Aug 2007 A1
20070185859 Flowers Aug 2007 A1
20070186165 Maislos Aug 2007 A1
20070192309 Fischer Aug 2007 A1
20070198267 Jones Aug 2007 A1
20070203736 Ashton Aug 2007 A1
20070208732 Flowers Sep 2007 A1
20070214182 Rosenberg Sep 2007 A1
20070250901 McIntire Oct 2007 A1
20070265850 Kennewick Nov 2007 A1
20070266257 Camaisa Nov 2007 A1
20070276651 Bliss Nov 2007 A1
20070299824 Pan Dec 2007 A1
20080034032 Healey Feb 2008 A1
20080046311 Shahine Feb 2008 A1
20080059188 Konopka Mar 2008 A1
20080065386 Cross Mar 2008 A1
20080065389 Cross Mar 2008 A1
20080091406 Baldwin Apr 2008 A1
20080103761 Printz May 2008 A1
20080103781 Wasson May 2008 A1
20080104071 Pragada May 2008 A1
20080109285 Reuther May 2008 A1
20080115163 Gilboa May 2008 A1
20080126091 Clark May 2008 A1
20080133215 Sarukkai Jun 2008 A1
20080140385 Mahajan Jun 2008 A1
20080147396 Wang Jun 2008 A1
20080147410 Odinak Jun 2008 A1
20080147637 Li Jun 2008 A1
20080154604 Sathish Jun 2008 A1
20080162471 Bernard Jul 2008 A1
20080177530 Cross Jul 2008 A1
20080189110 Freeman Aug 2008 A1
20080228496 Yu Sep 2008 A1
20080235023 Kennewick Sep 2008 A1
20080235027 Cross Sep 2008 A1
20080294437 Nakano Nov 2008 A1
20080294994 Kruger Nov 2008 A1
20080319751 Kennewick Dec 2008 A1
20090006077 Keaveney Jan 2009 A1
20090024476 Baar Jan 2009 A1
20090052635 Jones Feb 2009 A1
20090067599 Agarwal Mar 2009 A1
20090076827 Bulitta Mar 2009 A1
20090106029 DeLine Apr 2009 A1
20090117885 Roth May 2009 A1
20090144131 Chiu Jun 2009 A1
20090144271 Richardson Jun 2009 A1
20090150156 Kennewick Jun 2009 A1
20090164216 Chengalvarayan Jun 2009 A1
20090171664 Kennewick Jul 2009 A1
20090216540 Tessel Aug 2009 A1
20090248605 Mitchell Oct 2009 A1
20090259561 Boys Oct 2009 A1
20090259646 Fujita Oct 2009 A1
20090265163 Li Oct 2009 A1
20090271194 Davis Oct 2009 A1
20090273563 Pryor Nov 2009 A1
20090276700 Anderson Nov 2009 A1
20090287680 Paek Nov 2009 A1
20090299745 Kennewick Dec 2009 A1
20090299857 Brubaker Dec 2009 A1
20090304161 Pettyjohn Dec 2009 A1
20090307031 Winkler Dec 2009 A1
20090313026 Coffman Dec 2009 A1
20090319517 Guha Dec 2009 A1
20100023320 Cristo Jan 2010 A1
20100029261 Mikkelsen Feb 2010 A1
20100036967 Caine Feb 2010 A1
20100049501 Kennewick Feb 2010 A1
20100049514 Kennewick Feb 2010 A1
20100057443 Cristo Mar 2010 A1
20100063880 Atsmon Mar 2010 A1
20100064025 Nelimarkka Mar 2010 A1
20100094707 Freer Apr 2010 A1
20100138300 Wallis Jun 2010 A1
20100145700 Kennewick Jun 2010 A1
20100185512 Borger Jul 2010 A1
20100204986 Kennewick Aug 2010 A1
20100204994 Kennewick Aug 2010 A1
20100217604 Baldwin Aug 2010 A1
20100286985 Kennewick Nov 2010 A1
20100299142 Freeman Nov 2010 A1
20100312566 Odinak Dec 2010 A1
20100331064 Michelstein Dec 2010 A1
20110022393 Waller Jan 2011 A1
20110106527 Chiu May 2011 A1
20110112827 Kennewick May 2011 A1
20110112921 Kennewick May 2011 A1
20110119049 Ylonen May 2011 A1
20110131036 DiCristo Jun 2011 A1
20110131045 Cristo Jun 2011 A1
20110231182 Weider Sep 2011 A1
20110231188 Kennewick Sep 2011 A1
20110307167 Taschereau Dec 2011 A1
20120022857 Baldwin Jan 2012 A1
20120046935 Nagao Feb 2012 A1
20120101809 Kennewick Apr 2012 A1
20120101810 Kennewick Apr 2012 A1
20120109753 Kennewick May 2012 A1
20120150620 Mandyam Jun 2012 A1
20120150636 Freeman Jun 2012 A1
20120239498 Ramer Sep 2012 A1
20120240060 Pennington Sep 2012 A1
20120278073 Weider Nov 2012 A1
20130006734 Ocko Jan 2013 A1
20130054228 Baldwin Feb 2013 A1
20130060625 Davis Mar 2013 A1
20130080177 Chen Mar 2013 A1
20130211710 Kennewick Aug 2013 A1
20130253929 Weider Sep 2013 A1
20130254314 Chow Sep 2013 A1
20130297293 Cristo Nov 2013 A1
20130304473 Baldwin Nov 2013 A1
20130311324 Stoll Nov 2013 A1
20130332454 Stuhec Dec 2013 A1
20130339022 Baldwin Dec 2013 A1
20140006951 Hunter Jan 2014 A1
20140012577 Freeman Jan 2014 A1
20140108013 Cristo Apr 2014 A1
20140156278 Kennewick Jun 2014 A1
20140195238 Terao Jul 2014 A1
20140236575 Tur Aug 2014 A1
20140249821 Kennewick Sep 2014 A1
20140249822 Baldwin Sep 2014 A1
20140278413 Pitschel Sep 2014 A1
20140278416 Schuster Sep 2014 A1
20140288934 Kennewick Sep 2014 A1
20140365222 Weider Dec 2014 A1
20150019211 Simard Jan 2015 A1
20150019217 Cristo Jan 2015 A1
20150019227 Anandarajah Jan 2015 A1
20150066627 Freeman Mar 2015 A1
20150073910 Kennewick Mar 2015 A1
20150095159 Kennewick Apr 2015 A1
20150142447 Kennewick May 2015 A1
20150170641 Kennewick Jun 2015 A1
20150193379 Mehta Jul 2015 A1
20150228276 Baldwin Aug 2015 A1
20150293917 Bufe Oct 2015 A1
20150348544 Baldwin Dec 2015 A1
20150348551 Gruber Dec 2015 A1
20150364133 Freeman Dec 2015 A1
20160049152 Kennewick Feb 2016 A1
20160078482 Kennewick Mar 2016 A1
20160078491 Kennewick Mar 2016 A1
20160078773 Carter Mar 2016 A1
20160110347 Kennewick Apr 2016 A1
20160148610 Kennewick May 2016 A1
20160148612 Guo May 2016 A1
20160188292 Carter Jun 2016 A1
20160188573 Tang Jun 2016 A1
20160217785 Kennewick Jul 2016 A1
20160335676 Freeman Nov 2016 A1
Foreign Referenced Citations (31)
Number Date Country
1433554 Jul 2003 CN
1320043 Jun 2003 EP
1646037 Apr 2006 EP
H11249773 Sep 1999 JP
2001071289 Mar 2001 JP
2006146881 Jun 2006 JP
2008027454 Feb 2008 JP
2008058465 Mar 2008 JP
2008139928 Jun 2008 JP
2011504304 Feb 2011 JP
9946763 Sep 1999 WO
0021232 Jan 2000 WO
0046792 Jan 2000 WO
0171609 Sep 2001 WO
0178065 Oct 2001 WO
2004072954 Jan 2004 WO
2007019318 Jan 2007 WO
2007021587 Jan 2007 WO
2007027546 Jan 2007 WO
2007027989 Jan 2007 WO
2008098039 Jan 2008 WO
2008118195 Jan 2008 WO
2009075912 Jan 2009 WO
2009145796 Jan 2009 WO
2009111721 Sep 2009 WO
2010096752 Jan 2010 WO
2016044290 Mar 2016 WO
2016044316 Mar 2016 WO
2016044319 Mar 2016 WO
2016044321 Mar 2016 WO
2016061309 Apr 2016 WO
Non-Patent Literature Citations (22)
Entry
Davis, Z., et al., A Personal Handheld Multi-Modal Shopping Assistant, IEEE, 2006, 9 pages.
“Statement in Accordance with the Notice from the European Patent Office” dated Oct. 1, 2007 Concerning Business Methods (OJ EPO Nov. 2007, 592-593), XP002456252.
Arrington, Michael, “Google Redefines GPS Navigation Landscape: Google Maps Navigation for Android 2.0”, TechCrunch, printed from the Internet <http://www.techcrunch.com/2009/10/28/google-redefines-car-gps-navigation-google-maps-navigation-android/>, Oct. 28, 2009, 4 pages.
Bazzi, Issam et al., “Heterogeneous Lexical Units for Automatic Speech Recognition: Preliminary Investigations”, Proceedings of the IEEE International Conference on Acoustics, Speech, and Signal Processing, vol. 3, Jun. 5-9, 2000, XP010507574, pp. 1257-1260.
Belvin, Robert, et al., “Development of the HRL Route Navigation Dialogue System”, Proceedings of the First International Conference on Human Language Technology Research, San Diego, 2001, pp. 1-5.
Chai et al., “Mind: A Semantics-Based Multimodal Interpretation Framework for Conversational Systems”, Proceedings of the International CLASS Workshop on Natural, Intelligent and Effective Interaction in Multimodal Dialogue Systems, Jun. 2002, pp. 37-46.
Cheyer et al., “Multimodal Maps: An Agent-Based Approach”, International Conference on Cooperative Multimodal Communication (CMC/95), May 24-26, 1995, pp. 111-121.
El Meliani et al., “A Syllabic-Filler-Based Continuous Speech Recognizer for Unlimited Vocabulary”, Canadian Conference on Electrical and Computer Engineering, vol. 2, Sep. 5-8, 1995, pp. 1007-1010.
Elio et al., “On Abstract Task Models and Conversation Policies” in Workshop on Specifying and Implementing Conversation Policies, Autonomous Agents '99, Seattle, 1999, 10 pages.
Kirchhoff, Katrin, “Syllable-Level Desynchronisation of Phonetic Features for Speech Recognition”, Proceedings of the Fourth International Conference on Spoken Language, 1996, ICSLP 96, vol. 4, IEEE, 1996, 3 pages.
Kuhn, Thomas, et al., “Hybrid In-Car Speech Recognition for Mobile Multimedia Applications”, Vehicular Technology Conference, IEEE, Jul. 1999, pp. 2009-2013.
Lin, Bor-shen, et al., “A Distributed Architecture for Cooperative Spoken Dialogue Agents with Coherent Dialogue State and History”, ASRU'99, 1999, 4 pages.
Lind, R., et al., “The Network Vehicle—A Glimpse into the Future of Mobile Multi-Media”, IEEE Aerosp. Electron. Systems Magazine, vol. 14, No. 9, Sep. 1999, pp. 27-32.
Mao, Mark Z., “Automatic Training Set Segmentation for Multi-Pass Speech Recognition”, Department of Electrical Engineering, Stanford University, CA, copyright 2005, IEEE, pp. I-685 to I-688.
O'Shaughnessy, Douglas, “Interacting with Computers by Voice: Automatic Speech Recognition and Synthesis”, Proceedings of the IEEE, vol. 91, No. 9, Sep. 1, 2003, XP011100665. pages 1272-1305.
Reuters, “IBM to Enable Honda Drivers to Talk to Cars”, Charles Schwab & Co., Inc., Jul. 28, 2002, 1 page.
Turunen, “Adaptive Interaction Methods in Speech User Interfaces”, Conference on Human Factors in Computing Systems, Seattle, Washington, 2001, pp. 91-92.
Vanhoucke, Vincent, “Confidence Scoring and Rejection Using Multi-Pass Speech Recognition”, Nuance Communications, Menlo Park, CA, 2005, 4 pages.
Weng, Fuliang, et al., “Efficient Lattice Representation and Generation”, Speech Technology and Research Laboratory, SRI International, Menlo Park, CA, 1998, 4 pages.
Wu, Su-Lin, et al., “Incorporating Information from Syllable-Length Time Scales into Automatic Speech Recognition”, Proceedings of the 1998 IEEE International Conference on Acoustics, Speech and Signal Processing, 1998, vol. 2, IEEE, 1998, 4 pages.
Wu, Su-Lin, et al., “Integrating Syllable Boundary Information into Speech Recognition”, IEEE International Conference on Acoustics, Speech, and Signal Processing, ICASSP-97, 1997, vol. 2, IEEE, 1997, 4 pages.
Zhao, Yilin, “Telematics: Safe and Fun Driving”, IEEE Intelligent Systems, vol. 17, Issue 1, 2002, pp. 10-14.
Related Publications (1)
Number Date Country
20160078504 A1 Mar 2016 US
Provisional Applications (1)
Number Date Country
62051273 Sep 2014 US