Intelligent automated assistant

Information

  • Patent Grant
  • 12165635
  • Patent Number
    12,165,635
  • Date Filed
    Thursday, April 28, 2022
    2 years ago
  • Date Issued
    Tuesday, December 10, 2024
    a month ago
Abstract
The intelligent automated assistant system engages with the user in an integrated, conversational manner using natural language dialog, and invokes external services when appropriate to obtain information or perform various actions. The system can be implemented using any of a number of different platforms, such as the web, email, smartphone, and the like, or any combination thereof. In one embodiment, the system is based on sets of interrelated domains and tasks, and employs additional functionally powered by external services with which the system can interact.
Description
FIELD OF THE INVENTION

The present invention relates to intelligent systems, and more specifically for classes of applications for intelligent automated assistants.


BACKGROUND OF THE INVENTION

Today's electronic devices are able to access a large, growing, and diverse quantity of functions, services, and information, both via the Internet and from other sources. Functionality for such devices is increasing rapidly, as many consumer devices, smartphones, tablet computers, and the like, are able to run software applications to perform various tasks and provide different types of information. Often, each application, function, website, or feature has its own user interface and its own operational paradigms, many of which can be burdensome to learn or overwhelming for users. In addition, many users may have difficulty even discovering what functionality and/or information is available on their electronic devices or on various websites; thus, such users may become frustrated or overwhelmed, or may simply be unable to use the resources available to them in an effective manner.


In particular, novice users, or individuals who are impaired or disabled in some manner, and/or are elderly, busy, distracted, and/or operating a vehicle may have difficulty interfacing with their electronic devices effectively, and/or engaging online services effectively. Such users are particularly likely to have difficulty with the large number of diverse and inconsistent functions, applications, and websites that may be available for their use.


Accordingly, existing systems are often difficult to use and to navigate, and often present users with inconsistent and overwhelming interfaces that often prevent the users from making effective use of the technology.


SUMMARY

According to various embodiments of the present invention, an intelligent automated assistant is implemented on an electronic device, to facilitate user interaction with a device, and to help the user more effectively engage with local and/or remote services. In various embodiments, the intelligent automated assistant engages with the user in an integrated, conversational manner using natural language dialog, and invokes external services when appropriate to obtain information or perform various actions.


According to various embodiments of the present invention, the intelligent automated assistant integrates a variety of capabilities provided by different software components (e.g., for supporting natural language recognition and dialog, multimodal input, personal information management, task flow management, orchestrating distributed services, and the like). Furthermore, to offer intelligent interfaces and useful functionality to users, the intelligent automated assistant of the present invention may, in at least some embodiments, coordinate these components and services. The conversation interface, and the ability to obtain information and perform follow-on task, are implemented, in at least some embodiments, by coordinating various components such as language components, dialog components, task management components, information management components and/or a plurality of external services.


According to various embodiments of the present invention, intelligent automated assistant systems may be configured, designed, and/or operable to provide various different types of operations, functionalities, and/or features, and/or to combine a plurality of features, operations, and applications of an electronic device on which it is installed. In some embodiments, the intelligent automated assistant systems of the present invention can perform any or all of: actively eliciting input from a user, interpreting user intent, disambiguating among competing interpretations, requesting and receiving clarifying information as needed, and performing (or initiating) actions based on the discerned intent. Actions can be performed, for example, by activating and/or interfacing with any applications or services that may be available on an electronic device, as well as services that are available over an electronic network such as the Internet. In various embodiments, such activation of external services can be performed via APIs or by any other suitable mechanism. In this manner, the intelligent automated assistant systems of various embodiments of the present invention can unify, simplify, and improve the user's experience with respect to many different applications and functions of an electronic device, and with respect to services that may be available over the Internet. The user can thereby be relieved of the burden of learning what functionality may be available on the device and on web-connected services, how to interface with such services to get what he or she wants, and how to interpret the output received from such services; rather, the assistant of the present invention can act as a go-between between the user and such diverse services.


In addition, in various embodiments, the assistant of the present invention provides a conversational interface that the user may find more intuitive and less burdensome than conventional graphical user interfaces. The user can engage in a form of conversational dialog with the assistant using any of a number of available input and output mechanisms, such as for example speech, graphical user interfaces (buttons and links), text entry, and the like. The system can be implemented using any of a number of different platforms, such as device APIs, the web, email, and the like, or any combination thereof. Requests for additional input can be presented to the user in the context of such a conversation. Short and long term memory can be engaged so that user input can be interpreted in proper context given previous events and communications within a given session, as well as historical and profile information about the user.


In addition, in various embodiments, context information derived from user interaction with a feature, operation, or application on a device can be used to streamline the operation of other features, operations, or applications on the device or on other devices. For example, the intelligent automated assistant can use the context of a phone call (such as the person called) to streamline the initiation of a text message (for example to determine that the text message should be sent to the same person, without the user having to explicitly specify the recipient of the text message). The intelligent automated assistant of the present invention can thereby interpret instructions such as “send him a text message”, wherein the “him” is interpreted according to context information derived from a current phone call, and/or from any feature, operation, or application on the device. In various embodiments, the intelligent automated assistant takes into account various types of available context data to determine which address book contact to use, which contact data to use, which telephone number to use for the contact, and the like, so that the user need not re-specify such information manually.


In various embodiments, the assistant can also take into account external events and respond accordingly, for example, to initiate action, initiate communication with the user, provide alerts, and/or modify previously initiated action in view of the external events. If input is required from the user, a conversational interface can again be used.


In one embodiment, the system is based on sets of interrelated domains and tasks, and employs additional functionally powered by external services with which the system can interact. In various embodiments, these external services include web-enabled services, as well as functionality related to the hardware device itself. For example, in an embodiment where the intelligent automated assistant is implemented on a smartphone, personal digital assistant, tablet computer, or other device, the assistant can control many operations and functions of the device, such as to dial a telephone number, send a text message, set reminders, add events to a calendar, and the like.


In various embodiments, the system of the present invention can be implemented to provide assistance in any of a number of different domains. Examples include:

    • Local Services (including location- and time-specific services such as restaurants, movies, automated teller machines (ATMs), events, and places to meet);
    • Personal and Social Memory Services (including action items, notes, calendar events, shared links, and the like);
    • E-commerce (including online purchases of items such as books, DVDs, music, and the like);
    • Travel Services (including flights, hotels, attractions, and the like).


One skilled in the art will recognize that the above list of domains is merely exemplary. In addition, the system of the present invention can be implemented in any combination of domains.


In various embodiments, the intelligent automated assistant systems disclosed herein may be configured or designed to include functionality for automating the application of data and services available over the Internet to discover, find, choose among, purchase, reserve, or order products and services. In addition to automating the process of using these data and services, at least one intelligent automated assistant system embodiment disclosed herein may also enable the combined use of several sources of data and services at once. For ex-ample, it may combine information about products from several review sites, check prices and availability from multiple distributors, and check their locations and time constraints, and help a user find a personalized solution to their problem. Additionally, at least one intelligent automated assistant system embodiment disclosed herein may be configured or designed to include functionality for automating the use of data and services available over the Internet to discover, investigate, select among, reserve, and otherwise learn about things to do (including but not limited to movies, events, performances, exhibits, shows and at-tractions); places to go (including but not limited to travel destinations, hotels and other places to stay, landmarks and other sites of interest, etc.); places to eat or drink (such as restaurants and bars), times and places to meet others, and any other source of entertainment or social interaction which may be found on the Internet. Additionally, at least one intelligent automated assistant system embodiment disclosed herein may be configured or designed to include functionality for enabling the operation of applications and services via natural language dialog that may be otherwise provided by dedicated applications with graphical user interfaces including search (including location-based search); navigation (maps and directions); database lookup (such as finding businesses or people by name or other properties); getting weather conditions and forecasts, checking the price of market items or status of financial transactions; monitoring traffic or the status of flights; accessing and updating calendars and schedules; managing reminders, alerts, tasks and projects; communicating over email or other messaging platforms; and operating devices locally or remotely (e.g., dialing telephones, controlling light and temperature, controlling home security devices, playing music or video, etc.). Further, at least one intelligent automated assistant system embodiment disclosed herein may be configured or designed to include functionality for identifying, generating, and/or providing personalized recommendations for activities, products, services, source of entertainment, time management, or any other kind of recommendation service that benefits from an interactive dialog in natural language and automated access to data and services.


In various embodiments, the intelligent automated assistant of the present invention can control many features and operations of an electronic device. For example, the intelligent automated assistant can call services that interface with functionality and applications on a device via APIs or by other means, to perform functions and operations that might otherwise be initiated using a conventional user interface on the device. Such functions and operations may include, for example, setting an alarm, making a telephone call, sending a text message or email message, adding a calendar event, and the like. Such functions and operations may be performed as add-on functions in the context of a conversational dialog between a user and the assistant. Such functions and operations can be specified by the user in the context of such a dialog, or they may be automatically performed based on the context of the dialog. One skilled in the art will recognize that the assistant can thereby be used as a control mechanism for initiating and controlling various operations on the electronic device, which may be used as an alternative to conventional mechanisms such as buttons or graphical user interfaces.





BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate several embodiments of the invention and, together with the description, serve to explain the principles of the invention according to the embodiments. One skilled in the art will recognize that the particular embodiments illustrated in the drawings are merely exemplary, and are not intended to limit the scope of the present invention.



FIG. 1 is a block diagram depicting an example of one embodiment of an intelligent automated assistant system.



FIG. 2 illustrates an example of an interaction between a user and an intelligent automated assistant according to at least one embodiment.



FIG. 3 is a block diagram depicting a computing device suitable for implementing at least a portion of an intelligent automated assistant according to at least one embodiment.



FIG. 4 is a block diagram depicting an architecture for implementing at least a portion of an intelligent automated assistant on a standalone computing system, according to at least one embodiment.



FIG. 5 is a block diagram depicting an architecture for implementing at least a portion of an intelligent automated assistant on a distributed computing network, according to at least one embodiment.



FIG. 6 is a block diagram depicting a system architecture illustrating several different types of clients and modes of operation.



FIG. 7 is a block diagram depicting a client and a server, which communicate with each other to implement the present invention according to one embodiment.



FIG. 8 is a block diagram depicting a fragment of an active ontology ac-cording to one embodiment.



FIG. 9 is a block diagram depicting an example of an alternative embodiment of an intelligent automated assistant system.



FIG. 10 is a flow diagram depicting a method of operation for active input elicitation component(s) according to one embodiment.



FIG. 11 is a flow diagram depicting a method for active typed-input elicitation according to one embodiment.



FIGS. 12 to 21 are screen shots illustrating some portions of some of the procedures for active typed-input elicitation according to one embodiment.



FIG. 22 is a flow diagram depicting a method for active input elicitation for voice or speech input according to one embodiment.



FIG. 23 is a flow diagram depicting a method for active input elicitation for GUI-based input according to one embodiment.



FIG. 24 is a flow diagram depicting a method for active input elicitation at the level of a dialog flow according to one embodiment.



FIG. 25 is a flow diagram depicting a method for active monitoring for relevant events according to one embodiment.



FIG. 26 is a flow diagram depicting a method for multimodal active input elicitation according to one embodiment.



FIG. 27 is a set of screen shots illustrating an example of various types of functions, operations, actions, and/or other features which may be provided by domain models component(s) and services orchestration according to one embodiment.



FIG. 28 is a flow diagram depicting an example of a method for natural language processing according to one embodiment.



FIG. 29 is a screen shot illustrating natural language processing according to one embodiment.



FIGS. 30 and 31 are screen shots illustrating an example of various types of functions, operations, actions, and/or other features which may be provided by dialog flow processor component(s) according to one embodiment.



FIG. 32 is a flow diagram depicting a method of operation for dialog flow processor component(s) according to one embodiment.



FIG. 33 is a flow diagram depicting an automatic call and response procedure, according to one embodiment.



FIG. 34 is a flow diagram depicting an example of task flow for a constrained selection task according to one embodiment.



FIGS. 35 and 36 are screen shots illustrating an example of the operation of constrained selection task according to one embodiment.



FIG. 37 is a flow diagram depicting an example of a procedure for executing a service orchestration procedure according to one embodiment.



FIG. 38 is a flow diagram depicting an example of a service invocation procedure according to one embodiment.



FIG. 39 is a flow diagram depicting an example of a multiphase output procedure according to one embodiment.



FIGS. 40 and 41 are screen shots depicting examples of output processing according to one embodiment.



FIG. 42 is a flow diagram depicting an example of multimodal output processing according to one embodiment.



FIGS. 43A and 43B are screen shots depicting an example of the use of short term personal memory component(s) to maintain dialog context while changing location, according to one embodiment.



FIGS. 44A through 44C are screen shots depicting an example of the use of long term personal memory component(s), according to one embodiment.



FIG. 45 depicts an example of an abstract model for a constrained selection task.



FIG. 46 depicts an example of a dialog flow model to help guide the user through a search process.



FIG. 47 is a flow diagram depicting a method of constrained selection according to one embodiment.





DETAILED DESCRIPTION OF THE EMBODIMENTS

Various techniques will now be described in detail with reference to a few example embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects and/or features described or reference herein. It will be apparent, however, to one skilled in the art, that one or more aspects and/or features described or reference herein may be practiced without some or all of these specific details. In other instances, well known process steps and/or structures have not been described in detail in order to not obscure some of the aspects and/or features described or reference herein.


One or more different inventions may be described in the present application. Further, for one or more of the invention(s) described herein, numerous embodiments may be described in this patent application, and are presented for illustrative purposes only. The described embodiments are not intended to be limiting in any sense. One or more of the invention(s) may be widely applicable to numerous embodiments, as is readily apparent from the disclosure. These embodiments are described in sufficient detail to enable those skilled in the art to practice one or more of the invention(s), and it is to be understood that other embodiments may be utilized and that structural, logical, software, electrical and other changes may be made without departing from the scope of the one or more of the invention(s). Accordingly, those skilled in the art will recognize that the one or more of the invention(s) may be practiced with various modifications and alterations. Particular features of one or more of the invention(s) may be described with reference to one or more particular embodiments or figures that form a part of the present disclosure, and in which are shown, by way of illustration, specific embodiments of one or more of the invention(s). It should be understood, however, that such features are not limited to usage in the one or more particular embodiments or figures with reference to which they are described. The present disclosure is neither a literal description of all embodiments of one or more of the invention(s) nor a listing of features of one or more of the invention(s) that must be present in all embodiments.


Headings of sections provided in this patent application and the title of this patent application are for convenience only, and are not to be taken as limiting the disclosure in any way.


Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.


A description of an embodiment with several components in communication with each other does not imply that all such components are required. To the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of one or more of the invention(s).


Further, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of steps that may be described in this patent application does not, in and of itself, indicate a requirement that the steps be performed in that order. The steps of described processes may be performed in any order practical. Further, some steps may be performed simultaneously despite being described or implied as occurring non-simultaneously (e.g., because one step is described after the other step). Moreover, the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modifications thereto, does not imply that the illustrated process or any of its steps are necessary to one or more of the invention(s), and does not imply that the illustrated process is preferred.


When a single device or article is described, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article.


The functionality and/or the features of a device may be alternatively embodied by one or more other devices that are not explicitly described as having such functionality/features. Thus, other embodiments of one or more of the invention(s) need not include the device itself.


Techniques and mechanisms described or reference herein will sometimes be described in singular form for clarity. However, it should be noted that particular embodiments include multiple iterations of a technique or multiple instantiations of a mechanism unless noted otherwise.


Although described within the context of intelligent automated assistant technology, it may be understood that the various aspects and techniques described herein (such as those associated with active ontologies, for example) may also be deployed and/or applied in other fields of technology involving human and/or computerized interaction with software.


Other aspects relating to intelligent automated assistant technology (e.g., which may be utilized by, provided by, and/or implemented at one or more intelligent automated assistant system embodiments described herein) are disclosed in one or more of the following references:

    • U.S. Provisional Patent Application Ser. No. 61/295,774 for “Intelligent Automated Assistant”, filed Jan. 18, 2010, the disclosure of which is incorporated herein by reference;
    • U.S. patent application Ser. No. 11/518,292 for “Method And Apparatus for Building an Intelligent Automated Assistant”, filed Sep. 8, 2006, the disclosure of which is incorporated herein by reference; and
    • U.S. Provisional Patent Application Ser. No. 61/186,414 for “System and Method for Semantic Auto-Completion”, filed Jun. 12, 2009, the disclosure of which is incorporated herein by reference.


      Hardware Architecture


Generally, the intelligent automated assistant techniques disclosed herein may be implemented on hardware or a combination of software and hardware. For example, they may be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, or on a network interface card. In a specific embodiment, the techniques disclosed herein may be implemented in software such as an operating system or in an application running on an operating system.


Software/hardware hybrid implementation(s) of at least some of the intelligent automated assistant embodiment(s) disclosed herein may be implemented on a programmable machine selectively activated or reconfigured by a computer program stored in memory. Such network devices may have multiple network interfaces which may be configured or designed to utilize different types of network communication protocols. A general architecture for some of these machines may appear from the descriptions disclosed herein. According to specific embodiments, at least some of the features and/or functionalities of the various intelligent automated assistant embodiments disclosed herein may be implemented on one or more general-purpose network host machines such as an end-user computer system, computer, network server or server system, mobile computing device (e.g., personal digital assistant, mobile phone, smartphone, laptop, tablet computer, or the like), consumer electronic device, music player, or any other suitable electronic device, router, switch, or the like, or any combination thereof. In at least some embodiments, at least some of the features and/or functionalities of the various intelligent automated assistant embodiments disclosed herein may be implemented in one or more virtualized computing environments (e.g., network computing clouds, or the like).


Referring now to FIG. 3, there is shown a block diagram depicting a computing device 60 suitable for implementing at least a portion of the intelligent automated assistant features and/or functionalities disclosed herein. Computing device 60 may be, for example, an end-user computer system, network server or server system, mobile computing device (e.g., personal digital assistant, mobile phone, smartphone, laptop, tablet computer, or the like), consumer electronic device, music player, or any other suitable electronic device, or any combination or portion thereof. Computing device 60 may be adapted to communicate with other computing devices, such as clients and/or servers, over a communications network such as the Internet, using known protocols for such communication, whether wireless or wired.


In one embodiment, computing device 60 includes central processing unit (CPU) 62, interfaces 68, and a bus 67 (such as a peripheral component inter-connect (PCI) bus). When acting under the control of appropriate software or firmware, CPU 62 may be responsible for implementing specific functions associated with the functions of a specifically configured computing device or machine. For example, in at least one embodiment, a user's personal digital assistant (PDA) may be configured or designed to function as an intelligent automated assistant system utilizing CPU 62, memory 61, 65, and interface(s) 68. In at least one embodiment, the CPU 62 may be caused to perform one or more of the different types of intelligent automated assistant functions and/or operations under the control of software modules/components, which for example, may include an operating system and any appropriate applications software, drivers, and the like.


CPU 62 may include one or more processor(s) 63 such as, for example, a processor from the Motorola or Intel family of microprocessors or the MIPS family of microprocessors. In some embodiments, processor(s) 63 may include specially designed hardware (e.g., application-specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), field-programmable gate arrays (FPGAs), and the like) for controlling the operations of computing device 60. In a specific embodiment, a memory 61 (such as non-volatile random access memory (RAM) and/or read-only memory (ROM)) also forms part of CPU 62. However, there are many different ways in which memory may be coupled to the system. Memory block 61 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, and the like.


As used herein, the term “processor” is not limited merely to those integrated circuits referred to in the art as a processor, but broadly refers to a microcontroller, a microcomputer, a programmable logic controller, an application-specific integrated circuit, and any other programmable circuit.


In one embodiment, interfaces 68 are provided as interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data packets over a computing network and sometimes support other peripherals used with computing device 60. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various types of interfaces may be provided such as, for example, universal serial bus (USB), Serial, Ethernet, Firewire, PCI, parallel, radio frequency (RF), Bluetooth™, near-field communications (e.g., using near-field magnetics), 802.11 (WiFi), frame relay, TCP/IP, ISDN, fast Ethernet interfaces, Gigabit Ethernet interfaces, asynchronous transfer mode (ATM) interfaces, high-speed serial interface (HSSI) interfaces, Point of Sale (POS) interfaces, fiber data distributed interfaces (FDDIs), and the like. Generally, such interfaces 68 may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile and/or nonvolatile memory (e.g., RAM).


Although the system shown in FIG. 3 illustrates one specific architecture for a computing device 60 for implementing the techniques of the invention described herein, it is by no means the only device architecture on which at least a portion of the features and techniques described herein may be implemented. For example, architectures having one or any number of processors 63 can be used, and such processors 63 can be present in a single device or distributed among any number of devices. In one embodiment, a single processor 63 handles communications as well as routing computations. In various embodiments, different types of intelligent automated assistant features and/or functionalities may be implemented in an intelligent automated assistant system which includes a client device (such as a personal digital assistant or smartphone running client software) and server system(s) (such as a server system described in more detail below).


Regardless of network device configuration, the system of the present invention may employ one or more memories or memory modules (such as, for example, memory block 65) configured to store data, program instructions for the general-purpose network operations and/or other information relating to the functionality of the intelligent automated assistant techniques described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example. The memory or memories may also be configured to store data structures, keyword taxonomy information, advertisement information, user click and impression information, and/or other specific non-program information described herein.


Because such information and program instructions may be employed to implement the systems/methods described herein, at least some network device embodiments may include nontransitory machine-readable storage media, which, for example, may be configured or designed to store program instructions, state information, and the like for performing various operations described herein. Examples of such nontransitory machine-readable storage media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floptical disks, and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM), flash memory, memristor memory, random access memory (RAM), and the like. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.


In one embodiment, the system of the present invention is implemented on a standalone computing system. Referring now to FIG. 4, there is shown a block diagram depicting an architecture for implementing at least a portion of an intelligent automated assistant on a standalone computing system, according to at least one embodiment. Computing device 60 includes processor(s) 63 which run software for implementing intelligent automated assistant 1002. Input device 1206 can be of any type suitable for receiving user input, including for example a keyboard, touch screen, microphone (for example, for voice input), mouse, touchpad, trackball, five-way switch, joystick, and/or any combination thereof. Output device 1207 can be a screen, speaker, printer, and/or any combination thereof. Memory 1210 can be random-access memory having a structure and architecture as are known in the art, for use by processor(s) 63 in the course of running software. Storage device 1208 can be any magnetic, optical, and/or electrical storage device for storage of data in digital form; examples include flash memory, magnetic hard drive, CD-ROM, and/or the like.


In another embodiment, the system of the present invention is implemented on a distributed computing network, such as one having any number of clients and/or servers. Referring now to FIG. 5, there is shown a block diagram depicting an architecture for implementing at least a portion of an intelligent automated assistant on a distributed computing network, according to at least one embodiment.


In the arrangement shown in FIG. 5, any number of clients 1304 are provided; each client 1304 may run software for implementing client-side portions of the present invention. In addition, any number of servers 1340 can be provided for handling requests received from clients 1304. Clients 1304 and servers 1340 can communicate with one another via electronic network 1361, such as the Internet. Network 1361 may be implemented using any known net-work protocols, including for example wired and/or wireless protocols.


In addition, in one embodiment, servers 1340 can call external services 1360 when needed to obtain additional information or refer to store data concerning previous interactions with particular users. Communications with external services 1360 can take place, for example, via network 1361. In various embodiments, external services 1360 include web-enabled services and/or functionality related to or installed on the hardware device itself. For example, in an embodiment where assistant 1002 is implemented on a smartphone or other electronic device, assistant 1002 can obtain information stored in a calendar application (“app”), contacts, and/or other sources.


In various embodiments, assistant 1002 can control many features and operations of an electronic device on which it is installed. For example, assistant 1002 can call external services 1360 that interface with functionality and applications on a device via APIs or by other means, to perform functions and operations that might otherwise be initiated using a conventional user interface on the device. Such functions and operations may include, for example, setting an alarm, making a telephone call, sending a text message or email message, adding a calendar event, and the like. Such functions and operations may be performed as add-on functions in the context of a conversational dialog between a user and assistant 1002. Such functions and operations can be specified by the user in the context of such a dialog, or they may be automatically performed based on the context of the dialog. One skilled in the art will recognize that assistant 1002 can thereby be used as a control mechanism for initiating and controlling various operations on the electronic device, which may be used as an alternative to conventional mechanisms such as buttons or graphical user interfaces.


For example, the user may provide input to assistant 1002 such as “I need to wake tomorrow at 8 am.” Once assistant 1002 has determined the user's intent, using the techniques described herein, assistant 1002 can call external services 1340 to interface with an alarm clock function or application on the device. Assistant 1002 sets the alarm on behalf of the user. In this manner, the user can use assistant 1002 as a replacement for conventional mechanisms for setting the alarm or performing other functions on the device. If the user's requests are ambiguous or need further clarification, assistant 1002 can use the various techniques described herein, including active elicitation, paraphrasing, suggestions, and the like, to obtain the needed information so that the correct services 1340 are called and the intended action taken. In one embodiment, assistant 1002 may prompt the user for confirmation before calling a service 1340 to perform a function. In one embodiment, a user can selectively disable assistant's 1002 ability to call particular services 1340, or can disable all such service-calling if desired.


The system of the present invention can be implemented with many different types of clients 1304 and modes of operation. Referring now to FIG. 6, there is shown a block diagram depicting a system architecture illustrating several different types of clients 1304 and modes of operation. One skilled in the art will recognize that the various types of clients 1304 and modes of operation shown in FIG. 6 are merely exemplary, and that the system of the present invention can be implemented using clients 1304 and/or modes of operation other than those depicted. Additionally, the system can include any or all of such clients 1304 and/or modes of operation, alone or in any combination. Depicted examples include:

    • Computer devices with input/output devices and/or sensors 1402. A client component may be deployed on any such computer device 1402. At least one embodiment may be implemented using a web browser 1304A or other software application for enabling communication with servers 1340 via network 1361. Input and output channels may of any type, including for example visual and/or auditory channels. For example, in one embodiment, the system of the invention can be implemented using voice-based communication methods, allowing for an embodiment of the assistant for the blind whose equivalent of a web browser is driven by speech and uses speech for output.
    • Mobile Devices with I/O and sensors 1406, for which the client may be implemented as an application on the mobile device 1304B. This includes, but is not limited to, mobile phones, smartphones, personal digital assistants, tablet devices, networked game consoles, and the like.
    • Consumer Appliances with I/O and sensors 1410, for which the client may be implemented as an embedded application on the appliance 1304C.
    • Automobiles and other vehicles with dashboard interfaces and sensors 1414, for which the client may be implemented as an embedded system application 1304 D. This includes, but is not limited to, car navigation systems, voice control systems, in-car entertainment systems, and the like.
    • Networked computing devices such as routers 1418 or any other device that resides on or interfaces with a network, for which the client may be implemented as a device-resident application 1304E.
    • Email clients 1424, for which an embodiment of the assistant is connected via an Email Modality Server 1426. Email Modality server 1426 acts as a communication bridge, for example taking input from the user as email messages sent to the assistant and sending output from the assistant to the user as replies.
    • Instant messaging clients 1428, for which an embodiment of the assistant is connected via a Messaging Modality Server 1430. Messaging Modality server 1430 acts as a communication bridge, taking input from the user as messages sent to the assistant and sending output from the assistant to the user as messages in reply.
    • Voice telephones 1432, for which an embodiment of the assistant is connected via a Voice over Internet Protocol (VoIP) Modality Server 1430. VoIP Modality server 1430 acts as a communication bridge, taking input from the user as voice spoken to the assistant and sending output from the assistant to the user, for example as synthesized speech, in reply.


For messaging platforms including but not limited to email, instant messaging, discussion forums, group chat sessions, live help or customer support sessions and the like, assistant 1002 may act as a participant in the conversations. Assistant 1002 may monitor the conversation and reply to individuals or the group using one or more the techniques and methods described herein for one-to-one interactions.


In various embodiments, functionality for implementing the techniques of the present invention can be distributed among any number of client and/or server components. For example, various software modules can be implemented for performing various functions in connection with the present invention, and such modules can be variously implemented to run on server and/or client components. Referring now to FIG. 7, there is shown an example of a client 1304 and a server 1340, which communicate with each other to implement the present invention according to one embodiment. FIG. 7 depicts one possible arrangement by which software modules can be distributed among client 1304 and server 1340. One skilled in the art will recognize that the depicted arrangement is merely exemplary, and that such modules can be distributed in many different ways. In addition, any number of clients 1304 and/or servers 1340 can be provided, and the modules can be distributed among these clients 1304 and/or servers 1340 in any of a number of different ways.


In the example of FIG. 7, input elicitation functionality and output processing functionality are distributed among client 1304 and server 1340, with client part of input elicitation 1094a and client part of output processing 1092a located at client 1304, and server part of input elicitation 1094b and server part of output processing 1092b located at server 1340. The following components are located at server 1340:

    • complete vocabulary 1058b;
    • complete library of language pattern recognizers 1060b;
    • master version of short term personal memory 1052b;
    • master version of long term personal memory 1054b.


In one embodiment, client 1304 maintains subsets and/or portions of these components locally, to improve responsiveness and reduce dependence on network communications. Such subsets and/or portions can be maintained and updated according to well known cache management techniques. Such subsets and/or portions include, for example:

    • subset of vocabulary 1058a;
    • subset of library of language pattern recognizers 1060a;
    • cache of short term personal memory 1052a;
    • cache of long term personal memory 1054a.


Additional components may be implemented as part of server 1340, including for example:

    • language interpreter 1070;
    • dialog flow processor 1080;
    • output processor 1090;
    • domain entity databases 1072;
    • task flow models 1086;
    • services orchestration 1082;
    • service capability models 1088.


Each of these components will be described in more detail below. Server 1340 obtains additional information by interfacing with external services 1360 when needed.


Conceptual Architecture


Referring now to FIG. 1, there is shown a simplified block diagram of a specific example embodiment of an intelligent automated assistant 1002. As described in greater detail herein, different embodiments of intelligent automated assistant systems may be configured, designed, and/or operable to provide various different types of operations, functionalities, and/or features generally relating to intelligent automated assistant technology. Further, as described in greater detail herein, many of the various operations, functionalities, and/or features of the intelligent automated assistant system(s) disclosed herein may provide may enable or provide different types of advantages and/or benefits to different entities interacting with the intelligent automated assistant system(s). The embodiment shown in FIG. 1 may be implemented using any of the hardware architectures described above, or using a different type of hardware architecture.


For example, according to different embodiments, at least some intelligent automated assistant system(s) may be configured, designed, and/or operable to provide various different types of operations, functionalities, and/or features, such as, for example, one or more of the following (or combinations thereof):

    • automate the application of data and services available over the Internet to discover, find, choose among, purchase, reserve, or order products and services. In addition to automating the process of using these data and services, intelligent automated assistant 1002 may also enable the combined use of several sources of data and services at once. For example, it may combine information about products from several review sites, check prices and availability from multiple distributors, and check their locations and time constraints, and help a user find a personalized solution to their problem.
    • automate the use of data and services available over the Internet to discover, investigate, select among, reserve, and otherwise learn about things to do (including but not limited to movies, events, performances, exhibits, shows and attractions); places to go (including but not limited to travel destinations, hotels and other places to stay, landmarks and other sites of interest, and the like); places to eat or drink (such as restaurants and bars), times and places to meet others, and any other source of entertainment or social interaction which may be found on the Internet.
    • enable the operation of applications and services via natural language dialog that are otherwise provided by dedicated applications with graphical user interfaces including search (including location-based search); navigation (maps and directions); database lookup (such as finding businesses or people by name or other properties); getting weather conditions and forecasts, checking the price of market items or status of financial transactions; monitoring traffic or the status of flights; accessing and updating calendars and schedules; managing reminders, alerts, tasks and projects; communicating over email or other messaging platforms; and operating devices locally or remotely (e.g., dialing telephones, controlling light and temperature, controlling home security devices, playing music or video, and the like). In one embodiment, assistant 1002 can be used to initiate, operate, and control many functions and apps available on the device.
    • offer personal recommendations for activities, products, services, source of entertainment, time management, or any other kind of recommendation service that benefits from an interactive dialog in natural language and automated access to data and services.


According to different embodiments, at least a portion of the various types of functions, operations, actions, and/or other features provided by intelligent automated assistant 1002 may be implemented at one or more client systems(s), at one or more server systems (s), and/or combinations thereof.


According to different embodiments, at least a portion of the various types of functions, operations, actions, and/or other features provided by assistant 1002 may implement by at least one embodiment of an automated call and response procedure, such as that illustrated and described, for example, with respect to FIG. 33.


Additionally, various embodiments of assistant 1002 described herein may include or provide a number of different advantages and/or benefits over currently existing intelligent automated assistant technology such as, for example, one or more of the following (or combinations thereof):

    • The integration of speech-to-text and natural language understanding technology that is constrained by a set of explicit models of domains, tasks, services, and dialogs. Unlike assistant technology that attempts to implement a general-purpose artificial intelligence system, the embodiments described herein may apply the multiple sources of constraints to reduce the number of solutions to a more tractable size. This results in fewer ambiguous interpretations of language, fewer relevant domains or tasks, and fewer ways to operationalize the intent in services. The focus on specific domains, tasks, and dialogs also makes it feasible to achieve coverage over domains and tasks with human-managed vocabulary and mappings from intent to services parameters.
    • The ability to solve user problems by invoking services on their behalf over the Internet, using APIs. Unlike search engines which only return links and content, some embodiments of automated assistants 1002 described herein may automate research and problem-solving activities. The ability to invoke multiple services for a given request also provides broader functionality to the user than is achieved by visiting a single site, for instance to produce a product or service or find something to do.
    • The application of personal information and personal interaction history in the interpretation and execution of user requests. Unlike conventional search engines or question answering services, the embodiments described herein use information from personal interaction history (e.g., dialog history, previous selections from results, and the like), personal physical context (e.g., user's location and time), and personal information gathered in the context of interaction (e.g., name, email addresses, physical addresses, phone numbers, account numbers, preferences, and the like). Using these sources of information enables, for example,
      • better interpretation of user input (e.g., using personal history and physical context when interpreting language);
      • more personalized results (e.g., that bias toward preferences or recent selections);
      • improved efficiency for the user (e.g., by automating steps involving the signing up to services or filling out forms).
    • The use of dialog history in interpreting the natural language of user inputs. Because the embodiments may keep personal history and apply natural language understanding on user inputs, they may also use dialog context such as current location, time, domain, task step, and task parameters to interpret the new inputs. Conventional search engines and command processors interpret at least one query independent of a dialog history. The ability to use dialog history may make a more natural interaction possible, one which resembles normal human conversation.
    • Active input elicitation, in which assistant 1002 actively guides and constrains the input from the user, based on the same models and information used to interpret their input. For example, assistant 1002 may apply dialog models to suggest next steps in a dialog with the user in which they are refining a request; offer completions to partially typed input based on domain and context specific possibilities, or use semantic interpretation to select from among ambiguous interpretations of speech as text or text as intent.
    • The explicit modeling and dynamic management of services, with dynamic and robust services orchestration. The architecture of embodiments described enables assistant 1002 to interface with many external services, dynamically determine which services may provide information for a specific user request, map parameters of the user request to different service APIs, call multiple services at once, integrate results from multiple services, fail over gracefully on failed services, and/or efficiently maintain the implementation of services as their APIs and capabilities evolve.
    • The use of active ontologies as a method and apparatus for building assistants 1002, which simplifies the software engineering and data maintenance of automated assistant systems. Active ontologies are an integration of data modeling and execution environments for assistants. They provide a framework to tie together the various sources of models and data (domain concepts, task flows, vocabulary, language pattern recognizers, dialog context, user personal information, and mappings from domain and task requests to external services. Active ontologies and the other architectural innovations described herein make it practical to build deep functionality within domains, unifying multiple sources of information and services, and to do this across a set of domains.


In at least one embodiment, intelligent automated assistant 1002 may be operable to utilize and/or generate various different types of data and/or other types of information when performing specific tasks and/or operations. This may include, for example, input data/information and/or output data/information. For example, in at least one embodiment, intelligent automated assistant 1002 may be operable to access, process, and/or otherwise utilize information from one or more different types of sources, such as, for example, one or more local and/or remote memories, devices and/or systems. Additionally, in at least one embodiment, intelligent automated assistant 1002 may be operable to generate one or more different types of output data/information, which, for example, may be stored in memory of one or more local and/or remote devices and/or systems.


Examples of different types of input data/information which may be accessed and/or utilized by intelligent automated assistant 1002 may include, but are not limited to, one or more of the following (or combinations thereof):

    • Voice input: from mobile devices such as mobile telephones and tablets, computers with microphones, Bluetooth headsets, automobile voice control systems, over the telephone system, recordings on answering services, audio voicemail on integrated messaging services, consumer applications with voice input such as clock radios, telephone station, home entertainment control systems, and game consoles.
    • Text input from keyboards on computers or mobile devices, keypads on remote controls or other consumer electronics devices, email messages sent to the assistant, instant messages or similar short messages sent to the assistant, text received from players in multiuser game environments, and text streamed in message feeds.
    • Location information coming from sensors or location-based systems. Examples include Global Positioning System (GPS) and Assisted GPS (A-GPS) on mobile phones. In one embodiment, location information is combined with explicit user input. In one embodiment, the system of the present invention is able to detect when a user is at home, based on known address information and current location determination. In this manner, certain inferences may be made about the type of information the user might be interested in when at home as opposed to outside the home, as well as the type of services and actions that should be invoked on behalf of the user depending on whether or not he or she is at home.
    • Time information from clocks on client devices. This may include, for example, time from telephones or other client devices indicating the local time and time zone. In addition, time may be used in the context of user requests, such as for instance, to interpret phrases such as “in an hour” and “tonight”.
    • Compass, accelerometer, gyroscope, and/or travel velocity data, as well as other sensor data from mobile or handheld devices or embedded systems such as automobile control systems. This may also include device positioning data from remote controls to appliances and game consoles.
    • Clicking and menu selection and other events from a graphical user interface (GUI) on any device having a GUI. Further examples include touches to a touch screen.
    • Events from sensors and other data-driven triggers, such as alarm clocks, calendar alerts, price change triggers, location triggers, push notification onto a device from servers, and the like.


The input to the embodiments described herein also includes the context of the user interaction history, including dialog and request history.


Examples of different types of output data/information which may be generated by intelligent automated assistant 1002 may include, but are not limited to, one or more of the following (or combinations thereof):

    • Text output sent directly to an output device and/or to the user interface of a device
    • Text and graphics sent to a user over email
    • Text and graphics send to a user over a messaging service
    • Speech output, may include one or more of the following (or combinations thereof):
      • Synthesized speech
      • Sampled speech
      • Recorded messages
    • Graphical layout of information with photos, rich text, videos, sounds, and hyperlinks. For instance, the content rendered in a web browser.
    • Actuator output to control physical actions on a device, such as causing it to turn on or off, make a sound, change color, vibrate, control a light, or the like.
    • Invoking other applications on a device, such as calling a mapping application, voice dialing a telephone, sending an email or instant message, playing media, making entries in calendars, task managers, and note applications, and other applications.
    • Actuator output to control physical actions to devices attached or controlled by a device, such as operating a remote camera, controlling a wheelchair, playing music on remote speakers, playing videos on remote displays, and the like.


It may be appreciated that the intelligent automated assistant 1002 of FIG. 1 is but one example from a wide range of intelligent automated assistant system embodiments which may be implemented. Other embodiments of the intelligent automated assistant system (not shown) may include additional, fewer and/or different components/features than those illustrated, for example, in the example intelligent automated assistant system embodiment of FIG. 1.


User Interaction


Referring now to FIG. 2, there is shown an example of an interaction between a user and at least one embodiment of an intelligent automated assistant 1002. The example of FIG. 2 assumes that a user is speaking to intelligent automated assistant 1002 using input device 1206, which may be a speech input mechanism, and the output is graphical layout to output device 1207, which may be a scrollable screen. Conversation screen 101A features a conversational user interface showing what the user said 1018 (“I'd like a romantic place for Italian food near my office”) and assistant's 1002 response, which is a summary of its findings 101C (“OK, I found these Italian restaurants which reviews say are romantic close to your work:”) and a set of results 101 D (the first three of a list of restaurants are shown). In this example, the user clicks on the first result in the list, and the result automatically opens up to reveal more information about the restaurant, shown in information screen 101E. Information screen 101E and conversation screen 101A may appear on the same output device, such as a touch-screen or other display device; the examples depicted in FIG. 2 are two different output states for the same output device.


In one embodiment, information screen 101E shows information gathered and combined from a variety of services, including for example, any or all of the following:

    • Addresses and geolocations of businesses;
    • Distance from user's current location;
    • Reviews from a plurality of sources;


In one embodiment, information screen 101E also includes some examples of services that assistant 1002 might offer on behalf of the user, including:

    • Dial a telephone to call the business (“call”);
    • Remember this restaurant for future reference (“save”);
    • Send an email to someone with the directions and information about this restaurant (“share”);
    • Show the location of and directions to this restaurant on a map (“map it”);
    • Save personal notes about this restaurant (“my notes”).


As shown in the example of FIG. 2, in one embodiment, assistant 1002 includes intelligence beyond simple database applications, such as, for example,

    • Processing a statement of intent in a natural language 101B, not just keywords;
    • Inferring semantic intent from that language input, such as interpreting “place for Italian food” as “Italian restaurants”;
    • Operationalizing semantic intent into a strategy for using online services and executing that strategy on behalf of the user (e.g., operationalizing the desire for a romantic place into the strategy of checking on-line review sites for reviews that describe a place as “romantic”).


      Intelligent Automated Assistant Components


According to various embodiments, intelligent automated assistant 1002 may include a plurality of different types of components, devices, modules, processes, systems, and the like, which, for example, may be implemented and/or instantiated via the use of hardware and/or combinations of hardware and software. For example, as illustrated in the example embodiment of FIG. 1, assistant 1002 may include one or more of the following types of systems, components, devices, processes, and the like (or combinations thereof):

    • One or more active ontologies 1050;
    • Active input elicitation component(s) 1094 (may include client part 1094a and server part 1094b);
    • Short term personal memory component(s) 1052 (may include master version 1052b and cache 1052a);
    • Long-term personal memory component(s) 1054 (may include master version 1052b and cache 1052a);
    • Domain models component(s) 1056;
    • Vocabulary component(s) 1058 (may include complete vocabulary 1058b and subset 1058a);
    • Language pattern recognizer(s) component(s) 1060 (may include full library 1060b and subset 1560a);
    • Language interpreter component(s) 1070;
    • Domain entity database(s) 1072;
    • Dialog flow processor component(s) 1080;
    • Services orchestration component(s) 1082;
    • Services component(s) 1084;
    • Task flow models component(s) 1086;
    • Dialog flow models component(s) 1087;
    • Service models component(s) 1088;
    • Output processor component(s) 1090.


As described in connection with FIG. 7, in certain client/server-based embodiments, some or all of these components may be distributed between client 1304 and server 1340.


For purposes of illustration, at least a portion of the different types of components of a specific example embodiment of intelligent automated assistant 1002 will now be described in greater detail with reference to the example intelligent automated assistant 1002 embodiment of FIG. 1.


Active Ontologies 1050


Active ontologies 1050 serve as a unifying infrastructure that integrates models, components, and/or data from other parts of embodiments of intelligent automated assistants 1002. In the field of computer and information science, ontologies provide structures for data and knowledge representation such as classes/types, relations, attributes/properties and their instantiation in instances. Ontologies are used, for example, to build models of data and knowledge. In some embodiments of the intelligent automated system 1002, ontologies are part of the modeling framework in which to build models such as domain models.


Within the context of the present invention, an “active ontology” 1050 may also serve as an execution environment, in which distinct processing elements are arranged in an ontology-like manner (e.g., having distinct attributes and relations with other processing elements). These processing elements carry out at least some of the tasks of intelligent automated assistant 1002. Any number of active ontologies 1050 can be provided.


In at least one embodiment, active ontologies 1050 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof).

    • Act as a modeling and development environment, integrating models and data from various model and data components, including but not limited to
      • Domain models 1056
      • Vocabulary 1058
      • Domain entity databases 1072
      • Task flow models 1086
      • Dialog flow models 1087
      • Service capability models 1088
    • Act as a data-modeling environment on which ontology-based editing tools may operate to develop new models, data structures, database schemata, and representations.
    • Act as a live execution environment, instantiating values for elements of domain 1056, task 1086, and/or dialog models 1087, language pattern recognizers, and/or vocabulary 1058, and user-specific information such as that found in short term personal memory 1052, long term personal memory 1054, and/or the results of service orchestration 1182. For example, some nodes of an active ontology may correspond to domain concepts such as restaurant and its property restaurant name. During live execution, these active ontology nodes may be instantiated with the identity of a particular restaurant entity and its name, and how its name corresponds to words in a natural language input utterance. Thus, in this embodiment, the active ontology is serving as both a modeling environment specifying the concept that restaurants are entities with identities that have names, and for storing dynamic bindings of those modeling nodes with data from entity databases and parses of natural language.
    • Enable the communication and coordination among components and processing elements of an intelligent automated assistant, such as, for example, one or more of the following (or combinations thereof):
      • Active input elicitation component(s) 1094
      • Language interpreter component(s) 1070
      • Dialog flow processor component(s) 1080
      • Services orchestration component(s) 1082
      • Services component(s) 1084


In one embodiment, at least a portion of the functions, operations, actions, and/or other features of active ontologies 1050 described herein may be implemented, at least in part, using various methods and apparatuses described in U.S. patent application Ser. No. 11/518,292 for “Method and Apparatus for Building an Intelligent Automated Assistant”, filed Sep. 8, 2006.


In at least one embodiment, a given instance of active ontology 1050 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. Examples of different types of data which may be accessed by active ontologies 1050 may include, but are not limited to, one or more of the following (or combinations thereof):

    • Static data that is available from one or more components of intelligent automated assistant 1002;
    • Data that is dynamically instantiated per user session, for example, but not limited to, maintaining the state of the user-specific inputs and outputs exchanged among components of intelligent automated assistant 1002, the contents of short term personal memory, the inferences made from previous states of the user session, and the like.


In this manner, active ontologies 1050 are used to unify elements of various components in intelligent automated assistant 1002. An active ontology 1050 allows an author, designer, or system builder to integrate components so that the elements of one component are identified with elements of other components. The author, designer, or system builder can thus combine and integrate the components more easily.


Referring now to FIG. 8, there is shown an example of a fragment of an active ontology 1050 according to one embodiment. This example is intended to help illustrate some of the various types of functions, operations, actions, and/or other features that may be provided by active ontologies 1050.


Active ontology 1050 in FIG. 8 includes representations of a restaurant and meal event. In this example, a restaurant is a concept 1610 with properties such as its name 1612, cuisines served 1615, and its location 1613, which in turn might be modeled as a structured node with properties for street address 1614. The concept of a meal event might be modeled as a node 1616 including a dining party 1617 (which has a size 1619) and time period 1618.

    • Active ontologies may include and/or make reference to domain models 1056. For example, FIG. 8 depicts a dining out domain model 1622 linked to restaurant concept 1610 and meal event concept 1616. In this instance, active ontology 1050 includes dining out domain model 1622; specifically, at least two nodes of active ontology 1050, namely restaurant 1610 and meal event 1616, are also included in and/or referenced by dining out domain model 1622. This domain model represents, among other things, the idea that dining out involves meal event that occur at restaurants. The active ontology nodes restaurant 1610 and meal event 1616 are also included and/or referenced by other components of the intelligent automated assistant, a shown by dotted lines in FIG. 8.
    • Active ontologies may include and/or make reference to task flow models 1086. For example, FIG. 8 depicts an event planning task flow model 1630, which models the planning of events independent of domains, applied to a domain-specific kind of event: meal event 1616. Here, active ontology 1050 includes general event planning task flow model 1630, which comprises nodes representing events and other concepts involved in planning them. Active ontology 1050 also includes the node meal event 1616, which is a particular kind of event. In this example, meal event 1616 is included or made reference to by both domain model 1622 and task flow model 1630, and both of these models are included in and/or referenced by active ontology 1050. Again, meal event 1616 is an example of how active ontologies can unify elements of various components included and/or referenced by other components of the intelligent automated assistant, a shown by dotted lines in FIG. 8.
    • Active ontologies may include and/or make reference to dialog flow models 1087. For example, FIG. 8 depicts a dialog flow model 1642 for getting the values of constraints required for a transaction instantiated on the constraint party size as represented in concept 1619. Again, active ontology 1050 provides a framework for relating and unifying various components such as dialog flow models 1087. In this case, dialog flow model 1642 has a general concept of a constraint that is instantiated in this particular example to the active ontology node party size 1619. This particular dialog flow model 1642 operates at the abstraction of constraints, independent of domain. Active ontology 1050 represents party size property 1619 of party node 1617, which is related to meal event node 1616. In such an embodiment, intelligent automated assistant 1002 uses active ontology 1050 to unify the concept of constraint in dialog flow model 1642 with the property of party size 1619 as part of a cluster of nodes representing meal event concept 1616, which is part of the domain model 1622 for dining out.
    • Active ontologies may include and/or make reference to service models 1088. For example, FIG. 8 depicts a model of a restaurant reservation service 1672 associated with the dialog flow step for getting values required for that service to perform a transaction. In this instance, service model 1672 for a restaurant reservation service specifies that a reservation requires a value for party size 1619 (the number of people sitting at a table to reserve). The concept party size 1619, which is part of active ontology 1050, also is linked or related to a general dialog flow model 1642 for asking the user about the constraints for a transaction; in this instance, the party size is a required constraint for dialog flow model 1642.
    • Active ontologies may include and/or make reference to domain entity databases 1072. For example, FIG. 8 depicts a domain entity database of restaurants 1652 associated with restaurant node 1610 in active ontology 1050. Active ontology 1050 represents the general concept of restaurant 1610, as may be used by the various components of intelligent automated assistant 1002, and it is instantiated by data about specific restaurants in restaurant database 1652.
    • Active ontologies may include and/or make reference to vocabulary databases 1058. For example, FIG. 8 depicts a vocabulary database of cuisines 1662, such as Italian, French, and the like, and the words associated with each cuisine such as “French”, “continental”, “provincial”, and the like. Active ontology 1050 includes restaurant node 1610, which is related to cuisines served node 1615, which is associated with the representation of cuisines in cuisines database 1662. A specific entry in database 1662 for a cuisine, such as “French”, is thus related through active ontology 1050 as an instance of the concept of cuisines served 1615.
    • Active ontologies may include and/or make reference to any database that can be mapped to concepts or other representations in ontology 1050. Domain entity databases 1072 and vocabulary databases 1058 are merely two examples of how active ontology 1050 may integrate databases with each other and with other components of automated assistant 1002. Active ontologies allow the author, designer, or system builder to specify a nontrivial mapping between representations in the database and representations in ontology 1050. For example, the database schema for restaurants database 1652 may represent a restaurant as a table of strings and numbers, or as a projection from a larger database of business, or any other representation suitable for database 1652. In this example active ontology 1050, restaurant 1610 is a concept node with properties and relations, organized differently from the database tables. In this example, nodes of ontology 1050 are associated with elements of database schemata. The integration of database and ontology 1050 provides a unified representation for interpreting and acting on specific data entries in databases in terms of the larger sets of models and data in active ontology 1050. For instance, the word “French” may be an entry in cuisines database 1662. Because, in this example, database 1662 is integrated in active ontology 1050, that same word “French” also has an interpretation as a possible cuisine served at a restaurant, which is involved in planning meal events, and this cuisine serves as a constraint to use when using restaurants reservation services, and so forth. Active ontologies can thus integrate databases into the modeling and execution environment to inter-operate with other components of automated assistant 1002.


As described above, active ontology 1050 allows the author, designer, or system builder to integrate components; thus, in the example of FIG. 8, the elements of a component such as constraint in dialog flow model 1642 can be identified with elements of other components such as required parameter of restaurant reservation service 1672.


Active ontologies 1050 may be embodied as, for example, configurations of models, databases, and components in which the relationships among models, databases, and components are any of:

    • containership and/or inclusion;
    • relationship with links and/or pointers;
    • interface over APis, both internal to a program and between programs.


For example, referring now to FIG. 9, there is shown an example of an alternative embodiment of intelligent automated assistant system 1002, wherein domain models 1056, vocabulary 1058, language pattern recognizers 1060, short term personal memory 1052, and long term personal memory 1054 components are organized under a common container associated with active ontology 1050, and other components such as active input elicitation component(s) 1094, language interpreter 1070 and dialog flow processor 1080 are associated with active ontology 1050 via API relationships.


Active Input Elicitation Component(s) 1094


In at least one embodiment, active input elicitation component(s) 1094 (which, as described above, may be implemented in a stand-alone configuration or in a configuration including both server and client components) may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Elicit, facilitate and/or process input from the user or the user's environment, and/or information about their need(s) or request(s). For example, if the user is looking to find a restaurant, the input elicitation module may get information about the user's constraints or preferences for location, time, cuisine, price, and so forth.
    • Facilitate different kinds of input from various sources, such as for example, one or more of the following (or combinations thereof):
      • input from keyboards or any other input device that generates text
      • input from keyboards in user interfaces that offer dynamic suggested completions of partial input
      • input from voice or speech input systems
      • input from Graphical User Interfaces (GUUs) in which users click, select, or otherwise directly manipulate graphical objects to indicate choices
      • input from other applications that generate text and send it to the automated assistant, including email, text messaging, or other text communication platforms


By performing active input elicitation, assistant 1002 is able to disambiguate intent at an early phase of input processing. For example, in an embodiment where input is provided by speech, the waveform might be sent to a server 1340 where words are extracted, and semantic interpretation performed. The results of such semantic interpretation can then be used to drive active input elicitation, which may offer the user alternative candidate words to choose among based on their degree of semantic fit as well as phonetic match.


In at least one embodiment, active input elicitation component(s) 1094 actively, automatically, and dynamically guide the user toward inputs that may be acted upon by one or more of the services offered by embodiments of assistant 1002. Referring now to FIG. 10, there is shown a flow diagram depicting a method of operation for active input elicitation component(s) 1094 according to one embodiment.


The procedure begins 20. In step 21, assistant 1002 may offer interfaces on one or more input channels. For example, a user interface may offer the user options to speak or type or tap at any stage of a conversational interaction. In step 22, the user selects an input channel by initiating input on one modality, such as pressing a button to start recording speech or to bring up an interface for typing.


In at least one embodiment, assistant 1002 offers default suggestions for the selected modality 23. That is, it offers options 24 that are relevant in the current context prior to the user entering any input on that modality. For example, in a text input modality, assistant 1002 might offer a list of common words that would begin textual requests or commands such as, for example, one or more of the following (or combinations thereof): imperative verbs (e.g., find, buy, reserve, get, call, check, schedule, and the like), nouns (e.g., restaurants, movies, events, businesses, and the like), or menu-like options naming domains of discourse (e.g., weather, sports, news, and the like).


If the user selects one of the default options in 25, and a preference to autosubmit 30 is set, the procedure may return immediately. This is similar to the operation of a conventional menu selection.


However, the initial option may be taken as a partial input, or the user may have started to enter a partial input 26. At any point of input, in at least one embodiment, the user may choose to indicate that the partial input is complete 22, which causes the procedure to return.


In 28, the latest input, whether selected or entered, is added to the cumulative input.


In 29, the system suggestions next possible inputs that are relevant given the current input and other sources of constraints on what constitutes relevant and/or meaningful input.


In at least one embodiment, the sources of constraints on user input (for example, which are used in steps 23 and 29) are one or more of the various models and data sources that may be included in assistant 1002, which may include, but are not limited to, one or more of the following (or combinations thereof):

    • Vocabulary 1058. For example, words or phrases that match the current input may be suggested. In at least one embodiment, vocabulary may be associated with any or one or more nodes of active ontologies, domain models, task models, dialog models, and/or service models.
    • Domain models 1056, which may constrain the inputs that may instantiate or otherwise be consistent with the domain model. For example, in at least one embodiment, domain models 1056 may be used to suggest concepts, relations, properties, and/or instances that would be consistent with the current input.
    • Language pattern recognizers 1060, which may be used to recognize idioms, phrases, grammatical constructs, or other patterns in the current input and be used to suggest completions that fill out the pattern.
    • Domain entity databases 1072, which may be used to suggest possible entities in the domain that match the input (e.g., business names, movie names, event names, and the like).
    • Short term memory 1052, which may be used to match any prior input or portion of prior input, and/or any other property or fact about the history of interaction with a user. For example, partial input may be matched against cities that the user has encountered in a session, whether hypothetically (e.g., mentioned in queries) and/or physically (e.g., as determined from location sensors).
    • In at least one embodiment, semantic paraphrases of recent inputs, request, or results may be matched against the current input. For example, if the user had previously request “live music” and obtained concert listing, and then typed “music” in an active input elicitation environment, suggestions may include “live music” and/or “concerts”.
    • Long term personal memory 1054, which may be used to suggest matching items from long term memory. Such matching items may include, for example, one or more or any combination of: domain entities that are saved (e.g., “favorite” restaurants, movies, theaters, venues, and the like), to-do items, list items, calendar entries, people names in contacts/address books, street or city names mentioned in contact/address books, and the like.
    • Task flow models 1086, which may be used to suggest inputs based on the next possible steps of in a task flow.
    • Dialog flow models 1087, which may be used to suggest inputs based on the next possible steps of in a dialog flow.
    • Service capability models 1088, which may be used to suggest possible services to employ, by name, category, capability, or any other property in the model. For example, a user may type part of the name of a preferred review site, and assistant 1002 may suggest a complete command for querying that review site for review.


In at least one embodiment, active input elicitation component(s) 1094 present to the user a conversational interface, for example, an interface in which the user and assistant communicate by making utterances back and forth in a conversational manner. Active input elicitation component(s) 1094 may be operable to perform and/or implement various types of conversational interfaces.


In at least one embodiment, active input elicitation component(s) 1094 may be operable to perform and/or implement various types of conversational interfaces in which assistant 1002 uses plies of the conversation to prompt for information from the user according to dialog models. Dialog models may represent a procedure for executing a dialog, such as, for example, a series of steps required to elicit the information needed to perform a service.


In at least one embodiment, active input elicitation component(s) 1094 offer constraints and guidance to the user in real time, while the user is in the midst of typing, speaking, or otherwise creating input. For example, active elicitation may guide the user to type text inputs that are recognizable by an embodiment of assistant 1002 and/or that may be serviced by one or more services offered by embodiments of assistant 1002. This is an advantage over passively waiting for unconstrained input from a user because it enables the user's efforts to be focused on inputs that may or might be useful, and/or it enables embodiments of assistant 1002 to apply its interpretations of the input in real time as the user is inputting it.


At least a portion of the functions, operations, actions, and/or other features of active input elicitation described herein may be implemented, at least in part, using various methods and apparatuses described in U.S. patent application Ser. No. 11/518,292 for “Method and Apparatus for Building an Intelligent Automated Assistant”, filed Sep. 8, 2006.


According to specific embodiments, multiple instances or threads of active input elicitation component(s) 1094 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software.


According to different embodiments, one or more different threads or instances of active input elicitation component(s) 1094 may be initiated in response to detection of one or more conditions or events satisfying one or more different types of minimum threshold criteria for triggering initiation of at least one instance of active input elicitation component(s) 1094. Various examples of conditions or events which may trigger initiation and/or implementation of one or more different threads or instances of active input elicitation component(s) 1094 may include, but are not limited to, one or more of the following (or combinations thereof):

    • Start of user session. For example, when the user session starts up an application that is an embodiment of assistant 1002, the interface may offer the opportunity for the user to initiate input, for example, by pressing a button to initiate a speech input system or clicking on a text field to initiate a text input session.
    • User input detected.
    • When assistant 1002 explicitly prompts the user for input, as when it requests a response to a question or offers a menu of next steps from which to choose.
    • When assistant 1002 is helping the user perform a transaction and is gathering data for that transaction, e.g., filling in a form.


In at least one embodiment, a given instance of active input elicitation component(s) 1094 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. Examples of different types of data which may be accessed by active input elicitation component(s) 1094 may include, but are not limited to, one or more of the following (or combinations thereof):

    • database of possible words to use in a textual input;
    • grammar of possible phrases to use in a textual input utterance;
    • database of possible interpretations of speech input;
    • database of previous inputs from a user or from other users;
    • data from any of the various models and data sources that may be part of embodiments of assistant 1002, which may include, but are not limited to, one or more of the following (or combinations thereof):
    • Domain models 1056;
    • Vocabulary 1058;
    • Language pattern recognizers 1060;
    • Domain entity databases 1072;
    • Short term memory 1052;
    • Long term personal memory 1054;
    • Task flow models 1086;
    • Dialog flow models 1087;
    • Service capability models 1088.


According to different embodiments, active input elicitation component(s) 1094 may apply active elicitation procedures to, for example, one or more of the following (or combinations thereof):

    • typed input;
    • speech input;
    • input from graphical user interfaces (GUIs), including gestures;
    • input from suggestions offered in a dialog; and
    • events from the computational and/or sensed environments.


      Active Typed Input Elicitation


Referring now to FIG. 11, there is shown a flow diagram depicting a method for active typed input elicitation according to one embodiment.


The method begins 110. Assistant 1002 receives 111 partial text input, for example via input device 1206. Partial text input may include, for example, the characters that have been typed so far in a text input field. At any time, a user may indicate that the typed input is complete 112, as, for example, by pressing an Enter key. If not complete, a suggestion generator generates 114 candidate suggestions 116. These suggestions may be syntactic, semantic, and/or other kinds of suggestion based any of the sources of information or constraints described herein. If the suggestion is selected 118, the input is transformed 117 to include the selected suggestion.


In at least one embodiment, the suggestions may include extensions to the current input. For example, a suggestion for “rest” may be “restaurants.”


In at least one embodiment, the suggestions may include replacements of parts of the current input. For example, a suggestion for “rest” may be “places to eat”.


In at least one embodiment, the suggestions may include replacing and rephrasing of parts of the current input. For example, if the current input is “find restaurants of style” a suggestion may be “italian” and when the suggestion is chosen, the entire input may be rewritten as “find Italian restaurants”.


In at least one embodiment, the resulting input that is returned is annotated 119, so that information about which choices were made in 118 is preserved along with the textual input. This enables, for example, the semantic concepts or entities underlying a string to be associated with the string when it is returned, which improves accuracy of subsequent language interpretation.


Referring now to FIGS. 12 to 21, there are shown screen shots illustrating some portions of some of the procedures for active typed-input elicitation according to one embodiment. The screen shots depict an example of an embodiment of assistant 1002 as implemented on a smartphone such as the iPhone available from Apple Inc. of Cupertino, California. Input is provided to such device via a touch screen, including on-screen keyboard functionality. One skilled in the art will recognize that the screen shots depict an embodiment that is merely exemplary, and that the techniques of the present invention can be implemented on other devices and using other layouts and arrangements.


In FIG. 12, screen 1201 includes a top-level set of suggestions 1202 shown when no input has been provided in field 1203. This corresponds to no-input step 23 of FIG. 10 applied to step 114 of FIG. 11 where there is no input.


In FIG. 13, screen 1301 depicts an example of the use of vocabulary to offer suggested completions 1303 of partial user input 1305 entered in field 1203 using on-screen keyboard 1304. These suggested completions 1303 may be part of the function of active input elicitation 1094. The user has entered partial user input 1305 including the string “comm.” Vocabulary component 1058 has provided a mapping of this string into three different kinds of instances, which are listed as suggested completions 1303: the phrase “community & local events” is a category of the events domain; “chambers of commerce” is a category of the local business search domain, and “Jewish Community Center” is the name of an instance of local businesses. Vocabulary component 1058 may provide the data lookup and management of name spaces like these. The user can tap Go button 1306 to indicate that he or she has finished entering input: this causes assistant 1002 to proceed with the completed text string as a unit of user input.


In FIG. 14, screen 1401 depicts an example in which suggested semantic completions 1303 for a partial string “wh” 1305 include entire phrases with typed parameters. These kinds of suggestions may be enabled by the use of one or more of the various models and sources of input constraints described herein. For example, in one embodiment shown in FIG. 14, “what is happening in city” is an active elicitation of the location parameter of the Local Events domain; “where is business name” is an active elicitation of the Business Name constraint of the Local Business Search domain; “what is showing at the venue name” is an active elicitation of the Venue Name constraint of the Local Events domain; and “what is playing at the movie theater” is an active elicitation of the Movie Theater Name constraint of the Local Events domain. These examples illustrate that the suggested completions are generated by models rather than simply drawn from a database of previously entered queries.


In FIG. 15, screen 1501 depicts a continuation of the same example, after the user has entered additional text 1305 in field 1203. Suggested completions 1303 are updated to match the additional text 1305. In this example, data from a domain entity database 1072 were used: venues whose name starts with “f.” Note that this is a significantly smaller and more semantically relevant set of suggestions than all words that begin with “f.” Again, the suggestions are generated by applying a model, in this case the domain model that represents Local Events as happening at Venues, which are Businesses with Names. The suggestions actively elicit inputs that would make potentially meaningful entries when using a Local Events service.


In FIG. 16, screen 1601 depicts a continuation of the same example, after the user has selected one of suggested completions 1303. Active elicitation continues by prompting the user to further specify the type of information desired, here by presenting a number of specifiers 1602 from which the user can select. In this example, these specifiers are generated by the domain, task flow, and dialog flow models. The Domain is Local Events, which includes Categories of events that happen on Dates in Locations and have Event Names and Feature Performers. In this embodiment, the fact that these five options are offered to the user is generated from the Dialog Flow model that indicates that users should be asked for Constraints that they have not yet entered and from the Service Model that indicates that these five Constraints are parameters to Local Event services available to the assistant. Even the choice of preferred phrases to use as specifiers, such as “by category” and “featured”, are generated from the Domain Vocabulary databases.


In FIG. 17, screen 1701 depicts a continuation of the same example, after the user has selected one of specifiers 1602.


In FIG. 18, screen 1801 depicts a continuation of the same example, wherein the selected specifier 1602 has been added to field 1203, and additional specifiers 1602 are presented. The user can select one of specifiers 1602 and/or provide additional text input via keyboard 1304.


In FIG. 19, screen 1901 depicts a continuation of the same example, wherein the selected specifier 1602 has been added to field 1203, and yet more specifiers 1602 are presented. In this example, previously entered constraints are not actively elicited redundantly.


In FIG. 20, screen 2001 depicts a continuation of the same example, wherein the user has tapped the Go button 1306. The user's input is shown in box 2002, and a message is shown in box 2003, providing feedback to the user as to the query being performed in response to the user's input.


In FIG. 21, screen 2101 depicts a continuation of the same example, wherein results have been found. Message is shown in box 2102. Results 2103, including input elements allowing the user to view further details, save the identified event, buy tickets, add notes, or the like.


In one screen 2101, and other displayed screens, are scrollable, allowing the user to scroll upwards to see screen 2001 or other previously presented screens, and to make changes to the query if desired.


Active Speech Input Elicitation


Referring now to FIG. 22, there is shown a flow diagram depicting a method for active input elicitation for voice or speech input according to one embodiment.


The method begins 221. Assistant 1002 receives 121 voice or speech input in the form of an auditory signal. A speech-to-text service 122 or processor generates a set of candidate text interpretations 124 of the auditory signal. In one embodiment, speech-to-text service 122 is implemented using, for example, Nuance Recognizer, available from Nuance Communications, Inc. of Burlington, MA.


In one embodiment, assistant 1002 employs statistical language models to generate candidate text interpretations 124 of speech input 121.


In addition, in one embodiment, the statistical language models are tuned to look for words, names, and phrases that occur in the various models of assistant 1002 shown in FIG. 8. For example, in at least one embodiment the statistical language models are given words, names, and phrases from some or all of: domain models 1056 (e.g., words and phrases relating to restaurant and meal events), task flow models 1086 (e.g., words and phrases relating to planning an event), dialog flow models 1087 (e.g., words and phrases related to the constraints that are needed to gather the inputs for a restaurant reservation), domain entity databases 1072 (e.g., names of restaurants), vocabulary databases 1058 (e.g., names of cuisines), service models 1088 (e.g., names of service provides such as OpenTable), and/or any words, names, or phrases associated with any node of active ontology 1050.


In one embodiment, the statistical language models are also tuned to look for words, names, and phrases from long-term personal memory 1054. For example, statistical language models can be given text from to-do items, list items, personal notes, calendar entries, people names in contacts/address books, email addresses, street or city names mentioned in contact/address books, and the like.


A ranking component analyzes the candidate interpretations 124 and ranks 126 them according to how well they fit syntactic and/or semantic models of intelligent automated assistant 1002. Any sources of constraints on user input may be used. For example, in one embodiment, assistant 1002 may rank the output of the speech-to-text interpreter according to how well the interpretations parse in a syntactic and/or semantic sense, a domain model, task flow model, and/or dialog model, and/or the like: it evaluates how well various combinations of words in the text interpretations 124 would fit the concepts, relations, entities, and properties of active ontology 1050 and its associated models. For example, if speech-to-text service 122 generates the two candidate interpretations “italian food for lunch” and “italian shoes for lunch”, the ranking by semantic relevance 126 might rank “italian food for lunch” higher if it better matches the nodes assistant's 1002 active ontology 1050 (e.g., the words “italian”, “food” and “lunch” all match nodes in ontology 1050 and they are all connected by relationships in ontology 1050, whereas the word “shoes” does not match ontology 1050 or matches a node that is not part of the dining out domain network).


In various embodiments, algorithms or procedures used by assistant 1002 for interpretation of text inputs, including any embodiment of the natural language processing procedure shown in FIG. 28, can be used to rank and score candidate text interpretations 124 generated by speech-to-text service 122.


In one embodiment, if ranking component 126 determines 128 that the highest-ranking speech interpretation from interpretations 124 ranks above a specified threshold, The highest-ranking interpretation may be automatically selected 130. If no interpretation ranks above a specified threshold, possible candidate interpretations of speech 134 are presented 132 to the user. The user can then select 136 among the displayed choices.


In various embodiments, user selection 136 among the displayed choices can be achieved by any mode of input, including for example any of the modes of multimodal input described in connection with FIG. 16. Such input modes include, without limitation, actively elicited typed input 2610, actively elicited speech input 2620, actively presented GUI for input 2640, and/or the like. In one embodiment, the user can select among candidate interpretations 134, for example by tapping or speaking. In the case of speaking, the possible interpretation of the new speech input is highly constrained by the small set of choices offered 134. For example, if offered “Did you mean italian food or italian shoes?” the user can just say “food” and the assistant can match this to the phrase “italian food” and not get it confused with other global interpretations of the input.


Whether input is automatically selected 130 or selected 136 by the user, the resulting input 138 is returned. In at least one embodiment, the returned input is annotated 138, so that information about which choices were made in step 136 is preserved along with the textual input. This enables, for example, the semantic concepts or entities underlying a string to be associated with the string when it is returned, which improves accuracy of subsequent language interpretation. For example, if “Italian food” was offered as one of the candidate interpretations 134 based on a semantic interpretation of Cuisine=ItalianFood, then the machine-readable semantic interpretation can be sent along with the user's selection of the string “Italian food” as annotated text input 138.


In at least one embodiment, candidate text interpretations 124 are generated based on speech interpretations received as output of speech-to-text service 122.


In at least one embodiment, candidate text interpretations 124 are generated by paraphrasing speech interpretations in terms of their semantic meaning. In some embodiments, there can be multiple paraphrases of the same speech interpretation, offering different word sense or homonym alternatives. For example, if speech-to-text service 122 indicates “place for meet”, the candidate interpretations presented to the user could be paraphrased as “place to meet (local businesses)” and “place for meat (restaurants)”.


In at least one embodiment, candidate text interpretations 124 include offers to correct substrings.


In at least one embodiment, candidate text interpretations 124 include offers to correct substrings of candidate interpretations using syntactic and semantic analysis as described herein.


In at least one embodiment, when the user selects a candidate interpretation, it is returned.


In at least one embodiment, the user is offered an interface to edit the interpretation before it is returned.


In at least one embodiment, the user is offered an interface to continue with more voice input before input is returned. This enables one to incrementally build up an input utterance, getting syntactic and semantic connections, suggestions, and guidance at one iteration.


In at least one embodiment, the user is offered an interface to proceed directly from 136 to step 111 of a method of active typed input elicitation (described above in connection with FIG. 11). This enables one to interleave typed and spoken input, getting syntactic and semantic corrections, suggestions, and guidance at one step.


In at least one embodiment, the user is offered an interface to proceed directly from step 111 of an embodiment of active typed input elicitation to an embodiment of active speech input elicitation. This enables one to interleave typed and spoken input, getting syntactic and semantic corrections, suggestions, and guidance at one step.


Active GUI-Based Input Elicitation


Referring now to FIG. 23, there is shown a flow diagram depicting a method for active input elicitation for GUI-based input according to one embodiment.


The method begins 140. Assistant 1002 presents 141 graphical user interface (GUI) on output device 1207, which may include, for example, links and buttons. The user interacts 142 with at least one GUI element. Data 144 is received, and converted 146 to a uniform format. The converted data is then returned.


In at least one embodiment, some of the elements of the GUI are generated dynamically from the models of the active ontology, rather than written into a computer program. For example, assistant 1002 can offer a set of constraints to guide a restaurant reservation service as regions for tapping on a screen, with each region representing the name of the constraint and/or a value. For instance, the screen could have rows of a dynamically generated GUI layout with regions for the constraints Cuisine, Location, and Price Range. If the models of the active ontology change, the GUI screen would automatically change without reprogramming.


Active Dialog Suggestion Input Elicitation



FIG. 24 is a flow diagram depicting a method for active input elicitation at the level of a dialog flow according to one embodiment. Assistant 1002 suggests 151 possible responses 152. The user selects 154 a suggested response. The received input is converted 154 to a uniform format. The converted data is then returned.


In at least one embodiment, the suggestions offered in step 151 are offered as follow-up steps in a dialog and/or task flow.


In at least one embodiment, the suggestions offer options to refine a query, for example using parameters from a domain and/or task model. For example, one may be offered to change the assumed location or time of a request.


In at least one embodiment, the suggestions offer options to choose among ambiguous alternative interpretations given by a language interpretation procedure or component.


In at least one embodiment, the suggestions offer options to choose among ambiguous alternative interpretations given by a language interpretation procedure or component.


In at least one embodiment, the suggestions offer options to choose among next steps in a workflow associated dialog flow model 1087. For example, dialog flow model 1087 may suggest that after gathering the constrained for one domain (e.g., restaurant dining), assistant 1002 should suggest other related domains (e.g., a movie nearby).


Active Monitoring for Relevant Events


In at least one embodiment, asynchronous events may be treated as inputs in an analogous manner to the other modalities of active elicited input. Thus, such events may be provided as inputs to assistant 1002. Once interpreted, such events can be treated in a manner similar to any other input.


For example, a flight status change may initiate an alert notification to be sent to a user. If a flight is indicated as being late, assistant 1002 may continue the dialog by presenting alternative flights, making other suggestions, and the like, based on the detected event.


Such events can be of any type. For example, assistant 1002 might detect that the user just got home, or is lost (off a specified route), or that a stock price hit a threshold value, or that a television show the user is interested in is starting, or that a musician of interest is touring in the area. In any of these situations, assistant 1002 can proceed with a dialog in substantially the same manner as if the user had him- or herself initiated the inquiry. In one embodiment, events can even be based on data provided from other devices, for example to tell the user when a coworker has returned from lunch (the coworker's device can signal such an event to the user's device, at which time assistant 1002 installed on the user's device responds accordingly).


In one embodiment, the events can be notifications or alerts from a calendar, clock, reminder, or to-do application. For example, an alert from a calendar application about a dinner date can initiate a dialog with assistant 1002 about the dining event. The dialog can proceed as if the user had just spoken or typed the information about the upcoming dinner event, such as “dinner for 2 in San Francisco”.


In one embodiment, the context of possible event trigger 162 can include information about people, places, times, and other data. These data can be used as part of the input to assistant 1002 to use in various steps of processing.


In one embodiment, these data from the context of event trigger 162 can be used to disambiguate speech or text inputs from the user. For example, if a calendar event alert includes the name of a person invited to the event, that information can help disambiguate input which might match several people with the same or similar name.


Referring now to FIG. 25, there is shown a flow diagram depicting a method for active monitoring for relevant events according to one embodiment. In this example, event trigger events are sets of input 162. Assistant 1002 monitors 161 for such events. Detected events may be filtered and sorted 164 for semantic relevance using models, data and information available from other components in intelligent automated assistant 1002. For example, an event that reports a change in flight status may be given higher relevance if the short-term or long-term memory records for a user indicate that the user is on that flight and/or have made inquiries about it to assistant 1002. This sorting and filtering may then present only the top events for review by the user, who may then choose to pick one or more and act on them.


Event data is converted 166 to a uniform input format, and returned.


In at least one embodiment, assistant 1002 may proactively offer services associated with events that were suggested for user attention. For example, if a flight status alert indicates a flight may be missed, assistant 1002 may suggest to the user a task flow for replanning the itinerary or booking a hotel.


Input Elicitation Component(s) Example


The following example is intended to help illustrate some of the various types of functions, operations, actions, and/or other features which may be provided by active input elicitation component(s) 1094. Example: Command completion (what can the user say to assistant 1002?)


The user is facing a text input box with the general instruction to enter “what do you want to do?” Depending on the context and the user input, any of several system responses are provided. Examples are shown below












Case: Null input









User Input
System Response
Comment





With an empty field
Find restaurants,
Black text would be


and no dialog context,
hotels, movies, . . .
inserted into the


type a question or
Book a table, a room,
input field. Italicized


space character, or
a seat, . . .
text would be the


enter nothing for
Order food, flowers, . . .
follow-up suggestions


some period of time.
Buy a ticket, a book,
once the text was



a DVD, . . .
inserted.



Schedule a meeting,




an event, . . .




Remember to a thing




to do . . .




Explain results



















Case: First word input









User Input
System Response
Comment





With empty dialog

Find restaurants,

Black text would be


context If the user
hotels, movies, . . .
inserted into the


types the first

input would be the


letter of any

follow-up suggestions


command, it is

once the text was


suggested. For

inserted


example




 F |



















Case: Key word input









User Input
System Response
Comment





With empty dialog

Remember to a thing,

Black text would be


context If the user
to do . . .
inserted into the


types the first two
Find restaurants by
input field. Italicized


letters of any
location, cuisine,
text would be the


keyword, it is

follow-up suggestions


suggested as well

once the text was


as command. For

inserted.


example


 F |



















Case: Prompting for arguments









User Input
System Response
Comment





The user has entered
restaurants by location,
Offer not only the


or selected a
cuisine, . . .
selection class but


“command” verb
hotels by location,
advertise the


and nothing else. For
availability, . . .
constraint options.


example
movies by location,
Note that name of


 Find_|
genre, . . .
place is a just a



name of place
prompt, and would




not insert text.



















Case: Suggesting criteria









User Input
System Response
Comment





The user has already
in city, zip code
Black text would be


entered enough to
near home, office,
inserted into the


establish a task and
place name
input field. Italicized


domain, and now is
named restaurant
text would be the


prompted for
name
follow-up suggestions


constraints in order.

once the text was


find restaurants_|

inserted.



















Case: Adding Criteria









User Input
System Response
Comment





The user has said “in”
in city, zip code
Until they enter the


and now is prompted
Palo Alto, CA
next word, the


for locations
Menlo Park, CA
suggestions are a


Find restaurants in_|

prompt for what kind


The user has said
my home
of thing to type. The


“near” and now
my work
Places are cities from


is prompted for
Palo Alto, CA
personal memory.


locations
Menlo Park, CA
The Places are none


Find restaurants

or more places from


near_|

personal memory



















Case: Adding location or other constraints









User Input
System Response
Comment





Find restaurants in
serving food type or
Prompt for other


Palo Alto_|
cuisine
constraints


Find restaurants in
with availability tonight,
The 7:00 and 9:00


Palo Alto with
tomorrow, . . .
are our suggestions


availability_|
described as romantic,
based on current time



good service



tonight



tomorrow



at 7pm



at 9pm



other time or date



















Case: Starting from constraint, unknown task or domain











User Input
System Response
Comment







romantic_|
restaurants by location,
Constraint value from




cuisine, . . .
ontology tells you




hotels by location,
which selection




availability, . . .
classes to use




movies by location,




genre, . . .



comedy_|
movies by location,
“comedy” is a




genre, . . .
constraint value for




events by location, . . .
genre in movies, a




clubs by location
genre in events, and





“comedy clubs” is





a local directory





business category











Example: Name Completion.


Here, the user has typed some text without accepting any of the commands, or he or she is just extending a command with an entity name. The system may attempt to complete the names, depending on context. It also disambiguates the domain.












Case: words without context









User Input
System Response
Comment





il for
Il Fornaio (restaurant)
May require entity name




lookup



Ill Forgotten Gains
Notice multi-word completion



(movie)
Show domain as a suggestion.


tom cruise
movies
May require entity name


romantic
movies
lookup



restaurants
Based on ontology only



















Case: name with context









User Input
System Response
Comment





Find restaurants i|
Il Fornaio (restaurant)
May require entity name


for

lookup




Uses selection class and




location context from current




and past queries to constrain




completion. Show domain as




a suggestion.


tom cruise
movies
May require entity name




lookup


Find movies rom
romantic
Based on ontology only



Roman Holiday



(movie)


g-rated
movies










Example: Choosing Values from a Set


Here, the user is responding to a system request to enter a value for a specific parameter, such as location, time, cuisine, or genre. The user may either select from a list or enter a value. As she types, matching items from the list are shown as options. Examples are shown below.












Case: valueless selection









User Input
System Response
Comment





Restaurants
burgers
User may type anything else and


serving
Ice cream
doesn't have to pick from the menu



Hot dogs


Restaurants
Hamburgers


serving h
Hot dogs



Hot sauce


Movies playing
today



tonight



Friday night










Example: Reusing Previous Commands


Previous queries are also options to complete on in an autocomplete interface. They may be just matched as strings (when the input field is empty and there are no known constraints) or they may be suggested as relevant when in certain situations.












Case: completion on previous queries









User Input
System Response
Comment





Intel

Italian restaurants (normal completion)

Using string



Films starring Italian actors (recent
matching to retrieve



query)
previous queries


Lunch
lunch places in marin (recent query)



buy the book naked lunch










Example: Retrieving Personal Memory Items


Assistant 1002 may remember certain events and/or entities in personal memory associated with the user. Autocomplete can be performed based on such remembered items. Examples appear below.












Case: completion on events and entities in personal memory









User Input
System Response
Comment











Mary
lunch with Mary on Saturday



(from My Events)



film called “Something about Mary


Lunch
lunch with Mary on Saturday



(from My Events)



buy the book naked lunch (from My Todos)


Hob
Hobee's Restaurant in Palo Alto



(from My Restaurants)










Multimodal Active Input Elicitation


In at least one embodiment, active input elicitation component(s) 1094 may process input from a plurality of input modalities. At least one modality might be implemented with an active input elicitation procedure that takes advantages of the particular kinds of inputs and methods for selecting from suggested options. A described herein, they may be embodiments of procedures for active input elicitation for text input, speech input, GUI-based input, input in the context of a dialog, and/or input resulting from event triggers.


In at least one embodiment, for a single instance of intelligent automated assistant 1002, there may be support for one or more (or any combination of) typed input, speech input, GUI input, dialog input, and/or event input.


Referring now to FIG. 26, there is shown a flow diagram depicting a method for multimodal active input elicitation according to one embodiment. The method begins 100. Inputs may be received concurrently from one or more or any combination of the input modalities, in any sequence. Thus, the method includes actively eliciting typed input 2610, speech input 2620, GUI-based input 2640, input in the context of a dialog 2650, and/or input resulting from event triggers 2660. Any or all of these input sources are unified into unified input format 2690 and returned. Unified input format 2690 enables the other components of intelligent automated assistant 1002 to be designed and to operate independently of the particular modality of the input.


Offering active guidance for multiple modalities and levels enables constraint and guidance on the input beyond those available to isolated modalities. For example, the kinds of suggestions offered to choose among speech, text, and dialog steps are independent, so their combination is a significant improvement over adding active elicitation techniques to individual modalities or levels.


Combining multiple sources of constraints as described herein (syntactic/linguistic, vocabulary, entity databases, domain models, task models, service models, and the like) and multiple places where these constraints may be actively applied (speech, text, GUI, dialog, and asynchronous events) provides a new level of functionality for human-machine interaction.


Domain Models Component(s) 1056


Domain models 1056 component(s) include representations of the concepts, entities, relations, properties, and instances of a domain. For example, dining out domain model 1622 might include the concept of a restaurant as a business with a name and an address and phone number, the concept of a meal event with a party size and date and time associated with the restaurant.


In at least one embodiment, domain models component(s) 1056 of assistant 1002 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Domain model component(s) 1056 may be used by automated assistant 1002 for several processes, including: eliciting input 100, interpreting natural language 200, dispatching to services 400, and generating output 600.
    • Domain model component(s) 1056 may provide lists of words that might match a domain concept or entity, such as names of restaurants, which may be used for active elicitation of input 100 and natural language processing 200.
    • Domain model component(s) 1056 may classify candidate words in processes, for instance, to determine that a word is the name of a restaurant.
    • Domain model component(s) 1056 may show the relationship between partial information for interpreting natural language, for example that cuisine may be associated with business entities (e.g., “local Mexican food” may be interpreted as “find restaurants with style=Mexican”, and this inference is possible because of the information in domain model 1056).
    • Domain model component(s) 1056 may organize information about services used in service orchestration 1082, for example, that a particular web service may provide reviews of restaurants.
    • Domain model component(s) 1056 may provide the information for generating natural language paraphrases and other output formatting, for example, by providing canonical ways of describing concepts, relations, properties and instances.


According to specific embodiments, multiple instances or threads of the domain models component(s) 1056 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of domain models component(s) 1056 may be performed, implemented and/or initiated by one or more of the following types of systems, components, systems, devices, procedures, processes, and the like (or combinations thereof):

    • Domain models component(s) 1056 may be implemented as data structures that represent concepts, relations, properties, and instances. These data structures may be stored in memory, files, or databases.
    • Access to domain model component(s) 1056 may be implemented through direct APIs, network APIs, database query interfaces, and/or the like.
    • Creation and maintenance of domain models component(s) 1056 may be achieved, for example, via direct editing of files, database transactions, and/or through the use of domain model editing tools.
    • Domain models component(s) 1056 may be implemented as part of or in association with active ontologies 1050, which combine models with instantiations of the models for servers and users.


According to various embodiments, one or more different threads or instances of domain models component(s) 1056 may be initiated in response to detection of one or more conditions or events satisfying one or more different types of minimum threshold criteria for triggering initiation of at least one instance of domain models component(s) 1056. For example, trigger initiation and/or implementation of one or more different threads or instances of domain models component(s) 1056 may be triggered when domain model information is required, including during input elicitation, input interpretation, task and domain identification, natural language processing, service orchestration, and/or formatting output for users.


In at least one embodiment, a given instance of domain models component(s) 1056 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. For example, data from domain model component(s) 1056 may be associated with other model modeling components including vocabulary 1058, language pattern recognizers 1060, dialog flow models 1087, task flow models 1086, service capability models 1088, domain entity databases 1072, and the like. For example, businesses in domain entity databases 1072 that are classified as restaurants might be known by type identifiers which are maintained in the dining out domain model components.


Domain Models Component(s) Example


Referring now to FIG. 27, there is shown a set of screen shots illustrating an example of various types of functions, operations, actions, and/or other features which may be provided by domain models component(s) 1056 according to one embodiment.


In at least one embodiment, domain models component(s) 1056 are the unifying data representation that enables the presentation of information shown in screens 103A and 103B about a restaurant, which combines data from several distinct data sources and services and which includes, for example: name, address, business categories, phone number, identifier for saving to long term personal memory, identifier for sharing over email, reviews from multiple sources, map coordinates, personal notes, and the like.


Language Interpreter Component(s) 1070


In at least one embodiment, language interpreter component(s) 1070 of assistant 1002 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Analyze user input and identify a set of parse results.
      • User input can include any information from the user and his/her device context that can contribute to understanding the user's intent, which can include, for example one or more of the following (or combinations thereof): sequences of words, the identity of gestures or GUI elements involved in eliciting the input, current context of the dialog, current device application and its current data objects, and/or any other personal dynamic data obtained about the user such as location, time, and the like. For example, in one embodiment, user input is in the form of the uniform annotated input format 2690 resulting from active input elicitation 1094.
      • Parse results are associations of data in the user input with concepts, relationships, properties, instances, and/or other nodes and/or data structures in models, databases, and/or other representations of user intent and/context. Parse result associations can be complex mappings from sets and sequences of words, signals, and other elements of user input to one or more associated concepts, relations, properties, instances, other nodes, and/or data structures described herein.
    • Analyze user input and identify a set of syntactic parse results, which are parse results that associate data in the user input with structures that represent syntactic parts of speech, clauses and phrases including multiword names, sentence structure, and/or other grammatical graph structures. Syntactic parse results are described in element 212 of natural language processing procedure described in connection with FIG. 28.
    • Analyze user input and identify a set of semantic parse results, which are parse results that associate data in the user input with structures that represent concepts, relationships, properties, entities, quantities, propositions, and/or other representations of meaning and user intent. In one embodiment, these representations of meaning and intent are represented by sets of and/or elements of and/or instances of models or databases and/or nodes in ontologies, as described in element 220 of natural language processing procedure described in connection with FIG. 28.
    • Disambiguate among alternative syntactic or semantic parse results as described in element 230 of natural language processing procedure described in connection with FIG. 28.
    • Determine whether a partially typed input is syntactically and/or semantically meaningful in an autocomplete procedure such as one described in connection with FIG. 11.
    • Help generate suggested completions 114 in an autocomplete procedure such as one described in connection with FIG. 11.
    • Determine whether interpretations of spoken input are syntactically and/or semantically meaningful in a speech input procedure such as one described in connection with FIG. 22.


According to specific embodiments, multiple instances or threads of language interpreter component(s) 1070 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software.


According to different embodiments, one or more different threads or instances of language interpreter component(s) 1070 may be initiated in response to detection of one or more conditions or events satisfying one or more different types of minimum threshold criteria for triggering initiation of at least one instance of language interpreter component(s) 1070. Various examples of conditions or events which may trigger initiation and/or implementation of one or more different threads or instances of language interpreter component(s) 1070 may include, but are not limited to, one or more of the following (or combinations thereof):

    • while eliciting input, including but not limited to
      • Suggesting possible completions of typed input 114 (FIG. 11);
      • Ranking interpretations of speech 126 (FIG. 22);
      • When offering ambiguities as suggested responses in dialog 152 (FIG. 24);
    • when the result of eliciting input is available, including when input is elicited by any mode of active multimodal input elicitation 100.


In at least one embodiment, a given instance of language interpreter component(s) 1070 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of such data-base information may be accessed via communication with one or more local and/or remote memory devices. Examples of different types of data which may be accessed by the Language Interpreter component(s) may include, but are not limited to, one or more of the following (or combinations thereof):

    • Domain models 1056;
    • Vocabulary 1058;
    • Domain entity databases 1072;
    • Short term memory 1052;
    • Long term personal memory 1054;
    • Task flow models 1086;
    • Dialog flow models 1087;
    • Service capability models 1088.


Referring now also to FIG. 29, there is shown a screen shot illustrating natural language processing according to one embodiment. The user has entered (via voice or text) language input 2902 consisting of the phrase “who is playing this weekend at the fillmore.” This phrase is echoed back to the user on screen 2901. Language interpreter component(s) 1070 component process input 2902 and generates a parse result. The parse result associates that input with a request to show the local events that are scheduled for any of the upcoming weekend days at any event venue whose name matches “fillmore.” A paraphrase of the parse results is shown as 2903 on screen 2901.


Referring now also to FIG. 28, there is shown a flow diagram depicting an example of a method for natural language processing according to one embodiment.


The method begins 200. Language input 202 is received, such as the string “who is playing this weekend at the fillmore” in the example of FIG. 29. In one embodiment, the input is augmented by current context information, such as the current user location and local time. In word/phrase matching 210, language interpreter component(s) 1070 find associations between user input and concepts. In this example, associations are found between the string “playing” and the concept of listings at event venues; the string “this weekend” (along with the current local time of the user) and an instantiation of an approximate time period that represents the upcoming weekend; and the string “fillmore” with the name of a venue. Word/phrase matching 210 may use data from, for example, language pattern recognizers 1060, vocabulary database 1058, active ontology 1050, short term personal memory 1052, and long term personal memory 1054.


Language interpreter component(s) 1070 generate candidate syntactic parses 212 which include the chosen parse result but may also include other parse results. For example, other parse results may include those wherein “playing” is associated with other domains such as games or with a category of event such as sporting events.


Short- and/or long-term memory 1052, 1054 can also be used by language interpreter component(s) 1070 in generating candidate syntactic parses 212. Thus, input that was provided previously in the same session, and/or known information about the user, can be used, to improve performance, reduce ambiguity, and reinforce the conversational nature of the interaction. Data from active ontology 1050, domain models 1056, and task flow models 1086 can also be used, to implement evidential reasoning in determining valid candidate syntactic parses 212.


In semantic matching 220, language interpreter component(s) 1070 consider combinations of possible parse results according to how well they fit semantic models such as domain models and databases. In this case, the parse includes the associations (1) “playing” (a word in the user input) as “Local Event At Venue” (part of a domain model 1056 represented by a cluster of nodes in active ontology 1050) and (2) “fillmore” (another word in the input) as a match to an entity name in a domain entity database 1072 for Local Event Venues, which is represented by a domain model element and active ontology node (Venue Name).


Semantic matching 220 may use data from, for example, active ontology 1050, short term personal memory 1052, and long term personal memory 1054. For example, semantic matching 220 may use data from previous references to venues or local events in the dialog (from short term personal memory 1052) or personal favorite venues (from long term personal memory 1054).


A set of candidate, or potential, semantic parse results is generated 222.


In disambiguation step 230, language interpreter component(s) 1070 weigh the evidential strength of candidate semantic parse results 222. In this example, the combination of the parse of “playing” as “Local Event At Venue” and the match of “fillmore” as a Venue Name is a stronger match to a domain model than alternative combinations where, for instance, “playing” is associated with a domain model for sports but there is no association in the sports domain for “fillmore”.


Disambiguation 230 may use data from, for example, the structure of active ontology 1050. In at least one embodiment, the connections between nodes in an active ontology provide evidential support for disambiguating among candidate semantic parse results 222. For example, in one embodiment, if three active ontology nodes are semantically matched and are all connected in active ontology 1050, this indicates higher evidential strength of the semantic parse than if these matching nodes were not connected or connected by longer paths of connections in active ontology 1050. For example, in one embodiment of semantic matching 220, the parse that matches both Local Event At Venue and Venue Name is given increased evidential support because the combined representations of these aspects of the user intent are connected by links and/or relations in active ontology 1050: in this instance, the Local Event node is connected to the Venue node which is connected to the Venue Name node which is connected to the entity name in the database of venue names.


In at least one embodiment, the connections between nodes in an active ontology that provide evidential support for disambiguating among candidate semantic parse results 222 are directed arcs, forming an inference lattice, in which matching nodes provide evidence for nodes to which they are connected by directed arcs.


In 232, language interpreter component(s) 1070 sort and select 232 the top semantic parses as the representation of user intent 290.


Domain Entity Database(s) 1072


In at least one embodiment, domain entity database(s) 1072 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Store data about domain entities. Domain entities are things in the world or computing environment that may be modeled in domain models. Examples may include, but are not limited to, one or more of the following (or combinations thereof):
      • Businesses of any kind;
      • Movies, videos, songs and/or other musical products, and/or any other named entertainment products;
      • Products of any kind;
      • Events;
      • Calendar entries;
      • Cities, states, countries, neighborhoods, and/or other geographic, geopolitical, and/or geospatial points or regions;
      • Named places such as landmarks, airports, and the like;
    • Provide database services on these databases, including but not limited to simple and complex queries, transactions, triggered events, and the like.


According to specific embodiments, multiple instances or threads of domain entity database(s) 1072 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of domain entity database(s) 1072 may be performed, implemented and/or initiated by database software and/or hardware residing on client(s) 1304 and/or on server(s) 1340.


One example of a domain entity database 1072 that can be used in connection with the present invention according to one embodiment is a database of one or more businesses storing, for example, their names and locations. The database might be used, for example, to look up words contained in an input request for matching businesses and/or to look up the location of a business whose name is known. One skilled in the art will recognize that many other arrangements and implementations are possible.


Vocabulary Component(s) 1058


In at least one embodiment, vocabulary component(s) 1058 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof).

    • Provide databases associating words and strings with concepts, properties, relations, or instances of domain models or task models;
    • Vocabulary from vocabulary components may be used by automated assistant 1002 for several processes, including for example: eliciting input, interpreting natural language, and generating output.


According to specific embodiments, multiple instances or threads of vocabulary component(s) 1058 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of vocabulary component(s) 1058 may be implemented as data structures that associate strings with the names of concepts, relations, properties, and instances. These data structures may be stored in memory, files, or databases. Access to vocabulary component(s) 1058 may be implemented through direct APIs, network APIs, and/or database query interfaces. Creation and maintenance of vocabulary component(s) 1058 may be achieved via direct editing of files, database transactions, or through the use of domain model editing tools. Vocabulary component(s) 1058 may be implemented as part of or in association with active ontologies 1050. One skilled in the art will recognize that many other arrangements and implementations are possible.


According to different embodiments, one or more different threads or instances of vocabulary component(s) 1058 may be initiated in response to detection of one or more conditions or events satisfying one or more different types of minimum threshold criteria for triggering initiation of at least one instance of vocabulary component(s) 1058. In one embodiment, vocabulary component(s) 1058 are accessed whenever vocabulary information is required, including, for example, during input elicitation, input interpretation, and formatting output for users. One skilled in the art will recognize that other conditions or events may trigger initiation and/or implementation of one or more different threads or instances of vocabulary component(s) 1058.


In at least one embodiment, a given instance of vocabulary component(s) 1058 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. In one embodiment, vocabulary component(s) 1058 may access data from external databases, for instance, from a data warehouse or dictionary.


Language Pattern Recognizer Component(s) 1060


In at least one embodiment, language pattern recognizer component(s) 1060 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, looking for patterns in language or speech input that indicate grammatical, idiomatic, and/or other composites of input tokens. These patterns correspond to, for example, one or more of the following (or combinations thereof): words, names, phrases, data, parameters, commands, and/or signals of speech acts.


According to specific embodiments, multiple instances or threads of pattern recognizer component(s) 1060 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of language pattern recognizer component(s) 1060 may be performed, implemented and/or initiated by one or more files, databases, and/or programs containing expressions in a pattern matching language. In at least one embodiment, language pattern recognizer component(s) 1060 are represented declaratively, rather than as program code; this enables them to be created and maintained by editors and other tools other than programming tools. Examples of declarative representations may include, but are not limited to, one or more of the following (or combinations thereof): regular expressions, pattern matching rules, natural language grammars, parsers based on state machines and/or other parsing models.


One skilled in the art will recognize that other types of systems, components, systems, devices, procedures, processes, and the like (or combinations thereof) can be used for implementing language pattern recognizer component(s) 1060.


According to different embodiments, one or more different threads or instances of language pattern recognizer component(s) 1060 may be initiated in response to detection of one or more conditions or events satisfying one or more different types of minimum threshold criteria for triggering initiation of at least one instance of language pattern recognizer component(s) 1060. Various examples of conditions or events which may trigger initiation and/or implementation of one or more different threads or instances of language pattern recognizer component(s) 1060 may include, but are not limited to, one or more of the following (or combinations thereof):

    • during active elicitation of input, in which the structure of the language pattern recognizers may constrain and guide the input from the user;
    • during natural language processing, in which the language pattern recognizers help interpret input as language;
    • during the identification of tasks and dialogs, in which the language pattern recognizers may help identify tasks, dialogs, and/or steps therein.


In at least one embodiment, a given instance of language pattern recognizer component(s) 1060 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. Examples of different types of data which may be accessed by language pattern recognizer component(s) 1060 may include, but are not limited to, data from any of the models various models and data sources that may be part of embodiments of assistant 1002, which may include, but are not limited to, one or more of the following (or combinations thereof):

    • Domain models 1056;
    • Vocabulary 1058;
    • Domain entity databases 1072;
    • Short term memory 1052;
    • Long term personal memory 1054;
    • Task flow models 1086;
    • Dialog flow models 1087;
    • Service capability models 1088.


In one embodiment, access of data from other parts of embodiments of assistant 1002 may be coordinated by active ontologies 1050.


Referring again to FIG. 14, there is shown an example of some of the various types of functions, operations, actions, and/or other features which may be provided by language pattern recognizer component(s) 1060. FIG. 14 illustrates language patterns that language pattern recognizer component(s) 1060 may recognize. For example, the idiom “what is happening” (in a city) may be associated with the task of event planning and the domain of local events.


Dialog Flow Processor Component(s) 1080


In at least one embodiment, dialog flow processor component(s) 1080 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Given a representation of the user intent 290 from language interpretation 200, identify the task a user wants performed and/or a problem the user wants solved. For example, a task might be to find a restaurant.
    • For a given problem or task, given a representation of user intent 290, identify parameters to the task or problem. For example, the user might be looking for a recommended restaurant that serves Italian food near the user's home. The constraints that a restaurant be recommended, serving Italian food, and near home are parameters to the task of finding a restaurant.
    • Given the task interpretation and current dialog with the user, such as that which may be represented in personal short term memory 1052, select an appropriate dialog flow model and determine a step in the flow model corresponding to the current state.


According to specific embodiments, multiple instances or threads of dialog flow processor component(s) 1080 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software.


In at least one embodiment, a given instance of dialog flow processor component(s) 1080 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. Examples of different types of data which may be accessed by dialog flow processor component(s) 1080 may include, but are not limited to, one or more of the following (or combinations thereof):

    • task flow models 1086;
    • domain models 1056;
    • dialog flow models 1087.


Referring now to FIGS. 30 and 31, there are shown screen shots illustrating an example of various types of functions, operations, actions, and/or other features which may be provided by dialog flow processor component(s) according to one embodiment.


As shown in screen 3001, user requests a dinner reservation by providing speech or text input “book me a table for dinner.” Assistant 1002 generates a prompt 3003 asking the user to specify time and party size.


Once these parameters have been provided, screen 3101 is shown. Assistant 1002 outputs a dialog box 3102 indicating that results are being presented, and a prompt 3103 asking the user to click a time. Listings 3104 are also displayed.


In one embodiment, such a dialog is implemented as follows. Dialog flow processor component(s) 1080 are given a representation of user intent from language interpreter component 1070 and determine that the appropriate response is to ask the user for information required to perform the next step in a task flow. In this case, the domain is restaurants, the task is getting a reservation, and the dialog step is to ask the user for information required to accomplish the next step in the task flow. This dialog step is exemplified by prompt 3003 of screen 3001.


Referring now also to FIG. 32, there is shown a flow diagram depicting a method of operation for dialog flow processor component(s) 1080 according to one embodiment. The flow diagram of FIG. 32 is described in connection with the example shown in FIGS. 30 and 31.


The method begins 200. Representation of user intent 290 is received. As described in connection with FIG. 28, in one embodiment, representation of user intent 290 is a set of semantic parses. For the example shown in FIGS. 30 and 31, the domain is restaurants, the verb is “book” associated with restaurant reservations, and the time parameter is the evening of the current day.


In 310, dialog flow processor component(s) 1080 determine whether this interpretation of user intent is supported strongly enough to proceed, and/or if it is better supported than alternative ambiguous parses. In the current example, the interpretation is strongly supported, with no competing ambiguous parses. If, on the other hand, there are competing ambiguities or sufficient uncertainty, then step 322 is performed, to set the dialog flow step so that the execution phase causes the dialog to output a prompt for more information from the user.


In 312, the dialog flow processor component(s) 1080 determine the preferred interpretation of the semantic parse with other information to determine the task to perform and its parameters. Information may be obtained, for example, from domain models 1056, task flow models 1086, and/or dialog flow models 1087, or any combination thereof. In the current example, the task is identified as getting a reservation, which involves both finding a place that is reservable and available, and effecting a transaction to reserve a table. Task parameters are the time constraint along with others that are inferred in step 312.


In 320, the task flow model is consulted to determine an appropriate next step. Information may be obtained, for example, from domain models 1056, task flow models 1086, and/or dialog flow models 1087, or any combination thereof. In the example, it is determined that in this task flow the next step is to elicit missing parameters to an availability search for restaurants, resulting in prompt 3003 illustrated in FIG. 30, requesting party size and time for a reservation.


As described above, FIG. 31 depicts screen 3101 is shown including dialog element 3102 that is presented after the user answers the request for the party size and reservation time. In one embodiment, screen 3101 is presented as the result of another iteration through an automated call and response procedure, as described in connection with FIG. 33, which leads to another call to the dialog and flow procedure depicted in FIG. 32. In this instantiation of the dialog and flow procedure, after receiving the user preferences, dialog flow processor component(s) 1080 determines a different task flow step in step 320: to do an availability search. When request 390 is constructed, it includes the task parameters sufficient for dialog flow processor component(s) 1080 and services orchestration component(s) 1082 to dispatch to a restaurant booking service.


Dialog Flow Models Component(s) 1087


In at least one embodiment, dialog flow models component(s) 1087 may be operable to provide dialog flow models, which represent the steps one takes in a particular kind of conversation between a user and intelligent automated assistant 1002. For example, the dialog flow for the generic task of performing a transaction includes steps for getting the necessary data for the transaction and confirming the transaction parameters before committing it.


Task Flow Models Component(s) 1086


In at least one embodiment, task flow models component(s) 1086 may be operable to provide task flow models, which represent the steps one takes to solve a problem or address a need. For example, the task flow for getting a dinner reservation involves finding a desirable restaurant, checking availability, and doing a transaction to get a reservation for a specific time with the restaurant.


According to specific embodiments, multiple instances or threads of task flow models component(s) 1086 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of task flow models component(s) 1086 may be implemented as programs, state machines, or other ways of identifying an appropriate step in a flow graph.


In at least one embodiment, task flow models component(s) 1086 may use a task modeling framework called generic tasks. Generic tasks are abstractions that model the steps in a task and their required inputs and generated outputs, without being specific to domains. For example, a generic task for transactions might include steps for gathering data required for the transaction, executing the transaction, and outputting results of the transaction—all without reference to any particular transaction domain or service for implementing it. It might be instantiated for a domain such as shopping, but it is independent of the shopping domain and might equally well apply to domains of reserving, scheduling, and the like.


At least a portion of the functions, operations, actions, and/or other features associated with task flow models component(s) 1086 and/or procedure(s) described herein may be implemented, at least in part, using concepts, features, components, processes, and/or other aspects disclosed herein in connection with generic task modeling framework.


Additionally, at least a portion of the functions, operations, actions, and/or other features associated with task flow models component(s) 1086 and/or procedure(s) described herein may be implemented, at least in part, using concepts, features, components, processes, and/or other aspects relating to constrained selection tasks, as described herein. For example, one embodiment of generic tasks may be implemented using a constrained selection task model.


In at least one embodiment, a given instance of task flow models component(s) 1086 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. Examples of different types of data which may be accessed by task flow models component(s) 1086 may include, but are not limited to, one or more of the following (or combinations thereof):

    • Domain models 1056.
    • Vocabulary 1058;
    • Domain entity databases 1072;
    • Short term memory 1052;
    • Long term personal memory 1054;
    • Dialog flow models 1087;
    • Service capability models 1088.


Referring now to FIG. 34, there is shown a flow diagram depicting an example of task flow for a constrained selection task 351 according to one embodiment.


Constrained selection is a kind of generic task in which the goal is to select some item from a set of items in the world based on a set of constraints. For example, a constrained selection task 351 may be instantiated for the domain of restaurants. Constrained selection task 351 starts by soliciting criteria and constraints from the user 352. For example, the user might be interested in Asian food and may want a place to eat near his or her office.


In step 353, assistant 1002 presents items that meet the stated criteria and constraints for the user to browse. In this example, it may be a list of restaurants and their properties which may be used to select among them.


In step 354, the user is given an opportunity to refine criteria and constraints. For example, the user might refine the request by saying “near my office.” The system would then present a new set of results in step 353.


Referring now also to FIG. 35, there is shown an example of screen 3501 including list 3502 of items presented by constrained selection task 351 according to one embodiment.


In step 355, the user can select among the matching items. Any of a number of follow-on tasks 359 may then be made available, such as for example book 356, remember 357, or share 358. In various embodiments, follow-on tasks 359 can involve interaction with web-enabled services, and/or with functionality local to the device (such as setting a calendar appointment, making a telephone call, sending an email or text message, setting an alarm, and the like).


In the example of FIG. 35, the user can select an item within list 3502 to see more details and to perform additional actions. Referring now also to FIG. 36, there is shown an example of screen 3601 after the user has selected an item from list 3502. Additional information and options corresponding to follow-on tasks 359 concerning the selected item are displayed.


In various embodiments, the flow steps may be offered to the user in any of several input modalities, including but not limited to any combination of explicit dialog prompts and GUI links.


Services Component(s) 1084


Services component(s) 1084 represent the set of services that intelligent automated assistant 1002 might call on behalf of the user. Any service that can be called may be offered in a services component 1084.


In at least one embodiment, services component(s) 1084 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Provide the functions over an API that would normally be provided by a web-based user interface to a service. For example, a review website might provide a service API that would return reviews of a given entity automatically when called by a program. The API offers to intelligent automated assistant 1002 the services that a human would otherwise obtain by operating the user interface of the website.
    • Provide the functions over an API that would normally be provided by a user interface to an application. For example, a calendar application might provide a service API that would return calendar entries automatically when called by a program. The API offers to intelligent automated assistant 1002 the services that a human would otherwise obtain by operating the user interface of the application. In one embodiment, assistant 1002 is able to initiate and control any of a number of different functions available on the device. For example, if assistant 1002 is installed on a smartphone, personal digital assistant, tablet computer, or other device, assistant 1002 can perform functions such as: initiate applications, make calls, send emails and/or text messages, add calendar events, set alarms, and the like. In one embodiment, such functions are activated using services component(s) 1084.
    • Provide services that are not currently implemented in a user interface, but that are available through an API to assistant in larger tasks. For example, in one embodiment, an API to take a street address and return machine-readable geocoordinates might be used by assistant 1002 as a service component 1084 even if it has no direct user interface on the web or a device.


According to specific embodiments, multiple instances or threads of services component(s) 1084 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of services component(s) 1084 may be performed, implemented and/or initiated by one or more of the following types of systems, components, systems, devices, procedures, processes, and the like (or combinations thereof):

    • implementation of an API exposed by a service, locally or remotely or any combination;
    • inclusion of a database within automated assistant 1002 or a database service available to assistant 1002.


For example, a website that offers users an interface for browsing movies might be used by an embodiment of intelligent automated assistant 1002 as a copy of the database used by the website. Services component(s) 1084 would then offer an internal API to the data, as if it were provided over a network API, even though the data is kept locally.


As another example, services component(s) 1084 for an intelligent automated assistant 1002 that helps with restaurant selection and meal planning might include any or all of the following set of services which are available from third parties over the network:

    • a set of restaurant listing services which lists restaurants matching name, location, or other constraints;
    • a set of restaurant rating services which return rankings for named restaurants;
    • a set of restaurant reviews services which returns written reviews for named restaurants;
    • a geocoding service to locate restaurants on a map;
    • a reservation service that enables programmatic reservation of tables at restaurants.


      Services Orchestration Component(s) 1082


Services orchestration component(s) 1082 of intelligent automated assistant 1002 executes a service orchestration procedure.


In at least one embodiment, services orchestration component(s) 1082 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Dynamically and automatically determine which services may meet the user's request and/or specified domain(s) and task(s);
    • Dynamically and automatically call multiple services, in any combination of concurrent and sequential ordering;
    • Dynamically and automatically transform task parameters and constraints to meet input requirements of service APIs;
    • Dynamically and automatically monitor for and gather results from multiple services;
    • Dynamically and automatically merge service results data from various services into to a unified result model;
    • Orchestrate a plurality of services to meet the constraints of a request;
    • Orchestrate a plurality of services to annotate an existing result set with auxiliary information;
    • Output the result of calling a plurality of services in a uniform, service independent representation that unifies the results from the various services (for example, as a result of calling several restaurant services that return lists of restaurants, merge the data on at least one restaurant from the several services, removing redundancy).


For example, in some situations, there may be several ways to accomplish a particular task. For example, user input such as “remind me to leave for my meeting across town at 2 pm” specifies an action that can be accomplished in at least three ways: set alarm clock; create a calendar event; or call a to-do manager. In one embodiment, services orchestration component(s) 1082 makes the determination as to which way to best satisfy the request.


Services orchestration component(s) 1082 can also make determinations as to which combination of several services would be best to invoke in order to perform a given overall task. For example, to find and reserve a table for dinner, services orchestration component(s) 1082 would make determinations as to which services to call in order to perform such functions as looking up reviews, getting availability, and making a reservation. Determination of which services to use may depend on any of a number of different factors. For example, in at least one embodiment, information about reliability, ability of service to handle certain types of requests, user feedback, and the like, can be used as factors in determining which service(s) is/are appropriate to invoke.


According to specific embodiments, multiple instances or threads of services orchestration component(s) 1082 may be concurrently implemented and/or initiated via the use of one or more processors and/or other combinations of hardware and/or hardware and software.


In at least one embodiment, a given instance of services orchestration component(s) 1082 may use explicit service capability models 1088 to represent the capabilities and other properties of external services, and reason about these capabilities and properties while achieving the features of services orchestration component(s) 1082. This affords advantages over manually programming a set of services that may include, for example, one or more of the following (or combinations thereof):

    • Ease of development;
    • Robustness and reliability in execution;
    • The ability to dynamically add and remove services without disrupting code;
    • The ability to implement general distributed query optimization algorithms that are driven by the properties and capabilities rather than hard coded to specific services or APIs.


In at least one embodiment, a given instance of services orchestration component(s) 1082 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. Examples of different types of data which may be accessed by services orchestration component(s) 1082 may include, but are not limited to, one or more of the following (or combinations thereof):

    • Instantiations of domain models;
    • Syntactic and semantic parses of natural language input;
    • Instantiations of task models (with values for parameters);
    • Dialog and task flow models and/or selected steps within them;
    • Service capability models 1088;
    • Any other information available in an active ontology 1050.


Referring now to FIG. 37, there is shown an example of a procedure for executing a service orchestration procedure according to one embodiment.


In this particular example, it is assumed a single user is interesting in finding a good place for dinner at a restaurant, and is engaging intelligent automated assistant 1002 in a conversation to help provide this service.


Consider the task of finding restaurants that are of high quality, are well reviewed, near a particular location, available for reservation at a particular time, and serve a particular kind of food. These domain and task parameters are given as input 390.


The method begins 400. At 402, it is determined whether the given request may require any services. In some situations, services delegation may not be required, for example if assistant 1002 is able to perform the desired task itself. For example, in one embodiment, assistant 1002 may be able to answer a factual question without invoking services delegation. Accordingly, if the request does not require services, then standalone flow step is executed in 403 and its result 490 is returned. For example, if the task request was to ask for information about automated assistant 1002 itself, then the dialog response may be handled without invoking any external services.


If, in step 402, it is determined that services delegation is required, services orchestration component(s) 1082 proceed to step 404. In 404, services orchestration component(s) 1082 may match up the task requirements with declarative descriptions of the capabilities and properties of services in service capability models 1088. At least one service provider that might support the instantiated operation provides declarative, qualitative metadata detailing, for example, one or more of the following (or combinations thereof):

    • the data fields that are returned with results;
    • which classes of parameters the service provider is statically known to support;
    • policy functions for parameters the service provider might be able to support after dynamic inspection of the parameter values;
    • a performance rating defining how the service performs (e.g. relational DB, web service, triple store, full-text index, or some combination thereof);
    • property quality ratings statically defining the expected quality of property values returned with the result object;
    • an overall quality rating of the results the service may expect to return.


For example, reasoning about the classes of parameters that service may support, a service model may state that services 1, 2, 3, and 4 may provide restaurants that are near a particular location (a parameter), services 2 and 3 may filter or rank restaurants by quality (another parameter), services 3, 4, and 5 may return reviews for restaurants (a data field returned), service 6 may list the food types served by restaurants (a data field returned), and service 7 may check availability of restaurants for particular time ranges (a parameter). Services 8 through 99 offer capabilities that are not required for this particular domain and task.


Using this declarative, qualitative metadata, the task, the task parameters, and other information available from the runtime environment of the assistant, services orchestration component(s) 1082 determines 404 an optimal set of service providers to invoke. The optimal set of service providers may support one or more task parameters (returning results that satisfy one or more parameters) and also considers the performance rating of at least one service provider and the overall quality rating of at least one service provider.


The result of step 404 is a dynamically generated list of services to call for this particular user and request.


In at least one embodiment, services orchestration component(s) 1082 considers the reliability of services as well as their ability to answer specific information requests.


In at least one embodiment, services orchestration component(s) 1082 hedges against unreliability by calling overlapping or redundant services.


In at least one embodiment, services orchestration component(s) 1082 considers personal information about the user (from the short term personal memory component) to select services. For example, the user may prefer some rating services over others.


In step 450, services orchestration component(s) 1082 dynamically and automatically invokes multiple services on behalf of a user. In at least one embodiment, these are called dynamically while responding to a user's request. According to specific embodiments, multiple instances or threads of the services may be concurrently called. In at least one embodiment, these are called over a network using APIs, or over a network using web service APIs, or over the Internet using web service APIs, or any combination thereof.


In at least one embodiment, the rate at which services are called is programmatically limited and/or managed.


Referring now also to FIG. 38, there is shown an example of a service invocation procedure 450 according to one embodiment. Service invocation is used, for example, to obtain additional information or to perform tasks by the use of external services. In one embodiment, request parameters are transformed as appropriate for the service's API. Once results are received from the service, the results are transformed to a results representation for presentation to the user within assistant 1002.


In at least one embodiment, services invoked by service invocation procedure 450 can be a web service, application running on the device, operating system function, or the like.


Representation of request 390 is provided, including for example task parameters and the like. For at least one service available from service capability models 1088, service invocation procedure 450 performs transformation 452, calling 454, and output-mapping 456 steps.


In transformation step 452, the current task parameters from request representation 390 are transformed into a form that may be used by at least one service. Parameters to services, which may be offered as APIs or databases, may differ from the data representation used in task requests, and also from at least one other. Accordingly, the objective of step 452 is to map at least one task parameter in the one or more corresponding formats and values in at least one service being called.


For example, the names of businesses such as restaurants may vary across services that deal with such businesses. Accordingly, step 452 would involve transforming any names into forms that are best suited for at least one service.


As another example, locations are known at various levels of precision and using various units and conventions across services. Service 1 might may require ZIP codes, service 2 GPS coordinates, and service 3 postal street addresses.


The service is called 454 over an API and its data gathered. In at least one embodiment, the results are cached. In at least one embodiment, the services that do not return within a specified level performance (e.g., as specified in Service Level Agreement or SLA) are dropped.


In output mapping step 456, the data returned by a service is mapped back onto unified result representation 490. This step may include dealing with different formats, units, and so forth.


In step 412, results from multiple services are validated and merged. In one embodiment, if validated results are collected, an equality policy function—defined on a per-domain basis—is then called pair-wise across one or more results to determine which results represent identical concepts in the real world. When a pair of equal results is discovered, a set of property policy functions—also defined on a per-domain basis—are used to merge property values into a merged result. The property policy function may use the property quality ratings from the service capability models, the task parameters, the domain context, and/or the long-term personal memory 1054 to decide the optimal merging strategy.


For example, lists of restaurants from different providers of restaurants might be merged and duplicates removed. In at least one embodiment, the criteria for identifying duplicates may include fuzzy name matching, fuzzy location matching, fuzzy matching against multiple properties of domain entities, such as name, location, phone number, and/or website address, and/or any combination thereof.


In step 414, the results are sorted and trimmed to return a result list of the desired length.


In at least one embodiment, a request relaxation loop is also applied. If, in step 416, services orchestration component(s) 1082 determines that the current result list is not sufficient (e.g., it has fewer than the desired number of matching items), then task parameters may be relaxed 420 to allow for more results. For example, if the number of restaurants of the desired sort found within N miles of the target location is too small, then relaxation would run the request again, looking in an area larger than N miles away, and/or relaxing some other parameter of the search.


In at least one embodiment, the service orchestration method is applied in a second pass to “annotate” results with auxiliary data that is useful to the task.


In step 418, services orchestration component(s) 1082 determines whether annotation is required. It may be required if, for example, if the task may require a plot of the results on a map, but the primary services did not return geocoordinates required for mapping.


In 422, service capability models 1088 are consulted again to find services that may return the desired extra information. In one embodiment, the annotation process determines if additional or better data may be annotated to a merged result. It does this by delegating to a property policy function—defined on a per-domain basis—for at least one property of at least one merged result. The property policy function may use the merged property value and property quality rating, the property quality ratings of one or more other service providers, the domain context, and/or the user profile to decide if better data may be obtained. If it is determined that one or more service providers may annotate one or more properties for a merged result, a cost function is invoked to determine the optimal set of service providers to annotate.


At least one service provider in the optimal set of annotation service providers is then invoked 450 with the list of merged results, to obtain results 424. The changes made to at least one merged result by at least one service provider are tracked during this process, and the changes are then merged using the same property policy function process as was used in step 412. Their results are merged 426 into the existing result set.


The resulting data is sorted 428 and unified into a uniform representation 490.


It may be appreciated that one advantage of the methods and systems described above with respect to services orchestration component(s) 1082 is that they may be advantageously applied and/or utilized in various fields of technology other than those specifically relating to intelligent automated assistants. Examples of such other areas of technologies where aspects and/or features of service orchestration procedures include, for example, one or more of the following:

    • Dynamic “mash ups” on websites and web-based applications and services;
    • Distributed database query optimization;
    • Dynamic service oriented architecture configuration.


      Service Capability Models Component(s) 1088


In at least one embodiment, service capability models component(s) 1088 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Provide machine readable information about the capabilities of services to perform certain classes of computation;
    • Provide machine readable information about the capabilities of services to answer certain classes of queries;
    • Provide machine readable information about which classes of transactions are provided by various services;
    • Provide machine readable information about the parameters to APIs exposed by various services;
    • Provide machine readable information about the parameters that may be used in database queries on databases provided by various services.


      Output Processor Component(s) 1090


In at least one embodiment, output processor component(s) 1090 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Format output data that is represented in a uniform internal data structure into forms and layouts that render it appropriately on different modalities. Output data may include, for example, communication in natural language between the intelligent automated assistant and the user; data about domain entities, such as properties of restaurants, movies, products, and the like; domain specific data results from information services, such as weather reports, flight status checks, prices, and the like; and/or interactive links and buttons that enable the user to respond by directly interacting with the output presentation.
    • Render output data for modalities that may include, for example, any combination of: graphical user interfaces; text messages; email messages; sounds; animations; and/or speech output.
    • Dynamically render data for different graphical user interface display engines based on the request. For example, use different output processing layouts and formats depending on which web browser and/or device is being used.
    • Render output data in different speech voices dynamically.
    • Dynamically render to specified modalities based on user preferences.
    • Dynamically render output using user-specific “skins” that customize the look and feel.
    • Send a stream of output packages to a modality, showing intermediate status, feedback, or results throughout phases of interaction with assistant 1002.


According to specific embodiments, multiple instances or threads of output processor component(s) 1090 may be concurrently implemented and/or initiated via the use of one or more processor(s) 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of output processor component(s) 1090 may be performed, implemented and/or initiated by one or more of the following types of systems, components, systems, devices, procedures, processes, and the like (or combinations thereof):

    • software modules within the client or server of an embodiment of an intelligent automated assistant;
    • remotely callable services;
    • using a mix of templates and procedural code.


Referring now to FIG. 39, there is shown a flow diagram depicting an example of a multiphase output procedure according to one embodiment. The multiphase output procedure includes automated assistant 1002 processing steps 702 and multiphase output steps 704.


In step 710, a speech input utterance is obtained and a speech-to-text component (such as component described in connection with FIG. 22) interprets the speech to produce a set of candidate speech interpretations 712. In one embodiment, speech-to-text component is implemented using, for example, Nuance Recognizer, available from Nuance Communications, Inc. of Burlington, MA. Candidate speech interpretations 712 may be shown to the user in 730, for example in paraphrased form. For example, the interface might show “did you say?” alternatives listing a few possible alternative textual interpretations of the same speech sound sample.


In at least one embodiment, a user interface is provided to enable the user to interrupt and choose among the candidate speech interpretations.


In step 714, the candidate speech interpretations 712 are sent to a language interpreter 1070, which may produce representations of user intent 716 for at least one candidate speech interpretation 712. In step 732, paraphrases of these representations of user intent 716 are generated and presented to the user. (See related step 132 of procedure 120 in FIG. 22).


In at least one embodiment, the user interface enables the user to interrupt and choose among the paraphrases of natural language interpretations 732.


In step 718, task and dialog analysis is performed. In step 734, task and domain interpretations are presented to the user using an intent paraphrasing algorithm.


Referring now also to FIG. 40, there is shown a screen shot depicting an example of output processing according to one embodiment. Screen 4001 includes echo 4002 of the user's speech input, generated by step 730. Screen 4001 further includes paraphrase 4003 of the user's intent, generated by step 734. In one embodiment, as depicted in the example of FIG. 40, special formatting/highlighting is used for key words such as “events”, which may be used to facilitate training of the user for interaction with intelligent automated assistant 1002. For example, by visually observing the formatting of the displayed text, the user may readily identify and interpret back the intelligent automated assistant recognizes keywords such as “events”, “next Wednesday”, “San Francisco”, and the like.


Returning to FIG. 39, as requests are dispatched 720 to services and results are dynamically gathered, intermediate results may be displayed in the form of real-time progress 736. For example, a list of restaurants may be returned and then their reviews may be populated dynamically as the results from the reviews services arrive. Services can include web-enabled services and/or services that access information stored locally on the device and/or from any other source.


A uniform representation of response 722 is generated and formatted 724 for the appropriate output modality. After the final output format is completed, a different kind of paraphrase may be offered in 738. In this phase, the entire result set may be analyzed and compared against the initial request. A summary of results or answer to a question may then be offered.


Referring also to FIG. 41, there is shown another example of output processing according to one embodiment. Screen 4101 depicts paraphrase 4102 of the text interpretation, generated by step 732, real-time progress 4103 generated by step 736, and paraphrased summary 7104 generated by step 738. Also included are detailed results 4105.


In one embodiment, assistant 1002 is capable of generating output in multiple modes. Referring now to FIG. 42, there is shown a flow diagram depicting an example of multimodal output processing according to one embodiment.


The method begins 600. Output processor 1090 takes uniform representation of response 490 and formats 612 the response according to the device and modality that is appropriate and applicable. Step 612 may include information from device and modality models 610 and/or domain data models 614.


Once response 490 has been formatted 612, any of a number of different output mechanisms can be used, in any combination. Examples depicted in FIG. 42 include:

    • Generating 620 text message output, which is sent 630 to a text message channel;
    • Generating 622 email output, which is sent 632 as an email message;
    • Generating 624 GUI output, which is sent 634 to a device or web browser for rendering;
    • Generating 626 speech output, which is sent 636 to a speech generation module.


One skilled in the art will recognize that many other output mechanisms can be used.


In one embodiment, the content of output messages generated by multi-phase output procedure 700 is tailored to the mode of multimodal output processing 600. For example, if the output modality is speech 626, the language of used to paraphrase user input 730, text interpretations 732, task and domain interpretations 734, progress 736, and/or result summaries 738 may be more or less verbose or use sentences that are easier to comprehend in audible form than in written form. In one embodiment, the language is tailored in the steps of the multiphase output procedure 700; in other embodiments, the multiphase output procedure 700 produces an intermediate result that is further refined into specific language by multimodal output processing 600.


Short Term Personal Memory Component(s) 1052


In at least one embodiment, short term personal memory component(s) 1052 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • Keep a history of the recent dialog between the embodiment of the assistant and the user, including the history of user inputs and their interpretations;
    • Keep a history of recent selections by the user in the GUI, such as which items were opened or explored, which phone numbers were called, which items were mapped, which movie trailers where played, and the like;
    • Store the history of the dialog and user interactions in a database on the client, the server in a user-specific session, or in client session state such as web browser cookies or RAM used by the client;
    • Store the list of recent user requests;
    • Store the sequence of results of recent user requests;
    • Store the click-stream history of UI events, including button presses, taps, gestures, voice activated triggers, and/or any other user input.
    • Store device sensor data (such as location, time, positional orientation, motion, light level, sound level, and the like) which might be correlated with interactions with the assistant.


According to specific embodiments, multiple instances or threads of short term personal memory component(s) 1052 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software.


According to different embodiments, one or more different threads or instances of short term personal memory component(s) 1052 may be initiated in response to detection of one or more conditions or events satisfying one or more different types of minimum threshold criteria for triggering initiation of at least one instance of short term personal memory component(s) 1052. For example, short term personal memory component(s) 1052 may be invoked when there is a user session with the embodiment of assistant 1002, on at least one input form or action by the user or response by the system.


In at least one embodiment, a given instance of short term personal memory component(s) 1052 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. For example, short term personal memory component(s) 1052 may access data from long-term personal memory components(s) 1054 (for example, to obtain user identity and personal preferences) and/or data from the local device about time and location, which may be included in short term memory entries.


Referring now to FIGS. 43A and 43B, there are shown screen shots depicting an example of the use of short term personal memory component(s) 1052 to maintain dialog context while changing location, according to one embodiment. In this example, the user has asked about the local weather, then just says “in new york.” Screen 4301 shows the initial response, including local weather. When the user says “in new york”, assistant 1002 uses short term personal memory component(s) 1052 to access the dialog context and thereby determine that the current domain is weather forecasts. This enables assistant 1002 to interpret the new utterance “in new york” to mean “what is the weather forecast in New York this coming?”. Screen 4302 shows the appropriate response, including weather forecasts for New York.


In the example of FIGS. 43A and 43B, what was stored in short term memory was not only the words of the input “is it going to rain the day after tomorrow?” but the system's semantic interpretation of the input as the weather domain and the time parameter set to the day after tomorrow.


Long-Term Personal Memory Component(s) 1054


In at least one embodiment, long-term personal memory component(s) 1054 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • To persistently store the personal information and data about a user, including for example his or her preferences, identities, authentication credentials, accounts, addresses, and the like;
    • To store information that the user has collected by using the embodiment of assistant 1002, such as the equivalent of bookmarks, favorites, clippings, and the like;
    • To persistently store saved lists of business entities including restaurants, hotels, stores, theaters and other venues. In one embodiment, long-term personal memory component(s) 1054 saves more than just the names or URLs, but also saves the information sufficient to bring up a full listing on the entities including phone numbers, locations on a map, photos, and the like;
    • To persistently store saved movies, videos, music, shows, and other items of entertainment;
    • To persistently store the user's personal calendar(s), to do list(s), reminders and alerts, contact databases, social network lists, and the like;
    • To persistently store shopping lists and wish lists for products and services, coupons and discount codes acquired, and the like;
    • To persistently store the history and receipts for transactions including reservations, purchases, tickets to events, and the like.


According to specific embodiments, multiple instances or threads of long-term personal memory component(s) 1054 may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. For example, in at least some embodiments, various aspects, features, and/or functionalities of long-term personal memory component(s) 1054 may be performed, implemented and/or initiated using one or more databases and/or files on (or associated with) clients 1304 and/or servers 1340, and/or residing on storage devices.


According to different embodiments, one or more different threads or instances of long-term personal memory component(s) 1054 may be initiated in response to detection of one or more conditions or events satisfying one or more different types of minimum threshold criteria for triggering initiation of at least one instance of long-term personal memory component(s) 1054. Various examples of conditions or events which may trigger initiation and/or implementation of one or more different threads or instances of long-term personal memory component(s) 1054 may include, but are not limited to, one or more of the following (or combinations thereof):

    • Long term personal memory entries may be acquired as a side effect of the user interacting with an embodiment of assistant 1002. Any kind of interaction with the assistant may produce additions to the long term personal memory, including browsing, searching, finding, shopping, scheduling, purchasing, reserving, communicating with other people via an assistant.
    • Long term personal memory may also be accumulated as a consequence of users signing up for an account or service, enabling assistant 1002 access to accounts on other services, using an assistant 1002 service on a client device with access to other personal information databases such as calendars, to-do lists, contact lists, and the like.


In at least one embodiment, a given instance of long-term personal memory component(s) 1054 may access and/or utilize information from one or more associated databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices, which may be located, for example, at client(s) 1304 and/or server(s) 1340. Examples of different types of data which may be accessed by long-term personal memory component(s) 1054 may include, but are not limited to data from other personal information databases such as contact or friend lists, calendars, to-do lists, other list managers, personal account and wallet managers provided by external services 1360, and the like.


Referring now to FIGS. 44A through 44C, there are shown screen shots depicting an example of the use of long term personal memory component(s) 1054, according to one embodiment. In the example, a feature is provided (named “My Stuff”), which includes access to saved entities such as restaurants, movies, and businesses that are found via interactive sessions with an embodiment of assistant 1002. In screen 4401 of FIG. 44A, the user has found a restaurant. The user taps on Save to My Stuff 4402, which saves information about the restaurant in long-term personal memory component(s) 1054.


Screen 4403 of FIG. 44B depicts user access to My Stuff. In one embodiment, the user can select among categories to navigate to the desired item.


Screen 4404 of FIG. 44C depicts the My Restaurant category, including items previously stored in My Stuff.


Automated Call and Response Procedure


Referring now to FIG. 33, there is shown a flow diagram depicting an automatic call and response procedure, according to one embodiment. The procedure of FIG. 33 may be implemented in connection with one or more embodiments of intelligent automated assistant 1002. It may be appreciated that intelligent automated assistant 1002 as depicted in FIG. 1 is merely one example from a wide range of intelligent automated assistant system embodiments which may be implemented. Other embodiments of intelligent automated assistant systems (not shown) may include additional, fewer and/or different components/features than those illustrated, for example, in the example intelligent automated assistant 1002 depicted in FIG. 1.


In at least one embodiment, the automated call and response procedure of FIG. 33 may be operable to perform and/or implement various types of functions, operations, actions, and/or other features such as, for example, one or more of the following (or combinations thereof):

    • The automated call and response procedure of FIG. 33 may provide an interface control flow loop of a conversational interface between the user and intelligent automated assistant 1002. At least one iteration of the automated call and response procedure may serve as a ply in the conversation. A conversational interface is an interface in which the user and assistant 1002 communicate by making utterances back and forth in a conversational manner.
    • The automated call and response procedure of FIG. 33 may provide the executive control flow for intelligent automated assistant 1002. That is, the procedure controls the gathering of input, processing of input, generation of output, and presentation of output to the user.
    • The automated call and response procedure of FIG. 33 may coordinate communications among components of intelligent automated assistant 1002. That is, it may direct where the output of one component feeds into another, and where the overall input from the environment and action on the environment may occur.


In at least some embodiments, portions of the automated call and response procedure may also be implemented at other devices and/or systems of a computer network.


According to specific embodiments, multiple instances or threads of the automated call and response procedure may be concurrently implemented and/or initiated via the use of one or more processors 63 and/or other combinations of hardware and/or hardware and software. In at least one embodiment, one or more or selected portions of the automated call and response procedure may be implemented at one or more client(s) 1304, at one or more server(s) 1340, and/or combinations thereof.


For example, in at least some embodiments, various aspects, features, and/or functionalities of the automated call and response procedure may be performed, implemented and/or initiated by software components, network services, databases, and/or the like, or any combination thereof.


According to different embodiments, one or more different threads or instances of the automated call and response procedure may be initiated in response to detection of one or more conditions or events satisfying one or more different types of criteria (such as, for example, minimum threshold criteria) for triggering initiation of at least one instance of automated call and response procedure. Examples of various types of conditions or events which may trigger initiation and/or implementation of one or more different threads or instances of the automated call and response procedure may include, but are not limited to, one or more of the following (or combinations thereof):

    • a user session with an instance of intelligent automated assistant 1002, such as, for example, but not limited to, one or more of:
      • a mobile device application starting up, for instance, a mobile device application that is implementing an embodiment of intelligent automated assistant 1002;
      • a computer application starting up, for instance, an application that is implementing an embodiment of intelligent automated assistant 1002;
      • a dedicated button on a mobile device pressed, such as a “speech input button”;
      • a button on a peripheral device attached to a computer or mobile device, such as a headset, telephone handset or base station, a GPS navigation system, consumer appliance, remote control, or any other device with a button that might be associated with invoking assistance;
      • a web session started from a web browser to a website implementing intelligent automated assistant 1002;
      • an interaction started from within an existing web browser session to a website implementing intelligent automated assistant 1002, in which, for example, intelligent automated assistant 1002 service is requested;
      • an email message sent to a modality server 1426 that is mediating communication with an embodiment of intelligent automated assistant 1002;
      • a text message is sent to a modality server 1426 that is mediating communication with an embodiment of intelligent automated assistant 1002;
      • a phone call is made to a modality server 1434 that is mediating communication with an embodiment of intelligent automated assistant 1002;
      • an event such as an alert or notification is sent to an application that is providing an embodiment of intelligent automated assistant 1002.
    • when a device that provides intelligent automated assistant 1002 is turned on and/or started.


According to different embodiments, one or more different threads or instances of the automated call and response procedure may be initiated and/or implemented manually, automatically, statically, dynamically, concurrently, and/or combinations thereof. Additionally, different instances and/or embodiments of the automated call and response procedure may be initiated at one or more different time intervals (e.g., during a specific time interval, at regular periodic intervals, at irregular periodic intervals, upon demand, and the like).


In at least one embodiment, a given instance of the automated call and response procedure may utilize and/or generate various different types of data and/or other types of information when performing specific tasks and/or operations. This may include, for example, input data/information and/or output data/information. For example, in at least one embodiment, at least one instance of the automated call and response procedure may access, process, and/or otherwise utilize information from one or more different types of sources, such as, for example, one or more databases. In at least one embodiment, at least a portion of the database information may be accessed via communication with one or more local and/or remote memory devices. Additionally, at least one instance of the automated call and response procedure may generate one or more different types of output data/information, which, for example, may be stored in local memory and/or remote memory devices.


In at least one embodiment, initial configuration of a given instance of the automated call and response procedure may be performed using one or more different types of initialization parameters. In at least one embodiment, at least a portion of the initialization parameters may be accessed via communication with one or more local and/or remote memory devices. In at least one embodiment, at least a portion of the initialization parameters provided to an instance of the automated call and response procedure may correspond to and/or may be derived from the input data/information.


In the particular example of FIG. 33, it is assumed that a single user is accessing an instance of intelligent automated assistant 1002 over a network from a client application with speech input capabilities. The user is interested in finding a good place for dinner at a restaurant, and is engaging intelligent automated assistant 1002 in a conversation to help provide this service.


In step 100, the user is prompted to enter a request. The user interface of the client offers several modes of input, as described in connection with FIG. 26. These may include, for example:

    • an interface for typed input, which may invoke an active typed-input elicitation procedure as illustrated in FIG. 11;
    • an interface for speech input, which may invoke an active speech input elicitation procedure as illustrated in FIG. 22.
    • an interface for selecting inputs from a menu, which may invoke active GUI-based input elicitation as illustrated in FIG. 23.


One skilled in the art will recognize that other input modes may be provided.


In one embodiment, step 100 may include presenting options remaining from a previous conversation with assistant 1002, for example using the techniques described in the active dialog suggestion input elicitation procedure described in connection with FIG. 24.


For example, by one of the methods of active input elicitation in step 100, the user might say to assistant 1002, “where may 1 get some good Italian around here?” For example, the user might have spoken this into a speech input component. An embodiment of an active input elicitation component 1094 calls a speech-to-text service, asks the user for confirmation, and then represents the confirmed user input as a uniform annotated input format 2690.


An embodiment of language interpreter component 1070 is then called in step 200, as described in connection with FIG. 29. Language interpreter component 1070 parses the text input and generates a list of possible interpretations of the user's intent 290. In one parse, the word “italian” is associated with restaurants of style Italian; “good” is associated with the recommendation property of restaurants; and “around here” is associated with a location parameter describing a distance from a global sensor reading (for example, the user's location as given by GPS on a mobile device).


In step 300, the representation of the user's intent 290 is passed to dialog flow processor 1080, which implements an embodiment of a dialog and flow analysis procedure as described in connection with FIG. 32. Dialog flow processor 1080 determines which interpretation of intent is most likely, maps this interpretation to instances of domain models and parameters of a task model, and determines the next flow step in a dialog flow. In the current example, a restaurant domain model is instantiated with a constrained selection task to find a restaurant by constraints (the cuisine style, recommendation level, and proximity constraints). The dialog flow model indicates that the next step is to get some examples of restaurants meeting these constraints and present them to the user.


In step 400, an embodiment of the flow and service orchestration procedure 400 is invoked, via services orchestration component 1082. It invokes a set of services 1084 on behalf of the user's request to find a restaurant. In one embodiment, these services 1084 contribute some data to a common result. Their data are merged and the resulting list of restaurants is represented in a uniform, service-independent form.


In step 500, output processor 1092 generates a dialog summary of the results, such as, “I found some recommended Italian restaurants near here.” Output processor 1092 combines this summary with the output result data, and then sends the combination to a module that formats the output for the user's particular mobile device in step 600.


In step 700, this device-specific output package is sent to the mobile device, and the client software on the device renders it on the screen (or other output device) of the mobile device.


The user browses this presentation, and decides to explore different options. If the user is done 790, the method ends. If the user is not done 490, another iteration of the loop is initiated by returning to step 100.


The automatic call and response procedure may be applied, for example to a user's query “how about mexican food?” Such input may be elicited in step 100. In step 200, the input is interpreted as restaurants of style Mexican, and combined with the other state (held in short term personal memory 1052) to support the interpretation of the same intent as the last time, with one change in the restaurant style parameter. In step 300, this updated intent produces a refinement of the request, which is given to service orchestration component(s) 1082 in step 400.


In step 400 the updated request is dispatched to multiple services 1084, resulting in a new set of restaurants which are summarized in dialog in 500, formatted for the device in 600, and sent over the network to show new information on the user's mobile device in step 700.


In this case, the user finds a restaurant of his or her liking, shows it on a map, and sends directions to a friend.


One skilled in the art will recognize that different embodiments of the automated call and response procedure (not shown) may include additional features and/or operations than those illustrated in the specific embodiment of FIG. 33, and/or may omit at least a portion of the features and/or operations of automated call and response procedure illustrated in the specific embodiment of FIG. 33.


Constrained Selection


In one embodiment, intelligent automated assistant 1002 uses constrained selection in its interactions with the user, so as to more effectively identify and present items that are likely to be of interest to the user.


Constrained selection is a kind of generic task. Generic tasks are abstractions that characterize the kinds of domain objects, inputs, outputs, and control flow that are common among a class of tasks. A constrained selection task is performed by selecting items from a choice set of domain objects (such as restaurants) based on selection constraints (such as a desired cuisine or location). In one embodiment, assistant 1002 helps the user explore the space of possible choices, eliciting the user's constraints and preferences, presenting choices, and offering actions to perform on those choices such as to reserve, buy, remember, or share them. The task is complete when the user selects one or more items on which to perform the action.


Constrained selection is useful in many contexts: for example, picking a movie to see, a restaurant for dinner, a hotel for the night, a place to buy a book, or the like. In general, constrained selection is useful when one knows the category and needs to select an instance of the category with some desired properties.


One conventional approach to constrained selection is a directory service. The user picks a category and the system offers a list of choices. In a local directory, one may constrain the directory to a location, such as a city. For instance, in a “yellow pages” service, users select the book for a city and then look up the category, and the book shows one or more items for that category. The main problem with a directory service is that the number of possibly relevant choices is large (e.g., restaurants in a given city).


Another conventional approach is a database application, which provides a way to generate a choice set by eliciting a query from the user, retrieving matching items, and presenting the items in some way that highlights salient features. The user browses the rows and columns of the result set, possibly sorting the results or changing the query until he or she finds some suitable candidates. The problem with the database service is that it may require the user to operationalize their human need as a formal query and to use the abstract machinery of sort, filter, and browse to explore the resulting data. These are difficult for most people to do, even with graphical user interfaces.


A third conventional approach is open-ended search, such as “local search.” Search is easy to do, but there are several problems with search services that make them difficult for people to accomplish the task of constrained selection. Specifically:

    • As with directory search, the user may not just enter a category and look at one or more possible choice, but must narrow down the list.
    • If the user can narrow the selection by constraints, it is not obvious what constraints may be used (e.g., may 1 search for places that are within walking distance or are open late?)
    • It is not clear how to state constraints (e.g., is it called cuisine or restaurant type, and what are the possible values?)
    • Multiple preferences conflict; there is usually no objectively “best” answer to a given situation (e.g., I want a place that is close by and cheap serving gourmet food with excellent service and which is open until midnight).
    • Preferences are relative, and they depend on what is available. For example, if the user may get a table at a highly rated restaurant, he or she might choose it even though it is expensive. In general, though, the user would prefer less expensive options.


In various embodiments, assistant 1002 of the present invention helps streamline the task of constrained selection. In various embodiments, assistant 1002 employs database and search services, as well as other functionality, to reduce the effort, on the part of the user, of stating what he or she is looking for, considering what is available, and deciding on a satisfactory solution.


In various embodiments, assistant 1002 helps to make constrained selection simpler for humans in any of a number of different ways.


For example, in one embodiment, assistant 1002 may operationalize properties into constraints. The user states what he or she wants in terms of properties of the desired outcome. Assistant 1002 operationalizes this input into formal constraints. For example, instead of saying “find one or more restaurants less than 2 miles from the center of Palo Alto whose cuisine includes Italian food” the user may just say “Italian restaurants in palo alto.” Assistant 1002 may also operationalize qualities requested by the user that are not parameters to a database. For example, if the user requests romantic restaurants, the system may operationalize this as a text search or tag matching constraint. In this manner, assistant 1002 helps overcome some of the problems users may otherwise have with constrained selection. It is easier, for a user, to imagine and describe a satisfactory solution than to describe conditions that would distinguish suitable from unsuitable solutions.


In one embodiment, assistant 1002 may suggest useful selection criteria, and the user need only say which criteria are important at the moment. For example, assistant 1002 may ask “which of these matter: price (cheaper is better), location (closer is better), rating (higher rated is better)?” Assistant 1002 may also suggest criteria that may require specific values; for example, “you can say what kind of cuisine you would like or a food item you would like”.


In one embodiment, assistant 1002 may help the user make a decision among choices that differ on a number of competing criteria (for example, price, quality, availability, and convenience).


By providing such guidance, assistant 1002 may help users in making multi-parametric decisions in any of several ways:

    • One is to reduce the dimensionality of the space, combining raw data such as ratings from multiple sources into a composite “recommendation” score. The composite score may take into account domain knowledge about the sources of data (e.g., Zagat ratings may be more predictive of quality than Yelp).
    • Another approach is to focus on a subset of criteria, turning a problem of “what are all the possible criteria to consider and how to they combine?” into a selection of the most important criteria in a given situation (e.g., “which is more important, price or proximity?”).
    • Another way to simply the decision making is to assume default values and preference orders (e.g., all things being equal, higher rated and closer and cheaper are better). The system may also remember users' previous responses that indicate their default values and preferences.
    • Fourth, the system may offer salient properties of items in the choice set that were not mentioned in the original request. For example, the user may have asked for local Italian food. The system may offer a choice set of restaurants, and with them, a list of popular tags used by reviewers or a tag line from a guide book (e.g., “a nice spot for a date” “great pasta”). This could let people pick out a specific item and complete the task. Research shows that most people make decisions by evaluating specific instances rather than deciding on criteria and rationally accepting the one that pops to the top. It also shows that people learn about features from concrete cases. For example, when choosing among cars, buyers may not care about navigation systems until they see that some of the cars have them (and then the navigation system may become an important criterion). Assistant 1002 may present salient properties of listed items that help people pick a winner or that suggest a dimension along which to optimize.


      Conceptual Data Model


In one embodiment, assistant 1002 offers assistance with the constrained selection task by simplifying the conceptual data model. The conceptual data model is the abstraction presented to users in the interface of assistant 1002. To overcome the psychological problems described above, in one embodiment assistant 1002 provides a model that allows users to describe what they want in terms of a few easily recognized and recalled properties of suitable choices rather than constraint expressions. In this manner, properties can be made easy to compose in natural language requests (e.g., adjectives modifying keyword markers) and be recognizable in prompts (“you may also favor recommended restaurants . . . ”). In one embodiment, a data model is used that allows assistant 1002 to determine the domain of interest (e.g., restaurants versus hotels) and a general approach to guidance that may be instantiated with domain-specific properties.


In one embodiment, the conceptual data model used by assistant 1002 includes a selection class. This is a representation of the space of things from which to choose. For example, in the find-a-restaurant application, the selection class is the class of restaurants. The selection class may be abstract and have subclasses, such as “things to do while in a destination.” In one embodiment, the conceptual data model assumes that, in a given problem solving situation, the user is interested in choosing from a single selection class. This assumption simplifies the interaction and also allows assistant 1002 to declare its boundaries of competence (“I know about restaurants, hotels, and movies” as opposed to “I know about life in the city”).


Given a selection class, in one embodiment the data model presented to the user for the constrained selection task includes, for example: items; item features; selection criteria; and constraints.


Items are instances of the selection class.


Item features are properties, attributes, or computed values that may be presented and/or associated with at least one item. For example, the name and phone number of a restaurant are item features. Features may be intrinsic (the name or cuisine of a restaurant) or relational (e.g., the distance from one's current location of interest). They may be static (e.g., restaurant name) or dynamic (rating). They may be composite values computed from other data (e.g., a “value for money” score). Item features are abstractions for the user made by the domain modeler; they do not need to correspond to underlying data from back-end services.


Selection criteria are item features that may be used to compare the value or relevance of items. That is, they are ways to say which items are preferred. Selection criteria are modeled as features of the items themselves, whether they are intrinsic properties or computed. For example, proximity (defined as distance from the location of interest) is a selection criterion. Location in space-time is a property, not a selection criterion, and it is used along with the location of interest to compute the distance from the location of interest.


Selection criteria may have an inherent preference order. That is, the values of any particular criterion may be used to line up items in a best first order. For example, the proximity criterion has an inherent preference that closer is better. Location, on the other hand, has no inherent preference value. This restriction allows the system to make default assumptions and guide the selection if the user only mentions the criterion. For example, the user interface might offer to “sort by rating” and assume that higher rated is better.


One or more selection criteria are also item features; they are those features related to choosing among possible items. However, item features are not necessarily related to a preference (e.g., the names and phone numbers of restaurants are usually irrelevant to choosing among them).


In at least one embodiment, constraints are restrictions on the desired values of the selection criteria. Formally, constraints might be represented as set membership (e.g., cuisine type includes Italian), pattern matches (e.g., restaurant review text includes “romantic”), fuzzy inequalities (e.g., distance less than a few miles), qualitative thresholds (e.g., highly rated), or more complex functions (e.g., a good value for money). To make things simple enough for normal humans, this data model reduces at least one or more constraints to symbolic values that may be matched as words. Time and distance may be excluded from this reduction. In one embodiment, the operators and threshold values used for implementing constraints are hidden from the user. For example, a constraint on the selection criteria called “cuisine” may be represented as a symbolic value such as “Italian” or “Chinese.” A constraint on rating is “recommended” (a binary choice). For time and distance, in one embodiment assistant 1002 uses proprietary representations that handle a range of inputs and constraint values. For example, distance might be “walking distance” and time might be “tonight”: in one embodiment, assistant 1002 uses special processing to match such input to more precise data.


In at least one embodiment, some constraints may be required constraints. This means that the task simply cannot be completed without this data. For example, it is hard to pick a restaurant without some notion of desired location, even if one knows the name.


To summarize, a domain is modeled as selection classes with item features that are important to users. Some of the features are used to select and order items offered to the user—these features are called selection criteria. Constraints are symbolic limits on the selection criteria that narrow the set of items to those that match.


Often, multiple criteria may compete and constraints may match partially. The data model reduces the selection problem from an optimization (finding the best solution) to a matching problem (finding items that do well on a set of specified criteria and match a set of symbolic constraints). The algorithms for selecting criteria and constraints and determining an ordering are described in the next section.


Methodology for Constrained Selection


In one embodiment, assistant 1002 performs constrained selection by taking as input an ordered list of criteria, with implicit or explicit constraints on at least one, and generating a set of candidate items with salient features. Computationally, the selection task may be characterized as a nested search: first, identify a selection class, then identify the important selection criteria, then specify constraints (the boundaries of acceptable solutions), and search through instances in order of best fit to find acceptable items.


Referring now to FIG. 45, there is shown an example of an abstract model 4500 for a constrained selection task as a nested search. In the example assistant 1002 identifies 4505 a selection call among all local search types 4501. The identified class is restaurant. Within the set of all restaurants 4502, assistant 1002 selects 4506 criteria. In the example, the criterion is identified as distance. Within the set of restaurants in PA 4503, assistant 1002 specifies 4507 constraints for the search. In the example, the identified constraint is “Italian cuisine”). Within the set of Italian restaurants in PA 4504, assistant 4508 selects items for presentation to the user.


In one embodiment, such a nested search is what assistant 1002 does once it has the relevant input data, rather than the flow for eliciting the data and presenting results. In one embodiment, such control flow is governed via a dialog between assistant 1002 and the user which operates by other procedures, such as dialog and task flow models. Constrained selection offers a framework for building dialog and task flow models at this level of abstraction (that is, suitable for constrained selection tasks regardless of domain).


Referring now to FIG. 46, there is shown an example of a dialog 4600 to help guide the user through a search process, so that the relevant input data can be obtained.


In the example dialog 4600, the first step is for the user to state the kind of thing they are looking for, which is the selection class. For example, the user might do this by saying “dining in palo alto.” This allows assistant 1002 to infer 4601 the task and domain.


Once assistant 1002 has understood the task and domain binding (selection class=restaurants), the next step is to understand which selection criteria are important to this user, for example by soliciting 4603 criteria and/or constraints. In the example above, “in palo alto” indicates a location of interest. In the context of restaurants, the system may interpret a location as a proximity constraint (technically, a constraint on the proximity criterion). Assistant 1002 explains what is needed, receives input. If there is enough information to constrain the choice set to a reasonable size, then assistant 1002 paraphrases the input and presents 4605 one or more restaurants that meet the proximity constraint, sorted in some useful order. The user can then select 4607 from this list, or refine 4606 the criteria and constraints. Assistant 1002 reasons about the constraints already stated, and uses domain-specific knowledge to suggest other criteria that might help, soliciting constraints on these criteria as well. For example, assistant 1002 may reason that, when recommending restaurants within walking distance of a hotel, the useful criteria to solicit would be cuisine and table availability.


The constrained selection task is complete when the user selects 4607 an instance of the selection class. In one embodiment, additional follow-on tasks 4602 are enabled by assistant 1002. Thus, assistant 1002 can offer services that indicate selection while providing some other value. Examples 4608 booking a restaurant, setting a reminder on a calendar, and/or sharing the selection with others by sending an invitation. For example, booking a restaurant certainly indicates that it was selected; other options might be to put the restaurant on a calendar or send in invitation with directions to friends.


Referring now to FIG. 47, there is shown a flow diagram depicting a method of constrained selection according to one embodiment. In one embodiment, assistant 1002 operates in an opportunistic and mixed-initiative manner, permitting the user to jump to the inner loop, for instance, by stating task, domain, criteria, and constraints one or more at once in the input.


The method begins 4701. Input is received 4702 from the user, according to any of the modes described herein. If, based on the input, the task not known, assistant 1002 requests 4705 clarifying input from the user.


In step 4717, assistant 1002 determines whether the user provides additional input. If so, assistant 1002 returns to step 4702. Otherwise the method ends 4799.


If, in step 4703, the task is known, assistant 1002 determines 4704 whether the task is constrained selection. If not, assistant 1002 proceeds 4706 to the specified task flow.


If, in step 4704, the task is constrained selection, assistant 1002 determines 4707 whether the selection class can be determined. If not, assistant 1002 offers 4708 a choice of known selection classes, and returns to step 4717.


If, in step 4707, the selection class can be determined, assistant 1002 determines 4709 whether all required constraints can be determined. If not, assistant 1002 prompts 4710 for required information, and returns to step 4717.


If, in step 4709, all required constants can be determined, assistant 1002 determines 4711 whether any result items can be found, given the constraints. If there are no items that meet the constraints, assistant 1002 offers 4712 ways to relax the constraints. For example, assistant 1002 may relax the constraints from lowest to highest precedence, using a filter/sort algorithm. In one embodiment, if there are items that meet some of the constraints, then assistant 1002 may paraphrase the situation (outputting, for example, “I could not find Recommended Greek restaurants that deliver on Sundays in San Carlos. However, I found 3 Greek restaurants and 7 Recommend restaurants in San Carlos.”). In one embodiment, if there are no items that match any constraints, then assistant 1002 may paraphrase this situation and prompt for different constraints (outputting, for example, “Sorry, I could not find any restaurants in Anytown, Texas. You may pick a different location.”). Assistant 1002 returns to step 4717.


If, in step 4711, result items can be found, assistant 1002 offers 4713 a list of items. In one embodiment, assistant 1002 paraphrases the currently specified criteria and constraints (outputting, for example, “Here are some recommended Italian restaurants in San Jose.” (recommended=yes, cuisine=Italian, proximity=<in San Jose>)). In one embodiment, assistant 1002 presents a sorted, paginated list of items that meet the known constraints. If an item only shows some of the constraints, such a condition can be shown as part of the item display. In one embodiment, assistant 1002 offers the user ways to select an item, for example by initiating another task on that item such as booking, remembering, scheduling, or sharing. In one embodiment, on any given item, assistant 1002 presents item features that are salient for picking instances of the selection class. In one embodiment, assistant 1002 shows how the item meets a constraint; for example, Zagat rating of 5 meets the Recommended=yes constraint, and “1 mile away” meets the “within walking distance of an address” constraint. In one embodiment, assistant 1002 allows the user to drill down for more detail on an item, which results in display of more item features.


Assistant 1002 determines 4714 whether the user has selected an item. If the user selects an item, the task is complete. Any follow-on task is performed 4715, if there is one, and the method ends 4799.


If, in step 4714, the user does not select an item, assistant 1002 offers 4716 the user ways to select other criteria and constraints and returns to step 4717. For example, given the currently specified criteria and constraints, assistant 1002 may offer criteria that are most likely to constrain the choice set to a desired size. If the user selects a constraint value, that constraint value is added to the previously determined constraints when steps 4703 to 4713 are repeated.


Since one or more criteria may have an inherent preference value, selecting the criteria may add information to the request. For example, allowing the user to indicate that positive reviews are valued allows assistant 1002 to sort by this criterion. Such information can be taken into account when steps 4703 to 4713 are repeated.


In one embodiment, assistant 1002 allows the user to raise the importance of a criterion that is already specified, so that it would be higher in the precedence order. For example, if the user asked for fast, cheap, highly recommended restaurants within one block of their location, assistant 1002 may request that the user chooses which of these criteria are more important. Such information can be taken into account when steps 4703 to 4713 are repeated.


In one embodiment, the user can provide additional input at any point while the method of FIG. 47 is being performed. In one embodiment, assistant 1002 checks periodically or continuously for such input, and, in response, loops back to step 4703 to process it.


In one embodiment, when outputting an item or list of items, assistant 1002 indicates, in the presentation of items, the features that were used to select and order them. For example, if the user asked for nearby Italian restaurants, such item features for distance and cuisine may be shown in the presentation of the item. This may include highlighting matches, as well as listing selection criteria that were involved in the presentation of an item.


Example Domains


Table 1 provides an example of constrained selection domains that may be handled by assistant 1002 according to various embodiments.










TABLE 1








Based on these criteria
























special
general


Select a
Location
Price
Availability
Type
Quality
Name
Services
search
search





Restaurant
proximity
affordability
open tables
cuisine
rating by
restaurant
delivery
menu
keywords







guide,
name

items








review






Hotel
proximity
price range
available
motel,
rating, by
hotel
amenities

keywords





rooms
hotel,
guide,
name









B&B, . . .
review






Movie
theatre

show times
genre
rating by
movie title

actors,




proximity



review


etc



Local
proximity


business
rating by
business


keywords


Business



category
review
name





Local
venue

by date


event title


keywords


event
proximity










concert
venue

by tour
music

band

band
keywords



proximity

schedule
genre

name

members



CD, book,

price range
online, in
download,
popularity
album or

artist
keywords


DVD to


store, etc.
physical

song name

title, etc.



buy










Filtering and Sorting Results


In one embodiment, when presenting items that meet currently specified criteria and constraints, a filter/sort methodology can be employed. In one embodiment selection constraints may serve as both filter and sort parameters to the underlying services. Thus, any selection criterion can be used to determine which items are in the list, and to compute the order in which to paginate and show them. Sort order for this task is akin to relevance rank in search. For example, proximity is a criterion with symbolic constraint values such as “within driving distance” and a general notion of sorting by distance. The “driving distance” constraint might be used to select a group of candidate items. Within that group, closer items might be sorted higher in the list.


In one embodiment, selection constraints and associated filtering and sorting are at discrete “levels”, which are functions of both the underlying data and the input from the user. For example, proximity is grouped into levels such as “walking distance”, “taxi distance”, “driving distance.” When sorting, one or more items within walking distance are treated as if they were the same distance. The input from the user may come into play in the way he or she specifies a constraint. If the user enters “in palo alto”, for example, then one or more items within the Palo Alto city limits are perfect matches and are equivalent. If the user enters, “near the University Avenue train station” then the match would depend on a distance from that address, with the degree of match dependent on the selection class (e.g., near for restaurants is different than near for hotels). Even within a constraint that may be specified with a continuous value, a discretization may be applied. This may be important for sorting operations, so that multiple criteria may participate in determining the best-first ordering.


In one embodiment, the item list—those items that are considered “matching” or “good enough”—may be shorter or longer than the number of items shown on one “page” of the output. Generally, items in the first page are given the most attention, but conceptually there is a longer list, and pagination is simply a function of the form factor of the output medium. This means, for instance, that if the user is offered a way to sort or browse the items by some criterion, then it is the entire set of items (more than one page worth) that is sorted or browsed.


In one embodiment, there is a precedence ordering among selection criteria. That is, some criteria may matter more than others in the filter and sort. In one embodiment, those criteria selected by the user are given higher precedence than others, and there is a default ordering over one or more criteria. This allows for a general lexicographic sort. The assumption is that there is a meaningful a priori precedence. For example, unless the user states otherwise, it may be more important for a restaurant to be close than to be inexpensive. In one embodiment, the apriori precedence ordering is domain-specific. The model allows for user-specific preferences to override the domain defaults, if that is desired.


Since the values of constraints can represent several internal data types, there are different ways for constraints to match, and they may be specific to the constraint. For example, in one embodiment:

    • Binary constraints match one or more or none. For example, whether a restaurant is “Fast” might be either true or not.
    • Set membership constraints match one or more or none based on a property value. For example, cuisine=Greek means the set of cuisines for a restaurant includes Greek.
    • Enumeration constraints match at a threshold. For example, a rating criterion might have constraint values rated, highly-rated, or top-rated. Constraining to highly-rated would also match top-rated.
    • Numeric constraints match at a threshold that may be criterion specific. For example, “open late” might be a criterion, and the user might ask for places open after 10:00 pm. This kind of constraint may be slightly out of scope for the constrained selection task, since it is not a symbolic constraint value. However, in one embodiment, assistant 1002 recognizes some cases of numeric constraints like this, and maps them to threshold values with symbolic constraints (e.g., “restaurants in palo alto open now”→“here are 2 restaurants in palo alto that are open late”).
    • Location and time are handled specially. A constraint on proximity might be a location of interest specified at some level of granularity, and that determines the match. If the user specifies a city, then city-level matching is appropriate; a ZIP code may allow for a radius. Assistant 1002 may also understand locations that are “near” other locations of interest, also based on special processing. Time is relevant as a constraint value of criteria that have threshold value based on a service call, such as table availability or flights within a given time range.


In one embodiment, constraints can be modeled so that there is a single threshold value for selection and a small set of discrete values for sorting. For example, the affordability criterion might be modeled as a roughly binary constraint, where affordable restaurants are any under some threshold price range. When the data justify multiple discrete levels for selection, constraints can be modeled using a gradient of matching. In one embodiment two levels of matching (such as strong and weak matching) may be provided; however, one skilled in the art will recognize that in other embodiments, any number of levels of matching can be provided. For example, proximity may be matched with a fuzzy boundary, so that things that are near the location of interest may match weakly. The operational consequence of a strong or weak match is in the filter/sort algorithm as described below.


For at least one criterion, an approach to matching and default thresholds can be established, if relevant. The user may be able to say just the name of the constraint, a symbolic constraint value, or a precise constraint expression if it is handled specially (such as time and location).


An ideal situation for constrained selection occurs when the user states constraints that result in a short list of candidates, one or more of which meet the constraints. The user then chooses among winners based on item features. In many cases, however, the problem is over- or under-constrained. When it is over-constrained, there are few or no items that meet the constraints. When it is under-constrained, there are so many candidates that examining the list is not expedient. In one embodiment, the general constrained selection model of the present invention is able to handle multiple constraints with robust matching and usually produce something to choose from. Then the user may elect to refine their criteria and constraints or just complete the task with a “good enough” solution.


Method

In one embodiment, the following method is used for filtering and sorting results:


1. Given an ordered list of selection criteria selected by the user, determine constraints on at least one.

    • a. If the user specified a constraint value, use it. For example, if the user said “greek food” the constraint is cuisine=Greek. If the user said “san Francisco” the constraint is In the City of San Francisco. If the user said “south of market” then the constraint is In the Neighborhood of SoMa.
    • b. Otherwise use a domain- and criteria-specific default. For example, if the user said “a table at some thai place” he or she is indicating that the availability criterion is relevant, but he or she did not specify a constraint value. The default constraint values for availability might be some range of date times such as tonight and a default party size of 2.


2. Select a minimum of N results by specified constraints.

    • a. Try to get N results at strong match.
    • b. If that fails, try to relax constraints, in reverse precedence order. That is, match at strong level for one or more of the criteria except the last, which may match at a weak level. If there is no weak match for that constraint, then try weak matches up the line from lowest to highest precedence.
    • c. Then repeat the loop allowing failure to match on constraints, from lowest to highest precedence.


3. After getting a minimum choice set, sort lexicographically over one or more criteria (which may include user-specified criteria as well as other criteria) in precedence order.

    • a. Consider the set of user-specified criteria as highest precedence, then one or more remaining criteria in their a priori precedence. For example, if the a priori precedence is (availability, cuisine, proximity, rating), and the user gives constraints on proximity and cuisine, then the sort precedence is (cuisine, proximity, availability, rating).
    • b. Sort on criteria using discrete match levels (strong, weak, none), using the same approach as in relaxing constraints, this time applied the full criteria list.
      • i. If a choice set was obtained without relaxing constraints, then one or more of the choice set may “tie” in the sort because they one or more match at strong levels. Then, the next criteria in the precedence list may kick in to sort them. For example, if the user says cuisine=Italian, proximity=In San Francisco, and the sort precedence is (cuisine, proximity, availability, rating), then one or more the places on the list have equal match values for cuisine and proximity. So the list would be sorted on availability (places with tables available bubble to the top). Within the available places, the highest rated ones would be at the top.
      • ii. If the choice set was obtained by relaxing constraints, then one or more of the fully matching items are at the top of the list, then the partially matching items. Within the matching group, they are sorted by the remaining criteria, and the same for the partially matching group. For example, if there were only two Italian restaurants in San Francisco, then the available one would be shown first, then the unavailable one. Then the rest of the restaurants in San Francisco would be shown, sorted by availability and rating.


        Precedence Ordering


The techniques described herein allow assistant 1002 to be extremely robust in the face of partially specified constraints and incomplete data. In one embodiment, assistant 1002 uses these techniques to generate a user list of items in best-first order, i.e. according to relevance.


In one embodiment, such relevance sorting is based on an a priori precedence ordering. That is, of the things that matter about a domain, a set of criteria is chosen and placed in order of importance. One or more things being equal, criteria higher in the precedence order may be more relevant to a constrained selection among items than those lower in the order. Assistant 1002 may operate on any number of criteria. In addition, criteria may be modified over time without breaking existing behaviors.


In one embodiment, the precedence order among criteria may be tuned with domain-specific parameters, since the way criteria interact may depend on the selection class. For example, when selecting among hotels, availability and price may be dominant constraints, whereas for restaurants, cuisine and proximity may be more important.


In one embodiment, the user may override the default criteria ordering in the dialog. This allows the system to guide the user when searches are over-constrained, by using the ordering to determine which constraints should be relaxed. For example, if the user gave constraints on cuisine, proximity, recommendation, and food item, and there were no fully matching items, the user could say that food item was more important than recommendation level and change the mix so the desired food item matches were sorted to the top.


In one embodiment, when precedence order is determined, user-specified constraints take precedence over others. For example, in one embodiment, proximity is a required constraint and so is always specified, and further has precedence over other unselected constraints. Therefore it does not have to be the highest precedence constraint in order to be fairly dominant. Also, many criteria may not match at one or more unless a constraint is given by the user, and so the precedence of these criteria only matters within user-selected criteria. For example, when the user specifies a cuisine it is important to them, and otherwise is not relevant to sorting items.


For example, the following is a candidate precedence sorting paradigm for the restaurant domain:

    • 1. cuisine* (not sortable unless a constraint value is given)
    • 2. availability* (sortable using a default constraint value, e.g., time)
    • 3. recommended
    • 4. proximity* (a constraint value is always given)
    • 5. affordability
    • 6. may deliver
    • 7. food item (not sortable unless a constraint value, e.g., a keyword, is given)
    • 8. keywords (not sortable unless a constraint value, e.g., a keyword, is given)
    • 9. restaurant name


The following is an example of a design rationale for the above sorting paradigm:

    • If a user specifies a cuisine, he or she wants it to stick.
    • One or more things being equal, sort by rating level (it is the highest precedence among criteria than may be used to sort without a constraint).
    • In at least one embodiment, proximity may be more important than most things. However, since it matches at discrete levels (in a city, within a radius for walking and the like), and it is always specified, then most of the time most matching items may “tie” on proximity.
    • Availability (as determined by a search on a website such as open-table.com, for instance) is a valuable sort criterion, and may be based on a default value for sorting when not specified. If the user indicates a time for booking, then only available places may be in the list and the sort may be based on recommendation.
    • If the user says they want highly recommended places, then it may sort above proximity and availability, and these criteria may be relaxed before recommendation. The assumption is that if someone is looking for nice place, they may be willing to drive a bit farther and it is more important than a default table availability. If a specific time for availability is specified, and the user requests recommended places, then places that are both recommended and available may come first, and recommendation may relax to a weak match before availability fails to match at one or more.
    • The remaining constraints except for name are one or more based on incomplete data or matching. So they are weak sort heuristics by default, and when they are specified the match one or more-or-none.
    • Name may be used as a constraint to handle the case where someone mentions the restaurant by name, e.g., find one or more Hobee's restaurants near Palo Alto. In this case, one or more items may match the name, and may be sorted by proximity (the other specified constraint in this example).


      Domain Modeling: Mapping Selection Criteria to Underlying Data


It may be desirable to distinguish between the data that are available for computation by assistant 1002 and the data used for making selections. In one embodiment, assistant 1002 uses a data model that reduces the complexity for the user by folding one or more kinds of data used to distinguish among items into a simple selection criteria model. Internally, these data may take several forms. Instances of the selection class can have intrinsic properties and attributes (such as cuisine of a restaurant), may be compared along dimensions (such as the distance from some location), and may be discovered by some query (such as whether it matches a text pattern or is available at a given time). They may also be computed from other data which are not exposed to the user as selection criteria (e.g., weighted combinations of ratings from multiple sources). These data are one or more relevant to the task, but the distinctions among these three kinds of data are not relevant to the user. Since the user thinks in terms of features of the desired choice rather than in properties and dimensions, assistant 1002 operationalizes these various criteria into features of the items. Assistant 1002 provides a user-facing domain data model and maps it to data found in web services.


One type of mapping is an isomorphism from underlying data to user-facing criteria. For example, the availability of tables for reservations as seen by the user could be exactly what an online reservation website, such as opentable.com, offers, using the same granularity for time and party size.


Another type of mapping is a normalization of data from one or more services to a common value set, possibly with a unification of equivalent values. For example, cuisines of one or more restaurants may be represented as a single ontology in assistant 1002, and mapped to various vocabularies used in different services. That ontology might be hierarchical, and have leaf nodes pointing to specific values from at least one service. For example, one service might have a cuisine value for “Chinese”, another for “Szechuan”, and a third for “Asian.” The ontology used by assistant 1002 would cause references to “Chinese food” or “Szechuan” to semantically match one or more of these nodes, with confidence levels reflecting the degree of match.


Normalization might also be involved when resolving differences in precision. For example, the location of a restaurant may be given to the street level in one service but only to city in another. In one embodiment, assistant 1002 uses a deep structural representation of locations and times that may be mapped to different surface data values.


In one embodiment, assistant 1002 uses a special kind of mapping for open-ended qualifiers (e.g., romantic, quiet) which may be mapped to matches in full text search, tags, or other open-textured features. The name of the selection constraint in this case would be something like “is described as”.


In at least one embodiment, constraints may be mapped to operational preference orderings. That is, given the name of a selection criterion and its constraint value, assistant 1002 is able to interpret the criterion as an ordering over possible items. There are several technical issues to address in such a mapping. For example:

    • Preference orderings may conflict. The ordering given by one constraint may be inconsistent or even inversely correlated with the ordering given by another. For example, price and quality tend to be in opposition. In one embodiment, assistant 1002 interprets constraints chosen by the user in a weighted or otherwise combined ordering that reflects the user's desires but is true to the data. For example, the user may ask for “cheap fast food French restaurants within walking distance rated highly.” In many locations, there may not be any such restaurant. However, in one embodiment, assistant 1002 may show a list of items that tries to optimize for at least one constraint, and explain why at least one is listed. For example, item one might be “highly rated French cuisine” and another “cheap fast food within walking distance”.
    • Data may be used as either hard or soft constraints. For example, the price range of a restaurant may be important to choosing one, but it may be difficult to state a threshold value for price up-front. Even seemingly hard constraints like cuisine may be, in practice, soft constraints because of partial matching. Since, in one embodiment, assistant 1002 using a data modeling strategy that seeks to flatten one or more criteria into symbolic values (such as “cheap” or “close”), these constraints may be mapped into a function that gets the criteria and order right, without being strict about matching specific threshold values. For symbolic criteria with clear objective truth values, assistant 1002 may weigh the objective criteria higher than other criteria, and make it clear in the explanation that it knows that some of the items do not strictly match the requested criteria.
    • Items may match some but not one or more constraints, and the “best fitting” items may be shown.
    • In general, assistant 1002 determines which item features are salient for a domain, and which may serve as selection criteria, and for at least one criteria, possible constraint values. Such information can be provided, for example, via operational data and API calls.


      Paraphrase and Prompt Text


As described above, in one embodiment assistant 1002 provides feedback to show it understands the user's intent and is working toward the user's goal by producing paraphrases of its current understanding. In the conversational dialog model of the present invention, the paraphrase is what assistant 1002 outputs after the user's input, as a preface (for example, paraphrase 4003 in FIG. 40) or summary of the results to follow (for example, list 3502 in FIG. 35).


The prompt is a suggestion to the user about what else they can do to refine their request or explore the selection space along some dimensions.


In one embodiment, the purposes of paraphrase and prompt text include, for example:

    • to show that assistant 1002 understands the concepts in the user's input, not just the text;
    • to indicate the boundaries of assistant's 1002 understanding;
    • to guide the user to enter text that is required for the assumed task;
    • to help the user explore the space of possibilities in constrained selection;
    • to explain the current results obtained from services in terms of the user's stated criteria and assistant's 1002 assumptions (for example, to explain the results of under- and over-constrained requests).


For example, the following paraphrase and prompt illustrates several of these goals:

    • User input: indonesian food in menlo park
    • System interpretation:
    • Task=constrainedSelection
    • SelectionClass=restaurant
    • Constraints:
      • Location=Menlo Park, CA
      • Cuisine=Indonesian (known in ontology)
    • Results from Services: no strong matches
    • Paraphrase: Sorry, I can't find any Indonesian restaurants near Menlo Park.
    • Prompt: You could try other cuisines or locations.
    • Prompt under hypertext links:
    • Indonesian: You can try other food categories such as Chinese, or a favorite food item such as steak.
    • Menlo Park: Enter a location such as a city, neighborhood, street address, or “near” followed by a landmark.
    • Cuisines: Enter a food category such as Chinese or Pizza.
    • Locations: Enter a location: a city, zip code, or “near” followed by the name of a place.


In one embodiment, assistant 1002 responds to user input relatively quickly with the paraphrase. The paraphrase is then updated after results are known. For example, an initial response may be “Looking for Indonesian restaurants near Menlo Park . . . ” Once results are obtained, assistant 1002 would update the text to read, “Sorry, I can't find any Indonesian restaurants near Menlo Park. You could try other cuisines or locations.” Note that certain items are highlighted (indicated here by underline), indicating that those items represent constraints that can be relaxed or changed.


In one embodiment, special formatting/highlighting is used for key words in the paraphrase. This can be helpful to facilitate training of the user for interaction with intelligent automated assistant 1002, by indicating to the user which words are most important to, and more likely to be recognized by, assistant 1002. User may then be more likely to use such words in the future.


In one embodiment, paraphrase and prompt are generated using any relevant context data. For example, any of the following data items can be used, alone or in combination:

    • The parse—a tree of ontology nodes bound to their matching input tokens, with annotations and exceptions. For each node in the parse, this may include the node's metadata and/or any tokens in the input that provide evidence for the node's value.
    • The task, if known
    • The selection class.
    • The location constraint, independent of selection class.
    • Which required parameters are unknown for the given selection class (e.g., location is a required constraint on restaurants).
    • The name of a named entity in the parse that is an instance of the selection class, if there is one (e.g., a specific restaurant or movie name.)
    • Is this a follow-up refinement or the beginning of a conversation? (Reset starts a new conversation.)
    • Which constraints in the parse are bound to values in the input that changed their values? In other words, which constraints were just changed by the latest input?
    • Is the selection class inferred or directly stated?
    • Sorted by quality, relevance, or proximity?
    • For each constraint specified, how well was it matched?
    • Was refinement entered as text or clicking?


In one embodiment, the paraphrase algorithm accounts for the query, domain model 1056, and the service results. Domain model 1056 contains classes and features including metadata that is used to decide how to generate text. Examples of such metadata for paraphrase generation include:

    • OsConstraint={trueIfalse}
    • IsMultiValued={trueIfalse}
    • ConstraintType={EntityName, Location, Time, CategoryConstraint, AvailabilityConstraint, BinaryConstraint, SearchQualifier, Guessed-Qualifier}
    • DisplayName=string
    • DisplayTemplateSingular=string
    • DisplayTemplatePlural=string
    • GrammaticalRole={AdjectiveBeforeNoun,Noun,ThatClauseModifer}


For example, a parse might contain these elements:

    • Class: Restaurant
    • IsConstraint=false
    • DisplayTemplateSingular=“restaurant”
    • DisplayTemplatePlural=“restaurants”
    • GrammaticalRole=Noun
    • Feature: RestaurantName (example: “Il Fornaio”)
    • IsConstraint=true
    • IsMultiValued=false
    • ConstraintType=EntityName
    • DisplayTemplateSingular=“named $1”
    • DisplayTemplatePlural=“named $1”
    • GrammaticalRole=Noun
    • Feature: RestaurantCuisine (example: “Chinese”)
    • IsConstraint=true
    • IsMultiValued=false
      • ConstraintType=CategoryConstraint
    • GrammaticalRole=AdjectiveBeforeNoun
    • Feature: RestaurantSubtype (example: “café”)
    • IsConstraint=true
    • IsMultiValued=false
    • ConstraintType=CategoryConstraint
    • DisplayTemplateSingular=“$1”
    • DisplayTemplatePlural=“$Is”
    • GrammaticalRole=Noun
    • Feature: RestaurantQualifiers (example: “romantic”)
    • IsConstraint=true
    • IsMultiValued=true
    • ConstraintType=SearchQualifier
    • DisplayTemplateSingular=“is described as $1”
    • DisplayTemplatePlural=“are described as $1”
    • DisplayTemplateCompact=“matching $1”
    • GrammaticalRole=Noun
    • Feature: FoodType (example: “burritos”)
    • IsConstraint=true
    • IsMultiValued=false
    • ConstraintType=SearchQualifier
    • DisplayTemplateSingular=“serves $1”
    • DisplayTemplatePlural=“serve $1”
    • DisplayTemplateCompact=“serving $1”
    • GrammaticalRole=ThatClauseModifer
    • Feature: IsRecommended (example: true)
    • IsConstraint=true
    • IsMultiValued=false
    • ConstraintType=BinaryConstraint
    • DisplayTemplateSingular=“recommended”
    • DisplayTemplatePlural=“recommended”
    • GrammaticalRole=AdjectiveBeforeNoun
    • Feature: RestaurantGuessedQualifiers (example: “spectacular”)
    • IsConstraint=true
    • IsMultiValued=false
    • ConstraintType=GuessedQualifier
    • DisplayTemplateSingular=“matches $1 in reviews”
    • DisplayTemplatePlural=“match $1 in reviews”
    • DisplayTemplateCompact=“matching $1”
    • GrammaticalRole=ThatClauseModifer


In one embodiment, assistant 1002 is able to handle unmatched input. To handle such input, domain model 1056 can provide for nodes of type GuessedQualifier for each selection class, and rules that match otherwise unmatched words if they are in the right grammatical context. That is, GuessedQualifiers are treated as miscellaneous nodes in the parse which match when there are words that are not found in the ontology but which are in the right context to indicate that that are probably qualifiers of the selection class. The difference between GuessedQualifiers and SearchQualifiers is that the latter are matched to vocabulary in the ontology. This distinction allows us to paraphrase that assistant 1002 identified the intent solidly on the SearchQualifiers and can be more hesitant when echoing back the GuessedQualifiers.


In one embodiment, assistant 1002 performs the following steps when generating paraphrase text:

    • 1. If the task is unknown, explain what assistant 1002 can do and prompt for more input.
    • 2. If the task is a constrained selection task and the location is known, then explain the domains that assistant 1002 knows and prompt for the selection class.
    • 3. If the selection class is known but a required constraint is missing, then prompt for that constraint. (for example, location is required for constrained selection on restaurants)
    • 4. If the input contains an EntityName of the selection class, then output “looking up”<name> in <location>.
    • 5. If this is the initial request in a conversation, then output “looking for” followed by the complex noun phrase that describes the constraints.
    • 6. If this is a follow-up refinement step in the dialog,
      • a. If the user just completed a required input, then output “thanks” and then paraphrase normally. (This happens when there is a required constraint that is mapped to the user input.)
      • b. If the user is changing a constraint, acknowledge this and then paraphrase normally.
      • c. If the user typed in the proper name of an instance of the selection class, handle this specially.
      • d. If the user just added an unrecognized phrase, then indicate how it will be folded in as search. If appropriate, the input may be dispatched to a search service.
      • e. If the user is just adding a normal constraint, then output “OK”, and paraphrase normally.
    • 7. To explain results, use the same approach for paraphrase. However, when the results are surprising or unexpected, then explain the results using knowledge about the data and service. Also, when the query is over-or underconstrained, prompt for more input.


      Grammar for Constructing Complex Noun Phrases


In one embodiment, when paraphrasing 734 a constrained selection task query, the foundation is a complex noun phrase around the selection class that refers to the current constraints. Each constraint has a grammatical position, based on its type. For example, in one embodiment, assistant 1002 may construct a paraphrase such as:














recommendedromanticItalian restaurants near Menlo Park


 with open tables for 2 that serve osso buco and are described as “quiet


 A grammar to construct this is


<paraphraseNounClause> :== <binaryConstraint> <searchQualifier> <categoryConstraint >


 <itemNoun> <locationConstraint> <availabiltyConstraint> <adjectivalClauses>


<binaryConstraint> :--- single adjective that indicates the presence or absence of a


 BinaryConstraint (e.g., recommended (best), affordable (cheap))


 It is possible to list more than one in the same query.


<searchQualifier> :== a word or words that match the ontology for a qualifier of the selection


 class, which would be passed into a search engine service. (e.g., romantic restaurants,


 funny movies).


 Use when ConstraintType= Search Qualifier.


<categoryConstraint> :== an adjective that identifies the genre, cuisine, or category of the


 selection class (e.g., Chinese restaurant or R-rated file). It is the last prefix adjective


 because it is the most intrinsic. Use for features of type CategoryConstraint and


 GrammaticalRole=AdjectiveBeforeNoun.


<itemNoun> :== <namedEntityPhrase> | <selectionClass> | <selectionClassSubType > find


 the most specific way to display the noun. NamedEntity < Sub Type < Class


<selectionClass > :== a noun that is the generic name for the selection class (e.g., restaurant,


 movie, place)


<selectionClassSubType> :== a noun phrase that is the subtype of the selection class if it is


 known (e.g., diner, museum, store, bar for the selection class local business). Use for


 features in which ConstraintType =CategoryConstraint and


 GrammaticalRole=AdjectiveBeforeNoun.


<namedEntityPhrase> :==<entityName> |


 “the” (<selection Class> | <selectionClassSubType>)


<entityName> :== the proper name of an instance of the selection class (e.g., “Il Fornaio”


 “Animal House” “Harry's Bar”)


<locationConstraint> :== <locationPreposition> <locationName>


<locationPreposition> :== “in”, “near”, “at”, and the like


<locationName> :== city, street address, landmark, or something for OPS like “your current


 location”


<availabilityConstraint> :== the availability constraint expressed as a prepositional phrase that


 comes after the noun (e.g., “with open tables”, “with seats available”, “available online”).


 It comes right after the noun to give it salience.


<adjectivalClauses>:== <modiferVerbPhrase > | “that” <modiferVerbPhrase> “and”


 <modiferVerbPhrase>


<modiferVerbPhrase> := a verb phrase that expresses a search-keyword style constraint on the


 selection class (e.g., restaurants that “are described as quiet”, “serve meat after 11”,


 “match ‘tragically hip’ in reviews”; movies that “contain violence”, “star Billy Bob


 Thornton”). Include all constraints in the parse whose


 GrammaticalRole=ThatClauseModifer, using the “that...and” variant if there are more


 than one. Use the DisplayTemplatePlural to generate the “that” clauses, putting the


 GuessedQualifier last. If there is only one such constraint, use the


 DisplayTemplateCompact variant.









Table 2 provides some examples of paraphrases that may be provided in response to the first input for a task, according to one embodiment.









TABLE 2







Paraphrases in response to first input








Input
Initial Paraphrase





tie house
Sorry, I don't understand “tie house.” I know



about restaurants, hotels, and other local




businesses, flights, weather, and buying things




online. What are you looking for, and where?


palo alto
I can help you find restaurants, businesses, events, and



things to do in Palo Alto. What are you looking for?


food
Looking for a place to eat? Where? (examples)


Italian food
I can tell you about Italian restaurants in your area.



Where would you like to eat?


burrito
I can help you find places that serve burritos in



your area. Where would you like to eat?


best mexican food
I can help you find good Mexican restaurants in



your area. Where are you?


restaurants in palo alto
Looking for restaurants near Palo Alto.


Italian palo alto
Looking for Italian restaurants near Palo Alto.


thai food in menlo park
Looking for Thai restaurants near Menlo Park


indonesian food in menlo park
Looking for Indonesian restaurants near Menlo Park


best mexican food in Palo Alto
Looking for recommendedMexican restaurants



near Palo Alto.


fast food menlo park
Looking for fast food restaurants near Menlo Park


healthy food in menlo park
Looking for places near Menlo Park that serve




healthy food.



dive bar in menlo park
Looking for dive bars near Menlo Park.


pool room in menlo park
Looking for pool rooms near Menlo Park.


hookah room in menlo park
Looking for places near Menlo Park described as



“hookah room”.


spicy food in sf
Looking for places near Menlo Park that serve




spicy food.



burgers in Menlo park
Looking for places near Menlo Park that serve




burgers.



belly dancing place in sf
Looking for places near San Francisco described



as “belly dancing”.


belly dancing place in menlo park
Looking for places near Menlo Park described as



“belly dancing”.


juke joint in sf
Looking for joints near San Francisco described as



“juke”.


tie house Menlo park
Looking for places near Menlo Park described as



“tie house”.


thai house palo alto
Looking up Thai House in Palo Alto


ii fornaio menlo park
Looking up Il Fornaio in Palo Alto


ii fornao in Menlo park
Looking for places near Palo Alto described as



“il fornao”.


cliff house in Menlo park
Looking up Cliff House in Palo Alto


romantic restaurant in palo alto
Looking for romantic restaurants in Palo Alto


romantic restaurant in palo alto
Looking for romantic restaurants in Palo Alto


quiet romantic restaurant in palo alto
Looking for romantic restaurants in Palo Alto



described as “quiet”


quiet romantic restaurant in palo alto
Looking for romantic restaurants in Palo Alto



described as “quiet


tragically hip restaurant in palo alto
Looking for restaurants in Palo Alto described as



“tragically hip”


tragically hip restaurant in palo alto
Looking for restaurants in Palo Alto described as



“tragically hip”


table for two tonight in palo alto
Checking availability for tonight at restaurants



near Palo Alto.


table for two italian food tonight in
Checking availability for tonight at Italian


Palo alto
restaurants near Palo Alto.


il fornaio palo alto 6pm for 2
Checking availability for tables tonight at




Il Fornaio in Palo Alto.



table for 2 at thai house in PA
Checking availability for tables tonight at Thai




House in Palo Alto.



Pizza delivery in menlo park


I want the best quiet romantic
OK, looking for recommendedromanticitalian


italian restaurant for osso buco in
restaurants near Menlo Park that serve osso buco


or near menlo park
and are described as “quiet”.


Book me a table for 2 at the best
OK, looking for recommendedromanticitalian


quiet romantic italian restaurant for
restaurants near Menlo Parkwith open tables for 2


osso buco in or near menlo park
that serve osso buco and are described as “quiet”.










Refining a Query about Places to Eat


Table 3 provides some examples of paraphrases in response to a situation where user's intent to find a place to eat is known, but they have not selected a particular place to eat. They are facing a list of restaurants, and they provide refinements.


Refinements









TABLE 3





Paraphrases in response to refinements
















menlo park
Thanks, now looking for restaurants in


(was un-known)

Menlo Park.



cheapest
OK, looking for affordable restaurants near




Menlo Park.



chinese
OK, changing cuisine to Chinese. Looking for


(was italian)

Chinese restaurants near Menlo Park



pizza (adding
OK, looking for Italian restaurants near


food item)

Menlo Park that serve pizza.



san francisco
OK, changing location to San Francisco. Looking


(was menlo park)
for Italian restaurants near San Francisco that



serve pizza.


tragically hip
OK, I'll search reviews for “tragically hip”.


quiet romantic
OK, looking for romantic restaurants in Palo Alto



described as “quiet”


cliff house
Cliff House sounds familiar. I'll look it up



in Palo Alto.









Table 4 provides some examples of results summaries that are provided once results are obtained.









TABLE 4







Results Summaries









Input
#Results
Results Summary












tie house
N/A
N/A (no call to services)


palo alto
N/A
N/A (no call to services)


food
N/A
N/A (no call to services)


Italian food
N/A
N/A (no call to services)


burrito
N/A
N/A (no call to services)


best mexican food
N/A
N/A (no call to services)


restaurants palo alto
many
Here are some recommended restaurants




near Palo Alto. Do you prefer any




particular food type?




Would you like a reservation?


Italian palo alto
some
Here are some Italian restaurants near Palo Alto.




To reserve a table, click on available times.


thai food in menlo park
some
Here are some Thai restaurants near Menlo Park.




To reserve a table, click on available times.


indonesian food in menlo
0
Sorry I can't find any Indonesian restaurants near


park


Menlo Park. You could try other cuisines or






locations.



best mexican food in Palo
some
Here are some recommended Mexican restaurants


Alto

near Palo Alto.


fast food menlo park
some
OK, here are some fast food restaurants




near Menlo Park.


healthy food in menlo
some
Here are some places near Menlo Park that might


park

serve healthy food, based on reviews.


dive bar in menlo park
some
Here are some bars near Menlo Park. I don't see




anything specific to “dive bars,” Are there other




ways of saying it?


pool room in menlo park
some
Here are some places in Menlo Park that are




described as pool rooms. You can add other words




to describe what you want.


hookah room in menlo
0
I can't find places Menlo Park matching “hookah


park

room”. Interested in restaurants, hotels,




or local businesses?


spicy food in sf
weak
Here are some places to eat in San Francisco. I



match
don't know which serve spicy food. Could it go by




another name?


burgers in Menlo park
some
You might find burgers at these places to eat near





Menlo Park.



belly dancing place in sf
some
Here are some places in Menlo Park that are




described as “belly dancing”. You can add other




words to describe what you want


belly dancing place in
0
I can help you find restaurants, businesses,


menlo park


events, and things to do in San Francisco,





What are some other words for “belly dancing place”?


juke joint in sf
0
I can help you find restaurants, businesses,





events, and things to do in San Francisco.





What are some other words for “juke joint”?


tie house Menlo park
0
Sorry, I don't know about “tie house” in Menlo





Park. Any other names for it?



thai house palo alto
1
Got it: Thai House restaurant in Palo Alto, CA.




Want to reserve a table? When and for how many?


il fornaio menlo park
weak
There is a Il Fornaio in Palo Alto, which is near



match
Menlo Park.


il fornao in Menlo park
spell
Did you mean Il Fornaio in Palo Alto? If not, try



match
different words.


cliff house in Menlo park
0
I couldn't find Cliff House in Palo Alto. Could it




go by different name or be in a different city?


romantic restaurant in
some
Here are some restaurants near Palo Alto that are


palo alto

described in reviews as romantic.


romantic restaurant in
0
Here are restaurants near Palo Alto. Searching


palo alto

reviews did not find any described as romantic.




Any other preferences?


quiet romantic restaurant
some
Here are some restaurants near Palo Alto that match


in palo alto

“quiet romantic” in reviews.


quiet romantic restaurant
0
Here are some restaurants near Palo Alto.


in palo alto

Searching reviews did find any matching “quiet




romantic”. Any other preferences?


tragically hip restaurant
some
Here are some restaurants near Palo Alto that match


in palo alto

“tragically hip” in reviews.


tragically hip restaurant
0
Here are some restaurants near Palo Alto.


in palo alto

Searching reviews did not find any matching




“tragically hip”. Any other preferences?


table for two italian food
some
Here are restaurants with open tables from 6pm to


tonight in palo alto


8pm tonight for a party of two





in Palo Alto, CA,


table for two italian food
some
Here are restaurants with open tables from 6pm to


tonight in palo alto


8pm tonight for a party of two





in Palo Alto, CA.


il fornaio palo alto 6pm
1
Here are table options at Il Fornaio restaurant in


for 2


Palo Alto, CA at 6pm today for





a party of 2.


table for 2 at thai house
1
Here is information for Thai House in Palo Alto,


in PA


CA. You can call them at the phone number listed.



pizza delivery in menlo

Here are places that serve pizza in menlo park. I do


park

not have delivery options at this time. Click on




restaurant phone number to call for delivery.


I want the best quiet
weak
Here are the best matches for recommended


romantic italian
match,

romantic italian restaurant near Menlo Park that



restaurant for osso buco
soiled by
serve osso buco and are described as “quiet”. Click


in or near menlo park
availability
on available times to reserve a table.


Book me a table for 2 at
weak
Here are the best matches for recommended


the best quiet romantic
match,

romantic italian restaurants near Menlo Park



italian restaurant for osso
sorted by
with open tables for 2 that serve osso buco


buco in or near menlo
availability
and are described as “quiet”. Click on available


park

times to reserve a table.


refinements


menlo park (was un-
some
Here are some recommended restaurants near


known)


Menlo Park. Do you prefer any particular





food type?


cheapest
some
I found 4 affordable restaurants near Menlo Park.


chinese (was italian)
some
I found 4 Chinese restaurants near Menlo Park.


pizza (adding food item)
some
I found 4 Italian restaurants near Menlo Park that




serve pizza.


san Francisco (was menlo
some
I found 4 Italian restaurants near San Francisco.


park)


tragically hip
some
I found 4 restaurants near Palo Alto that match




“tragically hip” in reviews.


quiet romantic
some
Here are some restaurants near Palo Alto that match




“quiet romantic” in reviews.


cliff house
0
I couldn't find Cliff House in Palo Alto. Could it




go by a different name or be in a different city?









Table 5 provides some examples of prompts that are provided when users click on active links.


Prompts when Users Click on Active Links









TABLE 5







Prompts when users click on active links









Anchor Text
Prompt Text
Notes





Location, where
Enter a location: a city, zip code, or
This prompt might be used when



“near” followed by the name of a
the user has not specified a



place.
location yet


Palo Alto
Enter a location such as a city,
This prompt might be used when



neighborhood, street address, or
the user is changing locations.



“near” followed by a landmark.


food type
Enter a food category such as
Merge food type and cuisine can



Chinese or Pizza.
be merged


Italian
You can try other food categories
User already said Italian.



such as Chinese, or a favorite food
Assistant 1002 is helping the



item such as stake.
user explore alternatives. If it is




a food item, if dominates over




cuisine.


reservation
Enter the day and time to reserve a
Prompting for a reservation



table, such as “tomorrow at 8”.


healthy food
You can also enter menu items or
Known food type



cuisines


spicy food
You can also enter menu items or
Unknown food type



cuisines


restaurants
What kind of restaurant? (e.g.,
Clicking on the restaurants link



Chinese, Pizza)
should insert the wood




“restaurant” on the end of the




text input.


businesses
You can find local florists, ATMs,
Clicking on the businesses link



doctors, drug stores, and the like
should add to the machine



What kind of business are you
readable tag that this is a local



looking for?
search


events
You can discover upcoming



converts, shows and the like What



interests you?


things to do
Music, art, theater, sports, and the



like What kind of thing would you



like to do in this area?


hotels
I can help you find an available



hotel room. Any preferences for



amenities or location?


weather
Enter a city, and I'll tell you what
If location is known, just show



the weather is like there.
the weather data


buying things
I can help you find music, movies,



books, electronics, toys and more --



and buy it from Amazon. What are



you looking for?










Suggesting Possible Responses in a Dialog


In one embodiment, assistant 1002 provides contextual suggestions. Suggestions a way for assistant 1002 to offer the user options to move forward from his or her current situation in the dialog. The set of suggestions offered by assistant 1002 depends on context, and the number of suggestions offered may depend on the medium and form factor. For example, in one embodiment, the most salient suggestions may be offered in line in the dialog, an extended list of suggestions (“more”) may be offered in a scrollable menu, and even more suggestions are reachable by typing a few characters and picking from autocomplete options. One skilled in the art will recognize that other mechanisms may be used for providing suggestions.


In various embodiments, different types of suggestions may be provided. Examples of suggestion types include:

    • options to refine a query, including adding or removing or changing constraint values;
    • options to repair or recover from bad situations, such as “not what I mean” or “start over” or “search the web”;
    • options to disambiguate among;
    • interpretations of speech;
    • interpretations of text, including spell correction and semantic ambiGUIty;
    • context-specific commands, such as “show these on a map” or “send directions to my date” or “explain these results”;
    • suggested cross-selling offers, such as next steps in meal or event planning scenarios;
    • options to reuse previous commands, or parts of them.


In various embodiments, the context that determines the most relevant suggestions may be derived from, for example:

    • dialog state
    • user state, including, for example:
      • static properties (name, home address, etc)
      • dynamic properties (location, time, network speed)
    • interaction history, including, for example:
      • query history
      • results history
      • the text that has been entered so far into autocomplete.


In various embodiments, suggestions may be generated by any mechanism, such as for example:

    • paraphrasing a domain, task, or constraint based on the ontology model;
    • prompting in autocomplete based on the current domain and constraints;
    • paraphrasing ambiguous alternative interpretations;
    • alternative interpretations of speech-to-text;
    • hand authoring, based on special dialog conditions.


According to one embodiment, suggestions are generated as operations on commands in some state of completion. Commands are explicit, canonical representations of requests, including assumptions and inferences, based on attempted interpretations on user input. In situations where the user input is incomplete or ambiguous, suggestions are an attempt to help the user adjust the input to clarify the command.


In one embodiment, each command is an imperative sentence having some combination of a

    • command verb (imperative such as “find” or “where is”);
    • domain (selection class such as “restaurants”);
    • constraint(s) such as location=Palo Alto and cuisine=Italian.


These parts of a command (verb, domain, constraints) correspond to nodes in the ontology.


A suggestion, then, may be thought of as operations on a command, such as setting it, changing it, or declaring that it is relevant or not relevant. Examples include:

    • setting a command verb or domain (“find restaurants”)
    • changing a command verb (“book it”, “map it”, “save it”)
    • changing a domain (“looking for a restaurant, not a local business”)
    • stating that a constraint is relevant (“try refining by cuisine”)
    • choosing a value for a constraint (“Italian”, “French”, and the like)
    • choosing a constraint and value together (“near here”, “tables for 2”)
    • stating that a constraint value is wrong (“not that Boston”)
    • stating that a constraint is not relevant (“ignore the expense”)
    • stating the intent to change a constraint value (“try a different location”)
    • changing a constraint value (“Italian, not Chinese”)
    • adding to a constraint value (“and with a pool, too”)
    • snapping a value to grid (“Los Angeles, not los angelos”)
    • initiating a new command, reusing context ([after movies] “find nearby restaurants”, “send directions to my friend”)
    • initiating a command that is “meta” to context (“explain these results”)
    • initiating a new command, resetting or ignoring context (“start over”, “help with speech”)


A suggestion may also involve some combination of the above. For example:

    • “the movie Milk not [restaurants serving] the food item milk”
    • “restaurants serving pizza, not just pizza joints”
    • “The place called Costco in Mountain View, 1 don't care whether you think it is a restaurant or local business”
    • “Chinese in mountain view” [a recent query]


In one embodiment, assistant 1002 includes a general mechanism to maintain a list of suggestions, ordered by relevance. The format in which a suggestion is offered may differ depending on current context, mode, and form factor of the device.


In one embodiment, assistant 1002 determines which constraints to modify by considering any or all of the following factors:

    • Consider whether the constraint has a value;
    • Consider whether the constraint was inferred or explicitly stated;
    • Consider its salience (suggestionIndex).


In one embodiment, assistant 1002 determines an output format for the suggestion. Examples of output formats include:

    • change domain:
      • if autocomplete option “find restaurants”, then “try something different”
      • else [was inferred] “not looking for restaurants”
    • change name constraint:
      • if name was inferred, offer alterative ambiguous interpretation”
      • stuff into autocomplete the entity names from current results
      • different name
      • consider that it wasn't a name lookup (remove constraint)—maybe offer category in place of it
    • “not named”
    • “not in Berkeley”
    • “some other day”
    • not that sense of (use ambiguity alternatives)
    • inferred date: “any day, I don't need a reservation”


In one embodiment, assistant 1002 attempts to resolve ambiguities via suggestions. For example, if the set of current interpretations of user intent is too ambiguous 310, then suggestions are one way to prompt for more information 322. In one embodiment, for constrained selection tasks, assistant 1002 factors out common constraints among ambiguous interpretations of intent 290 and presents the differences among them to the user. For example, if the user input includes the word “café” and this word could match the name of a restaurant or the type of restaurant, then assistant 102 can ask “did you mean restaurants named ‘café’ or ‘café restaurants’?”


In one embodiment, assistant 1002 infers constraints under certain situations. That is, for constrained selection tasks, not all constraints need be mentioned explicitly in the user input; some can be inferred from other information available in active ontology 1050, short term memory 1052, and/or other sources of information available to assistant 1002. For example:

    • Inferring domain or location
    • Default assumption, like location
    • Weakly matched constraint (fuzzy, low salience location, etc)
    • Ambiguous criteria (match to constraint value without prefix (name vs. category, often ambiguous)


In cases where the assistant 1002 infers constraint values, it may also offer these assumptions as suggestions for the user to overrule. For example, it might tell the user “I assumed you meant around here. Would you like to look at a different location?”


The present invention has been described in particular detail with respect to possible embodiments. Those of skill in the art will appreciate that the invention may be practiced in other embodiments. First, the particular naming of the components, capitalization of terms, the attributes, data structures, or any other programming or structural aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, formats, or protocols. Further, the system may be implemented via a combination of hardware and software, as described, or entirely in hardware elements, or entirely in software elements. Also, the particular division of functionality between the various system components described herein is merely exemplary, and not mandatory; functions performed by a single system component may instead be performed by multiple components, and functions performed by multiple components may instead be performed by a single component.


In various embodiments, the present invention can be implemented as a system or a method for performing the above-described techniques, either singly or in any combination. In another embodiment, the present invention can be implemented as a computer program product comprising a nontransitory computer-readable storage medium and computer program code, encoded on the medium, for causing a processor in a computing device or other electronic device to perform the above-described techniques.


Reference in the specification to “one embodiment” or to “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.


Some portions of the above are presented in terms of algorithms and symbolic representations of operations on data bits within a memory of a computing device. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps (instructions) leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared and otherwise manipulated. It is convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. Furthermore, it is also convenient at times, to refer to certain arrangements of steps requiring physical manipulations of physical quantities as modules or code devices, without loss of generality.


It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “displaying” or “determining” or the like, refer to the action and processes of a computer system, or similar electronic computing module and/or device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system memories or registers or other such information storage, transmission or display devices.


Certain aspects of the present invention include process steps and instructions described herein in the form of an algorithm. It should be noted that the process steps and instructions of the present invention can be embodied in software, firmware and/or hardware, and when embodied in software, can be downloaded to reside on and be operated from different platforms used by a variety of operating systems.


The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in the computing device. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. Further, the computing devices referred to herein may include a single processor or may be architectures employing multiple processor designs for increased computing capability.


The algorithms and displays presented herein are not inherently related to any particular computing device, virtualized system, or other apparatus. Various general-purpose systems may also be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will be apparent from the description provided herein. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any references above to specific languages are provided for disclosure of enablement and best mode of the present invention.


Accordingly, in various embodiments, the present invention can be implemented as software, hardware, and/or other elements for controlling a computer system, computing device, or other electronic device, or any combination or plurality thereof. Such an electronic device can include, for example, a processor, an input device (such as a keyboard, mouse, touchpad, trackpad, joy-stick, trackball, microphone, and/or any combination thereof), an output device (such as a screen, speaker, and/or the like), memory, long-term storage (such as magnetic storage, optical storage, and/or the like), and/or network connectivity, according to techniques that are well known in the art. Such an electronic device may be portable or nonportable. Examples of electronic devices that may be used for implementing the invention include: a mobile phone, personal digital assistant, smartphone, kiosk, desktop computer, laptop computer, tablet computer, consumer electronic device, consumer entertainment device; music player; camera; television; set-top box; electronic gaming unit; or the like. An electronic device for implementing the present invention may use any operating system such as, for example, iOS or MacOS, available from Apple Inc. of Cupertino, California, or any other operating system that is adapted for use on the device.


While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of the above description, will appreciate that other embodiments may be devised which do not depart from the scope of the present invention as described herein. In addition, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the claims.

Claims
  • 1. An electronic device, comprising: one or more processors;a memory; andone or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, within a communication session between a user and a digital assistant, a user request for the digital assistant to facilitate a restaurant reservation;in response to receiving the user request for the digital assistant to facilitate the restaurant reservation, facilitating the restaurant reservation by: identifying one or more restaurant reservation parameters;determining one or more values for the one or more restaurant reservation parameters;transmitting the one or more values to a restaurant reservation service;receiving a response from the restaurant reservation service indicating whether the restaurant reservation was successfully made; andproviding, in the communication session, an output corresponding to the received response.
  • 2. The electronic device of claim 1, the one or more programs including instructions for: displaying, in the communication session, a plurality of restaurants; andreceiving, from the user, a selection of a restaurant from the plurality of restaurants.
  • 3. The electronic device of claim 1, wherein identifying one or more restaurant reservation parameters further comprises: identifying a restaurant domain; andselecting the one or more restaurant reservation parameters from the restaurant domain.
  • 4. The electronic device of claim 1, the one or more programs including instructions for: identifying the restaurant reservation service based on at least one of user history or user preference.
  • 5. The electronic device of claim 1, the one or more programs including instructions for: identifying the restaurant reservation service based on at least one of reliability information, user reviews, and cost information.
  • 6. The electronic device of claim 1, the one or more programs including instructions for: after receiving the response from the restaurant reservation service, storing the restaurant reservation.
  • 7. The electronic device of claim 1, wherein the restaurant reservation service is a third party service.
  • 8. The electronic device of claim 1, wherein determining the one or more values for the one or more restaurant reservation parameters further comprises: prompting the user to provide the one or more values for the one or more restaurant reservation parameters; andreceiving, from the user, an input specifying the one or more values for the one or more restaurant reservation parameters.
  • 9. The electronic device of claim 8, wherein prompting the user to provide the one or more values for one or more one or more values for the one or more restaurant reservation parameters further comprises: displaying, in the communication session, a plurality of candidate values; andreceiving, from the user, the input specifying the one or more values for the one or more restaurant reservation parameters further comprises receiving, from the user, a selection of a candidate value of the plurality of candidate values.
  • 10. The electronic device of claim 1, the one or more programs including instructions for: performing a semantic analysis on the user request to determine whether the user request includes a request for the digital assistant to facilitate the restaurant reservation.
  • 11. The electronic device of claim 10, wherein performing the semantic analysis includes performing natural language processing.
  • 12. The electronic device of claim 10, wherein performing the semantic analysis further comprises: determining whether one or more words of the user request are associated with a restaurant domain; anddetermining whether the one or more words of the user request are associated with a task of reserving a table identified by the restaurant domain.
  • 13. The electronic device of claim 10, the one or more programs including instructions for: identifying a restaurant of a plurality of restaurants based on the semantic analysis of the user request.
  • 14. A non-transitory computer-readable medium storing one or more programs comprising instructions, wherein the instructions, when executed by one or more processors of an electronic device, cause the electronic device to: receive, within a communication session between a user and a digital assistant, a user request for the digital assistant to facilitate a restaurant reservation;in response to receiving the user request for the digital assistant to facilitate the restaurant reservation, facilitate the restaurant reservation by: identifying one or more restaurant reservation parameters;determining one or more values for the one or more restaurant reservation parameters;transmitting the one or more values to a restaurant reservation service;receiving a response from the restaurant reservation service indicating whether the restaurant reservation was successfully made; andproviding, in the communication session, an output corresponding to the received response.
  • 15. The non-transitory computer-readable medium of claim 14, wherein the instructions cause the electronic device to: display, in the communication session, a plurality of restaurants; andreceive, from the user, a selection of a restaurant from the plurality of restaurants.
  • 16. The non-transitory computer-readable medium of claim 14, wherein identifying one or more restaurant reservation parameters further comprises: identifying a restaurant domain; andselecting the one or more restaurant reservation parameters from the restaurant domain.
  • 17. The non-transitory computer-readable medium of claim 14, wherein the instructions cause the electronic device to: identify the restaurant reservation service based on at least one of user history or user preference.
  • 18. The non-transitory computer-readable medium of claim 14 wherein the instructions cause the electronic device to: identify the restaurant reservation service based on at least one of reliability information, user reviews, and cost information.
  • 19. The non-transitory computer-readable medium of claim 14, wherein the instructions cause the electronic device to: after receiving the response from the restaurant reservation service, store the restaurant reservation.
  • 20. The non-transitory computer-readable medium of claim 14, wherein the restaurant reservation service is a third party service.
  • 21. The non-transitory computer-readable medium of claim 14, wherein determining the one or more values for the one or more restaurant reservation parameters further comprises: prompting the user to provide the one or more values for the one or more restaurant reservation parameters; andreceiving, from the user, an input specifying the one or more values for the one or more restaurant reservation parameters.
  • 22. The non-transitory computer-readable medium of claim 21, wherein prompting the user to provide the one or more values for the one or more restaurant reservation parameters further comprises: displaying, in the communication session, a plurality of candidate values; andreceiving, from the user, the input specifying the one or more values for the one or more restaurant reservation parameters further comprises receiving, from the user, a selection of a candidate value of the plurality of candidate values.
  • 23. The non-transitory computer-readable medium of claim 14, wherein the instructions cause the electronic device to: perform a semantic analysis on the user request to determine whether the user request includes a request for the digital assistant to facilitate the restaurant reservation.
  • 24. The non-transitory computer-readable medium of claim 23, wherein performing the semantic analysis includes performing natural language processing.
  • 25. The non-transitory computer-readable medium of claim 23, wherein performing the semantic analysis further comprises: determining whether one or more words of the user request are associated with a restaurant domain; anddetermining whether the one or more words of the user request are associated with a task of reserving a table identified by the restaurant domain.
  • 26. The non-transitory computer-readable medium of claim 23, wherein the instructions cause the electronic device to: identify a restaurant of a plurality of restaurants based on the semantic analysis of the user request.
  • 27. A computer-implemented method, comprising: at an electronic device with one or more processors and memory:receiving, within a communication session between a user and a digital assistant, a user request for the digital assistant to facilitate a restaurant reservation;in response to receiving the user request for the digital assistant to facilitate the restaurant reservation, facilitating the restaurant reservation by: identifying one or more restaurant reservation parameters;determining one or more values for the one or more restaurant reservation parameters;transmitting the one or more values to a restaurant reservation service;receiving a response from the restaurant reservation service indicating whether the restaurant reservation was successfully made; andproviding, in the communication session, an output corresponding to the received response.
  • 28. The method of claim 27, comprising: displaying, in the communication session, a plurality of restaurants; andreceiving, from the user, a selection of a restaurant from the plurality of restaurants.
  • 29. The method of claim 27, wherein identifying one or more restaurant reservation parameters further comprises: identifying a restaurant domain; andselecting the one or more restaurant reservation parameters from the restaurant domain.
  • 30. The method of claim 27, comprising: identifying the restaurant reservation service based on at least one of user history or user preference.
  • 31. The method of claim 27, comprising: identifying the restaurant reservation service based on at least one of reliability information, user reviews, and cost information.
  • 32. The method of claim 27, comprising: after receiving the response from the restaurant reservation service, storing the restaurant reservation.
  • 33. The method of claim 27, wherein the restaurant reservation service is a third party service.
  • 34. The method of claim 27, wherein determining the one or more values for the one or more restaurant reservation parameters further comprises: prompting the user to provide the one or more values for the one or more restaurant reservation parameters; andreceiving, from the user, an input specifying the one or more values for the one or more restaurant reservation parameters.
  • 35. The method of claim 34, wherein prompting the user to provide the one or more values for the one or more restaurant reservation parameters further comprises: displaying, in the communication session, a plurality of candidate values; andreceiving, from the user, the input specifying the one or more values for the one or more restaurant reservation parameters further comprises receiving, from the user, a selection of a candidate value of the plurality of candidate values.
  • 36. The method of claim 27, comprising: performing a semantic analysis on the user request to determine whether the user request includes a request for the digital assistant to facilitate the restaurant reservation.
  • 37. The method of claim 36, wherein performing the semantic analysis includes performing natural language processing.
  • 38. The method of claim 36, wherein performing the semantic analysis further comprises: determining whether one or more words of the user request are associated with a restaurant domain; anddetermining whether the one or more words of the user request are associated with a task of reserving a table identified by the restaurant domain.
  • 39. The method of claim 36, comprising: identifying a restaurant of a plurality of restaurants based on the semantic analysis of the user request.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 16/879,643, entitled “Task Flow Identification Based on User Intent,” filed May 20, 2020, (now granted as U.S. Pat. No. 11,423,886), which is a continuation of U.S. application Ser. No. 15/394,162, entitled “Task Flow Identification Based on User Intent,” filed Dec. 29, 2016, (now granted as U.S. Pat. No. 10,706,841), which is a continuation of U.S. application Ser. No. 13/492,809, entitled “Intelligent Automated Assistant,” filed Jun. 9, 2012 (now granted as U.S. Pat. No. 9,548,050), which is a continuation of U.S. application Ser. No. 12/987,982, entitled “Intelligent Automated Assistant,” filed Jan. 10, 2011 (now granted as U.S. Pat. No. 9,318,108), which claims the benefit of U.S. Provisional Patent Application Ser. No. 61/295,774, entitled “Intelligent Automated Assistant”, filed Jan. 18, 2010, each of which are hereby incorporated by reference in their entirety for all purposes. This application is further related to U.S. patent application Ser. No. 11/518,292 for “Method and Apparatus for Building an Intelligent Automated Assistant”, filed Sep. 8, 2006, which is incorporated herein by reference. This application is further related to U.S. Provisional Patent Application Ser. No. 61/186,414 for “System and Method for Semantic Auto-Completion”, filed Jun. 12, 2009, which is incorporated herein by reference.

US Referenced Citations (3218)
Number Name Date Kind
4955047 Morganstein et al. Sep 1990 A
5047614 Bianco Sep 1991 A
5377103 Lamberti et al. Dec 1994 A
5621903 Luciw et al. Apr 1997 A
5729704 Stone et al. Mar 1998 A
5862223 Walker et al. Jan 1999 A
6070139 Miyazawa et al. May 2000 A
6324512 Junqua et al. Nov 2001 B1
6347315 Kiyoki et al. Feb 2002 B1
6510417 Woods et al. Jan 2003 B1
6526382 Yuschik Feb 2003 B1
6622136 Russell Sep 2003 B2
6640098 Roundtree Oct 2003 B1
6697824 Bowman-Amuah Feb 2004 B1
6721728 McGreevy Apr 2004 B2
6762692 Mingot et al. Jul 2004 B1
6772123 Cooklev et al. Aug 2004 B2
6836537 Zirngibl et al. Dec 2004 B1
6931384 Horvitz et al. Aug 2005 B1
6965863 Zuberec et al. Nov 2005 B1
7085723 Ross et al. Aug 2006 B2
7127403 Saylor et al. Oct 2006 B1
7171360 Huang et al. Jan 2007 B2
7203297 Vitikainen et al. Apr 2007 B2
7228278 Nguyen et al. Jun 2007 B2
7257537 Ross et al. Aug 2007 B2
7293015 Zhou Nov 2007 B2
7302394 Baray et al. Nov 2007 B1
7398209 Kennewick et al. Jul 2008 B2
7447637 Grant et al. Nov 2008 B1
7460652 Chang Dec 2008 B2
7552055 Lecoeuche Jun 2009 B2
7562082 Zhou Jul 2009 B2
7657828 Lucas et al. Feb 2010 B2
7684990 Caskey et al. Mar 2010 B2
7757176 Vakil et al. Jul 2010 B2
7818176 Freeman et al. Oct 2010 B2
7996228 Miller et al. Aug 2011 B2
8056070 Goller et al. Nov 2011 B2
8090571 Elshishiny et al. Jan 2012 B2
8095364 Longe et al. Jan 2012 B2
8099289 Mozer et al. Jan 2012 B2
8099395 Pabla et al. Jan 2012 B2
8099418 Inoue et al. Jan 2012 B2
8103510 Sato Jan 2012 B2
8103947 Lunt et al. Jan 2012 B2
8107401 John et al. Jan 2012 B2
8112275 Kennewick et al. Feb 2012 B2
8112280 Lu Feb 2012 B2
8115772 Ostermann et al. Feb 2012 B2
8117026 Lee et al. Feb 2012 B2
8117037 Gazdzinski Feb 2012 B2
8117542 Radtke et al. Feb 2012 B2
8121413 Hwang et al. Feb 2012 B2
8121837 Agapi et al. Feb 2012 B2
8122094 Kotab Feb 2012 B1
8122353 Bouta Feb 2012 B2
8130929 Wilkes et al. Mar 2012 B2
8131557 Davis et al. Mar 2012 B2
8135115 Hogg, Jr. et al. Mar 2012 B1
8138912 Singh et al. Mar 2012 B2
8140330 Cevik et al. Mar 2012 B2
8140335 Kennewick et al. Mar 2012 B2
8140368 Eggenberger et al. Mar 2012 B2
8140567 Padovitz et al. Mar 2012 B2
8145489 Freeman et al. Mar 2012 B2
8150694 Kennewick et al. Apr 2012 B2
8150700 Shin et al. Apr 2012 B2
8155956 Cho et al. Apr 2012 B2
8156005 Vieri Apr 2012 B2
8156060 Borzestowski et al. Apr 2012 B2
8160877 Nucci et al. Apr 2012 B1
8160883 Lecoeuche Apr 2012 B2
8165321 Paquier et al. Apr 2012 B2
8165886 Gagnon et al. Apr 2012 B1
8166019 Lee et al. Apr 2012 B1
8166032 Sommer et al. Apr 2012 B2
8170790 Lee et al. May 2012 B2
8170966 Musat et al. May 2012 B1
8171137 Parks et al. May 2012 B1
8175872 Kristjansson et al. May 2012 B2
8175876 Bou-ghazale et al. May 2012 B2
8179370 Yamasani et al. May 2012 B1
8188856 Singh et al. May 2012 B2
8190359 Bourne May 2012 B2
8190596 Nambiar et al. May 2012 B2
8194827 Jaiswal et al. Jun 2012 B2
8195460 Degani et al. Jun 2012 B2
8195467 Mozer et al. Jun 2012 B2
8195468 Weider et al. Jun 2012 B2
8200489 Baggenstoss Jun 2012 B1
8200495 Braho et al. Jun 2012 B2
8201109 Van Os et al. Jun 2012 B2
8204238 Mozer Jun 2012 B2
8205788 Gazdzinski et al. Jun 2012 B1
8209177 Sakuma et al. Jun 2012 B2
8209183 Patel et al. Jun 2012 B1
8213911 Williams et al. Jul 2012 B2
8219115 Nelissen Jul 2012 B1
8219406 Yu et al. Jul 2012 B2
8219407 Roy et al. Jul 2012 B1
8219555 Mianji Jul 2012 B1
8219608 alSafadi et al. Jul 2012 B2
8224649 Chaudhari et al. Jul 2012 B2
8224757 Bohle Jul 2012 B2
8228299 Maloney et al. Jul 2012 B1
8233919 Haag et al. Jul 2012 B2
8234111 Lloyd et al. Jul 2012 B2
8239206 LeBeau et al. Aug 2012 B1
8239207 Seligman et al. Aug 2012 B2
8244545 Paek et al. Aug 2012 B2
8244712 Serlet et al. Aug 2012 B2
8250071 Killalea et al. Aug 2012 B1
8254829 Kindred et al. Aug 2012 B1
8255216 White Aug 2012 B2
8255217 Stent et al. Aug 2012 B2
8260117 Xu et al. Sep 2012 B1
8260247 Lazaridis et al. Sep 2012 B2
8260617 Dhanakshirur et al. Sep 2012 B2
8260619 Bansal et al. Sep 2012 B1
8270933 Riemer et al. Sep 2012 B2
8271287 Kermani Sep 2012 B1
8275621 Alewine et al. Sep 2012 B2
8275736 Guo et al. Sep 2012 B2
8279171 Hirai et al. Oct 2012 B2
8280438 Barbera Oct 2012 B2
8285546 Reich Oct 2012 B2
8285551 Gazdzinski Oct 2012 B2
8285553 Gazdzinski Oct 2012 B2
8285737 Lynn et al. Oct 2012 B1
8290274 Mori et al. Oct 2012 B2
8290777 Nguyen et al. Oct 2012 B1
8290778 Gazdzinski Oct 2012 B2
8290781 Gazdzinski Oct 2012 B2
8296124 Holsztynska et al. Oct 2012 B1
8296145 Clark et al. Oct 2012 B2
8296146 Gazdzinski Oct 2012 B2
8296153 Gazdzinski Oct 2012 B2
8296380 Kelly et al. Oct 2012 B1
8296383 Lindahl Oct 2012 B2
8300776 Davies et al. Oct 2012 B2
8300801 Sweeney et al. Oct 2012 B2
8301456 Gazdzinski Oct 2012 B2
8311189 Champlin et al. Nov 2012 B2
8311834 Gazdzinski Nov 2012 B1
8311835 Lecoeuche Nov 2012 B2
8311838 Lindahl et al. Nov 2012 B2
8312017 Martin et al. Nov 2012 B2
8321786 Lunati Nov 2012 B2
8326627 Kennewick et al. Dec 2012 B2
8332205 Krishnan et al. Dec 2012 B2
8332218 Cross, Jr. et al. Dec 2012 B2
8332224 Di Cristo et al. Dec 2012 B2
8332748 Karam Dec 2012 B1
8335689 Wittenstein et al. Dec 2012 B2
8340975 Rosenberger Dec 2012 B1
8345665 Vieri et al. Jan 2013 B2
8346563 Hjelm et al. Jan 2013 B1
8346757 Lamping et al. Jan 2013 B1
8352183 Thota et al. Jan 2013 B2
8352268 Naik et al. Jan 2013 B2
8352272 Rogers et al. Jan 2013 B2
8355919 Silverman et al. Jan 2013 B2
8359234 Vieri Jan 2013 B2
8370145 Endo et al. Feb 2013 B2
8370158 Gazdzinski Feb 2013 B2
8371503 Gazdzinski Feb 2013 B2
8374871 Ehsani et al. Feb 2013 B2
8375320 Kotler et al. Feb 2013 B2
8380504 Peden et al. Feb 2013 B1
8380507 Herman et al. Feb 2013 B2
8381107 Rottler et al. Feb 2013 B2
8381135 Hotelling et al. Feb 2013 B2
8386485 Kerschberg et al. Feb 2013 B2
8386926 Matsuoka et al. Feb 2013 B1
8391844 Novick et al. Mar 2013 B2
8392717 Chai et al. Mar 2013 B2
8396295 Gao et al. Mar 2013 B2
8396714 Rogers et al. Mar 2013 B2
8396715 Odell et al. Mar 2013 B2
8401163 Kirchhoff et al. Mar 2013 B1
8406745 Upadhyay et al. Mar 2013 B1
8407239 Dean et al. Mar 2013 B2
8423288 Stahl et al. Apr 2013 B2
8428758 Naik et al. Apr 2013 B2
8433572 Caskey et al. Apr 2013 B2
8433778 Shreesha et al. Apr 2013 B1
8434133 Kulkarni et al. Apr 2013 B2
8442821 Vanhoucke May 2013 B1
8447612 Gazdzinski May 2013 B2
8452597 Bringert et al. May 2013 B2
8452602 Bringert et al. May 2013 B1
8453058 Coccaro et al. May 2013 B1
8457959 Kaiser Jun 2013 B2
8458115 Cai et al. Jun 2013 B2
8458278 Christie et al. Jun 2013 B2
8463592 Lu et al. Jun 2013 B2
8464150 Davidson et al. Jun 2013 B2
8473289 Jitkoff et al. Jun 2013 B2
8473485 Wong et al. Jun 2013 B2
8477323 Low et al. Jul 2013 B2
8478816 Parks et al. Jul 2013 B2
8479122 Hotelling et al. Jul 2013 B2
8484027 Murphy Jul 2013 B1
8489599 Bellotti Jul 2013 B2
8498670 Cha et al. Jul 2013 B2
8498857 Kopparapu et al. Jul 2013 B2
8514197 Shahraray et al. Aug 2013 B2
8515736 Duta Aug 2013 B1
8515750 Lei et al. Aug 2013 B1
8521513 Millett et al. Aug 2013 B2
8521526 Lloyd et al. Aug 2013 B1
8521531 Kim Aug 2013 B1
8521533 Ostermann et al. Aug 2013 B1
8527276 Senior et al. Sep 2013 B1
8533266 Koulomzin et al. Sep 2013 B2
8537033 Gueziec Sep 2013 B2
8539342 Lewis Sep 2013 B1
8543375 Hong Sep 2013 B2
8543397 Nguyen Sep 2013 B1
8543398 Strope et al. Sep 2013 B1
8560229 Park et al. Oct 2013 B1
8560366 Mikurak Oct 2013 B2
8571528 Channakeshava Oct 2013 B1
8571851 Tickner et al. Oct 2013 B1
8577683 Dewitt Nov 2013 B2
8583416 Huang et al. Nov 2013 B2
8583511 Hendrickson Nov 2013 B2
8583638 Donelli Nov 2013 B2
8589156 Burke et al. Nov 2013 B2
8589161 Kennewick et al. Nov 2013 B2
8589374 Chaudhari Nov 2013 B2
8589869 Wolfram Nov 2013 B2
8589911 Sharkey et al. Nov 2013 B1
8595004 Koshinaka Nov 2013 B2
8595642 Lagassey Nov 2013 B1
8600743 Lindahl et al. Dec 2013 B2
8600746 Lei et al. Dec 2013 B1
8600930 Sata et al. Dec 2013 B2
8606090 Eyer Dec 2013 B2
8606568 Tickner et al. Dec 2013 B1
8606576 Barr et al. Dec 2013 B1
8606577 Stewart et al. Dec 2013 B1
8615221 Cosenza et al. Dec 2013 B1
8620659 Di Cristo et al. Dec 2013 B2
8620662 Bellegarda Dec 2013 B2
8626681 Jurca et al. Jan 2014 B1
8630841 Van Caldwell et al. Jan 2014 B2
8635073 Chang Jan 2014 B2
8638363 King et al. Jan 2014 B2
8639516 Lindahl et al. Jan 2014 B2
8645128 Agiomyrgiannakis Feb 2014 B1
8645137 Bellegarda et al. Feb 2014 B2
8645138 Weinstein et al. Feb 2014 B1
8654936 Eslambolchi et al. Feb 2014 B1
8655646 Lee et al. Feb 2014 B2
8655901 Li et al. Feb 2014 B1
8660843 Falcon et al. Feb 2014 B2
8660849 Gruber et al. Feb 2014 B2
8660924 Hoch et al. Feb 2014 B2
8660970 Fiedorowicz Feb 2014 B1
8661112 Creamer et al. Feb 2014 B2
8661340 Goldsmith et al. Feb 2014 B2
8670979 Gruber et al. Mar 2014 B2
8675084 Bolton et al. Mar 2014 B2
8676273 Fujisaki Mar 2014 B1
8676583 Gupta et al. Mar 2014 B2
8676904 Lindahl Mar 2014 B2
8677377 Cheyer et al. Mar 2014 B2
8681950 Mack et al. Mar 2014 B2
8682667 Haughay Mar 2014 B2
8687777 Lavian et al. Apr 2014 B1
8688446 Yanagihara Apr 2014 B2
8688453 Joshi et al. Apr 2014 B1
8689135 Portele et al. Apr 2014 B2
8694322 Snitkovskiy et al. Apr 2014 B2
8695074 Saraf et al. Apr 2014 B2
8696364 Cohen Apr 2014 B2
8706472 Ramerth et al. Apr 2014 B2
8706474 Blume et al. Apr 2014 B2
8706503 Cheyer et al. Apr 2014 B2
8707195 Fleizach et al. Apr 2014 B2
8712778 Thenthiruperai Apr 2014 B1
8713119 Lindahl et al. Apr 2014 B2
8713418 King et al. Apr 2014 B2
8719006 Bellegarda May 2014 B2
8719014 Wagner May 2014 B2
8719039 Sharifi May 2014 B1
8731610 Appaji May 2014 B2
8731912 Tickner et al. May 2014 B1
8731942 Cheyer et al. May 2014 B2
8739208 Davis et al. May 2014 B2
8744852 Seymour et al. Jun 2014 B1
8751971 Fleizach et al. Jun 2014 B2
8760537 Johnson et al. Jun 2014 B2
8762145 Ouchi et al. Jun 2014 B2
8762156 Chen Jun 2014 B2
8762469 Lindahl Jun 2014 B2
8768693 Somekh et al. Jul 2014 B2
8768702 Mason et al. Jul 2014 B2
8775154 Clinchant et al. Jul 2014 B2
8775177 Heigold et al. Jul 2014 B1
8775341 Commons Jul 2014 B1
8775931 Fux et al. Jul 2014 B2
8781456 Prociw Jul 2014 B2
8781841 Wang Jul 2014 B1
8793301 Wegenkittl et al. Jul 2014 B2
8798255 Lubowich et al. Aug 2014 B2
8798995 Edara Aug 2014 B1
8799000 Guzzoni et al. Aug 2014 B2
8805684 Aleksic et al. Aug 2014 B1
8805690 Lebeau et al. Aug 2014 B1
8812299 Su Aug 2014 B1
8812302 Xiao et al. Aug 2014 B2
8812321 Gilbert et al. Aug 2014 B2
8823507 Touloumtzis Sep 2014 B1
8823793 Clayton et al. Sep 2014 B2
8825474 Zhai et al. Sep 2014 B1
8831947 Wasserblat et al. Sep 2014 B2
8831949 Smith et al. Sep 2014 B1
8838457 Cerra et al. Sep 2014 B2
8855915 Furuhata et al. Oct 2014 B2
8861925 Ohme Oct 2014 B1
8862252 Rottler et al. Oct 2014 B2
8868111 Kahn et al. Oct 2014 B1
8868409 Mengibar et al. Oct 2014 B1
8868431 Yamazaki et al. Oct 2014 B2
8868469 Xu et al. Oct 2014 B2
8868529 Lerenc Oct 2014 B2
8880405 Cerra et al. Nov 2014 B2
8886534 Nakano et al. Nov 2014 B2
8886540 Cerra et al. Nov 2014 B2
8886541 Friedlander Nov 2014 B2
8892446 Cheyer et al. Nov 2014 B2
8893023 Perry et al. Nov 2014 B2
8897822 Martin Nov 2014 B2
8898064 Thomas et al. Nov 2014 B1
8898568 Bull et al. Nov 2014 B2
8903716 Chen et al. Dec 2014 B2
8909693 Frissora et al. Dec 2014 B2
8918321 Czahor Dec 2014 B2
8922485 Lloyd Dec 2014 B1
8930176 Li et al. Jan 2015 B2
8930191 Gruber et al. Jan 2015 B2
8938394 Faaborg et al. Jan 2015 B1
8938450 Spivack et al. Jan 2015 B2
8938688 Bradford et al. Jan 2015 B2
8942986 Cheyer et al. Jan 2015 B2
8943423 Merrill et al. Jan 2015 B2
8964947 Noolu et al. Feb 2015 B1
8965770 Petrushin Feb 2015 B2
8972240 Brockett et al. Mar 2015 B2
8972432 Shaw et al. Mar 2015 B2
8972878 Mohler et al. Mar 2015 B2
8976063 Hawkins et al. Mar 2015 B1
8976108 Hawkins et al. Mar 2015 B2
8977255 Freeman et al. Mar 2015 B2
8983383 Haskin Mar 2015 B1
8984098 Tomkins et al. Mar 2015 B1
8989713 Doulton Mar 2015 B2
8990235 King et al. Mar 2015 B2
8994660 Neels et al. Mar 2015 B2
8995972 Cronin Mar 2015 B1
8996350 Dub et al. Mar 2015 B1
8996376 Fleizach et al. Mar 2015 B2
8996381 Mozer et al. Mar 2015 B2
8996639 Faaborg et al. Mar 2015 B1
9002714 Kim et al. Apr 2015 B2
9009046 Stewart Apr 2015 B1
9015036 Karov Zangvil et al. Apr 2015 B2
9020804 Barbaiani et al. Apr 2015 B2
9026425 Nikoulina et al. May 2015 B2
9026426 Wu et al. May 2015 B2
9031834 Coorman et al. May 2015 B2
9031970 Das et al. May 2015 B1
9037967 Al-jefri et al. May 2015 B1
9043208 Koch et al. May 2015 B2
9043211 Haiut et al. May 2015 B2
9046932 Medlock et al. Jun 2015 B2
9049255 Macfarlane et al. Jun 2015 B2
9049295 Cooper et al. Jun 2015 B1
9053706 Jitkoff et al. Jun 2015 B2
9058105 Drory et al. Jun 2015 B2
9058332 Darby et al. Jun 2015 B1
9058811 Wang et al. Jun 2015 B2
9063979 Chiu et al. Jun 2015 B2
9064495 Torok et al. Jun 2015 B1
9065660 Ellis et al. Jun 2015 B2
9070247 Kuhn et al. Jun 2015 B2
9070366 Mathias et al. Jun 2015 B1
9071701 Donaldson et al. Jun 2015 B2
9075435 Noble et al. Jul 2015 B1
9075824 Gordo et al. Jul 2015 B2
9076448 Bennett et al. Jul 2015 B2
9076450 Sadek et al. Jul 2015 B1
9081411 Kalns et al. Jul 2015 B2
9081482 Zhai et al. Jul 2015 B1
9082402 Yadgar et al. Jul 2015 B2
9083581 Addepalli et al. Jul 2015 B1
9094636 Sanders et al. Jul 2015 B1
9098467 Blanksteen et al. Aug 2015 B1
9101279 Ritchey et al. Aug 2015 B2
9112984 Sejnoha et al. Aug 2015 B2
9117212 Sheets et al. Aug 2015 B2
9117447 Gruber et al. Aug 2015 B2
9123338 Sanders et al. Sep 2015 B1
9143907 Caldwell et al. Sep 2015 B1
9159319 Hoffmeister Oct 2015 B1
9164983 Liu et al. Oct 2015 B2
9171541 Kennewick et al. Oct 2015 B2
9171546 Pike Oct 2015 B1
9172747 Walters et al. Oct 2015 B2
9183845 Gopalakrishnan et al. Nov 2015 B1
9190062 Haughay Nov 2015 B2
9202520 Tang Dec 2015 B1
9208153 Zaveri et al. Dec 2015 B1
9213754 Zhan et al. Dec 2015 B1
9218122 Thoma et al. Dec 2015 B2
9218809 Bellegard et al. Dec 2015 B2
9218819 Stekkelpa et al. Dec 2015 B1
9223537 Brown et al. Dec 2015 B2
9230561 Ostermann et al. Jan 2016 B2
9232293 Hanson Jan 2016 B1
9236047 Rasmussen Jan 2016 B2
9241073 Rensburg et al. Jan 2016 B1
9245151 LeBeau et al. Jan 2016 B2
9250703 Hernandez-Abrego et al. Feb 2016 B2
9251713 Giovanniello et al. Feb 2016 B1
9251787 Hart et al. Feb 2016 B1
9255812 Maeoka et al. Feb 2016 B2
9257120 Alvarez Guevara et al. Feb 2016 B1
9258604 Bilobrov et al. Feb 2016 B1
9262412 Yang et al. Feb 2016 B2
9262612 Cheyer Feb 2016 B2
9263058 Huang et al. Feb 2016 B2
9274598 Beymer et al. Mar 2016 B2
9280535 Varma et al. Mar 2016 B2
9282211 Osawa Mar 2016 B2
9286727 Kim et al. Mar 2016 B2
9286910 Li et al. Mar 2016 B1
9292487 Weber Mar 2016 B1
9292489 Sak et al. Mar 2016 B1
9292492 Sarikaya et al. Mar 2016 B2
9299344 Braho et al. Mar 2016 B2
9300718 Khanna Mar 2016 B2
9301256 Mohan et al. Mar 2016 B2
9305543 Fleizach et al. Apr 2016 B2
9305548 Kennewick et al. Apr 2016 B2
9311308 Sankarasubramaniam et al. Apr 2016 B2
9311912 Swietlinski et al. Apr 2016 B1
9313317 LeBeau et al. Apr 2016 B1
9318108 Gruber Apr 2016 B2
9325809 Barros et al. Apr 2016 B1
9325842 Siddiqi et al. Apr 2016 B1
9330659 Ju et al. May 2016 B2
9330668 Nanavati et al. May 2016 B2
9330720 Lee May 2016 B2
9335983 Breiner et al. May 2016 B2
9338493 Van Os et al. May 2016 B2
9342829 Zhou et al. May 2016 B2
9342930 Kraft et al. May 2016 B1
9349368 Lebeau et al. May 2016 B1
9355472 Kocienda et al. May 2016 B2
9361084 Costa Jun 2016 B1
9367541 Servan et al. Jun 2016 B1
9368114 Larson et al. Jun 2016 B2
9377871 Waddell et al. Jun 2016 B2
9378456 White et al. Jun 2016 B2
9378740 Rosen et al. Jun 2016 B1
9380155 Reding et al. Jun 2016 B1
9383827 Faaborg et al. Jul 2016 B1
9384185 Medlock et al. Jul 2016 B2
9390726 Smus et al. Jul 2016 B1
9396722 Chung et al. Jul 2016 B2
9401140 Weber et al. Jul 2016 B1
9401147 Jitkoff et al. Jul 2016 B2
9405741 Schaaf et al. Aug 2016 B1
9406224 Sanders et al. Aug 2016 B1
9406299 Gollan et al. Aug 2016 B2
9408182 Hurley et al. Aug 2016 B1
9412392 Lindahl Aug 2016 B2
9418650 Bharadwaj et al. Aug 2016 B2
9423266 Clark et al. Aug 2016 B2
9424246 Spencer et al. Aug 2016 B2
9424840 Hart et al. Aug 2016 B1
9431021 Scalise et al. Aug 2016 B1
9432499 Hajdu et al. Aug 2016 B2
9436918 Pantel et al. Sep 2016 B2
9437186 Liu et al. Sep 2016 B1
9437189 Epstein et al. Sep 2016 B2
9442687 Park et al. Sep 2016 B2
9443527 Watanabe et al. Sep 2016 B1
9454599 Golden et al. Sep 2016 B2
9454957 Mathias et al. Sep 2016 B1
9465798 Lin Oct 2016 B2
9465833 Aravamudan et al. Oct 2016 B2
9465864 Hu et al. Oct 2016 B2
9466027 Byrne et al. Oct 2016 B2
9466294 Tunstall-pedoe et al. Oct 2016 B1
9471566 Zhang et al. Oct 2016 B1
9472196 Wang et al. Oct 2016 B1
9483388 Sankaranarasimhan et al. Nov 2016 B2
9483461 Fleizach et al. Nov 2016 B2
9483529 Pasoi et al. Nov 2016 B1
9484021 Mairesse et al. Nov 2016 B1
9485286 Sellier et al. Nov 2016 B1
9495129 Fleizach et al. Nov 2016 B2
9501741 Cheyer et al. Nov 2016 B2
9502025 Kennewick et al. Nov 2016 B2
9508028 Bannister et al. Nov 2016 B2
9510044 Pereira et al. Nov 2016 B1
9514470 Topatan et al. Dec 2016 B2
9516014 Zafiroglu et al. Dec 2016 B2
9519453 Perkuhn et al. Dec 2016 B2
9524355 Forbes et al. Dec 2016 B2
9529500 Gauci et al. Dec 2016 B1
9531862 Vadodaria Dec 2016 B1
9535906 Lee et al. Jan 2017 B2
9536527 Carlson Jan 2017 B1
9536544 Osterman et al. Jan 2017 B2
9547647 Badaskar Jan 2017 B2
9548050 Gruber Jan 2017 B2
9548979 Johnson et al. Jan 2017 B1
9569549 Jenkins et al. Feb 2017 B1
9575964 Yadgar et al. Feb 2017 B2
9576575 Heide Feb 2017 B2
9578173 Sanghavi et al. Feb 2017 B2
9602946 Karkkainen et al. Mar 2017 B2
9607612 Deleeuw Mar 2017 B2
9612999 Prakah-asante et al. Apr 2017 B2
9619200 Chakladar et al. Apr 2017 B2
9620113 Kennewick et al. Apr 2017 B2
9620126 Chiba Apr 2017 B2
9626695 Balasubramanian et al. Apr 2017 B2
9626955 Fleizach et al. Apr 2017 B2
9633004 Giuli et al. Apr 2017 B2
9633191 Fleizach et al. Apr 2017 B2
9633660 Haughay Apr 2017 B2
9633674 Sinha Apr 2017 B2
9646313 Kim et al. May 2017 B2
9648107 Penilla et al. May 2017 B1
9652453 Mathur et al. May 2017 B2
9658746 Cohn et al. May 2017 B2
9659002 Medlock et al. May 2017 B2
9659298 Lynch et al. May 2017 B2
9665567 Li et al. May 2017 B2
9665662 Gautam et al. May 2017 B1
9668121 Naik et al. May 2017 B2
9672725 Dotan-Cohen et al. Jun 2017 B2
9672822 Brown et al. Jun 2017 B2
9690542 Reddy et al. Jun 2017 B2
9691161 Yalniz et al. Jun 2017 B1
9691378 Meyers et al. Jun 2017 B1
9696963 Son et al. Jul 2017 B2
9697016 Jacob Jul 2017 B2
9697822 Naik et al. Jul 2017 B1
9697827 Lilly et al. Jul 2017 B1
9697828 Prasad et al. Jul 2017 B1
9698999 Mutagi Jul 2017 B2
9720907 Bangalore et al. Aug 2017 B2
9721566 Newendorp et al. Aug 2017 B2
9721570 Beal et al. Aug 2017 B1
9723130 Rand Aug 2017 B2
9734817 Putrycz Aug 2017 B1
9734839 Adams Aug 2017 B1
9741343 Miles et al. Aug 2017 B1
9747083 Roman et al. Aug 2017 B1
9747093 Latino et al. Aug 2017 B2
9755605 Li et al. Sep 2017 B1
9760566 Heck et al. Sep 2017 B2
9767710 Lee et al. Sep 2017 B2
9772994 Karov et al. Sep 2017 B2
9786271 Combs et al. Oct 2017 B1
9792907 Bocklet et al. Oct 2017 B2
9798719 Karov et al. Oct 2017 B2
9812128 Mixter et al. Nov 2017 B2
9813882 Masterman Nov 2017 B1
9818400 Paulik et al. Nov 2017 B2
9823811 Brown et al. Nov 2017 B2
9823828 Zambetti et al. Nov 2017 B2
9824379 Khandelwal et al. Nov 2017 B2
9824691 Montero et al. Nov 2017 B1
9824692 Khoury et al. Nov 2017 B1
9830044 Brown et al. Nov 2017 B2
9830449 Wagner Nov 2017 B1
9842168 Heck et al. Dec 2017 B2
9842584 Hart et al. Dec 2017 B1
9846685 Li Dec 2017 B2
9846836 Gao et al. Dec 2017 B2
9858925 Gruber et al. Jan 2018 B2
9858927 Williams et al. Jan 2018 B2
9886953 Lemay et al. Feb 2018 B2
9887949 Shepherd et al. Feb 2018 B2
9911415 Vanblon et al. Mar 2018 B2
9916839 Scalise et al. Mar 2018 B1
9922642 Pitschel et al. Mar 2018 B2
9928835 Tang Mar 2018 B1
9934777 Joseph et al. Apr 2018 B1
9934785 Hulaud Apr 2018 B1
9946862 Yun et al. Apr 2018 B2
9948728 Linn et al. Apr 2018 B2
9959129 Kannan et al. May 2018 B2
9959506 Karppanen May 2018 B1
9966065 Gruber et al. May 2018 B2
9966068 Cash et al. May 2018 B2
9967381 Kashimba et al. May 2018 B1
9971495 Shetty et al. May 2018 B2
9984686 Mutagi et al. May 2018 B1
9986419 Naik et al. May 2018 B2
9990129 Yang et al. Jun 2018 B2
9990176 Gray Jun 2018 B1
9990921 Vanblon et al. Jun 2018 B2
9996626 Bailey et al. Jun 2018 B1
9998552 Ledet Jun 2018 B1
10001817 Zambetti et al. Jun 2018 B2
10013416 Bhardwaj et al. Jul 2018 B1
10013654 Levy et al. Jul 2018 B1
10013979 Roma et al. Jul 2018 B1
10019436 Huang Jul 2018 B2
10025378 Venable et al. Jul 2018 B2
10026209 Dagley et al. Jul 2018 B1
10027662 Mutagi et al. Jul 2018 B1
10032451 Mamkina et al. Jul 2018 B1
10032455 Newman et al. Jul 2018 B2
10037758 Jing et al. Jul 2018 B2
10043516 Saddler et al. Aug 2018 B2
10049161 Kaneko Aug 2018 B2
10049663 Orr et al. Aug 2018 B2
10049668 Huang et al. Aug 2018 B2
10055390 Sharifi et al. Aug 2018 B2
10055681 Brown et al. Aug 2018 B2
10074360 Kim Sep 2018 B2
10074371 Wang et al. Sep 2018 B1
10078487 Gruber et al. Sep 2018 B2
10083213 Podgorny et al. Sep 2018 B1
10083690 Giuli et al. Sep 2018 B2
10088972 Brown et al. Oct 2018 B2
10089072 Piersol et al. Oct 2018 B2
10096319 Jin et al. Oct 2018 B1
10101887 Bernstein et al. Oct 2018 B2
10102359 Cheyer Oct 2018 B2
10115055 Weiss et al. Oct 2018 B2
10127901 Zhao et al. Nov 2018 B2
10127908 Deller et al. Nov 2018 B1
10134425 Johnson, Jr. Nov 2018 B1
10135965 Woolsey et al. Nov 2018 B2
10146923 Pitkänen et al. Dec 2018 B2
10147421 Liddell et al. Dec 2018 B2
10147441 Pogue et al. Dec 2018 B1
10169329 Futrell et al. Jan 2019 B2
10170123 Orr et al. Jan 2019 B2
10170135 Pearce et al. Jan 2019 B1
10175879 Missig et al. Jan 2019 B2
10176167 Evermann Jan 2019 B2
10176802 Ladhak et al. Jan 2019 B1
10176808 Lovitt et al. Jan 2019 B1
10178301 Welbourne et al. Jan 2019 B1
10185542 Carson et al. Jan 2019 B2
10186254 Williams et al. Jan 2019 B2
10186266 Devaraj et al. Jan 2019 B1
10191627 Cieplinski et al. Jan 2019 B2
10191646 Zambetti et al. Jan 2019 B2
10191718 Rhee et al. Jan 2019 B2
10192546 Piersol et al. Jan 2019 B1
10192552 Raitio et al. Jan 2019 B2
10192557 Lee et al. Jan 2019 B2
10198877 Maltsev et al. Feb 2019 B1
10199051 Binder et al. Feb 2019 B2
10200824 Gross et al. Feb 2019 B2
10204627 Nitz et al. Feb 2019 B2
10210860 Ward et al. Feb 2019 B1
10216351 Yang Feb 2019 B2
10216832 Bangalore et al. Feb 2019 B2
10223066 Martel et al. Mar 2019 B2
10225711 Parks et al. Mar 2019 B2
10228904 Raux Mar 2019 B2
10229109 Cherepanov et al. Mar 2019 B1
10229356 Liu et al. Mar 2019 B1
10237711 Linn et al. Mar 2019 B2
10242501 Pusch et al. Mar 2019 B1
10248308 Karunamuni et al. Apr 2019 B2
10249300 Booker et al. Apr 2019 B2
10249305 Yu Apr 2019 B2
10255922 Sharifi et al. Apr 2019 B1
10261672 Dolbakian et al. Apr 2019 B1
10261830 Gupta et al. Apr 2019 B2
10269345 Castillo Sanchez et al. Apr 2019 B2
10275513 Cowan et al. Apr 2019 B1
10289205 Sumter et al. May 2019 B1
10296160 Shah et al. May 2019 B2
10297253 Walker, II et al. May 2019 B2
10303772 Hosn et al. May 2019 B2
10304463 Mixter et al. May 2019 B2
10311482 Baldwin Jun 2019 B2
10311871 Newendorp et al. Jun 2019 B2
10325598 Basye et al. Jun 2019 B2
10332509 Catanzaro et al. Jun 2019 B2
10332513 D'souza et al. Jun 2019 B1
10332518 Garg et al. Jun 2019 B2
10339224 Fukuoka Jul 2019 B2
10339714 Corso et al. Jul 2019 B2
10346540 Karov et al. Jul 2019 B2
10346753 Soon-Shiong et al. Jul 2019 B2
10346878 Ostermann et al. Jul 2019 B1
10353975 Oh et al. Jul 2019 B2
10354168 Bluche Jul 2019 B2
10354677 Mohamed et al. Jul 2019 B2
10356243 Sanghavi et al. Jul 2019 B2
10360716 Van Der Meulen et al. Jul 2019 B1
10365887 Mulherkar Jul 2019 B1
10366160 Castelli et al. Jul 2019 B2
10366692 Adams et al. Jul 2019 B1
10372814 Gliozzo et al. Aug 2019 B2
10372881 Ingrassia, Jr. et al. Aug 2019 B2
10389876 Engelke et al. Aug 2019 B2
10402066 Kawana Sep 2019 B2
10403283 Schramm et al. Sep 2019 B1
10409454 Kagan et al. Sep 2019 B2
10410637 Paulik et al. Sep 2019 B2
10417037 Gruber et al. Sep 2019 B2
10417344 Futrell et al. Sep 2019 B2
10417554 Scheffler Sep 2019 B2
10437928 Bhaya et al. Oct 2019 B2
10446142 Lim et al. Oct 2019 B2
10453117 Reavely et al. Oct 2019 B1
10469665 Bell et al. Nov 2019 B1
10474961 Brigham et al. Nov 2019 B2
10475446 Gruber et al. Nov 2019 B2
10482875 Henry Nov 2019 B2
10490195 Krishnamoorthy et al. Nov 2019 B1
10496364 Yao Dec 2019 B2
10496705 Irani et al. Dec 2019 B1
10497365 Gruber et al. Dec 2019 B2
10504518 Irani et al. Dec 2019 B1
10512750 Lewin et al. Dec 2019 B1
10515133 Sharifi Dec 2019 B1
10521946 Roche et al. Dec 2019 B1
10528386 Yu Jan 2020 B2
10540976 Van Os et al. Jan 2020 B2
10558893 Bluche Feb 2020 B2
10566007 Fawaz et al. Feb 2020 B2
10568032 Freeman et al. Feb 2020 B2
10579401 Dawes Mar 2020 B2
10580409 Walker, II et al. Mar 2020 B2
10582355 Lebeau et al. Mar 2020 B1
10585957 Heck et al. Mar 2020 B2
10586369 Roche et al. Mar 2020 B1
10599449 Chatzipanagiotis et al. Mar 2020 B1
10629186 Slifka Apr 2020 B1
10630795 Aoki et al. Apr 2020 B2
10642934 Heck et al. May 2020 B2
10659851 Lister et al. May 2020 B2
10671428 Zeitlin Jun 2020 B2
10684099 Zaetterqvist Jun 2020 B2
10684703 Hindi et al. Jun 2020 B2
10699697 Qian et al. Jun 2020 B2
10706841 Gruber Jul 2020 B2
10721190 Zhao et al. Jul 2020 B2
10732708 Roche et al. Aug 2020 B1
10743107 Yoshioka et al. Aug 2020 B1
10748529 Milden Aug 2020 B1
10748546 Kim et al. Aug 2020 B2
10754658 Tamiya Aug 2020 B2
10755032 Douglas et al. Aug 2020 B2
10757499 Vautrin et al. Aug 2020 B1
10769385 Evermann Sep 2020 B2
10783151 Bushkin et al. Sep 2020 B1
10783883 Mixter et al. Sep 2020 B2
10789945 Acero et al. Sep 2020 B2
10791176 Phipps et al. Sep 2020 B2
10795944 Brown et al. Oct 2020 B2
10796100 Bangalore et al. Oct 2020 B2
10803255 Dubyak et al. Oct 2020 B2
10811013 Secker-Walker et al. Oct 2020 B1
10818288 Garcia et al. Oct 2020 B2
10842968 Kahn et al. Nov 2020 B1
10846618 Ravi et al. Nov 2020 B2
10860629 Gangadharaiah et al. Dec 2020 B1
10861483 Feinauer et al. Dec 2020 B2
10880668 Robinson et al. Dec 2020 B1
10885277 Ravi et al. Jan 2021 B2
10892996 Piersol Jan 2021 B2
10909459 Tsatsin et al. Feb 2021 B2
10944859 Weinstein et al. Mar 2021 B2
10957311 Solomon et al. Mar 2021 B2
10957337 Chen et al. Mar 2021 B2
10970660 Harris et al. Apr 2021 B1
10974139 Feder et al. Apr 2021 B2
10978056 Challa et al. Apr 2021 B1
10978090 Binder et al. Apr 2021 B2
10983971 Carvalho et al. Apr 2021 B2
11009970 Hindi et al. May 2021 B2
11037565 Kudurshian et al. Jun 2021 B2
11061543 Blatz et al. Jul 2021 B1
11076039 Weinstein et al. Jul 2021 B2
11094311 Candelore et al. Aug 2021 B2
11132172 Naik et al. Sep 2021 B1
11169660 Gupta et al. Nov 2021 B2
11183205 Ebenezer et al. Nov 2021 B1
11200027 Aggarwal et al. Dec 2021 B2
11204787 Radebaugh et al. Dec 2021 B2
11269426 Jorasch et al. Mar 2022 B2
11423866 Park Aug 2022 B2
20010047264 Roundtree Nov 2001 A1
20010049275 Pierry et al. Dec 2001 A1
20010049277 Meyer et al. Dec 2001 A1
20020002548 Roundtree Jan 2002 A1
20020002575 Eisler et al. Jan 2002 A1
20020002594 Roundtree et al. Jan 2002 A1
20020004736 Roundtree et al. Jan 2002 A1
20020032591 Mahaffy Mar 2002 A1
20020040297 Tsiao et al. Apr 2002 A1
20020042707 Zhao et al. Apr 2002 A1
20020052913 Yamada et al. May 2002 A1
20020103644 Brocious et al. Aug 2002 A1
20020116171 Russell Aug 2002 A1
20020123891 Epstein et al. Sep 2002 A1
20020133347 Schoneburg et al. Sep 2002 A1
20020133355 Ross et al. Sep 2002 A1
20020164000 Cohen et al. Nov 2002 A1
20020198714 Zhou Dec 2002 A1
20030005174 Coffman et al. Jan 2003 A1
20030078779 Desai et al. Apr 2003 A1
20030101054 Davis et al. May 2003 A1
20030125955 Arnold et al. Jul 2003 A1
20030154116 Lofton Aug 2003 A1
20030182131 Arnold et al. Sep 2003 A1
20030233230 Ammicht et al. Dec 2003 A1
20040010484 Foulger et al. Jan 2004 A1
20040022369 Vitikainen et al. Feb 2004 A1
20040044516 Kennewick et al. Mar 2004 A1
20040085162 Agarwal et al. May 2004 A1
20040138890 Ferrans et al. Jul 2004 A1
20040230637 Lecoueche et al. Nov 2004 A1
20040236778 Junqua et al. Nov 2004 A1
20040243419 Wang Dec 2004 A1
20050021424 Lewis Jan 2005 A1
20050033582 Gadd Feb 2005 A1
20050043974 Vassilev et al. Feb 2005 A1
20050055403 Brittan Mar 2005 A1
20050074113 Mathew et al. Apr 2005 A1
20050075875 Shozakai et al. Apr 2005 A1
20050080780 Colledge et al. Apr 2005 A1
20050114306 Shu et al. May 2005 A1
20050154591 Lecoeuche Jul 2005 A1
20050165607 Di Fabbrizio et al. Jul 2005 A1
20050171779 Joublin Aug 2005 A1
20050182628 Choi Aug 2005 A1
20050203747 Lecoeuche Sep 2005 A1
20050203782 Smith Sep 2005 A1
20050234872 Torge et al. Oct 2005 A1
20050288936 Busayapongchai et al. Dec 2005 A1
20060009973 Nguyen et al. Jan 2006 A1
20060069664 Ling et al. Mar 2006 A1
20060100876 Nishizaki et al. May 2006 A1
20060106595 Brockett et al. May 2006 A1
20060235690 Tomasic et al. Oct 2006 A1
20060293876 Kamatani et al. Dec 2006 A1
20070027845 Dettinger et al. Feb 2007 A1
20070033261 Wagner et al. Feb 2007 A1
20070038609 Wu Feb 2007 A1
20070050191 Weider et al. Mar 2007 A1
20070055525 Kennewick et al. Mar 2007 A1
20070060114 Ramer Mar 2007 A1
20070094026 Ativanichayaphong et al. Apr 2007 A1
20070100709 Lee et al. May 2007 A1
20070100790 Cheyer et al. May 2007 A1
20070106674 Agrawal et al. May 2007 A1
20070124289 Imielinski May 2007 A1
20070135949 Snover et al. Jun 2007 A1
20070143376 McIntosh Jun 2007 A1
20070208555 Blass et al. Sep 2007 A1
20070213984 Ativanichayaphong et al. Sep 2007 A1
20070214122 Bala Sep 2007 A1
20070265847 Ross et al. Nov 2007 A1
20080015864 Ross et al. Jan 2008 A1
20080040339 Zhou et al. Feb 2008 A1
20080048908 Sato Feb 2008 A1
20080065387 Cross, Jr. et al. Mar 2008 A1
20080091406 Baldwin et al. Apr 2008 A1
20080167876 Bakis et al. Jul 2008 A1
20080189110 Freeman et al. Aug 2008 A1
20080195630 Exartier et al. Aug 2008 A1
20080221879 Cerra et al. Sep 2008 A1
20080228495 Cross, Jr. et al. Sep 2008 A1
20080235017 Satomura Sep 2008 A1
20080247519 Abella et al. Oct 2008 A1
20080255972 Ulrich et al. Oct 2008 A1
20080294517 Hill Nov 2008 A1
20080319763 Di Fabbrizio et al. Dec 2008 A1
20090055179 Cho et al. Feb 2009 A1
20090076821 Brenner et al. Mar 2009 A1
20090077165 Rhodes et al. Mar 2009 A1
20090119588 Moore May 2009 A1
20090144428 Bowater et al. Jun 2009 A1
20090150156 Kennewick et al. Jun 2009 A1
20090167553 Hong Jul 2009 A1
20090183070 Robbins Jul 2009 A1
20090215503 Zhang et al. Aug 2009 A1
20090216396 Yamagata Aug 2009 A1
20090222488 Boerries et al. Sep 2009 A1
20090248456 Fahmy et al. Oct 2009 A1
20090265368 Crider et al. Oct 2009 A1
20090307162 Bui et al. Dec 2009 A1
20090327263 Maghoul Dec 2009 A1
20100030578 Siddique Feb 2010 A1
20100049514 Kennewick et al. Feb 2010 A1
20100070899 Hunt et al. Mar 2010 A1
20100076843 Ashton Mar 2010 A1
20100082376 Levitt Apr 2010 A1
20100138215 Williams Jun 2010 A1
20100138759 Roy Jun 2010 A1
20100145694 Ju et al. Jun 2010 A1
20100185643 Rao et al. Jul 2010 A1
20100250599 Schmidt et al. Sep 2010 A1
20100262599 Nitz Oct 2010 A1
20100312547 Van Os et al. Dec 2010 A1
20100332236 Tan Dec 2010 A1
20110010644 Merrill et al. Jan 2011 A1
20110047072 Ciurea Feb 2011 A1
20110106736 Aharonson et al. May 2011 A1
20110137664 Kho et al. Jun 2011 A1
20110143811 Rodriguez Jun 2011 A1
20110153373 Dantzig et al. Jun 2011 A1
20110195758 Damale et al. Aug 2011 A1
20110295590 Lloyd et al. Dec 2011 A1
20110314404 Kotler et al. Dec 2011 A1
20120002820 Leichter Jan 2012 A1
20120005224 Ahrens et al. Jan 2012 A1
20120005602 Anttila et al. Jan 2012 A1
20120008754 Mukherjee et al. Jan 2012 A1
20120010886 Razavilar Jan 2012 A1
20120011138 Dunning et al. Jan 2012 A1
20120013609 Reponen et al. Jan 2012 A1
20120015629 Olsen et al. Jan 2012 A1
20120016658 Wu et al. Jan 2012 A1
20120016678 Gruber et al. Jan 2012 A1
20120019400 Patel et al. Jan 2012 A1
20120020490 Leichter Jan 2012 A1
20120020503 Endo et al. Jan 2012 A1
20120022787 LeBeau et al. Jan 2012 A1
20120022857 Baldwin et al. Jan 2012 A1
20120022860 Lloyd et al. Jan 2012 A1
20120022868 LeBeau et al. Jan 2012 A1
20120022869 Lloyd et al. Jan 2012 A1
20120022870 Kristjansson et al. Jan 2012 A1
20120022872 Gruber et al. Jan 2012 A1
20120022874 Lloyd et al. Jan 2012 A1
20120022876 LeBeau et al. Jan 2012 A1
20120022967 Bachman et al. Jan 2012 A1
20120023088 Cheng et al. Jan 2012 A1
20120023095 Wadycki et al. Jan 2012 A1
20120023462 Rosing et al. Jan 2012 A1
20120026395 Jin et al. Feb 2012 A1
20120029661 Jones et al. Feb 2012 A1
20120029910 Medlock et al. Feb 2012 A1
20120034904 LeBeau et al. Feb 2012 A1
20120035907 Lebeau et al. Feb 2012 A1
20120035908 Lebeau et al. Feb 2012 A1
20120035924 Jitkoff et al. Feb 2012 A1
20120035925 Friend et al. Feb 2012 A1
20120035926 Ambler Feb 2012 A1
20120035931 LeBeau et al. Feb 2012 A1
20120035932 Jitkoff et al. Feb 2012 A1
20120035935 Park et al. Feb 2012 A1
20120036556 LeBeau et al. Feb 2012 A1
20120039539 Boiman et al. Feb 2012 A1
20120039578 Issa et al. Feb 2012 A1
20120041752 Wang et al. Feb 2012 A1
20120041756 Hanazawa et al. Feb 2012 A1
20120041759 Barker et al. Feb 2012 A1
20120042014 Desai et al. Feb 2012 A1
20120042343 Laligand et al. Feb 2012 A1
20120052945 Miyamoto et al. Mar 2012 A1
20120053815 Montanari et al. Mar 2012 A1
20120053829 Agarwal et al. Mar 2012 A1
20120053945 Gupta et al. Mar 2012 A1
20120055253 Sinha Mar 2012 A1
20120056815 Mehra Mar 2012 A1
20120058783 Kim et al. Mar 2012 A1
20120059655 Cartales Mar 2012 A1
20120059813 Sejnoha et al. Mar 2012 A1
20120060052 White et al. Mar 2012 A1
20120062473 Xiao et al. Mar 2012 A1
20120064975 Gault et al. Mar 2012 A1
20120065972 Strifler et al. Mar 2012 A1
20120066212 Jennings Mar 2012 A1
20120066581 Spalink Mar 2012 A1
20120075054 Ge et al. Mar 2012 A1
20120075184 Madhvanath Mar 2012 A1
20120077479 Sabotta et al. Mar 2012 A1
20120078611 Soltani et al. Mar 2012 A1
20120078624 Yook et al. Mar 2012 A1
20120078627 Wagner Mar 2012 A1
20120078635 Rothkopf et al. Mar 2012 A1
20120078747 Chakrabarti et al. Mar 2012 A1
20120082317 Pance et al. Apr 2012 A1
20120083286 Kim et al. Apr 2012 A1
20120084086 Gilbert et al. Apr 2012 A1
20120084087 Yang et al. Apr 2012 A1
20120084089 Lloyd et al. Apr 2012 A1
20120084251 Lingenfelder et al. Apr 2012 A1
20120084634 Wong et al. Apr 2012 A1
20120088219 Briscoe et al. Apr 2012 A1
20120089331 Schmidt et al. Apr 2012 A1
20120089659 Halevi et al. Apr 2012 A1
20120094645 Jeffrey Apr 2012 A1
20120101823 Weng et al. Apr 2012 A1
20120105257 Murillo et al. May 2012 A1
20120108166 Hymel May 2012 A1
20120108221 Thomas et al. May 2012 A1
20120109632 Sugiura et al. May 2012 A1
20120109753 Kennewick et al. May 2012 A1
20120109997 Sparks et al. May 2012 A1
20120110456 Larco et al. May 2012 A1
20120114108 Katis et al. May 2012 A1
20120116770 Chen et al. May 2012 A1
20120117499 Mori et al. May 2012 A1
20120117590 Agnihotri et al. May 2012 A1
20120124126 Alcazar et al. May 2012 A1
20120124177 Sparks May 2012 A1
20120124178 Sparks May 2012 A1
20120128322 Shaffer et al. May 2012 A1
20120130709 Bocchieri et al. May 2012 A1
20120130978 Li et al. May 2012 A1
20120130995 Risvik et al. May 2012 A1
20120135714 King, II May 2012 A1
20120136529 Curtis et al. May 2012 A1
20120136572 Norton May 2012 A1
20120136649 Freising et al. May 2012 A1
20120136658 Shrum, Jr. et al. May 2012 A1
20120136855 Ni et al. May 2012 A1
20120136985 Popescu et al. May 2012 A1
20120137367 Dupont et al. May 2012 A1
20120287067 Ikegami May 2012 A1
20120148077 Aldaz et al. Jun 2012 A1
20120149342 Cohen et al. Jun 2012 A1
20120149394 Singh et al. Jun 2012 A1
20120150532 Mirowski et al. Jun 2012 A1
20120150544 McLoughlin et al. Jun 2012 A1
20120150580 Norton Jun 2012 A1
20120158293 Burnham Jun 2012 A1
20120158399 Tremblay et al. Jun 2012 A1
20120158422 Burnham et al. Jun 2012 A1
20120159380 Kocienda et al. Jun 2012 A1
20120162540 Ouchi et al. Jun 2012 A1
20120163710 Skaff et al. Jun 2012 A1
20120166177 Beld et al. Jun 2012 A1
20120166196 Ju et al. Jun 2012 A1
20120166429 Moore et al. Jun 2012 A1
20120166942 Ramerth et al. Jun 2012 A1
20120166959 Hilerio et al. Jun 2012 A1
20120166998 Cotterill et al. Jun 2012 A1
20120173222 Wang et al. Jul 2012 A1
20120173244 Kwak et al. Jul 2012 A1
20120173464 Tur et al. Jul 2012 A1
20120174121 Treat et al. Jul 2012 A1
20120176255 Choi et al. Jul 2012 A1
20120179457 Newman et al. Jul 2012 A1
20120179467 Williams et al. Jul 2012 A1
20120179471 Newman et al. Jul 2012 A1
20120185237 Gajic et al. Jul 2012 A1
20120185480 Ni et al. Jul 2012 A1
20120185781 Guzman et al. Jul 2012 A1
20120185803 Wang et al. Jul 2012 A1
20120185821 Yaseen et al. Jul 2012 A1
20120191461 Lin et al. Jul 2012 A1
20120192096 Bowman et al. Jul 2012 A1
20120197743 Grigg et al. Aug 2012 A1
20120197967 Sivavakeesar Aug 2012 A1
20120197995 Caruso Aug 2012 A1
20120197998 Kessel et al. Aug 2012 A1
20120200489 Miyashita et al. Aug 2012 A1
20120201362 Crossan et al. Aug 2012 A1
20120203767 Williams et al. Aug 2012 A1
20120209454 Miller et al. Aug 2012 A1
20120209654 Romagnino et al. Aug 2012 A1
20120209853 Desai et al. Aug 2012 A1
20120209874 Wong et al. Aug 2012 A1
20120210266 Jiang et al. Aug 2012 A1
20120210378 Mccoy et al. Aug 2012 A1
20120214141 Raya et al. Aug 2012 A1
20120214517 Singh et al. Aug 2012 A1
20120215640 Ramer et al. Aug 2012 A1
20120215762 Hall et al. Aug 2012 A1
20120221339 Wang et al. Aug 2012 A1
20120221552 Reponen et al. Aug 2012 A1
20120222132 Burger et al. Aug 2012 A1
20120223889 Medlock et al. Sep 2012 A1
20120223936 Aughey et al. Sep 2012 A1
20120232885 Barbosa et al. Sep 2012 A1
20120232886 Capuozzo et al. Sep 2012 A1
20120232906 Lindahl Sep 2012 A1
20120233207 Mohajer Sep 2012 A1
20120233266 Hassan et al. Sep 2012 A1
20120233280 Ebara Sep 2012 A1
20120239403 Cano et al. Sep 2012 A1
20120239661 Giblin Sep 2012 A1
20120239761 Linner et al. Sep 2012 A1
20120242482 Elumalai et al. Sep 2012 A1
20120245719 Story, Jr. et al. Sep 2012 A1
20120245939 Braho et al. Sep 2012 A1
20120245941 Cheyer Sep 2012 A1
20120245944 Gruber et al. Sep 2012 A1
20120246064 Balkow Sep 2012 A1
20120250858 Iqbal et al. Oct 2012 A1
20120252367 Gaglio et al. Oct 2012 A1
20120252540 Kirigaya Oct 2012 A1
20120253785 Hamid et al. Oct 2012 A1
20120253791 Heck et al. Oct 2012 A1
20120254143 Varma et al. Oct 2012 A1
20120254152 Park et al. Oct 2012 A1
20120254290 Naaman Oct 2012 A1
20120259615 Morin et al. Oct 2012 A1
20120259638 Kalinli Oct 2012 A1
20120262296 Bezar Oct 2012 A1
20120265482 Grokop et al. Oct 2012 A1
20120265528 Gruber et al. Oct 2012 A1
20120265535 Bryant-Rich et al. Oct 2012 A1
20120265787 Hsu et al. Oct 2012 A1
20120265806 Blanchflower et al. Oct 2012 A1
20120271625 Bernard Oct 2012 A1
20120271634 Lenke Oct 2012 A1
20120271635 Ljolje Oct 2012 A1
20120271640 Basir Oct 2012 A1
20120271676 Aravamudan et al. Oct 2012 A1
20120272177 Vaghefinazari et al. Oct 2012 A1
20120275377 Lehane et al. Nov 2012 A1
20120278744 Kozitsyn et al. Nov 2012 A1
20120278812 Wang Nov 2012 A1
20120284015 Drewes Nov 2012 A1
20120284027 Mallett et al. Nov 2012 A1
20120290291 Shelley et al. Nov 2012 A1
20120290300 Lee et al. Nov 2012 A1
20120290657 Parks et al. Nov 2012 A1
20120290680 Hwang Nov 2012 A1
20120295708 Hernandez-Abrego et al. Nov 2012 A1
20120296638 Patwa Nov 2012 A1
20120296649 Bansal et al. Nov 2012 A1
20120296654 Hendrickson et al. Nov 2012 A1
20120296891 Rangan Nov 2012 A1
20120297341 Glazer et al. Nov 2012 A1
20120297348 Santoro Nov 2012 A1
20120303369 Brush et al. Nov 2012 A1
20120303371 Labsky et al. Nov 2012 A1
20120304124 Chen et al. Nov 2012 A1
20120304239 Shahraray et al. Nov 2012 A1
20120309363 Gruber et al. Dec 2012 A1
20120310642 Cao et al. Dec 2012 A1
20120310649 Cannistraro et al. Dec 2012 A1
20120310652 O'Sullivan Dec 2012 A1
20120310922 Johnson et al. Dec 2012 A1
20120311478 Van Os et al. Dec 2012 A1
20120311583 Gruber et al. Dec 2012 A1
20120311584 Gruber et al. Dec 2012 A1
20120311585 Gruber et al. Dec 2012 A1
20120316774 Yariv et al. Dec 2012 A1
20120316862 Sultan et al. Dec 2012 A1
20120316875 Nyquist et al. Dec 2012 A1
20120316878 Singleton et al. Dec 2012 A1
20120316955 Panguluri et al. Dec 2012 A1
20120317194 Tian Dec 2012 A1
20120317498 Logan et al. Dec 2012 A1
20120321112 Schubert et al. Dec 2012 A1
20120323560 Cortes et al. Dec 2012 A1
20120324391 Tocci Dec 2012 A1
20120327009 Fleizach Dec 2012 A1
20120329529 Van Der Raadt Dec 2012 A1
20120330660 Jaiswal Dec 2012 A1
20120330661 Lindahl Dec 2012 A1
20120330990 Chen et al. Dec 2012 A1
20130002716 Walker et al. Jan 2013 A1
20130005405 Prociw Jan 2013 A1
20130006633 Grokop et al. Jan 2013 A1
20130006637 Kanevsky et al. Jan 2013 A1
20130006638 Lindahl Jan 2013 A1
20130007240 Qiu et al. Jan 2013 A1
20130007648 Gamon et al. Jan 2013 A1
20130009858 Lacey Jan 2013 A1
20130010575 He et al. Jan 2013 A1
20130013313 Shechtman et al. Jan 2013 A1
20130013319 Grant et al. Jan 2013 A1
20130014026 Beringer et al. Jan 2013 A1
20130014143 Bhatia et al. Jan 2013 A1
20130018659 Chi Jan 2013 A1
20130018863 Regan et al. Jan 2013 A1
20130022189 Ganong et al. Jan 2013 A1
20130024277 Tuchman et al. Jan 2013 A1
20130024576 Dishneau et al. Jan 2013 A1
20130027875 Zhu et al. Jan 2013 A1
20130028404 Omalley et al. Jan 2013 A1
20130030787 Cancedda et al. Jan 2013 A1
20130030789 Dalce Jan 2013 A1
20130030804 Zavaliagkos et al. Jan 2013 A1
20130030815 Madhvanath et al. Jan 2013 A1
20130030904 Aidasani et al. Jan 2013 A1
20130030913 Zhu et al. Jan 2013 A1
20130030955 David Jan 2013 A1
20130031162 Willis et al. Jan 2013 A1
20130031476 Coin et al. Jan 2013 A1
20130176208 Tanaka et al. Jan 2013 A1
20130033643 Kim et al. Feb 2013 A1
20130035086 Chardon et al. Feb 2013 A1
20130035942 Kim et al. Feb 2013 A1
20130035961 Yegnanarayanan Feb 2013 A1
20130035994 Pattan et al. Feb 2013 A1
20130036200 Roberts et al. Feb 2013 A1
20130038618 Urbach Feb 2013 A1
20130041647 Ramerth et al. Feb 2013 A1
20130041654 Walker et al. Feb 2013 A1
20130041661 Lee et al. Feb 2013 A1
20130041665 Jang et al. Feb 2013 A1
20130041667 Longe et al. Feb 2013 A1
20130041968 Cohen et al. Feb 2013 A1
20130046544 Kay et al. Feb 2013 A1
20130047178 Moon et al. Feb 2013 A1
20130050089 Neels et al. Feb 2013 A1
20130054550 Bolohan Feb 2013 A1
20130054609 Rajput et al. Feb 2013 A1
20130054613 Bishop Feb 2013 A1
20130054631 Govani et al. Feb 2013 A1
20130054675 Jenkins et al. Feb 2013 A1
20130054706 Graham et al. Feb 2013 A1
20130054945 Free et al. Feb 2013 A1
20130055099 Yao et al. Feb 2013 A1
20130055147 Vasudev et al. Feb 2013 A1
20130055201 No et al. Feb 2013 A1
20130060571 Soemo et al. Mar 2013 A1
20130060807 Rambhia et al. Mar 2013 A1
20130061139 Mahkovec et al. Mar 2013 A1
20130063611 Papakipos et al. Mar 2013 A1
20130066832 Sheehan et al. Mar 2013 A1
20130067307 Tian et al. Mar 2013 A1
20130067312 Rose Mar 2013 A1
20130067421 Osman et al. Mar 2013 A1
20130069769 Pennington et al. Mar 2013 A1
20130073286 Bastea-Forte et al. Mar 2013 A1
20130073293 Jang et al. Mar 2013 A1
20130073346 Chun et al. Mar 2013 A1
20130073580 Mehanna et al. Mar 2013 A1
20130073676 Cockcroft Mar 2013 A1
20130078930 Chen et al. Mar 2013 A1
20130080152 Brun et al. Mar 2013 A1
20130080162 Chang et al. Mar 2013 A1
20130080167 Mozer Mar 2013 A1
20130080177 Chen Mar 2013 A1
20130080178 Kang et al. Mar 2013 A1
20130080251 Dempski Mar 2013 A1
20130082967 Hillis et al. Apr 2013 A1
20130084882 Khorashadi et al. Apr 2013 A1
20130085755 Bringert et al. Apr 2013 A1
20130085761 Bringert et al. Apr 2013 A1
20130086609 Levy et al. Apr 2013 A1
20130090921 Liu et al. Apr 2013 A1
20130091090 Spivack et al. Apr 2013 A1
20130095805 LeBeau et al. Apr 2013 A1
20130096909 Brun et al. Apr 2013 A1
20130096911 Beaufort et al. Apr 2013 A1
20130096917 Edgar et al. Apr 2013 A1
20130097566 Berglund Apr 2013 A1
20130097682 Zeljkovic et al. Apr 2013 A1
20130100017 Papakipos et al. Apr 2013 A1
20130100268 Mihailidis et al. Apr 2013 A1
20130103391 Millmore et al. Apr 2013 A1
20130103405 Namba et al. Apr 2013 A1
20130106742 Lee et al. May 2013 A1
20130107053 Ozaki May 2013 A1
20130109412 Nguyen et al. May 2013 A1
20130110505 Gruber et al. May 2013 A1
20130110511 Spiegel et al. May 2013 A1
20130110515 Guzzoni et al. May 2013 A1
20130110518 Gruber et al. May 2013 A1
20130110519 Cheyer et al. May 2013 A1
20130110520 Cheyer et al. May 2013 A1
20130110943 Menon et al. May 2013 A1
20130111330 Staikos et al. May 2013 A1
20130111348 Gruber et al. May 2013 A1
20130111365 Chen et al. May 2013 A1
20130111487 Cheyer et al. May 2013 A1
20130111581 Griffin et al. May 2013 A1
20130115927 Gruber et al. May 2013 A1
20130117022 Chen et al. May 2013 A1
20130124189 Baldwin et al. May 2013 A1
20130124672 Pan May 2013 A1
20130125168 Agnihotri et al. May 2013 A1
20130130669 Xiao et al. May 2013 A1
20130132081 Ryu et al. May 2013 A1
20130132084 Stonehocker et al. May 2013 A1
20130132089 Fanty et al. May 2013 A1
20130132871 Zeng et al. May 2013 A1
20130138440 Strope et al. May 2013 A1
20130141551 Kim Jun 2013 A1
20130142317 Reynolds Jun 2013 A1
20130142345 Waldmann Jun 2013 A1
20130144594 Bangalore et al. Jun 2013 A1
20130144616 Bangalore Jun 2013 A1
20130151258 Chandrasekar et al. Jun 2013 A1
20130151339 Kim et al. Jun 2013 A1
20130152092 Yadgar Jun 2013 A1
20130154811 Ferren et al. Jun 2013 A1
20130155948 Pinheiro et al. Jun 2013 A1
20130156198 Kim et al. Jun 2013 A1
20130157629 Lee et al. Jun 2013 A1
20130158977 Senior Jun 2013 A1
20130159847 Banke et al. Jun 2013 A1
20130159861 Rottler et al. Jun 2013 A1
20130165232 Nelson et al. Jun 2013 A1
20130166278 James et al. Jun 2013 A1
20130166303 Chang et al. Jun 2013 A1
20130166332 Hammad Jun 2013 A1
20130166442 Nakajima et al. Jun 2013 A1
20130167242 Paliwal Jun 2013 A1
20130170738 Capuozzo et al. Jul 2013 A1
20130172022 Seymour et al. Jul 2013 A1
20130173258 Liu et al. Jul 2013 A1
20130173268 Weng et al. Jul 2013 A1
20130173513 Chu et al. Jul 2013 A1
20130173610 Hu et al. Jul 2013 A1
20130173614 Ismalon Jul 2013 A1
20130174034 Brown et al. Jul 2013 A1
20130176147 Anderson et al. Jul 2013 A1
20130176244 Yamamoto et al. Jul 2013 A1
20130176592 Sasaki Jul 2013 A1
20130179168 Bae et al. Jul 2013 A1
20130179172 Nakamura et al. Jul 2013 A1
20130179440 Gordon Jul 2013 A1
20130179806 Bastide et al. Jul 2013 A1
20130183942 Novick et al. Jul 2013 A1
20130183944 Mozer et al. Jul 2013 A1
20130185059 Riccardi Jul 2013 A1
20130185066 Tzirkel-hancock et al. Jul 2013 A1
20130185074 Gruber et al. Jul 2013 A1
20130185081 Cheyer et al. Jul 2013 A1
20130185336 Singh et al. Jul 2013 A1
20130187850 Schulz et al. Jul 2013 A1
20130187857 Griffin et al. Jul 2013 A1
20130190021 Vieri et al. Jul 2013 A1
20130191117 Atti et al. Jul 2013 A1
20130191408 Volkert Jul 2013 A1
20130197911 Wei et al. Aug 2013 A1
20130197914 Yelvington et al. Aug 2013 A1
20130198159 Hendry Aug 2013 A1
20130198841 Poulson Aug 2013 A1
20130204813 Master et al. Aug 2013 A1
20130204897 McDougall Aug 2013 A1
20130204967 Seo et al. Aug 2013 A1
20130207898 Sullivan et al. Aug 2013 A1
20130210410 Xu Aug 2013 A1
20130210492 You et al. Aug 2013 A1
20130212501 Anderson et al. Aug 2013 A1
20130218553 Fujii et al. Aug 2013 A1
20130218560 Hsiao et al. Aug 2013 A1
20130218574 Falcon et al. Aug 2013 A1
20130218899 Raghavan et al. Aug 2013 A1
20130219333 Palwe et al. Aug 2013 A1
20130222249 Pasquero et al. Aug 2013 A1
20130223279 Tinnakornsrisuphap et al. Aug 2013 A1
20130225128 Gomar Aug 2013 A1
20130226935 Bai et al. Aug 2013 A1
20130226996 Itagaki et al. Aug 2013 A1
20130231917 Naik Sep 2013 A1
20130234947 Kristensson et al. Sep 2013 A1
20130235987 Arroniz-Escobar Sep 2013 A1
20130238312 Waibel Sep 2013 A1
20130238326 Kim et al. Sep 2013 A1
20130238334 Ma et al. Sep 2013 A1
20130238540 O'donoghue et al. Sep 2013 A1
20130238647 Thompson Sep 2013 A1
20130238729 Holzman et al. Sep 2013 A1
20130244615 Miller Sep 2013 A1
20130244633 Jacobs et al. Sep 2013 A1
20130246048 Nagase et al. Sep 2013 A1
20130246050 Yu et al. Sep 2013 A1
20130246329 Pasquero et al. Sep 2013 A1
20130253911 Petri et al. Sep 2013 A1
20130253912 Medlock et al. Sep 2013 A1
20130260739 Saino Oct 2013 A1
20130262168 Makanawala et al. Oct 2013 A1
20130268263 Park et al. Oct 2013 A1
20130268956 Recco Oct 2013 A1
20130275117 Winer Oct 2013 A1
20130275136 Czahor Oct 2013 A1
20130275138 Gruber et al. Oct 2013 A1
20130275164 Gruber et al. Oct 2013 A1
20130275199 Proctor, Jr. et al. Oct 2013 A1
20130275625 Taivalsaari et al. Oct 2013 A1
20130275875 Gruber et al. Oct 2013 A1
20130275899 Schubert et al. Oct 2013 A1
20130279724 Stafford et al. Oct 2013 A1
20130282709 Zhu et al. Oct 2013 A1
20130283168 Brown et al. Oct 2013 A1
20130283199 Selig et al. Oct 2013 A1
20130283283 Wang et al. Oct 2013 A1
20130285913 Griffin et al. Oct 2013 A1
20130288722 Ramanujam et al. Oct 2013 A1
20130289991 Eshwar et al. Oct 2013 A1
20130289993 Rao Oct 2013 A1
20130289994 Newman et al. Oct 2013 A1
20130290001 Yun et al. Oct 2013 A1
20130290222 Gordo et al. Oct 2013 A1
20130290905 Luvogt et al. Oct 2013 A1
20130291015 Pan Oct 2013 A1
20130297078 Kolavennu Nov 2013 A1
20130297198 Velde et al. Nov 2013 A1
20130297317 Lee et al. Nov 2013 A1
20130297319 Kim Nov 2013 A1
20130297348 Cardoza et al. Nov 2013 A1
20130300645 Fedorov Nov 2013 A1
20130300648 Kim et al. Nov 2013 A1
20130303106 Martin Nov 2013 A1
20130304476 Kim et al. Nov 2013 A1
20130304479 Teller et al. Nov 2013 A1
20130304758 Gruber et al. Nov 2013 A1
20130304815 Puente et al. Nov 2013 A1
20130305119 Kern et al. Nov 2013 A1
20130307855 Lamb et al. Nov 2013 A1
20130307997 O'Keefe et al. Nov 2013 A1
20130308922 Sano et al. Nov 2013 A1
20130311179 Wagner Nov 2013 A1
20130311184 Badavne et al. Nov 2013 A1
20130311487 Moore et al. Nov 2013 A1
20130311997 Gruber et al. Nov 2013 A1
20130315038 Ferren et al. Nov 2013 A1
20130316679 Miller et al. Nov 2013 A1
20130316746 Miller et al. Nov 2013 A1
20130317921 Havas Nov 2013 A1
20130318478 Ogura Nov 2013 A1
20130321267 Bhatti et al. Dec 2013 A1
20130322634 Bennett et al. Dec 2013 A1
20130322665 Bennett et al. Dec 2013 A1
20130325340 Forstall et al. Dec 2013 A1
20130325436 Wang et al. Dec 2013 A1
20130325443 Begeja et al. Dec 2013 A1
20130325447 Levien et al. Dec 2013 A1
20130325448 Levien et al. Dec 2013 A1
20130325460 Kim et al. Dec 2013 A1
20130325480 Lee et al. Dec 2013 A1
20130325481 Van Os et al. Dec 2013 A1
20130325484 Chakladar et al. Dec 2013 A1
20130325844 Plaisant Dec 2013 A1
20130325967 Parks et al. Dec 2013 A1
20130325970 Roberts et al. Dec 2013 A1
20130325979 Mansfield et al. Dec 2013 A1
20130326576 Zhang et al. Dec 2013 A1
20130328809 Smith Dec 2013 A1
20130329023 Suplee, III et al. Dec 2013 A1
20130331127 Sabatelli et al. Dec 2013 A1
20130332113 Piemonte et al. Dec 2013 A1
20130332159 Federighi et al. Dec 2013 A1
20130332162 Keen Dec 2013 A1
20130332164 Nalk Dec 2013 A1
20130332168 Kim et al. Dec 2013 A1
20130332172 Prakash et al. Dec 2013 A1
20130332400 González Dec 2013 A1
20130332538 Clark et al. Dec 2013 A1
20130332721 Chaudhri et al. Dec 2013 A1
20130339028 Rosner et al. Dec 2013 A1
20130339256 Shroff Dec 2013 A1
20130339454 Walker et al. Dec 2013 A1
20130339991 Ricci Dec 2013 A1
20130342672 Gray et al. Dec 2013 A1
20130343584 Bennett et al. Dec 2013 A1
20130343721 Abecassis Dec 2013 A1
20130346065 Davidson et al. Dec 2013 A1
20130346068 Solem et al. Dec 2013 A1
20130346347 Patterson et al. Dec 2013 A1
20130346488 Lunt et al. Dec 2013 A1
20130347018 Limp et al. Dec 2013 A1
20130347029 Tang et al. Dec 2013 A1
20130347102 Shi Dec 2013 A1
20130347117 Parks et al. Dec 2013 A1
20140001255 Anthoine Jan 2014 A1
20140002338 Raffa et al. Jan 2014 A1
20140006012 Zhou et al. Jan 2014 A1
20140006025 Krishnan et al. Jan 2014 A1
20140006027 Kim et al. Jan 2014 A1
20140006028 Hu Jan 2014 A1
20140006030 Fleizach et al. Jan 2014 A1
20140006153 Thangam et al. Jan 2014 A1
20140006191 Shankar et al. Jan 2014 A1
20140006483 Garmark et al. Jan 2014 A1
20140006496 Dearman et al. Jan 2014 A1
20140006562 Handa et al. Jan 2014 A1
20140006947 Garmark et al. Jan 2014 A1
20140006951 Hunter Jan 2014 A1
20140006955 Greenzeiger et al. Jan 2014 A1
20140008163 Mikonaho et al. Jan 2014 A1
20140012574 Pasupalak et al. Jan 2014 A1
20140012580 Ganong, III et al. Jan 2014 A1
20140012586 Rubin et al. Jan 2014 A1
20140012587 Park Jan 2014 A1
20140013336 Yang Jan 2014 A1
20140019116 Lundberg et al. Jan 2014 A1
20140019133 Bao et al. Jan 2014 A1
20140019460 Sambrani et al. Jan 2014 A1
20140026037 Garb et al. Jan 2014 A1
20140028029 Jochman Jan 2014 A1
20140028477 Michalske Jan 2014 A1
20140028735 Williams et al. Jan 2014 A1
20140032453 Eustice et al. Jan 2014 A1
20140032678 Koukoumidis et al. Jan 2014 A1
20140033071 Gruber et al. Jan 2014 A1
20140035823 Khoe et al. Feb 2014 A1
20140037075 Bouzid et al. Feb 2014 A1
20140039888 Taubman et al. Feb 2014 A1
20140039893 Weiner et al. Feb 2014 A1
20140039894 Shostak Feb 2014 A1
20140040274 Aravamudan et al. Feb 2014 A1
20140040748 Lemay et al. Feb 2014 A1
20140040754 Donelli Feb 2014 A1
20140040801 Patel et al. Feb 2014 A1
20140040918 Li Feb 2014 A1
20140040961 Green et al. Feb 2014 A1
20140046934 Zhou et al. Feb 2014 A1
20140047001 Phillips et al. Feb 2014 A1
20140052451 Cheong et al. Feb 2014 A1
20140052680 Nitz et al. Feb 2014 A1
20140052791 Chakra et al. Feb 2014 A1
20140053082 Park Feb 2014 A1
20140053101 Buehler et al. Feb 2014 A1
20140053210 Cheong et al. Feb 2014 A1
20140057610 Olincy et al. Feb 2014 A1
20140059030 Hakkani-Tur et al. Feb 2014 A1
20140059423 Gorga et al. Feb 2014 A1
20140067361 Nikoulina et al. Mar 2014 A1
20140067371 Liensberger Mar 2014 A1
20140067402 Kim Mar 2014 A1
20140067738 Kingsbury Mar 2014 A1
20140067740 Solari Mar 2014 A1
20140068751 Last Mar 2014 A1
20140074454 Brown et al. Mar 2014 A1
20140074466 Sharifi et al. Mar 2014 A1
20140074470 Jansche et al. Mar 2014 A1
20140074472 Lin et al. Mar 2014 A1
20140074482 Ohno Mar 2014 A1
20140074483 Van Os Mar 2014 A1
20140074589 Nielsen et al. Mar 2014 A1
20140074815 Plimton Mar 2014 A1
20140074846 Moss et al. Mar 2014 A1
20140075453 Bellessort et al. Mar 2014 A1
20140078065 Akkok Mar 2014 A1
20140079195 Srivastava et al. Mar 2014 A1
20140080410 Jung et al. Mar 2014 A1
20140080428 Rhoads et al. Mar 2014 A1
20140081619 Solntseva et al. Mar 2014 A1
20140081633 Badaskar Mar 2014 A1
20140081635 Yanagihara Mar 2014 A1
20140081829 Milne Mar 2014 A1
20140081941 Bai et al. Mar 2014 A1
20140082500 Wilensky et al. Mar 2014 A1
20140082501 Bae et al. Mar 2014 A1
20140082545 Zhai et al. Mar 2014 A1
20140082715 Grajek et al. Mar 2014 A1
20140086458 Rogers Mar 2014 A1
20140087711 Geyer et al. Mar 2014 A1
20140088952 Fife et al. Mar 2014 A1
20140088961 Woodward et al. Mar 2014 A1
20140088964 Bellegarda Mar 2014 A1
20140088970 Kang Mar 2014 A1
20140092007 Kim et al. Apr 2014 A1
20140095171 Lynch et al. Apr 2014 A1
20140095172 Cabaco et al. Apr 2014 A1
20140095173 Lynch et al. Apr 2014 A1
20140095432 Trumbull et al. Apr 2014 A1
20140095601 Abuelsaad et al. Apr 2014 A1
20140095965 Li Apr 2014 A1
20140096077 Jacob et al. Apr 2014 A1
20140096209 Saraf et al. Apr 2014 A1
20140098247 Rao et al. Apr 2014 A1
20140100847 Ishii et al. Apr 2014 A1
20140101127 Simhon et al. Apr 2014 A1
20140104175 Ouyang et al. Apr 2014 A1
20140108017 Mason et al. Apr 2014 A1
20140108357 Procops et al. Apr 2014 A1
20140108391 Volkert Apr 2014 A1
20140112556 Kalinli-Akbacak Apr 2014 A1
20140114554 Lagassey Apr 2014 A1
20140115062 Liu et al. Apr 2014 A1
20140115114 Garmark et al. Apr 2014 A1
20140118155 Bowers et al. May 2014 A1
20140118624 Jang et al. May 2014 A1
20140120961 Buck May 2014 A1
20140122059 Patel et al. May 2014 A1
20140122085 Piety et al. May 2014 A1
20140122086 Kapur et al. May 2014 A1
20140122136 Jayanthi May 2014 A1
20140122153 Truitt May 2014 A1
20140123022 Lee et al. May 2014 A1
20140128021 Walker et al. May 2014 A1
20140129006 Chen et al. May 2014 A1
20140129226 Lee et al. May 2014 A1
20140132935 Kim et al. May 2014 A1
20140134983 Jung et al. May 2014 A1
20140135036 Bonanni et al. May 2014 A1
20140136013 Wolverton et al. May 2014 A1
20140136187 Wolverton et al. May 2014 A1
20140136195 Abdossalami et al. May 2014 A1
20140136212 Kwon et al. May 2014 A1
20140136946 Matas May 2014 A1
20140136987 Rodriguez May 2014 A1
20140142922 Liang et al. May 2014 A1
20140142923 Jones et al. May 2014 A1
20140142935 Lindahl et al. May 2014 A1
20140142953 Kim et al. May 2014 A1
20140143550 Ganong, III et al. May 2014 A1
20140143721 Suzuki et al. May 2014 A1
20140143784 Mistry et al. May 2014 A1
20140146200 Scott et al. May 2014 A1
20140149118 Lee et al. May 2014 A1
20140152577 Yuen et al. Jun 2014 A1
20140153709 Byrd et al. Jun 2014 A1
20140155031 Lee et al. Jun 2014 A1
20140156262 Yuen et al. Jun 2014 A1
20140156269 Lee et al. Jun 2014 A1
20140156279 Okamoto et al. Jun 2014 A1
20140156564 Knight et al. Jun 2014 A1
20140157319 Kimura et al. Jun 2014 A1
20140157422 Livshits et al. Jun 2014 A1
20140163751 Davis et al. Jun 2014 A1
20140163951 Nikoulina et al. Jun 2014 A1
20140163953 Parikh Jun 2014 A1
20140163954 Joshi et al. Jun 2014 A1
20140163962 Castelli et al. Jun 2014 A1
20140163976 Park et al. Jun 2014 A1
20140163977 Hoffmeister et al. Jun 2014 A1
20140163978 Basye et al. Jun 2014 A1
20140163981 Cook et al. Jun 2014 A1
20140163995 Burns et al. Jun 2014 A1
20140164305 Lynch et al. Jun 2014 A1
20140164312 Lynch et al. Jun 2014 A1
20140164476 Thomson Jun 2014 A1
20140164508 Lynch et al. Jun 2014 A1
20140164532 Lynch et al. Jun 2014 A1
20140164533 Lynch et al. Jun 2014 A1
20140164953 Lynch et al. Jun 2014 A1
20140169795 Clough Jun 2014 A1
20140171064 Das Jun 2014 A1
20140172412 Viegas et al. Jun 2014 A1
20140172878 Clark et al. Jun 2014 A1
20140173445 Grassiotto Jun 2014 A1
20140173460 Kim Jun 2014 A1
20140176814 Ahn Jun 2014 A1
20140179295 Luebbers et al. Jun 2014 A1
20140180499 Cooper et al. Jun 2014 A1
20140180689 Kim Jun 2014 A1
20140180697 Torok et al. Jun 2014 A1
20140181741 Apacible et al. Jun 2014 A1
20140181865 Koganei Jun 2014 A1
20140188335 Madhok et al. Jul 2014 A1
20140188460 Ouyang et al. Jul 2014 A1
20140188477 Zhang Jul 2014 A1
20140188478 Zhang Jul 2014 A1
20140188485 Kim et al. Jul 2014 A1
20140188835 Zhang et al. Jul 2014 A1
20140195226 Yun et al. Jul 2014 A1
20140195230 Han et al. Jul 2014 A1
20140195233 Bapat et al. Jul 2014 A1
20140195244 Cha et al. Jul 2014 A1
20140195251 Zeinstra et al. Jul 2014 A1
20140195252 Gruber et al. Jul 2014 A1
20140198048 Unruh et al. Jul 2014 A1
20140203939 Harrington et al. Jul 2014 A1
20140205076 Kumar et al. Jul 2014 A1
20140207439 Venkatapathy et al. Jul 2014 A1
20140207446 Klein et al. Jul 2014 A1
20140207447 Jiang et al. Jul 2014 A1
20140207466 Smadi Jul 2014 A1
20140207468 Bartnik Jul 2014 A1
20140207582 Flinn et al. Jul 2014 A1
20140211944 Hayward et al. Jul 2014 A1
20140214429 Pantel Jul 2014 A1
20140214537 Yoo et al. Jul 2014 A1
20140215367 Kim et al. Jul 2014 A1
20140215513 Ramer et al. Jul 2014 A1
20140218372 Missig et al. Aug 2014 A1
20140222422 Sarikaya et al. Aug 2014 A1
20140222435 Li et al. Aug 2014 A1
20140222436 Binder et al. Aug 2014 A1
20140222678 Sheets et al. Aug 2014 A1
20140222967 Harrang et al. Aug 2014 A1
20140223377 Shaw et al. Aug 2014 A1
20140223481 Fundament Aug 2014 A1
20140226503 Cooper et al. Aug 2014 A1
20140229158 Zweig et al. Aug 2014 A1
20140229184 Shires Aug 2014 A1
20140230055 Boehl Aug 2014 A1
20140232570 Skinder et al. Aug 2014 A1
20140232656 Pasquero et al. Aug 2014 A1
20140236595 Gray Aug 2014 A1
20140236986 Guzman Aug 2014 A1
20140237042 Ahmed et al. Aug 2014 A1
20140237366 Poulos et al. Aug 2014 A1
20140244248 Arisoy et al. Aug 2014 A1
20140244249 Mohamed et al. Aug 2014 A1
20140244254 Ju et al. Aug 2014 A1
20140244257 Colibro et al. Aug 2014 A1
20140244258 Song et al. Aug 2014 A1
20140244263 Pontual et al. Aug 2014 A1
20140244266 Brown et al. Aug 2014 A1
20140244268 Abdelsamie et al. Aug 2014 A1
20140244270 Han et al. Aug 2014 A1
20140244271 Lindahl Aug 2014 A1
20140244712 Walters et al. Aug 2014 A1
20140245140 Brown et al. Aug 2014 A1
20140247383 Dave et al. Sep 2014 A1
20140247926 Gainsboro et al. Sep 2014 A1
20140249812 Bou-Ghazale et al. Sep 2014 A1
20140249816 Pickering et al. Sep 2014 A1
20140249817 Hart et al. Sep 2014 A1
20140249820 Hsu et al. Sep 2014 A1
20140249821 Kennewick et al. Sep 2014 A1
20140250046 Winn et al. Sep 2014 A1
20140257809 Goel et al. Sep 2014 A1
20140257815 Zhao et al. Sep 2014 A1
20140257902 Moore et al. Sep 2014 A1
20140258324 Mauro et al. Sep 2014 A1
20140258357 Singh et al. Sep 2014 A1
20140258857 Dykstra-Erickson et al. Sep 2014 A1
20140258905 Lee et al. Sep 2014 A1
20140267022 Kim Sep 2014 A1
20140267599 Drouin et al. Sep 2014 A1
20140267933 Young Sep 2014 A1
20140272821 Pitschel et al. Sep 2014 A1
20140273979 Van Os et al. Sep 2014 A1
20140274005 Luna et al. Sep 2014 A1
20140274203 Ganong, III et al. Sep 2014 A1
20140274211 Sejnoha et al. Sep 2014 A1
20140278051 Mcgavran et al. Sep 2014 A1
20140278343 Tran Sep 2014 A1
20140278349 Grieves et al. Sep 2014 A1
20140278379 Coccaro et al. Sep 2014 A1
20140278390 Kingsbury et al. Sep 2014 A1
20140278391 Braho et al. Sep 2014 A1
20140278394 Bastyr et al. Sep 2014 A1
20140278406 Tsumura et al. Sep 2014 A1
20140278413 Pitschel et al. Sep 2014 A1
20140278426 Jost et al. Sep 2014 A1
20140278429 Ganong, III Sep 2014 A1
20140278435 Ganong, III et al. Sep 2014 A1
20140278436 Khanna et al. Sep 2014 A1
20140278438 Hart et al. Sep 2014 A1
20140278443 Gunn et al. Sep 2014 A1
20140278444 Larson et al. Sep 2014 A1
20140278513 Prakash et al. Sep 2014 A1
20140279622 Lamoureux et al. Sep 2014 A1
20140279739 Elkington et al. Sep 2014 A1
20140279787 Cheng et al. Sep 2014 A1
20140280072 Coleman Sep 2014 A1
20140280107 Heymans et al. Sep 2014 A1
20140280138 Li et al. Sep 2014 A1
20140280292 Skinder Sep 2014 A1
20140280353 Delaney et al. Sep 2014 A1
20140280450 Luna Sep 2014 A1
20140280757 Tran Sep 2014 A1
20140281944 Winer Sep 2014 A1
20140281983 Xian et al. Sep 2014 A1
20140281997 Fleizach et al. Sep 2014 A1
20140282003 Gruber et al. Sep 2014 A1
20140282007 Fleizach Sep 2014 A1
20140282045 Ayanam et al. Sep 2014 A1
20140282178 Borzello et al. Sep 2014 A1
20140282201 Pasquero et al. Sep 2014 A1
20140282203 Pasquero et al. Sep 2014 A1
20140282559 Verduzco et al. Sep 2014 A1
20140282586 Shear et al. Sep 2014 A1
20140282743 Howard et al. Sep 2014 A1
20140288990 Moore et al. Sep 2014 A1
20140289508 Wang Sep 2014 A1
20140297267 Spencer et al. Oct 2014 A1
20140297281 Togawa et al. Oct 2014 A1
20140297284 Gruber et al. Oct 2014 A1
20140297288 Yu et al. Oct 2014 A1
20140298395 Yang et al. Oct 2014 A1
20140304086 Dasdan et al. Oct 2014 A1
20140304605 Ohmura et al. Oct 2014 A1
20140309990 Gandrabur et al. Oct 2014 A1
20140309996 Zhang Oct 2014 A1
20140310001 Kalns et al. Oct 2014 A1
20140310002 Nitz et al. Oct 2014 A1
20140310348 Keskitalo et al. Oct 2014 A1
20140310365 Sample et al. Oct 2014 A1
20140310595 Acharya et al. Oct 2014 A1
20140313007 Harding Oct 2014 A1
20140315492 Woods Oct 2014 A1
20140316585 Boesveld et al. Oct 2014 A1
20140317030 Shen et al. Oct 2014 A1
20140317502 Brown et al. Oct 2014 A1
20140324429 Weilhammer et al. Oct 2014 A1
20140324884 Lindahl et al. Oct 2014 A1
20140330560 Venkatesha et al. Nov 2014 A1
20140330569 Kolavennu et al. Nov 2014 A1
20140330951 Sukoff et al. Nov 2014 A1
20140335823 Heredia et al. Nov 2014 A1
20140337037 Chi Nov 2014 A1
20140337048 Brown et al. Nov 2014 A1
20140337266 Wolverton et al. Nov 2014 A1
20140337370 Aravamudan et al. Nov 2014 A1
20140337371 Li Nov 2014 A1
20140337438 Govande et al. Nov 2014 A1
20140337621 Nakhimov Nov 2014 A1
20140337751 Lim et al. Nov 2014 A1
20140337814 Kalns et al. Nov 2014 A1
20140342762 Hajdu et al. Nov 2014 A1
20140343834 Demerchant et al. Nov 2014 A1
20140343943 Al-telmissani Nov 2014 A1
20140343946 Torok et al. Nov 2014 A1
20140344205 Luna et al. Nov 2014 A1
20140344627 Schaub et al. Nov 2014 A1
20140344687 Durham et al. Nov 2014 A1
20140347181 Luna et al. Nov 2014 A1
20140350847 Ichinokawa Nov 2014 A1
20140350924 Zurek et al. Nov 2014 A1
20140350933 Bak et al. Nov 2014 A1
20140351741 Medlock et al. Nov 2014 A1
20140351760 Skory et al. Nov 2014 A1
20140358519 Mirkin et al. Dec 2014 A1
20140358521 Mikutel et al. Dec 2014 A1
20140358523 Sheth et al. Dec 2014 A1
20140358549 O'connor et al. Dec 2014 A1
20140359637 Yan Dec 2014 A1
20140359709 Nassar et al. Dec 2014 A1
20140361973 Raux et al. Dec 2014 A1
20140363074 Dolfing et al. Dec 2014 A1
20140364149 Marti et al. Dec 2014 A1
20140365209 Evermann Dec 2014 A1
20140365214 Bayley Dec 2014 A1
20140365216 Gruber et al. Dec 2014 A1
20140365226 Sinha Dec 2014 A1
20140365227 Cash et al. Dec 2014 A1
20140365407 Brown et al. Dec 2014 A1
20140365505 Clark et al. Dec 2014 A1
20140365880 Bellegarda Dec 2014 A1
20140365885 Carson et al. Dec 2014 A1
20140365895 Magahern et al. Dec 2014 A1
20140365922 Yang Dec 2014 A1
20140365945 Karunamuni et al. Dec 2014 A1
20140370817 Luna Dec 2014 A1
20140370841 Roberts et al. Dec 2014 A1
20140372112 Xue et al. Dec 2014 A1
20140372356 Bilal et al. Dec 2014 A1
20140372468 Collins et al. Dec 2014 A1
20140372931 Zhai et al. Dec 2014 A1
20140379326 Sarikaya et al. Dec 2014 A1
20140379334 Fry Dec 2014 A1
20140379338 Fry Dec 2014 A1
20140379341 Seo et al. Dec 2014 A1
20140379798 Bunner et al. Dec 2014 A1
20140380285 Gabel et al. Dec 2014 A1
20150003797 Schmidt Jan 2015 A1
20150004958 Wang et al. Jan 2015 A1
20150005009 Tomkins et al. Jan 2015 A1
20150006148 Goldszmit et al. Jan 2015 A1
20150006157 Silva et al. Jan 2015 A1
20150006167 Kato et al. Jan 2015 A1
20150006176 Pogue et al. Jan 2015 A1
20150006178 Peng et al. Jan 2015 A1
20150006184 Marti et al. Jan 2015 A1
20150006199 Snider et al. Jan 2015 A1
20150012271 Peng et al. Jan 2015 A1
20150012862 Ikeda et al. Jan 2015 A1
20150019219 Tzirkel-Hancock et al. Jan 2015 A1
20150019221 Lee et al. Jan 2015 A1
20150019445 Glass et al. Jan 2015 A1
20150019944 Kalgi Jan 2015 A1
20150019954 Dalal et al. Jan 2015 A1
20150019974 Doi et al. Jan 2015 A1
20150025405 Vairavan et al. Jan 2015 A1
20150025890 Jagatheesan et al. Jan 2015 A1
20150026620 Kwon et al. Jan 2015 A1
20150027178 Scalisi Jan 2015 A1
20150031416 Labowicz et al. Jan 2015 A1
20150032443 Karov et al. Jan 2015 A1
20150032457 Koo et al. Jan 2015 A1
20150033219 Breiner et al. Jan 2015 A1
20150033275 Natani et al. Jan 2015 A1
20150034855 Shen Feb 2015 A1
20150038161 Jakobson et al. Feb 2015 A1
20150039292 Suleman et al. Feb 2015 A1
20150039295 Soschen Feb 2015 A1
20150039299 Weinstein et al. Feb 2015 A1
20150039305 Huang Feb 2015 A1
20150039606 Salaka et al. Feb 2015 A1
20150040012 Faaborg et al. Feb 2015 A1
20150045003 Vora et al. Feb 2015 A1
20150045007 Cash Feb 2015 A1
20150045068 Soffer et al. Feb 2015 A1
20150046434 Lim et al. Feb 2015 A1
20150046537 Rakib Feb 2015 A1
20150046828 Desai et al. Feb 2015 A1
20150050633 Christmas et al. Feb 2015 A1
20150050923 Tu et al. Feb 2015 A1
20150051754 Kwon et al. Feb 2015 A1
20150053779 Adamek et al. Feb 2015 A1
20150053781 Nelson et al. Feb 2015 A1
20150055879 Yang Feb 2015 A1
20150058013 Pakhomov et al. Feb 2015 A1
20150058018 Georges et al. Feb 2015 A1
20150058720 Smadja et al. Feb 2015 A1
20150058785 Ookawara Feb 2015 A1
20150065149 Russell et al. Mar 2015 A1
20150065200 Namgung et al. Mar 2015 A1
20150066479 Pasupalak et al. Mar 2015 A1
20150066494 Salvador et al. Mar 2015 A1
20150066496 Deoras et al. Mar 2015 A1
20150066506 Romano et al. Mar 2015 A1
20150066516 Nishikawa et al. Mar 2015 A1
20150066817 Slayton et al. Mar 2015 A1
20150067485 Kim et al. Mar 2015 A1
20150067819 Shribman et al. Mar 2015 A1
20150067822 Randall Mar 2015 A1
20150071121 Patil et al. Mar 2015 A1
20150073788 Sak et al. Mar 2015 A1
20150073804 Senior et al. Mar 2015 A1
20150074524 Nicholson et al. Mar 2015 A1
20150074615 Han et al. Mar 2015 A1
20150081295 Yun et al. Mar 2015 A1
20150082180 Ames et al. Mar 2015 A1
20150082229 Ouyang et al. Mar 2015 A1
20150086174 Abecassis et al. Mar 2015 A1
20150088511 Bharadwaj et al. Mar 2015 A1
20150088514 Typrin Mar 2015 A1
20150088518 Kim et al. Mar 2015 A1
20150088522 Hendrickson et al. Mar 2015 A1
20150088523 Schuster Mar 2015 A1
20150088998 Isensee et al. Mar 2015 A1
20150092520 Robison et al. Apr 2015 A1
20150094834 Vega et al. Apr 2015 A1
20150095031 Conkie et al. Apr 2015 A1
20150095159 Kennewick et al. Apr 2015 A1
20150095268 Greenzeiger et al. Apr 2015 A1
20150095278 Flinn et al. Apr 2015 A1
20150100144 Lee et al. Apr 2015 A1
20150100313 Sharma Apr 2015 A1
20150100316 Williams et al. Apr 2015 A1
20150100537 Grieves et al. Apr 2015 A1
20150100983 Pan Apr 2015 A1
20150106061 Yang et al. Apr 2015 A1
20150106085 Lindahl Apr 2015 A1
20150106093 Weeks et al. Apr 2015 A1
20150106737 Montoy-Wilson et al. Apr 2015 A1
20150112684 Scheffer et al. Apr 2015 A1
20150113407 Hoffert et al. Apr 2015 A1
20150113435 Phillips Apr 2015 A1
20150120296 Stern et al. Apr 2015 A1
20150120641 Soon-Shiong et al. Apr 2015 A1
20150120723 Deshmukh et al. Apr 2015 A1
20150121216 Brown et al. Apr 2015 A1
20150123898 Kim et al. May 2015 A1
20150127337 Heigold et al. May 2015 A1
20150127348 Follis May 2015 A1
20150127350 Agiomyrgiannakis May 2015 A1
20150128058 Anajwala May 2015 A1
20150133049 Lee et al. May 2015 A1
20150133109 Freeman et al. May 2015 A1
20150134318 Cuthbert et al. May 2015 A1
20150134322 Cuthbert et al. May 2015 A1
20150134323 Cuthbert et al. May 2015 A1
20150134334 Sachidanandam et al. May 2015 A1
20150135085 Shoham et al. May 2015 A1
20150135123 Carr et al. May 2015 A1
20150140934 Abdurrahman et al. May 2015 A1
20150140990 Kim et al. May 2015 A1
20150141150 Zha May 2015 A1
20150142420 Sarikaya et al. May 2015 A1
20150142438 Dai et al. May 2015 A1
20150142440 Parkinson et al. May 2015 A1
20150142447 Kennewick et al. May 2015 A1
20150142851 Gupta et al. May 2015 A1
20150143419 Bhagwat et al. May 2015 A1
20150148013 Baldwin et al. May 2015 A1
20150149177 Kalns et al. May 2015 A1
20150149182 Kalns et al. May 2015 A1
20150149354 Mccoy May 2015 A1
20150149469 Xu et al. May 2015 A1
20150149899 Bernstein et al. May 2015 A1
20150149964 Bernstein et al. May 2015 A1
20150154001 Knox et al. Jun 2015 A1
20150154185 Waibel Jun 2015 A1
20150154976 Mutagi Jun 2015 A1
20150160855 Bi Jun 2015 A1
20150161291 Gur et al. Jun 2015 A1
20150161370 North et al. Jun 2015 A1
20150161521 Shah et al. Jun 2015 A1
20150161989 Hsu et al. Jun 2015 A1
20150162000 Di Censo et al. Jun 2015 A1
20150162001 Kar et al. Jun 2015 A1
20150162006 Kummer Jun 2015 A1
20150163558 Wheatley Jun 2015 A1
20150169081 Neels et al. Jun 2015 A1
20150169284 Quast et al. Jun 2015 A1
20150169336 Harper et al. Jun 2015 A1
20150169696 Krishnappa et al. Jun 2015 A1
20150170073 Baker Jun 2015 A1
20150170664 Doherty et al. Jun 2015 A1
20150172262 Ortiz, Jr. et al. Jun 2015 A1
20150172463 Quast et al. Jun 2015 A1
20150178388 Winnemoeller et al. Jun 2015 A1
20150178785 Salonen Jun 2015 A1
20150179168 Hakkani-tur et al. Jun 2015 A1
20150179176 Ryu et al. Jun 2015 A1
20150181285 Zhang et al. Jun 2015 A1
20150185964 Stout Jul 2015 A1
20150185993 Wheatley et al. Jul 2015 A1
20150185996 Brown et al. Jul 2015 A1
20150186012 Coleman et al. Jul 2015 A1
20150186110 Kannan Jul 2015 A1
20150186154 Brown et al. Jul 2015 A1
20150186155 Brown et al. Jul 2015 A1
20150186156 Brown et al. Jul 2015 A1
20150186351 Hicks et al. Jul 2015 A1
20150186538 Yan et al. Jul 2015 A1
20150186783 Byrne et al. Jul 2015 A1
20150186892 Zhang et al. Jul 2015 A1
20150187355 Parkinson et al. Jul 2015 A1
20150187369 Dadu et al. Jul 2015 A1
20150189362 Lee et al. Jul 2015 A1
20150193379 Mehta Jul 2015 A1
20150193391 Khvostichenko et al. Jul 2015 A1
20150193392 Greenblatt et al. Jul 2015 A1
20150194152 Katuri et al. Jul 2015 A1
20150194165 Faaborg et al. Jul 2015 A1
20150195379 Zhang et al. Jul 2015 A1
20150195606 McDevitt Jul 2015 A1
20150199077 Zuger et al. Jul 2015 A1
20150199960 Huo et al. Jul 2015 A1
20150199965 Leak et al. Jul 2015 A1
20150199967 Reddy et al. Jul 2015 A1
20150200879 Wu et al. Jul 2015 A1
20150201064 Bells et al. Jul 2015 A1
20150201077 Konig et al. Jul 2015 A1
20150205425 Kuscher et al. Jul 2015 A1
20150205568 Matsuoka Jul 2015 A1
20150205632 Gaster Jul 2015 A1
20150205858 Xie et al. Jul 2015 A1
20150206529 Kwon et al. Jul 2015 A1
20150208226 Kuusilinna et al. Jul 2015 A1
20150212791 Kumar et al. Jul 2015 A1
20150213140 Volkert Jul 2015 A1
20150213796 Waltermann et al. Jul 2015 A1
20150215258 Nowakowski et al. Jul 2015 A1
20150215350 Slayton et al. Jul 2015 A1
20150217870 Mccullough et al. Aug 2015 A1
20150220264 Lewis et al. Aug 2015 A1
20150220507 Mohajer et al. Aug 2015 A1
20150220715 Kim et al. Aug 2015 A1
20150220972 Subramanya et al. Aug 2015 A1
20150221302 Han et al. Aug 2015 A1
20150221304 Stewart Aug 2015 A1
20150221307 Shah et al. Aug 2015 A1
20150222586 Ebersman et al. Aug 2015 A1
20150224848 Eisenhour Aug 2015 A1
20150227505 Morimoto Aug 2015 A1
20150227633 Shapira Aug 2015 A1
20150228274 Leppanen et al. Aug 2015 A1
20150228275 Watanabe et al. Aug 2015 A1
20150228281 Raniere Aug 2015 A1
20150228282 Evrard Aug 2015 A1
20150228283 Ehsani et al. Aug 2015 A1
20150228292 Goldstein et al. Aug 2015 A1
20150230095 Smith et al. Aug 2015 A1
20150234556 Shaofeng et al. Aug 2015 A1
20150234636 Barnes, Jr. Aug 2015 A1
20150234800 Patrick et al. Aug 2015 A1
20150235434 Miller et al. Aug 2015 A1
20150237301 Shi et al. Aug 2015 A1
20150242091 Lu et al. Aug 2015 A1
20150242385 Bao et al. Aug 2015 A1
20150243278 Kibre et al. Aug 2015 A1
20150243279 Morse et al. Aug 2015 A1
20150243283 Halash et al. Aug 2015 A1
20150244665 Choi et al. Aug 2015 A1
20150245154 Dadu et al. Aug 2015 A1
20150248651 Akutagawa et al. Sep 2015 A1
20150248886 Sarikaya et al. Sep 2015 A1
20150249715 Helvik et al. Sep 2015 A1
20150253146 Annapureddy et al. Sep 2015 A1
20150253885 Kagan et al. Sep 2015 A1
20150254057 Klein et al. Sep 2015 A1
20150254058 Klein et al. Sep 2015 A1
20150254333 Fife et al. Sep 2015 A1
20150255068 Kim et al. Sep 2015 A1
20150255071 Chiba Sep 2015 A1
20150256873 Klein et al. Sep 2015 A1
20150261298 Li Sep 2015 A1
20150261496 Faaborg et al. Sep 2015 A1
20150261850 Mittal Sep 2015 A1
20150261944 Hosom et al. Sep 2015 A1
20150262583 Kanda et al. Sep 2015 A1
20150269139 McAteer et al. Sep 2015 A1
20150269617 Mikurak Sep 2015 A1
20150269677 Milne Sep 2015 A1
20150269943 VanBlon et al. Sep 2015 A1
20150277574 Jain et al. Oct 2015 A1
20150278199 Hazen et al. Oct 2015 A1
20150278348 Paruchuri et al. Oct 2015 A1
20150278370 Stratvert et al. Oct 2015 A1
20150278737 Chen Huebscher et al. Oct 2015 A1
20150279358 Kingsbury et al. Oct 2015 A1
20150279360 Mengibar et al. Oct 2015 A1
20150279366 Krestnikov et al. Oct 2015 A1
20150281380 Wang et al. Oct 2015 A1
20150281401 Le et al. Oct 2015 A1
20150286627 Chang et al. Oct 2015 A1
20150286716 Snibbe et al. Oct 2015 A1
20150286937 Hildebrand Oct 2015 A1
20150287401 Lee et al. Oct 2015 A1
20150287408 Svendsen et al. Oct 2015 A1
20150287409 Jang Oct 2015 A1
20150287411 Kojima et al. Oct 2015 A1
20150288629 Choi et al. Oct 2015 A1
20150294086 Kare et al. Oct 2015 A1
20150294377 Chow Oct 2015 A1
20150294516 Chiang Oct 2015 A1
20150294670 Roblek et al. Oct 2015 A1
20150295915 Xiu Oct 2015 A1
20150296065 Narita et al. Oct 2015 A1
20150301796 Visser et al. Oct 2015 A1
20150302316 Buryak et al. Oct 2015 A1
20150302855 Kim et al. Oct 2015 A1
20150302856 Kim et al. Oct 2015 A1
20150302857 Yamada Oct 2015 A1
20150302870 Burke et al. Oct 2015 A1
20150308470 Graham et al. Oct 2015 A1
20150309691 Seo et al. Oct 2015 A1
20150309997 Lee et al. Oct 2015 A1
20150310114 Ryger et al. Oct 2015 A1
20150310858 Li et al. Oct 2015 A1
20150310862 Dauphin et al. Oct 2015 A1
20150310879 Buchanan et al. Oct 2015 A1
20150310888 Chen Oct 2015 A1
20150312182 Langholz Oct 2015 A1
20150312409 Czarnecki et al. Oct 2015 A1
20150314454 Breazeal et al. Nov 2015 A1
20150317069 Clements et al. Nov 2015 A1
20150317310 Eiche et al. Nov 2015 A1
20150319264 Allen et al. Nov 2015 A1
20150319411 Kasmir et al. Nov 2015 A1
20150324041 Varley et al. Nov 2015 A1
20150324334 Lee et al. Nov 2015 A1
20150324362 Glass et al. Nov 2015 A1
20150331664 Osawa et al. Nov 2015 A1
20150331711 Huang et al. Nov 2015 A1
20150332667 Mason Nov 2015 A1
20150334346 Cheatham, III et al. Nov 2015 A1
20150339049 Kasemset et al. Nov 2015 A1
20150339391 Kang et al. Nov 2015 A1
20150340033 Di Fabbrizio et al. Nov 2015 A1
20150340034 Schalkwyk et al. Nov 2015 A1
20150340040 Mun et al. Nov 2015 A1
20150340042 Sejnoha et al. Nov 2015 A1
20150341717 Song et al. Nov 2015 A1
20150346845 Di Censo et al. Dec 2015 A1
20150347086 Liedholm et al. Dec 2015 A1
20150347381 Bellegarda Dec 2015 A1
20150347382 Dolfing et al. Dec 2015 A1
20150347383 Willmore et al. Dec 2015 A1
20150347385 Flor et al. Dec 2015 A1
20150347393 Futrell et al. Dec 2015 A1
20150347552 Habouzit et al. Dec 2015 A1
20150347733 Tsou et al. Dec 2015 A1
20150347985 Gross et al. Dec 2015 A1
20150348533 Saddler et al. Dec 2015 A1
20150348547 Paulik et al. Dec 2015 A1
20150348548 Piernot et al. Dec 2015 A1
20150348549 Giuli et al. Dec 2015 A1
20150348551 Gruber et al. Dec 2015 A1
20150348554 Orr et al. Dec 2015 A1
20150348555 Sugita Dec 2015 A1
20150348565 Rhoten et al. Dec 2015 A1
20150349934 Pollack et al. Dec 2015 A1
20150350031 Burks et al. Dec 2015 A1
20150350342 Thorpe et al. Dec 2015 A1
20150350594 Mate et al. Dec 2015 A1
20150352999 Bando et al. Dec 2015 A1
20150355879 Beckhardt et al. Dec 2015 A1
20150356410 Faith et al. Dec 2015 A1
20150363587 Ahn et al. Dec 2015 A1
20150364128 Zhao et al. Dec 2015 A1
20150364140 Thörn Dec 2015 A1
20150365251 Kinoshita et al. Dec 2015 A1
20150370531 Faaborg Dec 2015 A1
20150370780 Wang et al. Dec 2015 A1
20150370787 Akbacak et al. Dec 2015 A1
20150370884 Hurley et al. Dec 2015 A1
20150371215 Zhou et al. Dec 2015 A1
20150371529 Dolecki Dec 2015 A1
20150371639 Foerster et al. Dec 2015 A1
20150371663 Gustafson et al. Dec 2015 A1
20150371664 Bar-or et al. Dec 2015 A1
20150371665 Naik et al. Dec 2015 A1
20150373183 Woolsey et al. Dec 2015 A1
20150379118 Wickenkamp et al. Dec 2015 A1
20150379414 Yeh et al. Dec 2015 A1
20150379993 Subhojit et al. Dec 2015 A1
20150381923 Wickenkamp et al. Dec 2015 A1
20150382047 Van Os et al. Dec 2015 A1
20150382079 Lister et al. Dec 2015 A1
20150382147 Clark et al. Dec 2015 A1
20160004499 Kim et al. Jan 2016 A1
20160004690 Bangalore et al. Jan 2016 A1
20160005320 deCharms et al. Jan 2016 A1
20160006795 Yunten Jan 2016 A1
20160012038 Edwards et al. Jan 2016 A1
20160014476 Caliendo, Jr. et al. Jan 2016 A1
20160018872 Tu et al. Jan 2016 A1
20160018900 Tu et al. Jan 2016 A1
20160018959 Yamashita et al. Jan 2016 A1
20160019886 Hong Jan 2016 A1
20160019896 Alvarez Guevara et al. Jan 2016 A1
20160021414 Padi et al. Jan 2016 A1
20160026242 Burns et al. Jan 2016 A1
20160026258 Ou et al. Jan 2016 A1
20160027431 Kurzweil et al. Jan 2016 A1
20160028666 Li Jan 2016 A1
20160028802 Balasingh et al. Jan 2016 A1
20160029316 Mohan et al. Jan 2016 A1
20160034042 Joo Feb 2016 A1
20160034811 Paulik et al. Feb 2016 A1
20160036750 Yuan et al. Feb 2016 A1
20160036953 Lee et al. Feb 2016 A1
20160041809 Clayton et al. Feb 2016 A1
20160042735 Vibbert et al. Feb 2016 A1
20160042748 Jain et al. Feb 2016 A1
20160043905 Fiedler Feb 2016 A1
20160048666 Dey et al. Feb 2016 A1
20160050254 Rao et al. Feb 2016 A1
20160055422 Li Feb 2016 A1
20160061623 Pahwa et al. Mar 2016 A1
20160062459 Publicover et al. Mar 2016 A1
20160062605 Agarwal et al. Mar 2016 A1
20160063094 Udupa et al. Mar 2016 A1
20160063095 Nassar et al. Mar 2016 A1
20160063998 Krishnamoorthy et al. Mar 2016 A1
20160065155 Bharj et al. Mar 2016 A1
20160065626 Jain et al. Mar 2016 A1
20160066020 Mountain Mar 2016 A1
20160070581 Soon-Shiong Mar 2016 A1
20160071516 Lee et al. Mar 2016 A1
20160071517 Beaver et al. Mar 2016 A1
20160071521 Haughay Mar 2016 A1
20160072940 Cronin Mar 2016 A1
20160077794 Kim et al. Mar 2016 A1
20160078359 Csurka et al. Mar 2016 A1
20160078860 Paulik et al. Mar 2016 A1
20160080165 Ehsani et al. Mar 2016 A1
20160080475 Singh et al. Mar 2016 A1
20160085295 Shimy et al. Mar 2016 A1
20160085827 Chadha et al. Mar 2016 A1
20160086116 Rao et al. Mar 2016 A1
20160086599 Kurata et al. Mar 2016 A1
20160088335 Zucchetta Mar 2016 A1
20160091871 Marti et al. Mar 2016 A1
20160091967 Prokofieva et al. Mar 2016 A1
20160092046 Hong et al. Mar 2016 A1
20160092434 Bellegarda Mar 2016 A1
20160092447 Pathurudeen et al. Mar 2016 A1
20160092766 Sainath et al. Mar 2016 A1
20160093291 Kim Mar 2016 A1
20160093298 Naik et al. Mar 2016 A1
20160093301 Bellegarda et al. Mar 2016 A1
20160093304 Kim et al. Mar 2016 A1
20160094700 Lee et al. Mar 2016 A1
20160094889 Venkataraman et al. Mar 2016 A1
20160094979 Naik et al. Mar 2016 A1
20160098991 Luo et al. Apr 2016 A1
20160098992 Renard et al. Apr 2016 A1
20160099892 Palakovich et al. Apr 2016 A1
20160099984 Karagiannis et al. Apr 2016 A1
20160104480 Sharifi Apr 2016 A1
20160104486 Penilla et al. Apr 2016 A1
20160111091 Bakish Apr 2016 A1
20160112746 Zhang et al. Apr 2016 A1
20160112792 Lee et al. Apr 2016 A1
20160117386 Ajmera et al. Apr 2016 A1
20160118048 Heide Apr 2016 A1
20160119338 Cheyer Apr 2016 A1
20160125048 Hamada May 2016 A1
20160125071 Gabbai May 2016 A1
20160132046 Beoughter et al. May 2016 A1
20160132290 Raux May 2016 A1
20160132484 Nauze et al. May 2016 A1
20160132488 Clark et al. May 2016 A1
20160133254 Vogel et al. May 2016 A1
20160139662 Dabhade May 2016 A1
20160140951 Agiomyrgiannakis et al. May 2016 A1
20160140962 Sharifi May 2016 A1
20160147725 Patten et al. May 2016 A1
20160148610 Kennewick, Jr. et al. May 2016 A1
20160148612 Guo et al. May 2016 A1
20160149966 Remash et al. May 2016 A1
20160150020 Farmer et al. May 2016 A1
20160151668 Barnes et al. Jun 2016 A1
20160154624 Son et al. Jun 2016 A1
20160154880 Hoarty Jun 2016 A1
20160155442 Kannan et al. Jun 2016 A1
20160155443 Khan et al. Jun 2016 A1
20160156574 Hum et al. Jun 2016 A1
20160162456 Munro et al. Jun 2016 A1
20160163311 Crook et al. Jun 2016 A1
20160163312 Naik et al. Jun 2016 A1
20160170710 Kim et al. Jun 2016 A1
20160170966 Kolo Jun 2016 A1
20160171980 Liddell et al. Jun 2016 A1
20160173578 Sharma et al. Jun 2016 A1
20160173617 Allinson Jun 2016 A1
20160173960 Snibbe et al. Jun 2016 A1
20160179462 Bjorkengren Jun 2016 A1
20160179464 Reddy et al. Jun 2016 A1
20160179787 Deleeuw Jun 2016 A1
20160180840 Siddiq et al. Jun 2016 A1
20160180844 Vanblon et al. Jun 2016 A1
20160182410 Janakiraman et al. Jun 2016 A1
20160182709 Kim et al. Jun 2016 A1
20160188181 Smith Jun 2016 A1
20160188738 Gruber et al. Jun 2016 A1
20160189198 Daniel et al. Jun 2016 A1
20160189715 Nishikawa Jun 2016 A1
20160189717 Kannan et al. Jun 2016 A1
20160196110 Yehoshua et al. Jul 2016 A1
20160198319 Huang et al. Jul 2016 A1
20160203002 Kannan et al. Jul 2016 A1
20160203193 Kevin et al. Jul 2016 A1
20160210551 Lee et al. Jul 2016 A1
20160210981 Lee Jul 2016 A1
20160212206 Wu et al. Jul 2016 A1
20160212208 Kulkarni et al. Jul 2016 A1
20160212488 Os et al. Jul 2016 A1
20160217784 Gelfenbeyn et al. Jul 2016 A1
20160217794 Imoto et al. Jul 2016 A1
20160224540 Stewart et al. Aug 2016 A1
20160224559 Hicks et al. Aug 2016 A1
20160224774 Pender Aug 2016 A1
20160225372 Cheung et al. Aug 2016 A1
20160227107 Beaumont Aug 2016 A1
20160227633 Sun et al. Aug 2016 A1
20160232500 Wang et al. Aug 2016 A1
20160239568 Packer et al. Aug 2016 A1
20160239645 Heo et al. Aug 2016 A1
20160239848 Chang et al. Aug 2016 A1
20160240187 Fleizach et al. Aug 2016 A1
20160240189 Lee et al. Aug 2016 A1
20160240192 Raghuvir Aug 2016 A1
20160247061 Trask et al. Aug 2016 A1
20160249319 Dotan-Cohen et al. Aug 2016 A1
20160253312 Rhodes Sep 2016 A1
20160253528 Gao et al. Sep 2016 A1
20160259623 Sumner et al. Sep 2016 A1
20160259656 Sumner et al. Sep 2016 A1
20160259779 Labskýet al. Sep 2016 A1
20160260431 Newendorp et al. Sep 2016 A1
20160260433 Sumner et al. Sep 2016 A1
20160260434 Gelfenbeyn et al. Sep 2016 A1
20160260436 Lemay et al. Sep 2016 A1
20160262442 Davila et al. Sep 2016 A1
20160266871 Schmid et al. Sep 2016 A1
20160267904 Biadsy et al. Sep 2016 A1
20160269540 Butcher et al. Sep 2016 A1
20160274938 Strinati et al. Sep 2016 A1
20160275941 Bellegarda et al. Sep 2016 A1
20160275947 Li et al. Sep 2016 A1
20160282824 Smallwood et al. Sep 2016 A1
20160282956 Ouyang et al. Sep 2016 A1
20160283185 Mclaren et al. Sep 2016 A1
20160284005 Daniel et al. Sep 2016 A1
20160284199 Dotan-Cohen et al. Sep 2016 A1
20160285808 Franklin et al. Sep 2016 A1
20160286045 Shaltiel et al. Sep 2016 A1
20160293157 Chen et al. Oct 2016 A1
20160293167 Chen et al. Oct 2016 A1
20160293168 Chen Oct 2016 A1
20160294755 Prabhu Oct 2016 A1
20160299685 Zhai et al. Oct 2016 A1
20160299882 Hegerty et al. Oct 2016 A1
20160299883 Zhu et al. Oct 2016 A1
20160299977 Hreha Oct 2016 A1
20160300571 Foerster et al. Oct 2016 A1
20160301639 Liu et al. Oct 2016 A1
20160306683 Standley et al. Oct 2016 A1
20160307566 Bellegarda Oct 2016 A1
20160308799 Schubert et al. Oct 2016 A1
20160309035 Li Oct 2016 A1
20160313906 Kilchenko et al. Oct 2016 A1
20160314788 Jitkoff et al. Oct 2016 A1
20160314789 Marcheret et al. Oct 2016 A1
20160314792 Alvarez et al. Oct 2016 A1
20160315996 Ha et al. Oct 2016 A1
20160316349 Lee et al. Oct 2016 A1
20160317924 Tanaka et al. Nov 2016 A1
20160321239 Iso-Sipilä et al. Nov 2016 A1
20160321261 Spasojevic et al. Nov 2016 A1
20160321358 Kanani et al. Nov 2016 A1
20160322043 Bellegarda Nov 2016 A1
20160322044 Jung et al. Nov 2016 A1
20160322045 Hatfield et al. Nov 2016 A1
20160322048 Amano et al. Nov 2016 A1
20160322050 Wang et al. Nov 2016 A1
20160322055 Sainath et al. Nov 2016 A1
20160328147 Zhang et al. Nov 2016 A1
20160328205 Agrawal et al. Nov 2016 A1
20160328893 Cordova et al. Nov 2016 A1
20160329060 Ito et al. Nov 2016 A1
20160334973 Reckhow et al. Nov 2016 A1
20160335138 Surti et al. Nov 2016 A1
20160335139 Hurley et al. Nov 2016 A1
20160335532 Sanghavi et al. Nov 2016 A1
20160336007 Hanazawa et al. Nov 2016 A1
20160336010 Lindahl Nov 2016 A1
20160336011 Koll et al. Nov 2016 A1
20160336024 Choi et al. Nov 2016 A1
20160337299 Lane et al. Nov 2016 A1
20160337301 Rollins et al. Nov 2016 A1
20160342317 Lim et al. Nov 2016 A1
20160342685 Basu et al. Nov 2016 A1
20160342781 Jeon Nov 2016 A1
20160350650 Leeman-Munk et al. Dec 2016 A1
20160350812 Priness et al. Dec 2016 A1
20160351190 Piernot et al. Dec 2016 A1
20160352567 Robbins et al. Dec 2016 A1
20160352924 Senarath et al. Dec 2016 A1
20160357304 Hatori et al. Dec 2016 A1
20160357728 Bellegarda et al. Dec 2016 A1
20160357790 Elkington et al. Dec 2016 A1
20160357861 Carlhian et al. Dec 2016 A1
20160357870 Hentschel et al. Dec 2016 A1
20160358598 Williams et al. Dec 2016 A1
20160358600 Nallasamy et al. Dec 2016 A1
20160358619 Ramprashad et al. Dec 2016 A1
20160359771 Sridhar Dec 2016 A1
20160360039 Sanghavi et al. Dec 2016 A1
20160360336 Gross et al. Dec 2016 A1
20160360382 Gross et al. Dec 2016 A1
20160364378 Futrell et al. Dec 2016 A1
20160365101 Foy et al. Dec 2016 A1
20160371250 Rhodes Dec 2016 A1
20160372112 Miller et al. Dec 2016 A1
20160372119 Sak et al. Dec 2016 A1
20160378747 Orr et al. Dec 2016 A1
20160379091 Lin et al. Dec 2016 A1
20160379626 Deisher et al. Dec 2016 A1
20160379632 Hoffmeister et al. Dec 2016 A1
20160379633 Lehman et al. Dec 2016 A1
20160379639 Weinstein et al. Dec 2016 A1
20160379641 Liu et al. Dec 2016 A1
20170000348 Karsten et al. Jan 2017 A1
20170003931 Dvortsov et al. Jan 2017 A1
20170004209 Johl et al. Jan 2017 A1
20170004824 Yoo et al. Jan 2017 A1
20170005818 Gould Jan 2017 A1
20170006329 Jang et al. Jan 2017 A1
20170011091 Chehreghani Jan 2017 A1
20170011279 Soldevila et al. Jan 2017 A1
20170011303 Annapureddy et al. Jan 2017 A1
20170011742 Jing et al. Jan 2017 A1
20170013124 Havelka et al. Jan 2017 A1
20170013331 Watanabe et al. Jan 2017 A1
20170018271 Khan et al. Jan 2017 A1
20170019987 Dragone et al. Jan 2017 A1
20170023963 Davis et al. Jan 2017 A1
20170025124 Mixter et al. Jan 2017 A1
20170026318 Daniel et al. Jan 2017 A1
20170026509 Rand Jan 2017 A1
20170027522 Van Hasselt et al. Feb 2017 A1
20170031576 Saoji et al. Feb 2017 A1
20170032783 Lord et al. Feb 2017 A1
20170032787 Dayal Feb 2017 A1
20170032791 Elson et al. Feb 2017 A1
20170039283 Bennett et al. Feb 2017 A1
20170039475 Cheyer et al. Feb 2017 A1
20170040002 Basson et al. Feb 2017 A1
20170041388 Tal et al. Feb 2017 A1
20170047063 Ohmura et al. Feb 2017 A1
20170052760 Johnson et al. Feb 2017 A1
20170053652 Choi et al. Feb 2017 A1
20170055895 Jardins et al. Mar 2017 A1
20170060853 Lee et al. Mar 2017 A1
20170061423 Bryant et al. Mar 2017 A1
20170068423 Napolitano et al. Mar 2017 A1
20170068513 Stasior et al. Mar 2017 A1
20170068550 Zeitlin Mar 2017 A1
20170068670 Orr et al. Mar 2017 A1
20170069308 Aleksic et al. Mar 2017 A1
20170069321 Toiyama Mar 2017 A1
20170075653 Dawidowsky et al. Mar 2017 A1
20170076518 Patterson et al. Mar 2017 A1
20170076720 Gopalan et al. Mar 2017 A1
20170076721 Bargetzi et al. Mar 2017 A1
20170078490 Kaminsky et al. Mar 2017 A1
20170083179 Gruber et al. Mar 2017 A1
20170083285 Meyers et al. Mar 2017 A1
20170083504 Huang Mar 2017 A1
20170084277 Sharifi Mar 2017 A1
20170085547 De Aguiar et al. Mar 2017 A1
20170085696 Abkairov Mar 2017 A1
20170090428 Oohara Mar 2017 A1
20170090569 Levesque Mar 2017 A1
20170091168 Bellegarda et al. Mar 2017 A1
20170091169 Bellegarda et al. Mar 2017 A1
20170091612 Gruber et al. Mar 2017 A1
20170092259 Jeon Mar 2017 A1
20170092270 Newendorp et al. Mar 2017 A1
20170092278 Evermann et al. Mar 2017 A1
20170093356 Cudak et al. Mar 2017 A1
20170097743 Hameed et al. Apr 2017 A1
20170102837 Toumpelis Apr 2017 A1
20170102915 Kuscher et al. Apr 2017 A1
20170103749 Zhao et al. Apr 2017 A1
20170103752 Senior et al. Apr 2017 A1
20170105190 Logan et al. Apr 2017 A1
20170110117 Chakladar et al. Apr 2017 A1
20170110125 Xu et al. Apr 2017 A1
20170116177 Walia Apr 2017 A1
20170116982 Gelfenbeyn et al. Apr 2017 A1
20170116987 Kang et al. Apr 2017 A1
20170116989 Yadgar et al. Apr 2017 A1
20170124190 Wang et al. May 2017 A1
20170124311 Li et al. May 2017 A1
20170124531 McCormack May 2017 A1
20170125016 Wang May 2017 A1
20170127124 Wilson et al. May 2017 A9
20170131778 Iyer May 2017 A1
20170132019 Karashchuk et al. May 2017 A1
20170132199 Vescovi et al. May 2017 A1
20170133007 Drewes May 2017 A1
20170140041 Dotan-Cohen et al. May 2017 A1
20170140052 Bufe, III et al. May 2017 A1
20170140644 Hwang et al. May 2017 A1
20170140760 Sachdev May 2017 A1
20170147722 Greenwood May 2017 A1
20170147841 Stagg et al. May 2017 A1
20170148044 Fukuda et al. May 2017 A1
20170154033 Lee Jun 2017 A1
20170154055 Dimson et al. Jun 2017 A1
20170154628 Mohajer et al. Jun 2017 A1
20170155940 Jin et al. Jun 2017 A1
20170155965 Ward Jun 2017 A1
20170161018 Lemay et al. Jun 2017 A1
20170161268 Badaskar Jun 2017 A1
20170161293 Ionescu et al. Jun 2017 A1
20170161393 Oh et al. Jun 2017 A1
20170161500 Yang Jun 2017 A1
20170162191 Grost et al. Jun 2017 A1
20170162202 Anthony et al. Jun 2017 A1
20170162203 Huang et al. Jun 2017 A1
20170169506 Wishne et al. Jun 2017 A1
20170169818 Vanblon et al. Jun 2017 A1
20170169819 Mese et al. Jun 2017 A1
20170177080 Deleeuw Jun 2017 A1
20170177547 Ciereszko et al. Jun 2017 A1
20170178619 Naik et al. Jun 2017 A1
20170178620 Fleizach et al. Jun 2017 A1
20170178626 Gruber et al. Jun 2017 A1
20170178666 Yu Jun 2017 A1
20170180499 Gelfenbeyn et al. Jun 2017 A1
20170185375 Martel et al. Jun 2017 A1
20170185581 Bojja et al. Jun 2017 A1
20170186429 Giuli et al. Jun 2017 A1
20170187711 Joo et al. Jun 2017 A1
20170193083 Bhatt et al. Jul 2017 A1
20170195493 Sudarsan et al. Jul 2017 A1
20170195495 Deora et al. Jul 2017 A1
20170195636 Child et al. Jul 2017 A1
20170199870 Zheng et al. Jul 2017 A1
20170199874 Patel et al. Jul 2017 A1
20170200066 Wang et al. Jul 2017 A1
20170201609 Salmenkaita et al. Jul 2017 A1
20170201613 Engelke et al. Jul 2017 A1
20170206899 Bryant et al. Jul 2017 A1
20170215052 Koum et al. Jul 2017 A1
20170220212 Yang et al. Aug 2017 A1
20170221486 Kurata et al. Aug 2017 A1
20170223189 Meredith et al. Aug 2017 A1
20170227935 Su et al. Aug 2017 A1
20170228367 Pasupalak et al. Aug 2017 A1
20170228382 Haviv et al. Aug 2017 A1
20170229121 Taki et al. Aug 2017 A1
20170230429 Garmark et al. Aug 2017 A1
20170230497 Kim et al. Aug 2017 A1
20170230709 Van Os et al. Aug 2017 A1
20170235361 Rigazio et al. Aug 2017 A1
20170235618 Lin et al. Aug 2017 A1
20170235721 Almosallam et al. Aug 2017 A1
20170236512 Williams et al. Aug 2017 A1
20170236514 Nelson Aug 2017 A1
20170238039 Sabattini Aug 2017 A1
20170242478 Ma Aug 2017 A1
20170242653 Lang et al. Aug 2017 A1
20170242657 Jarvis et al. Aug 2017 A1
20170242840 Lu et al. Aug 2017 A1
20170243468 Dotan-Cohen et al. Aug 2017 A1
20170243576 Millington et al. Aug 2017 A1
20170243583 Raichelgauz et al. Aug 2017 A1
20170243586 Civelli et al. Aug 2017 A1
20170249309 Sarikaya Aug 2017 A1
20170256256 Wang et al. Sep 2017 A1
20170262051 Tall et al. Sep 2017 A1
20170263247 Kang et al. Sep 2017 A1
20170263248 Gruber et al. Sep 2017 A1
20170263249 Akbacak et al. Sep 2017 A1
20170263254 Dewan et al. Sep 2017 A1
20170264451 Yu et al. Sep 2017 A1
20170264711 Natarajan et al. Sep 2017 A1
20170270715 Lindsay et al. Sep 2017 A1
20170270822 Cohen Sep 2017 A1
20170270912 Levit et al. Sep 2017 A1
20170278513 Li et al. Sep 2017 A1
20170278514 Mathias et al. Sep 2017 A1
20170285915 Napolitano et al. Oct 2017 A1
20170286397 Gonzalez Oct 2017 A1
20170287472 Ogawa et al. Oct 2017 A1
20170289305 Liensberger et al. Oct 2017 A1
20170295446 Shivappa Oct 2017 A1
20170301348 Chen et al. Oct 2017 A1
20170308552 Soni et al. Oct 2017 A1
20170308609 Berkhin et al. Oct 2017 A1
20170311005 Lin Oct 2017 A1
20170316775 Le et al. Nov 2017 A1
20170316782 Haughay Nov 2017 A1
20170319123 Voss et al. Nov 2017 A1
20170323637 Naik Nov 2017 A1
20170329466 Krenkler et al. Nov 2017 A1
20170329490 Esinovskaya et al. Nov 2017 A1
20170329572 Shah et al. Nov 2017 A1
20170329630 Jann et al. Nov 2017 A1
20170330567 Van Wissen et al. Nov 2017 A1
20170336920 Chan et al. Nov 2017 A1
20170337035 Choudhary et al. Nov 2017 A1
20170337478 Sarikaya et al. Nov 2017 A1
20170345411 Raitio et al. Nov 2017 A1
20170345420 Barnett, Jr. Nov 2017 A1
20170345429 Hardee et al. Nov 2017 A1
20170346949 Sanghavi et al. Nov 2017 A1
20170347180 Petrank Nov 2017 A1
20170351487 Avilés-Casco et al. Dec 2017 A1
20170352346 Paulik et al. Dec 2017 A1
20170352350 Booker et al. Dec 2017 A1
20170357478 Piersol et al. Dec 2017 A1
20170357529 Venkatraman et al. Dec 2017 A1
20170357632 Pagallo et al. Dec 2017 A1
20170357633 Wang et al. Dec 2017 A1
20170357637 Nell et al. Dec 2017 A1
20170357640 Bellegarda et al. Dec 2017 A1
20170357716 Bellegarda et al. Dec 2017 A1
20170358300 Laurens et al. Dec 2017 A1
20170358301 Raitio et al. Dec 2017 A1
20170358302 Orr et al. Dec 2017 A1
20170358303 Walker, II et al. Dec 2017 A1
20170358304 Castillo et al. Dec 2017 A1
20170358305 Kudurshian et al. Dec 2017 A1
20170358317 James Dec 2017 A1
20170359680 Ledvina et al. Dec 2017 A1
20170365251 Park et al. Dec 2017 A1
20170371509 Jung et al. Dec 2017 A1
20170371885 Aggarwal et al. Dec 2017 A1
20170374093 Dhar et al. Dec 2017 A1
20170374176 Agrawal et al. Dec 2017 A1
20180004372 Zurek et al. Jan 2018 A1
20180004396 Ying Jan 2018 A1
20180005112 Iso-Sipila et al. Jan 2018 A1
20180007060 Leblang et al. Jan 2018 A1
20180007096 Levin et al. Jan 2018 A1
20180007538 Naik et al. Jan 2018 A1
20180012596 Piernot et al. Jan 2018 A1
20180018248 Bhargava et al. Jan 2018 A1
20180018590 Szeto et al. Jan 2018 A1
20180018814 Patrik et al. Jan 2018 A1
20180024985 Asano Jan 2018 A1
20180025124 Mohr et al. Jan 2018 A1
20180025287 Mathew et al. Jan 2018 A1
20180028918 Tang et al. Feb 2018 A1
20180033431 Newendorp et al. Feb 2018 A1
20180033435 Jacobs, II Feb 2018 A1
20180033436 Zhou Feb 2018 A1
20180045963 Hoover et al. Feb 2018 A1
20180046340 Mall Feb 2018 A1
20180047201 Filev et al. Feb 2018 A1
20180047391 Baik et al. Feb 2018 A1
20180047393 Tian et al. Feb 2018 A1
20180047406 Park Feb 2018 A1
20180052909 Sharifi et al. Feb 2018 A1
20180054505 Hart et al. Feb 2018 A1
20180060032 Boesen Mar 2018 A1
20180060301 Li et al. Mar 2018 A1
20180060312 Won Mar 2018 A1
20180060555 Boesen Mar 2018 A1
20180061400 Carbune et al. Mar 2018 A1
20180061401 Sarikaya et al. Mar 2018 A1
20180062691 Barnett, Jr. Mar 2018 A1
20180063308 Crystal et al. Mar 2018 A1
20180063324 Van Meter, II Mar 2018 A1
20180063624 Boesen Mar 2018 A1
20180067904 Li Mar 2018 A1
20180067914 Chen et al. Mar 2018 A1
20180067918 Bellegarda et al. Mar 2018 A1
20180068074 Shen Mar 2018 A1
20180069743 Bakken et al. Mar 2018 A1
20180075847 Lee et al. Mar 2018 A1
20180075849 Khoury et al. Mar 2018 A1
20180077095 Deyle et al. Mar 2018 A1
20180082692 Khoury et al. Mar 2018 A1
20180088969 Vanblon et al. Mar 2018 A1
20180089166 Meyer et al. Mar 2018 A1
20180089588 Ravi et al. Mar 2018 A1
20180090143 Saddler et al. Mar 2018 A1
20180091604 Yamashita et al. Mar 2018 A1
20180091847 Wu et al. Mar 2018 A1
20180096683 James et al. Apr 2018 A1
20180096690 Mixter et al. Apr 2018 A1
20180101599 Kenneth et al. Apr 2018 A1
20180101925 Brinig et al. Apr 2018 A1
20180102914 Kawachi et al. Apr 2018 A1
20180103209 Fischler et al. Apr 2018 A1
20180107917 Hewavitharana et al. Apr 2018 A1
20180107945 Gao et al. Apr 2018 A1
20180108346 Paulik et al. Apr 2018 A1
20180108351 Beckhardt et al. Apr 2018 A1
20180108357 Liu Apr 2018 A1
20180113673 Sheynblat Apr 2018 A1
20180314362 Kim et al. Apr 2018 A1
20180121432 Parson et al. May 2018 A1
20180122376 Kojima May 2018 A1
20180122378 Mixter et al. May 2018 A1
20180126260 Chansoriya et al. May 2018 A1
20180129967 Herreshoff May 2018 A1
20180130470 Lemay et al. May 2018 A1
20180130471 Trufinescu et al. May 2018 A1
20180137856 Gilbert May 2018 A1
20180137857 Zhou et al. May 2018 A1
20180137865 Ling May 2018 A1
20180143857 Anbazhagan et al. May 2018 A1
20180143967 Anbazhagan et al. May 2018 A1
20180144465 Hsieh et al. May 2018 A1
20180144615 Kinney et al. May 2018 A1
20180144746 Mishra et al. May 2018 A1
20180144748 Leong May 2018 A1
20180146089 Rauenbuehler et al. May 2018 A1
20180150744 Orr et al. May 2018 A1
20180152557 White et al. May 2018 A1
20180157372 Kurabayashi Jun 2018 A1
20180157408 Yu et al. Jun 2018 A1
20180157992 Susskind et al. Jun 2018 A1
20180158548 Taheri et al. Jun 2018 A1
20180158552 Liu et al. Jun 2018 A1
20180165857 Lee et al. Jun 2018 A1
20180166076 Higuchi et al. Jun 2018 A1
20180167884 Dawid et al. Jun 2018 A1
20180173403 Carbune et al. Jun 2018 A1
20180173542 Chan et al. Jun 2018 A1
20180174406 Arashi et al. Jun 2018 A1
20180174576 Soltau et al. Jun 2018 A1
20180174597 Lee et al. Jun 2018 A1
20180182376 Gysel et al. Jun 2018 A1
20180188840 Tamura et al. Jul 2018 A1
20180188948 Ouyang et al. Jul 2018 A1
20180189267 Takiel Jul 2018 A1
20180190263 Calef, III Jul 2018 A1
20180190273 Karimli et al. Jul 2018 A1
20180190279 Anderson et al. Jul 2018 A1
20180191670 Suyama Jul 2018 A1
20180196683 Radebaugh et al. Jul 2018 A1
20180205983 Lee et al. Jul 2018 A1
20180210874 Fuxman et al. Jul 2018 A1
20180213448 Segal et al. Jul 2018 A1
20180217810 Agrawal Aug 2018 A1
20180218735 Hunt et al. Aug 2018 A1
20180221783 Gamero Aug 2018 A1
20180225131 Tommy et al. Aug 2018 A1
20180225274 Tommy et al. Aug 2018 A1
20180232203 Gelfenbeyn et al. Aug 2018 A1
20180232688 Pike et al. Aug 2018 A1
20180233132 Herold et al. Aug 2018 A1
20180233140 Koishida et al. Aug 2018 A1
20180247065 Rhee et al. Aug 2018 A1
20180253209 Jaygarl et al. Sep 2018 A1
20180253652 Palzer et al. Sep 2018 A1
20180260680 Finkelstein et al. Sep 2018 A1
20180268023 Korpusik et al. Sep 2018 A1
20180268106 Velaga Sep 2018 A1
20180270343 Rout et al. Sep 2018 A1
20180275839 Kocienda et al. Sep 2018 A1
20180276197 Nell et al. Sep 2018 A1
20180277113 Hartung et al. Sep 2018 A1
20180278740 Choi et al. Sep 2018 A1
20180285056 Cutler et al. Oct 2018 A1
20180293984 Lindahl Oct 2018 A1
20180293988 Huang et al. Oct 2018 A1
20180293989 De et al. Oct 2018 A1
20180299878 Cella et al. Oct 2018 A1
20180300317 Bradbury Oct 2018 A1
20180300400 Paulus Oct 2018 A1
20180300608 Sevrens et al. Oct 2018 A1
20180300952 Evans et al. Oct 2018 A1
20180307216 Ypma et al. Oct 2018 A1
20180308470 Park et al. Oct 2018 A1
20180308477 Nagasaka Oct 2018 A1
20180308480 Jang et al. Oct 2018 A1
20180308485 Kudurshian et al. Oct 2018 A1
20180308486 Saddler et al. Oct 2018 A1
20180314552 Kim et al. Nov 2018 A1
20180314689 Wang et al. Nov 2018 A1
20180315415 Mosley et al. Nov 2018 A1
20180315416 Berthelsen et al. Nov 2018 A1
20180322112 Bellegarda et al. Nov 2018 A1
20180322881 Min et al. Nov 2018 A1
20180324518 Dusan et al. Nov 2018 A1
20180329508 Klein et al. Nov 2018 A1
20180329677 Gruber et al. Nov 2018 A1
20180329957 Frazzingaro et al. Nov 2018 A1
20180329982 Patel et al. Nov 2018 A1
20180329998 Thomson et al. Nov 2018 A1
20180330714 Paulik et al. Nov 2018 A1
20180330721 Thomson et al. Nov 2018 A1
20180330722 Newendorp et al. Nov 2018 A1
20180330723 Acero et al. Nov 2018 A1
20180330729 Golipour et al. Nov 2018 A1
20180330730 Garg et al. Nov 2018 A1
20180330731 Zeitlin et al. Nov 2018 A1
20180330733 Orr et al. Nov 2018 A1
20180330737 Paulik et al. Nov 2018 A1
20180332118 Phipps et al. Nov 2018 A1
20180332389 Ekkizogloy et al. Nov 2018 A1
20180335903 Coffman et al. Nov 2018 A1
20180336049 Mukherjee et al. Nov 2018 A1
20180336184 Bellegarda et al. Nov 2018 A1
20180336197 Skilling et al. Nov 2018 A1
20180336275 Graham et al. Nov 2018 A1
20180336439 Kliger et al. Nov 2018 A1
20180336449 Adan et al. Nov 2018 A1
20180336880 Arik et al. Nov 2018 A1
20180336885 Mukherjee et al. Nov 2018 A1
20180336892 Kim et al. Nov 2018 A1
20180336894 Graham et al. Nov 2018 A1
20180336904 Piercy et al. Nov 2018 A1
20180336905 Kim et al. Nov 2018 A1
20180336911 Dahl et al. Nov 2018 A1
20180336920 Bastian et al. Nov 2018 A1
20180338191 Van Scheltinga et al. Nov 2018 A1
20180341643 Alders et al. Nov 2018 A1
20180343557 Naik et al. Nov 2018 A1
20180349084 Nagasaka et al. Dec 2018 A1
20180349346 Hatori et al. Dec 2018 A1
20180349349 Bellegarda et al. Dec 2018 A1
20180349447 Maccartney et al. Dec 2018 A1
20180349472 Kohlschuetter et al. Dec 2018 A1
20180349728 Wang et al. Dec 2018 A1
20180350345 Naik Dec 2018 A1
20180350353 Gruber et al. Dec 2018 A1
20180357073 Johnson et al. Dec 2018 A1
20180357308 Cheyer Dec 2018 A1
20180358015 Cash et al. Dec 2018 A1
20180358019 Mont-Reynaud Dec 2018 A1
20180365653 Cleaver et al. Dec 2018 A1
20180366105 Kim Dec 2018 A1
20180366116 Nicholson et al. Dec 2018 A1
20180373487 Gruber et al. Dec 2018 A1
20180373493 Watson et al. Dec 2018 A1
20180373796 Rathod Dec 2018 A1
20180374484 Huang et al. Dec 2018 A1
20190005024 Somech et al. Jan 2019 A1
20190012141 Piersol et al. Jan 2019 A1
20190012445 Lesso et al. Jan 2019 A1
20190012449 Cheyer Jan 2019 A1
20190012599 El Kaliouby et al. Jan 2019 A1
20190013018 Rekstad Jan 2019 A1
20190013025 Alcorn et al. Jan 2019 A1
20190014450 Gruber et al. Jan 2019 A1
20190019077 Griffin et al. Jan 2019 A1
20190027152 Huang et al. Jan 2019 A1
20190034040 Shah et al. Jan 2019 A1
20190034826 Ahmad et al. Jan 2019 A1
20190035385 Lawson et al. Jan 2019 A1
20190035405 Haughay Jan 2019 A1
20190037258 Justin et al. Jan 2019 A1
20190042059 Baer Feb 2019 A1
20190042627 Osotio et al. Feb 2019 A1
20190043507 Huang et al. Feb 2019 A1
20190044854 Yang et al. Feb 2019 A1
20190045040 Lee et al. Feb 2019 A1
20190051306 Torama et al. Feb 2019 A1
20190051309 Kim et al. Feb 2019 A1
20190057697 Giuli et al. Feb 2019 A1
20190065144 Sumner et al. Feb 2019 A1
20190065993 Srinivasan et al. Feb 2019 A1
20190066674 Jaygarl et al. Feb 2019 A1
20190068810 Okamoto et al. Feb 2019 A1
20190173996 Butcher et al. Feb 2019 A1
20190073607 Jia et al. Mar 2019 A1
20190073998 Leblang et al. Mar 2019 A1
20190074009 Kim et al. Mar 2019 A1
20190074015 Orr et al. Mar 2019 A1
20190074016 Orr et al. Mar 2019 A1
20190079476 Funes Mar 2019 A1
20190080685 Johnson, Jr. Mar 2019 A1
20190080698 Miller Mar 2019 A1
20190082044 Olivia et al. Mar 2019 A1
20190087412 Seyed Ibrahim et al. Mar 2019 A1
20190087455 He et al. Mar 2019 A1
20190095050 Gruber et al. Mar 2019 A1
20190095069 Proctor et al. Mar 2019 A1
20190095171 Carson et al. Mar 2019 A1
20190102145 Wilberding et al. Apr 2019 A1
20190102378 Piernot et al. Apr 2019 A1
20190102381 Futrell et al. Apr 2019 A1
20190103103 Ni et al. Apr 2019 A1
20190103112 Walker et al. Apr 2019 A1
20190116264 Sanghavi et al. Apr 2019 A1
20190122666 Raitio et al. Apr 2019 A1
20190122692 Binder et al. Apr 2019 A1
20190124019 Leon et al. Apr 2019 A1
20190129499 Li May 2019 A1
20190129615 Sundar et al. May 2019 A1
20190132694 Hanes et al. May 2019 A1
20190134501 Feder et al. May 2019 A1
20190138704 Shrivastava et al. May 2019 A1
20190139541 Andersen et al. May 2019 A1
20190139563 Chen et al. May 2019 A1
20190141494 Gross et al. May 2019 A1
20190147052 Lu et al. May 2019 A1
20190147369 Gupta et al. May 2019 A1
20190147880 Booker et al. May 2019 A1
20190147883 Mellenthin et al. May 2019 A1
20190149972 Parks et al. May 2019 A1
20190156830 Devaraj et al. May 2019 A1
20190158994 Gross et al. May 2019 A1
20190163667 Feuz et al. May 2019 A1
20190164546 Piernot et al. May 2019 A1
20190172243 Mishra et al. Jun 2019 A1
20190172467 Kim et al. Jun 2019 A1
20190179607 Thangarathnam et al. Jun 2019 A1
20190179890 Evermann Jun 2019 A1
20190180770 Kothari et al. Jun 2019 A1
20190182176 Niewczas Jun 2019 A1
20190187787 White et al. Jun 2019 A1
20190188326 Daianu et al. Jun 2019 A1
20190188328 Oyenan et al. Jun 2019 A1
20190189118 Piernot et al. Jun 2019 A1
20190189125 Van Os et al. Jun 2019 A1
20190190898 Cui Jun 2019 A1
20190197053 Graham et al. Jun 2019 A1
20190213601 Hackman et al. Jul 2019 A1
20190213774 Jiao et al. Jul 2019 A1
20190213999 Grupen et al. Jul 2019 A1
20190214024 Gruber et al. Jul 2019 A1
20190220245 Martel et al. Jul 2019 A1
20190220246 Orr et al. Jul 2019 A1
20190220247 Lemay et al. Jul 2019 A1
20190220704 Schulz-Trieglaff et al. Jul 2019 A1
20190220727 Dohrmann et al. Jul 2019 A1
20190222684 Li et al. Jul 2019 A1
20190224049 Creasy et al. Jul 2019 A1
20190230215 Zhu et al. Jul 2019 A1
20190230426 Chun Jul 2019 A1
20190236130 Li et al. Aug 2019 A1
20190236459 Cheyer et al. Aug 2019 A1
20190244618 Newendorp et al. Aug 2019 A1
20190251167 Krishnapura Subbaraya et al. Aug 2019 A1
20190251339 Hawker Aug 2019 A1
20190251960 Maker et al. Aug 2019 A1
20190259386 Kudurshian et al. Aug 2019 A1
20190272818 Fernandez et al. Sep 2019 A1
20190272825 O'Malley et al. Sep 2019 A1
20190272831 Kajarekar Sep 2019 A1
20190273963 Jobanputra et al. Sep 2019 A1
20190278841 Pusateri et al. Sep 2019 A1
20190287012 Asli et al. Sep 2019 A1
20190287522 Lambourne et al. Sep 2019 A1
20190294769 Lesso Sep 2019 A1
20190295529 Tomita Sep 2019 A1
20190295540 Grima Sep 2019 A1
20190295544 Garcia et al. Sep 2019 A1
20190303442 Peitz et al. Oct 2019 A1
20190304438 Qian et al. Oct 2019 A1
20190310765 Napolitano et al. Oct 2019 A1
20190311708 Bengio et al. Oct 2019 A1
20190311720 Pasko Oct 2019 A1
20190318722 Bromand Oct 2019 A1
20190318724 Chao et al. Oct 2019 A1
20190318725 Le Roux et al. Oct 2019 A1
20190318732 Huang et al. Oct 2019 A1
20190318735 Chao et al. Oct 2019 A1
20190318739 Garg et al. Oct 2019 A1
20190339784 Lemay et al. Nov 2019 A1
20190341027 Vescovi et al. Nov 2019 A1
20190341056 Paulik et al. Nov 2019 A1
20190347063 Liu et al. Nov 2019 A1
20190348022 Park et al. Nov 2019 A1
20190354548 Orr et al. Nov 2019 A1
20190355346 Bellegarda Nov 2019 A1
20190355384 Sereshki et al. Nov 2019 A1
20190361729 Gruber et al. Nov 2019 A1
20190369748 Hindi et al. Dec 2019 A1
20190369842 Dolbakian et al. Dec 2019 A1
20190369868 Jin et al. Dec 2019 A1
20190370292 Irani et al. Dec 2019 A1
20190370323 Davidson et al. Dec 2019 A1
20190370443 Lesso Dec 2019 A1
20190371315 Newendorp et al. Dec 2019 A1
20190371316 Weinstein et al. Dec 2019 A1
20190371317 Irani et al. Dec 2019 A1
20190371331 Schramm et al. Dec 2019 A1
20190372902 Piersol Dec 2019 A1
20190373102 Weinstein et al. Dec 2019 A1
20190385418 Mixter et al. Dec 2019 A1
20190387352 Jot et al. Dec 2019 A1
20200019609 Yu et al. Jan 2020 A1
20200020326 Srinivasan et al. Jan 2020 A1
20200035224 Ward et al. Jan 2020 A1
20200042334 Radebaugh et al. Feb 2020 A1
20200043467 Qian et al. Feb 2020 A1
20200043471 Ma et al. Feb 2020 A1
20200043482 Gruber et al. Feb 2020 A1
20200043489 Bradley et al. Feb 2020 A1
20200044485 Smith et al. Feb 2020 A1
20200051565 Singh Feb 2020 A1
20200051583 Wu et al. Feb 2020 A1
20200053218 Gray Feb 2020 A1
20200058299 Lee et al. Feb 2020 A1
20200065601 Andreassen Feb 2020 A1
20200073629 Lee et al. Mar 2020 A1
20200075018 Chen Mar 2020 A1
20200075040 Provost et al. Mar 2020 A1
20200076538 Soultan et al. Mar 2020 A1
20200081615 Lu et al. Mar 2020 A1
20200090393 Shin et al. Mar 2020 A1
20200091958 Curtis et al. Mar 2020 A1
20200092625 Raffle Mar 2020 A1
20200098352 Feinstein et al. Mar 2020 A1
20200098362 Piernot et al. Mar 2020 A1
20200098368 Lemay et al. Mar 2020 A1
20200104357 Bellegarda et al. Apr 2020 A1
20200104362 Yang et al. Apr 2020 A1
20200104369 Bellegarda Apr 2020 A1
20200104668 Sanghavi et al. Apr 2020 A1
20200105260 Piernot et al. Apr 2020 A1
20200117717 Ramamurti et al. Apr 2020 A1
20200118566 Zhou Apr 2020 A1
20200118568 Kudurshian et al. Apr 2020 A1
20200125820 Kim et al. Apr 2020 A1
20200127988 Bradley et al. Apr 2020 A1
20200134316 Krishnamurthy et al. Apr 2020 A1
20200135180 Mukherjee et al. Apr 2020 A1
20200135209 Delfarah et al. Apr 2020 A1
20200135226 Mittal et al. Apr 2020 A1
20200137230 Spohrer Apr 2020 A1
20200143812 Walker et al. May 2020 A1
20200143819 Delcroix et al. May 2020 A1
20200152186 Koh et al. May 2020 A1
20200159579 Shear et al. May 2020 A1
20200159651 Myers May 2020 A1
20200160179 Chien et al. May 2020 A1
20200169637 Sanghavi et al. May 2020 A1
20200175566 Bender et al. Jun 2020 A1
20200176004 Kleijn et al. Jun 2020 A1
20200176018 Feinauer et al. Jun 2020 A1
20200184057 Mukund Jun 2020 A1
20200184964 Myers et al. Jun 2020 A1
20200184966 Yavagal Jun 2020 A1
20200193997 Piernot et al. Jun 2020 A1
20200210142 Mu et al. Jul 2020 A1
20200218780 Jun et al. Jul 2020 A1
20200219517 Wang et al. Jul 2020 A1
20200221155 Hansen et al. Jul 2020 A1
20200227034 Summa et al. Jul 2020 A1
20200227044 Lindahl Jul 2020 A1
20200243069 Amores et al. Jul 2020 A1
20200249985 Zeitlin Aug 2020 A1
20200252508 Gray Aug 2020 A1
20200258508 Aggarwal et al. Aug 2020 A1
20200267222 Phipps et al. Aug 2020 A1
20200272485 Karashchuk et al. Aug 2020 A1
20200279556 Gruber et al. Sep 2020 A1
20200279576 Binder et al. Sep 2020 A1
20200279627 Nida et al. Sep 2020 A1
20200285327 Hindi et al. Sep 2020 A1
20200286472 Newendorp et al. Sep 2020 A1
20200286493 Orr et al. Sep 2020 A1
20200294494 Suyama et al. Sep 2020 A1
20200298394 Han et al. Sep 2020 A1
20200301950 Theo et al. Sep 2020 A1
20200302356 Gruber et al. Sep 2020 A1
20200302919 Greborio et al. Sep 2020 A1
20200302925 Shah et al. Sep 2020 A1
20200302930 Chen et al. Sep 2020 A1
20200302932 Schramm et al. Sep 2020 A1
20200304955 Gross et al. Sep 2020 A1
20200304972 Gross et al. Sep 2020 A1
20200305084 Freeman et al. Sep 2020 A1
20200310513 Nicholson et al. Oct 2020 A1
20200312315 Li et al. Oct 2020 A1
20200312317 Kothari et al. Oct 2020 A1
20200314191 Madhavan et al. Oct 2020 A1
20200319850 Stasior et al. Oct 2020 A1
20200320592 Soule et al. Oct 2020 A1
20200327895 Gruber et al. Oct 2020 A1
20200334492 Zheng et al. Oct 2020 A1
20200335121 Mosseri et al. Oct 2020 A1
20200342082 Sapozhnykov et al. Oct 2020 A1
20200342849 Yu et al. Oct 2020 A1
20200342863 Aggarwal et al. Oct 2020 A1
20200356243 Meyer et al. Nov 2020 A1
20200356634 Srinivasan et al. Nov 2020 A1
20200357391 Ghoshal et al. Nov 2020 A1
20200357406 York et al. Nov 2020 A1
20200357409 Sun et al. Nov 2020 A1
20200364411 Evermann Nov 2020 A1
20200365155 Milden Nov 2020 A1
20200367006 Beckhardt Nov 2020 A1
20200372633 Lee, II et al. Nov 2020 A1
20200372904 Vescovi et al. Nov 2020 A1
20200372905 Wang et al. Nov 2020 A1
20200374243 Jina et al. Nov 2020 A1
20200379610 Ford et al. Dec 2020 A1
20200379640 Bellegarda et al. Dec 2020 A1
20200379726 Blatz et al. Dec 2020 A1
20200379727 Blatz et al. Dec 2020 A1
20200379728 Gada et al. Dec 2020 A1
20200380389 Eldeeb et al. Dec 2020 A1
20200380956 Rossi et al. Dec 2020 A1
20200380963 Chappidi et al. Dec 2020 A1
20200380966 Acero et al. Dec 2020 A1
20200380973 Novitchenko et al. Dec 2020 A1
20200380980 Shum et al. Dec 2020 A1
20200380985 Gada et al. Dec 2020 A1
20200382616 Vaishampayan et al. Dec 2020 A1
20200382635 Vora et al. Dec 2020 A1
20210110106 Vescovi et al. Dec 2020 A1
20210006943 Gross et al. Jan 2021 A1
20210011557 Lemay et al. Jan 2021 A1
20210012113 Petill et al. Jan 2021 A1
20210012775 Kang et al. Jan 2021 A1
20210012776 Peterson et al. Jan 2021 A1
20210043190 Wang et al. Feb 2021 A1
20210065698 Topcu et al. Mar 2021 A1
20210067631 Van Os et al. Mar 2021 A1
20210072953 Amarillo et al. Mar 2021 A1
20210074264 Liang et al. Mar 2021 A1
20210090314 Hussen et al. Mar 2021 A1
20210097998 Kim et al. Apr 2021 A1
20210104232 Lee et al. Apr 2021 A1
20210105528 Van Os et al. Apr 2021 A1
20210110115 Moritz et al. Apr 2021 A1
20210110254 Duy et al. Apr 2021 A1
20210124597 Ramakrishnan et al. Apr 2021 A1
20210127220 Mathieu et al. Apr 2021 A1
20210134318 Harvey et al. May 2021 A1
20210141839 Tang et al. May 2021 A1
20210149629 Martel et al. May 2021 A1
20210149996 Bellegarda May 2021 A1
20210150151 Jiaming et al. May 2021 A1
20210151041 Gruber et al. May 2021 A1
20210151070 Binder et al. May 2021 A1
20210152684 Weinstein et al. May 2021 A1
20210165826 Graham et al. Jun 2021 A1
20210191603 Napolitano et al. Jun 2021 A1
20210191968 Orr et al. Jun 2021 A1
20210208752 Hwang Jul 2021 A1
20210208841 Wilberding Jul 2021 A1
20210216760 Dominic et al. Jul 2021 A1
20210224032 Ryan et al. Jul 2021 A1
20210224474 Jerome et al. Jul 2021 A1
20210233532 Aram et al. Jul 2021 A1
20210248804 Hussen Abdelaziz et al. Aug 2021 A1
20210249009 Manjunath et al. Aug 2021 A1
20210258881 Freeman et al. Aug 2021 A1
20210264913 Schramm et al. Aug 2021 A1
20210271333 Hindi et al. Sep 2021 A1
20210273894 Tian et al. Sep 2021 A1
20210278956 Dolbakian et al. Sep 2021 A1
20210281965 Malik et al. Sep 2021 A1
20210294569 Piersol et al. Sep 2021 A1
20210294571 Carson et al. Sep 2021 A1
20210303116 Barlow Sep 2021 A1
20210306812 Gross et al. Sep 2021 A1
20210312931 Paulik et al. Oct 2021 A1
20210318901 Gruber et al. Oct 2021 A1
20210327409 Naik Oct 2021 A1
20210334528 Bray et al. Oct 2021 A1
20210335342 Yuan et al. Oct 2021 A1
20210349605 Nonaka et al. Nov 2021 A1
20210349608 Blatz et al. Nov 2021 A1
20210350799 Hansen et al. Nov 2021 A1
20210350803 Hansen et al. Nov 2021 A1
20210350810 Phipps et al. Nov 2021 A1
20210352115 Hansen et al. Nov 2021 A1
20210357172 Sinesio et al. Nov 2021 A1
20210365161 Ellis et al. Nov 2021 A1
20210365174 Ellis et al. Nov 2021 A1
20210366480 Lemay et al. Nov 2021 A1
20210373851 Stasior et al. Dec 2021 A1
20210375290 Hu et al. Dec 2021 A1
20210377381 Aggarwal et al. Dec 2021 A1
20210390259 Hildick-Smith et al. Dec 2021 A1
20210390955 Piernot et al. Dec 2021 A1
20210393168 Santarelli et al. Dec 2021 A1
20210402306 Huang Dec 2021 A1
20210407318 Pitschel et al. Dec 2021 A1
20210407502 Vescovi et al. Dec 2021 A1
20220019292 Lemay et al. Jan 2022 A1
20220021631 Jina et al. Jan 2022 A1
20220021978 Gui et al. Jan 2022 A1
20220028387 Walker et al. Jan 2022 A1
20220030345 Gong et al. Jan 2022 A1
20220043986 Nell et al. Feb 2022 A1
20220067283 Bellegarda et al. Mar 2022 A1
20220068278 York et al. Mar 2022 A1
20220083986 Duffy et al. Mar 2022 A1
20220084511 Nickson et al. Mar 2022 A1
20220093088 Sridhar et al. Mar 2022 A1
20220093095 Dighe et al. Mar 2022 A1
20220093109 Orr et al. Mar 2022 A1
20220093110 Kim et al. Mar 2022 A1
20220107780 Gruber et al. Apr 2022 A1
20220122615 Chen et al. Apr 2022 A1
20220139396 Gada et al. May 2022 A1
20220148587 Drummie et al. May 2022 A1
20220156041 Newendorp et al. May 2022 A1
20220157310 Newendorp et al. May 2022 A1
20220157315 Raux et al. May 2022 A1
20220383864 Gruber et al. Dec 2022 A1
Foreign Referenced Citations (784)
Number Date Country
2014100581 Sep 2014 AU
2015203483 Jul 2015 AU
2015101171 Oct 2015 AU
2018100187 Mar 2018 AU
2017222436 Oct 2018 AU
2659698 Sep 2009 CA
2666438 Jun 2013 CA
709795 Dec 2015 CH
1771712 May 2006 CN
1898721 Jan 2007 CN
1959628 May 2007 CN
101162153 Apr 2008 CN
101292282 Oct 2008 CN
101636736 Jan 2010 CN
102324233 Jan 2012 CN
102340590 Feb 2012 CN
102346557 Feb 2012 CN
102346719 Feb 2012 CN
102368256 Mar 2012 CN
102402985 Apr 2012 CN
102405463 Apr 2012 CN
102449438 May 2012 CN
102483915 May 2012 CN
102495406 Jun 2012 CN
102498457 Jun 2012 CN
102510426 Jun 2012 CN
102520789 Jun 2012 CN
101661754 Jul 2012 CN
102629246 Aug 2012 CN
102651217 Aug 2012 CN
102663016 Sep 2012 CN
102681761 Sep 2012 CN
102681896 Sep 2012 CN
102682769 Sep 2012 CN
102682771 Sep 2012 CN
102685295 Sep 2012 CN
102693725 Sep 2012 CN
102694909 Sep 2012 CN
202453859 Sep 2012 CN
102710976 Oct 2012 CN
102722478 Oct 2012 CN
102737104 Oct 2012 CN
102750087 Oct 2012 CN
102792320 Nov 2012 CN
102801853 Nov 2012 CN
102820033 Dec 2012 CN
102844738 Dec 2012 CN
102866828 Jan 2013 CN
102870065 Jan 2013 CN
102882752 Jan 2013 CN
102890936 Jan 2013 CN
102915731 Feb 2013 CN
102917004 Feb 2013 CN
102917271 Feb 2013 CN
102918493 Feb 2013 CN
102955652 Mar 2013 CN
103035240 Apr 2013 CN
103035251 Apr 2013 CN
103038728 Apr 2013 CN
103064956 Apr 2013 CN
103093334 May 2013 CN
103093755 May 2013 CN
103109249 May 2013 CN
103135916 Jun 2013 CN
103187053 Jul 2013 CN
103197963 Jul 2013 CN
103198831 Jul 2013 CN
103209369 Jul 2013 CN
103217892 Jul 2013 CN
103226949 Jul 2013 CN
103236260 Aug 2013 CN
103246638 Aug 2013 CN
103268315 Aug 2013 CN
103280218 Sep 2013 CN
103292437 Sep 2013 CN
103324100 Sep 2013 CN
103327063 Sep 2013 CN
103365279 Oct 2013 CN
103366741 Oct 2013 CN
203249629 Oct 2013 CN
103390016 Nov 2013 CN
103412789 Nov 2013 CN
103414949 Nov 2013 CN
103426428 Dec 2013 CN
103455234 Dec 2013 CN
103456303 Dec 2013 CN
103456306 Dec 2013 CN
103457837 Dec 2013 CN
103475551 Dec 2013 CN
103477592 Dec 2013 CN
103533143 Jan 2014 CN
103533154 Jan 2014 CN
103543902 Jan 2014 CN
103562863 Feb 2014 CN
103582896 Feb 2014 CN
103593054 Feb 2014 CN
103608859 Feb 2014 CN
103620605 Mar 2014 CN
103645876 Mar 2014 CN
103677261 Mar 2014 CN
103686723 Mar 2014 CN
103714816 Apr 2014 CN
103716454 Apr 2014 CN
103727948 Apr 2014 CN
103744761 Apr 2014 CN
103760984 Apr 2014 CN
103761104 Apr 2014 CN
103765385 Apr 2014 CN
103778527 May 2014 CN
103780758 May 2014 CN
103792985 May 2014 CN
103794212 May 2014 CN
103795850 May 2014 CN
103809548 May 2014 CN
103841268 Jun 2014 CN
103885663 Jun 2014 CN
103902373 Jul 2014 CN
103930945 Jul 2014 CN
103942932 Jul 2014 CN
103959751 Jul 2014 CN
203721183 Jul 2014 CN
103971680 Aug 2014 CN
104007832 Aug 2014 CN
102693729 Sep 2014 CN
104036774 Sep 2014 CN
104038621 Sep 2014 CN
104050153 Sep 2014 CN
104090652 Oct 2014 CN
104092829 Oct 2014 CN
104113471 Oct 2014 CN
104125322 Oct 2014 CN
104144377 Nov 2014 CN
104145304 Nov 2014 CN
104169837 Nov 2014 CN
104180815 Dec 2014 CN
104185868 Dec 2014 CN
104240701 Dec 2014 CN
104243699 Dec 2014 CN
104281259 Jan 2015 CN
104281390 Jan 2015 CN
104284257 Jan 2015 CN
104284486 Jan 2015 CN
104335207 Feb 2015 CN
104335234 Feb 2015 CN
104350454 Feb 2015 CN
104360990 Feb 2015 CN
104374399 Feb 2015 CN
104423625 Mar 2015 CN
104423780 Mar 2015 CN
104427104 Mar 2015 CN
104463552 Mar 2015 CN
104464733 Mar 2015 CN
104487929 Apr 2015 CN
104516522 Apr 2015 CN
104573472 Apr 2015 CN
104575493 Apr 2015 CN
104575501 Apr 2015 CN
104584010 Apr 2015 CN
104584096 Apr 2015 CN
104584601 Apr 2015 CN
104604274 May 2015 CN
104679472 Jun 2015 CN
104699746 Jun 2015 CN
104731441 Jun 2015 CN
104769584 Jul 2015 CN
104769670 Jul 2015 CN
104798012 Jul 2015 CN
104821167 Aug 2015 CN
104821934 Aug 2015 CN
104836909 Aug 2015 CN
104854583 Aug 2015 CN
104867492 Aug 2015 CN
104869342 Aug 2015 CN
104951077 Sep 2015 CN
104967748 Oct 2015 CN
104969289 Oct 2015 CN
104978963 Oct 2015 CN
105025051 Nov 2015 CN
105027197 Nov 2015 CN
105093526 Nov 2015 CN
105100356 Nov 2015 CN
105144136 Dec 2015 CN
105164678 Dec 2015 CN
105164719 Dec 2015 CN
105190607 Dec 2015 CN
105247511 Jan 2016 CN
105247551 Jan 2016 CN
105264524 Jan 2016 CN
105278681 Jan 2016 CN
105320251 Feb 2016 CN
105320726 Feb 2016 CN
105379234 Mar 2016 CN
105430186 Mar 2016 CN
105471705 Apr 2016 CN
105472587 Apr 2016 CN
105516441 Apr 2016 CN
105554217 May 2016 CN
105556592 May 2016 CN
105808200 Jul 2016 CN
105830048 Aug 2016 CN
105869641 Aug 2016 CN
105872222 Aug 2016 CN
105917311 Aug 2016 CN
106030699 Oct 2016 CN
106062734 Oct 2016 CN
106062790 Oct 2016 CN
106415412 Feb 2017 CN
106462383 Feb 2017 CN
106463114 Feb 2017 CN
106465074 Feb 2017 CN
106471570 Mar 2017 CN
106534469 Mar 2017 CN
106558310 Apr 2017 CN
106773742 May 2017 CN
106776581 May 2017 CN
107004412 Aug 2017 CN
107450800 Dec 2017 CN
107480161 Dec 2017 CN
107491285 Dec 2017 CN
107491468 Dec 2017 CN
107506037 Dec 2017 CN
107545262 Jan 2018 CN
107608998 Jan 2018 CN
107615378 Jan 2018 CN
107623616 Jan 2018 CN
107786730 Mar 2018 CN
107852436 Mar 2018 CN
107871500 Apr 2018 CN
107919123 Apr 2018 CN
107924313 Apr 2018 CN
107978313 May 2018 CN
108268187 Jul 2018 CN
108647681 Oct 2018 CN
109447234 Mar 2019 CN
109657629 Apr 2019 CN
110135411 Aug 2019 CN
110263144 Sep 2019 CN
105164719 Nov 2019 CN
110531860 Dec 2019 CN
110598671 Dec 2019 CN
110647274 Jan 2020 CN
110825469 Feb 2020 CN
110945840 Mar 2020 CN
111124224 May 2020 CN
107123417 Jun 2020 CN
111316203 Jun 2020 CN
202016008226 May 2017 DE
1396797 Mar 2004 EP
1588353 Oct 2005 EP
1699042 Sep 2006 EP
1939860 Jul 2008 EP
2431842 Mar 2012 EP
2523109 Nov 2012 EP
2523188 Nov 2012 EP
2551784 Jan 2013 EP
2555536 Feb 2013 EP
2575128 Apr 2013 EP
2632129 Aug 2013 EP
2639792 Sep 2013 EP
2669889 Dec 2013 EP
2672229 Dec 2013 EP
2672231 Dec 2013 EP
2675147 Dec 2013 EP
2680257 Jan 2014 EP
2683147 Jan 2014 EP
2683175 Jan 2014 EP
2672231 Apr 2014 EP
2717259 Apr 2014 EP
2725577 Apr 2014 EP
2733598 May 2014 EP
2733896 May 2014 EP
2743846 Jun 2014 EP
2760015 Jul 2014 EP
2779160 Sep 2014 EP
2781883 Sep 2014 EP
2787683 Oct 2014 EP
2801890 Nov 2014 EP
2801972 Nov 2014 EP
2801974 Nov 2014 EP
2824564 Jan 2015 EP
2849177 Mar 2015 EP
2879402 Jun 2015 EP
2881939 Jun 2015 EP
2891049 Jul 2015 EP
2915021 Sep 2015 EP
2930715 Oct 2015 EP
2938022 Oct 2015 EP
2940556 Nov 2015 EP
2947859 Nov 2015 EP
2950307 Dec 2015 EP
2957986 Dec 2015 EP
2973380 Jan 2016 EP
2985984 Feb 2016 EP
2891049 Mar 2016 EP
3032532 Jun 2016 EP
3035329 Jun 2016 EP
3038333 Jun 2016 EP
3115905 Jan 2017 EP
3125097 Feb 2017 EP
2672231 May 2017 EP
3161612 May 2017 EP
3200185 Aug 2017 EP
3224708 Oct 2017 EP
3227771 Oct 2017 EP
3246916 Nov 2017 EP
3270658 Jan 2018 EP
3300074 Mar 2018 EP
2973380 Aug 2018 EP
2983065 Aug 2018 EP
3392876 Oct 2018 EP
3401773 Nov 2018 EP
2973002 Jun 2019 EP
3506151 Jul 2019 EP
3323058 Feb 2020 EP
2011MU03716 Feb 2012 IN
2012MU01227 Jun 2012 IN
62-8389 Jul 1994 JP
63-32493 Dec 1994 JP
7-219961 Aug 1995 JP
9-27000 Jan 1997 JP
10-31497 Feb 1998 JP
11-136278 May 1999 JP
11-175553 Jul 1999 JP
11-265400 Sep 1999 JP
2000-216910 Aug 2000 JP
2000-331004 Nov 2000 JP
2001-22779 Jan 2001 JP
2001-075775 Mar 2001 JP
2001-125896 May 2001 JP
2001-297174 Oct 2001 JP
2002-30676 Jan 2002 JP
2002-41276 Feb 2002 JP
2002-82748 Mar 2002 JP
2002-132804 May 2002 JP
2002-230021 Aug 2002 JP
2002-524806 Aug 2002 JP
2002-525690 Aug 2002 JP
2002-287793 Oct 2002 JP
2002-341892 Nov 2002 JP
2003-15682 Jan 2003 JP
2003-194547 Jul 2003 JP
2003-533909 Nov 2003 JP
2004-70504 Mar 2004 JP
2004-94936 Mar 2004 JP
2004-523004 Jul 2004 JP
2004-295837 Oct 2004 JP
2004-333870 Nov 2004 JP
2004-355003 Dec 2004 JP
2005-55782 Mar 2005 JP
2005-63257 Mar 2005 JP
2005-149481 Jun 2005 JP
2005-181386 Jul 2005 JP
2005-332212 Dec 2005 JP
2005-334363 Dec 2005 JP
2005-537576 Dec 2005 JP
2006-4274 Jan 2006 JP
2006-59094 Mar 2006 JP
2006-189394 Jul 2006 JP
2006-195637 Jul 2006 JP
2006-201870 Aug 2006 JP
2006-318373 Nov 2006 JP
2006-526185 Nov 2006 JP
2007-17990 Jan 2007 JP
2007-500903 Jan 2007 JP
2007-79690 Mar 2007 JP
2007-264471 Oct 2007 JP
2007-280179 Oct 2007 JP
2007-323612 Dec 2007 JP
2007-325089 Dec 2007 JP
2008-26381 Feb 2008 JP
2008-39928 Feb 2008 JP
2008-58813 Mar 2008 JP
2008-64885 Mar 2008 JP
2008-90545 Apr 2008 JP
2008-514983 May 2008 JP
2008-185693 Aug 2008 JP
2008-198022 Aug 2008 JP
2008-233678 Oct 2008 JP
2008-269480 Nov 2008 JP
2008-287697 Nov 2008 JP
2009-505142 Feb 2009 JP
2009-47920 Mar 2009 JP
2009-140444 Jun 2009 JP
2009-522861 Jun 2009 JP
2009-157951 Jul 2009 JP
2009-186989 Aug 2009 JP
2009-193448 Aug 2009 JP
2009-193457 Aug 2009 JP
2009-193532 Aug 2009 JP
2009-205367 Sep 2009 JP
2009-217611 Sep 2009 JP
2010-518526 May 2010 JP
2012-14394 Jan 2012 JP
2012-502377 Jan 2012 JP
2012-22478 Feb 2012 JP
2012-33997 Feb 2012 JP
2012-37619 Feb 2012 JP
2012-40655 Mar 2012 JP
2012-63536 Mar 2012 JP
2012-508530 Apr 2012 JP
2012-89020 May 2012 JP
2012-511774 May 2012 JP
2012-116442 Jun 2012 JP
2012-142744 Jul 2012 JP
2012-147063 Aug 2012 JP
2012-150804 Aug 2012 JP
2012-164070 Aug 2012 JP
2012-165084 Aug 2012 JP
2012-518847 Aug 2012 JP
2012-211932 Nov 2012 JP
2012-220959 Nov 2012 JP
2013-37688 Feb 2013 JP
2013-46171 Mar 2013 JP
2013-511214 Mar 2013 JP
2013-65284 Apr 2013 JP
2013-73240 Apr 2013 JP
2013-513315 Apr 2013 JP
2013-80476 May 2013 JP
2013-517566 May 2013 JP
2013-131087 Jul 2013 JP
2013-134430 Jul 2013 JP
2013-134729 Jul 2013 JP
2013-140520 Jul 2013 JP
2013-527947 Jul 2013 JP
2013-528012 Jul 2013 JP
2013-148419 Aug 2013 JP
2013-156349 Aug 2013 JP
2013-174987 Sep 2013 JP
2013-535059 Sep 2013 JP
2013-200265 Oct 2013 JP
2013-200423 Oct 2013 JP
2013-205999 Oct 2013 JP
2013-238935 Nov 2013 JP
2013-238936 Nov 2013 JP
2013-248292 Dec 2013 JP
2013-257694 Dec 2013 JP
2013-258600 Dec 2013 JP
2014-2586 Jan 2014 JP
2014-10688 Jan 2014 JP
2014-502445 Jan 2014 JP
2014-26629 Feb 2014 JP
2014-45449 Mar 2014 JP
2014-507903 Mar 2014 JP
2014-60600 Apr 2014 JP
2014-72586 Apr 2014 JP
2014-77969 May 2014 JP
2014-89711 May 2014 JP
2014-109889 Jun 2014 JP
2014-124332 Jul 2014 JP
2014-126600 Jul 2014 JP
2014-127754 Jul 2014 JP
2014-140121 Jul 2014 JP
2014-518409 Jul 2014 JP
2014-142566 Aug 2014 JP
2014-145842 Aug 2014 JP
2014-146940 Aug 2014 JP
2014-150323 Aug 2014 JP
2014-519648 Aug 2014 JP
2014-524627 Sep 2014 JP
2014-191272 Oct 2014 JP
2014-219614 Nov 2014 JP
2014-222514 Nov 2014 JP
2015-1931 Jan 2015 JP
2015-4928 Jan 2015 JP
2015-8001 Jan 2015 JP
2015-12301 Jan 2015 JP
2015-18365 Jan 2015 JP
2015-501022 Jan 2015 JP
2015-501034 Jan 2015 JP
2015-504619 Feb 2015 JP
2015-41845 Mar 2015 JP
2015-52500 Mar 2015 JP
2015-60423 Mar 2015 JP
2015-81971 Apr 2015 JP
2015-83938 Apr 2015 JP
2015-94848 May 2015 JP
2015-514254 May 2015 JP
2015-519675 Jul 2015 JP
2015-524974 Aug 2015 JP
2015-526776 Sep 2015 JP
2015-527683 Sep 2015 JP
2015-528140 Sep 2015 JP
2015-528918 Oct 2015 JP
2015-531909 Nov 2015 JP
2016-504651 Feb 2016 JP
2016-35614 Mar 2016 JP
2016-508007 Mar 2016 JP
2016-71247 May 2016 JP
2016-119615 Jun 2016 JP
2016-151928 Aug 2016 JP
2016-524193 Aug 2016 JP
2016-536648 Nov 2016 JP
2017-11608 Jan 2017 JP
2017-19331 Jan 2017 JP
2017-516153 Jun 2017 JP
2017-123187 Jul 2017 JP
2017-211608 Nov 2017 JP
2017-537361 Dec 2017 JP
6291147 Feb 2018 JP
2018-101242 Jun 2018 JP
2018-113035 Jul 2018 JP
2018-525950 Sep 2018 JP
2018-536889 Dec 2018 JP
10-2002-0004931 Jan 2002 KR
2002-0004931 Jan 2002 KR
10-2002-0064149 Aug 2002 KR
10-2004-0014835 Feb 2004 KR
10-2006-0037228 May 2006 KR
10-2006-0073574 Jun 2006 KR
10-2006-0091469 Aug 2006 KR
10-2007-0022393 Feb 2007 KR
10-2007-0100837 Oct 2007 KR
10-2008-0049647 Jun 2008 KR
10-2009-0001716 Jan 2009 KR
10-2009-0122944 Dec 2009 KR
10-2012-0020164 Mar 2012 KR
10-2012-0031722 Apr 2012 KR
10-2012-0066523 Jun 2012 KR
10-2012-0082371 Jul 2012 KR
10-2012-0084472 Jul 2012 KR
10-1178310 Aug 2012 KR
10-2012-0120316 Nov 2012 KR
10-2012-0137424 Dec 2012 KR
10-2012-0137434 Dec 2012 KR
10-2012-0137435 Dec 2012 KR
10-2012-0137440 Dec 2012 KR
10-2012-0138826 Dec 2012 KR
10-2012-0139827 Dec 2012 KR
10-1193668 Dec 2012 KR
10-2013-0035983 Apr 2013 KR
10-2013- 0086750 Aug 2013 KR
10-2013-0090947 Aug 2013 KR
10-2013-0108563 Oct 2013 KR
10-1334342 Nov 2013 KR
10-2013-0131252 Dec 2013 KR
10-2013-0133629 Dec 2013 KR
10-2014- 0007282 Jan 2014 KR
10-2014-0024271 Feb 2014 KR
10-2014- 0025996 Mar 2014 KR
10-2014-0031283 Mar 2014 KR
10-2014-0033574 Mar 2014 KR
10-2014-0042994 Apr 2014 KR
10-2014-0055204 May 2014 KR
10-2014- 0059697 May 2014 KR
10-2014-0068752 Jun 2014 KR
10-2014- 0071208 Jun 2014 KR
10-2014-0088449 Jul 2014 KR
10-2014- 0093949 Jul 2014 KR
10-2014-0106715 Sep 2014 KR
10-2014- 0107253 Sep 2014 KR
10-2014-0147557 Dec 2014 KR
10-2015- 0006454 Jan 2015 KR
10-2015-0013631 Feb 2015 KR
10-1506510 Mar 2015 KR
10-2015-0038375 Apr 2015 KR
10-2015-0039380 Apr 2015 KR
10-2015-0041974 Apr 2015 KR
10-2015-0043512 Apr 2015 KR
10-2015-0062811 Jun 2015 KR
10-2015-0095624 Aug 2015 KR
10-1555742 Sep 2015 KR
10-2015-0113127 Oct 2015 KR
10-2015-0131262 Nov 2015 KR
10-2015-0138109 Dec 2015 KR
10-2016-0004351 Jan 2016 KR
10-2016-0010523 Jan 2016 KR
10-2016-0040279 Apr 2016 KR
10-2016-0055839 May 2016 KR
10-2016-0065503 Jun 2016 KR
10-2016-0101079 Aug 2016 KR
10-2016-0101198 Aug 2016 KR
10-2016-0105847 Sep 2016 KR
10-2016-0121585 Oct 2016 KR
10-2016-0127165 Nov 2016 KR
10-2016-0140694 Dec 2016 KR
10-2016-0147854 Dec 2016 KR
10-2017-0004482 Jan 2017 KR
10-2017-0036805 Apr 2017 KR
10-2017-0104006 Sep 2017 KR
10-2017-0107058 Sep 2017 KR
10-1776673 Sep 2017 KR
10-2018-0032632 Mar 2018 KR
10-2018-0034637 Apr 2018 KR
10-2018-0135877 Dec 2018 KR
10-1959328 Mar 2019 KR
10-2020-0105519 Sep 2020 KR
2273106 Mar 2006 RU
2349970 Mar 2009 RU
2353068 Apr 2009 RU
2364917 Aug 2009 RU
2012141604 Apr 2014 RU
201227715 Jul 2012 TW
201245989 Nov 2012 TW
201312548 Mar 2013 TW
201407184 Feb 2014 TW
201610982 Mar 2016 TW
201629750 Aug 2016 TW
200014727 Mar 2000 WO
200014728 Mar 2000 WO
200171480 Sep 2001 WO
200249253 Jun 2002 WO
2004023334 Mar 2004 WO
2004023455 Mar 2004 WO
2004064299 Jul 2004 WO
2004102417 Nov 2004 WO
2005064592 Jul 2005 WO
2006084144 Aug 2006 WO
2007009225 Jan 2007 WO
2007013521 Feb 2007 WO
2007055766 May 2007 WO
2008098900 Aug 2008 WO
2008140236 Nov 2008 WO
2010109358 Sep 2010 WO
2011088053 Jul 2011 WO
2011133573 Oct 2011 WO
2011097309 Dec 2011 WO
2011088053 Jan 2012 WO
2012008434 Jan 2012 WO
2012019020 Feb 2012 WO
2012019637 Feb 2012 WO
2012033312 Mar 2012 WO
2012056463 May 2012 WO
2012063260 May 2012 WO
2012084965 Jun 2012 WO
2012092562 Jul 2012 WO
2012112331 Aug 2012 WO
2012129231 Sep 2012 WO
2012063260 Oct 2012 WO
2012135157 Oct 2012 WO
2012154317 Nov 2012 WO
2012154748 Nov 2012 WO
2012155079 Nov 2012 WO
2012160567 Nov 2012 WO
2012167168 Dec 2012 WO
2012173902 Dec 2012 WO
2013009578 Jan 2013 WO
2013022135 Feb 2013 WO
2013022223 Feb 2013 WO
2013048880 Apr 2013 WO
2013049358 Apr 2013 WO
2013057153 Apr 2013 WO
2013101489 Jul 2013 WO
2013118988 Aug 2013 WO
2013122310 Aug 2013 WO
2013128999 Sep 2013 WO
2013133533 Sep 2013 WO
2013137660 Sep 2013 WO
2013163113 Oct 2013 WO
2013163857 Nov 2013 WO
2013169842 Nov 2013 WO
2013173504 Nov 2013 WO
2013173511 Nov 2013 WO
2013176847 Nov 2013 WO
2013184953 Dec 2013 WO
2013184990 Dec 2013 WO
2014003138 Jan 2014 WO
2014004544 Jan 2014 WO
2014018580 Jan 2014 WO
2014021967 Feb 2014 WO
2014022148 Feb 2014 WO
2014028735 Feb 2014 WO
2014028797 Feb 2014 WO
2014031505 Feb 2014 WO
2014032461 Mar 2014 WO
2014040022 Mar 2014 WO
2014046475 Mar 2014 WO
2014047047 Mar 2014 WO
2014048855 Apr 2014 WO
2014066352 May 2014 WO
2014070872 May 2014 WO
2014073825 May 2014 WO
2014078965 May 2014 WO
2014093339 Jun 2014 WO
2014093911 Jun 2014 WO
2014096506 Jun 2014 WO
2014124332 Aug 2014 WO
2014137074 Sep 2014 WO
2014138604 Sep 2014 WO
2014143959 Sep 2014 WO
2014144395 Sep 2014 WO
2014144579 Sep 2014 WO
2014144949 Sep 2014 WO
2014149473 Sep 2014 WO
2014151153 Sep 2014 WO
2014124332 Oct 2014 WO
2014159578 Oct 2014 WO
2014159581 Oct 2014 WO
2014162570 Oct 2014 WO
2014169269 Oct 2014 WO
2014173189 Oct 2014 WO
2013173504 Dec 2014 WO
2014197336 Dec 2014 WO
2014197339 Dec 2014 WO
2014197635 Dec 2014 WO
2014197730 Dec 2014 WO
2014200728 Dec 2014 WO
2014204659 Dec 2014 WO
2014210392 Dec 2014 WO
2015018440 Feb 2015 WO
2015020942 Feb 2015 WO
2015029379 Mar 2015 WO
2015030796 Mar 2015 WO
2015036817 Mar 2015 WO
2015041882 Mar 2015 WO
2015041892 Mar 2015 WO
2015047932 Apr 2015 WO
2015053485 Apr 2015 WO
2015054141 Apr 2015 WO
2015080530 Jun 2015 WO
2015084659 Jun 2015 WO
2015092943 Jun 2015 WO
2015094169 Jun 2015 WO
2015094369 Jun 2015 WO
2015098306 Jul 2015 WO
2015099939 Jul 2015 WO
2015112625 Jul 2015 WO
2015116151 Aug 2015 WO
2015121449 Aug 2015 WO
2015127404 Aug 2015 WO
2015151133 Oct 2015 WO
2015153310 Oct 2015 WO
2015157013 Oct 2015 WO
2015183368 Dec 2015 WO
2015183401 Dec 2015 WO
2015183699 Dec 2015 WO
2015184186 Dec 2015 WO
2015184387 Dec 2015 WO
2015200207 Dec 2015 WO
2016027933 Feb 2016 WO
2016028946 Feb 2016 WO
2016033257 Mar 2016 WO
2016039992 Mar 2016 WO
2016040721 Mar 2016 WO
2016051519 Apr 2016 WO
2016052164 Apr 2016 WO
2016054230 Apr 2016 WO
2016057268 Apr 2016 WO
2016075081 May 2016 WO
2016085775 Jun 2016 WO
2016085776 Jun 2016 WO
2016089029 Jun 2016 WO
2016100139 Jun 2016 WO
2016111881 Jul 2016 WO
2016144840 Sep 2016 WO
2016144982 Sep 2016 WO
2016144983 Sep 2016 WO
2016175354 Nov 2016 WO
2016187149 Nov 2016 WO
2016190950 Dec 2016 WO
2016209444 Dec 2016 WO
2016209924 Dec 2016 WO
2017044160 Mar 2017 WO
2017044257 Mar 2017 WO
2017044260 Mar 2017 WO
2017044629 Mar 2017 WO
2017053311 Mar 2017 WO
2017058293 Apr 2017 WO
2017059388 Apr 2017 WO
2017071420 May 2017 WO
2017142116 Aug 2017 WO
2017160487 Sep 2017 WO
2017200777 Nov 2017 WO
2017203484 Nov 2017 WO
2017213678 Dec 2017 WO
2017213682 Dec 2017 WO
2017218194 Dec 2017 WO
2018009397 Jan 2018 WO
2018044633 Mar 2018 WO
2018067528 Apr 2018 WO
2018176053 Sep 2018 WO
2018209152 Nov 2018 WO
2018213401 Nov 2018 WO
2018213415 Nov 2018 WO
2018231307 Dec 2018 WO
2019067930 Apr 2019 WO
2019078576 Apr 2019 WO
2019079017 Apr 2019 WO
2019143397 Jul 2019 WO
2019147429 Aug 2019 WO
2019236217 Dec 2019 WO
2020010530 Jan 2020 WO
2020109074 Jun 2020 WO
2021054565 Mar 2021 WO
2021252230 Dec 2021 WO
Non-Patent Literature Citations (761)
Entry
Notice of Acceptance received for Australian Patent Application No. 2021240130, mailed on Jan. 16, 2023, 3 pages.
Abdelaziz et al., “Speaker-Independent Speech-Driven Visual Speech Synthesis using Domain-Adapted Acoustic Models”, May 15, 2019, 9 pages.
Accessibility on IOS, Apple Inc., Online available at: https://developer.apple.com/accessibility/ios/, Retrieved on Jul. 26, 2021, 2 pages.
Alsharif et al., “Long Short-Term Memory Neural Network for Keyboard Gesture Decoding”, IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP), Brisbane, Australia, Sep. 2015, 5 pages.
Apple Differential Privacy Team, “Learning with Privacy at Scale”, Apple Machine Learning Blog, vol. 1, No. 8, Online available at: <https://machinelearning.apple.com/2017/12/06/learning-with-privacy-at-scale.html>, Dec. 2017, 9 pages.
Bodapati et al., “Neural Word Decomposition Models for Abusive Language. Detection”, Proceedings of the Third Workshop on Abusive Language Online, Aug. 1, 2019, pp. 135-145.
Bulyko et al., “Error-Correction Detection and Response Generation in a Spoken Dialogue System”, Speech Communication, vol. 45, 2005, pp. 271-288.
Büttner et al., “The Design Space of Augmented and Virtual Reality Applications for Assistive Environments in Manufacturing: A Visual Approach”, In Proceedings of the 10th International Conference on PErvasive Technologies Related to Assistive Environments (PETRA '17), Island of Rhodes, Greece, Online available at: https://dl.acm.org/doi/pdf/10.1145/3056540.3076193, Jun. 21-23, 2017, pp. 433-440.
Chen, Angela, “Amazon's Alexa now handles patient health information”, Available online at: <https://www.theverge.com/2019/4/4/18295260/amazon-hipaa-alexa-echo-patient-health-information-privacy-voice-assistant>, Apr. 4, 2019, 2 pages.
Chenghao, Yuan, “MacroDroid”, Online available at: https://www.ifanr.com/weizhizao/612531, Jan. 25, 2016, 7 pages (Official Copy Only). {See communication under 37 CFR § 1.98(a) (3)}.
Cox et al., “Speech and Language Processing for Next-Millennium Communications Services”, Proceedings of the IEEE, vol. 88, No. 8, Aug. 2000, pp. 1314-1337.
Dai, et al., “Transformer-XL: Attentive Language Models Beyond a Fixed-Length Context”, Online available at: arXiv:1901.02860v3, Jun. 2, 2019, 20 pages.
Davis et al., “A Personal Handheld Multi-Modal Shopping Assistant”, International Conference on Networking and Services, IEEE, 2006, 9 pages.
Dighe et al., “Lattice-Based Improvements for Voice Triggering Using Graph Neural Networks”, in 2020 IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP), Jan. 25, 2020, 5 pages.
Dwork et al., “The Algorithmic Foundations of Differential Privacy”, Foundations and Trends in Theoretical Computer Science: vol. 9: No. 3-4, 211-407, 2014, 281 pages.
Edim, et al., “A Multi-Agent Based Virtual Personal Assistant for E-Health Service”, Journal of Information Engineering and Applications, vol. 3, No. 11, 2013, 9 pages.
Ganin et al., “Unsupervised Domain Adaptation by Backpropagation”, in Proceedings of the 32nd International Conference on Machine Learning, vol. 37, Jul. 2015, 10 pages.
Gatys et al., “Image Style Transfer Using Convolutional Neural Networks”, Proceedings of IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP), 2016, pp. 2414-2423.
Geyer et al., “Differentially Private Federated Learning: A Client Level Perspective”, arXiv: 1712.07557v2, Mar. 2018, 7 pages.
Goodfellow et al., “Generative Adversarial Networks”, Proceedings of the Neural Information Processing Systems, Dec. 2014, 9 pages.
Graves, Alex, “Sequence Transduction with Recurrent Neural Networks”, Proceeding of International Conference of Machine Learning (ICML) Representation Learning Workshop, Nov. 14, 2012, 9 pages.
Gruber, Tom, “Siri, A Virtual Personal Assistant-Bringing Intelligence to the Interface”, Semantic Technologies Conference, Jun. 16, 2009, 21 pages.
Gu et al., “BadNets: Evaluating Backdooring Attacks on Deep Neural Networks”, IEEE Access, vol. 7, Mar. 21, 2019, pp. 47230-47244.
Guo et al., “StateLens: A Reverse Engineering Solution for Making Existing Dynamic Touchscreens Accessible”, In Proceedings of the 32nd Annual Symposium on User Interface Software and Technology (UIST '19), New Orleans, LA, USA, Online available at: https://dl.acm.org/doi/pdf/10.1145/3332165.3347873, Oct. 20-23, 2019, pp. 371-385.
Guo et al., “Time-Delayed Bottleneck Highway Networks Using a DFT Feature for Keyword Spotting”, IEEE International Conference on Acoustics, Speech and Signal Processing (Icassp). IEEE, 2018, 5 pages.
Guo et al., “VizLens: A Robust and Interactive Screen Reader for Interfaces in the Real World”, In Proceedings of the 29th Annual Symposium on User Interface Software and Technology (UIST '16), Tokyo, Japan, Online available at: https://dl.acm.org/doi/pdf/10.1145/2984511.2984518, Oct. 16-19, 2016, pp. 651-664.
Haung et al., “A Study for Improving Device-Directed Speech Detection Toward Frictionless Human-Machine Interaction”, in Proc. Interspeech, 2019, 5 pages.
Hawkeye, “Hawkeye—A better user testing platform”, Online Available at: https://www.youtube.com/watch?v=el0TWOg_760, Oct. 16, 2019, 3 pages.
Hawkeye, “Learn where people look in your products”, Online Available at: https://www.usehawkeye.com, 2019, 6 pages.
Heller et al., “AudioScope: Smartphones as Directional Microphones in Mobile Audio Augmented Reality Systems”, In Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems (CHI '15), Crossings, Seoul, Korea, Online available at: https://dl.acm.org/doi/pdf/10.1145/2702123.2702159, Apr. 18-23, 2015, pp. 949-952.
Henderson et al., “Efficient Natural Language Response Suggestion for Smart Reply”, Available Online at: https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/1846e8a466c079eae7e90727e27caf5f98f10e0c.pdf, 2017, 15 pages.
Hinton et al., “Distilling the Knowledge in A Neural Network”, arXiv preprintarXiv:1503.02531, Mar. 2, 2015, 9 pages.
Hook et al., “Automatic speech based emotion recognition using paralinguistics features”, Bulletin of the Polish Academy of Sciences, Technical Sciences, vol. 67, No. 3, 2019, pp. 479-488.
“How to adjust the order of control center buttons on iPhone iOS12 version after buying a mobile phone”, Available online at: https://jingyan.baidu.com/article/5bbb5albbe5a9713eba1791b.html?, Jun. 14, 2019, 4 pages (Official Copy only). {See communication under 37 CFR § 1.98(a) (3)}.
Idasallinen, “What's The ‘Like’ Meter Based on?”, Online Available at:—<https://community.spotify.com/t5/Content-Questions/What-s-the-like-meter-based-on/td-p/1209974>, Sep. 22, 2015, 6 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/020861, mailed on Nov. 29, 2011, 15 pages.
Jeon et al., “Voice Trigger Detection from LVCSR Hypothesis Lattices Using Bidirectional Lattice Recurrent Neural Networks”, International Conference on Acoustics, Speech and Signal Processing (ICASSP). IEEE, Feb. 29, 2020, 5 pages.
Jeong et al., “Development Trend of N-Screen Service”, Journal of Broadcasting Engineering, vol. 17, No. 1, Sep. 2012, 18 pages (6 pages of English Translation and 12 pages of Official Copy).
Kannan et al., “Smart Reply: Automated Response Suggestion for Email”, Available Online at: https://arxiv.org/pdf/1606.04870.pdf, Jun. 15, 2016, 10 pages.
Kondrat, Tomek, “Automation for Everyone with MacroDroid”, Online available at: https://www.xda-developers.com/automation-for-everyone-with-macrodroid/, Nov. 17, 2013, 6 pages.
Kruger et al., “Virtual World Accessibility with the Perspective Viewer”, Proceedings of ICEAPVI, Athens, Greece, Feb. 12-14, 2015, 6 pages.
Kumar, Shiu, “Ubiquitous Smart Home System Using Android Application”, International Journal of Computer Networks & Communications (IJCNC) vol. 6, No. 1, Jan. 2014, pp. 33-43.
Kumatani et al., “Direct Modeling of Raw Audio with DNNS For Wake Word Detection”, in 2017 IEEE Automatic Speech Recognition and Understanding Workshop (ASRU), 2017, 6 pages.
Lin, Luyuan, “An Assistive Handwashing System with Emotional Intelligence”, Using Emotional Intelligence in Cognitive Intelligent Assistant Systems, 2014, 101 pages.
Maas et al., “Combining Acoustic Embeddings and Decoding Features for End-Of-Utterance Detection in Real-Time Far-Field Speech Recognition Systems”, in 2018 IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP). IEEE, 2018, 5 pages.
Mallidi et al., “Device-Directed Utterance Detection”, Proc. Interspeech, Aug. 7, 2018, 4 pages.
“Method to Provide Remote Voice Navigation Capability on the Device”, IP.COM, Jul. 21, 2016, 4 pages.
Microsoft Soundscape—A map delivered in 3D sound, Microsoft Research, Online available at: https://www.microsoft.com/en-us/research/product/soundscape/, Retrieved on Jul. 26, 2021, 5 pages.
Mnih et al., “Human-Level Control Through Deep Reinforcement Learning”, Nature, vol. 518, Feb. 26, 2015, pp. 529-533.
Müller et al., “A Taxonomy for Information Linking in Augmented Reality”, AVR 2016, Part I, LNCS 9768, 2016, pp. 368-387.
Muller et al., “Control Theoretic Models of Pointing”, ACM Transactions on Computer-Human Interaction, Aug. 2017, 36 pages.
Non-Final Office Action received for U.S. Appl. No. 16/912,278, mailed on Mar. 30, 2022, 9 pages.
Norouzian et al., “Exploring Attention Mechanism for Acoustic based Classification of Speech Utterances into System-Directed and Non-System-Directed”, International Conference on Acoustics, Speech and Signal Processing (ICASSP). IEEE, Feb. 1, 2019, 5 pages.
Notice of Allowance received for Korean Patent Application No. 10-2022-7006342, mailed on Apr. 29, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Office Action received for Australian Patent Application No. 2020257070, mailed on May 23, 2022, 2 pages.
Office Action received for Canadian Patent Application No. 3,077,914, mailed on Apr. 26, 2022, 4 pages.
Pavlopoulos et al., “ConvAI at SemEval-2019 Task 6: Offensive Language Identification and Categorization with Perspective and BERT”, Proceedings of the 13th International Workshop on Semantic Evaluation (SemEval-2019), Jun. 6-7, 2019, pp. 571-576.
Philips, Chris, “Thumbprint Radio: A Uniquely Personal Station Inspired By All of Your Thumbs Up”, Pandora News, Online Available at:—<https://blog.pandora.com/author/chris-phillips/>, Dec. 14, 2015, 7 pages.
Ping, et al., “Deep Voice 3: Scaling Text to Speech with Convolutional Sequence Learning”, Available online at: https://arxiv.org/abs/1710.07654, Feb. 22, 2018, 16 pages.
“Pose, Cambridge Dictionary Definition of Pose”, Available online at: <https://dictionary.cambridge.org/dictionary/english/pose>, 4 pages.
“Radio Stations Tailored to You Based on the Music You Listen to on iTunes”, Apple Announces iTunes Radio, Press Release, Jun. 10, 2013, 3 pages.
Ramakrishnan et al., “Speech emotion recognition approaches in human computer interaction”, Telecommunication Systems, vol. 52, 2013, pp. 1467-1478.
Raux, Antoine, “High-Density Dialog Management The Topic Stack”, Adventures in High Density, Online available at: https://medium.com/adventures-in-high-density/high-density-dialog-management-23efcf91db1e, Aug. 1, 2018, 10 pages.
Ravi, Sujith, “Google AI Blog: On-device Machine Intelligence”, Available Online at: https://ai.googleblog.com/2017/02/on-device-machine-intelligence.html, Feb. 9, 2017, 4 pages.
Robbins, F Mike, “Automatically place an Android Phone on Vibrate at Work”, Available online at: https://mikefrobbins.com/2016/07/21/automatically-place-an-android-phone-on-vibrate-at-work/, Jul. 21, 2016, pp. 1-11.
Rodrigues et al., “Exploring Mixed Reality in Specialized Surgical Environments”, In Proceedings of the 2017 CHI Conference Extended Abstracts on Human Factors in Computing Systems (Chi EA '17), Denver, CO, USA, Online available at: https://dl.acm.org/doi/pdf/10.1145/3027063.3053273, May 6-11, 2017, pp. 2591-2598.
Ross et al., “Epidemiology as a Framework for Large-Scale Mobile Application Accessibility Assessment”, In Proceedings of the 19th International ACM SIGACCESS Conference on Computers and Accessibility (ASSETS '17), Baltimore, MD, USA, Online available at: https://dl.acm.org/doi/pdf/10.1145/3132525.3132547, Oct. 29-Nov. 1, 2017, pp. 2-11.
Schenk et al., “GazeEverywhere: Enabling Gaze-only User Interaction on an Unmodified Desktop PC in Everyday Scenarios”, In Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems (CHI'17). ACM, New York, NY, 30343044. Online Available at: https://doi.org/10.1145/3025453.3025455, May 6-11, 2017, 11 pages.
Sigtia et al., “Efficient Voice Trigger Detection for Low Resource Hardware”, in Proc. Interspeech 2018, Sep. 2-6, 2018, pp. 2092-2096.
Sigtia et al., “Multi-Task Learning for Voice Trigger Detection”, in IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP), 2020, Apr. 20, 2020, 5 pages.
Simonite, Tom, “Confronting Siri: Microsoft Launches Digital Assistant Cortana”, 2014, 2 pages (Official Copy Only). {See communication under 37 CFR § 1.98(a) (3)}.
Song, Yang, “Research of Chinese Continuous Digital Speech Input System Based on HTK”, Computer and Digital Engineering, vol. 40, No. 4, Dec. 31, 2012, 5 pages (Official Copy Only). {See communication under 37 CFR § 1.98(a) (3)}.
Speicher et al., “What is Mixed Reality?”, In Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems (CHI '19). ACM, Article 537, Glasgow, Scotland, UK, Online available at: https://dl.acm.org/doi/pdf/10.1145/3290605.3300767, May 4-9, 2019, 15 pages.
Sperber et al., “Self-Attentional Models for Lattice Inputs”, in Proceedings of the 57th Annual Meeting of the Association for Computational Linguistics, Florence, Italy, Association for Computational Linguistics, Jun. 4, 2019, 13 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/879,643, mailed on May 20, 2022, 2 pages.
Sutskever et al., “Sequence to Sequence Learning with Neural Networks”, Proceedings of the 27th International Conference on Neural Information Processing Systems, 2014, 9 pages.
Tamar et al., “Value Iteration Networks”, Advances in Neural Information Processing Systems, vol. 29, 2016, 16 pages.
Tech Target Contributor, “AI Accelerator”, Available online at: https://searchenterpriseai.techtarget.com/definition/AI-accelerator, Apr. 2018, 3 pages.
Tech With Brett, “Everything the Google Nest Hub Can Do”, Available online at: https://www.youtube.com/watch?v=x3vdytgru2E, Nov. 12, 2018, 13 pages.
Tech With Brett, “Google Home Multiple Users Setup”, Available online at: https://www.youtube.com/watch?v=BQOAbRUeFRo&t=257s, Jun. 29, 2017, 4 pages.
Tkachenko, Sergey, “Chrome will automatically create Tab Groups”, Available online at : https://winaero.com/chrome-will-automatically-create-tab-groups/, Sep. 18, 2020, 5 pages.
Tkachenko, Sergey, “Enable Tab Groups Auto Create in Google Chrome”, Available online at : https://winaero.com/enable-tab-groups-auto-create-in-google-chrome/, Nov. 30, 2020, 5 pages.
“Use Macrodroid skillfully to automatically clock in with Ding Talk”, Online available at: https://blog.csdn.net/qq_26614295/article/details/84304541, Nov. 20, 2018, 11 pages (Official Copy Only). {See communication under 37 CFR § 1.98(a) (3)}.
Vazquez et al., “An Assisted Photography Framework to Help Visually Impaired Users Properly Aim a Camera”, ACM Transactions on Computer-Human Interaction, vol. 21, No. 5, Article 25, Online available at: https://dl.acm.org/doi/pdf/10.1145/2651380, Nov. 2014, 29 pages.
Velian Speaks Tech, “10 Google Assistant Tips!”, Available online at: https://www.youtube.com/watch?v=3RNWA3NK9fs, Feb. 24, 2020, 3 pages.
Walker, Amy, “NHS Gives Amazon Free Use of Health Data Under Alexa Advice Deal”, Available online at: <https://www.theguardian.com/society/2019/dec/08/nhs-gives-amazon-free-use-of-health-data-under-alexa-advice-deal>, 3 pages.
Wang, et al., “Tacotron: Towards End to End Speech Synthesis”, Available online at: https://arxiv.org/abs/1703.10135, Apr. 6, 2017, 10 pages.
Wang, et al., “Training Deep Neural Networks with 8-bit Floating Point Numbers”, 32nd Conference on Neural Information Processing Systems (Neurl PS 2018), 2018, 10 pages.
Wei et al., “Design and Implement On Smart Home System”, 2013 Fourth International Conference on Intelligent Systems Design and Engineering Applications, Available online at: https://ieeexplore.ieee.org/document/6843433, 2013, pp. 229-231.
“What's on Spotify?”, Music for everyone, Online Available at:—<https://web.archive.org/web/20160428115328/https://www.spotify.com/us/>, Apr. 28, 2016, 6 pages.
Win, et al., “Myanmar Text to Speech System based on Tacotron-2”, International Conference on Information and Communication Tehcnology Convergence (ICTC), Oct. 21-23, 2020, pp. 578-583.
Wu et al., “Monophone-Based Background Modeling for Two-Stage On-device Wake Word Detection”, in 2018 IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP), Apr. 2018, 5 pages.
Xu et al., “Show, Attend and Tell: Neural Image Caption Generation with Visual Attention”, Proceedings of the 32nd International Conference on Machine Learning, Lille, France, 2015, 10 pages.
Young et al., “POMDP-Based Statistical Spoken Dialog Systems: A Review”, Proceedings of the IEEE, vol. 101, No. 5, 2013, 18 pages.
Zhang et al., “Interaction Proxies for Runtime Repair and Enhancement of Mobile Application Accessibility”, In Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems (CHI '17). ACM, Denver, CO, USA, Online available at: https://dl.acm.org/doi/pdf/10.1145/3025453.3025846, May 6-11, 2017, pp. 6024-6037.
Zhang et al., “Very Deep Convolutional Networks for End-To-End Speech Recognition”, IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP), 2017, 5 pages.
Zhao et al., “Big Data Analysis and Application”, Aviation Industry Press, Dec. 2015, pp. 236-241 (Official Copy Only). (See communication under 37 CFR § 1.98(a) (3)}.
Zhao et al., “CueSee: Exploring Visual Cues for People with Low Vision to Facilitate a Visual Search Task”, In Proceedings of the 2016 ACM International Joint Conference on Pervasive and Ubiquitous Computing. ACM, UbiComp '16, Heidelberg, Germany, Online available at: https://dl.acm.org/doi/pdf/10.1145/2971648.2971730, Sep. 12-16, 2016, pp. 73-84.
Zhao et al., “Enabling People with Visual Impairments to Navigate Virtual Reality with a Haptic and Auditory Cane Simulation”, In Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems (CHI '18). ACM, Article 116, Montréal, QC, Canada, Online available at: https://dl.acm.org/doi/pdf/10.1145/3173574.3173690, Apr. 21-26, 2018, 14 pages.
Zhao et al., “SeeingVR: A Set of Tools to Make Virtual Reality More Accessible to People with Low Vision”, In Proceedings of the 2019 CHI Conference on Human Factors in Computing Systems (CHI '19). ACM, Article 111, Glasgow, Scotland, UK, Online available at: https://dl.acm.org/doi/pdf/10.1145/3290605.3300341, May 4-9, 2019, 14 pages.
Zhao et al., “Transferring Age and Gender Attributes for Dimensional Emotion Prediction from Big Speech Data Using Hierarchical Deep Learning”, 2018 4th IEEE International Conference on Big Data Security on Cloud, 2018, pp. 20-24.
Zheng, et al., “Intent Detection and Semantic Parsing for Navigation Dialogue Language Processing”, 2017 IEEE 20th International Conference on Intelligent Transportation Systems (ITSC), 2017, 6 pages.
Zhou et al., “Learning Dense Correspondence via 3D-guided Cycle Consistency”, Proceedings of the IEEE Conference on Computer Vision and Pattern Recognition (CVPR), 2016, 10 pages.
Notice of Hearing received for Indian Patent Application No. 8904/CHENP/2012, mailed on Apr. 10, 2023, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8908/CHENP/2012, mailed on Apr. 10, 2023, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8909/CHENP/2012, mailed on Apr. 10, 2023, 2 pages.
Summons to Oral Proceedings received for European Patent Application No. 11707939.2, mailed on Aug. 24, 2022, 14 pages.
Decision to Grant received for Russian Patent Application No. 2018112505, mailed on Oct. 14, 2022, 25 pages (9 pages of English Translation and 16 pages of Official Copy).
Final Office Action received for U.S. Appl. No. 16/912,278, mailed on Nov. 10, 2022, 10 pages.
Notice of Acceptance received for Australian Patent Application No. 2020257070, mailed on Jun. 9, 2022, 3 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/879,643, mailed on Jun. 2, 2022, 2 pages.
Notice of Allowance received for Mexican Patent Application No. MX/a/2017/006911, mailed on Sep. 9, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Office Action received for Australian Patent Application No. 2021240130, mailed on Oct. 4, 2022, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2021202350, mailed on Nov. 15, 2022, 3 pages.
Final Office Action received for U.S. Appl. No. 16/912,278, mailed on Aug. 16, 2023, 5 pages.
Office Action received for Japanese Patent Application No. 2022-114276, mailed on Aug. 7, 2023, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Notice of Allowance received for Canadian Patent Application No. 3,077,914, mailed on Feb. 10, 2023, 1 page.
Notice of Allowance received for Korean Patent Application No. 10-2022-7026740, mailed on Mar. 23, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/912,278, mailed on May 3, 2023, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8902/CHENP/2012, mailed on May 1, 2023, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8903/CHENP/2012, mailed on May 1, 2023, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8910/CHENP/2012, mailed on May 1, 2023, 2 pages.
Aaaaplay, “Sony Media Remote for iOS and Android”, Online available at: <https://www.youtube.com/watch?v=W8QoeQhlGok>, Feb. 4, 2012, 3 pages.
Advisory Action received for U.S. Appl. No. 13/492,809, mailed on Nov. 10, 2014, 5 pages.
Advisory Action received for U.S. Appl. No. 13/913,336, mailed on Feb. 20, 2018, 3 pages.
“Alexa, Turn Up the Heat!, Smartthings Samsung [online]”, Online available at:—<https://web.archive.org/web/20160329142041/https://blog.smartthings.com/news/smartthingsupdates/alexa-turn-up-the-heat/>, Mar. 3, 2016, 3 pages.
Alfred App, “Alfred”, Online available at:—<http://www.alfredapp.com/>, retrieved on Feb. 8, 2012, 5 pages.
Anania Peter, “Amazon Echo with Home Automation (Smartthings)”, Online available at:—<https://www.youtube.com/watch?v=LMW6aXmsWNE>, Dec. 20, 2015, 1 page.
Android Authority, “How to use Tasker: A Beginner's Guide”, Online available at:—<https://youtube.com/watch?v= rDpdS_YWzFc>, May 1, 2013, 1 page.
Apple, “VoiceOver for Os X”, Online available at:—<http://www.apple.com/accessibility/voiceover/>, May 19, 2014, pp. 1-3.
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/352,410, mailed on Mar. 18, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/879,643, mailed on Mar. 29, 2022, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/879,643, mailed on Sep. 27, 2021, 2 pages.
Asakura et al., “What LG thinks; How the TV should be in the Living Room”, HiVi, vol. 31, No. 7, Stereo Sound Publishing, Inc., Jun. 17, 2013, pp. 68-71.
Ashingtondctech & Gaming, “SwipeStatusBar—Reveal the Status Bar in a Fullscreen App”, Online Available at: <https://www.youtube.com/watch?v=wA_tT9IAreQ>, Jul. 1, 2013, 3 pages.
“Ask Alexa—Things That Are Smart Wiki”, Online available at:—<http://thingsthataresmart.wiki/index.php?title=Ask_Alexa&oldid=4283>, Jun. 8, 2016, pp. 1-31.
Automate Your Life, “How to Setup Google Home Routines—A Google Home Routines Walkthrough”, Online Available at: <https://www.youtube.com/watch?v=pXokZHP9kZg>, Aug. 12, 2018, 1 page.
Bell, Jason, “Machine Learning Hands-On for Developers and Technical Professionals”, Wiley, 2014, 82 pages.
Bellegarda, Jeromer, “Chapter 1: Spoken Language Understanding for Natural Interaction: The Siri Experience”, Natural Interaction with Robots, Knowbots and Smartphones, 2014, pp. 3-14.
Bellegarda, Jeromer, “Spoken Language Understanding for Natural Interaction: The Siri Experience”, Slideshow retrieved from : <https://www.uni-ulm.de/fileadmin/website_uni_ulm/iui.iwsds2012/files/Bellegarda.pdf>, International Workshop on Spoken Dialog Systems (IWSDS), May 2012, pp. 1-43.
Beointegration.com, “BeoLink Gateway—Programming Example”, Online Available at: <https:/ /www.youtube.com/watch?v=TXDaJFm5UH4>, Mar. 4, 2015, 3 pages.
Board Decision received for Chinese Patent Application No. 201480030811.4, mailed on Feb. 1, 2021, 44 pages.
Board Opinion received for Chinese Patent Application No. 201480030811.4, mailed on May 13, 2020, 23 pages.
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 11707939.2, mailed on Oct. 9, 2020, 18 pages.
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 16188272.5, mailed on Dec. 2, 2021, 1 page.
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 16188272.5, mailed on Nov. 24, 2021, 21 pages.
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 16188272.5, mailed on Oct. 19, 2021, 2 pages.
Burgess, Brian, “Amazon Echo Tip: Enable the Wake Up Sound”, Online available at :—<https://www.groovypost.com/howto/amazon-echo-tip-enable-wake-up-sound/>, Jun. 30, 2015, 4 pages.
Butcher, Mike, “EVI Arrives in Town to go Toe-to-Toe with Siri”, TechCrunch, Jan. 23, 2012, pp. 1-2.
Cambria et al., “Jumping NLP curves: A Review of Natural Language Processing Research.”, IEEE Computational Intelligence magazine, 2014, vol. 9, May 2014, pp. 48-57.
Caraballo et al., “Language Identification Based on a Discriminative Text Categorization Technique”, Iberspeech 2012—VII Jornadas En Tecnologia Del Habla and Ill Iberian Sltech Workshop, Nov. 21, 2012, pp. 1-10.
Castleos, “Whole House Voice Control Demonstration”, Online available at:—<https://www.youtube.com/watch?v=9SRCoxrZ_W4>, Jun. 2, 2012, 1 pages.
Chang et al., “Monaural Multi-Talker Speech Recognition with Attention Mechanism and Gated Convolutional Networks”, Interspeech 2018, Sep. 2-6, 2018, pp. 1586-1590.
Chen et al., “A Convolutional Neural Network with Dynamic Correlation Pooling”, 13th International Conference on Computational Intelligence and Security, IEEE, 2017, pp. 496-499.
Chen et al., “Progressive Joint Modeling in Unsupervised Single-Channel Overlapped Speech Recognition”, IEEE/ACM Transactions On Audio, Speech, and Language Processing, vol. 26, No. 1, Jan. 2018, pp. 184-196.
Chen, Yi, “Multimedia Siri Finds and Plays Whatever You Ask For”, PSFK Report, Feb. 9, 2012, pp. 1-9.
Cheyer et al., “Demonstration Video of Multimodal Maps Using an Open-Agent Architecture”, published by SRI International no later than 1996, as depicted in Exemplary Screenshots from video entitled 'Demonstration Video of Multimodal Maps Using an Open-Agent Architecture, 6 pages.
Cheyer, Adam, “Adam Cheyer—About”, Online available at:—<http://www.adam.cheyer.com/about.html>, retrieved on Sep. 17, 2012, pp. 1-2.
Colt, Sam, “Here's One Way Apple's Smartwatch Could Be Better Than Anything Else”, Business Insider, Aug. 21, 2014, pp. 1-4.
Conneau et al., “Supervised Learning of Universal Sentence Representations from Natural Language Inference Data”, Proceedings of the 2017 Conference on Empirical Methods in Natural Language Processing, Copenhagen, Denmark, Sep. 7-11, 2017, pp. 670-680.
Czech Lucas, “A System for Recognizing Natural Spelling of English Words”, Diploma Thesis, Karlsruhe Institute of Technology, May 7, 2014, 107 pages.
Decision of Appeal received for Japanese Patent Application No. 2012-549003, mailed on Jun. 26, 2017, 138 pages.
Decision on Appeal received for Korean Patent Application No. 10-2015-7035370, mailed on Jun. 7, 2019, 13 pages.
Decision to Grant received for Russian Patent Application No. 2012135502, mailed on Sep. 11, 2014, 15 pages.
Decision to Grant received for Russian Patent Application No. 2012144606, mailed on Nov. 19, 2014, 13 pages.
Decision to Grant received for Russian Patent Application No. 2012144639, mailed on Nov. 28, 2014, 10 pages.
Decision to Grant received for Russian Patent Application No. 2012144643, mailed on Nov. 20, 2014, 13 pages.
Decision to Grant received for Russian Patent Application No. 2012144647, mailed on Jan. 27, 2015, 16 pages.
Decision to Grant received for Russian Patent Application No. 2012144648, mailed on Nov. 19, 2014, 14 pages.
Decision to Grant received for Russian Patent Application No. 2015120954, mailed on Feb. 14, 2018, 20 pages.
Decision to Refuse received for European Patent Application No. 11707939.2, mailed on Dec. 16, 2020, 31 pages.
Decision to Refuse received for European Patent Application No. 14737370.8, mailed on Jun. 26, 2019, 18 pages.
Decision to Refuse received for European Patent Application No. 16188272.5, mailed on Dec. 9, 2021, 2 pages.
Decision to Refuse received for Russian Patent Application No. 2012144640, mailed on Nov. 28, 2014, 8 pages.
Deedeevuu, “Amazon Echo Alarm Feature”, Online available at:—<https://www.youtube.com/watch?v=fdjU8eRLk7c>, Feb. 16, 2015, 1 page.
Delcroix et al., “Context Adaptive Deep Neural Networks For Fast Acoustic Model Adaptation”, ICASSP, 2015, pp. 4535-4539.
Delcroix et al., “Context Adaptive Neural Network for Rapid Adaptation of Deep CNN Based Acoustic Models”, Interspeech 2016, Sep. 8-12, 2016, pp. 1573-1577.
Derrick, Amanda, “How to Set Up Google Home for Multiple Users”, Lifewire, Online available at:—<https://www.lifewire.com/set-up-google-home-multiple-users-4685691>, Jun. 8, 2020, 9 pages.
Dihelson, “How Can I Use Voice or Phrases as Triggers to Macrodroid?”, Macrodroid Forums, Online Available at:—<https://www.tapatalk.com/groups/macrodroid/how-can-i-use-voice-or-phrases-as-triggers-to-macr-t4845.html>, May 9, 2018, 5 pages.
“Directv™ Voice”, Now Part of the DIRECTTV Mobile App for Phones, Sep. 18, 2013, 5 pages.
Earthling 1984, “Samsung Galaxy Smart Stay Feature Explained”, Online available at :—<https://www.youtube.com/watch?v=RpjBNtSjupl>, May 29, 2013, 1 page.
Eder et al., “At the Lower End of Language—Exploring the Vulgar and Obscene Side of German”, Proceedings of the Third Workshop on Abusive Language Online, Florence, Italy, Aug. 1, 2019, pp. 119-128.
Evi, “Meet Evi: The One Mobile Application that Provides Solutions for your Everyday Problems”, Feb. 2012, 3 pages.
Ex Parte Quayle Action received for U.S. Appl. No. 13/725,713, mailed on Dec. 18, 2013, 5 pages.
Extended European Search Report received for European Patent Application No. 11707939.2, mailed on Nov. 18, 2016, 13 pages.
Extended European Search Report received for European Patent Application No. 14737370.8, mailed on May 19, 2016, 12 pages.
Extended European Search Report received for European Patent Application No. 16188272.5, mailed on Nov. 18, 2016, 12 pages.
Extended European Search Report received for European Patent Application No. 18202474.5, mailed on Feb. 12, 2019, 9 pages.
Extended European Search Report received for European Patent Application No. 19195766.1, mailed on Oct. 8, 2019, 15 pages.
Filipowicz, Luke, “How to use the QuickType keyboard in iOS 8”, Online available at:—<https://www.imore.com/comment/568232>, Oct. 11, 2014, pp. 1-17.
Final Office Action received for U.S. Appl. No. 12/987,982, mailed on Jul. 25, 2014, 21 pages.
Final Office Action received for U.S. Appl. No. 13/492,809, mailed on Feb. 9, 2016, 11 pages.
Final Office Action received for U.S. Appl. No. 13/492,809, mailed on May 22, 2014, 10 pages.
Final Office Action received for U.S. Appl. No. 13/725,481, mailed on Dec. 19, 2013, 16 pages.
Final Office Action received for U.S. Appl. No. 13/725,550, mailed on Nov. 13, 2013, 10 pages.
Final Office Action received for U.S. Appl. No. 13/725,616, mailed on Nov. 15, 2013, 8 pages.
Final Office Action received for U.S. Appl. No. 13/725,742, mailed on Nov. 18, 2013, 6 pages.
Final office action received for U.S. Appl. No. 13/725,761, mailed on Dec. 19, 2013, 13 pages.
Final office action received for U.S. Appl. No. 13/725,761, mailed on Jul. 11, 2014, 5 pages.
Final Office Action received for U.S. Appl. No. 13/784,707, mailed on Nov. 6, 2013, 12 pages.
Final Office Action received for U.S. Appl. No. 13/913,336, mailed on Oct. 24, 2017, 9 pages.
Final Office Action received for U.S. Appl. No. 15/394,162, mailed on Oct. 29, 2019, 17 pages.
Final Office Action received for U.S. Appl. No. 16/879,643, mailed on Dec. 15, 2021, 14 pages.
Findlater et al., “Beyond QWERTY: Augmenting Touch-Screen Keyboards with Multi-Touch Gestures for Non-Alphanumeric Input”, CHI '12, May 5-10, 2012, 4 pages.
Gadget Hacks, “Tasker Too Complicated? Give MacroDroid a Try [How-To]”, Online available at: <https://www.youtube.com/watch?v=8YL9cWCykKc>, May 27, 2016, 1 page.
“Galaxy S7: How to Adjust Screen Timeout & Lock Screen Timeout”, Online available at :—<https://www.youtube.com/watch?v=n6e1WKUS2ww>, Jun. 9, 2016, 1 page.
Ghauth et al., “Text Censoring System for Filtering Malicious Content Using Approximate String Matching and Bayesian Filtering”, Proc. 4th INNS Symposia Series on Computational Intelligence in Information Systems, Bandar Seri Begawan, Brunei, 2015, pp. 149-158.
Google Developers,“Voice search in your app”, Online available at:—<https://www.youtube.com/watch?v=PS1FbB5qWEI>, Nov. 12, 2014, 1 page.
Guim, Mark, “How to Set a Person-Based Reminder with Cortana”, Online available at:—<http://www.wpcentral.com/how-to-person-based-reminder-cortana>, Apr. 26, 2014, 15 pages.
Gupta et al., “I-vector-based Speaker Adaptation of Deep Neural Networks for French Broadcast Audio Transcription”, ICASSP, 2014, 2014, pp. 6334-6338.
Gupta, Naresh, “Inside Bluetooth Low Energy”, Artech House, 2013, 274 pages.
Hardawar, Devindra, “Driving App Waze Builds its own Siri for Hands-Free Voice Control”, Online available at:—<http://venturebeat.com/2012/02/09/driving-app-waze-builds-its-own-siri-for-hands-free-voice-control/>, retrieved on Feb. 9, 2012, 4 pages.
Hashimoto, Yoshiyuki, “Simple Guide for iPhone Siri, which can be Operated with your Voice”, Shuwa System Co., Ltd., vol. 1, Jul. 5, 2012, pp. 8, 130, 131.
Hayashi et al., “Internet Information Navigation Service Titan”, NTT Technology Journal, JPN, vol. 8, No. 8, Aug. 1996, pp. 20-23.
“Headset Button Controller v7.3 APK Full APP Download for Andriod, Blackberry, iPhone”, Online available at:—<http://fullappdownload.com/headset-button-controller-v7-3-apk/>, Jan. 27, 2014, 11 pages.
Hershey et al., “Deep Clustering: Discriminative Embeddings for Segmentation and Separation”, Proc. ICASSP, Mar. 2016, 6 pages.
“Hey Google: How to Create a Shopping List with Your Google Assistant”, Online available at :—<https://www.youtube.com/watch?v=w9NCsElax1Y>, May 25, 2018, 1 page.
“How to Enable Google Assistant on Galaxy S7 and Other Android Phones (No Root)”, Online available at :—<https://www.youtube.com/watch?v=HekIQbWyksE>, Mar. 20, 2017, 1 page.
“How to Use Ok Google Assistant Even Phone is Locked”, Online available at:—<https://www.youtube.com/watch?v=9B_gP4j_SP8>, Mar. 12, 2018, 1 page.
Hutsko et al., “iPhone All-in-One For Dummies”, 3rd Edition, 2013, 98 pages.
id3.org, “id3v2.4.0-Frames”, Online available at:—<http://id3.org/id3v2.4.0-frames?action=print>, retrieved on Jan. 22, 2015, pp. 1-41.
Ikeda, Masaru, “beGLOBAL SEOUL 2015 Startup Battle: Talkey”, YouTube Publisher, Online Available at:—<https://www.youtube.com/watch?v=4Wkp7sAAldg>, May 14, 2015, 1 page.
Inews and Tech, “How To Use The QuickType Keyboard In IOS 8”, Online available at :—<http://www.inewsandtech.com/how-to-use-the-quicktype-keyboard-in-ios-8/>, Sep. 17, 2014, 6 pages.
“Interactive Voice”, Online available at:—<http://www.helloivee.com/company/>, retrieved on Feb. 10, 2014, 2 pages.
Intention to Grant received for Indian Patent Application No. 6734CHENP2012, mailed on Feb. 15, 2022, 2 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/020861, mailed on Aug. 2, 2012, 11 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/040961, mailed on Dec. 17, 2015, 20 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/040961, mailed on Mar. 10, 2015, 5 pages.
Internet Services and Social Net, “How to Search for Similar Websites”,Online available at:—<https://www.youtube.com/watch ?v=nLf2uirpt5s>, see from 0:17 to 1:06, Jul. 4, 2013, 1 page.
Invitation to Pay Additional Fees received for PCT Application No. PCT/US2014/040961, mailed on Jan. 14, 2015, 3 pages.
“iPhone 6 Smart Guide Full Version for SoftBank”, Gijutsu-Hyohron Co., Ltd., vol. 1, Dec. 1, 2014, 4 pages.
Isik et al., “Single-Channel Multi-Speaker Separation using Deep Clustering”, Interspeech 2016, Sep. 8-12, 2016, pp. 545-549.
Jonsson et al., “Proximity-based Reminders Using Bluetooth”, 2014 IEEE International Conference on Pervasive Computing and Communications Demonstrations, 2014, pp. 151-153.
Jouvet et al., “Evaluating Grapheme-to-phoneme Converters in Automatic Speech Recognition Context”, IEEE, 2012, pp. 4821-4824.
Kanda et al., “Robust Domain Selection Using Dialogue History in Multi-domain Spoken Dialogue Systems”, Journal of Information Processing Society, vol. 48, No. 5, May 15, 2007, pp. 1980-1989.
Kanda et al., “Spoken Language Understanding Using Dialogue Context in Database Search Task”, Journal of Information Processing Society, vol. 47, No. 6, Jun. 6, 2006, pp. 1802-1811.
Karn, Ujjwal, “An Intuitive Explanation of Convolutional Neural Networks”, The Data Science Blog, Aug. 11, 2016, 23 pages.
Kastrenakes, Jacob, “Siri's creators will unveil their new AI bot on Monday”, The Verge, Online available at:—<https://web.archive.org/web/20160505090418/https://www.theverge.com/2016/5/4/11593564/viv-labs-unveiling-monday-new-ai-from-siri-creators>, May 4, 2016, 3 pages.
Kawamae et al., “Study on the Structure of Index Data for Metasearch System”, Material of 38th SIG of Artificial Intelligence Foundation & 45th SIG of Knowledge Base System, JPN, Sep. 29, 1999, pp. 37-42.
Kazmucha Allyson, “How to Send Map Locations Using iMessage”, iMore.com,Online available at:—<http://www.imore.com/how-use-imessage-share-your-location-your-iphone>, Aug. 2, 2012, 6 pages.
Kickstarter, “Ivee Sleek: Wi-Fi Voice-Activated Assistant”, Online available at:—<https://www.kickstarter.com/projects/ivee/ivee-sleek-wi-fi-voice-activated-assistant>, retrieved on Feb. 10, 2014, pp. 1-13.
King et al., “Robust Speech Recognition Via Anchor Word Representations”, Interspeech 2017, Aug. 20-24, 2017, pp. 2471-2475.
Komatani et al., “Multi-domain Spoken Dialogue System with Extensibility and Robustness Against Speech Recognition Errors”, Proceedings of the 7th SIGdial Workshop on Discourse and Dialogue, Association for Computational Linguistics, Jul. 2006, pp. 9-17.
Lee, Sungjin, “Structured Discriminative Model For Dialog State Tracking”, Proceedings of the SIGDIAL 2013 Conference, Aug. 22-24, 2013, pp. 442-451.
“Link Your Voice to Your Devices with Voice Match, Google Assistant Help”, Online available at <https://support.google.com/assistant/answer/9071681?co=GENIE.Platform%3DAndroid&hl=en>, Retrieved on Jul. 1, 2020, 2 pages.
Liou et al., “Autoencoder for Words”, Neurocomputing, vol. 139, Sep. 2014, pp. 84-96.
Liu et al., “Accurate Endpointing with Expected Pause Duration”, Sep. 6-10, 2015, pp. 2912-2916.
Loukides et al., “What Is the Internet of Things?”, O'Reilly Media, Inc., Online Available at: <https://www.oreilly.com/library/view/what-is-the/9781491975633/>, 2015, 31 pages.
Luo et al., “Speaker-Independent Speech Separation With Deep Attractor Network”, IEEE/ACM Transactions on Audio, Speech, and Language Processing, vol. 26, No. 4, Apr. 2018, pp. 787-796.
Marketing Land, “Amazon Echo: Play music”, Online Available at:—<https://www.youtube.com/watch?v=A7V5NPbsXi4>, Apr. 27, 2015, 3 pages.
“Meet Ivee, Your Wi-Fi Voice Activated Assistant”, Availale Online at:—<http://www.helloivee.com/>, retrieved on Feb. 10, 2014, 8 pages.
“Mel Scale”, Wikipedia the Free Encyclopedia, last modified on Oct. 13, 2009 and retrieved on Jul. 28, 2010, available online <http://en.wikipedia.org/wiki/Mel_scale>, 2 pages.
Mhatre et al., “Donna Interactive Chat-bot acting as a Personal Assistant”, International Journal of Computer Applications (0975-8887), vol. 140, No. 10, Apr. 2016, 6 pages.
Mikolov et al., “Linguistic Regularities in Continuous Space Word Representations”, Proceedings of NAACL-HLT, Jun. 9-14, 2013, pp. 746-751.
Miller Chance, “Google Keyboard Updated with New Personalized Suggestions Feature”, Online available at:—<http://9to5google.com/2014/03/19/google-keyboard-updated-with-new-personalized-suggestions-feature/>, Mar. 19, 2014, 4 pages.
“Minimum Phase”, Wikipedia the free Encyclopedia, Last Modified on Jan. 12, 2010 and retrieved on Jul. 28, 2010, available online at <http://en.wikipedia.org/wiki/Minimum_phase>, 8 pages.
Minutes of the Oral Proceedings received for European Patent Application No. 11707939.2, mailed on Dec. 15, 2020, 9 pages.
Minutes of the Oral Proceedings received for European Patent Application No. 14737370.8, mailed on Jun. 26, 2019, 3 pages.
“Mobile Speech Solutions, Mobile Accessibility”, SVOX AG Product Information Sheet, Online available at:—<http://www.svox.com/site/bra840604/con782768/mob965831936.aSQ?osLang=1>, Sep. 27, 2012, 1 page.
Modern Techies, “Braina-Artificial Personal Assistant for PC(like Cortana, Siri)!!!!”, Online available at: <https://www.youtube.com/watch?v=_Coo2P8ilqQ>, Feb. 24, 2017, 3 pages.
Morrison Jonathan, “iPhone 5 Siri Demo”, Online Available at:—<https://www.youtube.com/watch?v =_wHWwG5IhWc>, Sep. 21, 2012, 3 pages.
My Cool Aids, “What's New”, Online available at :—<http://www.mycoolaids.com/>, 2012, 1 page.
Nakamura et al., “Study of Information Clouding Methods to Prevent Spoilers of Sports Match”, Proceedings of the International Working Conference on Advanced Visual Interfaces (AVI' 12), ISBN: 978-1-4503-1287-5, May 2012, pp. 661-664.
Nakamura et al., “Study of Methods to Diminish Spoilers of Sports Match: Potential of a Novel Concept “Information Clouding””, vol. 54, No. 4, ISSN: 1882-7764. Online available at: <https://ipsj.ixsq.nii.ac.jp/ej/index.php?active_action=repository_view_main_item_detail&page_id=13&block_id=8&item_id=91589&item_no=1>, Apr. 2013, pp. 1402-1412.
“Natural Language Interface Using Constrained Intermediate Dictionary of Results”, List of Publications Manually reviewed for the Search of U.S. Pat. No. 7,177,798, Mar. 22, 2013, 1 page.
NDTV, “Sony SmartWatch 2 Launched in India for Rs. 14,990”, available at <http://gadgets.ndtv.com/others/news/sony-smartwatch-2-launched-in-india-for-rs-14990-420319>, Sep. 18, 2013, 4 pages.
Nguyen et al., “Generic Manager for Spoken Dialogue Systems”, In DiaBruck: 7th Workshop on the Semantics and Pragmatics of Dialogue, Proceedings, 2003, 2 pages.
Non Final Office Action received for U.S. Appl. No. 13/725,481, mailed on Jul. 5, 2013, 13 pages.
Non Final Office Action received for U.S. Appl. No. 13/725,550, mailed on Apr. 16, 2013, 8 pages.
Non Final Office Action received for U.S. Appl. No. 13/725,616, mailed on Jun. 28, 2013, 9 pages.
Non Final Office Action received for U.S. Appl. No. 13/725,713, mailed on Jul. 5, 2013, 14 pages.
Non Final Office Action received for U.S. Appl. No. 13/725,742, mailed on Jun. 27, 2013, 9 pages.
Non Final office action received for U.S. Appl. No. 13/725,761, mailed on Jul. 2, 2013, 12 pages.
Non Final Office Action received for U.S. Appl. No. 13/784,694, mailed on May 23, 2013, 7 pages.
Non Final Office Action received for U.S. Appl. No. 13/784,694, mailed on Oct. 10, 2013, 9 pages.
Non Final Office Action received for U.S. Appl. No. 13/784,707, mailed on Jul. 11, 2013, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 12/987,982, mailed on Dec. 2, 2013, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 12/987,982, mailed on Mar. 5, 2015, 24 pages.
Non-Final Office Action received for U.S. Appl. No. 12/987,982, mailed on Mar. 14, 2013, 28 pages.
Non-Final Office Action received for U.S. Appl. No. 13/492,809, mailed on Jun. 11, 2015, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 13/492,809, mailed on Mar. 7, 2013, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 13/492,809, mailed on Nov. 27, 2013, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 13/725,512 , mailed on Jul. 26, 2013, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 13/725,656, mailed on Mar. 27, 2013, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 13/913,336, mailed on Jan. 30, 2017, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 13/913,336, mailed on Jul. 2, 2018, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 15/394,162, mailed on Feb. 28, 2019, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 16/352,410, mailed on Dec. 2, 2019, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 16/879,643, mailed on Aug. 19, 2021, 12 pages.
Notice of Acceptance received for Australian Patent Application No. 2017204217, mailed on Oct. 8, 2018, 3 pages.
Notice of Acceptance received for Australian Patent application No. 2011205426, mailed on Jan. 6, 2014, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2013205568, mailed on May 20, 2015, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2013205569, mailed on Feb. 15, 2016, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2013205571, mailed on Jun. 1, 2015, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2013205586, mailed on Aug. 6, 2015, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2013205588, mailed on Feb. 12, 2016, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2013205590, mailed on May 20, 2015, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2013205591, mailed on Feb. 12, 2016, 2 pages.
Notice of Acceptance received for Australian Patent application No. 2014274913, mailed on May 1, 2017, 3 pages.
Notice of Acceptance received for Australian Patent application No. 2016204262, mailed on Dec. 22, 2017, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2018202411, mailed on Sep. 18, 2019, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2019200296, mailed on Sep. 5, 2019, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2019283968, mailed on Jan. 25, 2021, 3 pages.
Notice of Acceptance received for Canadian Patent application No. 2,793,118, mailed on May 12, 2017, 1 page.
Notice of Acceptance received for U.S. Patent Application No. 2013205584, mailed on Mar. 9, 2016, 2 pages.
Notice of Allowance received for Brazilian Patent Application No. 112012017826-1, mailed on Oct. 20, 2020, 2 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028965-5, mailed on Jan. 19, 2021, 2 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028966-3, mailed on Jan. 26, 2021, 2 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028968-0, mailed on Jan. 19, 2021, 3 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028969-8, mailed on Oct. 20, 2020, 3 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028970-1, mailed on Jan. 19, 2021, 2 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028971-0, mailed on Jan. 26, 2021, 3 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028972-8, mailed on Jan. 26, 2021, 2 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028973-6, mailed on Jan. 26, 2021, 2 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122012028974-4, mailed on Jan. 26, 2021, 3 pages.
Notice of Allowance received for Canadian Patent Application No. 2,787,351, mailed on Aug. 6, 2015, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,791,791, mailed on Aug. 9, 2016, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,792,412, mailed on Sep. 14, 2015, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,792,442, mailed on Feb. 4, 2016, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,792,570, mailed on Sep. 16, 2015, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,793,002, mailed on Feb. 23, 2016, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,793,248, mailed on Aug. 24, 2016, 2 pages.
Notice of Allowance received for Canadian Patent Application No. 2,793,741, mailed on Sep. 16, 2015, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,793,743, mailed on May 20, 2015, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,954,559, mailed on Jun. 14, 2018, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,954,559, mailed on Oct. 20, 2017, 1 page.
Notice of Allowance received for Canadian Patent Application No. 3,000, 109, mailed on Oct. 16, 2019, 1 page.
Notice of Allowance received for Chinese Patent Application No. 201610126045.2, mailed on Jul. 16, 2019, 2 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127579, mailed on Sep. 16, 2016, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127580, mailed on Jun. 30, 2017, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127581, mailed on May 21, 2018, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127582, mailed on Jun. 24, 2016, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127583, mailed on May 27, 2016, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127584, mailed on May 30, 2016, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127585, mailed on Jul. 10, 2017, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127586, mailed on May 9, 2016, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2014-127587, mailed on May 21, 2018, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2017-117880, mailed on Feb. 12, 2019, 4 pages.
Notice of Allowance received for Japanese Patent Application No. 2018-050944, mailed on Dec. 22, 2020, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7021659, mailed on Jan. 20, 2016, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7028786, mailed on Feb. 27, 2015, 2 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7028802, mailed on Feb. 27, 2015, 2 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7028805, mailed on Aug. 28, 2015, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7029183, mailed on Dec. 16, 2015, 5 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7029195, mailed on May 30, 2016, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7029197, mailed on Feb. 27, 2015, 2 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7029381, mailed on Nov. 27, 2015, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7029382, mailed on Nov. 20, 2015, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7029385, mailed on Aug. 21, 2015, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2016-7023962, mailed on May 31, 2017, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2017-7024596, mailed on Dec. 19, 2018, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2017-7035711, mailed on Mar. 28, 2019, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2019-7007971, mailed on Dec. 26, 2019, 5 pages.
Notice of Allowance received for Korean Patent Application No. 10-2019-7018332, mailed on Sep. 28, 2020, 7 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-7008719, mailed on Jun. 17, 2020, 5 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-7023927, mailed on May 27, 2021, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-7037138, mailed on Nov. 24, 2021, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2021-7027594, mailed on Mar. 14, 2022, 4 pages.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011794, mailed on Nov. 19, 2014, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011795, mailed on Nov. 20, 2014, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011797, mailed on Nov. 20, 2014, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011798, mailed on Nov. 28, 2014, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011799, mailed on Nov. 27, 2014, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011800, mailed on Feb. 9, 2016, 2 pages.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011803, mailed on Nov. 28, 2014, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011807, mailed on Nov. 28, 2014, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011808, mailed on Jan. 23, 2015, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2015/004983, mailed on Dec. 16, 2015, 2 pages.
Notice of Allowance received for Mexican Patent Application No. MX/a/2015/004983, mailed on Jun. 10, 2016, 1 page.
Notice of Allowance received for Mexican Patent Application No. MX/a/2016/011562, mailed on Mar. 31, 2017, 1 page.
Notice of Allowance received for Russian Patent Application No. 2012144637, mailed on Oct. 17, 2014, 15 pages.
Notice of Allowance received for U.S. Appl. No. 12/987,982, mailed on Dec. 15, 2015, 9 pages.
Notice of Allowance received for U.S. Appl. No. 13/492,809, mailed on Sep. 8, 2016, 14 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,481, mailed on Jul. 23, 2014, 7 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,481, mailed on May 12, 2014, 7 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,512 , mailed on Dec. 17, 2013, 9 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,550, mailed on Jun. 11, 2014, 10 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,550, mailed on Sep. 18, 2014, 10 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,616, mailed on Apr. 3, 2014, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,616, mailed on Jul. 17, 2014, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,656, mailed on Dec. 4, 2013, 10 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,656, mailed on Jul. 10, 2013, 10 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,713, mailed on Jan. 30, 2014, 5 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,742, mailed on Feb. 19, 2014, 7 pages.
Notice of Allowance received for U.S. Appl. No. 13/725,761, mailed on Apr. 10, 2015, 5 pages.
Notice of Allowance received for U.S. Appl. No. 13/784,694, mailed on Aug. 1, 2014, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/784,694, mailed on Feb. 21, 2014, 7 pages.
Notice of Allowance received for U.S. Appl. No. 13/784,694, mailed on Jun. 2, 2014, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/784,707, mailed on Feb. 20, 2014, 7 pages.
Notice of Allowance received for U.S. Appl. No. 13/784,707, mailed on Mar. 20, 2014, 2 pages.
Notice of Allowance received for U.S. Appl. No. 13/913,336, mailed on Dec. 14, 2018, 9 pages.
Notice of Allowance received for U.S. Appl. No. 15/394,162, mailed on Feb. 20, 2020, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/352,410, mailed on Mar. 26, 2020, 8 pages.
Notice of Allowance received for U.S. Appl. No. 16/879,643, mailed on Apr. 29, 2022, 10 pages.
Notice of Hearing received for Indian Patent Application No. 8905/CHENP/2012, mailed on Aug. 13, 2020, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8906/CHENP/2012, mailed on May 11, 2021, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8907/CHENP/2012, mailed on Feb. 3, 2021, 2 pages.
Notification to Grant received for Chinese Patent Application No. 201180013559.2, mailed on Jan. 18, 2016, 3 pages.
Office Action received for Australian Patent Application No. 2013205568, mailed on Feb. 13, 2015, 3 pages.
Office Action received for Australian Patent application No. 2013205569, mailed on Feb. 16, 2015, 3 pages.
Office Action received for Australian Patent application No. 2013205571, mailed on Feb. 16, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2013205584, mailed on Dec. 7, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2013205584, mailed on Feb. 18, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2013205585, mailed on Feb. 19, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2013205586, mailed on Feb. 17, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2013205588, mailed on Feb. 17, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2013205590, mailed on Feb. 16, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2013205591, mailed on Feb. 16, 2015, 3 pages.
Office Action received for Australian Patent Application No. 2014274913, mailed on Aug. 5, 2016, 3 pages.
Office Action received for Australian Patent Application No. 2016204262, mailed on Feb. 24, 2017, 3 pages.
Office Action received for Australian Patent Application No. 2017204217, mailed on Feb. 12, 2018, 3 pages.
Office Action received for Australian Patent Application No. 2018202411, mailed on Jan. 23, 2019, 2 pages.
Office Action received for Australian Patent Application No. 2019200296, mailed on Jul. 19, 2019, 2 pages.
Office Action received for Australian Patent Application No. 2019283923, mailed on Jul. 29, 2021, 6 pages.
Office Action received for Australian Patent Application No. 2019283923, mailed on Jun. 2, 2021, 4 pages.
Office Action received for Australian Patent Application No. 2019283923, mailed on Sep. 25, 2020, 4 pages.
Office Action received for Australian Patent Application No. 2019283968, mailed on Jul. 24, 2020, 3 pages.
Office Action received for Australian Patent Application No. 2020257070, mailed on Oct. 14, 2021, 4 pages.
Office Action received for Australian Patent Application No. 2021202350, mailed on Apr. 12, 2022, 3 pages.
Office Action received for Brazilian Patent Application No. 112012017826-1, mailed on Sep. 6, 2019, 5 pages.
Office Action received for Brazilian Patent Application No. BR122012028965-5, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028965-5, mailed on Oct. 9, 2020, 5 pages.
Office Action received for Brazilian Patent Application No. BR122012028966-3, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028966-3, mailed on Oct. 9, 2020, 5 pages.
Office Action received for Brazilian Patent Application No. BR122012028968-0, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028968-0, mailed on Oct. 9, 2020, 5 pages.
Office Action received for Brazilian Patent Application No. BR122012028969-8, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028970-1, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028970-1, mailed on Oct. 9, 2020, 5 pages.
Office Action received for Brazilian Patent Application No. BR122012028971-0, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028971-0, mailed on Oct. 9, 2020, 5 pages.
Office Action received for Brazilian Patent Application No. BR122012028972-8, mailed on Sep. 4, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028973-6, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028973-6, mailed on Oct. 9, 2020, 5 pages.
Office Action received for Brazilian Patent Application No. BR122012028974-4, mailed on May 27, 2020, 6 pages.
Office Action received for Brazilian Patent Application No. BR122012028974-4, mailed on Oct. 9, 2020, 5 pages.
Office Action received for Canadian Patent Application No. 2,787,351, mailed on May 28, 2014, 4 pages.
Office Action received for Canadian Patent Application No. 2,791,791, mailed on Aug. 13, 2014, 3 pages.
Office Action received for Canadian Patent Application No. 2,791,791, mailed on Aug. 25, 2015, 4 pages.
Office Action received for Canadian Patent Application No. 2,792,412, mailed on Aug. 21, 2014, 3 pages.
Office Action received for Canadian Patent Application No. 2,792,442, mailed on Aug. 25, 2015, 3 pages.
Office Action received for Canadian Patent Application No. 2,792,570, mailed on Sep. 3, 2014, 3 pages.
Office Action received for Canadian Patent Application No. 2,793,002, mailed on Sep. 3, 2014, 3 pages.
Office Action received for Canadian Patent Application No. 2,793,002, mailed on Sep. 22, 2015, 3 pages.
Office Action received for Canadian Patent Application No. 2,793,118, mailed on Aug. 21, 2015, 4 pages.
Office Action received for Canadian Patent Application No. 2,793,118, mailed on Jul. 11, 2016, 4 pages.
Office Action received for Canadian Patent Application No. 2,793,118, mailed on Mar. 19, 2015, 3 pages.
Office Action received for Canadian Patent Application No. 2,793,248, mailed on Sep. 3, 2014, 3 pages.
Office Action received for Canadian Patent Application No. 2,793,248, mailed on Sep. 10, 2015, 3 pages.
Office Action received for Canadian Patent Application No. 2,793,741, mailed on Aug. 21, 2014, 2 pages.
Office Action received for Canadian Patent Application No. 2,793,743, mailed on May 20, 2014, 4 pages.
Office Action received for Canadian Patent Application No. 2,954,559, mailed on Mar. 27, 2017, 3 pages.
Office Action received for Canadian Patent Application No. 3,000, 109, mailed on Jan. 14, 2019, 3 pages.
Office Action received for Canadian Patent Application No. 3077914, mailed on Jun. 8, 2021, 5 pages.
Office Action received for Chinese Patent Application No. 201180013559.2, mailed on Feb. 28, 2015, 14 pages.
Office Action received for Chinese Patent Application No. 201480030811.4, mailed on Jan. 28, 2019, 11 pages.
Office Action received for Chinese Patent Application No. 201480030811.4, mailed on Mar. 1, 2018, 17 pages.
Office Action received for Chinese Patent Application No. 201480030811.4, mailed on Mar. 3, 2017, 19 pages.
Office Action received for Chinese Patent Application No. 201480030811.4, mailed on Sep. 8, 2017, 17 pages.
Office Action received for Chinese Patent Application No. 201480030811.4, mailed on Sep. 30, 2018, 19 pages.
Office Action received for Chinese Patent Application No. 201610126045.2, mailed on May 8, 2018, 10 pages.
Office Action received for Chinese Patent Application No. 201610126045.2, mailed on Nov. 12, 2018, 5 pages.
Office Action received for European Patent Application No. 11707939.2 , mailed on Jan. 18, 2019, 8 pages.
Office Action received for European Patent Application No. 14737370.8, mailed on Dec. 21, 2017, 5 pages.
Office Action received for European Patent Application No. 16188272.5, mailed on May 10, 2019, 8 pages.
Office Action received for European Patent Application No. 18202474.5, mailed on Apr. 15, 2021, 15 pages.
Office Action received for European Patent Application No. 19195766.1, mailed on Jan. 3, 2022, 11 pages.
Office Action received for Indian Patent Application No. 201948016386, mailed on Oct. 29, 2021, 6 pages.
Office Action received for Indian Patent Application No. 6734/CHENP/2012, mailed on Mar. 17, 2021, 3 pages.
Office Action received for Indian Patent Application No. 6734/CHENP/2012, mailed on Oct. 30, 2018, 8 pages.
Office Action received for Indian Patent Application No. 8902/CHENP/2012, mailed on Oct. 30, 2018, 6 pages.
Office Action received for Indian Patent Application No. 8903/CHENP/2012, mailed on Aug. 9, 2018, 6 pages.
Office Action received for Indian Patent Application No. 8904/CHENP/2012, mailed on Oct. 23, 2018, 6 pages.
Office Action received for Indian Patent Application No. 8905/CHENP/2012, mailed on Oct. 8, 2018, 7 pages.
Office Action received for Indian Patent Application No. 8906/CHENP/2012, mailed on Oct. 24, 2018, 6 pages.
Office Action received for Indian Patent Application No. 8907/CHENP/2012, mailed on Oct. 24, 2018, 6 pages.
Office Action received for Indian Patent Application No. 8908/CHENP/2012, mailed on Oct. 24, 2018, 6 pages.
Office Action received for Indian Patent Application No. 8909/CHENP/2012, mailed on Oct. 25, 2018, 6 pages.
Office Action received for Indian Patent Application No. 8910/CHENP/2012, mailed on Oct. 25, 2018, 6 pages.
Office Action received for Japanese Patent Application No. 2012-549003, mailed on Dec. 20, 2013, 3 pages.
Office Action received for Japanese Patent Application No. 2012-549003, mailed on Feb. 22, 2016, 15 pages.
Office Action received for Japanese Patent Application No. 2012-549003, mailed on Mar. 2, 2015, 10 pages.
Office Action received for Japanese Patent Application No. 2012-549003, mailed on Oct. 21, 2016, 51 pages.
Office Action received for Japanese Patent Application No. 2014-127579, mailed on Apr. 4, 2016, 6 pages.
Office Action received for Japanese Patent Application No. 2014-127579, mailed on Sep. 14, 2015, 5 pages.
Office Action received for Japanese Patent Application No. 2014-127580, mailed on Jan. 20, 2017, 10 pages.
Office Action received for Japanese Patent Application No. 2014-127580, mailed on Jun. 21, 2016, 12 pages.
Office Action received for Japanese Patent Application No. 2014-127580, mailed on Sep. 28, 2015, 7 pages.
Office Action received for Japanese Patent Application No. 2014-127581, mailed on Aug. 31, 2015, 9 pages.
Office Action received for Japanese Patent Application No. 2014-127581, mailed on Jun. 24, 2016, 4 pages.
Office Action received for Japanese Patent Application No. 2014-127581, mailed on Nov. 24, 2016, 4 pages.
Office Action received for Japanese Patent Application No. 2014-127581, mailed on Oct. 2, 2017, 44 pages.
Office Action received for Japanese Patent Application No. 2014-127582, mailed on Aug. 31, 2015, 11 pages.
Office Action received for Japanese Patent Application No. 2014-127583, mailed on Sep. 7, 2015, 3 pages.
Office Action received for Japanese Patent Application No. 2014-127584, mailed on Sep. 4, 2015, 3 pages.
Office Action received for Japanese Patent Application No. 2014-127585, mailed on Feb. 17, 2017, 9 pages.
Office Action received for Japanese Patent Application No. 2014-127585, mailed on Jul. 15, 2016, 8 pages.
Office Action received for Japanese Patent Application No. 2014-127585, mailed on Sep. 10, 2015, 4 pages.
Office Action received for Japanese Patent Application No. 2014-127586, mailed on Sep. 14, 2015, 8 pages.
Office Action received for Japanese Patent Application No. 2014-127587, mailed on Aug. 23, 2017, 6 pages.
Office Action received for Japanese Patent Application No. 2014-127587, mailed on Jan. 27, 2017, 6 pages.
Office Action received for Japanese Patent Application No. 2014-127587, mailed on Jul. 4, 2016, 7 pages.
Office Action received for Japanese Patent Application No. 2014-127587, mailed on Mar. 19, 2018, 3 pages.
Office Action received for Japanese Patent Application No. 2014-127587, mailed on Sep. 14, 2015, 9 pages.
Office Action received for Japanese Patent Application No. 2017-117880, mailed on May 11, 2018, 9 pages.
Office Action received for Japanese Patent Application No. 2017-117880, mailed on Sep. 29, 2017, 6 pages.
Office Action received for Japanese Patent Application No. 2018-050944, mailed on Feb. 28, 2020, 6 pages.
Office Action received for Japanese Patent Application No. 2018-050944, mailed on Mar. 29, 2019, 8 pages.
Office Action received for Japanese Patent Application No. 2018-050944, mailed on Sep. 11, 2020, 4 pages.
Office Action received for Japanese Patent Application No. 2020-109934, mailed on Mar. 18, 2022, 6 pages.
Office Action received for Japanese Patent Application No. 2020-109934, mailed on May 31, 2021, 5 pages.
Office Action received for Korean Patent Application No. 10-2012-7021659, mailed on Apr. 30, 2014, 8 pages.
Office Action received for Korean Patent Application No. 10-2012-7021659, mailed on Feb. 27, 2015, 15 pages.
Office Action received for Korean Patent Application No. 10-2012-7028786, mailed on Apr. 30, 2014, 15 pages.
Office Action received for Korean Patent Application No. 10-2012-7028802, mailed on Apr. 30, 2014, 10 pages.
Office Action received for Korean Patent Application No. 10-2012-7028805, mailed on Feb. 27, 2015, 14 pages.
Office Action received for Korean Patent Application No. 10-2012-7029183, mailed on Apr. 30, 2014, 11 pages.
Office Action received for Korean Patent Application No. 10-2012-7029183, mailed on Jan. 28, 2015, 10 pages.
Office Action received for Korean Patent Application No. 10-2012-7029183, mailed on Sep. 7, 2015, 7 pages.
Office Action received for Korean Patent Application No. 10-2012-7029195, mailed on Apr. 30, 2014, 11 pages.
Office Action received for Korean Patent Application No. 10-2012-7029195, mailed on Feb. 27, 2015, 16 pages.
Office Action received for Korean Patent Application No. 10-2012-7029195, mailed on Jan. 28, 2016, 6 pages.
Office Action received for Korean Patent Application No. 10-2012-7029197, mailed on Apr. 30, 2014, 10 pages.
Office Action received for Korean Patent Application No. 10-2012-7029381, mailed on Apr. 30, 2014, 12 pages.
Office Action received for Korean Patent Application No. 10-2012-7029381, mailed on Mar. 28, 2015, 5 pages.
Office Action received for Korean Patent Application No. 10-2012-7029382, mailed on Apr. 30, 2014, 9 pages.
Office Action received for Korean Patent Application No. 10-2012-7029382, mailed on Jan. 28, 2015, 7 pages.
Office Action received for Korean Patent Application No. 10-2012-7029382, mailed on Jul. 31, 2015, 12 pages.
Office Action received for Korean Patent Application No. 10-2012-7029385, mailed on Apr. 30, 2015, 13 pages.
Office Action received for Korean Patent Application No. 10-2012-7029385, mailed on Jun. 27, 2014, 13 pages.
Office Action received for Korean Patent Application No. 10-2015-7035370, mailed on Jul. 11, 2016, 12 pages.
Office Action received for Korean Patent Application No. 10-2015-7035370, mailed on May 31, 2017, 6 pages.
Office Action received for Korean Patent Application No. 10-2015-7035370, mailed on Oct. 11, 2017, 7 pages.
Office Action received for Korean Patent Application No. 10-2016-7023962, mailed on Oct. 20, 2016, 5 pages.
Office Action received for Korean Patent Application No. 10-2017-7024596, mailed on Feb. 22, 2018, 10 pages.
Office Action received for Korean Patent Application No. 10-2017-7035711, mailed on May 18, 2018, 14 pages.
Office Action received for Korean Patent Application No. 10-2019-7007971, mailed on May 17, 2019, 12 pages.
Office Action received for Korean Patent Application No. 10-2019-7018332, mailed on Mar. 12, 2020, 9 pages.
Office Action received for Korean Patent Application No. 10-2019-7018332, mailed on Sep. 10, 2019, 5 pages.
Office Action received for Korean Patent Application No. 10-2020-7023927, mailed on Nov. 18, 2020, 10 pages.
Office Action received for Korean Patent Application No. 10-2020-7037138, mailed on Jan. 21, 2021, 13 pages.
Office Action received for Korean Patent Application No. 10-2021-7027594, mailed on Nov. 30, 2021, 9 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/008369, mailed on Oct. 21, 2013, 6 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011794, mailed on Jun. 13, 2014, 2 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011795, mailed on Feb. 19, 2014, 1 page.
Office Action received for Mexican Patent Application No. MX/a/2012/011795, mailed on Jun. 13, 2014, 2 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011797, mailed on Feb. 19, 2014, 1 page.
Office Action received for Mexican Patent Application No. MX/a/2012/011797, mailed on Jun. 13, 2014, 2 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011798, mailed on Feb. 19, 2014, 1 page.
Office Action received for Mexican Patent Application No. MX/a/2012/011798, mailed on Jun. 24, 2014, 3 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011799, mailed on Jun. 25, 2014, 2 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011800, mailed on Aug. 20, 2015, 9 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011800, mailed on Dec. 5, 2014, 5 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011803, mailed on Feb. 19, 2014, 1 page.
Office Action received for Mexican Patent Application No. MX/a/2012/011803, mailed on Jun. 25, 2014, 2 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011807, mailed on Feb. 19, 2014, 1 page.
Office Action received for Mexican Patent Application No. MX/a/2012/011807, mailed on Jun. 26, 2014, 2 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011808, mailed on Feb. 19, 2014, 1 page.
Office Action received for Mexican Patent Application No. MX/a/2017/006911, mailed on Feb. 22, 2022, 12 pages.
Office Action received for Mexican Patent Application No. MX/a/2017/006911, mailed on Jun. 17, 2021, 5 pages.
Office Action received for Mexican Patent Application No. MX/a/2012/011799, mailed on Feb. 19, 2014, 1 page.
Office Action received for Russian Patent Application No. 2012135502, mailed on Feb. 13, 2014, 8 pages.
Office Action received for Russian Patent Application No. 2012144605, mailed on Mar. 21, 2014, 7 pages.
Office Action received for Russian Patent Application No. 2012144606, mailed on Mar. 20, 2014, 7 pages.
Office Action received for Russian Patent Application No. 2012144637, mailed on Mar. 20, 2014, 8 pages.
Office Action received for Russian Patent Application No. 2012144640, mailed on Mar. 19, 2014, 9 pages.
Office Action received for Russian Patent Application No. 2012144644, mailed on Mar. 19, 2014, 8 pages.
Office Action received for Russian Patent Application No. 2012144647, mailed on Jun. 18, 2014, 8 pages.
Office Action received for Russian Patent Application No. 2018112505, mailed on Sep. 2, 2021, 12 pages.
Office Action received for United Kingdom Patent Application No. 1213633.9, mailed on Feb. 16, 2017, 5 pages.
Office Action received for United Kingdom Patent Application No. 1213633.9, mailed on Sep. 28, 2017, 5 pages.
Osxdaily, “Get a List of Siri Commands Directly from Siri”, Online available at:—<http://osxdaily.com/2013/02/05/list-siri-commands/>, Feb. 5, 2013, 15 pages.
Pak, Gamerz, “Braina: Artificially Intelligent Assistant Software for Windows PC in(urdu / hindhi)”, Online available at: <https://www.youtube.com/watch?v=JH_rMjw8lqc>, Jul. 24, 2018, 3 pages.
Pathak et al., “Privacy-preserving Speech Processing: Cryptographic and String-matching Frameworks Show Promise”, In: IEEE signal processing magazine, Online available at:—<http://www.merl.com/publications/docs/TR2013-063.pdf>, Feb. 13, 2013, 16 pages.
Patra et al., “A Kernel-Based Approach for Biomedical Named Entity Recognition”, Scientific World Journal, vol. 2013, 2013, pp. 1-7.
Pc Mag, “How to Voice Train Your Google Home Smart Speaker”, Online available at: <https://in.pcmag.com/google-home/126520/how-to-voice-train-your-google-home-smart-speaker>, Oct. 25, 2018, 12 pages.
Pennington et al., “GloVe: Global Vectors for Word Representation”, Proceedings of the Conference on Empirical Methods Natural Language Processing (EMNLP), Doha, Qatar, Oct. 25-29, 2014, pp. 1532-1543.
Perlow, Jason, “Alexa Loop Mode with Playlist for Sleep Noise”, Online Available at: <https://www.youtube.com/watch?v=nSkSuXziJSg>, Apr. 11, 2016, 3 pages.
pocketables.com, “AutoRemote example profile”, Online available at: https://www.youtube.com/watch?v=kC_zhUnNZj8, Jun. 25, 2013, 1 page.
Qian et al., “Single-channel Multi-talker Speech Recognition With Permutation Invariant Training”, Speech Communication, Issue 104, 2018, pp. 1-11.
“Quick Type Keyboard on iOS 8 Makes Typing Easier”, Online available at:—<https://www.youtube.com/watch?v=0CldLR4fhVU>, Jun. 3, 2014, 3 pages.
Rasch, Katharina, “Smart Assistants for Smart Homes”, Doctoral Thesis in Electronic and Computer Systems, 2013, 150 pages.
Result of Consultation received for European Patent Application No. 11707939.2, mailed on Aug. 19, 2020, 4 pages.
Result of Consultation received for European Patent Application No. 16188272.5, mailed on Oct. 13, 2021, 3 pages.
Rios Mafe, “New Bar Search for Facebook”, YouTube, available at:—<https://www.youtube.com/watch?v=vwgN1WbvCas>, Jul. 19, 2013, 2 pages.
Ritchie, Rene, “QuickType keyboard in iOS 8: Explained”, Online Available at:—<https://www.imore.com/quicktype-keyboards-ios-8-explained>, Jun. 21, 2014, pp. 1-19.
Routines, “SmartThings Support”, Online available at:—<https://web.archive.org/web/20151207165701/https://support.smartthings.com/hc/en-us/articles/205380034-Routines>, 2015, 3 pages.
Rowland et al., “Designing Connected Products: UX for the Consumer Internet of Things”, O'Reilly, May 2015, 452 pages.
Samsung Support, “Create a Quick Command in Bixby to Launch Custom Settings by at Your Command”, Online Available at:—<https://www.facebook.com/samsungsupport/videos/10154746303151213>, Nov. 13, 2017, 1 page.
Santos et al., “Fighting Offensive Language on Social Media with Unsupervised TextStyle Transfer”, Proceedings of the 56th Annual Meeting of the Association for Computational Linguistics (vol. 2: Short Papers), May 20, 2018, 6 pages.
Seehafer Brent, “Activate Google Assistant on Galaxy S7 with Screen off”, Online available at:—<https://productforums.google.com/forum/#!topic/websearch/lp3qIGBHLVI>, Mar. 8, 2017, 4 pages.
Selfridge et al., “Interact: Tightly-coupling Multimodal Dialog with an Interactive Virtual Assistant”, International Conference on Multimodal Interaction, ACM, Nov. 9, 2015, pp. 381-382.
Senior et al., “Improving DNN Speaker Independence With I-Vector Inputs”, ICASSP, 2014, pp. 225-229.
Seroter et al., “SOA Patterns with BizTalk Server 2013 and Microsoft Azure”, Packt Publishing, Jun. 2015, 454 pages.
Seto, Haruka, “Application Integration Programming with VBA Next Generation Office Development Techniques”, Visual Basic magazine , Shoeisha Co., Ltd., vol. 6, No. 12, Oct. 1, 2000, 15 pages.
Settle et al., “End-to-End Multi-Speaker Speech Recognition”, Proc. ICASSP, Apr. 2018, 6 pages.
Shen et al., “Style Transfer from Non-Parallel Text by Cross-Alignment”, 31st Conference on Neural Information Processing Systems (NIPS 2017), 2017, 12 pages.
Siou, Serge, “How to Control Apple TV 3rd Generation Using Remote app”, Online available at: <https://www.youtube.com/watch?v=PhyKftZ0S9M>, May 12, 2014, 3 pages.
“Skilled at Playing my iPhone 5”, Beijing Hope Electronic Press, Jan. 2013, 6 pages.
“SmartThings +Amazon Echo”, Smartthings Samsung [online], Online available at:—<https://web.archive.org/web/20160509231428/https://blog.smartthings.com/featured/alexa-turn-on-my-smartthings/>, Aug. 21, 2015, 3 pages.
Smith, Jake, “Amazon Alexa Calling: How to Set it up and Use it on Your Echo”, iGeneration, May 30, 2017, 5 pages.
Spivack, Nova, “Sneak Preview of Siri—Part Two—Technical Foundations—Interview with Tom Gruber”, CTO of Siri I Twine, Available at URL:https://web.archive.org/web/20100114234454/http://www.twine.com/item/12vhy39k4-22m/interview-with-tom-gruber-of-siri, Jan. 14, 2010, 5 pages.
SRI, “SRI Speech: Products: Software Development Kits: EduSpeak”, Online available at:—<http://web.archive.org/web/20090828084033/http://www.speechatsri.com/products/eduspeak>shtml, retrieved on Jun. 20, 2013, pp. 1-2.
Summons to Attend Oral Proceedings received for European Patent Application No. 11707939.2, mailed on Mar. 20, 2020, 12 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 14737370.8, mailed on Jan. 21, 2019, 12 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 16188272.5, mailed on Apr. 26, 2021, 11 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 16188272.5, mailed on Oct. 26, 2021, 11 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 18202474.5, mailed on Mar. 14, 2022, 15 pages.
Sundaram et al., “Latent Perceptual Mapping with Data-Driven Variable-Length Acoustic Units for Template-Based Speech Recognition”, ICASSP 2012, Mar. 2012, pp. 4125-4128.
Sundermeyer et al., “From Feedforward to Recurrent LSTM Neural Networks for Language Modeling.”, IEEE Transactions to Audio, Speech, and Language Processing, vol. 23, No. 3, Mar. 2015, pp. 517-529.
Sundermeyer et al., “LSTM Neural Networks for Language Modeling”, INTERSPEECH 2012, Sep. 9-13, 2012, pp. 194-197.
Supplemental Notice of Allowance received for U.S. Appl. No. 15/394,162, mailed on Apr. 9, 2020, 2 pages.
Susaki et al., “A New Decision Factor for IR System Extracted from Structure of Hypertexts”, Report of Information Processing Society of Japan, JPN, vol. 99, No. 57, Jul. 16, 1999, pp. 73-80.
Tan et al., “Knowledge Transfer In Permutation Invariant Training For Single-channel Multi-talker Speech Recognition”, ICASSP 2018, 2018, pp. 5714-5718.
Tatsuya et al., “Open-Source Speech Recognition Software Julius”, Journal of Japanese Society for Artificial Intelligence, vol. 20, No. 1, Jan. 2005, pp. 41-49.
“The world of Virtual Assistants—more SemTech .,”, End of Business as Usual—Glenn's External blog, Available at URL:https://web.archive.org/web/20091101840940/http://glennas.wordpress.com/2009/10/17/the-world-of-virtual-assistants-more-semtech/, Oct. 17, 2009, 5 pages.
Tofel et al., “SpeakToit: A Personal Assistant for Older iPhones, iPads”, Apple News, Tips and Reviews, Feb. 9, 2012, 7 pages.
Tomita et al., “Multi-database Searching System Based on WWW: WebSENA”, NTT Technology Journal, JPN, vol. 10, No. 5 (serial No. 100), May 1, 1998, pp. 55-58.
Ushida et al., “Spoken Dialogue Engine based on Autonomous Behavior Decision Model”, Omron Technics, vol. 40, No. 1, 2000, pp. 16-21.
Vaswani et al., “Attention Is All You Need”, 31st Conference on Neural Information Processing Systems (NIPS 2017), 2017, pp. 1-11.
Villemure et al., “The Dragon Drive Innovation Showcase: Advancing the State-of-the-art in Automotive Assistants”, 2018, 7 pages.
Vodafone Deutschland, “Samsung Galaxy S3 Tastatur Spracheingabe”, Online available at—<https://www.youtube.com/watch?v=6kOd6Gr8uFE>, Aug. 22, 2012, 1 page.
Wang et al., “End-to-end Anchored Speech Recognition”, Proc. ICASSP2019, May 12-17, 2019, 5 pages.
Weng et al., “Deep Neural Networks for Single-Channel Multi-Talker Speech Recognition”, IEEE/ACM Transactions on Audio, Speech, and Language Processing, vol. 23, No. 10, Oct. 2015, pp. 1670-1679.
Wikipedia, “Home Automation”, Online Available at:—<https://en.wikipedia.org/w/index.php?title=Home_automation&oldid=686569068>, Oct. 19, 2015, 9 pages.
Wikipedia, “Siri”, Online Available at:—<https://en.wikipedia.org/w/index.php?title=Siri&oldid=689697795>, Nov. 8, 2015, 13 Pages.
Wikipedia, “Virtual Assistant”, Wikipedia, Online Available at:—<https://en.wikipedia.org/w/index.php?title=Virtual_assistant&oldid=679330666>, Sep. 3, 2015, 4 pages.
“Windows Practical & Secret Techniques Compendium”, C & R Institute Inc, first Edition, Natsumesha Co, Ltd, Apr. 10, 2007, 5 pages.
X.Al, “How it Works”, Online available at:—<https://web.archive.org/web/20160531201426/https://x.ai/how-it-works/>, May 31, 2016, 6 pages.
Xiang et al., “Correcting Phoneme Recognition Errors in Learning Word Pronunciation through Speech Interaction”, Speech Communication, vol. 55, No. 1, Jan. 1, 2013, pp. 190-203.
Xu et al., “Policy Optimization of Dialogue Management in Spoken Dialogue System for Out-of-Domain Utterances”, 2016 International Conference on Asian Language Processing (IALP), IEEE, Nov. 21, 2016, pp. 10-13.
Xu et al., “Speech-Based Interactive Games for Language Learning: Reading,Translation, and Question-Answering”, Computational Linguistics and Chinese Language Processing, vol. 14, No. 2, Jun. 2009, pp. 133-160.
Yan et al., “A Scalable Approach to Using DNN-derived Features in GMM-HMM Based Acoustic Modeling for LVCSR”, 14th Annual Conference of the International Speech Communication Association, InterSpeech 2013, Aug. 2013, pp. 104-108.
Yang Astor, “Control Android TV via Mobile Phone APP RKRemoteControl”, Online Available at : <https://www.youtube.com/watch?v=zpmUeOX_xro>, Mar. 31, 2015, 4 pages.
Yates Michaelc., “How Can I Exit Google Assistant After I'm Finished with it”, Online available at:—<https://productforums.google.com/forum/#!msg/phone-by-google/faECnR2RJwA/gKNtOkQgAQAJ>, Jan. 11, 2016, 2 pages.
Ye et al., “iPhone 4S Native Secret”, Jun. 30, 2012, 1 page.
Yeh Jui-Feng, “Speech Act Identification Using Semantic Dependency Graphs With Probabilistic Context-free Grammars”, ACM Transactions on Asian and Low-Resource Language Information Processing, vol. 15, No. 1, Dec. 2015, pp. 5.1-5.28.
Yousef, Zulfikara., “Braina (A.I) Artificial Intelligence Virtual Personal Assistant”, Online available at:—<https://www.youtube.com/watch?v=2h6xpB8bPSA>, Feb. 7, 2017, 3 pages.
Yu et al., “Permutation Invariant Training of Deep Models For Speaker-Independent Multi-talker Speech Separation”, Proc. ICASSP, 2017, 5 pages.
Yu et al., “Recognizing Multi-talker Speech with Permutation Invariant Training”, Interspeech 2017, Aug. 20-24, 2017, pp. 2456-2460.
Zainab, “Google Input Tools Shows Onscreen Keyboard in Multiple Languages [Chrome]”, Online available at:—<http://www.addictivetips.com/internet-tips/google-input-tools-shows-multiple-language-onscreen-keyboards-chrome/>, Jan. 3, 2012, 3 pages.
Zhan et al., “Play with Android Phones”, Feb. 29, 2012, 1 page.
Zhong et al., “JustSpeak: Enabling Universal Voice Control on Android”, W4A'14, Proceedings of the 11th Web for All Conference, No. 36, Apr. 7-9, 2014, 8 pages.
Zmolikova et al., “Speaker-Aware Neural Network Based Beamformer for Speaker Extraction In Speech Mixtures”, Interspeech 2017, Aug. 20-24, 2017, pp. 2655-2659.
Non-Final Office Action received for U.S. Appl. No. 16/912,278, mailed on Mar. 3, 2023, 10 pages.
Notice of Allowance received for Korean Patent Application No. 10-2022-7020185, mailed on Feb. 23, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Notice of Hearing received for Indian Patent Application No. 8904/CHENP/2012, mailed on Feb. 21, 2023, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8908/CHENP/2012, mailed on Feb. 21, 2023, 2 pages.
Notice of Hearing received for Indian Patent Application No. 8909/CHENP/2012, mailed on Feb. 21, 2023, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/879,643, mailed on Jun. 23, 2022, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/912,278, mailed on Jul. 27, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/879,643, mailed on Jul. 20, 2022, 2 pages.
Office Action received for Indian Patent Application No. 202248011347, mailed on Dec. 2, 2022, 5 pages.
Office Action received for Indian Patent Application No. 202248011348, mailed on Dec. 2, 2022, 5 pages.
Office Action received for Indian Patent Application No. 202248011349, mailed on Dec. 2, 2022, 5 pages.
Office Action received for Indian Patent Application No. 202248011350, mailed on Dec. 12, 2022, 5 pages.
Office Action received for Korean Patent Application No. 10-2022-7026740, mailed on. Sep. 14, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
709795, CH, A1, Cited by the client on Mar. 3, 2021.
102324233, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201580046330.7 on Aug. 23, 2021.
102346719, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201810019395.8 on Oct. 29, 2021.
102495406, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110571137.2 on Sep. 30, 2021.
102520789, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010735884.0 on Mar. 10, 2021.
102663016, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201910330895.8 on Dec. 15, 2020.
102681761, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201710551469.8 on Nov. 10, 2021.
102890936, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201710386932.8 on Apr. 6, 2021.
102915731, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201580080518.3 on Dec. 18, 2020.
103093755, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010736257.9 on Aug. 30, 2021.
103187053, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201580080518.3 on Oct. 18, 2021.
103197963, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201910115436.8 on Mar. 14, 2022.
103217892, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110557428.6 on Dec. 2, 2021.
103324100, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201680065149.5 on Dec. 15, 2021.
203249629, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201680049880.9 on Apr. 6, 2021.
103414949, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201680003291.7 on Mar. 24, 2021.
103456303, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010736257.9 on Aug. 30, 2021.
103457837, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010997038.6 Sep. 9, 2021.
103475551, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010735884.0 on Mar. 10, 2021.
103593054, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201710551469.8 on Jul. 15, 2021.
103686723, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201680065149.5 on Dec. 15, 2021.
103761104, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110943177.5 on Mar. 8, 2022.
103778527, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110571137.2 on Sep. 30, 2021.
103780758, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110557428.6 on Dec. 2,. 2021.
103809548, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 2020107358840 on Mar. 10, 2021.
103885663, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010356666.6 on Dec. 31, 2020.
103942932, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110571137.2 on Sep. 30, 2021.
102693729. CN, B, Cited by the client on Mar. 29, 2022.
104036774, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201580080518.3 on Dec. 18, 2020.
104092829, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201680065149.5 on Dec. 15, 2021.
104185868, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201580080518.3 on Oct. 18, 2021.
104240701, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201710551469.8 on Nov. 10, 2021.
104360990, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201810998619.4 on Dec. 28, 2020.
104423780, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201810998574.0 on Dec. 25, 2020.
104464733, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201680049415.5 on Dec. 28, 2020.
104731441, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201810019395.8 on Oct. 29, 2021.
104798012, CN, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-205151 on Nov. 26, 2021.
104836909, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202011041038.5 on Feb. 26, 2021.
104867492, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201710386355.2 on Dec. 11, 2020.
105247551, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201710386355.2 on Dec. 11, 2020.
105516441, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201810019395.8 on Oct. 29, 2021.
105554217, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202011041038.5 on Jan. 26, 2022.
105872222, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 201980033273.7 on Jul. 5, 2021.
106773742, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202011041038.5 on Feb. 26, 2021.
107623616, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010356666.6 on Dec. 31, 2020.
107786730, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010356666.6 on Dec. 31, 2020.
108268187, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110513252.4 on Mar. 14, 2022.
110263144, CN, A, Cited by the WiPO in an Office Action for reiated Patent Application No. PCT/US2021/036910 on Sep. 29, 2021.
111124224, CN, A, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202110513252.4 on Mar. 14, 2022.
107123417, CN, A, Cited by the client on Mar. 29, 2022.
111316203, CN, A, Cited by the applicant on Jun. 18, 2021.
2012-40655, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2018-087328 on Nov. 17, 2020.
2012-511774, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-172654 on Oct. 1, 2021.
2012-165084, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-205151 on Nov. 26, 2021.
2012-220959, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2018-087328 on Nov. 17, 2020.
2013-131087, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-1726554 on Oct. 1, 2021.
2013-174987, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-172654 on Oct. 1, 2021.
2013-200265, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-217267 on Nov. 15, 2021.
2013-238935, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-172654 on Oct. 1, 2021.
20113-248292, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-217267 on Nov. 15, 2021.
2013-257694, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2018-192102 on Mar. 11, 2021.
2015-1931, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-217267 on Nov. 15, 2021.
2016-35614, JP, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-123111 on Jun. 25, 2021.
2017-11608, JP, A, Cited by the Korean Patent Office in an Office Action for related Patent Application No. 10-2022-7002780 on Feb. 22, 2022.
2017-1213187, JP, A, Cited by the applicant on Jun. 18, 2021.
2017-211608, JP, A, Cited by the Korean Patent Office in an Office Action for related Patent Application No. 10-2020-7037527 on Oct. 25, 2021.
2018-101242, JP, A, Cited by the Danish Patent Office in an Office Action for related Patent Application No. PA202070658 on Jan. 22, 2021.
10-2014-0007282, KR, A, Cited by the Korean Patent Office in an Office Action for related Patent Application No. 10-2020-7037527 on Oct. 25, 2021.
10-2014-0071208, KR, A, Cited by the Japanese Patent Office in an Office Action for related Patent Application No. 2020-205151 on Nov. 26, 2021.
10-2015-0062811, KR, A, Cited by the appiicant on Jun. 18, 2021.
10-2020-0105519, KR, A, Cited by the applicant on Jun. 18, 2021.
Chenghao, Yuan, “MacroDroid”, Online available at: https://www.ifanr.com/weizhizao/612531, Jan. 25, 2016, 7 pages, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202010167391.1 on Apr. 20, 2021.
“How to adjust the order of control center buttons on iPhone iOS12 version after buying a mobile phone”, Available online at: https://jingyan.baidu.com/article/5bbb5albbe5a9713eba1791b.html?, Jun. 14, 2019, 4 pages, Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 2021105132524 on Mar. 14, 2022.
Simonite, Tom, “Confronting Siri: Microsoft Launches Digital Assistant Cortana”, 2014, 2 pages, Cited by the Chinese Patent Office in an Office Action for related Patent Appiication No. 201680049844.2 on Dec. 18, 2020.
Song, Yang, “Research of Chinese Continuous Digital Speech Input System Based on HTK”, Computer and Digital Engineering, vol. 40, No. 4, Dec. 31, 2012, 5 pages, Cited by the Chinese Patent Office in an Office Action for reiated Patent Appiication No. 201710109781.1 on Feb. 22, 2021.
“Use Macrodroid skillfully to automatically clock in with Ding Talk”, Online available at: https://blog.csdn.net/qq_26614295/article/details/84304541, Nov. 20, 2018, 11 pages, Cited by the Chinese Patent Office in an Office Action for reiated Patent Appiication No. 202010167391.1 on Apr. 20, 2021.
Zhao et al., “Big Data Analysis and Application”, Aviation Industry Press, Dec. 2015, pp. 236-241, Cited by the Chinese Patent Office in an Office Action for reiated Patent Application No. 202010356666.6 on Jun. 23, 2021.
Notice of Allowance received for Japanese Patent Application No. 2020-109934, mailed on Dec. 19, 2022, 19 pages (1 page of English Translation and 18 pages of Official Copy).
Summons to Oral Proceedings received for European Patent Application No. 16188272.5, mailed on Sep. 6, 2023, 13 pages.
Examiner-Initiated Interview Summary received for U.S. Appl. No. 16/912,278, mailed on Jan. 30, 2024, 2 pages.
Office Action received for Chinese Patent Application No. 202110472089.1, mailed on Jan. 15, 2024, 29 pages (9 pages of English Translation and 20 pages of Official Copy).
Brownlee John, “Siri app turns your GPS-enabled iPhone into a virtual concierge”, Online Available at: https://web.archive.org/web/20111006222659/http://www.cultofmac.com:80/29188/siri-app-turns-your-gps-enabled-iPhone-into-a-virtual-concierge/, Oct. 6, 2011. 7 pages.
Esposito Dom, “How to Make Restaurant Reservations with Siri”, Online available at: https://www.youtube.com/watch?v=Op828q-vqCQ, Dec. 23, 2012, 2 pages.
Horowitz Paul, “Buy Movie Tickets with Siri”, Online Available at: https://web.archive.org/web/20130203112931/https://osxdaily.com/2013/01/28/buy-movie-tickets-with-siri/, Feb. 3, 2013, 4 pages.
Kazmucha Allyson, “How to find restaurants, read reviews, and make reservations using Siri”, Online Available at: https://web.archive.org/web/20121023225357/https://www.imore.com/how-find-restaurants-make-reservations-read-ratings-and-more-Siri, Oct. 23, 2012, 17 pages.
Notice of Allowance received for Japanese Patent Application No. 2024-011222, mailed on Mar. 22, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 16/912,278, mailed on Mar. 27, 2024, 2 pages.
Office Action received for Australian Patent Application No. 2023200803, mailed on Mar. 22, 2024, 3 pages.
Office Action received for Australian Patent Application No. 2023202682, mailed on Mar. 27, 2024, 8 pages.
Decision to Refuse received for Japanese Patent Application No. 2022-114276, mailed on Nov. 24, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 16/912,278, mailed on Feb. 12, 2024, 12 pages.
Office Action received for Australian Patent Application No. 2023200803, mailed on Feb. 5, 2024, 3 pages.
Office Action received for Korean Patent Application No. 10-2023-7017413, mailed on Jan. 18, 2024, 9 pages (3 pages of English Translation and 6 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2023-7019935, mailed on Jan. 30, 2024, 8 pages (3 pages of English Translation and 5 pages of Official Copy).
Communication for Board of Appeal received for European Patent Application No. 16188272.5, mailed on Mar. 13, 2024, 2 pages.
Notice of Allowance received for Japanese Patent Application No. 2022-114276, mailed on Mar. 15, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 16/912,278, mailed on Mar. 13, 2024, 2 pages.
Notice of Allowance received for U.S. Appl. No. 16/912,278, mailed on Mar. 21, 2024, 2 pages.
Notice of Acceptance received for Australian Patent Application No. 2023200803, mailed on Jul. 31, 2024, 3 pages.
Notice of Hearing received for Indian Patent Application No. 201948016386, mailed on Jul. 30, 2024, 2 pages.
Office Action received for Chinese Patent Application No. 202110472089.1, mailed on Jul. 30, 2024, 28 pages (7 pages of English Translation and 21 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2023-7019935, mailed on Sep. 6, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2023-7017413, mailed on Sep. 19, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Office Action received for Australian Patent Application No. 2023202682, mailed on Sep. 16, 2024, 4 pages.
Related Publications (1)
Number Date Country
20220254338 A1 Aug 2022 US
Provisional Applications (1)
Number Date Country
61295774 Jan 2010 US
Continuations (4)
Number Date Country
Parent 16879643 May 2020 US
Child 17732011 US
Parent 15394162 Dec 2016 US
Child 16879643 US
Parent 13492809 Jun 2012 US
Child 15394162 US
Parent 12987982 Jan 2011 US
Child 13492809 US