The present invention relates to intelligent systems, and more specifically for classes of applications for intelligent automated assistants.
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.
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 ser-vices 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:
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.
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.
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:
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
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
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
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
In the arrangement shown in
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 1360 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 1360 are called and the intended action taken. In one embodiment, assistant 1002 may prompt the user for confirmation before calling a service 1360 to perform a function. In one embodiment, a user can selectively disable assistant's 1002 ability to call particular services 1360 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
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
In the example of
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:
Additional components may be implemented as part of server 1340, including for example:
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
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):
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
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):
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):
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):
It may be appreciated that the intelligent automated assistant 1002 of
User Interaction
Referring now to
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:
In one embodiment, information screen 101E also includes some examples of services that assistant 1002 might offer on behalf of the user, including:
As shown in the example of
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
As described in connection with
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
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):
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):
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
Active ontology 1050 in
As described above, active ontology 1050 allows the author, designer, or system builder to integrate components; thus, in the example of
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:
For example, referring now to
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):
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
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):
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):
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):
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):
Referring now to
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
In
In
In
In
In
In
In
In
In
In
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
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, Mass.
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
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
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
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 corrections, 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
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
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
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
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.
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
Case: First Word Input
Find restaurants,
Case: Key Word Input
Remember to a thing,
Case: Prompting for Arguments
Case: Suggesting Criteria
Case: Adding Criteria
Case: Adding Location or Other Constraints
Case: Starting from Constraint, Unknown Task or Domain
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
Case: Name with Context
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: Valueclass Selection
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
Italian restaurants (normal
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
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
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):
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):
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
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):
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):
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):
Referring now also to
Referring now also to
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
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):
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):
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):
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):
In one embodiment, access of data from other parts of embodiments of assistant 1002 may be coordinated by active ontologies 1050.
Referring again to
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):
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):
Referring now to
As shown in screen 3001, user requests a dinner reservation by providing speech or text input 3002 “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
The method begins 300. Representation of user intent 290 is received. As described in connection with
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
As described above,
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 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):
Referring now to
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
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
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):
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):
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:
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):
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):
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):
Referring now to
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. The method begins 400. These domain and task parameters are given as input 390.
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):
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
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 410 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:
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):
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):
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):
Referring now to
In step 710, a speech input utterance is obtained and a speech-to-text component (such as component described in connection with
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
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
Returning to
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
In one embodiment, assistant 1002 is capable of generating output in multiple modes. Referring now to
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
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 mul-tiphase 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):
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
In the example of
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):
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):
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
Screen 4403 of
Screen 4404 of
Automated Call and Response Procedure
Referring now to
In at least one embodiment, the automated call and response procedure of
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):
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
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
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
For example, by one of the methods of active input elicitation in step 100, the user might say to assistant 1002, “where may I 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
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
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, “1 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
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:
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:
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 (“1 know about restaurants, hotels, and movies” as opposed to “1 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
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
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 (e.g., constrained selection task 4602) 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 4604 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 4609 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
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, 1 could not find any restaurants in Anytown, Tx. 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
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
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 a priori 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:
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:
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:
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:
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
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:
For example, the following paraphrase and prompt illustrates several of these goals:
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:
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:
For example, a parse might contain these elements:
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:
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:
recommended romantic Italian restaurants near Menlo Park
with open tables for 2 that serve osso buco and are described as “quiet”
A grammar to construct this is
Table 1 provides some examples of paraphrases that may be provided in response to the first input for a task, according to one embodiment.
businesses, flights, weather, and buying things
Park
healthy food.
spicy food.
burgers.
Fornaioin Palo Alto.
House in Palo Alto.
Refining a Query about Places to Eat
Table 2 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.
Park.
Table 3 provides some examples of results summaries that are provided once results are obtained.
Palo Alto. Do you prefer any particular food
type? Would you like a reservation?
locations.
Menlo Park.
businesses?
Menlo Park.
events, and things to do in San Francisco. What
events, and things to do in San Francisco. What
Park. Any other names for it?
to 8 pm tonight for a party of two in Palo Alto,
CA.
to 8 pm tonightfor a party of two in Palo Alto,
CA.
Palo Alto, CA at 6 pm today for a party of 2.
Alto, CA. You can call them at the phone
romantic italian restaurants near Menlo Park that
romantic italian restaurants near Menlo Park with
open tables for 2 that serve osso buco and are
Menlo Park. Do you prefer any particular food
Table 4 provides some examples of prompts that are provided when users click on active links.
Prompts when Users Click on Active Links
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:
In various embodiments, the context that determines the most relevant suggestions may be derived from, for example:
In various embodiments, suggestions may be generated by any mechanism, such as for example:
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
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:
A suggestion may also involve some combination of the above. For example:
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:
In one embodiment, assistant 1002 determines an output format for the suggestion. Examples of output formats include:
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:
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?”
As described earlier in the specification, when the digital assistant is active, the digital assistant optionally maintains a dialogue interface to facilitate real-time, two-way communications between the digital assistant and the user. The dialogue interface of the digital assistant is capable of receiving inputs from and providing outputs to the user through multiple modalities (e.g., via speech, text, touch, gestures, and other audio, visual, and tactile means). In some embodiments, the dialogue interface is a speech-only (e.g., an eyes-free and hands-free interface) input and output interface, and the user and the digital assistant communicate entirely through speech and sounds. In some embodiments, the dialogue interface provides a conversation screen in addition to a speech-based input and output interface. In some embodiments, the conversation screen presents textual paraphrases of the user's speech input (e.g., a search request) and/or presents information and search results in textual and graphical forms. In some embodiments, the conversation screen allows the user to enter text, select search results, and/or interact with various user interface elements presented on the conversation screen. In some embodiments, the conversation screen is a single frame displayed on the user device containing textual representations of the dialogue between the user and the digital assistant. In some embodiments, the textual representations include a series of text boxes, text bubbles, or other visual renditions of the original text input from the user, text derived from user speech input (e.g., original words or paraphrases), and/or text output provided the digital assistant.
In the process 4800, in response to receiving the search request, the digital assistant presents a plurality of search results to the user through the dialogue interface, each search result corresponding to a respective reservable item identified in accordance with the search request (4820). A reservable item refers to an item that can be reserved and/or purchase according to a reservation or booking process prescribed by the provider of the item. Examples of a reservable item include a table at a restaurant, a ticket or seating at an event, concert, movie, sports game, performance, talk, or the like, an item on sale at an auction, and the like. A search result corresponds to a respective reservable item identified in accordance with the search request, and provides information (e.g., name, location, show time, price, rating, etc.) about the reservable item or a third-party provider of the reservable item. For example, a search result for a restaurant search request provides information (e.g., name, cuisine, and location) on a restaurant that has open tables for reservation. A search result for an entertainment search request provides information (e.g., name, time, location, and price) on an entertainment event (e.g., a movie or a concert) that has tickets for sale. Search criteria for identifying reservable items include a search class or selection class (e.g., restaurants, entertainment events, etc.), and various constraints (e.g., location, time, price, review, genre, cuisine, etc.) for filtering and ranking the search results.
In some embodiments, the digital assistant presents a list of search results on the conversation screen. In some embodiments, the digital assistant reads through the list of search results on the conversation screen to the user. In an eyes-free mode, the digital assistant optionally reads the list of search results to the user without presenting them on a conversation screen. In some embodiments, the digital assistant provides a speech output summarizing the search results, and presents more detailed information regarding the search results on the conversation screen.
In some embodiments, the search request is a restaurant search request, and search results that are presented to the user correspond to restaurants that are identified in accordance the restaurant search request. For example, when a digital assistant is active, the digital assistant monitors various input channels for user input (e.g., listens to capture the user's speech input and/or captures text or gesture inputs on the conversation screen). When the digital assistant captures a speech input from the user requesting a search for restaurants (e.g., a speech input “Find me a romantic Italian restaurant in Menlo Park.”), the digital assistant parses the speech input to determine the search criteria specified in the speech input (e.g., Task={Search or ConstrainedSelection}, SelectionClass=Restaurant, SearchConstraints={RestaurantCuisine=“Italian”, RestaurantQualifiers=“romantic”, RestaurantLocation=“Menlo Park”}). In some embodiments, one or more of the search criteria are based on context information such as other inputs from the user or saved preferences of the user.
After the search criteria of the search are determined, the digital assistant performs a search for restaurants according to the search criteria specified in the speech input and the context information. Then the digital assistant presents the search results to the user through the dialogue interface of the digital assistant.
In some embodiments, before the search is performed or before the search results are presented, the digital assistant provides a speech output through the dialogue interface, the speech output paraphrasing the search request received from the user. For example, when the user says “Find me a place to eat in Palo Alto.” The digital assistant can respond by saying “OK, searching for restaurants in Palo Alto.” For another example, when the user says “I want to have Italian for dinner today.” If the current time is close to dinner time, the digital assistant can respond by saying “OK, searching for Italian restaurants near your current location.”
In some embodiments, the digital assistant provides a speech output with the search results, where the speech output announces the one or more search criteria used to identify the search results. For example, after the digital assistant has performed a search for Italian restaurants in Palo Alto according to the user's request, the digital assistant announces the search results by saying “Here are five Italian restaurants I found in Palo Alto: . . . ” For another example, after the digital assistant has performed a search for restaurants near the user's current location, the digital assistant announces the search results by saying “I found a fast food restaurant and a French restaurant nearby: . . . ”
In some embodiments, after announcing the search results through a speech output, the digital assistant optionally read through the list of search results to the user. In some embodiments, both the announcement and the search results are presented on a conversation screen on the user device. In some embodiments, text representing the search criteria (e.g., restaurant, Italian, Palo Alto, nearby) used to identify the search results are highlighted in the announcement and/or the search results.
In some embodiments, the announcement for the search results can indicate changes (e.g., relaxation and/or variation) in the search criteria used to obtain to the search results. For example, when the user had requested to find a Malaysian restaurant in Palo Alto, and no Malaysian restaurants were found in Palo Alto, the digital assistant can expand the search area to include the nearby cities (e.g., Menlo Park). When the digital assistant presents the search results obtained from the expanded search, the digital assistant announces the search results by saying, “No Malaysian restaurants were found in Palo Alto, but I found one Malaysian restaurant in Menlo Park which borders Palo Alto.”
In some embodiments, the search request is an entertainment search request, and the search results correspond to a plurality of entertainment events identified in accordance the entertainment search request. Entertainment events refer to public activities and events related to entertainment and fun that generally occur at predetermined times and typically require a reservation or ticket for attendance. Examples of entertainment events include movies, shows, concerts, performances, sports games, tours, etc.
For example, when the digital assistant captures a speech input from the user requesting a search for a particular type of entertainment events (e.g., a speech input “Who's playing at the Fillmore next week?”), the digital assistant processes the speech input and determines that “the Fillmore” is the name of a music venue, and that the user is searching for concerts that are playing at the Fillmore next week. Based on the speech processing, the digital assistant obtains the search criteria specified in the speech input (e.g., Task={Search or Constrained Selection, SelectionClass=Entertainment Event, Sub-class=Concerts, SearchConstraints={Venue=“Fillmore,” Time=“next week”}). In some embodiments, one or more of the search criteria can be based on context information associated with the speech input, such as other inputs from the user or saved preferences of the user. After the search criteria of the entertainment event search are determined, the digital assistant performs a search for entertainment events (e.g., upcoming concerts) according to the search criteria specified in the speech input (e.g., Venue=Fillmore, and Time=next week) and the context information (e.g., the current date). Once the entertainment events meeting the search criteria have been identified, the digital assistant generates and presents the search results to the user through the dialogue interface of the digital assistant.
In some embodiments, before the search is performed or before the search results are presented, the digital assistant provides a speech output through the dialogue interface, the speech output paraphrasing the search request received from the user. For example, when the user's speech input was, “Who's playing at the Fillmore next week?” The digital assistant determines the search criteria based on the speech input, and paraphrases the search request by saying, “Searching for concerts at the Fillmore Concert Hall next week.”
In some embodiments, when paraphrasing the search request, the digital assistant provides both explicit search criteria and implicit search criteria derived from the context information in the paraphrase. For example, if the digital assistant had just booked a table for two at an Italian restaurant for Saturday evening at the user's request, and subsequently detected a speech input saying, “I want to catch a movie before the dinner What's on?” Based on the speech input, the digital assistant can determine explicit search criteria such as Task=Search, SelectionClass=Entertainment Events, Sub-class=Movies, and implicit search criteria such as Date=“Saturday evening”=(e.g., Jun. 9, 2012), Time=“before dinner”=(e.g., between 4:00 PM-6:00 PM), Location=“near restaurant”=(e.g., within 15 miles of Palo Alto). Therefore, when paraphrasing the search request, the digital assistant speaks or presents on the conversation screen, “Searching for movies playing between 4:00 PM to 6:00 PM on Saturday.”
In some embodiments, the digital assistant provides a speech output with the search results to announce one or more search criteria used to identify the search results. For example, when presenting the search results for the movie search in the above example, the digital assistant can provide a speech output saying “Here are movies that are showing before your dinner on Saturday: . . . ” or “I found 6 movies with show times between 4:00 PM and 6:00 PM on Saturday: . . . ” After announcing the search results through a speech output, the digital assistant optionally read through the list of search results to the user. In some embodiments, both the announcement and the search results are presented on a conversation screen on the user device. In some embodiments, text representing the search criteria (e.g., “movies”, “Saturday”, “before your dinner”, “between 4:00 PM and 6:00 PM”) used to identify the search results are highlighted in the announcement and/or the search results.
As shown in the examples above, in some embodiments, a search request includes context information associated with the speech input received from the user. In some embodiments, the digital assistant maintaining the context information based on one or more prior user interactions between the user and the digital assistant through the dialogue interface. More details on how context information is utilized have been provided in earlier sections of the specification. Examples of context information include personal interaction history (e.g., dialog history, previous selections from results, and the like), personal physical context (e.g., user's current location and the current time), and personal information gathered in the context of interaction (e.g., name, email addresses, physical addresses, phone numbers, account numbers, calendar information, contacts, preferences, and the like).
In some embodiments, the digital assistant determines at least some of the search criteria in the search request based at least in part on the context information associated with the speech input. After the search criteria are determined from the speech input and the associated context information, the digital assistant identifies reservable items in accordance with the search criteria that have been determined, and generate the search results based on the identified reservable items.
Below is another example in which context information is used to derive a search criterion of the search request. While the digital assistant is executing the reservation procedure at the user's request to purchase two tickets for a selected concert at the Fillmore for Saturday, or shortly after the reservation was made, the user provides a speech input through the dialogue interface saying, “Where can we eat before the concert?” In response to the speech input, and based on the context information already available to the digital assistant (e.g., the location and time for the concert), the digital assistant executes a restaurant search for places near the Fillmore that are open before the concert time on Saturday. In some embodiments, the digital assistant also infers a party-size requirement for the restaurant search request from the context information (e.g., the number of concert tickets that is being purchased), and presents only restaurants that have open tables meeting the party-size requirement as search results.
In some embodiments, after a search request is received from the user, the digital assistant determines based on the speech input and the associated context information that additional input from the user is needed to further constrain the search, or to sort the search results already obtained using the search criteria initially provided by the user. For example, when the user says “What's playing at the Fillmore?” The digital assistant will be able to determine that the user is interested in searching for events occurring at the Fillmore. However, without earlier user inputs or context information indicating a relevant time period for the search, the digital assistant will not be able to provide the most relevant search results. In such a scenario, the digital assistant determines that additional input from the user is needed or desirable to further constrain the search.
In some embodiments, upon determining that additional user input specifying one or more additional search criteria is needed or desirable, the digital assistant generates a speech output through the dialogue interface of the digital assistant to request the additional search criteria. For example, the digital assistant may provide a speech output saying, “OK, are you interested in all performances of this week? Or just the weekend?” In response to providing the speech output, the digital assistant receives additional inputs from the user through the dialogue interface, and supplements the search request with the additional inputs. For example, if the user says “Just this weekend.” Then, the digital assistant derives an additional search criterion {Date=“this weekend”=actual date range of the upcoming weekend (e.g., “Jun. 9-10, 2012”)} and supplements the original search request with this additional search criterion. If the user instead says, “Fine me performances for this Saturday only.” The digital assistant derives an additional search criterion {Date=“this Saturday”=actual date of the upcoming Saturday (e.g., Jun. 9, 2012)} and supplements the original search request with this additional search criterion. In some embodiments, the digital assistant also paraphrases the augmented search request to the user, by saying “OK, searching for performances at the Fillmore for this weekend” or “OK, searching for performances at the Fillmore for this Saturday.”
In some embodiments, the digital assistant can perform a search based on multiple search criteria specified in the original search request, and obtains some preliminary search results that do not meet all search criteria equally well. In such a scenario, in some embodiments, the digital assistant generates a speech input requesting additional input regarding the relative importance of the search criteria to the user. For example, if the original search request is for “romantic Italian restaurants in Palo Alto” and the digital assistant has identified non-Italian restaurants in Palo Alto that are considered romantic, romantic Italian restaurants that are just outside of Palo Alto, and Italian restaurants in Palo Alto that may or may not be considered romantic. Based on the mix of preliminary search results, the digital assistant generates an output requesting additional input regarding the relative importance of the three search criteria “RestaurantQualifiers=romantic,” “RestaurantCuisine=Italian,” and “RestaurantLocation=Palo Alto.” For example, the digital assistant can ask the user, “Which is more important, atmosphere, location, or cuisine?” Based on the user's subsequent input (e.g., a speech input saying “Cuisine and atmosphere.”), the digital assistant derives the additional constraint, and filters and/or ranks the search results according to the additional constraint (e.g., give more weight to the Cuisine and Atmosphere criteria).
In some embodiments, for each search result, the digital assistant presents one or more properties of the reservable item corresponding to the search result, where each property corresponds to one of the search criteria used in identifying the search results. For example, if the search request was for a place to eat before the concert, the properties shown along with the name of each restaurant in the search results can include the distance between the restaurant and the Fillmore (i.e., the location of the concert). For another example, if the search was for romantic Italian restaurants in Menlo Park, the digital assistant will present a snippet for each restaurant in the search results, and in the snippets, keywords such as “Italian” “Italy” “romantic” “nice atmosphere,” “Tuscany,” etc. are highlighted in the restaurant name, cuisine, and/or customer reviews.
In some embodiments, when presenting the search results, the digital assistant concurrently presenting one or more user interface elements in the dialogue interface (e.g., in the conversation screen) along with the plurality of search results. The user interface elements include, for example, links, buttons, and other interactive elements. In some embodiments, selection of one of the user interface elements causes presentation of additional information related to one or more of the search results in the dialogue interface. For example, a reviews user interface element causes more customer reviews for a selected search result to be presented through the dialogue interface. Alternatively, a reviews user interface element causes the interface of a restaurant review site to be loaded on the user device, and customer reviews for a selected search result are shown in their original format at the review site (i.e., selection of the reviews user interface element caused the review site to punch out of the dialogue interface of the digital assistant). Other examples of the user interface elements include links and buttons that cause presentation of a review, a map, a trailer, an availability summary, and a rating associated with one or more of the plurality of search results.
In some embodiments, when presenting the search results, the digital assistant also concurrently present one or more user interface elements in the dialogue interface (e.g., on a conversation screen) for invoking various follow-on actions regarding the search results. Selection of such a user interface element causes a follow-on action associated with one or more of the search results to be executed by the digital assistant. For example, in some embodiments, the digital assistant presents a call button for a search result. When the call button is invoked, it causes the digital assistant to initiates a telephone call to a telephone number associate with the search result (e.g., a telephone number associated with a restaurant or ticketing office). In some embodiments, the digital assistant presents a reviews button for each search result. When the reviews button is invoked, it causes the digital assistant to present reviews associated with the reservable item (e.g., restaurant, movies, concerts, etc.) corresponding to the search result. In some embodiments, the reviews are sourced from multiple third-party websites or services. In some embodiments, the digital assistant presents a directions button for each search result. When the directions button is invoked, it causes the digital assistant to generate a directions request for an address associated with the search result (e.g., the address of a restaurant identified by the search result). In response to the directions request, a directions interface can be presented with the address associated with the search result as the destination. Alternatively, a route between the user's current location and the address associated with the search result can be presented. In some embodiments, the directions interface or the route can be presented through the dialogue interface of the digital assistant, and the user can continue to interact with the digital assistant while reviewing the directions interface or the route. In some embodiments, the digital assistant presents one or more reservation or purchase user interface element (e.g., a reservation or buy button) for each search result. When one of the reservation or purchase user interface elements is invoked, the digital assistant initiates a reservation procedure for reserving or purchasing the reservable item (e.g., a table at a restaurant, tickets for an entertainment event) associated with the search result. In some embodiments, the digital assistant also presents user interface elements for sharing a link or saving a link to a search result.
As shown in
In the process 4800, in response to receiving the reservation request, the digital assistant executes a reservation procedure to reserve a respective reservable item corresponding to the particular search result while maintaining the dialogue interface to receive subsequent user input (4840). In some embodiments, the reservation procedure executed by the digital assistant reserves a table at a respective restaurant corresponding to the particular search result for which the reservation request was submitted. In some embodiments, the reservation procedure purchases or reserves one or more tickets for a respective entertainment events corresponding to the particular search result for which the reservation request was submitted.
In some embodiments, the digital assistant executes a reservation procedure to reserve a respective reservable item (e.g., a restaurant table or seating at an event) by invoking a task flow associated with the reservation task. In some embodiments, the task flow invokes third-party services (e.g., an online reservation service for restaurants or an online ticketing service for movies and other entertainment events) for making the requested reservation. In some embodiments, while executing the reservation procedure, the digital assistant and the user continue to communicate through the dialogue interface regarding the reservation process, and related transactions. For example, while executing the reservation procedure, the digital assistant can ask the user whether the user has any additional requirements for the reservation (e.g., dietary restrictions, party-size, wine preference, etc. for restaurant reservation, and seating preferences for event reservations).
In some embodiments, the digital assistant performs the requested reservation in the background, while the user and the digital assistant continue to interact regarding other search results, and/or other unrelated tasks and requests through the dialogue interface. For example, while the digital assistant executes the reservation procedure, the user can review the menu of the restaurant that is being reserved, or ask the digital assistant to search for a flower shop near the restaurant through the dialogue interface of the digital assistant.
In some embodiments, the task flow of the reservation task further includes generating and storing a reminder or calendar entry in accordance with the reservation. For example, after a reservation has been made successfully at a restaurant or after tickets have been purchase for an event by the digital assistant, the digital assistant generates a reminder or calendar entry for the reservation according to the date, time, and/or location of the reservation. In some embodiments, the digital assistant has access to the user's electronic calendars, and inserts the reminder or calendar entry directly into the user's calendars. In some embodiments, the digital assistant sends a request to a third-party service, e.g., an online calendar service, to insert the reminder or calendar entry in the user's calendar. In some embodiments, the digital assistant requests the user's permission through the dialogue interface before the reminder or calendar entry is created for the user.
In some embodiments, the task flow of the reservation task further includes generating an invitation for another user in accordance with the reservation. For example, in some embodiments, if the reservation is for more than one person (e.g., reservation for a table for two or more people at a restaurant, or purchasing of two or more tickets for an event), the digital assistant determines the identities of the people who will be invited to join the meal at the restaurant or to attend the entertainment event with the user. Once the identities of these other people have been determined, the digital assistant generates an invitation to those people.
In some embodiments, the digital assistant determines the identities of the invitees to the meal or event based on the context information collected during the dialogue session in which the reservation was made. For example, if the user had said “Make a reservation for me and my mom at this restaurant.” The digital assistant can determined the identity and contact information of the user's mom based on the user's contacts in the user's address book. In some embodiments, the digital assistant can offer to generate the invitation and prompt the user to provide the necessary contact information of the invitee(s).
The features provided above with respect to
For example, suppose that the user has bought a ticket for a particular movie through the digital assistant during a particular dialogue session. Afterwards, the user asks the digital assistant to find a restaurant near the movie theater by providing a speech input “Where can we eat after the movie?” In such a scenario, the digital assistant uses the context provided by the prior user interactions (e.g., purchasing the movie ticket) to determine which movie the user was referring to in the speech input. After determining that the user was referring to the particular movie for which the user has just purchased a ticket, the digital assistant is able to determine the date, time, and location associated with that movie. The digital assistant then uses the determined date, time, and location as the search criteria for the newly received search request (e.g., the restaurant search request). In other words, without having to require the user to explicitly repeat the name, date, time, and location of the movie, the digital assistant processed the user's speech input, and determined the appropriate search criteria for the newly received restaurant search request using context information, including prior user interactions between the digital assistant and the user.
In some embodiments, the digital assistant processes the speech input from the user along with the associated context information to determine whether additional input is required to clarify the search request, to further constraint a search, and/or to rank the relative importance of various search criteria specified in the search request. If the digital assistant determines that such additional input is needed or desirable, the digital assistant generates a speech output or a textual prompt to request such additional input.
In some embodiments, the digital assistant provides a speech output through the dialogue interface requesting at least one additional search criterion for the restaurant search request. In response to providing the speech output, the digital assistant receives additional input (e.g., a speech input responding to the digital assistant's request) from the user through the dialogue interface. The digital assistant processes the additional input and supplements the restaurant search request with the additional user input.
In some embodiments, the digital assistant also provides a speech input requesting the user to specify the relative importance among multiple search criteria. Once the digital assistant receives the additional user input specifying the relative importance among the multiple search criteria, the digital assistant ranks and/or filters the search results based on the additional user input.
In some embodiments, the digital assistant receives the speech input from the user, and processes the speech input and associated context information to identify a party-size requirement for the restaurant search request. For example, when the user says, “I want to invite my parents to a nice dinner on Saturday night, please find me a good restaurant.” Based on this speech input, the digital assistant can infer a party-size requirement of three (3), i.e., the user and the user's parents, for the restaurant search request.
In the above example, the digital assistant infers the party-size requirement from the user's speech input directly. In another example, if the user has just purchased two movie tickets through the digital assistant, and then asks the digital assistant, “Where can we eat before the movie?” Based on the context information associated with the speech input (i.e., the purchasing of the movie tickets), the digital assistant infers that the movie referred to in the speech input is the same movie for which the tickets have been purchased. In addition, based on the fact that two movie tickets have been purchased, the digital assistant infers a party-size requirement of two (2) (i.e., the two people who are going to the movie) for the restaurant search request. In some embodiments, the digital assistant generates a speech output requesting the user to provide a party-size requirement for the restaurant search, and obtains the party-size requirement from the user's additional input provided in response to the digital assistant's request.
In some embodiments, after the digital assistant determines the party-size requirement for the restaurant search request, the digital assistant identifies one or more restaurants each having at least one open table meeting the party-size requirement. In some embodiments, the digital assistant submits the party-size requirement along with one or more other search criteria of the restaurant search request to one or more third-party information sources (e.g., online restaurant search and reservation services), and requests that only restaurants meeting the party-size requirement be provided by the third-party information sources. In some embodiments, the digital assistant requests the availability information for restaurants that satisfy at least a minimum set of the search criteria, and select only restaurants that have at least one open table meeting the party-size requirement as potential search results.
In some embodiments, after the restaurants meeting the party-size requirement (as well as the other search criteria) have been identified, the digital assistant generates the search results based on the identified restaurants. In some embodiments, each search result presents information about a respective restaurant, and also availability information about the restaurant. For example, if the user's restaurant search request did not specify a date and time for the restaurant search, the search results optionally presents the date(s) and time slot(s) that have availability (i.e., open tables) meeting the party-size requirement of the restaurant search request.
In some embodiments, before presenting the search results to the user, the digital assistant ranks the search results based on information collected from multiple third-party information services. For example, in some embodiments, the digital assistant compiles the reviews of candidate restaurants from multiple online sources, and reconciles the differences among the reviews and ratings from the different online sources. In some embodiments, the digital assistant also removes duplicate information, and/or integrates different facets of information regarding the same candidate restaurant that are available from the different online sources. Then, after reconciling and integrating the information from the multiple online sources regarding the candidate restaurants, the digital assistant generates and ranks the search results based on the integrated and reconciled information. More details regarding how information from multiple sources are integrated and reconciled is provided in earlier sections of this specification.
In some embodiments, the digital assistant identifies multiple restaurants in accordance with the restaurant search request, and places a hold on a respective open reservation slot for each of the multiple restaurants. For example, if the user has specified a party-size requirement in the restaurant search request, or if the digital assistant has inferred the party-size requirement based on context information (e.g., prior user input, prior user interactions, or default user preferences, etc.), the digital assistant places a hold on a restaurant reservation slot (or an open table) satisfying the party-size requirement. In some embodiments, the hold is placed through an application program interface (API) of a third-party online restaurant reservation service. In some embodiments, the hold is automatically placed on each restaurant that has been determined to satisfy all of the search criteria of the restaurant search request. In some embodiments, a hold is not placed on restaurants that only satisfy some of the search criteria of the restaurant search request until an affirmative instruction to do so is provided by the user (e.g., through real-time input or through previously saved user preferences). In some embodiments, the hold is automatically released after a predetermined time period if no subsequent reservation procedure is performed to convert the hold to an actual reservation.
In some embodiments, after the search results are presented to the user through the dialogue interface of the digital assistant, the digital assistant receives a reservation request for one of the search results from the user through the dialogue interface of the digital assistant. In response to receiving the reservation request, the digital assistant executes a reservation procedure to make a reservation for a respective restaurant corresponding to the search result. More details on how the digital assistant receives the reservation request and executes the reservation procedure are provided with respect to
In some embodiments, the digital assistant receives a reservation request for one of the search results from the user through the dialogue interface of the digital assistant. In response to receiving the reservation request, if a hold has been placed for the restaurant corresponding to the search result, the digital assistant converts the hold placed for the respective restaurant to a reservation. After successfully converting the hold to the reservation, the digital assistant releases the holds placed on other restaurants that are not reserved. In some embodiments, the digital assistant requests a user confirmation before actually making the reservation. In some embodiments, the hold is placed without a party-size requirement, and the digital assistant requests the party-size requirement from the user when the user asks the digital assistant to convert a hold to an actual reservation.
In some embodiments, when presenting the search results to the user, the digital assistant concurrently presenting a predetermined number of search results through the dialogue interface each time. For example, the digital assistant provides no more than five results (e.g., 3-5 results) concurrently to the user. In some embodiments, more results are only presented to the user when the user requests to see more results. By limiting the number of concurrently presented search results to a small number (e.g., 3-5), the digital assistant can reduce the cognitive burden placed on the user when the user reviews the results.
In some embodiments, for each of the search results, the digital assistant presents one or more properties of the respective restaurant corresponding to the search result, where each property corresponds to a respective restaurant search criterion used in identifying the plurality of search results. For example, if distance from a particular location was used as a search criterion for the restaurant search, then, for each search result, the distance between that particular location and a respective restaurant corresponding to the search result can be presented for the search result. Other properties such as cuisine (e.g., French, Italian, pizza, vegetarian, American, burgers, Californian, etc.), atmosphere (e.g., romantic, nice, trendy, cool, clean, good, etc.), price (e.g., expensive, $$$, cheap, etc.), popularity (e.g., number of reviews, years in existence, number of good reviews, number of bad reviews, etc.) can also be presented for each search result when they are used as the restaurant search criteria.
In some embodiments, the digital assistant concurrently presents one or more user interface elements (e.g., a reviews tab, a maps button, a ratings link, etc.) in the dialogue interface (e.g., on the conversation screen) along with the plurality of search results, where selection of the user interface elements causes presentation of a review, a map, or a rating associated with a respective restaurant corresponding to a selected search result.
In some embodiments, the digital assistant concurrently presents one or more user interface elements (e.g., a call button, a review submission button or link, a link-saving button, a link-sharing button, a direction request button, a reservation button, etc.) in the dialogue interface (e.g., on the conversation screen) along with the plurality of search results. Selection of the user interface elements causes follow-on actions of: initiating a telephonic call to a third party, submitting a review, saving a link, sharing a link, requesting directions, or making a reservation, with regard to a respective restaurant corresponding to a selected search result.
In some embodiments, supplementing the speech input includes determining a search criterion that is not specified or referred to in the speech input. For example, the context information may be used to provide a location search criterion, while the speech input makes no mention of any location. In some embodiments, disambiguating the speech input includes determining that the speech input includes a term that has multiple reasonable interpretations, selecting one of the multiple reasonable interpretations based on the context information associated with the speech input, and generating a search criterion based on the selected interpretation.
In some embodiments, the context information associated with the speech input includes at least one prior interaction between the user and the digital assistant through the dialogue interface. In some embodiments, the context information includes information stored in one or more applications, such as a calendar application, an e-mail application, an instant messaging application, and an address book application. For example, if the user mentions a name or scheduled appointment in the speech input, the digital assistant can obtain more information about the person(s) associated with that name or information about the scheduled appointment by accessing the user's address book or calendar through the appropriate applications.
In some embodiments, the context information includes one or more of a current location, a current time, and current or forecasted weather information. In some embodiments, the context information includes information extracted from one or more speech inputs previously received through the dialogue interface. In some embodiments, the context information includes information extracted from one or more non-verbal input previously received through the dialogue interface. For example, the non-verbal input includes text input, pointer input, and gesture input received from the user through various input devices coupled to the user device.
In some embodiments, the digital assistant concurrently presents one or more user interface elements in the dialogue interface along with the search results. In some embodiments, one of the user interface elements is for downloading and playing a media file associated with a corresponding entertainment event search result. For example, among the search results for a movie search, a respective trailers button can be presented for each movie search result. Selection of the trailers button will cause a movie trailer to be downloaded and played on the user device. In some embodiments, user interface elements for presenting reviews, show times, and making reservations are also provided for each search result.
In some embodiments, after the digital assistant has provided the search results to the user through the dialogue interface, the digital assistant continue to communicate with the user through the dialogue interface. For example, the digital assistant can receive a follow-up speech input from the user requesting additional information. The requested additional information can be in regard to one or more of the search results previously presented through the dialogue interface (e.g., through speech outputs by the digital assistant, and/or presented on a conversation screen) or one or more search results that are currently presented on the conversation screen. For example, after the digital assistant presented a number of movie search results based on the user's initial search request through the dialogue interface, the user can provide a follow-up speech input requesting additional information regarding one or more of the movie search results by saying, “Are there other movies on this topic?” or “Show me some other movies by the same director.” or “Show me only movies that have a B+ rating.” For another example, after the user has viewed the trailer for one of the movie search results, the user can provide a follow-up speech input by saying, “Are there other movies played by the same actress?”
In some embodiments, in response to receiving the follow-up speech input, the digital assistant disambiguates at least part of the follow-up speech input to generate a search query for retrieving the requested additional information, where the disambiguating is based at least in part on one or more properties related to respective entertainment events corresponding to the search results. For example, suppose that the user selects one of the movie search results, and provides a follow-up speech input, “Are there other movies by the same director?” In response to the follow-up speech input, the digital assistant identifies the movie that corresponds to the selected search results, and determines a relevant property associated with movie, namely, the director for the movie. Based on the relevant property (e.g., the identity of the director for the movie), the digital assistant disambiguates the user's follow-up speech input, and generates a search query for retrieving movies that were directed by the identified director.
In some embodiments, the digital assistant retrieves the requested additional information based on the search query, and presents the information to the user through the dialogue interface of the digital assistant. Continuing with the above example, once the digital assistant has retrieved the search results for movies that were directed by the identified director, the digital assistant presents the newly retrieved search results to the user through the dialogue interface. The user and the digital assistant can continue to interact with each other through the dialogue interface with respect to the newly retrieved search results, the search results presented earlier, and/or a new search request.
In some embodiments, during a dialogue session in which a speech input was received, the digital assistant maintains a dialogue context based on user inputs received through the dialogue interface and information provided to the user through the dialogue interface. A dialogue session includes the exchange of speech input and output between the user and the digital assistant. In some embodiments, the dialogue session also includes requests and responses exchanged through other modalities, such as textual prompts provided by the digital assistant and textual response provided by the user, as well as notifications or alerts provided by the digital assistant and user inputs to address the notifications and alerts.
A dialogue session can be defined in various ways. In some embodiments, a dialogue session is defined by a predetermined duration, e.g., a period of several minutes, tens of minutes, one hour, one day, several days, or even longer. It is advantageous to keep the dialogue session within a reasonable length, e.g., less than half an hour, so that maintaining the context information does not take up too much computation resources. In addition, the user is more likely to refer back to an item mentioned recently in the dialogue, and therefore, it is not particularly necessary to define a very long dialogue session.
In some embodiments, a dialogue session is defined as continuous or intermittent interactions between the digital assistant and the user with no interruptions longer than a predetermined duration (e.g., 2 minutes or 5 minutes). For example, a user can interact with the digital assistant continuously for a while, punch out of the digital assistant's conversation screen to access another application, and then resumes interaction with the digital assistant afterwards. In this example, as long as the user resumes the interaction with the digital assistant before the predetermined duration required for maintaining the dialogue session expires, the dialogue session persists, and the dialogue context associated with the dialogue session is continuously maintained.
In some embodiments, a dialogue session is defined by a starting trigger event and an ending trigger event. For example, the user can press a button or speak a trigger phrase to invoke the active listening of the digital assistant and start the dialogue session. After interacting with the digital assistant during the dialogue session, the user can press the button or speak another trigger phrase to end the dialogue session. Other ways of defining a dialogue session is possible.
In some embodiments, during the dialogue session in which an initial speech input was received, the digital assistant receives one or more additional speech inputs from the user through the dialogue interface. The digital assistant processes each of the one or more additional speech inputs based on the dialogue context maintained by the digital assistant to determine a user intent expressed in the additional speech input. In some embodiments, the processing of the additional speech input includes supplementing and/or disambiguating the additional speech input based on the dialogue context. In some embodiments, the digital assistant provides additional information in response to each of the one or more additional speech inputs based on the processing.
In some embodiments, when the digital assistant has presented the entertainment search results (e.g., movie search results or concert search results), the digital assistant receives a reservation request for one or more of the search results from the user through the dialogue interface of the digital assistant. In response to receiving the reservation request, the digital assistant executes a reservation procedure to purchase one or more tickets for a respective entertainment event corresponding to the one or more search results.
In some embodiments, the digital assistant performs the reservation procedure in the background while the digital assistant and the user continue to interact through the dialogue interface. In some embodiments, during the reservation procedure, the digital assistant communicates with the user regarding various preferences (e.g.) and additional information (e.g., credit card information, payment authorization, etc.) regarding the reservation through the dialogue interface of the digital assistant. In some embodiments, the digital assistant loads the interface of a third-party online reservation service, and allows the user to make the reservation directly through the interface of the third-party online reservation service.
In some embodiments, during the dialogue session in which an initial speech input (e.g., the speech input initiating the entertainment search request) was received, the digital assistant receives a reservation request through the dialogue interface of the digital assistant after presentation of the search results has been replaced with other information in response to subsequent user inputs. In response to the reservation request, the digital assistant determines a target entertainment event of the reservation request based on the dialogue context, where the target entertainment event corresponds to one of the search results previously presented. Once the target entertainment event has been determined, the digital assistant executes a reservation procedure to purchase one or more tickets for the determined target entertainment event. The example below illustrates this process:
Suppose that the user had requested a movie search using an initial speech input “What movies are on this Saturday?” After the digital assistant had presented the list of movies that were showing this Saturday through the dialogue interface, the user asked to see some trailers for some of the movie results. In response, the digital assistant showed the trailers to the user, and as a result, the list of movies previously presented on the screen was replaced with the trailers. While the digital assistant interacts with the user regarding the movie search, the movie search results, and the trailers, the digital assistant maintained the dialogue context related to the current dialogue session. After the movie trailers were shown, the user submits a reservation request to the digital assistant, for example, using a speech input “Ok, get me a ticket for the dinosaur movie.” Based on the speech input and the dialogue context of the current dialogue session, the digital assistant identifies the trailers that have been reviewed by the user, and determines the movies that correspond to those trailers. The digital assistant then identifies the particular movie among those movies that relates to dinosaurs. Once that particular movie related to dinosaurs has been identified, the digital assistant initiates the reservation procedure for the target entertainment event (i.e., the particular dinosaur movie that has been identified). In some embodiments, the digital assistant announces the name of the movie before proceeding to make the reservation or purchase the ticket for the movie.
For another example, a movie domain includes vocabulary, domain entity data, and language patterns associated with movies, actors, directors, movie theatres, movie histories, etc. The movie domain also includes task flows, dialogue flows, and service capability models associated with movie/actor/director searches, movie ratings, downloading and playing movie trailers, reserving or buying movie tickets, and other questions and answers related to movies.
Similarly, in some embodiments, the digital assistant also implements a sports domain. The sports domain includes vocabulary, domain entities, language patterns, task flows, dialogue flows, and service capability models associated with searching for information on sports, performing tasks related to sporting events, sending short messages related to sports, trading sports-related memorabilia, and the like.
In some embodiments, the digital assistant implements a music domain. The music domain includes vocabulary, domain entities, language patterns, task flows, dialogue flows, and service capability models associated with searching for information on music and music-related people, events, and products, performing tasks related to music (e.g., purchasing CDs, albums, merchandises and/or downloading media files), and buying tickets to events (e.g., concerts, premieres, album signings).
In some embodiments, the digital assistant implements an entertainment domain. The entertainment domain includes vocabulary, domain entities, language patterns, task flows, dialogue flows, and service capability models associated with searching for information on entertainment-related people and events.
In some embodiments, the digital assistant implements a shopping domain. The shopping domain includes vocabulary, domain entities, language patterns, task flows, dialogue flows, and service models associated with searching for products and shopping.
In some embodiments, the digital assistant implements a gaming domain. The shopping domain includes vocabulary, domain entities, language patterns, task flows, dialogue flows, and service models associated with searching for information on games, gaming, gaming products, walkthroughs, making gaming-related purchases, and trade gaming-related virtual and real goods, equipments, and properties.
In some embodiments, each domain includes multiple sub-domains. For example, in some embodiments, the entertainment domain includes the movies domain, the sports domain, and the music domain. In some embodiments, the sports domain includes sub-domains for different sports. In some embodiments, the music domain includes sub-domains for different music genres. In some embodiments, the sub-domains may further include their own sub-domains, and the sub-domains may overlap.
In some embodiments, the digital assistant selectively provides information related to a domain of information in response to natural language requests from the user. For example, based on the vocabulary (e.g., particular keywords), domain entities (e.g., well-known people and entities), and/or language patterns (e.g., a particular query template or request pattern) commonly associated with requests for each information domain implemented by the digital assistant, the digital assistant is able to determine that the user's request is likely to be directed to a particular domain of information. Once the digital assistant has determined the likely domain of interest, natural language processing of the user's current and subsequent requests can be biased toward that particular domain to disambiguate the names of people, locations, entities, and user's intent expressed in the natural language request.
For example, vocabulary associated with the sports domain includes proper names and nicknames of different sports, athletes, sports teams, sporting events, and well-known sponsors of sporting events, brands for sporting goods, venues of sporting events and games, sport history, terms of art and jargons of different sports and games, and the like. The language patterns associated with the sports domain include keywords and phrases such as “what's the score for . . . ”, “who is playing against . . . ?” “which team won the . . . ”, “what's the game stats for . . . ”, and so on. Based on the sports-related vocabulary and language patterns, the digital assistant can infer whether a user's request is related to the sports domain.
For another example, for the music domain, user often ask questions related to music, genres, billboard rankings of songs and albums, lyrics, albums and tours for particular artists, news about famous artists, the latest hits, and the like. The vocabulary associated with the music domain would include proper names and nicknames of musicians, singers, songs, genres, music groups, etc. The language patterns associated with the music domain include keywords and phrases such as “show me the lyrics for . . . ” “What's the name of the song that . . . ” “Who sang the song . . . ” “What's the latest song by . . . ”, and so on. Based on the music-related vocabulary and language patterns, the digital assistant can infer whether a user's request is related to the music domain.
In some embodiments, the digital assistant stores a collection of common query types representing the type of questions that user frequently ask in a particular information domain. For example, for the sports domain, users often ask questions related to game scores and player statistics, game times, team rosters, athlete salaries, player and/or team history, and current sports news. For the music domain, users often ask questions related to artists, genre, lyrics, the latest hits, classics, famous songs, well-known lines in particular songs, and so on.
In some embodiments, the digital assistant also implements sub-domains of common query types related to famous personalities and entities in the domain. For example, in some embodiments, in the sports domain, the digital assistant also implements sub-domains of common query types revolved around famous athletes, sports teams, and sports events, such as “Kobe-related questions,” “Giants-related questions”, “Super Bowl related questions, and the like. In some embodiments, for the music domain, the digital assistant can implement sub-domains of common query types related to famous singers, songs, and genres, such as “Elvis-related questions” “Blues-related questions”, “Hip-Pop-related questions, and the like.
As shown in
In the process 5100, the digital assistant receives a speech input from a user through a dialogue interface of a digital assistant (5104). The digital assistant determines context information associated with the speech input (5106). The digital assistant processes the speech input to determine one or more search criteria, where the processing includes supplementing and/or disambiguating the speech input using the context information and the vocabulary associated with the predetermined domain of information (5108).
For example, if the user's speech input include sports-related vocabulary, once the digital assistant detects the sports-related vocabulary, (e.g., keywords or language patterns associated with a predetermined query type stored in the sports domain), the digital assistant supplements and/or disambiguate the speech input using context information and the vocabulary associated with the sports domain. For a more detailed example, suppose the user says, “Who is playing the Lakers tonight?” From this speech input, the digital assistant recognizes the sports-related vocabulary “the Lakers” and the sports-related language pattern “Who is playing [a sports team] . . . ” which have both been stored in the sports domain of the digital assistant. As a result, the digital assistant determines that the user is interested in sports-related information. The digital assistant also uses the context information (e.g., the current date) to determine which date the user is referring to by the word “tonight” in the speech input. After the digital assistant has fully disambiguated the user's speech input, the digital assistant proceeds to perform a search to retrieve the requested information. Specifically, the digital assistant retrieves the name of the team that is playing against the Lakers in the evening of the current date.
For another more detailed example, suppose the user asks, “How did Lebron do last night?” According to the vocabulary (e.g., including proper and nicknames of basketball players) and domain entities (e.g., data records on players and sports teams) stored under the sports domain, the digital assistant recognizes that “Lebron” is the name of a famous basketball player “LeBron James”, and a current member of an NBA team called the “Miami Heat”. Based on the language pattern “How did [player name] do . . . ” stored under the sports domain, the digital assistant also recognizes that the user is asking a question related to player game statistics (i.e., a predetermined query type stored under the sports domain). After the digital assistant recognizes that the user is interested in knowing the game statistics for a basketball player of a particular team, the digital assistant uses the context information (e.g., the current date) to determine which game the Miami Heat played the day before, and proceeds the retrieve the game statistics for LeBron James for that game.
As shown in the example above, in the process 5100, the digital assistant retrieves information related to the predetermined domain of information (e.g., the sports domain) in accordance with the one or more search criteria (e.g., {query type=player's game statistics, player name=LeBron James, Team=Miami Heat, game date=yesterday=e.g., Jun. 8, 2012}) (5110). After the information is retrieved based on the search criteria, the digital assistant presents the retrieved information to the user through the dialogue interface of the digital assistant (5112). For example, the digital assistant can produce a speech output to the user saying, “LeBron did well last night, 30 points, 8 rebounds, and 2 assists.”
In some embodiments, after the digital assistant has established that the user is interested in a particular domain of information (e.g., after the digital assistant has satisfactorily answered a user's question related to the sport domain), the digital assistant can continue the conversation with the user within the sports domain. In some embodiments, the digital assistant carries on the conversation (e.g., continued questions and answers) by maintaining a dialogue context of the conversation. The dialogue context keeps track of what information have been asked and received by the user, at which time, and/or in which order.
For example, in some embodiments, during a dialogue session in which a speech input (e.g., an initial user question related to a particular domain of information) was received, the digital assistant maintains a dialogue context based on user inputs received through the dialogue interface and information provided to the user through the dialogue interface. Then, during the same dialogue session, the digital assistant receives one or more additional speech inputs from the user through the dialogue interface. The digital assistant processes each of the one or more additional speech inputs based on the dialogue context to determine the user intent expressed in the additional speech input. In some embodiments, the processing includes supplementing and/or disambiguating the additional speech inputs based on the dialogue context. Then, based on the processing, the digital assistant provides additional information in response to each of the one or more additional speech inputs.
Continuing with the above sport-related example, during the dialogue session in which the user asked about LeBron James' game statistics, the digital assistant maintains the dialogue context and keeps track of what the user has asked about, and what information has been provided to the user, at which times, and/or in which order. Suppose that, after hearing LeBron's game statistics, the user asks another question through an additional speech input “What about Kobe?” Based on this speech input, the digital assistant is able to identify that “Kobe” also refers to a basketball player. Based on the dialogue context stored by the digital assistant, the digital assistant determines that the user has just asked and received answers about the game statistics for another basketball player “LeBron James.” Therefore, the digital assistant interprets the user's question “What about Kobe” as a request for game statistics for Kobe Bryant. In some implementations, the digital assistant performs the task flow for retrieving player game statistics as previously performed, except for replacing the player name “LeBron James” with a different player name “Kobe Bryant.” Once the digital assistant retrieves the player game statistics for Kobe Bryant for last night, and the digital assistant presents the game statistics to the user through the dialogue interface through a speech output, “Kobe also did well last night, 30 points, 4 rebounds, and 4 assists.”
In some embodiments, for some query types, the digital assistants implements dialogue flows that offer to provide the user with additional information related to the user's current questions. For example, after the digital assistant provided the game statistics information about particular players, the digital assistant can offer to show a video clip of the game in which the players had scored. For example, after the digital assistant has provided the user with Kobe's game statistics last night, the digital assistant can ask the user “Would you like to see a video clip of the game?” If the user accepts, the digital assistant proceeds to play the video clip for the game last night in which Kobe has scored.
Suppose that after the digital assistant has provided Kobe's game statistics to the user, or after the video clips are shown to the user, the conversation between the digital assistant and the user continues. For example, the user then asks, “So, who makes more money?” The digital assistant identifies that the user's input matches a language pattern (e.g., “makes . . . money”) associated with a query type “player salaries” stored under the sports domain. Based on the dialogue context stored for the current dialogue session, the digital assistant determines that two basketball players (e.g., LeBron James and Kobe Bryant) have been mentioned in the most recent exchange between the user and the digital assistant. Based on the dialogue context, the digital assistant disambiguates the user's input and interprets the user's input as a question about the salaries of the two basketball players, and specifically, a comparison between the salaries of the two basketball players. After the digital assistant determines the user's intent, the digital assistant proceeds to retrieve the salary information about the two players, and formulate an output comparing the salaries of the two players. For example, the digital assistant can provide a speech output saying, “Based on my sources, Kobe made X dollars in 2011 in salaries, and LeBron made Y dollars in 2011 in salaries.”
In some embodiments, the digital assistant implements a dialogue flow to provide additional related information that may be of interest to the user. For example, in the dialogue flow associated with the player salary related queries, the digital assistant can provide information on product sponsorship by the players, and deals on the sponsored products. For example, the based on the dialogue flow, instead of a plain answer to the user's question regarding player salaries, the digital assistant provides a speech output saying, “Based on my sources, Kobe made X dollars in 2011 in salaries, and LeBron made Y dollars in 2011 in salaries. Both Kobe and LeBron contribute to charities. Would you like to join them in supporting the “After-School All-Stars” a national children's charity that provides after-school programs to inner-city kids?” If the user answers in the affirmative, the digital assistant invokes an appropriate task flow to initiate a donation procedure for the user.
In some embodiments, the digital assistant implements a dialogue flow to provide related information that may be of interest to the user if the digital assistant cannot provide a satisfactory answer to the user's original question. For example, if the user asks the digital assistant “Who is a better player?” The digital assistant determines that it is not able to provide a satisfactory answer to this complex question. As a result, the digital assistant provides an output that says “That's a touch question. But did you know that Kobe and LeBron both likes to tweet? But LeBron has four times more followers on Twitter™?”
Although the above examples are provided in the context of the sports domain, vocabulary, task flows, dialogue flows for other domains can be implemented in an analogous manner. For example, the digital assistant can also implement an entertainment domain to answer users' questions about celebrities, and the entertainment industry; a travels domain to answer users' questions about traveling, sight-seeing, and local and foreign cultures; a gaming domain to answer users' questions about games, gaming gadgets, walkthroughs, competitions, etc. Other domains are also possible.
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, Calif., 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.
This application is a continuation of U.S. patent application Ser. No. 13/913,336, entitled “INTELLIGENT AUTOMATED ASSISTANT,” filed Jun. 7, 2013, which is a continuation-in-part application of and claims priority to U.S. patent application Ser. No. 12/987,982, entitled “Intelligent Automated Assistant,” filed Jan. 10, 2011, which claims the benefit of U.S. Provisional Application Ser. No. 61/295,774, filed Jan. 18, 2010. This application further claims the benefit of U.S. Provisional Application Ser. No. 61/657,736, entitled “Intelligent Automated Assistant,” filed Jun. 8, 2012. All of the above-mentioned applications are incorporated herein by reference in their entirety. This application is further related to (1) U.S. application Ser. No. 11/518,292, filed Sep. 8, 2006, entitled “Method and Apparatus for Building an Intelligent Automated Assistant;” (2) U.S. Provisional Application Ser. No. 61/186,414 filed Jun. 12, 2009, entitled “System and Method for Semantic Auto-Completion;” (3) U.S. application Ser. No. 13/725,512, filed Dec. 21, 2012, entitled “Active Input Elicitation by Intelligent Automated Assistant,”; (4) U.S. application Ser. No. 13/725,550, filed Dec. 21, 2012, entitled “Determining User Intent Based on Ontologies of Domains,”; (5) U.S. application Ser. No. 13/725,616, filed Dec. 21, 2012, entitled “Service Orchestration for Intelligent Automated Assistant,”; (6) U.S. application Ser. No. 13/725,656, filed Dec. 21, 2012, entitled “Prioritizing Selection Criteria by Automated Assistant,”; (7) U.S. application Ser. No. 13/725,713, filed Dec. 21, 2012, entitled “Disambiguation Based on Active Input Elicitation by Intelligent Automated Assistant,”; (8) U.S. application Ser. No. 13/784,694, filed Mar. 4, 2013, entitled “Paraphrasing of User Request by Automated Digital Assistant,”; (9) U.S. application Ser. No. 13/784,707, filed Mar. 4, 2013, entitled “Maintaining Context Information Between User Interactions with a Voice Assistant,”; (10) U.S. application Ser. No. 13/725,742, filed Dec. 21, 2012, entitled “Intent Deduction Based on Previous User Interactions with a Voice Assistant,”; and (11) U.S. application Ser. No. 13/725,761, filed Dec. 21, 2012, entitled “Using Event Alert Text as Input to an Automated Assistant,”, all of which are incorporated herein by reference in their entirety. This application is 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.
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 |
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 |
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 |
7475010 | Chao | Jan 2009 | B2 |
7475015 | Epstein et al. | Jan 2009 | B2 |
7475063 | Datta et al. | Jan 2009 | B2 |
7477238 | Fux et al. | Jan 2009 | B2 |
7477240 | Yanagisawa | Jan 2009 | B2 |
7478037 | Strong | Jan 2009 | B2 |
7478091 | Mojsilovic et al. | Jan 2009 | B2 |
7478129 | Chemtob | Jan 2009 | B1 |
7479948 | Kim et al. | Jan 2009 | B2 |
7479949 | Jobs et al. | Jan 2009 | B2 |
7483832 | Tischer | Jan 2009 | B2 |
7483894 | Cao | Jan 2009 | B2 |
7487089 | Mozer | Feb 2009 | B2 |
7487093 | Mutsuno et al. | Feb 2009 | B2 |
7490034 | Finnigan et al. | Feb 2009 | B2 |
7490039 | Shaffer et al. | Feb 2009 | B1 |
7493251 | Gao et al. | Feb 2009 | B2 |
7493560 | Kipnes et al. | Feb 2009 | B1 |
7496498 | Chu et al. | Feb 2009 | B2 |
7496512 | Zhao et al. | Feb 2009 | B2 |
7499923 | Kawatani | Mar 2009 | B2 |
7502738 | Kennewick et al. | Mar 2009 | B2 |
7505795 | Lim et al. | Mar 2009 | B1 |
7508324 | Suraqui | Mar 2009 | B2 |
7508373 | Lin et al. | Mar 2009 | B2 |
7516123 | Betz et al. | Apr 2009 | B2 |
7519327 | White | Apr 2009 | B2 |
7519398 | Hirose | Apr 2009 | B2 |
7522927 | Fitch et al. | Apr 2009 | B2 |
7523036 | Akabane et al. | Apr 2009 | B2 |
7523108 | Cao | Apr 2009 | B2 |
7526466 | Au | Apr 2009 | B2 |
7526738 | Ording et al. | Apr 2009 | B2 |
7528713 | Singh et al. | May 2009 | B2 |
7529671 | Rockenbeck et al. | May 2009 | B2 |
7529676 | Koyama | May 2009 | B2 |
7529677 | Wittenber | May 2009 | B1 |
7535997 | McQuaide, Jr. et al. | May 2009 | B1 |
7536029 | Choi et al. | May 2009 | B2 |
7536565 | Girish et al. | May 2009 | B2 |
7538685 | Cooper et al. | May 2009 | B1 |
7539619 | Seligman et al. | May 2009 | B1 |
7539656 | Fratkina et al. | May 2009 | B2 |
7541940 | Upton | Jun 2009 | B2 |
7542967 | Hurst-Hiller et al. | Jun 2009 | B2 |
7542971 | Thione et al. | Jun 2009 | B2 |
7543232 | Easton, Jr. et al. | Jun 2009 | B2 |
7546382 | Healey et al. | Jun 2009 | B2 |
7546529 | Reynar et al. | Jun 2009 | B2 |
7548895 | Pulsipher | Jun 2009 | B2 |
7552045 | Barliga et al. | Jun 2009 | B2 |
7552055 | Lecoeuche | Jun 2009 | B2 |
7555431 | Bennett | Jun 2009 | B2 |
7555496 | Lantrip et al. | Jun 2009 | B1 |
7558381 | Ali et al. | Jul 2009 | B1 |
7558730 | Davis et al. | Jul 2009 | B2 |
7559026 | Girish et al. | Jul 2009 | B2 |
7561069 | Horstemeyer | Jul 2009 | B2 |
7562007 | Hwang | Jul 2009 | B2 |
7562032 | Abbosh et al. | Jul 2009 | B2 |
7565104 | Brown et al. | Jul 2009 | B1 |
7565380 | Venkatachary | Jul 2009 | B1 |
7568151 | Bargeron et al. | Jul 2009 | B2 |
7571092 | Nieh | Aug 2009 | B1 |
7571106 | Cao et al. | Aug 2009 | B2 |
7577522 | Rosenberg | Aug 2009 | B2 |
7580551 | Srihari et al. | Aug 2009 | B1 |
7580576 | Wang et al. | Aug 2009 | B2 |
7580839 | Tamura et al. | Aug 2009 | B2 |
7584092 | Brockett et al. | Sep 2009 | B2 |
7584093 | Potter et al. | Sep 2009 | B2 |
7584278 | Rajarajan et al. | Sep 2009 | B2 |
7584429 | Fabritius | Sep 2009 | B2 |
7593868 | Margiloff et al. | Sep 2009 | B2 |
7596269 | King et al. | Sep 2009 | B2 |
7596499 | Anguera et al. | Sep 2009 | B2 |
7596606 | Codignotto | Sep 2009 | B2 |
7596765 | Almas | Sep 2009 | B2 |
7599918 | Shen et al. | Oct 2009 | B2 |
7603349 | Kraft et al. | Oct 2009 | B1 |
7603381 | Burke et al. | Oct 2009 | B2 |
7603684 | Ellis | Oct 2009 | B1 |
7606444 | Erol et al. | Oct 2009 | B1 |
7606712 | Smith et al. | Oct 2009 | B1 |
7607083 | Gong et al. | Oct 2009 | B2 |
7609179 | Diaz-Gutierrez et al. | Oct 2009 | B2 |
7610258 | Yuknewicz et al. | Oct 2009 | B2 |
7613264 | Wells et al. | Nov 2009 | B2 |
7614008 | Ording | Nov 2009 | B2 |
7617094 | Aoki et al. | Nov 2009 | B2 |
7620407 | Donald et al. | Nov 2009 | B1 |
7620549 | Di Cristo et al. | Nov 2009 | B2 |
7620894 | Kahn | Nov 2009 | B1 |
7623119 | Autio et al. | Nov 2009 | B2 |
7624007 | Bennett | Nov 2009 | B2 |
7627481 | Kuo et al. | Dec 2009 | B1 |
7630900 | Strom | Dec 2009 | B1 |
7630901 | Omi | Dec 2009 | B2 |
7633076 | Huppi et al. | Dec 2009 | B2 |
7634409 | Kennewick et al. | Dec 2009 | B2 |
7634413 | Kuo et al. | Dec 2009 | B1 |
7634718 | Nakajima | Dec 2009 | B2 |
7634732 | Blagsvedt et al. | Dec 2009 | B1 |
7636657 | Ju et al. | Dec 2009 | B2 |
7640158 | Detlef et al. | Dec 2009 | B2 |
7640160 | Di Cristo et al. | Dec 2009 | B2 |
7643990 | Bellegarda | Jan 2010 | B1 |
7647225 | Bennett et al. | Jan 2010 | B2 |
7649454 | Singh et al. | Jan 2010 | B2 |
7649877 | Vieri et al. | Jan 2010 | B2 |
7653883 | Hotelling et al. | Jan 2010 | B2 |
7656393 | King et al. | Feb 2010 | B2 |
7657424 | Bennett | Feb 2010 | B2 |
7657430 | Ogawa | Feb 2010 | B2 |
7657828 | Lucas et al. | Feb 2010 | B2 |
7657844 | Gibson et al. | Feb 2010 | B2 |
7657849 | Chaudhri et al. | Feb 2010 | B2 |
7660715 | Thambiratnam | Feb 2010 | B1 |
7663607 | Hotelling et al. | Feb 2010 | B2 |
7664558 | Lindahl et al. | Feb 2010 | B2 |
7664638 | Cooper et al. | Feb 2010 | B2 |
7668710 | Doyle | Feb 2010 | B2 |
7669134 | Christie et al. | Feb 2010 | B1 |
7672841 | Bennett | Mar 2010 | B2 |
7672952 | Isaacson et al. | Mar 2010 | B2 |
7673238 | Girish et al. | Mar 2010 | B2 |
7673251 | Wibisono | Mar 2010 | B1 |
7673340 | Cohen et al. | Mar 2010 | B1 |
7676026 | Baxter, Jr. | Mar 2010 | B1 |
7676365 | Hwang et al. | Mar 2010 | B2 |
7676463 | Thompson et al. | Mar 2010 | B2 |
7679534 | Kay et al. | Mar 2010 | B2 |
7680649 | Park | Mar 2010 | B2 |
7681126 | Roose | Mar 2010 | B2 |
7683886 | Willey | Mar 2010 | B2 |
7683893 | Kim | Mar 2010 | B2 |
7684985 | Dominach et al. | Mar 2010 | B2 |
7684990 | Caskey et al. | Mar 2010 | B2 |
7684991 | Stohr et al. | Mar 2010 | B2 |
7689245 | Cox et al. | Mar 2010 | B2 |
7689408 | Chen et al. | Mar 2010 | B2 |
7689409 | Heinecke | Mar 2010 | B2 |
7689412 | Wu et al. | Mar 2010 | B2 |
7689421 | Li et al. | Mar 2010 | B2 |
7693715 | Hwang et al. | Apr 2010 | B2 |
7693717 | Kahn et al. | Apr 2010 | B2 |
7693719 | Chu et al. | Apr 2010 | B2 |
7693720 | Kennewick et al. | Apr 2010 | B2 |
7698131 | Bennett | Apr 2010 | B2 |
7702500 | Blaedow | Apr 2010 | B2 |
7702508 | Bennett | Apr 2010 | B2 |
7703091 | Martin et al. | Apr 2010 | B1 |
7706510 | Ng | Apr 2010 | B2 |
7707026 | Liu | Apr 2010 | B2 |
7707027 | Balchandran et al. | Apr 2010 | B2 |
7707032 | Wang et al. | Apr 2010 | B2 |
7707221 | Dunning et al. | Apr 2010 | B1 |
7707226 | Tonse | Apr 2010 | B1 |
7707267 | Lisitsa et al. | Apr 2010 | B2 |
7710262 | Ruha | May 2010 | B2 |
7711129 | Lindahl et al. | May 2010 | B2 |
7711550 | Feinberg et al. | May 2010 | B1 |
7711565 | Gazdzinski | May 2010 | B1 |
7711672 | Au | May 2010 | B2 |
7712053 | Bradford et al. | May 2010 | B2 |
7716056 | Weng et al. | May 2010 | B2 |
7716216 | Harik et al. | May 2010 | B1 |
7720674 | Kaiser et al. | May 2010 | B2 |
7720683 | Vermeulen et al. | May 2010 | B1 |
7721226 | Barabe et al. | May 2010 | B2 |
7721301 | Wong et al. | May 2010 | B2 |
7724242 | Hillis et al. | May 2010 | B2 |
7724696 | Parekh | May 2010 | B1 |
7725307 | Bennett | May 2010 | B2 |
7725318 | Gavalda et al. | May 2010 | B2 |
7725320 | Bennett | May 2010 | B2 |
7725321 | Bennett | May 2010 | B2 |
7725838 | Williams | May 2010 | B2 |
7729904 | Bennett | Jun 2010 | B2 |
7729916 | Coffman et al. | Jun 2010 | B2 |
7734461 | Kwak et al. | Jun 2010 | B2 |
7735012 | Naik | Jun 2010 | B2 |
7739588 | Reynar et al. | Jun 2010 | B2 |
7742953 | King et al. | Jun 2010 | B2 |
7743188 | Haitani et al. | Jun 2010 | B2 |
7747616 | Yamada et al. | Jun 2010 | B2 |
7752152 | Paek et al. | Jul 2010 | B2 |
7756707 | Garner et al. | Jul 2010 | B2 |
7756708 | Cohen et al. | Jul 2010 | B2 |
7756868 | Lee | Jul 2010 | B2 |
7756871 | Yacoub et al. | Jul 2010 | B2 |
7757173 | Beaman | Jul 2010 | B2 |
7757176 | Vakil et al. | Jul 2010 | B2 |
7757182 | Elliott et al. | Jul 2010 | B2 |
7761296 | Bakis et al. | Jul 2010 | B1 |
7763842 | Hsu et al. | Jul 2010 | B2 |
7774202 | Spengler et al. | Aug 2010 | B2 |
7774204 | Mozer et al. | Aug 2010 | B2 |
7774388 | Runchey | Aug 2010 | B1 |
7777717 | Fux et al. | Aug 2010 | B2 |
7778432 | Larsen | Aug 2010 | B2 |
7778595 | White et al. | Aug 2010 | B2 |
7778632 | Kurlander et al. | Aug 2010 | B2 |
7778830 | Davis et al. | Aug 2010 | B2 |
7779353 | Grigoriu et al. | Aug 2010 | B2 |
7779356 | Griesmer | Aug 2010 | B2 |
7779357 | Naik | Aug 2010 | B2 |
7783283 | Kuusinen et al. | Aug 2010 | B2 |
7783486 | Rosser et al. | Aug 2010 | B2 |
7788590 | Taboada et al. | Aug 2010 | B2 |
7788663 | Illowsky et al. | Aug 2010 | B2 |
7796980 | McKinney et al. | Sep 2010 | B1 |
7797265 | Brinker et al. | Sep 2010 | B2 |
7797269 | Rieman et al. | Sep 2010 | B2 |
7797331 | Theimer et al. | Sep 2010 | B2 |
7797629 | Fux et al. | Sep 2010 | B2 |
7801721 | Rosart et al. | Sep 2010 | B2 |
7801728 | Ben-David et al. | Sep 2010 | B2 |
7801729 | Mozer | Sep 2010 | B2 |
7805299 | Coifman | Sep 2010 | B2 |
7809550 | Barrows | Oct 2010 | B1 |
7809565 | Coifman | Oct 2010 | B2 |
7809569 | Attwater et al. | Oct 2010 | B2 |
7809570 | Kennewick et al. | Oct 2010 | B2 |
7809610 | Cao | Oct 2010 | B2 |
7809744 | Nevidomski et al. | Oct 2010 | B2 |
7818165 | Carlgren et al. | Oct 2010 | B2 |
7818176 | Freeman et al. | Oct 2010 | B2 |
7818215 | King et al. | Oct 2010 | B2 |
7818291 | Ferguson et al. | Oct 2010 | B2 |
7818672 | Mccormack et al. | Oct 2010 | B2 |
7822608 | Cross, Jr. et al. | Oct 2010 | B2 |
7823123 | Sabbouh | Oct 2010 | B2 |
7826945 | Zhang et al. | Nov 2010 | B2 |
7827047 | Anderson et al. | Nov 2010 | B2 |
7831246 | Smith et al. | Nov 2010 | B1 |
7831423 | Schubert | Nov 2010 | B2 |
7831426 | Bennett | Nov 2010 | B2 |
7831432 | Bodin et al. | Nov 2010 | B2 |
7835504 | Donald et al. | Nov 2010 | B1 |
7836437 | Kacmarcik et al. | Nov 2010 | B2 |
7840348 | Kim et al. | Nov 2010 | B2 |
7840400 | Lavi et al. | Nov 2010 | B2 |
7840447 | Kleinrock et al. | Nov 2010 | B2 |
7840581 | Ross et al. | Nov 2010 | B2 |
7840912 | Elias et al. | Nov 2010 | B2 |
7844394 | Kim | Nov 2010 | B2 |
7848924 | Nurminen et al. | Dec 2010 | B2 |
7848926 | Goto et al. | Dec 2010 | B2 |
7853444 | Wang et al. | Dec 2010 | B2 |
7853445 | Bachenko et al. | Dec 2010 | B2 |
7853574 | Kraenzel et al. | Dec 2010 | B2 |
7853577 | Sundaresan et al. | Dec 2010 | B2 |
7853664 | Wang et al. | Dec 2010 | B1 |
7853900 | Nguyen et al. | Dec 2010 | B2 |
7865817 | Ryan et al. | Jan 2011 | B2 |
7869998 | Di Fabbrizio et al. | Jan 2011 | B1 |
7869999 | Amato et al. | Jan 2011 | B2 |
7870118 | Jiang et al. | Jan 2011 | B2 |
7870133 | Krishnamoorthy et al. | Jan 2011 | B2 |
7873149 | Schultz et al. | Jan 2011 | B2 |
7873519 | Bennett | Jan 2011 | B2 |
7873654 | Bernard | Jan 2011 | B2 |
7877705 | Chambers et al. | Jan 2011 | B2 |
7880730 | Robinson et al. | Feb 2011 | B2 |
7881283 | Cormier et al. | Feb 2011 | B2 |
7881936 | Longe et al. | Feb 2011 | B2 |
7885390 | Chaudhuri et al. | Feb 2011 | B2 |
7885844 | Cohen et al. | Feb 2011 | B1 |
7886233 | Rainisto et al. | Feb 2011 | B2 |
7889101 | Yokota | Feb 2011 | B2 |
7889184 | Blumenberg et al. | Feb 2011 | B2 |
7889185 | Blumenberg et al. | Feb 2011 | B2 |
7890330 | Ozkaragoz et al. | Feb 2011 | B2 |
7890652 | Bull et al. | Feb 2011 | B2 |
7895039 | Braho et al. | Feb 2011 | B2 |
7895531 | Radtke et al. | Feb 2011 | B2 |
7899666 | Varone | Mar 2011 | B2 |
7904297 | Mirkovic et al. | Mar 2011 | B2 |
7908287 | Katragadda | Mar 2011 | B1 |
7912289 | Kansal et al. | Mar 2011 | B2 |
7912699 | Saraclar et al. | Mar 2011 | B1 |
7912702 | Bennett | Mar 2011 | B2 |
7912720 | Hakkani-Tur et al. | Mar 2011 | B1 |
7912828 | Bonnet et al. | Mar 2011 | B2 |
7913185 | Benson et al. | Mar 2011 | B1 |
7916979 | Simmons | Mar 2011 | B2 |
7917367 | Di Cristo et al. | Mar 2011 | B2 |
7917497 | Harrison et al. | Mar 2011 | B2 |
7920678 | Cooper et al. | Apr 2011 | B2 |
7920682 | Byrne et al. | Apr 2011 | B2 |
7920857 | Lau et al. | Apr 2011 | B2 |
7925525 | Chin | Apr 2011 | B2 |
7925610 | Elbaz et al. | Apr 2011 | B2 |
7929805 | Wang et al. | Apr 2011 | B2 |
7930168 | Weng et al. | Apr 2011 | B2 |
7930183 | Odell et al. | Apr 2011 | B2 |
7930197 | Ozzie et al. | Apr 2011 | B2 |
7936339 | Marggraff et al. | May 2011 | B2 |
7936861 | Martin et al. | May 2011 | B2 |
7936863 | John et al. | May 2011 | B2 |
7937075 | Zellner | May 2011 | B2 |
7941009 | Li et al. | May 2011 | B2 |
7945294 | Zhang et al. | May 2011 | B2 |
7945470 | Cohen et al. | May 2011 | B1 |
7949529 | Weider et al. | May 2011 | B2 |
7949534 | Davis et al. | May 2011 | B2 |
7949752 | Lange et al. | May 2011 | B2 |
7953679 | Chidlovskii et al. | May 2011 | B2 |
7957975 | Burns et al. | Jun 2011 | B2 |
7958136 | Curtis et al. | Jun 2011 | B1 |
7962179 | Huang | Jun 2011 | B2 |
7974835 | Balchandran et al. | Jul 2011 | B2 |
7974844 | Sumita | Jul 2011 | B2 |
7974972 | Cao | Jul 2011 | B2 |
7975216 | Woolf et al. | Jul 2011 | B2 |
7983478 | Liu et al. | Jul 2011 | B2 |
7983915 | Knight et al. | Jul 2011 | B2 |
7983917 | Kennewick et al. | Jul 2011 | B2 |
7983919 | Conkie | Jul 2011 | B2 |
7983997 | Allen et al. | Jul 2011 | B2 |
7984062 | Dunning et al. | Jul 2011 | B2 |
7986431 | Emori et al. | Jul 2011 | B2 |
7987151 | Schott et al. | Jul 2011 | B2 |
7987244 | Lewis et al. | Jul 2011 | B1 |
7991614 | Washio et al. | Aug 2011 | B2 |
7992085 | Wang-Aryattanwanich et al. | Aug 2011 | B2 |
7996228 | Miller et al. | Aug 2011 | B2 |
7996589 | Schultz et al. | Aug 2011 | B2 |
7996769 | Fux et al. | Aug 2011 | B2 |
7996792 | Anzures et al. | Aug 2011 | B2 |
7999669 | Singh et al. | Aug 2011 | B2 |
8000453 | Cooper et al. | Aug 2011 | B2 |
8005664 | Hanumanthappa | Aug 2011 | B2 |
8005679 | Jordan et al. | Aug 2011 | B2 |
8006180 | Tunning et al. | Aug 2011 | B2 |
8010614 | Musat et al. | Aug 2011 | B1 |
8014308 | Gates et al. | Sep 2011 | B2 |
8015006 | Kennewick et al. | Sep 2011 | B2 |
8015011 | Nagano et al. | Sep 2011 | B2 |
8015144 | Zheng et al. | Sep 2011 | B2 |
8018431 | Zehr et al. | Sep 2011 | B1 |
8019271 | Izdepski | Sep 2011 | B1 |
8019604 | Ma | Sep 2011 | B2 |
8020104 | Robarts et al. | Sep 2011 | B2 |
8024195 | Mozer et al. | Sep 2011 | B2 |
8024415 | Horvitz et al. | Sep 2011 | B2 |
8027836 | Baker et al. | Sep 2011 | B2 |
8031943 | Chen et al. | Oct 2011 | B2 |
8032383 | Bhardwaj et al. | Oct 2011 | B1 |
8036901 | Mozer | Oct 2011 | B2 |
8037034 | Plachta et al. | Oct 2011 | B2 |
8041557 | Liu | Oct 2011 | B2 |
8041570 | Mirkovic et al. | Oct 2011 | B2 |
8041611 | Kleinrock et al. | Oct 2011 | B2 |
8042053 | Darwish et al. | Oct 2011 | B2 |
8046231 | Hirota et al. | Oct 2011 | B2 |
8046363 | Cha et al. | Oct 2011 | B2 |
8046374 | Bromwich et al. | Oct 2011 | B1 |
8050500 | Batty et al. | Nov 2011 | B1 |
8054180 | Scofield et al. | Nov 2011 | B1 |
8055502 | Clark et al. | Nov 2011 | B2 |
8055708 | Chitsaz et al. | Nov 2011 | B2 |
8056070 | Goller et al. | Nov 2011 | B2 |
8060824 | Brownrigg, Jr. et al. | Nov 2011 | B2 |
8064753 | Freeman | Nov 2011 | B2 |
8065143 | Yanagihara | Nov 2011 | B2 |
8065155 | Gazdzinski | Nov 2011 | B1 |
8065156 | Gazdzinski | Nov 2011 | B2 |
8068604 | Leeds et al. | Nov 2011 | B2 |
8069046 | Kennewick et al. | Nov 2011 | B2 |
8069422 | Sheshagiri et al. | Nov 2011 | B2 |
8073681 | Baldwin et al. | Dec 2011 | B2 |
8073695 | Hendricks et al. | Dec 2011 | B1 |
8077153 | Benko et al. | Dec 2011 | B2 |
8078473 | Gazdzinski | Dec 2011 | B1 |
8082153 | Coffman et al. | Dec 2011 | B2 |
8082498 | Salamon et al. | Dec 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 |
8107401 | John et al. | Jan 2012 | B2 |
8112275 | Kennewick et al. | Feb 2012 | B2 |
8112280 | Lu | 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 |
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 |
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 |
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 |
8195467 | Mozer et al. | Jun 2012 | B2 |
8195468 | Kennewick 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 |
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 |
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 |
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 |
8260247 | Lazaridis et al. | Sep 2012 | B2 |
8260617 | Dhanakshirur et al. | Sep 2012 | B2 |
8270933 | Riemer et al. | Sep 2012 | B2 |
8271287 | Kermani | Sep 2012 | B1 |
8275621 | Alewine 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 |
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 et al. | Nov 2012 | B2 |
8326627 | Kennewick et al. | Dec 2012 | B2 |
8332205 | Krishnan et al. | Dec 2012 | B2 |
8332218 | Cross 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 | Feb 2013 | B1 |
8391844 | Lamiraux et al. | Mar 2013 | B2 |
8396714 | Rogers et al. | Mar 2013 | B2 |
8401163 | Kirchhoff et al. | Mar 2013 | B1 |
8406745 | Upadhyay et al. | Mar 2013 | B1 |
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 |
8442821 | Vanhoucke | May 2013 | B1 |
8447612 | Gazdzinski | May 2013 | B2 |
8452597 | Bringert et al. | May 2013 | B2 |
8457959 | Kaiser | Jun 2013 | B2 |
8458115 | Cai et al. | Jun 2013 | B2 |
8458278 | Christie et al. | Jun 2013 | B2 |
8464150 | Davidson et al. | Jun 2013 | B2 |
8473289 | Jitkoff et al. | Jun 2013 | B2 |
8479122 | Hotelling et al. | Jul 2013 | B2 |
8484027 | Murphy | Jul 2013 | B1 |
8489599 | Bellotti | 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 | Aug 2013 | B1 |
8521531 | Kim | Aug 2013 | B1 |
8527276 | Senior et al. | Sep 2013 | B1 |
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 |
8571851 | Tickner et al. | Oct 2013 | B1 |
8583416 | Huang et al. | Nov 2013 | B2 |
8583511 | Hendrickson | Nov 2013 | B2 |
8589156 | Burke et al. | Nov 2013 | B2 |
8589869 | Wolfram | Nov 2013 | B2 |
8589911 | Sharkey et al. | Nov 2013 | B1 |
8595004 | Koshinaka | Nov 2013 | B2 |
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 |
8620659 | Di Cristo et al. | Dec 2013 | B2 |
8620662 | Bellegarda | Dec 2013 | B2 |
8626681 | Jurca et al. | Jan 2014 | B1 |
8638363 | King et al. | Jan 2014 | B2 |
8639516 | Lindahl et al. | Jan 2014 | B2 |
8645137 | Bellegarda et al. | Feb 2014 | B2 |
8645138 | Weinstein et al. | Feb 2014 | B1 |
8654936 | Tofighbakhsh 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 |
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 |
8676904 | Lindahl et al. | Mar 2014 | B2 |
8677377 | Cheyer et al. | Mar 2014 | B2 |
8681950 | Vlack et al. | Mar 2014 | B2 |
8682667 | Haughay et al. | Mar 2014 | B2 |
8687777 | Lavian et al. | Apr 2014 | B1 |
8688446 | Yanagihara et al. | Apr 2014 | B2 |
8688453 | Joshi et al. | Apr 2014 | B1 |
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 |
8713119 | Lindahl et al. | Apr 2014 | B2 |
8713418 | King et al. | Apr 2014 | B2 |
8719006 | Bellegarda et al. | May 2014 | B2 |
8719014 | Wagner et al. | 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 | Rodriguez et al. | May 2014 | B2 |
8744852 | Seymour et al. | Jun 2014 | B1 |
8760537 | Johnson et al. | Jun 2014 | B2 |
8762145 | Ouchi et al. | Jun 2014 | B2 |
8762156 | Chen et al. | Jun 2014 | B2 |
8762469 | Lindahl et al. | Jun 2014 | B2 |
8768693 | Lempel et al. | Jul 2014 | B2 |
8768702 | Boettcher et al. | Jul 2014 | B2 |
8775154 | Clinchant et al. | Jul 2014 | B2 |
8775931 | Fux et al. | Jul 2014 | B2 |
8781456 | Prociw | Jul 2014 | B2 |
8781841 | Wang | Jul 2014 | B1 |
8798255 | Lubowich et al. | Aug 2014 | B2 |
8798995 | Edara et al. | Aug 2014 | B1 |
8799000 | Guzzoni et al. | Aug 2014 | B2 |
8805690 | LeBeau et al. | Aug 2014 | B1 |
8812302 | Xiao et al. | Aug 2014 | B2 |
8831947 | Wasserblat et al. | Sep 2014 | B2 |
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 |
8868409 | Mengibar et al. | Oct 2014 | B1 |
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 |
8898568 | Bull et al. | Nov 2014 | B2 |
8903716 | Chen et al. | Dec 2014 | B2 |
8909693 | Frissora et al. | Dec 2014 | B2 |
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 |
8972240 | Brockett et al. | Mar 2015 | B2 |
8972432 | Shaw et al. | Mar 2015 | B2 |
8972878 | Mohler et al. | Mar 2015 | B2 |
8983383 | Haskin | Mar 2015 | B1 |
8989713 | Doulton | Mar 2015 | B2 |
8990235 | King et al. | Mar 2015 | B2 |
8994660 | Neels et al. | Mar 2015 | B2 |
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 |
9009046 | Stewart | Apr 2015 | B1 |
9020804 | Barbaiani et al. | Apr 2015 | B2 |
9026425 | Nikoulina et al. | May 2015 | B2 |
9031834 | Coorman et al. | May 2015 | B2 |
9037967 | Al-Jefri et al. | May 2015 | B1 |
9043208 | Koch et al. | May 2015 | B2 |
9043211 | Haiut et al. | May 2015 | B2 |
9049255 | MacFarlane et al. | Jun 2015 | B2 |
9049295 | Cooper et al. | Jun 2015 | B1 |
9053706 | Jitkoff et al. | Jun 2015 | B2 |
9058811 | Wang et al. | Jun 2015 | B2 |
9063979 | Chiu et al. | Jun 2015 | B2 |
9064495 | Torok et al. | Jun 2015 | B1 |
9070366 | Mathias et al. | Jun 2015 | B1 |
9071701 | Donaldson et al. | Jun 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 |
9098467 | Blanksteen et al. | Aug 2015 | B1 |
9101279 | Ritchey et al. | Aug 2015 | B2 |
9112984 | Sejnoha et al. | Aug 2015 | B2 |
9117447 | Gruber et al. | Aug 2015 | B2 |
9123338 | Sanders 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 |
9183845 | Gopalakrishnan et al. | Nov 2015 | B1 |
9190062 | Haughay | Nov 2015 | B2 |
9208153 | Zaveri et al. | Dec 2015 | B1 |
9218809 | Bellegarda | Dec 2015 | B2 |
9218819 | Stekkelpak et al. | Dec 2015 | B1 |
9223537 | Brown et al. | Dec 2015 | B2 |
9241073 | Van Rensburg et al. | Jan 2016 | B1 |
9255812 | Maeoka et al. | Feb 2016 | B2 |
9258604 | Bilobrov et al. | Feb 2016 | B1 |
9262612 | Cheyer | Feb 2016 | B2 |
9280535 | Varma et al. | Mar 2016 | B2 |
9286910 | Li et al. | Mar 2016 | B1 |
9292487 | Weber | Mar 2016 | B1 |
9292489 | Sak et al. | Mar 2016 | B1 |
9299344 | Braho et al. | Mar 2016 | B2 |
9300718 | Khanna | Mar 2016 | B2 |
9305543 | Fleizach et al. | Apr 2016 | B2 |
9305548 | Kennewick et al. | Apr 2016 | B2 |
9311912 | Swietlinski et al. | Apr 2016 | B1 |
9313317 | LeBeau et al. | Apr 2016 | B1 |
9318108 | Gruber et al. | Apr 2016 | B2 |
9325809 | Barros et al. | Apr 2016 | B1 |
9330659 | Ju et al. | May 2016 | B2 |
9330720 | Lee | May 2016 | B2 |
9338493 | Van Os et al. | May 2016 | B2 |
9349368 | LeBeau et al. | May 2016 | B1 |
9361084 | Costa | Jun 2016 | B1 |
9367541 | Servan et al. | Jun 2016 | B1 |
9377871 | Waddell 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 |
9390726 | Smus et al. | Jul 2016 | B1 |
9396722 | Chung et al. | Jul 2016 | B2 |
9401147 | Jitkoff et al. | Jul 2016 | B2 |
9406224 | Sanders et al. | Aug 2016 | B1 |
9412392 | Lindahl | Aug 2016 | B2 |
9418650 | Bharadwaj et al. | Aug 2016 | B2 |
9423266 | Clark et al. | Aug 2016 | B2 |
9424840 | Hart et al. | Aug 2016 | B1 |
9436918 | Pantel et al. | Sep 2016 | B2 |
9437186 | Liu et al. | Sep 2016 | B1 |
9437189 | Epstein et al. | Sep 2016 | B2 |
9454957 | Mathias et al. | Sep 2016 | B1 |
9465833 | Aravamudan et al. | Oct 2016 | B2 |
9471566 | Zhang et al. | Oct 2016 | B1 |
9484021 | Mairesse 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 |
9519453 | Perkuhn et al. | Dec 2016 | B2 |
9524355 | Forbes et al. | Dec 2016 | B2 |
9535906 | Lee et al. | Jan 2017 | B2 |
9536527 | Carlson | Jan 2017 | B1 |
9547647 | Badaskar | Jan 2017 | B2 |
9548050 | Gruber et al. | Jan 2017 | B2 |
9569549 | Jenkins et al. | Feb 2017 | B1 |
9575964 | Yadgar et al. | Feb 2017 | B2 |
9578173 | Sanghavi et al. | Feb 2017 | B2 |
9607612 | Deleeuw | Mar 2017 | B2 |
9620113 | Kennewick et al. | Apr 2017 | B2 |
9620126 | Chiba | Apr 2017 | B2 |
9626955 | Fleizach et al. | Apr 2017 | B2 |
9633004 | Giuli et al. | Apr 2017 | B2 |
9633660 | Haughay | Apr 2017 | B2 |
9652453 | Mathur et al. | May 2017 | B2 |
9658746 | Cohn et al. | May 2017 | B2 |
9659298 | Lynch et al. | May 2017 | B2 |
9665567 | Liu et al. | May 2017 | B2 |
9668121 | Naik et al. | May 2017 | B2 |
9672725 | Dotan-Cohen et al. | Jun 2017 | B2 |
9691378 | Meyers et al. | Jun 2017 | B1 |
9697827 | Lilly et al. | Jul 2017 | B1 |
9698999 | Mutagi | Jul 2017 | B2 |
9720907 | Bangalore et al. | Aug 2017 | B2 |
9721566 | Newendorp et al. | 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 |
9755605 | Li et al. | Sep 2017 | B1 |
9813882 | Masterman | Nov 2017 | B1 |
9818400 | Paulik et al. | Nov 2017 | B2 |
9842584 | Hart et al. | Dec 2017 | B1 |
9858927 | Williams et al. | Jan 2018 | B2 |
9934785 | Hulaud | Apr 2018 | B1 |
9948728 | Linn et al. | Apr 2018 | B2 |
9966068 | Cash et al. | May 2018 | B2 |
9967381 | Kashimba et al. | May 2018 | B1 |
9990176 | Gray | Jun 2018 | B1 |
10037758 | Jing et al. | Jul 2018 | B2 |
10049663 | Orr et al. | Aug 2018 | B2 |
10049668 | Huang et al. | Aug 2018 | B2 |
10055681 | Brown et al. | Aug 2018 | B2 |
10074360 | Kim | Sep 2018 | B2 |
10096319 | Jin et al. | Oct 2018 | B1 |
10102359 | Cheyer | Oct 2018 | B2 |
10127901 | Zhao et al. | Nov 2018 | B2 |
10169329 | Futrell et al. | Jan 2019 | B2 |
10170123 | Orr et al. | Jan 2019 | B2 |
10191718 | Rhee et al. | Jan 2019 | B2 |
10192557 | Lee et al. | Jan 2019 | B2 |
10200824 | Gross et al. | Feb 2019 | 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 et al. | 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 | 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 |
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 |
20040230637 | Lecoueche et al. | Nov 2004 | A1 |
20040236778 | Junqua et al. | Nov 2004 | A1 |
20040243419 | Wang | Dec 2004 | A1 |
20050021424 | Lewis et al. | Jan 2005 | A1 |
20050033582 | Gadd et al. | Feb 2005 | A1 |
20050043974 | Vassilev et al. | Feb 2005 | A1 |
20050055403 | Brittan | Mar 2005 | A1 |
20050074113 | Mathew 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 |
20050288936 | Busayapongchai et al. | Dec 2005 | A1 |
20060009973 | Nguyen et al. | Jan 2006 | A1 |
20060069664 | Ling et al. | Mar 2006 | A1 |
20060100876 | Nishizaki | May 2006 | A1 |
20060106595 | Brockett et al. | May 2006 | A1 |
20060235690 | Tomasic et al. | Oct 2006 | A1 |
20060293876 | Kamatani et al. | Dec 2006 | A1 |
20070038609 | Wu | Feb 2007 | A1 |
20070050191 | Weider et al. | Mar 2007 | A1 |
20070055525 | Kennewick et al. | 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 |
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 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 et al. | Sep 2008 | A1 |
20080235017 | Satomura | Sep 2008 | A1 |
20080247519 | Abella et al. | Oct 2008 | A1 |
20080294517 | Hill | Nov 2008 | A1 |
20080319763 | Di fabbrizio et al. | Dec 2008 | A1 |
20090003115 | Lindahl et al. | Jan 2009 | A1 |
20090005012 | Van Heugten | Jan 2009 | A1 |
20090005891 | Batson et al. | Jan 2009 | A1 |
20090006096 | Li et al. | Jan 2009 | A1 |
20090006097 | Etezadi et al. | Jan 2009 | A1 |
20090006099 | Sharpe et al. | Jan 2009 | A1 |
20090006100 | Badger et al. | Jan 2009 | A1 |
20090006343 | Platt et al. | Jan 2009 | A1 |
20090006345 | Platt et al. | Jan 2009 | A1 |
20090006488 | Lindahl et al. | Jan 2009 | A1 |
20090006671 | Batson et al. | Jan 2009 | A1 |
20090007001 | Morin et al. | Jan 2009 | A1 |
20090007188 | Omernick | Jan 2009 | A1 |
20090011709 | Akasaka et al. | Jan 2009 | A1 |
20090012748 | Beish et al. | Jan 2009 | A1 |
20090012775 | El Hady et al. | Jan 2009 | A1 |
20090018828 | Nakadai et al. | Jan 2009 | A1 |
20090018829 | Kuperstein | Jan 2009 | A1 |
20090018834 | Cooper et al. | Jan 2009 | A1 |
20090018835 | Cooper et al. | Jan 2009 | A1 |
20090018839 | Cooper et al. | Jan 2009 | A1 |
20090018840 | Lutz et al. | Jan 2009 | A1 |
20090022329 | Mahowald | Jan 2009 | A1 |
20090024595 | Chen | Jan 2009 | A1 |
20090027334 | Foulk et al. | Jan 2009 | A1 |
20090028435 | Wu et al. | Jan 2009 | A1 |
20090030685 | Cerra et al. | Jan 2009 | A1 |
20090030800 | Grois | Jan 2009 | A1 |
20090030978 | Johnson et al. | Jan 2009 | A1 |
20090043580 | Mozer et al. | Feb 2009 | A1 |
20090043583 | Agapi et al. | Feb 2009 | A1 |
20090043763 | Peng | Feb 2009 | A1 |
20090044094 | Rapp et al. | Feb 2009 | A1 |
20090048821 | Yam et al. | Feb 2009 | A1 |
20090048841 | Pollet et al. | Feb 2009 | A1 |
20090048845 | Burckart et al. | Feb 2009 | A1 |
20090049067 | Murray | Feb 2009 | A1 |
20090055168 | Wu et al. | Feb 2009 | A1 |
20090055175 | Terrell et al. | Feb 2009 | A1 |
20090055179 | Cho et al. | Feb 2009 | A1 |
20090055186 | Lance et al. | Feb 2009 | A1 |
20090055380 | Peng et al. | Feb 2009 | A1 |
20090055381 | Wu et al. | Feb 2009 | A1 |
20090055648 | Kim et al. | Feb 2009 | A1 |
20090058823 | Kocienda | Mar 2009 | A1 |
20090058860 | Fong et al. | Mar 2009 | A1 |
20090060351 | Li et al. | Mar 2009 | A1 |
20090060472 | Bull et al. | Mar 2009 | A1 |
20090063974 | Bull et al. | Mar 2009 | A1 |
20090064031 | Bull et al. | Mar 2009 | A1 |
20090070097 | Wu et al. | Mar 2009 | A1 |
20090070102 | Maegawa | Mar 2009 | A1 |
20090070109 | Didcock et al. | Mar 2009 | A1 |
20090070114 | Staszak | Mar 2009 | A1 |
20090074214 | Bradford et al. | Mar 2009 | A1 |
20090076792 | Lawson-Tancred | Mar 2009 | A1 |
20090076796 | Daraselia | Mar 2009 | A1 |
20090076798 | Oh et al. | Mar 2009 | A1 |
20090076819 | Wouters et al. | Mar 2009 | A1 |
20090076821 | Brenner | Mar 2009 | A1 |
20090076825 | Bradford et al. | Mar 2009 | A1 |
20090077047 | Cooper et al. | Mar 2009 | A1 |
20090077165 | Rhodes et al. | Mar 2009 | A1 |
20090077464 | Goldsmith et al. | Mar 2009 | A1 |
20090079622 | Seshadri et al. | Mar 2009 | A1 |
20090083034 | Hernandez et al. | Mar 2009 | A1 |
20090083035 | Huang et al. | Mar 2009 | A1 |
20090083036 | Zhao et al. | Mar 2009 | A1 |
20090083037 | Gleason et al. | Mar 2009 | A1 |
20090083047 | Lindahl et al. | Mar 2009 | A1 |
20090089058 | Bellegarda | Apr 2009 | A1 |
20090091537 | Huang et al. | Apr 2009 | A1 |
20090092239 | Macwan et al. | Apr 2009 | A1 |
20090092260 | Powers | Apr 2009 | A1 |
20090092261 | Bard | Apr 2009 | A1 |
20090092262 | Costa et al. | Apr 2009 | A1 |
20090094029 | Koch et al. | Apr 2009 | A1 |
20090094033 | Mozer et al. | Apr 2009 | A1 |
20090097634 | Nambiar et al. | Apr 2009 | A1 |
20090097637 | Boscher et al. | Apr 2009 | A1 |
20090098903 | Donaldson et al. | Apr 2009 | A1 |
20090100049 | Cao | Apr 2009 | A1 |
20090100454 | Weber | Apr 2009 | A1 |
20090104898 | Harris | Apr 2009 | A1 |
20090106026 | Ferrieux | Apr 2009 | A1 |
20090106376 | Tom et al. | Apr 2009 | A1 |
20090106397 | O'Keefe | Apr 2009 | A1 |
20090112572 | Thorn | Apr 2009 | A1 |
20090112576 | Jackson et al. | Apr 2009 | A1 |
20090112592 | Candelore et al. | Apr 2009 | A1 |
20090112596 | Syrdal et al. | Apr 2009 | A1 |
20090112677 | Rhett | Apr 2009 | A1 |
20090112892 | Cardie et al. | Apr 2009 | A1 |
20090119587 | Allen et al. | May 2009 | A1 |
20090123021 | Jung et al. | May 2009 | A1 |
20090123071 | Iwasaki | May 2009 | A1 |
20090125299 | Wang | May 2009 | A1 |
20090125477 | Lu et al. | May 2009 | A1 |
20090125602 | Bhatia et al. | May 2009 | A1 |
20090125813 | Shen et al. | May 2009 | A1 |
20090125947 | Ibaraki | May 2009 | A1 |
20090128505 | Partridge et al. | May 2009 | A1 |
20090132253 | Bellegarda | May 2009 | A1 |
20090132255 | Lu | May 2009 | A1 |
20090137286 | Luke et al. | May 2009 | A1 |
20090138263 | Shozakai et al. | May 2009 | A1 |
20090138430 | Nambiar et al. | May 2009 | A1 |
20090138736 | Chin | May 2009 | A1 |
20090138828 | Schultz et al. | May 2009 | A1 |
20090144036 | Jorgensen et al. | Jun 2009 | A1 |
20090144049 | Haddad et al. | Jun 2009 | A1 |
20090144428 | Bowater et al. | Jun 2009 | A1 |
20090144609 | Liang et al. | Jun 2009 | A1 |
20090146848 | Ghassabian | Jun 2009 | A1 |
20090150147 | Jacoby et al. | Jun 2009 | A1 |
20090150156 | Kennewick et al. | Jun 2009 | A1 |
20090152349 | Bonev et al. | Jun 2009 | A1 |
20090153288 | Hope et al. | Jun 2009 | A1 |
20090154669 | Wood et al. | Jun 2009 | A1 |
20090157382 | Bar | Jun 2009 | A1 |
20090157384 | Toutanova et al. | Jun 2009 | A1 |
20090157401 | Bennett | Jun 2009 | A1 |
20090158200 | Palahnuk et al. | Jun 2009 | A1 |
20090158323 | Bober et al. | Jun 2009 | A1 |
20090158423 | Orlassino et al. | Jun 2009 | A1 |
20090160761 | Moosavi et al. | Jun 2009 | A1 |
20090160803 | Hashimoto | Jun 2009 | A1 |
20090163243 | Barbera | Jun 2009 | A1 |
20090164301 | O'Sullivan et al. | Jun 2009 | A1 |
20090164441 | Cheyer | Jun 2009 | A1 |
20090164655 | Pettersson et al. | Jun 2009 | A1 |
20090164937 | Alviar et al. | Jun 2009 | A1 |
20090167508 | Fadell et al. | Jul 2009 | A1 |
20090167509 | Fadell et al. | Jul 2009 | A1 |
20090171578 | Kim et al. | Jul 2009 | A1 |
20090171662 | Huang et al. | Jul 2009 | A1 |
20090171664 | Kennewick et al. | Jul 2009 | A1 |
20090172108 | Singh | Jul 2009 | A1 |
20090172542 | Girish et al. | Jul 2009 | A1 |
20090174667 | Kocienda et al. | Jul 2009 | A1 |
20090174677 | Gehani et al. | Jul 2009 | A1 |
20090177300 | Lee | Jul 2009 | A1 |
20090177461 | Ehsani et al. | Jul 2009 | A1 |
20090177966 | Chaudhri | Jul 2009 | A1 |
20090182445 | Girish et al. | Jul 2009 | A1 |
20090182549 | Anisimovich et al. | Jul 2009 | A1 |
20090182702 | Miller | Jul 2009 | A1 |
20090183070 | Robbins | Jul 2009 | A1 |
20090187402 | Scholl | Jul 2009 | A1 |
20090187577 | Reznik et al. | Jul 2009 | A1 |
20090187950 | Nicas et al. | Jul 2009 | A1 |
20090190774 | Wang et al. | Jul 2009 | A1 |
20090191895 | Singh et al. | Jul 2009 | A1 |
20090192782 | Drewes | Jul 2009 | A1 |
20090192787 | Roon | Jul 2009 | A1 |
20090192798 | Basson et al. | Jul 2009 | A1 |
20090198497 | Kwon | Aug 2009 | A1 |
20090204402 | Marwaha et al. | Aug 2009 | A1 |
20090204409 | Mozer et al. | Aug 2009 | A1 |
20090204478 | Kaib et al. | Aug 2009 | A1 |
20090204596 | Brun et al. | Aug 2009 | A1 |
20090204601 | Grasset | Aug 2009 | A1 |
20090204620 | Thione et al. | Aug 2009 | A1 |
20090210230 | Schwarz et al. | Aug 2009 | A1 |
20090210232 | Sanchez et al. | Aug 2009 | A1 |
20090213134 | Stephanick et al. | Aug 2009 | A1 |
20090215466 | Ahl et al. | Aug 2009 | A1 |
20090215503 | Zhang et al. | Aug 2009 | A1 |
20090216396 | Yamagata | Aug 2009 | A1 |
20090216528 | Gemello et al. | Aug 2009 | A1 |
20090216540 | Tessel et al. | Aug 2009 | A1 |
20090216704 | Zheng et al. | Aug 2009 | A1 |
20090219166 | MacFarlane et al. | Sep 2009 | A1 |
20090221274 | Venkatakrishnan et al. | Sep 2009 | A1 |
20090222257 | Sumita et al. | Sep 2009 | A1 |
20090222270 | Likens et al. | Sep 2009 | A2 |
20090222488 | Boerries et al. | Sep 2009 | A1 |
20090224867 | O'Shaughnessy et al. | Sep 2009 | A1 |
20090228126 | Spielberg et al. | Sep 2009 | A1 |
20090228273 | Wang et al. | Sep 2009 | A1 |
20090228277 | Bonforte et al. | Sep 2009 | A1 |
20090228281 | Singleton et al. | Sep 2009 | A1 |
20090228439 | Manolescu et al. | Sep 2009 | A1 |
20090228792 | Van Os et al. | Sep 2009 | A1 |
20090228842 | Westerman et al. | Sep 2009 | A1 |
20090233264 | Rogers et al. | Sep 2009 | A1 |
20090234638 | Ranjan et al. | Sep 2009 | A1 |
20090234651 | Basir et al. | Sep 2009 | A1 |
20090234655 | Kwon | Sep 2009 | A1 |
20090235280 | Tannier et al. | Sep 2009 | A1 |
20090239202 | Stone | Sep 2009 | A1 |
20090239552 | Churchill et al. | Sep 2009 | A1 |
20090240485 | Dalal et al. | Sep 2009 | A1 |
20090241054 | Hendricks | Sep 2009 | A1 |
20090241760 | Georges | Oct 2009 | A1 |
20090247237 | Mittleman et al. | Oct 2009 | A1 |
20090248182 | Logan et al. | Oct 2009 | A1 |
20090248395 | Alewine et al. | Oct 2009 | A1 |
20090248402 | Ito et al. | Oct 2009 | A1 |
20090248420 | Basir et al. | Oct 2009 | A1 |
20090248422 | Li et al. | Oct 2009 | A1 |
20090248456 | Fahmy et al. | Oct 2009 | A1 |
20090249198 | Davis et al. | Oct 2009 | A1 |
20090249247 | Tseng et al. | Oct 2009 | A1 |
20090252350 | Seguin | Oct 2009 | A1 |
20090253457 | Seguin | Oct 2009 | A1 |
20090253463 | Shin et al. | Oct 2009 | A1 |
20090254339 | Seguin | Oct 2009 | A1 |
20090254345 | Fleizach et al. | Oct 2009 | A1 |
20090254819 | Song et al. | Oct 2009 | A1 |
20090254823 | Barrett | Oct 2009 | A1 |
20090259472 | Schroeter | Oct 2009 | A1 |
20090259475 | Yamagami et al. | Oct 2009 | A1 |
20090259969 | Pallakoff | Oct 2009 | A1 |
20090265171 | Davis | Oct 2009 | A1 |
20090265368 | Crider et al. | Oct 2009 | A1 |
20090271109 | Lee et al. | Oct 2009 | A1 |
20090271175 | Bodin et al. | Oct 2009 | A1 |
20090271176 | Bodin et al. | Oct 2009 | A1 |
20090271178 | Bodin et al. | Oct 2009 | A1 |
20090271188 | Agapi et al. | Oct 2009 | A1 |
20090271189 | Agapi et al. | Oct 2009 | A1 |
20090274315 | Carnes et al. | Nov 2009 | A1 |
20090274376 | Selvaraj et al. | Nov 2009 | A1 |
20090278804 | Rubanovich et al. | Nov 2009 | A1 |
20090281789 | Waibel et al. | Nov 2009 | A1 |
20090284471 | Longe et al. | Nov 2009 | A1 |
20090284482 | Chin | Nov 2009 | A1 |
20090286514 | Lichorowic et al. | Nov 2009 | A1 |
20090287583 | Holmes | Nov 2009 | A1 |
20090290718 | Kahn et al. | Nov 2009 | A1 |
20090292987 | Sorenson | Nov 2009 | A1 |
20090296552 | Hicks et al. | Dec 2009 | A1 |
20090298474 | George | Dec 2009 | A1 |
20090298529 | Mahajan | Dec 2009 | A1 |
20090299745 | Kennewick et al. | Dec 2009 | A1 |
20090299751 | Jung | Dec 2009 | A1 |
20090299849 | Cao et al. | Dec 2009 | A1 |
20090300391 | Jessup et al. | Dec 2009 | A1 |
20090300488 | Salamon et al. | Dec 2009 | A1 |
20090304198 | Herre et al. | Dec 2009 | A1 |
20090305203 | Okumura et al. | Dec 2009 | A1 |
20090306967 | Nicolov et al. | Dec 2009 | A1 |
20090306969 | Goud et al. | Dec 2009 | A1 |
20090306979 | Jaiswal et al. | Dec 2009 | A1 |
20090306980 | Shin | Dec 2009 | A1 |
20090306981 | Cromack et al. | Dec 2009 | A1 |
20090306985 | Roberts et al. | Dec 2009 | A1 |
20090306988 | Chen et al. | Dec 2009 | A1 |
20090306989 | Kaji | Dec 2009 | A1 |
20090307162 | Bui et al. | Dec 2009 | A1 |
20090307201 | Dunning et al. | Dec 2009 | A1 |
20090307584 | Davidson et al. | Dec 2009 | A1 |
20090307594 | Kosonen et al. | Dec 2009 | A1 |
20090309352 | Walker et al. | Dec 2009 | A1 |
20090313014 | Shin et al. | Dec 2009 | A1 |
20090313020 | Koivunen | Dec 2009 | A1 |
20090313023 | Jones | Dec 2009 | A1 |
20090313026 | Coffman et al. | Dec 2009 | A1 |
20090313544 | Wood et al. | Dec 2009 | A1 |
20090313564 | Rottler et al. | Dec 2009 | A1 |
20090316943 | Frigola Munoz et al. | Dec 2009 | A1 |
20090318119 | Basir et al. | Dec 2009 | A1 |
20090318198 | Carroll | Dec 2009 | A1 |
20090319257 | Blume et al. | Dec 2009 | A1 |
20090319266 | Brown et al. | Dec 2009 | A1 |
20090319342 | Shilman et al. | Dec 2009 | A1 |
20090326923 | Yan et al. | Dec 2009 | A1 |
20090326936 | Nagashima | Dec 2009 | A1 |
20090326938 | Marila et al. | Dec 2009 | A1 |
20090326949 | Douthitt et al. | Dec 2009 | A1 |
20090327977 | Bachfischer et al. | Dec 2009 | A1 |
20100004918 | Lee et al. | Jan 2010 | A1 |
20100004930 | Strope et al. | Jan 2010 | A1 |
20100004931 | Ma et al. | Jan 2010 | A1 |
20100005081 | Bennett | Jan 2010 | A1 |
20100010803 | Ishikawa et al. | Jan 2010 | A1 |
20100010814 | Patel | Jan 2010 | A1 |
20100010948 | Ito et al. | Jan 2010 | A1 |
20100013760 | Hirai et al. | Jan 2010 | A1 |
20100013796 | Abileah et al. | Jan 2010 | A1 |
20100017212 | Attwater et al. | Jan 2010 | A1 |
20100017382 | Katragadda et al. | Jan 2010 | A1 |
20100019834 | Zerbe et al. | Jan 2010 | A1 |
20100020035 | Ryu et al. | Jan 2010 | A1 |
20100023318 | Lemoine | Jan 2010 | A1 |
20100023320 | Di Cristo et al. | Jan 2010 | A1 |
20100023331 | Duta et al. | Jan 2010 | A1 |
20100026526 | Yokota | Feb 2010 | A1 |
20100030549 | Lee et al. | Feb 2010 | A1 |
20100030928 | Conroy et al. | Feb 2010 | A1 |
20100031143 | Rao et al. | Feb 2010 | A1 |
20100036653 | Kim et al. | Feb 2010 | A1 |
20100036655 | Cecil et al. | Feb 2010 | A1 |
20100036660 | Bennett | Feb 2010 | A1 |
20100036829 | Leyba | Feb 2010 | A1 |
20100036928 | Granito et al. | Feb 2010 | A1 |
20100037183 | Miyashita et al. | Feb 2010 | A1 |
20100037187 | Kondziela | Feb 2010 | A1 |
20100042400 | Block et al. | Feb 2010 | A1 |
20100042576 | Roettger et al. | Feb 2010 | A1 |
20100046842 | Conwell et al. | Feb 2010 | A1 |
20100049498 | Cao et al. | Feb 2010 | A1 |
20100049514 | Kennewick et al. | Feb 2010 | A1 |
20100050064 | Liu et al. | Feb 2010 | A1 |
20100054512 | Solum | Mar 2010 | A1 |
20100057435 | Kent et al. | Mar 2010 | A1 |
20100057443 | Di Cristo et al. | Mar 2010 | A1 |
20100057457 | Ogata et al. | Mar 2010 | A1 |
20100057461 | Neubacher et al. | Mar 2010 | A1 |
20100057643 | Yang | Mar 2010 | A1 |
20100058200 | Jablokov et al. | Mar 2010 | A1 |
20100060646 | Unsal et al. | Mar 2010 | A1 |
20100063804 | Sato et al. | Mar 2010 | A1 |
20100063825 | Williams et al. | Mar 2010 | A1 |
20100063961 | Guiheneuf et al. | Mar 2010 | A1 |
20100064113 | Lindahl et al. | Mar 2010 | A1 |
20100064218 | Bull et al. | Mar 2010 | A1 |
20100064226 | Stefaniak et al. | Mar 2010 | A1 |
20100066546 | Aaron | Mar 2010 | A1 |
20100066684 | Shahraray et al. | Mar 2010 | A1 |
20100067723 | Bergmann et al. | Mar 2010 | A1 |
20100067867 | Lin et al. | Mar 2010 | A1 |
20100070281 | Conkie et al. | Mar 2010 | A1 |
20100070517 | Ghosh et al. | Mar 2010 | A1 |
20100070521 | Clinchant et al. | Mar 2010 | A1 |
20100070899 | Hunt et al. | Mar 2010 | A1 |
20100071003 | Bychkov et al. | Mar 2010 | A1 |
20100076760 | Kraenzel et al. | Mar 2010 | A1 |
20100076993 | Klawitter et al. | Mar 2010 | A1 |
20100077350 | Lim et al. | Mar 2010 | A1 |
20100079501 | Ikeda et al. | Apr 2010 | A1 |
20100079508 | Hodge et al. | Apr 2010 | A1 |
20100080398 | Waldmann | Apr 2010 | A1 |
20100080470 | Deluca et al. | Apr 2010 | A1 |
20100081456 | Singh et al. | Apr 2010 | A1 |
20100081487 | Chen et al. | Apr 2010 | A1 |
20100082286 | Leung | Apr 2010 | A1 |
20100082327 | Rogers et al. | Apr 2010 | A1 |
20100082328 | Rogers et al. | Apr 2010 | A1 |
20100082329 | Silverman et al. | Apr 2010 | A1 |
20100082333 | Al-Shammari | Apr 2010 | A1 |
20100082343 | Levit et al. | Apr 2010 | A1 |
20100082346 | Rogers et al. | Apr 2010 | A1 |
20100082347 | Rogers et al. | Apr 2010 | A1 |
20100082348 | Silverman et al. | Apr 2010 | A1 |
20100082349 | Bellegarda et al. | Apr 2010 | A1 |
20100082376 | Levitt | Apr 2010 | A1 |
20100082567 | Rosenblatt et al. | Apr 2010 | A1 |
20100082970 | Lindahl et al. | Apr 2010 | A1 |
20100086152 | Rank et al. | Apr 2010 | A1 |
20100086153 | Hagen et al. | Apr 2010 | A1 |
20100086156 | Rank et al. | Apr 2010 | A1 |
20100088020 | Sano et al. | Apr 2010 | A1 |
20100088093 | Lee et al. | Apr 2010 | A1 |
20100088100 | Lindahl | Apr 2010 | A1 |
20100094632 | Davis et al. | Apr 2010 | A1 |
20100098231 | Wohlert et al. | Apr 2010 | A1 |
20100100212 | Lindahl et al. | Apr 2010 | A1 |
20100100384 | Ju et al. | Apr 2010 | A1 |
20100100385 | Davis et al. | Apr 2010 | A1 |
20100100515 | Bangalore et al. | Apr 2010 | A1 |
20100100816 | Mccloskey et al. | Apr 2010 | A1 |
20100103776 | Chan | Apr 2010 | A1 |
20100106486 | Hua et al. | Apr 2010 | A1 |
20100106498 | Morrison et al. | Apr 2010 | A1 |
20100106500 | McKee et al. | Apr 2010 | A1 |
20100106503 | Farrell et al. | Apr 2010 | A1 |
20100114856 | Kuboyama | May 2010 | A1 |
20100114887 | Conway et al. | May 2010 | A1 |
20100121637 | Roy et al. | May 2010 | A1 |
20100125456 | Weng et al. | May 2010 | A1 |
20100125458 | Franco et al. | May 2010 | A1 |
20100125460 | Mellott et al. | May 2010 | A1 |
20100125811 | Moore et al. | May 2010 | A1 |
20100128701 | Nagaraja | May 2010 | A1 |
20100131265 | Boda et al. | May 2010 | A1 |
20100131269 | Park et al. | May 2010 | A1 |
20100131273 | Aley-Raz et al. | May 2010 | A1 |
20100131498 | Linthicum et al. | May 2010 | A1 |
20100131899 | Hubert | May 2010 | A1 |
20100138215 | Williams | Jun 2010 | A1 |
20100138224 | Bedingfield, Sr. | Jun 2010 | A1 |
20100138416 | Bellotti | Jun 2010 | A1 |
20100138680 | Brisebois et al. | Jun 2010 | A1 |
20100138759 | Roy | Jun 2010 | A1 |
20100138798 | Wilson et al. | Jun 2010 | A1 |
20100142740 | Roerup | Jun 2010 | A1 |
20100145694 | Ju et al. | Jun 2010 | A1 |
20100145700 | Kennewick et al. | Jun 2010 | A1 |
20100145707 | Ljolje et al. | Jun 2010 | A1 |
20100146442 | Nagasaka et al. | Jun 2010 | A1 |
20100150321 | Harris et al. | Jun 2010 | A1 |
20100153114 | Shih et al. | Jun 2010 | A1 |
20100153115 | Klee et al. | Jun 2010 | A1 |
20100153448 | Harpur et al. | Jun 2010 | A1 |
20100161311 | Massuh | Jun 2010 | A1 |
20100161313 | Karttunen | Jun 2010 | A1 |
20100161337 | Pulz et al. | Jun 2010 | A1 |
20100161554 | Datuashvili et al. | Jun 2010 | A1 |
20100164897 | Morin et al. | Jul 2010 | A1 |
20100169075 | Raffa et al. | Jul 2010 | A1 |
20100169093 | Washio | Jul 2010 | A1 |
20100169097 | Nachman et al. | Jul 2010 | A1 |
20100169098 | Patch | Jul 2010 | A1 |
20100171713 | Kwok et al. | Jul 2010 | A1 |
20100174544 | Heifets | Jul 2010 | A1 |
20100175066 | Paik | Jul 2010 | A1 |
20100179932 | Yoon et al. | Jul 2010 | A1 |
20100179991 | Lorch et al. | Jul 2010 | A1 |
20100180218 | Boston et al. | Jul 2010 | A1 |
20100185448 | Meisel | Jul 2010 | A1 |
20100185949 | Jaeger | Jul 2010 | A1 |
20100191520 | Gruhn et al. | Jul 2010 | A1 |
20100197359 | Harris | Aug 2010 | A1 |
20100198821 | Loritz et al. | Aug 2010 | A1 |
20100199180 | Brichter et al. | Aug 2010 | A1 |
20100199215 | Seymour et al. | Aug 2010 | A1 |
20100204986 | Kennewick et al. | Aug 2010 | A1 |
20100211199 | Naik et al. | Aug 2010 | A1 |
20100211379 | Gorman et al. | Aug 2010 | A1 |
20100211644 | Lavoie et al. | Aug 2010 | A1 |
20100216509 | Riemer et al. | Aug 2010 | A1 |
20100217604 | Baldwin et al. | Aug 2010 | A1 |
20100222033 | Scott et al. | Sep 2010 | A1 |
20100222098 | Garg | Sep 2010 | A1 |
20100223055 | Mclean | Sep 2010 | A1 |
20100223056 | Kadirkamanathan et al. | Sep 2010 | A1 |
20100223131 | Scott et al. | Sep 2010 | A1 |
20100225599 | Danielsson et al. | Sep 2010 | A1 |
20100225809 | Connors et al. | Sep 2010 | A1 |
20100227642 | Kim et al. | Sep 2010 | A1 |
20100228540 | Bennett | Sep 2010 | A1 |
20100228549 | Herman et al. | Sep 2010 | A1 |
20100228691 | Yang et al. | Sep 2010 | A1 |
20100229082 | Karmarkar et al. | Sep 2010 | A1 |
20100229100 | Miller et al. | Sep 2010 | A1 |
20100231474 | Yamagajo et al. | Sep 2010 | A1 |
20100235167 | Bourdon | Sep 2010 | A1 |
20100235341 | Bennett | Sep 2010 | A1 |
20100235729 | Kocienda et al. | Sep 2010 | A1 |
20100235732 | Bergman | Sep 2010 | A1 |
20100235770 | Ording et al. | Sep 2010 | A1 |
20100235780 | Westerman et al. | Sep 2010 | A1 |
20100241418 | Maeda et al. | Sep 2010 | A1 |
20100250542 | Fujimaki | Sep 2010 | A1 |
20100250599 | Schmidt et al. | Sep 2010 | A1 |
20100255858 | Juhasz | Oct 2010 | A1 |
20100257160 | Cao | Oct 2010 | A1 |
20100257478 | Longe et al. | Oct 2010 | A1 |
20100262599 | Nitz | Oct 2010 | A1 |
20100263015 | Pandey et al. | Oct 2010 | A1 |
20100268537 | Al-Telmissani | Oct 2010 | A1 |
20100268539 | Xu et al. | Oct 2010 | A1 |
20100269040 | Lee | Oct 2010 | A1 |
20100274753 | Liberty et al. | Oct 2010 | A1 |
20100277579 | Cho et al. | Nov 2010 | A1 |
20100278320 | Arsenault et al. | Nov 2010 | A1 |
20100278391 | Hsu et al. | Nov 2010 | A1 |
20100278453 | King | Nov 2010 | A1 |
20100280983 | Cho et al. | Nov 2010 | A1 |
20100281034 | Petrou et al. | Nov 2010 | A1 |
20100286984 | Wandinger et al. | Nov 2010 | A1 |
20100286985 | Kennewick et al. | Nov 2010 | A1 |
20100287514 | Cragun et al. | Nov 2010 | A1 |
20100290632 | Lin | Nov 2010 | A1 |
20100293460 | Budelli | Nov 2010 | A1 |
20100295645 | Falldin et al. | Nov 2010 | A1 |
20100299133 | Kopparapu et al. | Nov 2010 | A1 |
20100299138 | Kim | Nov 2010 | A1 |
20100299142 | Freeman et al. | Nov 2010 | A1 |
20100302056 | Dutton et al. | Dec 2010 | A1 |
20100304342 | Zilber | Dec 2010 | A1 |
20100304705 | Hursey et al. | Dec 2010 | A1 |
20100305807 | Basir et al. | Dec 2010 | A1 |
20100305947 | Schwarz et al. | Dec 2010 | A1 |
20100312547 | Van Os et al. | Dec 2010 | A1 |
20100312566 | Odinak et al. | Dec 2010 | A1 |
20100318366 | Sullivan et al. | Dec 2010 | A1 |
20100318576 | Kim | Dec 2010 | A1 |
20100322438 | Siotis | Dec 2010 | A1 |
20100324709 | Starmen | Dec 2010 | A1 |
20100324895 | Kurzweil et al. | Dec 2010 | A1 |
20100324896 | Attwater et al. | Dec 2010 | A1 |
20100324905 | Kurzweil et al. | Dec 2010 | A1 |
20100325131 | Dumais et al. | Dec 2010 | A1 |
20100325158 | Oral et al. | Dec 2010 | A1 |
20100325573 | Estrada et al. | Dec 2010 | A1 |
20100325588 | Reddy et al. | Dec 2010 | A1 |
20100330908 | Maddern et al. | Dec 2010 | A1 |
20100332003 | Yaguez | Dec 2010 | A1 |
20100332220 | Hursey et al. | Dec 2010 | A1 |
20100332224 | Mäkelä et al. | Dec 2010 | A1 |
20100332235 | David | Dec 2010 | A1 |
20100332236 | Tan | Dec 2010 | A1 |
20100332280 | Bradley et al. | Dec 2010 | A1 |
20100332348 | Cao | Dec 2010 | A1 |
20100332428 | Mehenry et al. | Dec 2010 | A1 |
20100332976 | Fux et al. | Dec 2010 | A1 |
20100333030 | Johns | Dec 2010 | A1 |
20100333163 | Daly | Dec 2010 | A1 |
20110002487 | Panther et al. | Jan 2011 | A1 |
20110004475 | Bellegarda | Jan 2011 | A1 |
20110006876 | Moberg et al. | Jan 2011 | A1 |
20110009107 | Guba et al. | Jan 2011 | A1 |
20110010178 | Lee et al. | Jan 2011 | A1 |
20110010644 | Merrill et al. | Jan 2011 | A1 |
20110015928 | Odell et al. | Jan 2011 | A1 |
20110016150 | Engstrom et al. | Jan 2011 | A1 |
20110016421 | Krupka et al. | Jan 2011 | A1 |
20110018695 | Bells et al. | Jan 2011 | A1 |
20110021211 | Ohki | Jan 2011 | A1 |
20110021213 | Carr | Jan 2011 | A1 |
20110022292 | Shen et al. | Jan 2011 | A1 |
20110022388 | Wu et al. | Jan 2011 | A1 |
20110022393 | Waller et al. | Jan 2011 | A1 |
20110022394 | Wide et al. | Jan 2011 | A1 |
20110022472 | Zon et al. | Jan 2011 | A1 |
20110022952 | Wu et al. | Jan 2011 | A1 |
20110029616 | Wang et al. | Feb 2011 | A1 |
20110030067 | Wilson | Feb 2011 | A1 |
20110033064 | Johnson et al. | Feb 2011 | A1 |
20110034183 | Haag et al. | Feb 2011 | A1 |
20110035144 | Okamoto et al. | Feb 2011 | A1 |
20110035434 | Lockwood | Feb 2011 | A1 |
20110038489 | Visser et al. | Feb 2011 | A1 |
20110039584 | Merrett | Feb 2011 | A1 |
20110040707 | Theisen et al. | Feb 2011 | A1 |
20110045841 | Kuhlke et al. | Feb 2011 | A1 |
20110047072 | Ciurea | Feb 2011 | A1 |
20110047149 | Vaananen | Feb 2011 | A1 |
20110047161 | Myaeng et al. | Feb 2011 | A1 |
20110047266 | Yu et al. | Feb 2011 | A1 |
20110047605 | Sontag et al. | Feb 2011 | A1 |
20110050591 | Kim et al. | Mar 2011 | A1 |
20110050592 | Kim et al. | Mar 2011 | A1 |
20110054647 | Chipchase | Mar 2011 | A1 |
20110054894 | Phillips et al. | Mar 2011 | A1 |
20110054901 | Qin et al. | Mar 2011 | A1 |
20110055256 | Phillips et al. | Mar 2011 | A1 |
20110060584 | Ferrucci et al. | Mar 2011 | A1 |
20110060587 | Phillips et al. | Mar 2011 | A1 |
20110060589 | Weinberg et al. | Mar 2011 | A1 |
20110060807 | Martin et al. | Mar 2011 | A1 |
20110060812 | Middleton | Mar 2011 | A1 |
20110064387 | Mendeloff et al. | Mar 2011 | A1 |
20110065456 | Brennan et al. | Mar 2011 | A1 |
20110066366 | Ellanti et al. | Mar 2011 | A1 |
20110066436 | Bezar | Mar 2011 | A1 |
20110066468 | Huang et al. | Mar 2011 | A1 |
20110066634 | Phillips et al. | Mar 2011 | A1 |
20110072033 | White et al. | Mar 2011 | A1 |
20110072492 | Mohler et al. | Mar 2011 | A1 |
20110076994 | Kim et al. | Mar 2011 | A1 |
20110077943 | Miki et al. | Mar 2011 | A1 |
20110080260 | Wang et al. | Apr 2011 | A1 |
20110081889 | Gao et al. | Apr 2011 | A1 |
20110082688 | Kim et al. | Apr 2011 | A1 |
20110083079 | Farrell et al. | Apr 2011 | A1 |
20110087491 | Wittenstein et al. | Apr 2011 | A1 |
20110087685 | Lin et al. | Apr 2011 | A1 |
20110090078 | Kim et al. | Apr 2011 | A1 |
20110092187 | Miller | Apr 2011 | A1 |
20110093261 | Angott | Apr 2011 | A1 |
20110093265 | Stent et al. | Apr 2011 | A1 |
20110093271 | Bernard et al. | Apr 2011 | A1 |
20110093272 | Isobe et al. | Apr 2011 | A1 |
20110099000 | Rai et al. | Apr 2011 | A1 |
20110099157 | Lebeau et al. | Apr 2011 | A1 |
20110103682 | Chidlovskii et al. | May 2011 | A1 |
20110105097 | Tadayon et al. | May 2011 | A1 |
20110106736 | Aharonson et al. | May 2011 | A1 |
20110106892 | Nelson et al. | May 2011 | A1 |
20110110502 | Daye et al. | May 2011 | A1 |
20110111724 | Baptiste | May 2011 | A1 |
20110112825 | Bellegarda | May 2011 | A1 |
20110112827 | Kennewick et al. | May 2011 | A1 |
20110112837 | Kurki-Suonio et al. | May 2011 | A1 |
20110112838 | Adibi | May 2011 | A1 |
20110112921 | Kennewick et al. | May 2011 | A1 |
20110116610 | Shaw et al. | May 2011 | A1 |
20110119049 | Ylonen | May 2011 | A1 |
20110119051 | Li et al. | May 2011 | A1 |
20110119623 | Kim | May 2011 | A1 |
20110119715 | Chang et al. | May 2011 | A1 |
20110123004 | Chang et al. | May 2011 | A1 |
20110125498 | Pickering et al. | May 2011 | A1 |
20110125540 | Jang et al. | May 2011 | A1 |
20110125701 | Nair et al. | May 2011 | A1 |
20110130958 | Stahl et al. | Jun 2011 | A1 |
20110131036 | DiCristo et al. | Jun 2011 | A1 |
20110131038 | Oyaizu et al. | Jun 2011 | A1 |
20110131045 | Cristo et al. | Jun 2011 | A1 |
20110137636 | Srihari et al. | Jun 2011 | A1 |
20110137664 | Kho et al. | Jun 2011 | A1 |
20110141141 | Kankainen | Jun 2011 | A1 |
20110143726 | de Silva | Jun 2011 | A1 |
20110143811 | Rodriguez | Jun 2011 | A1 |
20110144857 | Wingrove et al. | Jun 2011 | A1 |
20110144901 | Wang | Jun 2011 | A1 |
20110144973 | Bocchieri et al. | Jun 2011 | A1 |
20110144999 | Jang et al. | Jun 2011 | A1 |
20110145718 | Ketola et al. | Jun 2011 | A1 |
20110151830 | Blanda et al. | Jun 2011 | A1 |
20110153209 | Geelen | Jun 2011 | A1 |
20110153322 | Kwak et al. | Jun 2011 | A1 |
20110153324 | Ballinger et al. | Jun 2011 | A1 |
20110153329 | Moorer | Jun 2011 | A1 |
20110153330 | Yazdani et al. | Jun 2011 | A1 |
20110153373 | Dantzig et al. | Jun 2011 | A1 |
20110154193 | Creutz et al. | Jun 2011 | A1 |
20110157029 | Tseng | Jun 2011 | A1 |
20110161072 | Terao et al. | Jun 2011 | A1 |
20110161076 | Davis et al. | Jun 2011 | A1 |
20110161079 | Gruhn et al. | Jun 2011 | A1 |
20110161309 | Lung et al. | Jun 2011 | A1 |
20110161852 | Vainio et al. | Jun 2011 | A1 |
20110166851 | LeBeau et al. | Jul 2011 | A1 |
20110166855 | Vermeulen et al. | Jul 2011 | A1 |
20110167350 | Hoellwarth | Jul 2011 | A1 |
20110175810 | Markovic et al. | Jul 2011 | A1 |
20110178804 | Inoue et al. | Jul 2011 | A1 |
20110179002 | Dumitru et al. | Jul 2011 | A1 |
20110179372 | Moore et al. | Jul 2011 | A1 |
20110183627 | Ueda et al. | Jul 2011 | A1 |
20110183650 | Mckee et al. | Jul 2011 | A1 |
20110184721 | Subramanian et al. | Jul 2011 | A1 |
20110184730 | LeBeau et al. | Jul 2011 | A1 |
20110184736 | Slotznick | Jul 2011 | A1 |
20110184737 | Nakano et al. | Jul 2011 | A1 |
20110184768 | Norton et al. | Jul 2011 | A1 |
20110185288 | Gupta et al. | Jul 2011 | A1 |
20110191108 | Friedlander | Aug 2011 | A1 |
20110191271 | Baker et al. | Aug 2011 | A1 |
20110191344 | Jin et al. | Aug 2011 | A1 |
20110195758 | Damale et al. | Aug 2011 | A1 |
20110196670 | Dang et al. | Aug 2011 | A1 |
20110197128 | Assadollahi et al. | Aug 2011 | A1 |
20110199312 | Okuta | Aug 2011 | A1 |
20110201385 | Higginbotham et al. | Aug 2011 | A1 |
20110201387 | Paek et al. | Aug 2011 | A1 |
20110202526 | Lee et al. | Aug 2011 | A1 |
20110205149 | Tom et al. | Aug 2011 | A1 |
20110208511 | Sikstrom et al. | Aug 2011 | A1 |
20110208524 | Haughay | Aug 2011 | A1 |
20110209088 | Hinckley et al. | Aug 2011 | A1 |
20110212717 | Rhoads et al. | Sep 2011 | A1 |
20110216093 | Griffin | Sep 2011 | A1 |
20110218806 | Alewine et al. | Sep 2011 | A1 |
20110218855 | Cao et al. | Sep 2011 | A1 |
20110219018 | Bailey et al. | Sep 2011 | A1 |
20110223893 | Lau et al. | Sep 2011 | A1 |
20110224972 | Millett et al. | Sep 2011 | A1 |
20110228913 | Cochinwala et al. | Sep 2011 | A1 |
20110231182 | Weider et al. | Sep 2011 | A1 |
20110231184 | Kerr | Sep 2011 | A1 |
20110231188 | Kennewick et al. | Sep 2011 | A1 |
20110231218 | Tovar | Sep 2011 | A1 |
20110231432 | Sata et al. | Sep 2011 | A1 |
20110231474 | Locker et al. | Sep 2011 | A1 |
20110238191 | Kristjansson et al. | Sep 2011 | A1 |
20110238407 | Kent | Sep 2011 | A1 |
20110238408 | Larcheveque et al. | Sep 2011 | A1 |
20110238676 | Liu et al. | Sep 2011 | A1 |
20110239111 | Grover | Sep 2011 | A1 |
20110242007 | Gray et al. | Oct 2011 | A1 |
20110244888 | Ohki | Oct 2011 | A1 |
20110246471 | Rakib et al. | Oct 2011 | A1 |
20110249144 | Chang | Oct 2011 | A1 |
20110250570 | Mack et al. | Oct 2011 | A1 |
20110257966 | Rychlik | Oct 2011 | A1 |
20110258188 | Abdalmageed et al. | Oct 2011 | A1 |
20110260829 | Lee | Oct 2011 | A1 |
20110260861 | Singh et al. | Oct 2011 | A1 |
20110264643 | Cao | Oct 2011 | A1 |
20110264999 | Bells et al. | Oct 2011 | A1 |
20110274303 | Filson et al. | Nov 2011 | A1 |
20110276595 | Kirkland et al. | Nov 2011 | A1 |
20110276598 | Kozempel | Nov 2011 | A1 |
20110276944 | Bergman et al. | Nov 2011 | A1 |
20110279368 | Klein et al. | Nov 2011 | A1 |
20110280143 | Li et al. | Nov 2011 | A1 |
20110282663 | Talwar et al. | Nov 2011 | A1 |
20110282888 | Koperski et al. | Nov 2011 | A1 |
20110282906 | Wong | Nov 2011 | A1 |
20110283189 | McCarty | Nov 2011 | A1 |
20110283190 | Poltorak | Nov 2011 | A1 |
20110288852 | Dymetman et al. | Nov 2011 | A1 |
20110288855 | Roy | Nov 2011 | A1 |
20110288861 | Kurzweil et al. | Nov 2011 | A1 |
20110288863 | Rasmussen | Nov 2011 | A1 |
20110288866 | Rasmussen | Nov 2011 | A1 |
20110298585 | Barry | Dec 2011 | A1 |
20110301943 | Patch | Dec 2011 | A1 |
20110302162 | Xiao et al. | Dec 2011 | A1 |
20110302645 | Headley | Dec 2011 | A1 |
20110306426 | Novak et al. | Dec 2011 | A1 |
20110307241 | Waibel et al. | Dec 2011 | A1 |
20110307254 | Hunt et al. | Dec 2011 | A1 |
20110307491 | Fisk et al. | Dec 2011 | A1 |
20110307810 | Hilerio et al. | Dec 2011 | A1 |
20110313775 | Laligand et al. | Dec 2011 | A1 |
20110313803 | Friend et al. | Dec 2011 | A1 |
20110314003 | Ju et al. | Dec 2011 | A1 |
20110314032 | Bennett et al. | Dec 2011 | A1 |
20110314404 | Kotler et al. | Dec 2011 | A1 |
20110314539 | Horton | Dec 2011 | A1 |
20110320187 | Motik et al. | Dec 2011 | A1 |
20120002820 | Leichter | 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 |
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 |
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 |
20120041752 | Wang et al. | Feb 2012 | A1 |
20120041756 | Hanazawa et al. | Feb 2012 | A1 |
20120042014 | Desai et al. | Feb 2012 | A1 |
20120042343 | Laligand et al. | Feb 2012 | A1 |
20120053815 | Montanari et al. | Mar 2012 | A1 |
20120053829 | Agarwal et al. | Mar 2012 | A1 |
20120053945 | Gupta et al. | Mar 2012 | A1 |
20120056815 | Mehra | 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 |
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 |
20120084634 | Wong et al. | Apr 2012 | A1 |
20120088219 | Briscoe et al. | Apr 2012 | A1 |
20120089331 | Schmidt et al. | Apr 2012 | A1 |
20120101823 | Weng et al. | Apr 2012 | A1 |
20120108166 | Hymel | May 2012 | A1 |
20120108221 | Thomas et al. | May 2012 | A1 |
20120109997 | Sparks et al. | May 2012 | A1 |
20120110456 | Larco et al. | May 2012 | A1 |
20120116770 | Chen et al. | May 2012 | A1 |
20120117499 | Mori 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 |
20120136572 | Norton | May 2012 | A1 |
20120136649 | Freising 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 |
20120149342 | Cohen et al. | Jun 2012 | A1 |
20120149394 | Singh 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 |
20120163710 | Skaff et al. | Jun 2012 | A1 |
20120166196 | Ju et al. | Jun 2012 | A1 |
20120166959 | Hilerio 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 |
20120179457 | Newman et al. | Jul 2012 | A1 |
20120179467 | Williams | Jul 2012 | A1 |
20120185237 | Gajic et al. | Jul 2012 | A1 |
20120185480 | Ni et al. | Jul 2012 | A1 |
20120185781 | Guzman 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 |
20120197995 | Caruso | Aug 2012 | A1 |
20120197998 | Kessel et al. | Aug 2012 | A1 |
20120201362 | Crossan 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 |
20120214141 | Raya et al. | Aug 2012 | A1 |
20120214517 | Singh 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 |
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 et al. | Sep 2012 | A1 |
20120233207 | Mohajer | Sep 2012 | A1 |
20120233266 | Hassan 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 |
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 |
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 |
20120275377 | Lehane et al. | Nov 2012 | A1 |
20120278744 | Kozitsyn et al. | 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 |
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 |
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 |
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 |
20120316862 | Sultan et al. | Dec 2012 | A1 |
20120316875 | Nyquist et al. | Dec 2012 | A1 |
20120316878 | Singleton et al. | Dec 2012 | A1 |
20120317194 | Tian | Dec 2012 | A1 |
20120317498 | Logan et al. | Dec 2012 | A1 |
20120321112 | Schubert et al. | Dec 2012 | A1 |
20120324391 | Tocci et al. | 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 |
20130018659 | Chi | Jan 2013 | A1 |
20130024576 | Dishneau et al. | Jan 2013 | A1 |
20130027875 | Zhu et al. | Jan 2013 | A1 |
20130030787 | Cancedda et al. | Jan 2013 | A1 |
20130030789 | Dalce | Jan 2013 | A1 |
20130030804 | Zavaliagko et al. | Jan 2013 | A1 |
20130030815 | Madhvanath 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 |
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 |
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 |
20130050089 | Neels et al. | Feb 2013 | A1 |
20130054550 | Bolohan | Feb 2013 | A1 |
20130054609 | Rajput et al. | Feb 2013 | A1 |
20130054613 | Bishop | Feb 2013 | A1 |
20130054675 | Jenkins et al. | Feb 2013 | A1 |
20130054706 | Graham et al. | Feb 2013 | A1 |
20130055099 | Yao et al. | Feb 2013 | A1 |
20130055147 | Vasudev et al. | Feb 2013 | A1 |
20130063611 | Papakipos et al. | Mar 2013 | A1 |
20130066832 | Sheehan et al. | Mar 2013 | A1 |
20130067307 | Tian et al. | Mar 2013 | A1 |
20130073286 | Bastea-Forte et al. | Mar 2013 | A1 |
20130073346 | Chun et al. | 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 |
20130085755 | Bringert et al. | Apr 2013 | A1 |
20130085761 | Bringert 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 |
20130096917 | Edgar et al. | Apr 2013 | A1 |
20130097566 | Berglund | Apr 2013 | A1 |
20130097682 | Zeljkovic 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 |
20130110505 | Gruber 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 |
20130125168 | Agnihotri 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 et al. | Jun 2013 | A1 |
20130151339 | Kim et al. | Jun 2013 | A1 |
20130152092 | Yadgar et al. | Jun 2013 | A1 |
20130154811 | Ferren et al. | Jun 2013 | A1 |
20130157629 | Lee et al. | Jun 2013 | A1 |
20130158977 | Senior | Jun 2013 | A1 |
20130159847 | Banke et al. | Jun 2013 | A1 |
20130165232 | Nelson et al. | Jun 2013 | A1 |
20130166303 | Chang et al. | Jun 2013 | A1 |
20130166442 | Nakajima et al. | Jun 2013 | A1 |
20130170738 | Capuozzo et al. | Jul 2013 | A1 |
20130172022 | Seymour et al. | Jul 2013 | A1 |
20130173258 | Liu et al. | Jul 2013 | A1 |
20130174034 | Brown et al. | Jul 2013 | A1 |
20130176244 | Yamamoto et al. | Jul 2013 | A1 |
20130176592 | Sasaki | Jul 2013 | A1 |
20130179172 | Nakamura et al. | Jul 2013 | A1 |
20130179440 | Gordon | Jul 2013 | A1 |
20130183944 | Mozer et al. | Jul 2013 | A1 |
20130185059 | Riccardi 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 |
20130191117 | Atti et al. | Jul 2013 | A1 |
20130197911 | Wei et al. | Aug 2013 | A1 |
20130198841 | Poulson | Aug 2013 | A1 |
20130204813 | Master et al. | Aug 2013 | A1 |
20130204897 | McDougall | Aug 2013 | A1 |
20130207898 | Sullivan et al. | Aug 2013 | A1 |
20130218553 | Fujii et al. | Aug 2013 | A1 |
20130218560 | Hsiao et al. | Aug 2013 | A1 |
20130219333 | Palwe et al. | Aug 2013 | A1 |
20130222249 | Pasquero et al. | Aug 2013 | A1 |
20130225128 | Gomar | Aug 2013 | A1 |
20130226935 | Bai et al. | Aug 2013 | A1 |
20130231917 | Naik | Sep 2013 | A1 |
20130234947 | Kristensson et al. | Sep 2013 | A1 |
20130235987 | Arroniz-Escobar et al. | Sep 2013 | A1 |
20130238326 | Kim et al. | Sep 2013 | A1 |
20130238647 | Thompson | Sep 2013 | A1 |
20130244615 | Miller 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 |
20130268263 | Park et al. | Oct 2013 | A1 |
20130275117 | Winer | 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 |
20130282709 | Zhu et al. | Oct 2013 | A1 |
20130283168 | Brown et al. | Oct 2013 | A1 |
20130285913 | Griffin et al. | Oct 2013 | A1 |
20130289991 | Eshwar et al. | Oct 2013 | A1 |
20130289993 | Rao et al. | Oct 2013 | A1 |
20130289994 | Newman et al. | Oct 2013 | A1 |
20130291015 | Pan | Oct 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 |
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 |
20130311184 | Badavne et al. | Nov 2013 | A1 |
20130311997 | Gruber et al. | Nov 2013 | A1 |
20130316746 | Miller et al. | Nov 2013 | A1 |
20130322634 | Bennett 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 |
20130325481 | Van Os et al. | Dec 2013 | A1 |
20130325484 | Chakladar et al. | Dec 2013 | A1 |
20130325967 | Parks et al. | Dec 2013 | A1 |
20130325970 | Roberts et al. | Dec 2013 | A1 |
20130325979 | Mansfield 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 |
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 |
20130339256 | Shroff | Dec 2013 | A1 |
20130343721 | Abecassis | Dec 2013 | A1 |
20130346068 | Solem et al. | Dec 2013 | A1 |
20130346347 | Patterson et al. | Dec 2013 | A1 |
20130347117 | Parks et al. | Dec 2013 | A1 |
20140006012 | Zhou et al. | Jan 2014 | A1 |
20140006025 | Krishnan et al. | Jan 2014 | A1 |
20140006027 | Kim et al. | Jan 2014 | A1 |
20140006030 | Fleizach et al. | Jan 2014 | A1 |
20140006153 | Thangam et al. | Jan 2014 | A1 |
20140006483 | Garmark et al. | Jan 2014 | A1 |
20140006947 | Garmark et al. | Jan 2014 | A1 |
20140012574 | Pasupalak et al. | Jan 2014 | A1 |
20140012580 | Ganong et al. | Jan 2014 | A1 |
20140012586 | Rubin et al. | Jan 2014 | A1 |
20140012587 | Park | Jan 2014 | A1 |
20140019116 | Lundberg et al. | Jan 2014 | A1 |
20140019133 | Bao et al. | Jan 2014 | A1 |
20140019460 | Sambrani et al. | Jan 2014 | A1 |
20140028735 | Williams et al. | Jan 2014 | A1 |
20140032453 | Eustice et al. | Jan 2014 | A1 |
20140033071 | Gruber et al. | Jan 2014 | A1 |
20140035823 | Khoe et al. | Feb 2014 | A1 |
20140039888 | Taubman et al. | Feb 2014 | A1 |
20140039893 | Weiner | Feb 2014 | A1 |
20140039894 | Shostak | Feb 2014 | A1 |
20140040274 | Aravamudan et al. | Feb 2014 | A1 |
20140040748 | Lemay et al. | Feb 2014 | A1 |
20140040801 | Patel et al. | Feb 2014 | A1 |
20140040918 | Li et al. | Feb 2014 | A1 |
20140040961 | Green, Sr. 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 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 |
20140067361 | Nikoulina et al. | Mar 2014 | A1 |
20140067371 | Liensberger | Mar 2014 | A1 |
20140067402 | Kim | Mar 2014 | A1 |
20140068751 | Last et al. | 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 |
20140074483 | Van Os | Mar 2014 | A1 |
20140074815 | Plimton | Mar 2014 | A1 |
20140078065 | Akkok et al. | Mar 2014 | A1 |
20140079195 | Srivastava et al. | Mar 2014 | A1 |
20140080428 | Rhoads et al. | Mar 2014 | A1 |
20140081619 | Solntseva et al. | Mar 2014 | A1 |
20140081633 | Badaskar et al. | Mar 2014 | A1 |
20140082501 | Bae et al. | Mar 2014 | A1 |
20140086458 | Rogers et al. | Mar 2014 | A1 |
20140087711 | Geyer et al. | Mar 2014 | A1 |
20140088961 | Woodward et al. | Mar 2014 | A1 |
20140095171 | Lynch et al. | Apr 2014 | A1 |
20140095172 | Cabaco et al. | Apr 2014 | A1 |
20140095173 | Lynch et al. | Apr 2014 | A1 |
20140095601 | Abuelsaad 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 |
20140108017 | Mason et al. | 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 |
20140122059 | Patel et al. | May 2014 | A1 |
20140122086 | Kapur et al. | May 2014 | A1 |
20140122136 | Jayanthi | May 2014 | A1 |
20140122153 | Truitt | May 2014 | A1 |
20140132935 | Kim et al. | May 2014 | A1 |
20140134983 | Jung et al. | May 2014 | A1 |
20140135036 | Bonanni 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 |
20140143550 | Ganong, III et al. | May 2014 | A1 |
20140143721 | Suzuki et al. | May 2014 | A1 |
20140146200 | Scott 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 |
20140156279 | Okamoto et al. | Jun 2014 | A1 |
20140157422 | Livshits 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 |
20140163981 | Cook et al. | Jun 2014 | A1 |
20140163995 | Burns et al. | Jun 2014 | A1 |
20140164305 | Lynch et al. | Jun 2014 | A1 |
20140164476 | Thomson | Jun 2014 | A1 |
20140164532 | Lynch et al. | Jun 2014 | A1 |
20140164533 | Lynch et al. | Jun 2014 | A1 |
20140169795 | Clough | Jun 2014 | A1 |
20140172878 | Clark et al. | Jun 2014 | A1 |
20140173460 | Kim | Jun 2014 | A1 |
20140180499 | Cooper et al. | Jun 2014 | A1 |
20140180689 | Kim et al. | Jun 2014 | A1 |
20140180697 | Torok et al. | Jun 2014 | A1 |
20140181865 | Koganei | Jun 2014 | A1 |
20140188477 | Zhang | Jul 2014 | A1 |
20140195226 | Yun et al. | Jul 2014 | A1 |
20140195230 | Han et al. | Jul 2014 | A1 |
20140195233 | Bapat | 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 |
20140207466 | Smadi et al. | Jul 2014 | A1 |
20140207468 | Bartnik | Jul 2014 | A1 |
20140207582 | Flinn et al. | Jul 2014 | A1 |
20140214429 | Pantel | Jul 2014 | A1 |
20140214537 | Yoo et al. | Jul 2014 | A1 |
20140215513 | Ramer et al. | Jul 2014 | A1 |
20140218372 | Missig et al. | Aug 2014 | A1 |
20140222436 | Binder et al. | Aug 2014 | A1 |
20140222678 | Sheets et al. | Aug 2014 | A1 |
20140223377 | Shaw et al. | Aug 2014 | A1 |
20140223481 | Fundament | Aug 2014 | A1 |
20140226503 | Cooper et al. | Aug 2014 | A1 |
20140229184 | Shires | Aug 2014 | A1 |
20140230055 | Boehl | 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 |
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 |
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 |
20140249817 | Hart 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 |
20140258857 | Dykstra-Erickson et al. | Sep 2014 | A1 |
20140267022 | Kim | Sep 2014 | A1 |
20140267599 | Drouin et al. | Sep 2014 | A1 |
20140272821 | Pitschel et al. | Sep 2014 | A1 |
20140274005 | Luna et al. | Sep 2014 | A1 |
20140274203 | Ganong et al. | Sep 2014 | A1 |
20140274211 | Sejnoha 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 |
20140278429 | Ganong, III | Sep 2014 | A1 |
20140278435 | Ganong et al. | Sep 2014 | A1 |
20140278436 | Khanna et al. | Sep 2014 | A1 |
20140278443 | Gunn et al. | Sep 2014 | A1 |
20140278513 | Prakash et al. | Sep 2014 | A1 |
20140279739 | Elkington 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 |
20140281983 | Xian et al. | Sep 2014 | A1 |
20140282003 | Gruber et al. | Sep 2014 | A1 |
20140282007 | Fleizach | Sep 2014 | A1 |
20140282045 | Ayanam et al. | Sep 2014 | A1 |
20140282201 | Pasquero et al. | Sep 2014 | A1 |
20140282203 | Pasquero 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 |
20140304605 | Ohmura et al. | Oct 2014 | A1 |
20140309996 | Zhang | Oct 2014 | A1 |
20140310001 | Kalns et al. | Oct 2014 | A1 |
20140310002 | Nitz et al. | Oct 2014 | A1 |
20140316585 | Boesveld et al. | Oct 2014 | A1 |
20140317030 | Shen et al. | Oct 2014 | A1 |
20140317502 | Brown et al. | Oct 2014 | A1 |
20140324884 | Lindahl et al. | Oct 2014 | A1 |
20140330569 | Kolavennu et al. | Nov 2014 | A1 |
20140337048 | Brown et al. | Nov 2014 | A1 |
20140337266 | Wolverton et al. | Nov 2014 | A1 |
20140337371 | Li | Nov 2014 | A1 |
20140337438 | Govande et al. | Nov 2014 | A1 |
20140337751 | Lim et al. | Nov 2014 | A1 |
20140337814 | Kalns et al. | Nov 2014 | A1 |
20140342762 | Hajdu et al. | Nov 2014 | A1 |
20140344627 | Schaub et al. | Nov 2014 | A1 |
20140344687 | Durham et al. | 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 |
20140358523 | Sheth 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 |
20140365880 | Bellegarda | Dec 2014 | A1 |
20140365885 | Carson et al. | Dec 2014 | A1 |
20140365895 | Paulson 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 |
20140372931 | Zhai et al. | Dec 2014 | A1 |
20140379334 | Fry | Dec 2014 | A1 |
20140379341 | Seo et al. | Dec 2014 | A1 |
20140380285 | Gabel et al. | Dec 2014 | A1 |
20150003797 | Schmidt | Jan 2015 | A1 |
20150006148 | Goldszmit et al. | Jan 2015 | A1 |
20150006157 | Andrade Silva 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 |
20150019219 | Tzirkel-hancock et al. | Jan 2015 | A1 |
20150019221 | Lee et al. | Jan 2015 | A1 |
20150019974 | Doi et al. | Jan 2015 | A1 |
20150031416 | Wells et al. | Jan 2015 | A1 |
20150033219 | Breiner et al. | Jan 2015 | A1 |
20150033275 | Natani et al. | Jan 2015 | A1 |
20150039292 | Suleman et al. | 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 |
20150046537 | Rakib | Feb 2015 | A1 |
20150050633 | Christmas et al. | Feb 2015 | A1 |
20150053779 | Adamek et al. | Feb 2015 | A1 |
20150053781 | Nelson et al. | Feb 2015 | A1 |
20150058013 | Pakhomov et al. | Feb 2015 | A1 |
20150058018 | Georges et al. | Feb 2015 | A1 |
20150058785 | Ookawara | Feb 2015 | A1 |
20150065200 | Namgung 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 |
20150067485 | Kim et al. | Mar 2015 | A1 |
20150067822 | Randall | Mar 2015 | A1 |
20150071121 | Patil et al. | Mar 2015 | A1 |
20150073788 | Allauzen 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 |
20150082229 | Ouyang et al. | Mar 2015 | A1 |
20150088511 | Bharadwaj et al. | Mar 2015 | A1 |
20150088514 | Typrin | Mar 2015 | A1 |
20150088522 | Hendrickson et al. | Mar 2015 | A1 |
20150088523 | Schuster | Mar 2015 | A1 |
20150095031 | Conkie et al. | Apr 2015 | A1 |
20150095278 | Flinn et al. | Apr 2015 | A1 |
20150100316 | Williams et al. | Apr 2015 | A1 |
20150100537 | Grieves et al. | Apr 2015 | A1 |
20150100983 | Pan | Apr 2015 | A1 |
20150106093 | Weeks et al. | Apr 2015 | A1 |
20150113407 | Hoffert et al. | Apr 2015 | A1 |
20150120296 | Stern et al. | Apr 2015 | A1 |
20150120723 | Deshmukh et al. | Apr 2015 | A1 |
20150121216 | Brown et al. | Apr 2015 | A1 |
20150127337 | Heigold et al. | May 2015 | A1 |
20150127348 | Follis | May 2015 | A1 |
20150127350 | Agiomyrgiannakis | May 2015 | A1 |
20150133109 | Freeman 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 |
20150142420 | Sarikaya et al. | May 2015 | A1 |
20150142438 | Dai et al. | May 2015 | A1 |
20150142447 | Kennewick et al. | May 2015 | A1 |
20150142851 | Gupta 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 |
20150154185 | Waibel | Jun 2015 | A1 |
20150154976 | Mutagi | Jun 2015 | A1 |
20150160855 | Bi | Jun 2015 | A1 |
20150161370 | North et al. | Jun 2015 | A1 |
20150161521 | Shah et al. | Jun 2015 | A1 |
20150161989 | Hsu et al. | Jun 2015 | A1 |
20150162001 | Kar et al. | Jun 2015 | A1 |
20150163558 | Wheatley | Jun 2015 | A1 |
20150169284 | Quast et al. | Jun 2015 | A1 |
20150169336 | Harper et al. | 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 |
20150179176 | Ryu et al. | Jun 2015 | A1 |
20150185964 | Stout | 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 |
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 |
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 |
20150201064 | Bells et al. | Jul 2015 | A1 |
20150201077 | Konig et al. | Jul 2015 | A1 |
20150205858 | Xie et al. | Jul 2015 | A1 |
20150208226 | Kuusilinna et al. | Jul 2015 | A1 |
20150212791 | Kumar et al. | Jul 2015 | A1 |
20150213796 | Waltermann et al. | Jul 2015 | A1 |
20150215258 | Nowakowski et al. | Jul 2015 | A1 |
20150220507 | Mohajer et al. | Aug 2015 | A1 |
20150221304 | Stewart | Aug 2015 | A1 |
20150221307 | Shah et al. | Aug 2015 | A1 |
20150227505 | Morimoto | Aug 2015 | A1 |
20150227633 | Shapira | Aug 2015 | A1 |
20150228274 | Leppnen et al. | Aug 2015 | A1 |
20150228281 | Raniere | Aug 2015 | A1 |
20150230095 | Smith et al. | Aug 2015 | A1 |
20150234636 | Barnes, Jr. | Aug 2015 | A1 |
20150234800 | Patrick et al. | Aug 2015 | A1 |
20150242091 | Lu et al. | Aug 2015 | A1 |
20150243278 | Kibre et al. | Aug 2015 | A1 |
20150243283 | Halash 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 |
20150254057 | Klein et al. | Sep 2015 | A1 |
20150254058 | Klein et al. | Sep 2015 | A1 |
20150254333 | Fife et al. | Sep 2015 | A1 |
20150255071 | Chiba | Sep 2015 | A1 |
20150256873 | Klein et al. | Sep 2015 | A1 |
20150261496 | Faaborg et al. | Sep 2015 | A1 |
20150261850 | Mittal | Sep 2015 | A1 |
20150269139 | McAteer et al. | Sep 2015 | A1 |
20150277574 | Jain et al. | Oct 2015 | A1 |
20150278370 | Stratvert et al. | Oct 2015 | A1 |
20150279358 | Kingsbury et al. | Oct 2015 | A1 |
20150279360 | Mengibar et al. | Oct 2015 | A1 |
20150281380 | Wang et al. | Oct 2015 | A1 |
20150286627 | Chang et al. | Oct 2015 | A1 |
20150287401 | Lee et al. | Oct 2015 | A1 |
20150287409 | Jang | 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 |
20150295915 | Xiu | Oct 2015 | A1 |
20150302855 | Kim et al. | Oct 2015 | A1 |
20150302856 | Kim et al. | Oct 2015 | A1 |
20150302857 | Yamada | Oct 2015 | A1 |
20150309997 | Lee 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 |
20150312182 | Langholz | Oct 2015 | A1 |
20150317069 | Clements et al. | Nov 2015 | A1 |
20150317310 | Eiche et al. | Nov 2015 | A1 |
20150324041 | Varley et al. | Nov 2015 | A1 |
20150324334 | Lee et al. | Nov 2015 | A1 |
20150331664 | Osawa et al. | Nov 2015 | A1 |
20150331711 | Huang et al. | Nov 2015 | A1 |
20150332667 | Mason | 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 |
20150340040 | Mun et al. | Nov 2015 | A1 |
20150340042 | Sejnoha et al. | Nov 2015 | A1 |
20150341717 | Song et al. | Nov 2015 | A1 |
20150347086 | Liedholm et al. | Dec 2015 | A1 |
20150347381 | Bellegarda | Dec 2015 | A1 |
20150347382 | Dolfing et al. | Dec 2015 | A1 |
20150347385 | Flor et al. | Dec 2015 | A1 |
20150347393 | Futrell et al. | Dec 2015 | A1 |
20150347733 | Tsou et al. | Dec 2015 | A1 |
20150347985 | Gross 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 |
20150350031 | Burks et al. | Dec 2015 | A1 |
20150350342 | Thorpe 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 | Thorn | Dec 2015 | A1 |
20150370531 | Faaborg | Dec 2015 | A1 |
20150370780 | Wang et al. | Dec 2015 | A1 |
20150371215 | Zhou et al. | Dec 2015 | A1 |
20150371529 | Dolecki | Dec 2015 | A1 |
20150371639 | Foerster et al. | Dec 2015 | A1 |
20150371665 | Naik et al. | Dec 2015 | A1 |
20150373183 | Woolsey et al. | Dec 2015 | A1 |
20150379414 | Yeh et al. | Dec 2015 | A1 |
20150379993 | Subhojit et al. | Dec 2015 | A1 |
20150382047 | Napolitano et al. | Dec 2015 | A1 |
20150382079 | Lister et al. | Dec 2015 | A1 |
20150382147 | Clark et al. | Dec 2015 | A1 |
20160004690 | Bangalore et al. | Jan 2016 | A1 |
20160005320 | deCharms et al. | Jan 2016 | A1 |
20160012038 | Edwards et al. | Jan 2016 | A1 |
20160014476 | Caliendo, Jr. et al. | Jan 2016 | A1 |
20160018900 | Tu et al. | Jan 2016 | A1 |
20160019886 | Hong | Jan 2016 | A1 |
20160026258 | Ou et al. | Jan 2016 | A1 |
20160027431 | Kurzweil et al. | Jan 2016 | A1 |
20160028666 | Li | Jan 2016 | A1 |
20160029316 | Mohan et al. | Jan 2016 | A1 |
20160034042 | Joo | Feb 2016 | A1 |
20160034811 | Paulik et al. | Feb 2016 | A1 |
20160042735 | Vibbert et al. | Feb 2016 | A1 |
20160042748 | Jain et al. | Feb 2016 | A1 |
20160048666 | Dey et al. | Feb 2016 | A1 |
20160055422 | Li | Feb 2016 | A1 |
20160062605 | Agarwal et al. | Mar 2016 | A1 |
20160063998 | Krishnamoorthy et al. | Mar 2016 | A1 |
20160070581 | Soon-Shiong | Mar 2016 | A1 |
20160071516 | Lee et al. | Mar 2016 | A1 |
20160071521 | Haughay | Mar 2016 | A1 |
20160072940 | Cronin | Mar 2016 | A1 |
20160077794 | Kim et al. | Mar 2016 | A1 |
20160078860 | Paulik et al. | Mar 2016 | A1 |
20160080165 | Ehsani et al. | Mar 2016 | A1 |
20160086116 | Rao et al. | Mar 2016 | A1 |
20160091967 | Prokofieva et al. | Mar 2016 | A1 |
20160092447 | Venkataraman 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 |
20160094979 | Naik et al. | Mar 2016 | A1 |
20160098991 | Luo et al. | Apr 2016 | A1 |
20160104486 | Penilla et al. | Apr 2016 | A1 |
20160111091 | Bakish | 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 |
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 |
20160154880 | Hoarty | Jun 2016 | A1 |
20160155442 | Kannan et al. | Jun 2016 | A1 |
20160155443 | Khan 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 |
20160170966 | Kolo | Jun 2016 | A1 |
20160173578 | Sharma et al. | Jun 2016 | A1 |
20160173960 | Snibbe et al. | Jun 2016 | A1 |
20160179462 | Bjorkengren | Jun 2016 | A1 |
20160179787 | Deleeuw | 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 |
20160189717 | Kannan et al. | Jun 2016 | A1 |
20160198319 | Huang et al. | Jul 2016 | A1 |
20160210551 | Lee et al. | Jul 2016 | A1 |
20160210981 | Lee | Jul 2016 | A1 |
20160212488 | Os et al. | Jul 2016 | A1 |
20160217784 | Gelfenbeyn et al. | Jul 2016 | A1 |
20160224540 | Stewart et al. | Aug 2016 | A1 |
20160224774 | Pender | Aug 2016 | A1 |
20160225372 | Cheung et al. | Aug 2016 | A1 |
20160239645 | Heo et al. | Aug 2016 | A1 |
20160240187 | Fleizach et al. | Aug 2016 | A1 |
20160240189 | Lee et al. | Aug 2016 | A1 |
20160247061 | Trask 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 |
20160266871 | Schmid et al. | Sep 2016 | A1 |
20160267904 | Biadsy 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 |
20160284005 | Daniel et al. | Sep 2016 | A1 |
20160284199 | Dotan-Cohen et al. | Sep 2016 | A1 |
20160286045 | Shaltiel et al. | Sep 2016 | A1 |
20160293168 | Chen | Oct 2016 | A1 |
20160299685 | Zhai et al. | Oct 2016 | A1 |
20160299882 | Hegerty et al. | Oct 2016 | A1 |
20160299883 | Zhu et al. | Oct 2016 | A1 |
20160307566 | Bellegarda | Oct 2016 | A1 |
20160313906 | Kilchenko et al. | Oct 2016 | A1 |
20160314788 | Jitkoff et al. | Oct 2016 | A1 |
20160314792 | Alvarez et al. | Oct 2016 | A1 |
20160315996 | Ha et al. | Oct 2016 | A1 |
20160317924 | Tanaka et al. | Nov 2016 | A1 |
20160321261 | Spasojevic et al. | Nov 2016 | A1 |
20160322045 | Hatfeild et al. | Nov 2016 | A1 |
20160322048 | Amano et al. | Nov 2016 | A1 |
20160322050 | Wang et al. | Nov 2016 | A1 |
20160328205 | Agrawal et al. | Nov 2016 | A1 |
20160328893 | Cordova et al. | Nov 2016 | A1 |
20160336007 | Hanazawa | Nov 2016 | A1 |
20160336010 | Lindahl | Nov 2016 | A1 |
20160336024 | Choi et al. | Nov 2016 | A1 |
20160337299 | Lane et al. | Nov 2016 | A1 |
20160337301 | Rollins et al. | Nov 2016 | A1 |
20160342685 | Basu et al. | Nov 2016 | A1 |
20160342781 | Jeon | Nov 2016 | A1 |
20160351190 | Binder et al. | Dec 2016 | A1 |
20160352567 | Robbins 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 |
20160378747 | Orr et al. | Dec 2016 | A1 |
20160379091 | Lin et al. | Dec 2016 | A1 |
20160379626 | Deisher et al. | Dec 2016 | A1 |
20160379633 | Lehman et al. | Dec 2016 | A1 |
20160379641 | Liu et al. | Dec 2016 | A1 |
20170003931 | Dvortsov et al. | Jan 2017 | A1 |
20170004824 | Yoo et al. | Jan 2017 | A1 |
20170011091 | Chehreghani | Jan 2017 | A1 |
20170011303 | Annapureddy et al. | Jan 2017 | A1 |
20170011742 | Jing et al. | Jan 2017 | A1 |
20170013124 | Havelka et al. | Jan 2017 | A1 |
20170018271 | Khan et al. | Jan 2017 | A1 |
20170019987 | Dragone et al. | Jan 2017 | A1 |
20170025124 | Mixter et al. | Jan 2017 | A1 |
20170031576 | Saoji et al. | Feb 2017 | A1 |
20170032783 | Lord et al. | Feb 2017 | A1 |
20170032791 | Elson et al. | Feb 2017 | A1 |
20170039475 | Cheyer et al. | Feb 2017 | A1 |
20170040002 | Basson et al. | Feb 2017 | A1 |
20170055895 | Des 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 |
20170076720 | Gopalan et al. | Mar 2017 | A1 |
20170076721 | Bargetzi et al. | Mar 2017 | A1 |
20170083179 | Gruber et al. | Mar 2017 | A1 |
20170083285 | Meyers et al. | Mar 2017 | A1 |
20170083504 | Huang | Mar 2017 | A1 |
20170085547 | De Aguiar et al. | Mar 2017 | A1 |
20170090569 | Levesque | Mar 2017 | A1 |
20170091168 | Bellegarda et al. | Mar 2017 | A1 |
20170092270 | Newendorp et al. | Mar 2017 | A1 |
20170092278 | Evermann et al. | Mar 2017 | A1 |
20170102837 | Toumpelis | Apr 2017 | A1 |
20170102915 | Kuscher et al. | Apr 2017 | A1 |
20170103749 | Zhao et al. | Apr 2017 | A1 |
20170105190 | Logan et al. | Apr 2017 | A1 |
20170116177 | Walia | Apr 2017 | A1 |
20170116989 | Yadgar et al. | Apr 2017 | A1 |
20170124190 | Wang et al. | 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 |
20170140644 | Hwang et al. | May 2017 | A1 |
20170148044 | Fukuda et al. | May 2017 | A1 |
20170154033 | Lee | Jun 2017 | A1 |
20170154055 | Dimson et al. | Jun 2017 | A1 |
20170155940 | Ji et al. | Jun 2017 | A1 |
20170161018 | Lemay et al. | Jun 2017 | A1 |
20170161268 | Badaskar | Jun 2017 | A1 |
20170161293 | Ionescu et al. | Jun 2017 | A1 |
20170169818 | VanBlon et al. | Jun 2017 | A1 |
20170169819 | Mese et al. | Jun 2017 | A1 |
20170177547 | Ciereszko et al. | Jun 2017 | A1 |
20170178619 | Naik et al. | Jun 2017 | A1 |
20170178626 | Gruber et al. | 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 |
20170193083 | Bhatt et al. | Jul 2017 | A1 |
20170195493 | Kasilya Sudarsan 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 |
20170206899 | Bryant et al. | Jul 2017 | A1 |
20170221486 | Kurata 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 |
20170230429 | Garmark et al. | Aug 2017 | A1 |
20170230709 | Van Os et al. | Aug 2017 | A1 |
20170236512 | Williams et al. | Aug 2017 | A1 |
20170242653 | Lang et al. | Aug 2017 | A1 |
20170242657 | Jarvis et al. | Aug 2017 | A1 |
20170243468 | Dotan-Cohen et al. | Aug 2017 | A1 |
20170256256 | Wang 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 |
20170264451 | Yu et al. | Sep 2017 | A1 |
20170264711 | Natarajan et al. | Sep 2017 | A1 |
20170278514 | Mathias et al. | Sep 2017 | A1 |
20170285915 | Napolitano et al. | Oct 2017 | A1 |
20170286397 | Gonzalez | Oct 2017 | A1 |
20170295446 | Thagadur Shivappa | Oct 2017 | A1 |
20170311005 | Lin | Oct 2017 | A1 |
20170316775 | Le et al. | Nov 2017 | A1 |
20170316782 | Haughay et al. | Nov 2017 | A1 |
20170323637 | Naik | Nov 2017 | A1 |
20170329490 | Esinovskaya et al. | Nov 2017 | A1 |
20170329572 | Shah et al. | Nov 2017 | A1 |
20170345411 | Raitio et al. | Nov 2017 | A1 |
20170346949 | Sanghavi et al. | Nov 2017 | A1 |
20170352346 | Paulik et al. | Dec 2017 | A1 |
20170352350 | Booker et al. | Dec 2017 | A1 |
20170357478 | Piersol 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 |
20170371885 | Aggarwal et al. | Dec 2017 | A1 |
20170374093 | Dhar et al. | Dec 2017 | A1 |
20180007060 | Leblang 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 |
20180033431 | Newendorp et al. | Feb 2018 | A1 |
20180047406 | Park | Feb 2018 | A1 |
20180054505 | Hart et al. | Feb 2018 | A1 |
20180060032 | Boesen | Mar 2018 | A1 |
20180060312 | Won | Mar 2018 | A1 |
20180061400 | Carbune et al. | Mar 2018 | A1 |
20180063624 | Boesen | Mar 2018 | A1 |
20180067914 | Chen et al. | Mar 2018 | A1 |
20180069743 | Bakken et al. | Mar 2018 | A1 |
20180090143 | Saddler et al. | Mar 2018 | A1 |
20180096683 | James et al. | Apr 2018 | A1 |
20180107945 | Gao et al. | Apr 2018 | A1 |
20180108346 | Paulik et al. | Apr 2018 | A1 |
20180122378 | Mixter et al. | 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 |
20180144748 | Leong | May 2018 | A1 |
20180157372 | Kurabayashi | Jun 2018 | A1 |
20180182376 | Van Gysel et al. | Jun 2018 | A1 |
20180190273 | Karimli et al. | Jul 2018 | A1 |
20180196683 | Radebaugh et al. | Jul 2018 | A1 |
20180213448 | Segal et al. | Jul 2018 | A1 |
20180218735 | Hunt et al. | Aug 2018 | A1 |
20180232203 | Gelfenbeyn et al. | Aug 2018 | A1 |
20180253652 | Palzer et al. | Sep 2018 | A1 |
20180270343 | Rout et al. | Sep 2018 | A1 |
20180276197 | Nell et al. | Sep 2018 | A1 |
20180278740 | Choi et al. | Sep 2018 | A1 |
20180308485 | Kudurshian et al. | Oct 2018 | A1 |
20180308486 | Saddler et al. | Oct 2018 | A1 |
20180322112 | Bellegarda 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 |
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 |
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 |
20180336184 | Bellegarda et al. | Nov 2018 | A1 |
20180336275 | Graham et al. | Nov 2018 | A1 |
20180336449 | Adan et al. | Nov 2018 | A1 |
20180336892 | Kim et al. | Nov 2018 | A1 |
20180336894 | Graham et al. | Nov 2018 | A1 |
20180336905 | Kim et al. | Nov 2018 | A1 |
20180373487 | Gruber et al. | Dec 2018 | A1 |
20180374484 | Huang et al. | Dec 2018 | A1 |
20190012141 | Piersol et al. | Jan 2019 | A1 |
20190012449 | Cheyer | Jan 2019 | A1 |
20190014450 | Gruber et al. | Jan 2019 | A1 |
20190034040 | Shah et al. | Jan 2019 | A1 |
Number | Date | Country |
---|---|---|
2015203483 | Jul 2015 | AU |
2015101171 | Oct 2015 | AU |
2694314 | Aug 2010 | CA |
2792412 | Jul 2011 | CA |
2666438 | Jun 2013 | CA |
1898721 | Jan 2007 | CN |
1959628 | May 2007 | CN |
101162153 | Apr 2008 | CN |
101292282 | Oct 2008 | CN |
101416471 | Apr 2009 | CN |
101427244 | May 2009 | CN |
101448340 | Jun 2009 | CN |
101453498 | Jun 2009 | CN |
101499156 | Aug 2009 | CN |
101500041 | Aug 2009 | CN |
101515952 | Aug 2009 | CN |
101535983 | Sep 2009 | CN |
101547396 | Sep 2009 | CN |
101557432 | Oct 2009 | CN |
101601088 | Dec 2009 | CN |
101604521 | Dec 2009 | CN |
101632316 | Jan 2010 | CN |
101636736 | Jan 2010 | CN |
101673544 | Mar 2010 | CN |
101751387 | Jun 2010 | CN |
101833286 | Sep 2010 | CN |
101847405 | Sep 2010 | CN |
101894547 | Nov 2010 | CN |
101930789 | Dec 2010 | CN |
101939740 | Jan 2011 | CN |
101951553 | Jan 2011 | CN |
102137193 | Jul 2011 | CN |
102160043 | Aug 2011 | CN |
102201235 | Aug 2011 | CN |
102214187 | Oct 2011 | CN |
102246136 | Nov 2011 | CN |
202035047 | Nov 2011 | CN |
102282609 | Dec 2011 | CN |
202092650 | Dec 2011 | CN |
102368256 | Mar 2012 | CN |
102405463 | Apr 2012 | CN |
102498457 | Jun 2012 | CN |
102629246 | Aug 2012 | CN |
102682769 | Sep 2012 | CN |
102682771 | Sep 2012 | CN |
102685295 | Sep 2012 | CN |
102693725 | Sep 2012 | CN |
202453859 | Sep 2012 | CN |
102750087 | Oct 2012 | CN |
102792320 | Nov 2012 | CN |
102801853 | Nov 2012 | CN |
102870065 | Jan 2013 | CN |
102917004 | Feb 2013 | CN |
102917271 | Feb 2013 | CN |
102918493 | Feb 2013 | CN |
103035240 | Apr 2013 | CN |
103038728 | Apr 2013 | CN |
103093334 | May 2013 | CN |
103135916 | Jun 2013 | CN |
103198831 | Jul 2013 | CN |
103209369 | Jul 2013 | CN |
103292437 | Sep 2013 | CN |
103365279 | Oct 2013 | CN |
103562863 | Feb 2014 | CN |
103744761 | Apr 2014 | CN |
103795850 | May 2014 | CN |
103930945 | Jul 2014 | CN |
104038621 | Sep 2014 | CN |
104090652 | Oct 2014 | CN |
104144377 | Nov 2014 | CN |
104281259 | Jan 2015 | CN |
104284257 | Jan 2015 | CN |
104335234 | Feb 2015 | CN |
104423625 | Mar 2015 | CN |
104463552 | Mar 2015 | CN |
104516522 | Apr 2015 | CN |
104854583 | Aug 2015 | CN |
104951077 | Sep 2015 | CN |
105100356 | Nov 2015 | CN |
105247511 | Jan 2016 | CN |
105264524 | Jan 2016 | CN |
105471705 | Apr 2016 | CN |
107919123 | Apr 2018 | CN |
102008024258 | Nov 2009 | DE |
202016008226 | May 2017 | DE |
1699042 | Sep 2006 | EP |
1939860 | Jul 2008 | EP |
1909263 | Jan 2009 | EP |
1335620 | Mar 2009 | EP |
2069895 | Jun 2009 | EP |
2081185 | Jul 2009 | EP |
2094032 | Aug 2009 | EP |
2096840 | Sep 2009 | EP |
2107553 | Oct 2009 | EP |
2109295 | Oct 2009 | EP |
1720375 | Jul 2010 | EP |
2205010 | Jul 2010 | EP |
2309491 | Apr 2011 | EP |
2329348 | Jun 2011 | EP |
2339576 | Jun 2011 | EP |
2400373 | Dec 2011 | EP |
2431842 | Mar 2012 | EP |
2523188 | Nov 2012 | EP |
2551784 | Jan 2013 | EP |
2555536 | Feb 2013 | EP |
2575128 | Apr 2013 | EP |
2632129 | Aug 2013 | EP |
2669889 | Dec 2013 | EP |
2683175 | Jan 2014 | EP |
2733598 | May 2014 | EP |
2760015 | Jul 2014 | EP |
2801890 | Nov 2014 | EP |
2801972 | Nov 2014 | EP |
2824564 | Jan 2015 | EP |
2849177 | Mar 2015 | EP |
2930715 | Oct 2015 | EP |
2938022 | Oct 2015 | EP |
2940556 | Nov 2015 | EP |
2950307 | Dec 2015 | EP |
3035329 | Jun 2016 | EP |
3224708 | Oct 2017 | EP |
3246916 | Nov 2017 | EP |
3300074 | Mar 2018 | EP |
2983065 | Aug 2018 | EP |
6-208389 | Jul 1994 | JP |
6-332493 | 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-125896 | May 2001 | JP |
2001-297174 | Oct 2001 | JP |
2002-030676 | 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-341892 | Nov 2002 | JP |
2003-15682 | Jan 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-332212 | Dec 2005 | JP |
2005-334363 | 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 |
2009-2850 | Jan 2009 | JP |
2009-503623 | Jan 2009 | JP |
2009-36999 | Feb 2009 | JP |
2009-505142 | Feb 2009 | JP |
2009-47920 | Mar 2009 | JP |
2009-069062 | Apr 2009 | JP |
2009-98490 | May 2009 | JP |
2009-110300 | May 2009 | JP |
2009-116841 | May 2009 | JP |
2009-134409 | Jun 2009 | JP |
2009-140444 | Jun 2009 | JP |
2009-522861 | Jun 2009 | JP |
2009-157951 | Jul 2009 | JP |
2009-169470 | Jul 2009 | JP |
2009-177440 | Aug 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 |
2009-223840 | Oct 2009 | JP |
2009-294913 | Dec 2009 | JP |
2009-294946 | Dec 2009 | JP |
2009-543166 | Dec 2009 | JP |
2010-66519 | Mar 2010 | JP |
2010-78979 | Apr 2010 | JP |
2010-108378 | May 2010 | JP |
2010-518475 | May 2010 | JP |
2010-518526 | May 2010 | JP |
2010-146347 | Jul 2010 | JP |
2010-157207 | Jul 2010 | JP |
2010-166478 | Jul 2010 | JP |
2010-205111 | Sep 2010 | JP |
2010-224236 | Oct 2010 | JP |
4563106 | Oct 2010 | JP |
2010-535377 | Nov 2010 | JP |
2010-287063 | Dec 2010 | JP |
2011-33874 | Feb 2011 | JP |
2011-41026 | Mar 2011 | JP |
2011-45005 | Mar 2011 | JP |
2011-59659 | Mar 2011 | JP |
2011-81541 | Apr 2011 | JP |
2011-525045 | Sep 2011 | JP |
2011-238022 | Nov 2011 | JP |
2011-250027 | Dec 2011 | JP |
2012-014394 | Jan 2012 | JP |
2012-33997 | Feb 2012 | JP |
2012-508530 | Apr 2012 | JP |
2012-089020 | May 2012 | JP |
2012-116442 | Jun 2012 | JP |
2012-142744 | Jul 2012 | JP |
2012-147063 | Aug 2012 | JP |
2012-518847 | Aug 2012 | JP |
2013-37688 | Feb 2013 | JP |
2013-511214 | Mar 2013 | JP |
2013-65284 | Apr 2013 | JP |
2013-73240 | Apr 2013 | JP |
2013-513315 | Apr 2013 | JP |
2013-080476 | May 2013 | JP |
2013-517566 | May 2013 | JP |
2013-134430 | Jul 2013 | JP |
2013-140520 | Jul 2013 | JP |
2013-527947 | Jul 2013 | JP |
2013-528012 | Jul 2013 | JP |
2013-156349 | Aug 2013 | JP |
2013-200423 | Oct 2013 | JP |
2013-205999 | Oct 2013 | JP |
2013-238936 | Nov 2013 | JP |
2014-10688 | Jan 2014 | JP |
2014-026629 | Feb 2014 | JP |
2014-60600 | Apr 2014 | JP |
2014-72586 | Apr 2014 | JP |
2014-077969 | May 2014 | JP |
2014109889 | Jun 2014 | JP |
2014-124332 | Jul 2014 | JP |
2014-126600 | Jul 2014 | JP |
2014-145842 | Aug 2014 | JP |
2014-150323 | Aug 2014 | JP |
2014-222514 | Nov 2014 | JP |
2015-8001 | Jan 2015 | JP |
2015-18365 | Jan 2015 | JP |
2015-501022 | Jan 2015 | JP |
2015-41845 | Mar 2015 | JP |
2015-94848 | May 2015 | JP |
2015-519675 | Jul 2015 | JP |
2015-524974 | Aug 2015 | JP |
2015-526776 | Sep 2015 | JP |
2015-528140 | Sep 2015 | JP |
2015-528918 | Oct 2015 | JP |
2016-508007 | Mar 2016 | JP |
2016-119615 | Jun 2016 | JP |
2016-151928 | Aug 2016 | JP |
2017-19331 | Jan 2017 | JP |
10-2002-0004931 | Jan 2002 | KR |
10-2002-0064149 | Aug 2002 | KR |
10-2004-0014835 | Feb 2004 | 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-0028464 | Mar 2009 | KR |
10-2009-0030117 | Mar 2009 | KR |
10-2009-0086805 | Aug 2009 | KR |
10-0920267 | Oct 2009 | KR |
10-2009-0122944 | Dec 2009 | KR |
10-2009-0127961 | Dec 2009 | KR |
10-2009-0129192 | Dec 2009 | KR |
10-2010-0015958 | Feb 2010 | KR |
10-2010-0048571 | May 2010 | KR |
10-2010-0053149 | May 2010 | KR |
10-2010-0119519 | Nov 2010 | KR |
10-2011-0043644 | Apr 2011 | KR |
10-1032792 | May 2011 | KR |
10-2011-0068490 | Jun 2011 | KR |
10-2011-0072847 | Jun 2011 | KR |
10-2011-0086492 | Jul 2011 | KR |
10-2011-0100620 | Sep 2011 | KR |
10-2011-0113414 | Oct 2011 | KR |
10-2011-0115134 | Oct 2011 | KR |
10-2012-0020164 | Mar 2012 | KR |
10-2012-0031722 | Apr 2012 | KR |
10-1178310 | Aug 2012 | KR |
10-2012-0120316 | Nov 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-0108563 | Oct 2013 | KR |
10-1334342 | Nov 2013 | KR |
10-2013-0131252 | Dec 2013 | KR |
10-2013-0133629 | Dec 2013 | KR |
10-2014-0031283 | Mar 2014 | KR |
10-2014-0033574 | Mar 2014 | KR |
10-2014-0147557 | Dec 2014 | KR |
10-2015-0013631 | Feb 2015 | KR |
10-2015-0038375 | Apr 2015 | KR |
10-2015-0043512 | Apr 2015 | KR |
10-2016-0004351 | Jan 2016 | KR |
10-2016-0010523 | Jan 2016 | KR |
10-2016-0040279 | Apr 2016 | KR |
10-2017-0036805 | Apr 2017 | KR |
2273106 | Mar 2006 | RU |
2349970 | Mar 2009 | RU |
2353068 | Apr 2009 | RU |
2364917 | Aug 2009 | RU |
M348993 | Jan 2009 | TW |
200943903 | Oct 2009 | TW |
201018258 | May 2010 | TW |
201027515 | Jul 2010 | TW |
201028996 | Aug 2010 | TW |
201110108 | Mar 2011 | TW |
2011-42823 | Dec 2011 | TW |
201227715 | Jul 2012 | TW |
201245989 | Nov 2012 | TW |
201312548 | Mar 2013 | TW |
0014727 | Mar 2000 | WO |
0014728 | Mar 2000 | WO |
0171480 | Sep 2001 | WO |
0249253 | Jun 2002 | WO |
2005064592 | Jul 2005 | WO |
2006084144 | Aug 2006 | WO |
2007013521 | Feb 2007 | WO |
2007055766 | May 2007 | WO |
2008098900 | Aug 2008 | WO |
2008140236 | Nov 2008 | WO |
2009009240 | Jan 2009 | WO |
2009016631 | Feb 2009 | WO |
2009017280 | Feb 2009 | WO |
2009034686 | Mar 2009 | WO |
2009075912 | Jun 2009 | WO |
2009104126 | Aug 2009 | WO |
2009156438 | Dec 2009 | WO |
2009156978 | Dec 2009 | WO |
2010013369 | Feb 2010 | WO |
2010054373 | May 2010 | WO |
2010075623 | Jul 2010 | WO |
2010100937 | Sep 2010 | WO |
2010141802 | Dec 2010 | WO |
2011057346 | May 2011 | WO |
2011060106 | May 2011 | WO |
2011088053 | Jul 2011 | WO |
2011093025 | Aug 2011 | WO |
2011116309 | Sep 2011 | WO |
2011133543 | Oct 2011 | WO |
2011150730 | Dec 2011 | WO |
2011163350 | Dec 2011 | WO |
2011088053 | Jan 2012 | WO |
2012019637 | Feb 2012 | WO |
2012129231 | Sep 2012 | WO |
2012135157 | Oct 2012 | WO |
2012154317 | Nov 2012 | WO |
2012155079 | Nov 2012 | WO |
2012167168 | Dec 2012 | WO |
2013009578 | Jan 2013 | WO |
2013022135 | Feb 2013 | WO |
2013022223 | Feb 2013 | WO |
2013048880 | Apr 2013 | WO |
2013049358 | Apr 2013 | WO |
2013163113 | Oct 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 |
2014021967 | Feb 2014 | WO |
2014022148 | Feb 2014 | WO |
2014028797 | Feb 2014 | WO |
2014031505 | Feb 2014 | WO |
2014047047 | Mar 2014 | WO |
2014066352 | May 2014 | WO |
2014070872 | May 2014 | WO |
2014078965 | May 2014 | WO |
2014096506 | Jun 2014 | WO |
2014124332 | Aug 2014 | WO |
2014137074 | Sep 2014 | WO |
2014138604 | Sep 2014 | WO |
2014143959 | Sep 2014 | WO |
2014144579 | Sep 2014 | WO |
2014159581 | Oct 2014 | WO |
2014197336 | Dec 2014 | WO |
2014200728 | Dec 2014 | WO |
2014204659 | Dec 2014 | WO |
2015018440 | Feb 2015 | WO |
2015029379 | Mar 2015 | WO |
2015030796 | Mar 2015 | WO |
2015041892 | Mar 2015 | WO |
2015084659 | Jun 2015 | WO |
2015092943 | Jun 2015 | WO |
2015094169 | Jun 2015 | WO |
2015094369 | Jun 2015 | WO |
2015099939 | Jul 2015 | WO |
2015116151 | Aug 2015 | WO |
2015151133 | Oct 2015 | WO |
2015153310 | Oct 2015 | WO |
2015157013 | Oct 2015 | WO |
2015183401 | Dec 2015 | WO |
2015183699 | Dec 2015 | WO |
2015184186 | Dec 2015 | WO |
2015200207 | Dec 2015 | WO |
2016027933 | Feb 2016 | WO |
2016028946 | Feb 2016 | WO |
2016033257 | Mar 2016 | WO |
2016054230 | Apr 2016 | WO |
2016057268 | Apr 2016 | WO |
2016075081 | May 2016 | WO |
2016085775 | Jun 2016 | WO |
2016100139 | Jun 2016 | WO |
2016111881 | Jul 2016 | WO |
2016144840 | Sep 2016 | WO |
2016144982 | Sep 2016 | WO |
2016175354 | Nov 2016 | WO |
2016190950 | Dec 2016 | WO |
2016209444 | Dec 2016 | WO |
2017044260 | Mar 2017 | WO |
2017044629 | Mar 2017 | WO |
2017053311 | Mar 2017 | WO |
Entry |
---|
“Alexa, Turn Up the Heat!”, Smartthings Samsung [online], Available online at https://web.archive.org/web/20160329142041/https://blog.smartthings.com/news/smartthingsupdates/alexa-turn-up-the-heat/, Mar. 3, 2016, 3 pages. |
“Galaxy S7: How to Adjust Screen Timeout & Lock Screen Timeout”, Available online at:—“https://www.youtube.com/watch?v=n6e1WKUS2ww”, Jun. 9, 2016, 1 page. |
“Hey Google: How to Create a Shopping List with Your Google Assistant”, Available online at:—https://www.youtube.com/watch?v=w9NCsElax1Y, May 25, 2018, 1 page. |
“How to Enable Google Assistant on Galaxy 57 and other Android Phones (No Root)”, Available online at:—“https://www.youtube.com/watch?v=HeklQbWyksE”, Mar. 20, 2017, 1 page. |
“How to Use Ok Google Assistant Even Phone is Locked”, Available online at:—“https://www.youtube.com/watch?v=9B_gP4j_SP8”, Mar. 12, 2018, 1 page. |
“SmartThings +Amazon Echo”, Smartthings Samsung [online], Available online at <https://web.archive.org/web/20160509231428/https://blog.smartthings.com/featured/alexa-turn-on-my-smartthings/>, Aug. 21, 2015, 3 pages. |
“Ask Alexa—Things That Are Smart Wiki”, Available online at <URL:http://thingsthataresmart.wiki/index.php?title=Ask_Alexa&oldid=4283>, [retrieved from internet on Aug. 2, 2017], Jun. 8, 2016, pp. 1-31. |
“DIRECTV™ Voice”, Now Part of the DIRECTTV Mobile App for Phones, Sep. 18, 2013, 5 pages. |
Anania, Peter, “Amazon Echo with Home Automation (Smartthings)”, Available online at https://www.youtube.com/watch?v=LMW6aXmsWNE, Dec. 20, 2015, 1 page. |
api.ai, “Android App Review—Speaktoit Assistant”, Available at <https://www.youtube.com/watch?v=myE498nyfGw>, Mar. 30, 2011, 3 pages. |
Asakura et al., “What LG thinks; How the TV should be in the Living Room”, HiVi, vol. 31, No. 7 (Jul. 2013), Stereo Sound Publishing, Inc., Jun. 17, 2013, pp. 68-71 (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Ashbrook, Daniel L.., “Enabling Mobile Microinteractions”, Retrieved from the Internet: URL: “http://danielashbrook.com/wp-content/uploads/2012/06/2009-Ashbrook-Thesis.pdr”, May 2010, 186 pages. |
Ashingtondctech & Gaming, “SwipeStatusBar—Reveal the Status Bar in a Fullscreen App”, Online Available at: <https://www.youtube.com/watch?v=wA_tT9lAreQ>, Jul. 1, 2013, 3 pages. |
Bellegarda, Jerome, “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) 2012, May 2012, pp. 1-43. |
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 Iii Iberians Tech Workshop, Nov. 21, 2012, pp. 1-10. |
Castleos, “Whole House Voice Control Demonstration”, available online at : https://www.youtube.com/watch?v=9SRCoxrZ_W4, Jun. 2, 2012, 26 pages. |
Colt, Sam, “Here's One Way Apple's Smartwatch Could Be Better Than Anything Else”, Business Insider, Aug. 21, 2014, pp. 1-4. |
Decision to Grant received for Russian Patent Application No. 2012135502, dated Sep. 11, 2014, 15 pages (6 pages of English Translation and 9 pages of official copy). |
Decision to Grant received for Russian Patent Application No. 2012144606, dated Nov. 19, 2014, 13 pages (5 pages of English Translation and 8 pages of official copy). |
Decision to Grant received for Russian Patent Application No. 2012144639, dated Nov. 28, 2014, 10 pages (2 pages of English Translation and 8 pages of official copy). |
Decision to Grant received for Russian Patent Application No. 2012144643, dated Nov. 20, 2014, 13 pages (5 pages of English Translation and 8 pages of official copy). |
Decision to Grant received for Russian Patent Application No. 2012144647, dated Jan. 27, 2015, 16 pages (6 pages of English Translation and 10 pages of official copy). |
Decision to Grant received for Russian Patent Application No. 2012144648, dated Nov. 19, 2014, 14 pages (5 pages of English Translation and 7 pages of official copy). |
Decision to Grant received for Russian Patent Application No. 2015120954, dated Feb. 14, 2018, 20 pages (8 pages of English Translation and 12 pages of official copy). |
Deedeevuu, “Amazon Echo Alarm Feature”, Available online at https://www.youtube.com/watch?v=fdjU8eRLk7c, Feb. 16, 2015, 1 page. |
Earthling1984, “Samsung Galaxy Smart Stay Feature Explained”, Available online at:—“https://www.youtube.com/watch?v=RpjBNtSjupl”, May 29, 2013, 1 page. |
Filipowicz, Luke, “How to use the Quick Type Keyboard in iOS 8”, available online at <https://www.imore.com/comment/568232>, Oct. 11, 2014, pp. 1-17. |
Finkel et al., “Joint Parsing and Named Entity Recognition”, Human Language Technologies: The 2009 Annual Conference of the North American Chapter of the ACL, Jun. 2009, pp. 326-334. |
Gomez et al., “Mouth Gesture and Voice Command Based Robot Command Interface”, IEEE International Conference on Robotics and Automation, May 12-17, 2009, pp. 333-338. |
Google Developers, “Voice Search in Your App”, Available online at:—https://www.youtube.com/watch?v=PS1FbB5qWEI, Nov. 12, 2014, 1 page. |
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. |
Headset Button Controller v7.3 APK Full APP Download for Android, Blackberry, iPhone, Jan. 27, 2014, 11 pages. |
Hear voice from Google translate, Available on URL:https://www.youtube.com/watch?v=18AvMhFqD28, Jan. 28, 2011, 1 page. |
INews and Tech, “How to Use the QuickType Keyboard in iOS 8”, Available online at:—“http://www.inewsandtech.com/how-to-use-the-quicktype-keyboard-in-ios-8/”, Sep. 17, 2014, 6 pages. |
IOS 8 Release, “Quick Type Keyboard on iOS 8 Makes Typing Easier”, Retrieved from the Internet: URL:https://www.youtube.com/watch?v=0CidLR4fhVU, [Retrieved on Nov. 23, 2018], XP054978896, Jun. 3, 2014, 1 page. |
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. |
Karn, Ujjwal, “An Intuitive Explanation of Convolutional Neural Networks”, The Data Science Blog, Aug. 11, 2016, 23 pages. |
Kazmucha, Allyson, “How to Send Map Locations Using iMessage”, iMore.com, Available at <http://www.imore.com/how-use-imessage-share-your-location-your-iphone>, Aug. 2, 2012, 6 pages. |
Lewis, Cameron, “Task Ave for iPhone Review”, Mac Life, Available at <http://www.maclife.com/article/reviews/task_ave_iphone_review>, Mar. 3, 2011, 5 pages. |
Liou et al., “Autoencoder for Words”, Neurocomputing, vol. 139, Sep. 2014, pp. 84-96. |
Majerus, Wesley, “Cell Phone Accessibility for your Blind Child”, Retrieved from the Internet <URL:https://web.archive.org/web/20100210001100/https://nfb.org/images/nfb/publications/fr/fr28/3/fr280314.htm>, 2010, pp. 1-5. |
Marketing Land, “Amazon Echo: Play Music”, Online Available at: <https://www.youtube.com/watch?v=A7V5NPbsXi4>, Apr. 27, 2015, 3 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. |
Morrison, Jonathan, “iPhone 5 Siri Demo”, Online Available at <https://www.youtube.com/watch?v=_wHWwG5IhWc>, Sep. 21, 2012, 3 pages. |
Nakamura, Satoshi, “Overcoming the Language Barrier with Speech Translation Technology, Science & Technology Trends”, Quarterly Review No. 31, Apr. 2009, pp. 36-49. |
Nakazawa et al., “Detection and Labeling of Significant Scenes from TV program based on Twitter Analysis”, Proceedings of the 3rd Forum on Data Engineering and Information Management (deim 2011 proceedings), IEICE Data Engineering Technical Group. Available online at: http://db-event.jpn.org/deim2011/proceedings/pdf/f5-6.pdf, Feb. 28, 2011, 10 pages (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
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. |
Ng, Simon, “Google's Task List Now Comes to Iphone”, SimonBlog, Available at <http://www.simonblog.com/2009/02/04/googles-task-list-now-comes-to-iphone/>, Feb. 4, 2009, 3 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/987,982, dated Dec. 2, 2013, 18 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/394,162, dated Feb. 28, 2019, 23 pages. |
Notice of Acceptance received for Australian Patent Application No. 2017204217, dated Oct. 8, 2018, 3 pages. |
Notice of Acceptance received for Australian Patent application No. 2011205426, dated Jan. 6, 2014, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2013205568, dated May 20, 2015, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2013205569, dated Feb. 15, 2016, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2013205571, dated Jun. 1, 2015, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2013205586, dated Aug. 6, 2015, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2013205588, dated Feb. 12, 2016, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2013205590, dated May 20, 2015, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2013205591, dated Feb. 12, 2016, 2 pages. |
Notice of Acceptance received for Australian Patent application No. 2014274913, dated May 1, 2017, 3 pages. |
Notice of Acceptance received for Australian Patent application No. 2016204262, dated Dec. 22, 2017, 3 pages. |
Notice of Acceptance received for Canadian Patent application No. 2,793,118, dated May 12, 2017, 1 page. |
Notice of Acceptance received for U.S. Appl. No. 2013205584, dated Mar. 9, 2016, 2 pages. |
Notice of Allowance received for Canadian Patent Application No. 2,787,351, dathed Aug. 6, 2015, 1 page. |
Notice of Allowance received for Canadian Patent Application No. 2,791,791, dated Aug. 9, 2016, 1 page. |
Notice of Allowance received for Canadian Patent Application No. 2,792,412, dated Sep. 14, 2015, 1 page. |
Notice of Allowance received for Canadian Patent Application No. 2,792,570, dated Sep. 16, 2015, 1 page. |
Notice of Allowance received for Canadian Patent Application No. 2,793,002, dated Feb. 23, 2016, 1 page. |
Notice of Allowance received for Canadian Patent Application No. 2,793,248, dated Aug. 24, 2016, 2 pages. |
Notice of Allowance received for Canadian Patent Application No. 2,793,741, dated Sep. 16, 2015, 1 page. |
Notice of Allowance received for Canadian Patent Application No. 2,793,743, dated May 20, 2015, 1 page. |
Notice of Allowance received for Canadian Patent Application No. 2,954,559, dated Oct. 20, 2017, 1 page. |
Notice of Allowance received for Japanese Patent Application No. 2014-127579, dated Sep. 16, 2016, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Japanese Patent Application No. 2014-127580, dated Jun. 30, 2017, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Japanese Patent Application No. 2014-127582, dated Jun. 24, 2016, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Japanese Patent Application No. 2014-127583, dated May 27, 2016, 3 pages (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Japanese Patent Application No. 2014-127584, dated May 30, 2016, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Japanese Patent Application No. 2014-127585, dated Jul. 10, 2017, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Japanese Patent Application No. 2014-127586, dated May 9, 2016, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7021659, dated Jan. 20, 2016, 3 pages (1 page of English Translation and 2 pages of official copy). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7028786, dated Feb. 27, 2015, 2 pages (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7028802, dated Feb. 27, 2015, 2 pages (official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7028805, dated Aug. 28, 2015, 3 pages (1 page of English Translation and 2 pages of official copy). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7029183, dated Dec. 16, 2015, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7029195, dated May 30, 2016, 3 pages 3 pages (1 pages of English Translation and 2 pages of official copy). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7029197, dated Feb. 27, 2015, 2 pages (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7029381, dated Nov. 27, 2015, 3 pages (1 pages of English Translation and 2 pages of official copy). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7029382, dated Nov. 20, 2015, 3 pages (1 page of English Translation and 2 pages of official copy). |
Notice of Allowance received for Korean Patent Application No. 10-2012-7029385, dated Aug. 21, 2015, 3 pages (2 pages of English Translation and 1 page of official copy). |
Notice of Allowance received for Korean Patent Application No. 10-2016-7023962, dated May 31, 2017, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011794, dated Nov. 19, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011795, dated Nov. 20, 2014, 1 page (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011797, dated Nov. 20, 2014, 1 page (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011798, dated Nov. 28, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011799, dated Nov. 27, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011800, dated Feb. 9, 2016, 2 pages (English Translation only). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011803, dated Nov. 28, 2014, 1 page (Official Copy only), (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011807, dated Nov. 28, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011808, dated Jan. 23, 2015, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2015/004983, dated Dec. 16, 2015, 2 pages (1 page of English Translation and 1 page of Official copy). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2015/004983, dated Jun. 10, 2016, 1 page (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Mexican Patent Application No. MX/a/2016/011562, dated Mar. 31, 2017, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Notice of Allowance received for Russian Patent Application No. 2012144637, dated Oct. 17, 2014, 15 pages (6 pages of English Translation and 9 pages of official copy). |
Notice of Allowance received for U.S. Appl. No. 13/492,809, dated Sep. 8, 2016, 14 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,481, dated Jul. 23, 2014, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,713, dated Jan. 30, 2014, 5 pages. |
Nozawa et al., “iPhone 4S Perfect Manual”, vol. 1, First Edition, Nov. 11, 2011, 5 pages (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Australian Patent Application No. 2013205568, dated Feb. 13, 2015, 3 pages. |
Office Action received for Australian Patent application No. 2013205569, dated Feb. 16, 2015, 3 pages. |
Office Action received for Australian Patent application No. 2013205571, dated Feb. 16, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2013205584, dated Dec. 7, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2013205584, dated Feb. 18, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2013205585, dated Feb. 19, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2013205586, dated Feb. 17, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2013205588, dated Feb. 17, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2013205590, dated Feb. 16, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2013205591, dated Feb. 16, 2015, 3 pages. |
Office Action received for Australian Patent Application No. 2014274913, dated Aug. 5, 2016, 3 pages. |
Office Action received for Australian Patent Application No. 2016204262, dated Feb. 24, 2017, 3 pages. |
Office Action received for Australian Patent Application No. 2017204217, dated Feb. 12, 2018, 3 pages. |
Office Action received for Canadian Patent Application No. 2,787,351, dated May 28, 2014, 4 pages. |
Office Action received for Canadian Patent Application No. 2,791,791, dated Aug. 13, 2014, 3 pages. |
Office Action received for Canadian Patent Application No. 2,791,791, dated Aug. 25, 2015, 4 pages. |
Office Action received for Canadian Patent Application No. 2,792,412, dated Aug. 21, 2014, 3 pages. |
Office Action received for Canadian Patent Application No. 2,792,442, dated Aug. 25, 2015, 3 pages. |
Office Action received for Canadian Patent Application No. 2,792,442, dated Feb. 4, 2016, 1 page. |
Office Action received for Canadian Patent Application No. 2,792,570, dated Sep. 3, 2014, 3 pages. |
Office Action received for Canadian Patent Application No. 2,793,002, dated Sep. 3, 2014, 3 pages. |
Office Action received for Canadian Patent Application No. 2,793,002, dated Sep. 22, 2015, 3 pages. |
Office Action received for Canadian Patent Application No. 2,793,118, dated Aug. 21, 2015, 4 pages. |
Office Action received for Canadian Patent Application No. 2,793,118, dated Jul. 11, 2016, 4 pages. |
Office Action received for Canadian Patent Application No. 2,793,118, dated Mar. 19, 2015, 3 pages. |
Office Action received for Canadian Patent Application No. 2,793,248, dated Sep. 3, 2014, 3 pages. |
Office Action received for Canadian Patent Application No. 2,793,248, dated Sep. 10, 2015, 3 pages. |
Office Action received for Canadian Patent Application No. 2,793,741, dated Aug. 21, 2014, 2 pages. |
Office Action received for Canadian Patent Application No. 2,793,743, dated May 20, 2014, 4 pages. |
Office Action received for Canadian Patent Application No. 2,954,559, dated Mar. 27, 2017, 3 pages. |
Office Action received for Chinese Patent Application No. 201180013559.2, dated Feb. 28, 2015, 14 pages (8 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 201480030811.4, dated Mar. 3, 2017, 19 pages (5 pages of English Translation and 14 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 201480030811.4, dated Sep. 8, 2017, 17 pages (3 pages of English Translation and 14 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 201480030811.4, dated Sep. 30, 2018, 19 pages (5 pages of English Translation and 14 pages of Official copy). |
Office Action received for European Patent Application No. 14737370.8, dated Dec. 21, 2017, 5 pages. |
Office Action received for Indian Patent Application No. 6734/CHENP/2012, dated Oct. 30, 2018, 8 pages. |
Office Action received for Indian Patent Application No. 8902/CHENP/2012, dated Oct. 30, 2018, 6 pages. |
Office Action received for Indian Patent Application No. 8904/CHENP/2012, dated Oct. 23, 2018, 6 pages. |
Office Action received for Indian Patent Application No. 8905/CHENP/2012, dated Oct. 8, 2018, 7 pages. |
Office Action received for Indian Patent Application No. 8906/CHENP/2012, dated Oct. 24, 2018, 6 pages. |
Office Action received for Indian Patent Application No. 8907/CHENP/2012, dated Oct. 24, 2018, 6 pages. |
Office Action received for Indian Patent Application No. 8908/CHENP/2012, dated Oct. 24, 2018, 6 pages. |
Office Action received for Indian Patent Application No. 8909/CHENP/2012, dated Oct. 25, 2018, 6 pages. |
Office Action received for Indian Patent Application No. 8910/CHENP/2012, dated Oct. 25, 2018, 6 pages. |
Office Action received for Japanese Patent Application No. 2012-549003, dated Feb. 22, 2016, 15 pages (8 pages of English Translation and 7 pages of official copy). |
Office Action received for Japanese Patent Application No. 2012-549003, dated Jun. 26, 2017, 138 pages (95 pages of English Translation and 43 pages of official copy). |
Office Action received for Japanese Patent Application No. 2012-549003, dated Mar. 2, 2015, 10 pages (7 pages of English Translation and 3 pages of official copy). |
Office Action received for Japanese Patent Application No. 2012-549003, dated Oct. 21, 2016, 51 pages (30 pages of English Translation and 21 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127579, dated Apr. 4, 2016, 6 pages (3 pages of English Translation and 3 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127579, dated Sep. 14, 2015, 5 pages (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Japanese Patent Application No. 2014-127580, dated Jan. 20, 2017, 10 pages (5 pages of English Translation and 5 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127580, dated Jun. 21, 2016, 12 pages (6 pages of English Translation and 6 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127580, dated Sep. 28, 2015, 7 pages (Official copy only), (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action Action received for Japanese Patent Application No. 2014-127581, dated Aug. 31, 2015, 9 pages (5 pages of English Translation and 4 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127581, dated Jun. 24, 2016, 4 pages (2 pages of English Translation and 2 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127581, dated Nov. 24, 2016, 4 pages (2 pages of English Translation and 2 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127581, dated Oct. 2, 2017, 44 pages (24 pages of English Translation and 20 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127582, dated Aug. 31, 2015, 11 pages (6 pages of English Translation and 5 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127583, dated Sep. 7, 2015, 3 pages. (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Japanese Patent Application No. 2014-127584, dated Sep. 4, 2015, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Japanese Patent Application No. 2014-127585, dated Jul. 15, 2016, 8 pages (4 pages of English Translation and 4 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127585, dated Sep. 10, 2015, 4 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Japanese Patent Application No. 2014-127586, dated Sep. 14, 2015, 8 pages (4 pages of English Translation and 4 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127587, dated Aug. 23, 2017, 6 pages (3 pages of English Translation and 3 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127587, dated Jan. 27, 2017, 6 pages (3 pages of English Translation and 3 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127587, dated Jul. 4, 2016, 7 pages (3 pages of English Translation and 4 pages of official copy). |
Office Action received for Japanese Patent Application No. 2014-127587, dated Sep. 14, 2015, 9 pages (5 pages of English Translation and 4 pages of official copy). |
Office Action received for Japanese Patent Application No. 2017-117880, dated Sep. 29, 2017, 6 pages (3 Pages of English Translation and 3 pages of Official copy). |
Office Action received for Korean Patent Application No. 10-2012-7021659, dated Apr. 30, 2014, 8 pages (3 pages of English Translation and 5 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7021659, dated Feb. 27, 2015, 15 pages (10 pages of English Translation and 5 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7028786, dated Apr. 30, 2014, 15 pages (9 pages of English Translation and 6 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7028802, dated Apr. 30, 2014, 10 pages (4 pages of English Translation and 6 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7028805, dated Feb. 27, 2015, 14 pages (10 page of English Translation and 4 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7029183, dated Apr. 30, 2014, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2012-7029183, dated Jan. 28, 2015, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2012-7029183, dated Sep. 7, 2015, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2012-7029195, dated Apr. 30, 2014. 11 pages (5 pages of English Translation and 6 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7029195, dated Feb. 27, 2015, 16 pages (10 pages of English Translation and 6 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7029195, dated Jan. 28, 2016, 6 pages (3 pages of English Translation and 3 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7029197, dated Apr. 30, 2014, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2012-7029381, dated Apr. 30, 2014, 12 pages (5 pages of English Translation and 7 pages of official copy) |
Office Action received for Korean Patent Application No. 10-2012-7029381, dated Mar. 28, 2015, 5 pages (2 pages of English Translation and 3 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7029382, dated Apr. 30, 2014, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
Office Action Action received for Korean Patent Application No. 10-2012-7029382, dated Jan. 28, 2015, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2012-7029382, dated Jul. 31, 2015, 12 pages (9 pages of English Translation and 3 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7029385, dated Apr. 30, 2015, 13 pages (9 pages of English Translation and 4 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2012-7029385, dated Jun. 27, 2014, 13 pages (8 pages of English Translation and 5 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2015-7035370, dated Jul. 11, 2016, 12 pages (5 pages of English Translation and 7 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2015-7035370, dated May 31, 2017, 6 pages (3 pages of English Translation and 3 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2015-7035370, dated Oct. 11, 2017, 7 pages (3 pages of English Translation and 4 pages of official copy). |
Office Action received for Korean Patent Application No. 10-2016-7023962, dated Oct. 20, 2016, 5 pages (2 page of English Translation and 3 pages Official Copy). |
Office Action received for Korean Patent Application No. 10-2017-7024596, dated Feb. 22, 2018, 10 pages (4 pages of English Translation and 6 pages of official copy). |
Office Action received for Mexican Patent Application No. MX/a/2012/008369, dated Oct. 21, 2013, 6 pages (3 page of English Translation and 3 pages of official copy). |
Office Action received for Mexican Patent Application No. MX/a/2012/011794, dated Jun. 13, 2014, 2 pages (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011795, dated Feb. 19, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011795, dated Jun. 13, 2014, 2 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011797, dated Feb. 19, 2014, 1 page (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011797, dated Jun. 13, 2014, 2 pages (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011798, dated Feb. 19, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011798, dated Jun. 24, 2014, 3 pages (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011799, dated Jun. 25, 2014, 2 pages (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011800, dated Aug. 20, 2015, 9 pages (5 pages of English Translation and 4 pages of official copy). |
Office Action received for Mexican Patent Application No. MX/a/2012/011800, dated Dec. 5, 2014, 5 pages (3 pages of English Translation and 2 pages of Official copy). |
Office Action received for Mexican Patent Application No. MX/a/2012/011803, dated Feb. 19, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011803, dated Jun. 25, 2014, 2 pages (Official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011807, dated Feb. 19, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011807, dated Jun. 26, 2014, 2 pages (official copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011808, dated Feb. 19, 2014, 1 page (Official Copy only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Mexican Patent Application No. MX/a/2012/011799, dated Feb. 19, 2014, 1 page (Official Copy Only). (See Communication under 37 CFR § 1.98(a) (3)). |
Office Action received for Russian Patent Application No. 2012135502, dated Feb. 18, 2014, 8 pages (3 pages of English Translation and 5 pages of official copy). |
Office Action received for Russian Patent Application No. 2012144605, dated Mar. 26, 2014, 7 pages (3 pages of English Translation and 4 pages of official copy). |
Office Action received for Russian Patent Application No. 2012144606, dated Mar. 25, 2014, 7 pages (3 pages of English Translation and 4 pages of official copy). |
Office Action received for Russian Patent Application No. 2012144637, dated Mar. 25, 2014, 8 pages (3 pages of English Translation and 5 pages of official copy). |
Office Action received for Russian Patent Application No. 2012144640, dated Mar. 24, 2014, 9 pages (4 pages of English Translation and 5 pages of official copy). |
Office Action received for Russian Patent Application No. 2012144640, dated Nov. 28, 2014, 8 pages (3 pages of English Translation and 5 pages of official copy). |
Office Action received for Russian Patent Application No. 2012144644, dated Mar. 24, 2014, 8 pages (3 pages of English Translation and 5 pages of official copy). |
Office Action received for Russian Patent Application No. 2012144647, dated Jun. 20, 2014, 8 pages (3 pages of English Translation and 5 pages of official copy). |
Office Action received for United Kingdom Patent Application No. 1213633.9, dated Feb. 16, 2017, 5 pages. |
Office Action received for United Kingdom Patent Application No. 1213633.9, dated Sep. 28, 2017, 5 pages. |
Okuno et al., “System for Japanese Input Method based on the Internet”, Technical Report of Information Processing Society of Japan, Natural Language Processing, Japan, Information Processing Society of Japan, vol. 2009, No. 36, Mar. 18, 2009, 8 pages (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
Osxdaily, “Get a List of Siri Commands Directly from Siri”, Available at <http://osxdaily.com/2013/02/05/list-siri-cornmands/>, Feb. 5, 2013, 15 pages. |
Pan et al., “Natural Language Aided Visual Query Building for Complex Data Access”, In proceeding of: Proceedings of the Twenty-Second Conference on Innovative Applications of Artificial Intelligence, XP055114607, Jul. 11, 2010, pp. 1821-1826. |
Pathak et al,, “Privacy-preserving Speech Processing: Cryptographic and String-matching Frameworks Show Promise”, In: IEEE signal processing magazine, retrieved from <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. |
Pennington et al., “GloVe: Global Vectors for Word Representation”, Proceedings of the Conference on Empirical Methods Natural Language Processing (EMNLP), 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. |
Powell, Josh, “Now You See Me . . . Show/Hide Performance”, available at http://www.learningjquery.com/2010/05/now-you-see-me-showhide-performance, May 4, 2010, 3 pages. |
Routines, “SrnartThings Support”, Available online at <https://web.archive.org/web/20151207165701/https://support.smartthings.com/hc/en-us/articles/205380034-Routines>, 2015, 2 pages. |
Samsung Support, “Create a Qucik Command in Bixby to Launch Custom Settings by at your Command”, Retrieved from internet: https://www.facebook.com/samsungsupport/videos/10154746303151213, Nov. 13, 2017, 1 page |
Samsung, “SGH-a885 Series—Portable Quad-Band Mobile Phone-User Manual”, Retrieved from the Internet: URL: “http://web.archive.org/web/20100106113758/http://www.comparecellular.com/images/phones/userguide1896.pdf”, Jan. 1, 2009, 144 pages. |
Seehafer, Brent, “Activate google assistant on Galaxy S7 with screen off”, Available online at:—“https://productforums.google.co./forum/#!topic/websearch/Ip3qIGBHLVI”, Mar. 8, 2017, 4 pages. |
Selfrifge et al., “Interact: Tightly-coupling Multimodal Dialog with an Interactive Virtual Assistant”, International Conference on Multimodal Interaction, ACM, Nov. 9, 2015, pp. 381-382. |
Sundermeyer et al., “From Feedforward to Recurrent LSTM Neural Networks for Language Modeling”, IEEE Transactions to Audio, Speech, and Language Processing, 2015, vol. 23, Mar. 2015, pp. 517-529. |
Sundermeyer et al., “LSTM Neural Networks for Language Modeling”, Interspeech 2012, ISCA's 13 Annual Conference, Sep. 9-13, 2012, pp. 194-197. |
Tanaka, Tatsuo, “Next Generation IT Channel Strategy Through “Experience Technology””, Intellectual Resource Creation, Japan, Nomura Research Institute Ltd. vol. 19, No. 1, Dec. 20, 2010, 17 pages. (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
Vodafone Deutschland, “Samsung Galaxy S3 Tastatur Spracheingabe”, Available online at—“https://www.youtube.com/watch?v=6kOd6Gr8uFE”, Aug. 22, 2012, 1 page. |
Wikipedia, “Siri”, Available At: URL: <https:jjen.wikipedia.orgjwjindex.php?title=Siri&oldid>, Nov. 8, 2015, 13 Pages. |
Wikipedia, “Virtual Assistant”, Wikepedia, Online Available at : <https:jjen.wikipedia.orgjwjindex.php?title=Virtual assistant&oldid=679330666>, Sep. 3, 2015, 4 Pages. |
Wikipedia, “Home Automation”, Available At: https://en.wikipedia.org/w/index.php?titie= Home automation&oldid, Oct. 19, 2015, 9 Pages. |
X.AI, “How it Works”, May 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, Yuhong, “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. |
Yan et al., “A Scalable Approach to Using DNN-Derived Features in GMM-HMM Based Acoustic Modeling for LVCSR”, InInterspeech, 2013, pp. 104-108. |
Yates, Michael C., “How can I exit Google Assistant after i'm finished with it”, Available online at:—“https://productforums.google.com/forum/#lmsg/phone-by-google/faECnR2RJwA/gKNIOkQgAQAJ”, Jan. 11, 2016, 2 pages. |
Young et al., “The Hidden Information State model: A practical framework for POMDP-based spoken dialogue management”, Computer Speech & Language, vol. 24, Issue 2, 2010, pp. 150-174. |
Zangerle et al., “Recommending #-Tag in Twitter”, Proceedings of the Workshop on Semantic Adaptive Socail Web, 2011, pp. 1-12. |
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. |
Notice of Allowance received for Korean Patent Application No. 10-2017-7035711, dated Mar. 28, 2019, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
Extended European Search Report received for European Patent Application No. 19195766.1, dated Oct. 8, 2019, 15 pages. |
Notice of Acceptance received for Australian Patent Application No. 2018202411, dated Sep. 18, 2019, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2019200296, dated Sep. 5, 2019, 3 pages. |
Office Action received for Brazilian Patent Application No. 112012017826-1, dated Sep. 6, 2019, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2019-7018332, dated Sep. 10, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
“The world of Virtual Assistants—more SemTech . . . ”, End of Business as Usual—Glenn's External blog, Online Available at <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. |
Adium, “AboutAdium—Adium X—Trac”, available at <http://web.archive.org/web/20070819113247/http://trac.adiumx.com/wiki/AboutAdium>, retrieved on Nov. 25, 2011, 2 pages. |
Advisory Action received for U.S. Appl. No. 13/492,809, dated Nov. 10, 2014, 5 pages. |
Advisory Action received for U.S. Appl. No. 13/913,336, dated Feb. 20, 2018, 3 pages. |
Alfred App, “Alfred”, available at <http://www.alfredapp.com/>, retrieved on Feb. 8, 2012, 5 pages. |
Apple, “VoiceOver”, available at <http://www.apple.com/accessibility/voiceover/>, May 19, 2014, 3 pages. |
Berry et al., “PTIME: Personalized Assistance for Calendaring”, ACM Transactions on Intelligent Systems and Technology, vol. 2, No. 4, Article 40, Jul. 2011, pp. 1-22. |
Bertulucci, Jeff, “Google Adds Voice Search to Chrome Browser”, PC World, Jun. 14, 2011, 5 pages. |
Bocchieri et al., “Use of Geographical Meta-Data in ASR Language and Acoustic Models”, IEEE International Conference on Acoustics Speech and Signal Processing, 2010, pp. 5118-5121. |
Bulyko, et al, “Error-Correction Detection and Response Generation in a Spoken Dialogue System”, Speech Communication, vol. 45, 2005, pp. 271-288. |
Butcher, Mike, “EVI Arrives in Town to go Toe-to-Toe with Siri”, TechCrunch, Jan. 23, 2012, 2 pages. |
Chen, Yi, “Multimedia Siri Finds and Plays Whatever You Ask For”, PSFK Report, Feb. 9, 2012, 9 pages. |
Cheyer, Adam, “About Adam Cheyer”, available at <http://www.adam.cheyer.com/about.html>, retrieved on Sep. 17, 2012, 2 pages. |
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. |
Choi et al., “Acoustic and Visual Signal based Context Awareness System for Mobile Application”, IEEE Transactions on Consumer Electronics, vol. 57, No. 2, May 2011, pp. 738-746. |
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. |
Davis, et al, “A Personal Handheld Multi-Modal Shopping Assistant”, International Conference on Networking and Services, IEEE, 2006, 9 pages. |
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. |
Exhibit 1, “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. |
Extended European Search Report received for European Patent Application No. 11707939.2, dated Nov. 18. 2016, 13 pages. |
Extended European Search Report received for European Patent Application No. 14737370.8, dated May 19, 2016, 12 pages. |
Extended European Search Report received for European Patent Application No. 16188272.5, dated Nov. 18, 2016, 12 pages. |
Extended European Search Report received for European Patent Application No. 18202474.5, dated Feb. 12, 2019, 9 pages. |
Final Office Action received for U.S. Appl. No. 12/987,982, dated Jul. 25, 2014, 21 pages. |
Final Office Action received for U.S. Appl. No. 13/492,809, dated Feb. 9, 2016, 11 pages. |
Final Office Action received for U.S. Appl. No. 13/492,809, dated May 22, 2014, 10 pages. |
Final Office Action received for U.S. Appl. No. 13/725,481, dated Dec. 19, 2013, 16 pages. |
Final Office Action received for U.S. Appl. No. 13/725,550, dated Nov. 13, 2013, 10 pages. |
Final Office Action received for U.S. Appl. No. 13/725,616, dated Nov. 15, 2013, 8 pages. |
Final Office Action received for U.S. Appl. No. 13/725,742, dated Nov. 18, 2013, 6 pages. |
Final office action received for U.S. Appl. No. 13/725,761, dated Dec. 19, 2013, 13 pages. |
Final office action received for U.S. Appl. No. 13/725,761, dated Jul. 11, 2014, 5 pages. |
Final Office Action received for U.S. Appl. No. 13/784,707, dated Nov. 6, 2013, 12 pages. |
Final Office Action received for U.S. Appl. No. 13/913,336, dated Oct. 24, 2017, 9 pages. |
Findlater et al., “Beyond QWERTY: Augmenting Touch-Screen Keyboards with Multi-Touch Gestures for Non-Alphanumeric Input”, CHI '12, Austin, Texas, USA, May 5-10, 2012, 4 pages. |
Gannes, Liz, “Alfred App Gives Personalized Restaurant Recommendations”, AllThingsD, Jul. 18, 2011, pp. 1-3. |
Gruber, Thomas R., et al., U.S. Appl. No. 61/186,414, filed Jun. 12, 2009 titled “System and Method for Semantic Auto-Completion” 13 pages (Copy Not Attached). |
Gruber, Tom, “Big Think Small Screen: How Semantic Computing in the Cloud will Revolutionize the Consumer Experience on the Phone”, Keynote Presentation at Web 3.0 Conference, Jan. 2010, 41 pages. |
Gruber, Tom, “Siri, A Virtual Personal Assistant-Bringing Intelligence to the Interface”, Semantic Technologies Conference, Jun. 16, 2009, 21 pages. |
Guay, Matthew, “Location-Driven Productivity with Task Ave”, available at <http://iphone.appstorm.net/reviews/productivity/location-driven-productivity-with-task-ave/>, Feb. 19, 2011, 7 pages. |
Guim, Mark, “How to Set a Person-Based Reminder with Cortana”, available at <http://www.wpcentral.com/how-to-person-based-reminder-cortana>, Apr. 26, 2014, 15 pages. |
Hardwar, Devindra, “Driving App Waze Builds its own Siri for Hands-Free Voice Control”, Available online 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. |
Hayashi, et al, “Internet Information Navigation Service TITAN”, NTT Technology Journal, JPN, vol. 8, No. 8, Aug. 1996, pp. 20-23. |
id3.org, “id3v2.4.0-Frames”, available at <http://id3.org/id3V2.4.0-frames?action=print>, retrieved on Jan. 22, 2015, 41 pages. |
Interactive Voice, available at <http://www.helloivee.com/company/>, retrieved on Feb. 10, 2014, 2 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/020861, dated Aug. 2, 2012, 11 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/040961, dated Dec. 17, 2015, 20 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/020861, dated Nov. 29, 2011, 15 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/040961, dated Mar. 10, 2015, 5 pages. |
Invitation to Pay Additional Fees received for PCT Application No. PCT/US2014/040961, dated Jan. 14, 2015, 3 pages. |
Iowegian International, “FIR Filter Properties, DSPGuru, Digital Signal Processing Central”, available at <http://www.dspguru.com/dsp/faq/fir/properties> retrieved on Jul. 28, 2010, 6 pages. |
Jawaid et al., “Machine Translation with Significant Word Reordering and Rich Target-Side Morphology”, WDS'11 Proceedings of Contributed Papers, Part I, 2011, pp. 161-166. |
Jiang et al., “A Syllable-based Name Transliteration System”, Proc. of the 2009 Named Entities Workshop, Aug. 7 2009, pp. 96-99. |
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. (English Abstract submitted). |
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. (33 pages of English Translation and 10 pages of Official copy). |
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 (English Abstract Submitted). |
Kickstarter, “Ivee Sleek: Wi-Fi Voice-Activated Assistant”, available at <https://www.kickstarter.com/projects/ivee/ivee-sleek-wi-fi-voice-activated-assistant>, retrieved on Feb. 10, 2014, 13 pages. |
Komatani, Kazunori, 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. |
Meet Ivee, Your Wi-Fi Voice Activated Assistant, available 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 at <http://en.wikipedia.org/wiki/Mel_scale>, 2 pages. |
Microsoft, “Turn on and Use Magnifier”, available at <http://www.microsoft.com/windowsxp/using/accessibility/magnifierturnon.mspx>, retrieved on Jun. 6, 2009. |
Miller, Chance, “Google Keyboard Updated with New Personalized Suggestions Feature”, 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 at <http://en.wikipedia.org/wiki/Minimum_phase>, 8 pages. |
Mobile Speech Solutions, Mobile Accessibility, SVOX AG Product Information Sheet, available at <http://www.svox.com/site/bra840604/con782768/mob965831936.aSQ?osLang=1>, Sep. 27, 2012, 1 page. |
My Cool Aids, “What's New”, available at <http://www.mycoolaids.com/>, 2012, 1 page. |
Myers, Brad A., “Shortcutter for Palm”, available at <http://www.cs.cmu.edu/˜pebbles/v5/shortcutter/palm/index.html>, retrieved on Jun. 18, 2014, 10 pages. |
Naone, Erica, “TR10: Intelligent Software Assistant”, Technology Review, Mar.-Apr. 2009, 2 pages. |
Navigli, Roberto, “Word Sense Disambiguation: A Survey”, ACM Computing Surveys, vol. 41, No. 2, Feb. 2009, 69 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, dated Jul. 5, 2013, 13 pages. |
Non Final Office Action received for U.S. Appl. No. 13/725,550, dated Apr. 16, 2013, 8 pages. |
Non Final Office Action received for U.S. Appl. No. 13/725,616, dated Jun. 28, 2013, 9 pages. |
Non Final Office Action received for U.S. Appl. No. 13/725,713, dated Jul. 5, 2013, 14 pages. |
Non Final Office Action received for U.S. Appl. No. 13/725,742, dated Jun. 27, 2013, 9 pages. |
Non Final office action received for U.S. Appl. No. 13/725,761, dated Jul. 2, 2013, 12 pages. |
Non Final Office Action received for U.S. Appl. No. 13/784,694, dated May 23, 2013, 7 pages. |
Non Final Office Action received for U.S. Appl. No. 13/784,694, dated Oct. 10, 2013, 9 pages. |
Non Final Office Action received for U.S. Appl. No. 13/784,707, dated Jul. 11, 2013, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/987,982, dated Mar. 5, 2015, 24 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/987,982, dated Mar. 14, 2013, 28 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/492,809, dated Jun. 11, 2015, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/492,809, dated Mar. 7, 2013, 7 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/492,809, dated Nov. 27, 2013, 8 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/725,512 , dated Jul. 26, 2013, 14 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/725,656, dated Mar. 27, 2013, 7 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/913,336, dated Jan. 30, 2017, 17 pages. |
Non-Final Office Action received for U.S. Appl. No. 13/913,336, dated Jul. 2, 2018, 8 pages. |
Notice of Allowance received for Canadian Patent Application No. 2,954,559, dated Jun. 14, 2018, 1 page. |
Notice of Allowance received for Japanese Patent Application No. 2014-127581, dated May 21, 2018, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2014-127587, dated May 21, 2018, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2017-117880, dated Feb. 12, 2019, 4 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2017-7024596, dated Dec. 19, 2018, 4 pages. |
Notice of Allowance received for U.S. Appl. No. 12/987,982, dated Dec. 15, 2015, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,481, dated May 12, 2014, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,512, dated Dec. 17, 2013, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,550, dated Jun. 11, 2014, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,550, dated Sep. 18, 2014, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,616, dated Apr. 3, 2014, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,616, dated Jul. 17, 2014, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,656, dated Dec. 4, 2013, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,656, dated Jul. 10, 2013, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,742, dated Feb. 19, 2014, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 13/725,761, dated Apr. 10, 2015, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 13/784,694, dated Aug. 1, 2014, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 13/784,694, dated Feb. 21, 2014, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 13/784,694, dated Jun. 2, 2014, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 13/784,707, dated Feb. 20, 2014, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 13/784,707, dated Mar. 20, 2014, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 13/913,336, dated Dec. 14, 2018, 9 pages. |
Notification to Grant received for Chinese Patent Application No. 201180013559.2, dated Jan. 18, 2016, 3 pages. |
Office Action received for Australian Patent Application No. 2018202411, dated Jan. 23, 2019, 2 pages. |
Office Action received for Canadian Patent Application No. 3,000,109, dated Jan. 14, 2019, 3 pages. |
Office Action received for Chinese Patent Application No. 201480030811.4, dated Jan. 28, 2019, 11 pages. |
Office Action received for Chinese Patent Application No. 201480030811.4, dated Mar. 1, 2018, 17 pages. |
Office Action received for Chinese Patent Application No. 201610126045.2, dated May 8, 2018, 10 pages. |
Office Action received for Chinese Patent Application No. 201610126045.2, dated Nov. 12, 2018, 5 pages. |
Office Action received for European Patent Application No. 11707939.2 , dated Jan. 18, 2019, 8 pages. |
Office Action received for Indian Patent Application No. 8903/CHENP/2012, dated Aug. 9, 2018, 6 pages. |
Office Action received for Japanese Patent Application No. 2012-549003, dated Dec. 20, 2013, 3 pages. |
Office Action received for Japanese Patent Application No. 2014-127585, dated Feb. 17, 2017, 9 pages. |
Office Action received for Japanese Patent Application No. 2014-127587, dated Mar. 19, 2018, 3 pages. |
Office Action received for Japanese Patent Application No. 2017-117880, dated May 11, 2018, 9 pages. |
Office Action received for Korean Patent Application No. 10-2017-7035711, dated May 18, 2018, 14 pages. |
Phoenix Solutions, Inc., “Declaration of Christopher Schmandt Regarding the MIT Galaxy System”, West Interactive Corp., A Delaware Corporation, Document 40, Jul. 2, 2010, 162 pages. |
Reddi, “The Parser”. |
Rios, Mafe, “New bar search for Facebook”, Youtube, available at “https://www.youtube.com/watch?v=vwgN1WbvCas”, Jul. 19, 2013, 2 pages. |
Sarawagi, Sunita, “CRF Package Page”, available at <http://crf.sourceforge.net/>, retrieved on Apr. 6, 2011, 2 pages. |
Simonite, Tom, “One Easy Way to Make Siri Smarter”, Technology Review, Oct. 18, 2011, 2 pages. |
Speaker Recognition, Wikipedia, The Free Enclyclopedia, Nov. 2, 2010, 4 pages. |
Spivack, Nova, “Sneak Preview of Siri—Part Two—Technical Foundations—Interview with Tom Gruber, CTO of Siri”, Online Available at <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”, available at <http://web.archive.org/web/20090828084033/http://www.speechatsri.com/products/eduspeak>shtml, retrieved on Jun. 20, 2013, 2 pages. |
Stent et al., “Geo-Centric Language Models for Local Business Voice Search”, AT&T Labs—Research, 2009, pp. 389-396. |
Sullivan, Danny, “How Google Instant's Autocomplete Suggestions Work”, available at <http://searchengineland.com/how-google-instant-autocomplete-suggestions-work-62592>, Apr. 6, 2011, 12 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 14737370.8, dated Jan. 21, 2019, 12 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. |
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 (English Abstract submitted). |
Tatsuya, et al, “Open-Source Speech Recognition Software Julius”, Journal of Japanese Society for Artificial Intelligence, vol. 20, No. 1, Jan. 2005, p. 41-49 (Official Copy Only). |
TextnDrive, “Text'nDrive App Demo—Listen and Reply to your Messages by Voice while Driving!”, YouTube Video available at <http://www.youtube.com/watch?v=WaGfzoHsAMw>, Apr. 27, 2010, 1 page. |
Tofel, Kevin C., “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), 1998, pp. 55-58 (Official Copy). |
Tucker, Joshua, “Too Lazy to Grab Your TV Remote? Use Siri Instead”, Engadget, Nov. 30, 2011, 8 pages. |
Tur et al., “The CALO Meeting Assistant System”, IEEE Transactions on Audio, Speech and Language Processing, vol. 18, No. 6, Aug. 2010, pp. 1601-1611. |
Ushida, et al, “Spoken Dialogue Engine based on Autonomous Behavior Decision Model”, Omron Technics, vol. 40, No. 1, 2000, pp. 16-21 (Official Copy Only). |
Vlingo InCar, “Distracted Driving Solution with Vlingo InCar”, YouTube Video, Available online at <http://www.youtube.com/watch?v=Vqs8XfXxgz4>, Oct. 2010, 2 pages. |
Voiceassist, “Send Text, Listen to and Send E-Mail by Voice”, YouTube Video, Available online at <http://www.youtube.com/watch?v=0tEUe1nHHA4>, Jul. 30, 2009, 1 page. |
VoiceontheGo, “Voice on the Go (BlackBerry)”, YouTube Video, available online at <http://www.youtube.com/watch?v=pJqpWgQS98w>, Jul. 27, 2009, 1 page. |
Wikipedia, “Acoustic Model”, available at <http://en.wikipedia.org/wiki/AcousticModel>, retrieved on Sep. 14, 2011, 2 pages. |
Wikipedia, “Language Model”, available at <http://en.wikipedia.org/wiki/Language_model>, retrieved on Sep. 14, 2011, 4 pages. |
Wikipedia, “Speech Recognition”, available at <http://en.wikipedia.org/wiki/Speech_recognition>, retrieved on Sep. 14, 2011, 12 pages. |
Wilson, Mark, “New iPod Shuffle Moves Buttons to Headphones, Adds Text to Speech”, available at <http://gizmodo.com/5167946/new-ipod-shuffle-moves-buttons-to-headphones-adds-text-to-speech>, Mar. 11, 2009, 12 pages. |
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. |
Zainab, “Google Input Tools Shows Onscreen Keyboard in Multiple Languages [Chrome]”, available at <http://www.addictivetips.com/internet-tips/google-input-tools-shows-multiple-language-onscreen-keyboards-chrome/>, Jan. 3, 2012, 3 pages. |
Zhang et al., “Research of Text Classification Model Based on Latent Semantic Analysis and Improved HS-SVM”, Intelligent Systems and Applications (ISA), 2010 2nd International Workshop, May 22-23, 2010, 5 pages. |
Final Office Action received for U.S. Appl. No. 15/394,162, dated Oct. 29, 2019, 17 pages. |
Notice of Allowance received for Canadian Patent Application No. 3,000,109, dated Oct. 16, 2019, 1 page. |
Decision to Refuse received for European Patent Application No. 14737370.8, dated Jun. 26, 2019, 18 pages. |
Minutes of the Oral Proceedings received for European Patent Application No. 14737370.8, mailed on Jun. 26, 2019, 3 pages. |
Notice of Allowance received for Chinese Patent Application No. 201610126045.2, dated Jul. 16, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
Office Action received for European Patent Application No. 16188272.5, dated May 10, 2019, 8 pages. |
Office Action received for Japanese Patent Application No. 2018-050944, dated Mar. 29, 2019, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
Office Action received for Australian Patent Application No. 2019200296, dated Jul. 19, 2019, 2 pages. |
Decision on Appeal received for Korean Patent Application No. 10-2015-7035370, dated Jun. 7, 2019, 13 pages (3 pages of English Translation and 10 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2019-7007971, dated May 17, 2019, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
Notice of Allowance received for Korean Patent Application No. 10-2019-7007971, dated Dec. 26, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 15/394,162, dated Feb. 20, 2020, 6 pages. |
Office Action received for Brazilian Patent Application No. BR122012028965-5, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Brazilian Patent Application No. BR122012028966-3, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Brazilian Patent Application No. BR122012028968-0, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Brazilian Patent Application No. BR122012028969-8, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Brazilian Patent Application No. BR122012028970-1, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Brazilian Patent Application No. BR122012028971-0, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Brazilian Patent Application No. BR122012028973-6, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Brazilian Patent Application No. BR122012028974-4, dated May 27, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Number | Date | Country | |
---|---|---|---|
20190214024 A1 | Jul 2019 | US |
Number | Date | Country | |
---|---|---|---|
61657736 | Jun 2012 | US | |
61295774 | Jan 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13913336 | Jun 2013 | US |
Child | 16352410 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12987982 | Jan 2011 | US |
Child | 13913336 | US |