CN112099721A - Digital assistant user interface and response mode - Google Patents

Abstract

The present disclosure relates to digital assistant user interfaces and response modes. An exemplary process includes: receiving a user input while displaying a user interface different from the digital assistant user interface; in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of a display; and a response affordance displayed at a second portion of the display; wherein: a portion of the user interface remains visible at a third portion of the display; and the third portion is located between the first portion and the second portion.

Description

Digital assistant user interface and response mode

This application is a divisional application of the invention patent application having an application date of 16/9/2020, application number 202010977583.9, entitled "digital assistant user interface and response mode".

Technical Field

The present disclosure relates generally to intelligent automated assistants, and more particularly to user interfaces for intelligent automated assistants and the manner in which intelligent automated assistants can respond to user requests.

Background

Intelligent automated assistants (or digital assistants) may provide an advantageous interface between a human user and an electronic device. Such assistants can allow a user to interact with a device or system in speech and/or text form using natural language. For example, a user may provide a voice input containing a user request to a digital assistant that is running on an electronic device. The digital assistant can interpret the user intent from the speech input and manipulate the user intent into a task. These tasks may then be performed by executing one or more services of the electronic device, and relevant output responsive to the user request may be returned to the user.

The displayed user interface of the digital assistant can sometimes obscure (obscure) other displayed elements that may be of interest to the user. Further, the digital assistant may sometimes provide responses in a format that is undesirable to the user's current context. For example, a digital assistant may provide a displayed output when a user does not desire (or cannot) view the device display.

Disclosure of Invention

Exemplary methods are disclosed herein. An exemplary method includes, at an electronic device with a display and a touch-sensitive surface: receiving a user input while displaying a user interface different from the digital assistant user interface; in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; wherein: a portion of the user interface remains visible at a third portion of the display; and the third portion is located between the first portion and the second portion.

Example non-transitory computer readable media are disclosed herein. An example non-transitory computer readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of an electronic device with a display and a touch-sensitive surface, cause the electronic device to: receiving a user input while displaying a user interface different from the digital assistant user interface; in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; wherein: a portion of the user interface remains visible at a third portion of the display; and the third portion is located between the first portion and the second portion.

Example electronic devices are disclosed herein. An exemplary electronic device includes a display; a touch-sensitive surface; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a user input while displaying a user interface different from the digital assistant user interface; in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; wherein: a portion of the user interface remains visible at a third portion of the display; and the third portion is located between the first portion and the second portion.

An exemplary electronic device comprises means for: receiving a user input while displaying a user interface different from the digital assistant user interface; in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; wherein: a portion of the user interface remains visible at a third portion of the display; and the third portion is located between the first portion and the second portion.

Displaying a digital assistant user interface over a user interface, wherein a portion of the user interface remains visible at a portion of a display, may improve the effectiveness of the digital assistant and reduce visual interference of the digital assistant with user-device interactions. For example, information included in an underlying visible user interface may allow a user to better formulate requests to the digital assistant. As another example, displaying the user interface in such a manner can facilitate interaction between elements of the digital assistant user interface and the underlying user interface (e.g., digital assistant responses included in messages of the underlying messaging user interface). Moreover, having the digital assistant user interface and the underlying user interface co-exist on the display allows for simultaneous user interaction with both user interfaces, thereby better integrating the digital assistant into user-device interaction. In this way, the user-device interface may be more efficient (e.g., by enabling the digital assistant to more accurately and efficiently perform user-requested tasks, by reducing the visual interference of the digital assistant with the content being viewed by the user, by reducing the number of user inputs required to operate the device as desired), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

Exemplary methods are disclosed herein. An exemplary method includes, at an electronic device with a display and a touch-sensitive surface: displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface; in accordance with a determination that the user input corresponds to a first type of input: ceasing to display the digital assistant indicator and the response affordance; and in accordance with a determination that the user input corresponds to a second type of input different from the first type of input: updating the display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

Example non-transitory computer readable media are disclosed herein. An example non-transitory computer readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of an electronic device with a display and a touch-sensitive surface, cause the electronic device to: displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface; in accordance with a determination that the user input corresponds to a first type of input: ceasing to display the digital assistant indicator and the response affordance; and in accordance with a determination that the user input corresponds to a second type of input different from the first type of input: updating the display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

Example electronic devices are disclosed herein. An exemplary electronic device includes a display; a touch-sensitive surface; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface; in accordance with a determination that the user input corresponds to a first type of input: ceasing to display the digital assistant indicator and the response affordance; and in accordance with a determination that the user input corresponds to a second type of input different from the first type of input: updating the display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

An exemplary electronic device comprises means for: displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising: a digital assistant indicator displayed at a first portion of the display; and a response affordance displayed at a second portion of the display; while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface; in accordance with a determination that the user input corresponds to a first type of input: ceasing to display the digital assistant indicator and the response affordance; and in accordance with a determination that the user input corresponds to a second type of input different from the first type of input: updating the display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

Ceasing to display the digital assistant indicator and the response affordance in accordance with a determination that the user input corresponds to the first type of input may provide an intuitive and efficient way to eliminate digital assistants. For example, a user may simply provide a selection of an underlying user interface to eliminate input from the digital assistant user interface, thereby reducing interference of the digital assistant with user-device interaction. Updating the display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion provides an intuitive way for a digital assistant user interface to coexist with an underlying user interface. For example, a user may provide input selecting the underlying user interface to cause the underlying user interface to be updated as if the digital assistant user interface were not displayed. Moreover, preserving the digital assistant user interface (which may include information of interest to the user) while allowing the user to interact with the underlying user interface may reduce interference with the underlying user interface by the digital assistant. In this way, the user-device interface may be more efficient (e.g., by allowing user input to interact with the underlying user interface when displaying the digital assistant user interface, by reducing the visual interference of the digital assistant with the content being viewed by the user, by reducing the number of user inputs required to operate the device as desired), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

Exemplary methods are disclosed herein. An exemplary method includes, at an electronic device with one or more processors, memory, and a display: receiving a natural language input; initiating the digital assistant; in accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input; after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

Example non-transitory computer readable media are disclosed herein. An example non-transitory computer readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of an electronic device with a display, cause the electronic device to: receiving a natural language input; initiating the digital assistant; in accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input; after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

Example electronic devices are disclosed herein. An exemplary electronic device includes a display; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a natural language input; initiating the digital assistant; in accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input; after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

An exemplary electronic device comprises means for: receiving a natural language input; initiating the digital assistant; in accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input; after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

Presenting, by the digital assistant, the response package according to the first response mode may allow digital assistant responses to be presented in an informational manner that is appropriate for the user's current context. For example, the digital assistant may present the response in an audio format when the user's current context indicates that visual user-device interaction is not desired (or possible). As another example, the digital assistant can present the response in a visual format when the user's current context indicates that auditory user-device interaction is not desired. As another example, when the current context of the user indicates a desire for both audible and visual user-device interaction, the digital assistant can present a response having a visual component and a concise audio component, thereby reducing the length of the audio output of the digital assistant. Further, selecting the first response mode after receiving the natural language input (and before presenting the response package) may allow for more accurate determination of the user's current context (and thus more accurate determination of an appropriate response mode). In this way, the user-device interface may be more efficient and secure (e.g., by reducing visual interference of the digital assistant, by efficiently presenting responses in an informational manner, by intelligently adjusting the manner of responses based on the user's current context), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

Drawings

Fig. 1 is a block diagram illustrating a system and environment for implementing a digital assistant in accordance with various examples.

Fig. 2A is a block diagram illustrating a portable multifunction device implementing a client-side portion of a digital assistant, according to various examples.

Fig. 2B is a block diagram illustrating exemplary components for event processing according to various examples.

Fig. 3 illustrates a portable multifunction device implementing a client-side portion of a digital assistant, in accordance with various examples.

Fig. 4 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with various examples.

Fig. 5A illustrates an exemplary user interface of a menu of applications on a portable multifunction device according to various examples.

Fig. 5B illustrates an exemplary user interface of a multifunction device with a touch-sensitive surface separate from a display, in accordance with various examples.

Fig. 6A illustrates a personal electronic device, according to various examples.

Fig. 6B is a block diagram illustrating a personal electronic device, according to various examples.

Fig. 7A is a block diagram illustrating a digital assistant system or server portion thereof according to various examples.

Fig. 7B illustrates functionality of the digital assistant illustrated in fig. 7A according to various examples.

Fig. 7C illustrates a portion of an ontology according to various examples.

Fig. 8A-8 CT illustrate a user interface and a digital assistant user interface according to various examples.

Fig. 9A-9C illustrate multiple devices that determine which device should respond to a voice input according to various examples.

Fig. 10A-10V illustrate a user interface and a digital assistant user interface according to various examples.

Fig. 11 illustrates a system for selecting a digital assistant response mode and for presenting a response according to the selected digital assistant response mode, according to various examples.

Fig. 12 illustrates a device that presents responses to received natural language input according to different digital assistant response modes, according to various examples.

Fig. 13 illustrates an exemplary process implemented to select a digital assistant response mode, in accordance with various examples.

Fig. 14 illustrates a device that presents a response according to a voice response pattern when a user is determined to be in a vehicle (e.g., driving), according to various examples.

Fig. 15 illustrates a device presenting a response according to a voice response mode when the device is executing a navigation application according to various examples.

FIG. 16 illustrates a change in response pattern throughout a multi-turn DA interaction, according to various examples.

17A-17F illustrate processes for operating a digital assistant, according to various examples.

18A-18B illustrate a process for operating a digital assistant, according to various examples.

Fig. 19A-19E illustrate a process for selecting a digital assistant response mode according to various examples.

Detailed Description

In the following description of the examples, reference is made to the accompanying drawings in which are shown, by way of illustration, specific examples that may be implemented. It is to be understood that other examples may be used and structural changes may be made without departing from the scope of the various examples.

Although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first input may be referred to as a second input, and similarly, a second input may be referred to as a first input, without departing from the scope of the various described examples. The first input and the second input are both inputs, and in some cases are separate and distinct inputs.

The terminology used in the description of the various described examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various described examples and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises," "comprising," "includes," and/or "including," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Depending on the context, the term "if" may be interpreted to mean "when" ("where" or "upon") or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined." or "if [ a stated condition or event ] is detected" may be interpreted to mean "upon determining.. or" in response to determining. "or" upon detecting [ a stated condition or event ] or "in response to detecting [ a stated condition or event ]" depending on the context.

1. System and environment

Fig. 1 illustrates a block diagram of a system 100 according to various examples. In some examples, system 100 implements a digital assistant. The terms "digital assistant," "virtual assistant," "intelligent automated assistant," or "automatic digital assistant" refer to any information processing system that interprets natural language input in spoken and/or textual form to infer user intent and perform actions based on the inferred user intent. For example, to act on the inferred user intent, the system performs one or more of the following steps: identifying a task flow having steps and parameters designed to implement the inferred user intent, entering specific requirements into the task flow in accordance with the inferred user intent; executing the task flow by calling a program, a method, a service, an API, etc.; and to generate an output response to the user in audible (e.g., voice) and/or visual form.

In particular, the digital assistant is capable of accepting user requests at least partially in the form of natural language commands, requests, statements, narratives and/or inquiries. Typically, a user requests to seek an informational answer or perform a task by the digital assistant. Satisfactory responses to user requests include providing requested informational answers, performing requested tasks, or a combination of both. For example, a user presents a question to a digital assistant, such as "where do i am present? ". Based on the user's current location, the digital assistant answers "you are near the siemens of the central park. "the user also requests to perform a task, such as" please invite my friends to join my girlfriend's birthday party the next week. In response, the digital assistant can acknowledge the request by speaking "good, now" and then send an appropriate calendar invitation on behalf of the user to each of the user's friends listed in the user's electronic address book. During the performance of requested tasks, digital assistants sometimes interact with users over long periods of time in continuous conversations involving multiple exchanges of information. There are many other ways to interact with a digital assistant to request information or perform various tasks. In addition to providing verbal responses and taking programmed actions, the digital assistant also provides responses in other visual or audio forms, such as text, alerts, music, video, animation, and so forth.

As shown in fig. 1, in some examples, the digital assistant is implemented according to a client-server model. The digital assistant includes a client-side portion 102 (hereinafter "DA client 102") executing on a user device 104 and a server-side portion 106 (hereinafter "DA server 106") executing on a server system 108. The DA client 102 communicates with the DA server 106 over one or more networks 110. The DA client 102 provides client-side functionality, such as user-oriented input and output processing, as well as communicating with the DA server 106. DA server 106 provides server-side functionality for any number of DA clients 102, each located on a respective user device 104.

In some examples, DA server 106 includes a client-facing I/O interface 112, one or more processing modules 114, data and models 116, and an I/O interface 118 to external services. The client-facing I/O interface 112 facilitates client-facing input and output processing by the DA Server 106. The one or more processing modules 114 utilize the data and models 116 to process speech input and determine user intent based on natural language input. Further, the one or more processing modules 114 perform task execution based on the inferred user intent. In some examples, DA server 106 communicates with external services 120 over one or more networks 110 to complete tasks or collect information. An I/O interface 118 to external services facilitates such communication.

The user device 104 may be any suitable electronic device. In some examples, user device 104 is a portable multifunction device (e.g., device 200 described below with reference to fig. 2A), a multifunction device (e.g., device 400 described below with reference to fig. 4), or a personal electronic device (e.g., device 600 described below with reference to fig. 6A-6B). The portable multifunction device is for example a mobile phone that also contains other functions such as PDA and/or music player functions. Specific examples of portable multifunction devices include Apple from Apple Inc

iPod

And

an apparatus. Other examples of portable multifunction devices include, but are not limited to, ear/head phones, speakers, and laptop or tablet computers. Further, in some examples, user device 104 is a non-portable multifunction device. In particular, the user device 104 is a desktop computer, a game console, a speaker, a television, or a television set-top box. In some examples, the user device 104 includes a touch-sensitive surface (e.g., a touchscreen display and/or a trackpad). Further, the user device 104 optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick. Various examples of electronic devices, such as multifunction devices, are described in more detail below.

Examples of one or more communication networks 110 include a Local Area Network (LAN) and a Wide Area Network (WAN), such as the internet. The one or more communication networks 110 are implemented using any known network protocol, including various wired or wireless protocols, such as Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for Mobile communications (GSM), Enhanced Data GSM Environment (EDGE), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi, Voice over Internet protocol (VoIP), Wi-MAX, or any other suitable communication protocol.

The server system 108 is implemented on one or more stand-alone data processing devices or a distributed computer network. In some examples, the server system 108 also employs various virtual devices and/or services of third party service providers (e.g., third party cloud service providers) to provide potential computing resources and/or infrastructure resources of the server system 108.

In some examples, user device 104 communicates with DA server 106 via second user device 122. The second user device 122 is similar to or the same as the user device 104. For example, the second user equipment 122 is similar to the apparatus 200, 400, or 600 described below with reference to fig. 2A, 4, and 6A-6B. The user device 104 is configured to be communicatively coupled to the second user device 122 via a direct communication connection (such as bluetooth, NFC, BTLE, etc.) or via a wired or wireless network (such as a local area Wi-Fi network). In some examples, second user device 122 is configured to act as a proxy between user device 104 and DA server 106. For example, DA client 102 of user device 104 is configured to transmit information (e.g., a user request received at user device 104) to DA server 106 via second user device 122. DA server 106 processes the information and returns relevant data (e.g., data content in response to the user request) to user device 104 via second user device 122.

In some examples, the user device 104 is configured to send an abbreviated request for data to the second user device 122 to reduce the amount of information transmitted from the user device 104. Second user device 122 is configured to determine supplemental information to add to the abbreviated request to generate a complete request to transmit to DA server 106. The system architecture may advantageously allow a user device 104 (e.g., a watch or similar compact electronic device) with limited communication capabilities and/or limited battery power to access services provided by DA server 106 by using a second user device 122 (e.g., a mobile phone, laptop, tablet, etc.) with greater communication capabilities and/or battery power as a proxy to DA server 106. Although only two user devices 104 and 122 are shown in fig. 1, it should be understood that in some examples, system 100 may include any number and type of user devices configured to communicate with DA server system 106 in this proxy configuration.

While the digital assistant shown in fig. 1 includes both a client-side portion (e.g., DA client 102) and a server-side portion (e.g., DA server 106), in some examples, the functionality of the digital assistant is implemented as a standalone application that is installed on a user device. Moreover, the division of functionality between the client portion and the server portion of the digital assistant may vary in different implementations. For example, in some examples, the DA client is a thin client that provides only user-oriented input and output processing functions and delegates all other functions of the digital assistant to a backend server.

2. Electronic device

Attention is now directed to embodiments of an electronic device for implementing a client-side portion of a digital assistant. FIG. 2A is a block diagram illustrating a portable multifunction device 200 with a touch-sensitive display system 212 in accordance with some embodiments. The touch sensitive display 212 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to or called a "touch sensitive display system". Device 200 includes memory 202 (which optionally includes one or more computer-readable storage media), memory controller 222, one or more processing units (CPUs) 220, peripherals interface 218, RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, input/output (I/O) subsystem 206, other input control devices 216, and external ports 224. The device 200 optionally includes one or more optical sensors 264. Device 200 optionally includes one or more contact intensity sensors 265 for detecting the intensity of contacts on device 200 (e.g., a touch-sensitive surface of device 200 such as touch-sensitive display system 212). Device 200 optionally includes one or more tactile output generators 267 for generating tactile outputs on device 200 (e.g., on a touch-sensitive surface such as touch-sensitive display system 212 of device 200 or trackpad 455 of device 400). These components optionally communicate over one or more communication buses or signal lines 203.

As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (surrogate) for the force or pressure of a contact on the touch-sensitive surface. The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine the estimated contact force. Similarly, the pressure sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereof, the capacitance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof and/or the resistance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some implementations, the surrogate measurement of contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). The intensity of the contact is used as a property of the user input, allowing the user to access additional device functionality that is otherwise inaccessible to the user on smaller-sized devices with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical/mechanical controls, such as knobs or buttons).

As used in this specification and claims, the term "haptic output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to a center of mass of the device that is to be detected by a user with the user's sense of touch. For example, where a device or component of a device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other portion of a user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a haptic sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of the touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down click" or "up click" of a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click," even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement is not moving. As another example, even when there is no change in the smoothness of the touch sensitive surface, the movement of the touch sensitive surface is optionally interpreted or sensed by the user as "roughness" of the touch sensitive surface. While such interpretation of touch by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touch are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "click down," "click up," "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component thereof that would generate the sensory perception of a typical (or ordinary) user.

It should be understood that device 200 is only one example of a portable multifunction device, and that device 200 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of these components. The various components shown in fig. 2A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits.

Memory 202 includes one or more computer-readable storage media. These computer-readable storage media are, for example, tangible and non-transitory. The memory 202 comprises high-speed random access memory and also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 222 controls access to memory 202 by other components of device 200.

In some examples, the non-transitory computer-readable storage medium of memory 202 is used to store instructions (e.g., for performing aspects of the processes described below) for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In other examples, the instructions (e.g., for performing aspects of the processes described below) are stored on a non-transitory computer-readable storage medium (not shown) of the server system 108 or divided between the non-transitory computer-readable storage medium of the memory 202 and the non-transitory computer-readable storage medium of the server system 108.

Peripheral interface 218 is used to couple the input and output peripherals of the device to CPU 220 and memory 202. The one or more processors 220 execute or execute various software programs and/or sets of instructions stored in the memory 202 to perform various functions of the device 200 and to process data. In some embodiments, peripherals interface 218, CPU 220, and memory controller 222 are implemented on a single chip, such as chip 204. In some other embodiments, they are implemented on separate chips.

RF (radio frequency) circuitry 208 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 208 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 208 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF circuitry 208 optionally communicates with networks such as the internet, also known as the World Wide Web (WWW), intranets, and/or wireless networks such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), and other devices via wireless communications. The RF circuitry 208 optionally includes well-known circuitry for detecting Near Field Communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including, but not limited to, global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), evolution, data only (EV-DO), HSPA +, dual cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), wideband code division multiple access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), bluetooth low power consumption (BTLE), wireless fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over internet protocol (VoIP), Wi-MAX, email protocol (e.g., Internet Message Access Protocol (IMAP), and/or Post Office Protocol (POP))), Instant messaging (e.g., extensible messaging and presence protocol (XMPP), session initiation protocol with extensions for instant messaging and presence (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed at the filing date of this document.

Audio circuitry 210, speaker 211, and microphone 213 provide an audio interface between a user and device 200. The audio circuit 210 receives audio data from the peripheral interface 218, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 211. The speaker 211 converts the electrical signals into sound waves audible to a human. The audio circuit 210 also receives electrical signals converted from sound waves by the microphone 213. The audio circuit 210 converts the electrical signals to audio data and transmits the audio data to the peripheral interface 218 for processing. Audio data is retrieved from and/or transmitted to the memory 202 and/or RF circuitry 208 through the peripherals interface 218. In some embodiments, the audio circuit 210 also includes a headset jack (e.g., 312 in fig. 3). The headset jack provides an interface between the audio circuitry 210 and a removable audio input/output peripheral such as an output-only headset or a headset having both an output (e.g., a monaural headset or a binaural headset) and an input (e.g., a microphone).

The I/O subsystem 206 couples input/output peripheral devices on the device 200, such as the touch screen 212 and other input control devices 216, to a peripheral interface 218. The I/O subsystem 206 optionally includes a display controller 256, an optical sensor controller 258, an intensity sensor controller 259, a haptic feedback controller 261, and one or more input controllers 260 for other input or control devices. One or more input controllers 260 receive/transmit electrical signals from/to other input control devices 216. Other input control devices 216 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, input controller 260 is optionally coupled to (or not coupled to) any of: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (e.g., 308 in fig. 3) optionally include an up/down button for volume control of the speaker 211 and/or microphone 213. The one or more buttons optionally include a push button (e.g., 306 in fig. 3).

A quick push of the button disengages the lock on the touch screen 212 or begins the process of Unlocking the Device using a gesture on the touch screen, as described in U.S. patent application Ser. No. 7,657,849 entitled "Unlocking a Device by Performance on measures an Unlock Image," filed on 23.12.2005, which is hereby incorporated by reference in its entirety. Pressing the push button (e.g., 306) longer turns the device 200 on or off. The user can customize the functionality of one or more buttons. The touch screen 212 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch sensitive display 212 provides an input interface and an output interface between the device and the user. The display controller 256 receives electrical signals from the touch screen 212 and/or transmits electrical signals to the touch screen 212. Touch screen 212 displays visual output to a user. Visual output includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to a user interface object.

Touch screen 212 has a touch-sensitive surface, sensor, or group of sensors that accept input from a user based on tactile and/or haptic contact. Touch screen 212 and display controller 256 (along with any associated modules and/or sets of instructions in memory 202) detect contact (and any movement or breaking of the contact) on touch screen 212 and convert the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 212. In an exemplary embodiment, the point of contact between the touch screen 212 and the user corresponds to a finger of the user.

The touch screen 212 uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 212 and display controller 256 detect contact and any movement or breaking thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 212. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that available from Apple Inc

And iPod

The technique used in (1).

In some embodiments, the touch sensitive display of the touch screen 212 is similar to the following U.S. patents: 6,323,846(Westerman et al), 6,570,557(Westerman et al), and/or 6,677,932(Westerman) and/or the multi-touch pad described in U.S. patent publication 2002/0015024a1, which are hereby incorporated by reference in their entirety. However, touch screen 212 displays visual output from device 200, while touch sensitive trackpads do not provide visual output.

In some embodiments, the touch sensitive display of touch screen 212 is as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, entitled "Multi Touch Surface Controller", filed on 2.5.2006; (2) U.S. patent application Ser. No.10/840,862, entitled "Multipoint Touch Green," filed on 6/5/2004; (3) U.S. patent application Ser. No.10/903,964 entitled "Gestures For Touch Sensitive Input Devices" filed on 30.7.2004; (4) U.S. patent application Ser. No.11/048,264 entitled "Gestures For Touch Sensitive Input Devices" filed on 31/1/2005; (5) U.S. patent application Ser. No.11/038,590 entitled "model-Based Graphical User Interfaces For Touch Sensitive Input Devices", filed on 18.1.2005; (6) U.S. patent application Ser. No.11/228,758, entitled "Virtual Input Device plan On A Touch Screen User Interface," filed On 16.9.2005; (7) U.S. patent application Ser. No.11/228,700 entitled "Operation Of A Computer With A Touch Screen Interface," filed on 16.9.2005; (8) U.S. patent application Ser. No.11/228,737 entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keys" filed on 16.9.2005; and (9) U.S. patent application Ser. No.11/367,749 entitled "Multi-Functional Hand-Held Device" filed 3/2006. All of these applications are incorporated herein by reference in their entirety.

The touch screen 212 has, for example, a video resolution of over 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user makes contact with the touch screen 212 using any suitable object or appendage, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the action desired by the user.

In some embodiments, in addition to a touch screen, device 200 includes a touch pad (not shown) for activating or deactivating particular functions. In some embodiments, the trackpad is a touch-sensitive area of the device that, unlike a touchscreen, does not display visual output. The trackpad is a touch-sensitive surface separate from the touch screen 212 or an extension of the touch-sensitive surface formed by the touch screen.

The device 200 also includes a power system 262 for powering the various components. Power system 262 includes a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a Light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

The device 200 also includes one or more optical sensors 264. Fig. 2A shows an optical sensor coupled to optical sensor controller 258 in I/O subsystem 206. The optical sensor 264 includes a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 264 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 243 (also called a camera module), the optical sensor 264 captures still images or video. In some embodiments, the optical sensor is located at the rear of the device 200, opposite the touch screen display 212 at the front of the device, such that the touch screen display is used as a viewfinder for still and/or video image acquisition. In some embodiments, the optical sensor is located in the front of the device so that images of the user are acquired for the video conference while the user views other video conference participants on the touch screen display. In some implementations, the position of the optical sensor 264 can be changed by the user (e.g., by rotating a lens and sensor in the device housing) such that a single optical sensor 264 is used with a touch screen display for both video conferencing and still image and/or video image capture.

Device 200 optionally further comprises one or more contact intensity sensors 265. FIG. 2A shows a contact intensity sensor coupled to intensity sensor controller 259 in I/O subsystem 206. Contact intensity sensor 265 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 265 receives contact intensity information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed or adjacent to the touch-sensitive surface (e.g., touch-sensitive display system 212). In some embodiments, at least one contact intensity sensor is located on the back of device 200, opposite touch screen display 212, which is located on the front of device 200.

The device 200 also includes one or more proximity sensors 266. Fig. 2A shows a proximity sensor 266 coupled to the peripheral interface 218. Alternatively, the proximity sensor 266 is coupled to the input controller 260 in the I/O subsystem 206. The proximity sensor 266 performs as described in the following U.S. patent applications: 11/241,839 entitled "Proximaty Detector In Handheld Device"; no.11/240,788, entitled "Proximaty Detector In Handheld Device"; no.11/620,702, entitled "Using Ambient Light Sensor To augmentation Proximaty Sensor Output"; no.11/586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and U.S. patent application Ser. No.11/638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals," which is hereby incorporated by reference in its entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 212 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 200 optionally further comprises one or more tactile output generators 267. Fig. 2A shows a tactile output generator coupled to a tactile feedback controller 261 in the I/O subsystem 206. Tactile output generator 267 optionally includes one or more electro-acoustic devices such as speakers or other audio components; and/or an electromechanical device such as a motor, solenoid, electroactive aggregator, piezoelectric actuator, electrostatic actuator, or other tactile output generating component for converting energy into linear motion (e.g., a component for converting an electrical signal into a tactile output on the device). Contact intensity sensor 265 receives haptic feedback generation instructions from haptic feedback module 233 and generates haptic output on device 200 that can be felt by a user of device 200. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 212), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., into/out of the surface of device 200) or laterally (e.g., back and forth in the same plane as the surface of device 200). In some embodiments, at least one tactile output generator sensor is located on the back of device 200, opposite touch screen display 212, which is located on the front of device 200.

The device 200 also includes one or more accelerometers 268. Fig. 2A shows accelerometer 268 coupled to peripherals interface 218. Alternatively, accelerometer 268 is coupled to input controller 260 in I/O subsystem 206. Accelerometer 268 performs as described in the following U.S. patent publications: U.S. patent publication 20050190059, "accumulation-Based Detection System For Portable Electronic Devices" And U.S. patent publication 20060017692, "Methods And applications For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from one or more accelerometers. Device 200 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the one or more accelerometers 268 for obtaining information about the position and orientation (e.g., portrait or landscape) of device 200.

In some embodiments, the software components stored in memory 202 include an operating system 226, a communication module (or set of instructions) 228, a contact/motion module (or set of instructions) 230, a graphics module (or set of instructions) 232, a text input module (or set of instructions) 234, a Global Positioning System (GPS) module (or set of instructions) 235, a digital assistant client module 229, and an application program (or set of instructions) 236. In addition, memory 202 stores data and models, such as user data and models 231. Further, in some embodiments, memory 202 (fig. 2A) or 470 (fig. 4) stores device/global internal state 257, as shown in fig. 2A and 4. Device/global internal state 257 includes one or more of: an active application state indicating which applications (if any) are currently active; a display state indicating what applications, views, or other information occupy various areas of the touch screen display 212; sensor status, including information obtained from the various sensors of the device and the input control device 216; and location information regarding the location and/or pose of the device.

The operating system 226 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

The communication module 228 facilitates communication with other devices via the one or more external ports 224 and also includes various software components for processing data received by the RF circuitry 208 and/or the external ports 224. External port 224 (e.g., Universal Serial Bus (USB), firewire, etc.) is adapted to couple directly to other devices or indirectly through a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is an external port

(trademark of Apple inc.) a multi-pin (e.g., 30-pin) connector that is the same as or similar to and/or compatible with the 30-pin connector used on the device.

The contact/motion module 230 optionally detects contact with the touch screen 212 (in conjunction with the display controller 256) and other touch sensitive devices (e.g., a trackpad or a physical click wheel). The contact/motion module 230 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger-down event), determining contact intensity (e.g., force or pressure of contact, or a substitute for force or pressure of contact), determining whether there is movement of contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining whether contact has ceased (e.g., detecting a finger-up event or a contact-break). The contact/motion module 230 receives contact data from the touch-sensitive surface. Determining movement of the point of contact optionally includes determining velocity (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the point of contact, the movement of the point of contact being represented by a series of contact data. These operations are optionally applied to single point contacts (e.g., single finger contacts) or multiple point simultaneous contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, the contact/motion module 230 and the display controller 256 detect contact on a touch pad.

In some embodiments, the contact/motion module 230 uses a set of one or more intensity thresholds to determine whether an operation has been performed by the user (e.g., determine whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds are determined as a function of software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and may be adjusted without changing the physical hardware of device 200). For example, the mouse "click" threshold of the trackpad or touchscreen can be set to any one of a wide range of predefined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more intensity thresholds of a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting multiple intensity thresholds at once with a system-level click on an "intensity" parameter).

The contact/motion module 230 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, the gesture is optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event, and then detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at the location of the icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event, then detecting one or more finger-dragging events, and then subsequently detecting a finger-up (lift-off) event.

Graphics module 232 includes various known software components for rendering and displaying graphics on touch screen 212 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphic" includes any object that may be displayed to a user, including without limitation text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations and the like.

In some embodiments, graphics module 232 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 232 receives one or more codes specifying graphics to be displayed from an application program or the like, and also receives coordinate data and other graphics attribute data together if necessary, and then generates screen image data to output to the display controller 256.

Haptic feedback module 233 includes various software components for generating instructions for use by one or more haptic output generators 267 to produce haptic outputs at one or more locations on device 200 in response to user interaction with device 200.

Text input module 234, which in some examples is a component of graphics module 232, provides a soft keyboard for entering text in various applications (e.g., contacts 237, email 240, IM 241, browser 247, and any other application that requires text input).

The GPS module 235 determines the location of the device and provides this information for use in various applications (e.g., to the phone 238 for use in location-based dialing; to the camera 243 as picture/video metadata; and to applications that provide location-based services, such as weather desktop applets, local yellow pages desktop applets, and map/navigation desktop applets).

The digital assistant client module 229 includes various client side digital assistant instructions to provide client side functionality of the digital assistant. For example, the digital assistant client module 229 can accept voice (voice) input (e.g., speech (speech) input), text input, touch input, and/or gesture input through various user interfaces of the portable multifunction device 200 (e.g., the microphone 213, the one or more accelerometers 268, the touch-sensitive display system 212, the one or more optical sensors 264, the other input control device 216, etc.). The digital assistant client module 229 can also provide output in audio form (e.g., speech output), visual form, and/or tactile form through various output interfaces of the portable multifunction device 200 (e.g., the speaker 211, the touch-sensitive display system 212, the one or more tactile output generators 267, etc.). For example, the output is provided as voice, sound, alarm, text message, menu, graphic, video, animation, vibration, and/or a combination of two or more of the foregoing. During operation, digital assistant client module 229 communicates with DA server 106 using RF circuitry 208.

The user data and model 231 includes various data associated with the user (e.g., user-specific vocabulary data, user preference data, user-specified name pronunciations, data from the user's electronic address book, backlogs, shopping lists, etc.) to provide client-side functionality of the digital assistant. Further, the user data and models 231 include various models (e.g., speech recognition models, statistical language models, natural language processing models, ontologies, task flow models, service models, etc.) for processing user input and determining user intent.

In some examples, the digital assistant client module 229 utilizes various sensors, subsystems, and peripherals of the portable multifunction device 200 to gather additional information from the surroundings of the portable multifunction device 200 to establish a context associated with the user, the current user interaction, and/or the current user input. In some examples, the digital assistant client module 229 provides the context information, or a subset thereof, along with the user input to the DA server 106 to help infer the user intent. In some examples, the digital assistant also uses the contextual information to determine how to prepare and communicate the output to the user. The context information is referred to as context data.

In some examples, contextual information accompanying the user input includes sensor information, such as lighting, ambient noise, ambient temperature, images or video of the surrounding environment, and the like. In some examples, the context information may also include physical states of the device, such as device orientation, device location, device temperature, power level, velocity, acceleration, motion pattern, cellular signal strength, and the like. In some examples, information related to the software state of the DA server 106, such as the running process of the portable multifunction device 200, installed programs, past and current network activities, background services, error logs, resource usage, etc., is provided to the DA server 106 as contextual information associated with the user input.

In some examples, the digital assistant client module 229 selectively provides information (e.g., user data 231) stored on the portable multifunction device 200 in response to a request from the DA server 106. In some examples, the digital assistant client module 229 also elicits additional input from the user via a natural language dialog or other user interface upon request by the DA server 106. The digital assistant client module 229 communicates this additional input to the DA server 106 to assist the DA server 106 in intent inference and/or to implement the user intent expressed in the user request.

The digital assistant is described in more detail below with reference to fig. 7A-7C. It should be appreciated that the digital assistant client module 229 may include any number of sub-modules of the digital assistant module 726 described below.

The application programs 236 include the following modules (or sets of instructions), or a subset or superset thereof:

a contacts module 237 (sometimes referred to as a contact list or contact list);

a phone module 238;

a video conferencing module 239;

an email client module 240;

an Instant Messaging (IM) module 241;

fitness support module 242;

a camera module 243 for still and/or video images;

an image management module 244;

a video player module;

a music player module;

a browser module 247;

a calendar module 248;

desktop applet modules 249, which in some examples include one or more of the following: a weather desktop applet 249-1, a stock market desktop applet 249-2, a calculator desktop applet 249-3, an alarm desktop applet 249-4, a dictionary desktop applet 249-5, and other desktop applets acquired by the user and a desktop applet 249-6 created by the user;

a desktop applet creator module 250 for forming a user-created desktop applet 249-6;

A search module 251;

a video and music player module 252 that incorporates a video player module and a music player module;

a notepad module 253;

a map module 254; and/or

Online video module 255.

Examples of other application programs 236 stored in memory 202 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the contacts module 237 is used to manage contact lists or contact lists (e.g., stored in the application internal state 292 of the contacts module 237 in the memory 202 or the memory 470), including: adding one or more names to the address book; deleting names from the address book; associating a phone number, email address, physical address, or other information with a name; associating the image with a name; classifying and classifying names; providing a telephone number or email address to initiate and/or facilitate communications through the telephone 238, video conferencing module 239, email 240, or IM 241; and so on.

In conjunction with the RF circuitry 208, the audio circuitry 210, the speaker 211, the microphone 213, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the phone module 238 is operable to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in the contacts module 237, modify an already entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, wireless communication uses any of a variety of communication standards, protocols, and technologies.

In conjunction with the RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, touch screen 212, display controller 256, optical sensor 264, optical sensor controller 258, contact/motion module 230, graphics module 232, text input module 234, contacts module 237, and phone module 238, the video conference module 239 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants according to user instructions.

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, and text input module 234, email client module 240 includes executable instructions to create, send, receive, and manage emails in response to user instructions. In conjunction with the image management module 244, the e-mail client module 240 makes it very easy to create and send an e-mail having a still image or a video image photographed by the camera module 243.

In conjunction with the RF circuitry 208, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the instant message module 241 includes executable instructions for: inputting a sequence of characters corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for a phone-based instant message or using XMPP, SIMPLE, or IMPS for an internet-based instant message), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant messages include graphics, photos, audio files, video files, and/or other attachments as supported in MMS and/or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, text input module 234, GPS module 235, map module 254, and music player module, fitness support module 242 includes executable instructions for: creating fitness (e.g., having time, distance, and/or calorie burning goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

In conjunction with the touch screen 212, the display controller 256, the one or more optical sensors 264, the optical sensor controller 258, the contact/motion module 230, the graphics module 232, and the image management module 244, the camera module 243 includes executable instructions for: capturing still images or video (including video streams) and storing them in the memory 202, modifying features of the still images or video, or deleting the still images or video from the memory 202.

In conjunction with the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, the text input module 234, and the camera module 243, the image management module 244 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide or album), and storing still and/or video images.

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, and text input module 234, browser module 247 includes executable instructions for browsing the internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with the RF circuitry 208, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, the text input module 234, the email client module 240, and the browser module 247, the calendar module 248 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do items, etc.) according to user instructions.

In conjunction with the RF circuitry 208, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, the text input module 234, and the browser module 247, the desktop applet module 249 is a mini-application (e.g., a weather desktop applet 249-1, a stock desktop applet 249-2, a calculator desktop applet 249-3, an alarm desktop applet 249-4, and a dictionary desktop applet 249-5) or a mini-application created by a user (e.g., a user-created desktop applet 249-6) that may be downloaded and used by the user. In some embodiments, the desktop applet includes an HTML (hypertext markup language) file, a CSS (cascading style sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (extensible markup language) file and a JavaScript file (e.g., Yahoo! desktop applet).

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, text input module 234, and browser module 247, desktop applet creator module 250 is used by a user to create a desktop applet (e.g., to change a user-specified portion of a web page into a desktop applet).

In conjunction with touch screen 212, display controller 256, contact/motion module 230, graphics module 232, and text input module 234, search module 251 includes executable instructions for searching memory 202 for text, music, sound, images, videos, and/or other files that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

In conjunction with the touch screen 212, display controller 256, contact/motion module 230, graphics module 232, audio circuitry 210, speakers 211, RF circuitry 208, and browser module 247, the video and music player module 252 includes executable instructions that allow a user to download and playback recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, rendering, or otherwise playing back video (e.g., on the touch screen 212 or on an external display connected via the external port 224). In some embodiments, the device 200 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple inc.).

In conjunction with the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the notepad module 253 includes executable instructions to create and manage notepads, backlogs, and the like according to user instructions.

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, text input module 234, GPS module 235, and browser module 247, map module 254 is used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data related to stores and other points of interest at or near a particular location, and other location-based data) according to user instructions.

In conjunction with touch screen 212, display controller 256, contact/motion module 230, graphics module 232, audio circuit 210, speaker 211, RF circuit 208, text input module 234, email client module 240, and browser module 247, online video module 255 includes instructions that allow a user to access, browse, receive (e.g., by streaming and/or downloading), playback (e.g., on the touch screen or on a connected external display via external port 224), send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as h.264. In some embodiments, the link to a particular online video is sent using instant messaging module 241 instead of email client module 240. Additional description of Online video applications can be found in U.S. provisional patent application Ser. No.60/936,562 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video," filed on day 6/20 of 2007 and U.S. patent application Ser. No.11/968,067 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video," filed on day 12/31 of 2007, the contents of both of which are hereby incorporated by reference in their entirety.

Each of the modules and applications described above corresponds to a set of executable instructions for performing one or more of the functions described above as well as the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, a video player module may be combined with a music player module into a single module (e.g., video and music player module 252 in fig. 2A). In some embodiments, memory 202 stores a subset of the modules and data structures described above. In addition, memory 202 stores additional modules and data structures not described above.

In some embodiments, device 200 is a device on which the operation of a predefined set of functions is performed exclusively through a touch screen and/or a trackpad. By using a touch screen and/or touch pad as the primary input control device for operation of the device 200, the number of physical input control devices (such as push buttons, dials, etc.) on the device 200 is reduced.

The predefined set of functions performed exclusively through the touchscreen and/or trackpad optionally includes navigation between user interfaces. In some embodiments, the trackpad, when touched by a user, navigates device 200 from any user interface displayed on device 200 to a main, home, or root menu. In such embodiments, a "menu button" is implemented using a touch pad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

Fig. 2B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 202 (fig. 2A) or memory 470 (fig. 4) includes event classifier 270 (e.g., in operating system 226) and corresponding application 236-1 (e.g., any of the aforementioned applications 237 through 251, 255, 480 through 490).

The event sorter 270 receives the event information and determines the application 236-1 to which the event information is to be delivered and the application view 291 of the application 236-1. The event sorter 270 includes an event monitor 271 and an event dispatcher module 274. In some embodiments, the application 236-1 includes an application internal state 292 that indicates one or more current application views that are displayed on the touch-sensitive display 212 when the application is active or executing. In some embodiments, device/global internal state 257 is used by event classifier 270 to determine which application(s) are currently active, and application internal state 292 is used by event classifier 270 to determine the application view 291 to which to deliver event information.

In some embodiments, the application internal state 292 includes additional information, such as one or more of the following: resume information to be used when the application 236-1 resumes execution, user interface state information indicating that information is being displayed or is ready for display by the application 236-1, a state queue for enabling a user to return to a previous state or view of the application 236-1, and a repeat/undo queue of previous actions taken by the user.

The event monitor 271 receives event information from the peripheral interface 218. The event information includes information about a sub-event (e.g., a user touch on the touch-sensitive display 212 as part of a multi-touch gesture). Peripherals interface 218 transmits information it receives from I/O subsystem 206 or sensors such as proximity sensor 266, one or more accelerometers 268, and/or microphone 213 (through audio circuitry 210). Information received by peripheral interface 218 from I/O subsystem 206 includes information from touch-sensitive display 212 or a touch-sensitive surface.

In some embodiments, event monitor 271 sends requests to peripheral interface 218 at predetermined intervals. In response, peripheral interface 218 transmits event information. In other embodiments, peripheral interface 218 transmits event information only when there is a significant event (e.g., receiving input above a predetermined noise threshold and/or receiving input for more than a predetermined duration).

In some embodiments, event classifier 270 also includes hit view determination module 272 and/or activity event recognizer determination module 273.

When the touch-sensitive display 212 displays more than one view, the hit view determination module 272 provides a software process for determining where within one or more views a sub-event has occurred. The view consists of controls and other elements that the user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected corresponds to a programmatic hierarchy of applications or a programmatic level within the view hierarchy. For example, the lowest level view in which a touch is detected is referred to as the hit view, and the set of events considered to be correct inputs is determined based at least in part on the hit view of the initial touch that initiated the touch-based gesture.

Hit view determination module 272 receives information related to sub-events of the touch-based gesture. When the application has multiple views organized in a hierarchy, hit view determination module 272 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in the sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by hit view determination module 272, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

The activity event identifier determination module 273 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some implementations, the activity event recognizer determination module 273 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 273 determines that all views including the physical location of the sub-event are actively participating views, and thus determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, the higher views in the hierarchy will remain actively participating views.

Event dispatcher module 274 dispatches event information to event recognizers (e.g., event recognizer 280). In embodiments that include the activity event recognizer determination module 273, the event dispatcher module 274 delivers the event information to the event recognizer determined by the activity event recognizer determination module 273. In some embodiments, the event dispatcher module 274 stores event information in an event queue, which is retrieved by the respective event receiver 282.

In some embodiments, the operating system 226 includes an event classifier 270. Alternatively, the application 236-1 includes an event classifier 270. In yet another embodiment, the event classifier 270 is a stand-alone module or is part of another module stored in the memory 202 (such as the contact/motion module 230).

In some embodiments, the application 236-1 includes a plurality of event handlers 290 and one or more application views 291, each of which includes instructions for handling touch events occurring within a respective view of the application's user interface. Each application view 291 of the application 236-1 includes one or more event recognizers 280. Typically, the respective application view 291 includes a plurality of event recognizers 280. In other embodiments, one or more of the event recognizers 280 are part of a separate module that is a higher-level object such as a user interface toolkit (not shown) or the application 236-1 that inherits methods and other properties from it. In some embodiments, the respective event handlers 290 include one or more of: data updater 276, object updater 277, GUI updater 278, and/or event data 279 received from event classifier 270. Event handler 290 updates application internal state 292 with or calls data updater 276, object updater 277 or GUI updater 278. Alternatively, one or more of the application views 291 include one or more respective event handlers 290. Additionally, in some embodiments, one or more of the data updater 276, the object updater 277, and the GUI updater 278 are included in a respective application view 291.

The corresponding event identifier 280 receives event information (e.g., event data 279) from the event classifier 270 and identifies events from the event information. Event recognizer 280 includes an event receiver 282 and an event comparator 284. In some embodiments, event recognizer 280 also includes metadata 283 and at least a subset of event delivery instructions 288 (which include sub-event delivery instructions).

Event receiver 282 receives event information from event sorter 270. The event information includes information about a sub-event such as a touch or touch movement. According to the sub-event, the event information further includes additional information, such as the location of the sub-event. When the sub-event relates to the motion of a touch, the event information also includes the velocity and direction of the sub-event. In some embodiments, the event comprises rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information comprises corresponding information about the current orientation of the device (also referred to as the device pose).

Event comparator 284 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event or determines or updates the state of an event or sub-event. In some embodiments, event comparator 284 includes an event definition 286. The event definition 286 contains definitions of events (e.g., predefined sub-event sequences), such as event 1(287-1), event 2(287-2), and other events. In some embodiments, sub-events in event (287) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1(287-1) is a double click on the displayed object. For example, a double tap includes a first touch on the displayed object for a predetermined length of time (touch start), a first lift off for a predetermined length of time (touch end), a second touch on the displayed object for a predetermined length of time (touch start), and a second lift off for a predetermined length of time (touch end). In another example, the definition of event 2(287-2) is a drag on the displayed object. For example, the drag includes a predetermined length of time of touch (or contact) on the displayed object, movement of the touch on the touch-sensitive display 212, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 290.

In some embodiments, the event definitions 287 include definitions of events for respective user interface objects. In some embodiments, event comparator 284 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view that displays three user interface objects on the touch-sensitive display 212, when a touch is detected on the touch-sensitive display 212, the event comparator 284 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 290, the event comparator uses the results of the hit test to determine which event handler 290 should be activated. For example, the event comparator 284 selects the event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, the definition of the respective event (287) further comprises a delay action that delays the delivery of the event information until it has been determined that the sequence of sub-events does or does not correspond to the event type of the event recognizer.

When the respective event recognizer 280 determines that the sequence of sub-events does not match any event in the event definition 286, the respective event recognizer 280 enters an event not possible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, the respective event recognizer 280 includes metadata 283 with configurable attributes, tags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 283 includes configurable attributes, flags, and/or lists that indicate how or how event recognizers interact with each other. In some embodiments, metadata 283 includes configurable attributes, flags, and/or lists that indicate whether a sub-event is delivered to different levels in a view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the respective event identifier 280 activates the event handler 290 associated with the event. In some embodiments, the respective event identifier 280 delivers event information associated with the event to the event handler 290. Activating the event handler 290 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, event recognizer 280 throws a marker associated with the recognized event, and event handler 290 associated with the marker retrieves the marker and performs a predefined process.

In some embodiments, the event delivery instructions 288 include sub-event delivery instructions that deliver event information about sub-events without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the sequence of sub-events or to actively participating views. Event handlers associated with the sequence of sub-events or with actively participating views receive the event information and perform a predetermined process.

In some embodiments, the data updater 276 creates and updates data used in the application 236-1. For example, the data updater 276 updates a phone number used in the contacts module 237 or stores a video file used in the video player module. In some embodiments, the object updater 277 creates and updates objects used in the application 236-1. For example, object updater 277 creates a new user interface object or updates the location of a user interface object. The GUI updater 278 updates the GUI. For example, GUI updater 278 prepares display information and sends the display information to graphics module 232 for display on the touch-sensitive display.

In some embodiments, event handler 290 includes or has access to data updater 276, object updater 277, and GUI updater 278. In some embodiments, the data updater 276, the object updater 277, and the GUI updater 278 are included in a single module of the respective application 236-1 or application view 291. In other embodiments, they are included in two or more software modules.

It should be understood that the above discussion of event processing with respect to user touches on a touch sensitive display also applies to other forms of user input utilizing an input device to operate multifunction device 200, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds; contact movements on the touchpad, such as tapping, dragging, scrolling, etc.; inputting by a stylus; movement of the device; verbal instructions; detected eye movement; inputting biological characteristics; and/or any combination thereof, is optionally used as input corresponding to sub-events defining the event to be identified.

Fig. 3 illustrates a portable multifunction device 200 with a touch screen 212 in accordance with some embodiments. The touch screen optionally displays one or more graphics within a User Interface (UI) 300. In this embodiment, as well as others described below, a user can select one or more of these graphics by making gestures on the graphics, for example, with one or more fingers 302 (not drawn to scale in the figure) or one or more styluses 303 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics will occur when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up, and/or down), and/or a rolling of a finger (right to left, left to right, up, and/or down) that has made contact with device 200. In some implementations, or in some cases, inadvertent contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

The device 200 also includes one or more physical buttons, such as a "home" or menu button 304. As previously described, the menu button 304 is used to navigate to any application 236 in a set of applications executing on the device 200. Alternatively, in some embodiments, the menu buttons are implemented as soft keys in a GUI displayed on touch screen 212.

In some embodiments, device 200 includes a touch screen 212, menu buttons 304, a push button 306 for powering the device on/off and for locking the device, one or more volume adjustment buttons 308, a Subscriber Identity Module (SIM) card slot 310, a headset jack 312, and a docking/charging external port 224. Pressing the button 306 optionally serves to turn the device on/off by pressing the button and holding the button in a pressed state for a predefined time interval; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlocking the device or initiating an unlocking process. In an alternative embodiment, device 200 also accepts verbal input through microphone 213 for activating or deactivating certain functions. Device 200 also optionally includes one or more contact intensity sensors 265 for detecting the intensity of contacts on touch screen 212, and/or one or more tactile output generators 267 for generating tactile outputs for a user of device 200.

Fig. 4 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 400 need not be portable. In some embodiments, the device 400 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a child learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 400 typically includes one or more processing units (CPUs) 410, one or more network or other communication interfaces 460, memory 470, and one or more communication buses 420 for interconnecting these components. The communication bus 420 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 400 includes an input/output (I/O) interface 430 with a display 440, which is typically a touch screen display. The I/O interface 430 also optionally includes a keyboard and/or mouse (or other pointing device) 450 and a trackpad 455, a tactile output generator 457 (e.g., similar to one or more tactile output generators 267 described above with reference to fig. 2A), a sensor 459 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch-sensitive sensor, and/or a contact intensity sensor (similar to one or more contact intensity sensors 265 described above with reference to fig. 2A)) for generating tactile outputs on the device 400. Memory 470 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 470 optionally includes one or more storage devices located remotely from CPU 410. In some embodiments, memory 470 stores programs, modules, and data structures similar to or a subset of the programs, modules, and data structures stored in memory 202 of portable multifunction device 200 (fig. 2A). In addition, memory 470 optionally stores additional programs, modules, and data structures not present in memory 202 of portable multifunction device 200. For example, memory 470 of device 400 optionally stores drawing module 480, presentation module 482, word processing module 484, website creation module 486, disk editing module 488, and/or spreadsheet module 490, while memory 202 of portable multifunction device 200 (FIG. 2A) optionally does not store these modules.

Each of the above-described elements in fig. 4 is stored in one or more of the previously mentioned memory devices in some examples. Each of the above modules corresponds to a set of instructions for performing a function described above. The modules or programs (e.g., sets of instructions) described above need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory 470 stores a subset of the modules and data structures described above. In addition, memory 470 stores additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces that may be implemented on, for example, portable multifunction device 200.

Fig. 5A illustrates an exemplary user interface of an application menu on a portable multifunction device 200 according to some embodiments. A similar user interface is implemented on the device 400. In some embodiments, the user interface 500 includes the following elements, or a subset or superset thereof:

one or more signal strength indicators 502 of one or more wireless communications, such as cellular signals and Wi-Fi signals;

time 504;

A bluetooth indicator 505;

a battery status indicator 506;

tray 508 with icons for common applications, such as:

an icon 516 of the o-phone module 238 labeled "phone," optionally including an indicator 514 of the number of missed calls or voice messages;

an icon 518 for the e-mail client module 240 labeled "mail", optionally including an indicator 510 of the number of unread e-mails;

an icon 520 of the browser module 247 labeled "browser"; and

an icon 522 labeled "iPod" of the o video and music player module 252 (also known as iPod (trademark of Apple inc.) module 252); and

icons for other applications, such as:

icon 524 of o IM module 241 labeled "message";

an icon 526 labeled "calendar" for the o-calendar module 248;

an icon 528 of the o-image management module 244 labeled "photo";

an icon 530 labeled "camera" for the o-camera module 243;

an icon 532 labeled "online video" for online video module 255;

an icon 534 of the o-stock desktop applet 249-2 labeled "stock market";

o icon 536 of map module 254 labeled "map";

an icon 538 of the o-weather desktop applet 249-1 labeled "weather";

an icon 540 labeled "clock" for the o-alarm desktop applet 249-4;

o an icon 542 of fitness support module 242 labeled "fitness support";

icon 544 labeled "notepad" of o-notepad module 253; and

o an icon 546 labeled "settings" for settings applications or modules that provides access to the settings of the device 200 and its various applications 236.

It should be noted that the icon labels shown in fig. 5A are merely exemplary. For example, icon 522 of video and music player module 252 is optionally labeled "music" or "music player". Other tabs are optionally used for the various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

Fig. 5B illustrates an exemplary user interface on a device (e.g., device 400 of fig. 4) having a touch-sensitive surface 551 (e.g., tablet or trackpad 455 of fig. 4) separate from a display 550 (e.g., touchscreen display 212). The device 400 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 457) for detecting the intensity of contacts on the touch-sensitive surface 551 and/or one or more tactile output generators 459 for generating tactile outputs for a user of the device 400.

Although some of the examples that follow will be given with reference to input on the touch screen display 212 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in fig. 5B. In some implementations, the touch-sensitive surface (e.g., 551 in fig. 5B) has a major axis (e.g., 552 in fig. 5B) that corresponds to a major axis (e.g., 553 in fig. 5B) on the display (e.g., 550). According to these embodiments, the device detects contacts (e.g., 560 and 562 in fig. 5B) with the touch-sensitive surface 551 at locations that correspond to respective locations on the display (e.g., 560 corresponds to 568 and 562 corresponds to 570 in fig. 5B). As such, when the touch-sensitive surface (e.g., 551 in fig. 5B) is separated from the display (e.g., 550 in fig. 5B) of the multifunction device, user inputs (e.g., contacts 560 and 562 and their movements) detected by the device on the touch-sensitive surface are used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contact, single-finger tap gesture, finger swipe gesture), it should be understood that in some embodiments one or more of these finger inputs are replaced by inputs from another input device (e.g., mouse-based inputs or stylus inputs). For example, the swipe gesture is optionally replaced by a mouse click (e.g., rather than a contact), followed by movement of the cursor along the path of the swipe (e.g., rather than movement of the contact). As another example, a flick gesture is optionally replaced by a mouse click (e.g., instead of detecting a contact, followed by ceasing to detect a contact) while the cursor is over the location of the flick gesture. Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mouse and finger contacts are optionally used simultaneously.

Fig. 6A illustrates an exemplary personal electronic device 600. The device 600 includes a body 602. In some embodiments, device 600 includes some or all of the features described with respect to devices 200 and 400 (e.g., fig. 2A-4). In some embodiments, device 600 has a touch-sensitive display screen 604, hereinafter referred to as touch screen 604. Instead of or in addition to the touch screen 604, the device 600 has a display and a touch-sensitive surface. As with devices 200 and 400, in some embodiments, touch screen 604 (or touch-sensitive surface) has one or more intensity sensors for detecting the intensity of a contact (e.g., touch) being applied. One or more intensity sensors of touch screen 604 (or touch-sensitive surface) provide output data representing the intensity of a touch. The user interface of device 600 responds to the touch based on the strength of the touch, meaning that different strengths of the touch can invoke different user interface operations on device 600.

Techniques for detecting and processing touch intensities may be found, for example, in related applications: international patent Application PCT/US2013/040061 entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects reforming to an Application", filed on 8.5.2013, and International patent Application PCT/US2013/069483 entitled "Device, Method, and Graphical User Interface for translating Between Touch Input to Display Output references", filed 11.11.2013, each of which is hereby incorporated by reference in its entirety.

In some embodiments, device 600 has one or more input mechanisms 606 and 608. Input mechanisms 606 and 608 (if included) are in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 600 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow device 600 to be attached with, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watchband, bracelet, pants, belt, shoe, purse, backpack, and the like. These attachment mechanisms allow the user to wear the device 600.

Fig. 6B illustrates an exemplary personal electronic device 600. In some embodiments, the apparatus 600 includes some or all of the components described with respect to fig. 2A, 2B, and 4. The device 600 has a bus 612 that operatively couples an I/O portion 614 with one or more computer processors 616 and a memory 618. I/O portion 614 is connected to display 604, which may have touch sensitive component 622 and optionally also touch intensity sensitive component 624. Further, I/O portion 614 interfaces with communications unit 630 for receiving applications and operating system data using Wi-Fi, bluetooth, Near Field Communication (NFC), cellular, and/or other wireless communications technologies. Device 600 includes input mechanisms 606 and/or 608. For example, input mechanism 606 is a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 608 is a button.

In some examples, input mechanism 608 is a microphone. The personal electronic device 600 includes, for example, various sensors, such as a GPS sensor 632, an accelerometer 634, an orientation sensor 640 (e.g., a compass), a gyroscope 636, a motion sensor 638, and/or combinations thereof, all of which are operatively connected to the I/O portion 614.

The memory 618 of the personal electronic device 600 is a non-transitory computer-readable storage medium for storing computer-executable instructions that, when executed by the one or more computer processors 616, cause the computer processors to perform the techniques and processes described above, for example. The computer-executable instructions are also stored and/or transmitted, for instance, within any non-transitory computer-readable storage medium, for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. The personal electronic device 600 is not limited to the components and configuration of fig. 6B, but may include other components or additional components in a variety of configurations.

As used herein, the term "affordance" refers to a user-interactive graphical user interface object displayed, for example, on a display screen of a device 200, 400, 600, 800, 900, 902, or 904 (fig. 2A, 4, 6A-6B, 8A-8 CT, 9A-9C, 10A-10V, 12, 14, 15, and 16). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each constitute an affordance.

As used herein, the term "focus selector" refers to an input element that is used to indicate the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 455 in fig. 4 or touch-sensitive surface 551 in fig. 5B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 212 in fig. 2A or touch screen 212 in fig. 5A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a "focus selector" such that when an input (e.g., a press input by the contact) is detected at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by moving the focus from one button to another using tab or arrow keys); in these implementations, the focus selector moves according to movement of the focus between different regions of the user interface. Regardless of the particular form taken by the focus selector, the focus selector is typically a user interface element (or contact on a touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element with which the user of the user interface desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a trackpad or touchscreen), the location of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (as opposed to other user interface elements shown on the device display).

As used in the specification and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples acquired during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detecting contact, before detecting contact liftoff, before or after detecting contact start movement, before or after detecting contact end, before or after detecting an increase in intensity of contact, and/or before or after detecting a decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: maximum value of contact strength, mean value of contact strength, average value of contact strength, value at the first 10% of contact strength, half maximum value of contact strength, 90% maximum value of contact strength, and the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds includes a first intensity threshold and a second intensity threshold. In this example, a contact whose characteristic intensity does not exceed the first threshold results in a first operation, a contact whose characteristic intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose characteristic intensity exceeds the second threshold results in a third operation. In some embodiments, the comparison between the feature strengths and the one or more thresholds is used to determine whether to perform the one or more operations (e.g., whether to perform the respective operation or to forgo performing the respective operation), rather than to determine whether to perform the first operation or the second operation.

In some implementations, a portion of the gesture is recognized for determining the feature intensity. For example, the touch-sensitive surface receives a continuous swipe contact that transitions from a starting location and reaches an ending location where the intensity of the contact increases. In this example, the characteristic strength of the contact at the end position is based only on a portion of the continuous swipe contact, and not the entire swipe contact (e.g., the swipe contact is only located at the end position). In some embodiments, a smoothing algorithm is applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: a non-weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for the purpose of determining the feature intensity.

The intensity of a contact on the touch-sensitive surface is characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity that: at which intensity the device will perform the operations typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity that: at which intensity the device will perform a different operation than that typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected whose characteristic intensity is below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, a contact below the nominal contact detection intensity threshold is no longer detected), the device will move the focus selector in accordance with movement of the contact on the touch-sensitive surface without performing operations associated with a light press intensity threshold or a deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface drawings.

Increasing the contact characteristic intensity from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. Increasing the contact characteristic intensity from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. Increasing the contact characteristic intensity from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. The decrease in the characteristic intensity of the contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting a respective press input performed with a respective contact (or contacts), wherein the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the respective operation is performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., a "down stroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and the respective operation is performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "up stroke" of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental input sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold having a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting a subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., depending on the circumstances, the increase in contact intensity or the decrease in contact intensity).

For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input is triggered in response to detection of any of the following: the contact intensity increases above the press input intensity threshold, the contact intensity increases from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, the contact intensity decreases below the press input intensity threshold, and/or the contact intensity decreases below the hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples in which operations are described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operations are optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

3. Digital assistant system

Fig. 7A illustrates a block diagram of a digital assistant system 700, according to various examples. In some examples, the digital assistant system 700 is implemented on a standalone computer system. In some examples, the digital assistant system 700 is distributed across multiple computers. In some examples, some of the modules and functionality of the digital assistant are divided into a server portion and a client portion, where the client portion is located on one or more user devices (e.g., devices 104, 122, 200, 400, 600, 800, 900, 902, or 904) and communicates with the server portion (e.g., server system 108) over one or more networks, e.g., as shown in fig. 1. In some examples, digital assistant system 700 is a specific implementation of server system 108 (and/or DA server 106) shown in fig. 1. It should be noted that the digital assistant system 700 is only one example of a digital assistant system, and that the digital assistant system 700 has more or fewer components than shown, combines two or more components, or may have a different configuration or layout of components. The various components shown in fig. 7A are implemented in hardware, software instructions for execution by one or more processors, firmware (including one or more signal processing integrated circuits and/or application specific integrated circuits), or a combination thereof.

The digital assistant system 700 comprises a memory 702, an input/output (I/O) interface 706, a network communication interface 708, and one or more processors 704. These components may communicate with each other via one or more communication buses or signal lines 710.

In some examples, the memory 702 includes a non-transitory computer-readable medium, such as high-speed random access memory and/or a non-volatile computer-readable storage medium (e.g., one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices).

In some examples, I/O interface 706 couples input/output devices 716, such as a display, a keyboard, a touch screen, and a microphone, of digital assistant system 700 to user interface module 722. I/O interface 706, in conjunction with user interface module 722, receives user inputs (e.g., voice inputs, keyboard inputs, touch inputs, etc.) and processes those inputs accordingly. In some examples, for example, when the digital assistant is implemented on a standalone user device, the digital assistant system 700 includes any of the components and I/O communication interfaces described with respect to the devices 200, 400, 600, 800, 900, 902, or 904 in fig. 2A, 4, 6A-6B, 8A-8 CT, 9A-9C, 10A-10V, 12, 14, 15, and 16. In some examples, the digital assistant system 700 represents a server portion of a digital assistant implementation and may interact with a user through a client-side portion located on a user device (e.g., device 104, 200, 400, 600, 800, 900, 902, or 904).

In some examples, the network communication interface 708 includes one or more wired communication ports 712 and/or wireless transmission and reception circuitry 714. The wired communication port receives and transmits communication signals via one or more wired interfaces, such as ethernet, Universal Serial Bus (USB), FIREWIRE, and the like. The wireless circuitry 714 receives and transmits RF and/or optical signals to and from the communication network and other communication devices. The wireless communication uses any of a number of communication standards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA, Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communication protocol. Network communication interface 708 enables communication between digital assistant system 700 and other devices via a network, such as the internet, an intranet, and/or a wireless network, such as a cellular telephone network, a wireless Local Area Network (LAN), and/or a Metropolitan Area Network (MAN).

In some examples, memory 702 or the computer-readable storage medium of memory 702 stores programs, modules, instructions, and data structures, including all or a subset of the following: an operating system 718, a communications module 720, a user interface module 722, one or more application programs 724, and a digital assistant module 726. In particular, memory 702 or the computer-readable storage medium of memory 702 stores instructions for performing the processes described above. The one or more processors 704 execute the programs, modules, and instructions and read data from, or write data to, the data structures.

The operating system 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware, firmware, and software components.

The communications module 720 facilitates communications between the digital assistant system 700 and other devices via the network communications interface 708. For example, the communication module 720 communicates with the RF circuitry 208 of an electronic device, such as the devices 200, 400, or 600 shown in fig. 2A, 4, 6A-6B, respectively. The communications module 720 also includes various components for processing data received by the wireless circuitry 714 and/or the wired communications port 712.

User interface module 722 receives commands and/or input from a user (e.g., from a keyboard, touch screen, pointing device, controller, and/or microphone) via I/O interface 706 and generates user interface objects on the display. User interface module 722 also prepares and communicates output (e.g., voice, sound, animation, text, icons, vibration, haptic feedback, lighting, etc.) to the user via I/O interface 706 (e.g., via a display, audio channel, speaker, touch pad, etc.).

The application programs 724 include programs and/or modules configured to be executed by the one or more processors 704. For example, if the digital assistant system is implemented on a standalone user device, the applications 724 include user applications such as games, calendar applications, navigation applications, or mail applications. If the digital assistant system 700 is implemented on a server, the application programs 724 include, for example, an asset management application, a diagnostic application, or a scheduling application.

The memory 702 also stores a digital assistant module 726 (or a server portion of a digital assistant). In some examples, digital assistant module 726 includes the following sub-modules, or a subset or superset thereof: an input/output processing module 728, a Speech To Text (STT) processing module 730, a natural language processing module 732, a dialog flow processing module 734, a task flow processing module 736, a service processing module 738, and a speech synthesis processing module 740. Each of these modules has access to one or more of the following systems or data and models, or a subset or superset thereof, of the digital assistant module 726: ontology 760, vocabulary index 744, user data 748, task flow model 754, service model 756, and ASR system 758.

In some examples, using the processing modules, data, and models implemented in the digital assistant module 726, the digital assistant can perform at least some of the following: converting the speech input to text; identifying a user intent expressed in a natural language input received from a user; actively elicit and obtain information needed to fully infer a user's intent (e.g., by disambiguating words, games, intentions, etc.); determining a task flow for satisfying the inferred intent; and executing the task flow to satisfy the inferred intent.

In some examples, as shown in fig. 7B, I/O processing module 728 may interact with a user via I/O device 716 in fig. 7A or with a user device (e.g., device 104, 200, 400, 600, or 800) via network communication interface 708 in fig. 7A to obtain user input (e.g., voice input) and provide a response to the user input (e.g., as voice output). The I/O processing module 728 optionally obtains contextual information associated with the user input from the user device along with or shortly after receiving the user input. The contextual information includes user-specific data, vocabulary, and/or preferences related to user input. In some examples, the context information also includes software and hardware states of the user device at the time the user request is received, and/or information relating to the user's surroundings at the time the user request is received. In some examples, the I/O processing module 728 also sends follow-up questions to the user regarding the user request and receives answers from the user. When a user request is received by the I/O processing module 728 and the user request includes speech input, the I/O processing module 728 forwards the speech input to the STT processing module 730 (or speech recognizer) for speech-to-text conversion.

STT processing module 730 includes one or more ASR systems 758. The one or more ASR systems 758 may process speech input received through the I/O processing module 728 to generate recognition results. Each ASR system 758 includes a front-end speech preprocessor. A front-end speech preprocessor extracts representative features from speech input. For example, a front-end speech preprocessor performs a fourier transform on a speech input to extract spectral features characterizing the speech input as a sequence of representative multi-dimensional vectors. In addition, each ASR system 758 includes one or more speech recognition models (e.g., acoustic models and/or language models) and implements one or more speech recognition engines. Examples of speech recognition models include hidden markov models, gaussian mixture models, deep neural network models, n-gram language models, and other statistical models. Examples of speech recognition engines include dynamic time warping based engines and Weighted Finite State Transformer (WFST) based engines. The extracted representative features of the front-end speech preprocessor are processed using one or more speech recognition models and one or more speech recognition engines to produce intermediate recognition results (e.g., phonemes, phoneme strings, and sub-words), and ultimately text recognition results (e.g., words, word strings, or symbol sequences). In some examples, the voice input is processed at least in part by a third party service or on a device of the user (e.g., device 104, 200, 400, 600, or 800) to produce a recognition result. Once STT processing module 730 generates a recognition result that includes a text string (e.g., a word, or a sequence of words, or a sequence of symbols), the recognition result is passed to natural language processing module 732 for intent inference. In some examples, STT processing module 730 generates a plurality of candidate text representations of the speech input. Each candidate text representation is a sequence of words or symbols corresponding to the speech input. In some examples, each candidate text representation is associated with a speech recognition confidence score. Based on the speech recognition confidence scores, STT processing module 730 ranks the candidate text representations and provides n-best (e.g., n-highest ranked) candidate text representations to natural language processing module 732 for intent inference, where n is a predetermined integer greater than zero. For example, in one example, only the highest ranked (n ═ 1) candidate text representation is delivered to natural language processing module 732 for intent inference. As another example, the 5 highest ranked (n ═ 5) candidate text representations are passed to natural language processing module 732 for intent inference.

More details regarding the processing of Speech to text are described in U.S. utility model patent application serial No. 13/236,942 entitled "Consolidating Speech recognitions Results" filed on 20/9/2011, the entire disclosure of which is incorporated herein by reference.

In some examples, STT processing module 730 includes a vocabulary of recognizable words and/or accesses the vocabulary via speech-to-alphabet conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations for the word represented in the speech recognition phonetic alphabet. In particular, the vocabulary of recognizable words includes words associated with a plurality of candidate pronunciations. For example, the word includes

And

the word "tomato" associated with the candidate pronunciation. In addition, the vocabulary words are associated with custom candidate pronunciations based on previous speech input from the user. Such custom candidate pronunciations are stored in the STT processIn block 730, and is associated with a particular user via a user profile on the device. In some examples, the candidate pronunciation of the word is determined based on the spelling of the word and one or more linguistic and/or phonetic rules. In some examples, the candidate pronunciation is generated manually, e.g., based on a known standard pronunciation.

In some examples, candidate pronunciations are ranked based on their prevalence. For example, candidate pronunciations

Is ranked higher than

As the former is a more common pronunciation (e.g., among all users, for users in a particular geographic area, or for any other suitable subset of users). In some examples, the candidate pronunciations are ranked based on whether the candidate pronunciations are custom candidate pronunciations associated with the user. For example, the custom candidate pronunciation is ranked higher than the standard candidate pronunciation. This can be used to identify proper nouns with unique pronunciations that deviate from the canonical pronunciation. In some examples, the candidate pronunciation is associated with one or more speech features such as a geographic origin, country, or ethnicity. For example, candidate pronunciations

Associated with the United states and candidate pronunciations

Is associated with the united kingdom. Further, the ranking of the candidate pronunciations is based on one or more characteristics of the user (e.g., geographic origin, country, race, etc.) in a user profile stored on the device. For example, it may be determined from a user profile that the user is associated with the united states. Candidate pronunciation based on user association with the United states

Comparable candidate pronunciation (associated with the United states)

Higher (associated with the uk). In some examples, one of the ranked candidate pronunciations may be selected as a predicted pronunciation (e.g., the most likely pronunciation).

Upon receiving a speech input, the STT processing module 730 is used to determine a phoneme (e.g., using a sound model) corresponding to the speech input, and then attempt to determine a word (e.g., using a language model) that matches the phoneme. For example, if STT processing module 730 first identifies a phoneme sequence corresponding to a portion of the speech input

It may then determine that the sequence corresponds to the word "tomato" based on the vocabulary index 744.

In some examples, STT processing module 730 uses fuzzy matching techniques to determine words in the utterance. Thus, for example, STT processing module 730 determines a phoneme sequence

Corresponding to the word "tomato", even if the particular phoneme sequence is not a candidate phoneme sequence for the word.

The natural language processing module 732 of the digital assistant ("natural language processor") takes the n-best candidate textual representations ("word sequences" or "symbol sequences") generated by the STT processing module 730 and attempts to associate each candidate textual representation with one or more "actionable intents" identified by the digital assistant. An "executable intent" (or "user intent") represents a task that can be performed by the digital assistant and that can have an associated task flow implemented in the task flow model 754. An associated task stream is a series of programmed actions and steps taken by the digital assistant to perform a task. The capability scope of the digital assistant depends on the number and variety of task flows that have been implemented and stored in task flow model 754, or in other words, on the number and variety of "actionable intents" that the digital assistant recognizes. However, the effectiveness of a digital assistant also depends on the assistant's ability to infer the correct "executable intent or intents" from a user request expressed in natural language.

In some examples, natural language processing module 732 receives context information associated with the user request, for example, from I/O processing module 728, in addition to the sequence of words or symbols obtained from STT processing module 730. The natural language processing module 732 optionally uses the context information to clarify, supplement, and/or further define information contained in the candidate text representation received from the STT processing module 730. Contextual information includes, for example, user preferences, hardware and/or software states of the user device, sensor information collected before, during, or shortly after a user request, previous interactions (e.g., conversations) between the digital assistant and the user, and so forth. As described herein, in some examples, the contextual information is dynamic and varies with time, location, content of the conversation, and other factors.

In some examples, the natural language processing is based on, for example, ontology 760. Ontology 760 is a hierarchical structure that contains many nodes, each node representing an "actionable intent" or "attribute" related to one or more of the "actionable intents" or other "attributes". As described above, an "actionable intent" refers to a task that a digital assistant is capable of performing, i.e., that task is "actionable" or can be performed. "Properties" represent parameters associated with a sub-aspect of an actionable intent or another property. The connection between the actionable intent node and the property node in the ontology 760 defines how the parameters represented by the property node pertain to the task represented by the actionable intent node.

In some examples, ontology 760 consists of actionable intent nodes and property nodes. Within ontology 760, each actionable intent node is connected to one or more property nodes either directly or through one or more intermediate property nodes. Similarly, each property node is connected to one or more actionable intent nodes either directly or through one or more intermediate property nodes. For example, as shown in FIG. 7C, ontology 760 includes a "restaurant reservation" node (i.e., an actionable intent node). The property nodes "restaurant," "date/time" (for reservation), and "party size" are all directly connected to the actionable intent node (i.e., "restaurant reservation" node).

Further, the attribute nodes "cuisine", "price interval", "phone number", and "location" are child nodes of the attribute node "restaurant", and are all connected to the "restaurant reservation" node (i.e., actionable intent node) through the intermediate attribute node "restaurant". As another example, as shown in FIG. 7C, ontology 760 also includes a "set reminder" node (i.e., another actionable intent node). The property node "date/time" (for set reminders) and "subject" (for reminders) are both connected to the "set reminders" node. Since the attribute "date/time" is related to both the task of making restaurant reservations and the task of setting reminders, the attribute node "date/time" is connected to both the "restaurant reservation" node and the "set reminders" node in ontology 760.

The actionable intent node, along with its linked property nodes, is described as a "domain". In the present discussion, each domain is associated with a respective executable intent and refers to a set of nodes (and relationships between those nodes) associated with a particular executable intent. For example, ontology 760 shown in FIG. 7C includes an example of a restaurant reservation field 762 and an example of a reminder field 764 within ontology 760. The restaurant reservation domain includes the actionable intent node "restaurant reservation," the attribute nodes "restaurant," date/time, "and" party size, "and the child attribute nodes" cuisine, "" price range, "" phone number, "and" location. The reminder field 764 includes the actionable intent node "set reminder" and property nodes "subject" and "date/time". In some examples, ontology 760 is comprised of multiple domains. Each domain shares one or more attribute nodes with one or more other domains. For example, in addition to the restaurant reservation field 762 and reminder field 764, the "date/time" property node is associated with a number of different fields (e.g., a scheduling field, a travel reservation field, a movie tickets field, etc.).

Although fig. 7C shows two exemplary domains within ontology 760, other domains include, for example, "find movie", "initiate phone call", "find direction", "arrange meeting", "send message", and "provide answer to question", "read list", "provide navigation instructions", "provide instructions for task", etc. The "send message" field is associated with a "send message" actionable intent node and further includes attribute nodes such as "one or more recipients", "message type", and "message body". The attribute node "recipient" is further defined, for example, by child attribute nodes such as "recipient name" and "message address".

In some examples, ontology 760 includes all domains (and thus actionable intents) that a digital assistant is able to understand and act upon. In some examples, ontology 760 is modified, such as by adding or removing entire domains or nodes, or by modifying relationships between nodes within ontology 760.

In some examples, nodes associated with multiple related executables are clustered under a "super domain" in ontology 760. For example, a "travel" super-domain includes a cluster of attribute nodes and actionable intent nodes related to travel. Executable intent nodes related to travel include "airline reservations," "hotel reservations," "car rentals," "route planning," "finding points of interest," and the like. Actionable intent nodes under the same super-domain (e.g., a "travel" super-domain) have multiple attribute nodes in common. For example, executable intent nodes for "airline reservation," hotel reservation, "" car rental, "" get route, "and" find point of interest "share one or more of the attribute nodes" start location, "" destination, "" departure date/time, "" arrival date/time, "and" party size.

In some examples, each node in ontology 760 is associated with a set of words and/or phrases that are related to the property or executable intent represented by the node. The respective set of words and/or phrases associated with each node is a so-called "vocabulary" associated with the node. The respective set of words and/or phrases associated with each node is stored in the lexical index 744 associated with the property or actionable intent represented by the node. For example, returning to fig. 7B, the vocabulary associated with the node of the "restaurant" attribute includes words such as "food," "drinks," "cuisine," "hunger," "eating," "pizza," "fast food," "meal," and so forth. As another example, the words associated with the node of the actionable intent of "initiate a phone call" include words and phrases such as "call," "make a call," "dial," "make a call with … …," "call the number," "call to," and so forth. The vocabulary index 744 optionally includes words and phrases in different languages.

The natural language processing module 732 receives candidate text representations (e.g., one or more text strings or one or more symbol sequences) from the STT processing module 730 and, for each candidate representation, determines which nodes the words in the candidate text representation relate to. In some examples, a word or phrase in a candidate text representation is found to be associated (via lexical index 744) with one or more nodes in ontology 760, and then "triggers" or "activates" those nodes. Based on the number and/or relative importance of the activated nodes, the natural language processing module 732 selects one of the actionable intents as the task that the user intends for the digital assistant to perform. In some examples, the domain with the most "triggered" nodes is selected. In some examples, the domain with the highest confidence (e.g., based on the relative importance of its respective triggered node) is selected. In some examples, the domain is selected based on a combination of the number and importance of triggered nodes. In some examples, additional factors are also considered in selecting a node, such as whether the digital assistant has previously correctly interpreted a similar request from the user.

The user data 748 includes user-specific information such as user-specific vocabulary, user preferences, user addresses, a user's default second language, a user's contact list, and other short-term or long-term information for each user. In some examples, natural language processing module 732 uses user-specific information to supplement information contained in the user input to further define the user intent. For example, for a user request "invite my friend to my birthday party," natural language processing module 732 can access user data 748 to determine which people "friends" are and where and when the "birthday party" will be held without the user explicitly providing such information in their request.

It is to be appreciated that in some examples, natural language processing module 732 is implemented with one or more machine learning mechanisms (e.g., neural networks). In particular, one or more machine learning mechanisms are configured to receive candidate text representations and contextual information associated with the candidate text representations. Based on the candidate text representations and the associated context information, one or more machine learning mechanisms are configured to determine an intent confidence score based on a set of candidate actionable intents. The natural language processing module 732 may select one or more candidate actionable intents from a set of candidate actionable intents based on the determined intent confidence scores. In some examples, an ontology (e.g., ontology 760) is also utilized to select one or more candidate actionable intents from a set of candidate actionable intents.

Additional details of Searching for ontologies based on symbolic strings are described in U.S. utility patent application serial No. 12/341,743, entitled "Method and Apparatus for Searching Using An Active Ontology," filed on 22.12.2008, the entire disclosure of which is incorporated herein by reference.

In some examples, once natural language processing module 732 identifies an executable intent (or domain) based on a user request, natural language processing module 732 generates a structured query to represent the identified executable intent. In some examples, the structured query includes parameters for one or more nodes within the domain that can execute the intent, and at least some of the parameters are populated with specific information and requirements specified in the user request. For example, the user says "help me reserve a seat at 7 pm in a sushi shop. In this case, the natural language processing module 732 can correctly recognize the executable intention as "restaurant reservation" based on the user input. According to the ontology, the structured query of the "restaurant reservation" domain includes parameters such as { cuisine }, { time }, { date }, { party size }, and the like. In some examples, based on the speech input and text derived from the speech input using STT processing module 730, natural language processing module 732 generates a partially structured query for the restaurant reservation field, where the partially structured query includes parameters { cuisine ═ sushi class "} and { time ═ 7 pm" }. However, in this example, the user utterance contains insufficient information to complete a structured query associated with the domain. Thus, other necessary parameters such as { party number } and { date } are not specified in the structured query based on currently available information. In some examples, natural language processing module 732 populates some parameters of the structured query with the received contextual information. For example, in some examples, if the user requests a sushi store that is "nearby," the natural language processing module 732 populates the { location } parameter in the structured query with the GPS coordinates from the user device.

In some examples, natural language processing module 732 identifies a plurality of candidate executable intents for each candidate text representation received from STT processing module 730. Additionally, in some examples, a respective structured query is generated (partially or wholly) for each identified candidate executable intent. The natural language processing module 732 determines an intent confidence score for each candidate actionable intent and ranks the candidate actionable intents based on the intent confidence scores. In some examples, the natural language processing module 732 passes the generated one or more structured queries (including any completed parameters) to a task stream processing module 736 ("task stream processor"). In some examples, the one or more structured queries for the m-best (e.g., m highest ranked) candidate executables are provided to task flow processing module 736, where m is a predetermined integer greater than zero. In some examples, the one or more structured queries for the m best candidate executable intents are provided to task flow processing module 736 along with the corresponding one or more candidate textual representations.

Additional details of Inferring User Intent based on multiple candidate actionable intents determined From multiple candidate textual representations of Speech input are described in U.S. utility model patent application 14/298,725 entitled "System and Method for introducing User From Speech Inputs" filed 6.6.2014, the entire disclosure of which is incorporated herein by reference.

Task stream processing module 736 is configured to receive one or more structured queries from natural language processing module 732, complete the structured queries (if necessary), and perform the actions required to "complete" the user's final request. In some examples, the various processes necessary to accomplish these tasks are provided in the task flow model 754. In some examples, task flow model 754 includes procedures for obtaining additional information from a user, as well as task flows for performing actions associated with an executable intent.

As described above, to complete a structured query, the task flow processing module 736 needs to initiate additional conversations with the user in order to obtain additional information and/or clarify potentially ambiguous utterances. When such interaction is necessary, task flow processing module 736 invokes dialog flow processing module 734 to participate in a dialog with the user. In some examples, the dialog flow processor module 734 determines how (and/or when) to request additional information from the user, and receives and processes the user response. The questions are provided to the user and the answers are received from the user through the I/O processing module 728. In some examples, the conversation flow processing module 734 presents the conversation output to the user via audible output and/or visual output and receives input from the user via a spoken or physical (e.g., click) response. Continuing with the above example, when the task flow processing module 736 invokes the conversation flow processing module 734 to determine "party size" and "date" information for a structured query associated with the domain "restaurant reservation," the conversation flow processing module 734 generates a message such as "a few bits in a line? "and" which day to subscribe? "and the like to the user. Upon receiving an answer from the user, the dialog flow processing module 734 may populate the structured query with missing information or pass the information to the task flow processing module 736 to complete the missing information from the structured query.

Once the task flow processing module 736 has completed the structured query for the executable intent, the task flow processing module 736 begins executing the final task associated with the executable intent. Thus, the task flow processing module 736 performs the steps and instructions in the task flow model according to the specific parameters contained in the structured query. For example, a task flow model for the actionable intent "restaurant reservation" includes steps and instructions for contacting a restaurant and actually requesting a reservation for a particular party size at a particular time. For example, using structured queries such as: { restaurant reservation, restaurant ABC cafe, date 3/12/2012, time 7 pm, party number 5}, task flow processing module 736 may perform the following steps: (1) logging into a server of an ABC cafe or a coffee shop such as

The restaurant reservation system of (1), (2) entering date, time, and party size information in the form of a website, (3) submitting a form, and (4) forming a calendar entry for the reservation in the user's calendar.

In some examples, the task flow processing module 736 either completes the task requested in the user input or provides the informational answer requested in the user input with the assistance of the service processing module 738 ("service processing module"). For example, the service processing module 738 initiates phone calls, sets calendar entries, invokes map searches, invokes or interacts with other user applications installed on the user device, and invokes or interacts with third-party services (e.g., restaurant reservation portals, social networking sites, bank portals, etc.) on behalf of the task flow processing module 736. In some examples, the protocols and Application Programming Interfaces (APIs) required for each service are specified by respective ones of service models 756. The service handling module 738 accesses the appropriate service model for the service and generates a request for the service according to the service model according to the protocols and APIs required by the service.

For example, if a restaurant has enabled an online reservation service, the restaurant submits a service model that specifies the necessary parameters to make the reservation and an API to communicate the values of the necessary parameters to the online reservation service. The service processing module 738, when requested by the task flow processing module 736, can establish a network connection with the online booking service using the Web address stored in the service model and send the necessary parameters for booking (e.g., time, date, party size) to the online booking interface in a format according to the API of the online booking service.

In some examples, the natural language processing module 732, the conversation flow processing module 734, and the task flow processing module 736 are used jointly and iteratively to infer and define the user's intent, to obtain information to further clarify and refine the user's intent, and to ultimately generate a response (i.e., output to the user, or complete a task) to satisfy the user's intent. The generated response is a dialog response to the speech input that at least partially satisfies the user intent. Additionally, in some examples, the generated response is output as a speech output. In these examples, the generated response is sent to a speech synthesis processing module 740 (e.g., a speech synthesizer), where the generated response may be processed to synthesize the dialog response in speech form. In other examples, the generated response is data content relevant to satisfying the user request in the voice input.

In examples where the task flow processing module 736 receives multiple structured queries from the natural language processing module 732, the task flow processing module 736 first processes a first structured query of the received structured queries in an attempt to complete the first structured query and/or to perform one or more tasks or actions represented by the first structured query. In some examples, the first structured query corresponds to a highest ranked executable intent. In other examples, the first structured query is selected from structured queries received based on a combination of a corresponding speech recognition confidence score and a corresponding intent confidence score. In some examples, if the task flow processing module 736 encounters an error during processing of the first structured query (e.g., due to an inability to determine the necessary parameters), the task flow processing module 736 may continue to select and process a second structured query of the received structured queries that corresponds to a lower ranked executable intent. The second structured query is selected, for example, based on the speech recognition confidence score of the corresponding candidate text representation, the intent confidence score of the corresponding candidate actionable intent, the missing necessary parameters in the first structured query, or any combination thereof.

The speech synthesis processing module 740 is configured to synthesize speech output for presentation to a user. The speech synthesis processing module 740 synthesizes speech output based on text provided by the digital assistant. For example, the generated dialog response is in the form of a text string. The speech synthesis processing module 740 converts the text string into audible speech output. Speech synthesis processing module 740 uses any suitable speech synthesis technique to generate speech output from text, including but not limited to: concatenative synthesis, unit-selective synthesis, diphone synthesis, domain-specific synthesis, formant synthesis, articulatory synthesis, Hidden Markov Model (HMM) based synthesis, and sine wave synthesis. In some examples, speech synthesis processing module 740 is configured to synthesize individual words based on the phoneme strings corresponding to the words. For example, the phoneme string is associated with a word in the generated dialog response. The phoneme string is stored in metadata associated with the word. The speech synthesis processing module 740 is configured to directly process the phoneme string in the metadata to synthesize words in speech form.

In some examples, speech synthesis is performed on a remote device (e.g., server system 108) instead of (or in addition to) using speech synthesis processing module 740, and the synthesized speech is sent to the user device for output to the user. This may occur, for example, in some implementations where the output of the digital assistant is generated at the server system. Also, since the server system typically has more processing power or more resources than the user device, it is possible to obtain a higher quality speech output than the client side synthesis will achieve.

Additional details regarding digital assistants can be found in U.S. utility patent application 12/987,982 entitled "Intelligent Automated Assistant" filed on 10.1.2011 and U.S. utility patent application 13/251,088 entitled "Generation and Processing Task Items Using pages to Performance" filed on 30.9.2011, the entire disclosures of which are incorporated herein by reference.

4. Digital assistant user interface

Fig. 8A-8 CT illustrate a user interface and a digital assistant user interface according to various examples. Fig. 8A to 8CT are used to explain processes described below, including the processes in fig. 17A to 17F.

Fig. 8A illustrates an electronic device 800. Device 800 is implemented as device 104, device 122, device 200, or device 600. In some examples, device 800 implements, at least in part, digital assistant system 700. In the example of fig. 8A, device 800 is a smartphone with a display and a touch-sensitive surface. In other examples, device 800 is a different type of device, such as a wearable device (e.g., a smart watch), a tablet device, a laptop computer, or a desktop computer.

In fig. 8A, device 800 displays a user interface 802 on display 801 that is different from a Digital Assistant (DA) user interface 803, as described below. In the example of FIG. 8A, user interface 802 is a home screen user interface. In other examples, the user interface is another type of user interface, such as a lock screen user interface or an application specific user interface, e.g., a map application user interface, a weather application user interface, a messaging application user interface, a music application user interface, a movie application user interface, and so forth.

In some examples, device 800 receives user input while displaying a user interface other than DA user interface 803. The device 800 determines whether the user input satisfies the criteria for initiating the DA. Exemplary user inputs that satisfy the criteria for initiating a DA include: a predetermined type of voice input (e.g., "hey, Siri"); an input to select a virtual button or a physical button of device 800 (or an input to select such a button for a predetermined duration); this type of input: input received at an external device coupled to device 800; this type of user gesture: user gestures performed on display 801 (e.g., a drag or swipe gesture from a corner of display 801 toward the center of display 801); and this type of input: an input representing a movement of the device 800 (e.g., raising the device 800 to a viewing position).

In some examples, in accordance with a determination that the user input satisfies the criteria for initiating a DA, device 800 displays DA user interface 803 over the user interface. In some examples, displaying the DA user interface 803 (or another displayed element) over the user interface includes replacing at least a portion of the display of the user interface with the display of the DA user interface 803 (or the display of another graphical element). In some examples, in accordance with a determination that the user input does not meet the criteria for initiating DA, device 800 forgoes display of DA user interface 803 and performs an action (e.g., updating user interface 802) in response to the user input.

Fig. 8B shows DA user interface 803 displayed over user interface 802. In some examples, as shown in fig. 8B, DA user interface 803 includes a DA indicator 804. In some examples, the indicators 804 are displayed in different states to indicate the respective states of the DA. The DA states include a listening state (indicating that the DA is sampling speech input), a processing state (indicating that the DA is processing natural language requests), a speaking state (indicating that the DA is providing audio and/or text output), and an idle state. In some examples, indicators 804 each include different visualization effects indicating different DA states. FIG. 8B shows indicator 804 in a listening state after initiating the DA based on detecting that the user input meets the criteria, since the DA is ready to accept voice input.

In some examples, the size of the indicator 804 in the listening state varies based on the received natural language input. For example, indicator 804 expands and contracts in real-time according to the amplitude of the received speech input. Fig. 8C shows the indicator 804 in a listening state. In fig. 8C, the device 800 receives a natural language speech input "how do weather today? ", and the indicator 804 expands and contracts in real time according to the speech input.

Fig. 8D shows an indicator 804 in a processing state, for example, indicating that the DA is processing a request "how do the weather today? ". Fig. 8E shows the indicator 804 in a speaking state, e.g., indicating that the DA is currently providing an audio output of "weather good today" in response to a request. Fig. 8F shows the indicator 804 in an idle state. In some examples, user input selecting indicator 804 in the idle state causes the DA (and indicator 804) to enter a listening state, e.g., by activating one or more microphones to sample audio input.

In some examples, the DA provides audio output in response to a user request, while device 800 provides other audio output. In some examples, the DA reduces the volume of the other audio output when the audio output in response to the user request and the other audio output are simultaneously provided. For example, DA user interface 803 is displayed over a user interface that includes media (e.g., a movie or song) that is currently playing. When the DA provides audio output in response to a user request, the DA reduces the volume of the audio output of the media being played.

In some examples, DA user interface 803 includes a DA response affordance. In some examples, the response affordance corresponds to a response of the DA to the received natural language input. For example, FIG. 8E illustrates device 800 displaying a response affordance 805 that includes weather information in response to a received voice input.

As shown in fig. 8E-8F, the device 800 displays an indicator 804 at a first portion of the display 801 and a response affordance 805 at a second portion of the display 801. Displaying a portion of DA user interface 803 over user interface 802 remains visible (e.g., not visually obscured) at a third portion of display 801. For example, prior to receiving a user input to initiate the digital assistant (e.g., fig. 8A), the portion of the user interface 802 that remains visible is displayed at the third portion of the display 801. In some examples, the first, second, and third portions of the display 801 are referred to as an "indicator portion," "response portion," and a "User Interface (UI) portion," respectively.

In some examples, the UI portion is located between the indicator portion (displaying indicator 804) and the response portion (displaying response affordance 805). For example, in FIG. 8F, the UI section includes (or is) a display area 8011 (e.g., a rectangular area) between the bottom of the response affordance 805 to the top of the indicator 804, where a side edge of the display area 8011 is defined by a side edge of the response affordance 805 (or the display 801). In some examples, the portion of user interface 802 that remains visible at the UI portion of display 801 includes one or more user-selectable graphical elements, e.g., links and/or affordances, such as the home screen application affordance in fig. 8F.

In some examples, the device 800 displays the response affordance 805 in a first state. In some examples, the first state includes a compact state in which the display size of the response affordance 805 is small (e.g., compared to an expanded response affordance state, described below), and/or the response affordance 805 displays information in a compact (e.g., summarized) form (e.g., compared to an expanded response affordance state). In some examples, the device 800 receives user input corresponding to selection of the response affordance 805 in the first state and, in response, replaces display of the response affordance 805 in the first state with display of the response affordance 805 in the second state. In some examples, the second state is an expanded state in which the display size of the response affordance 805 is larger (e.g., as compared to the compact state), and/or the response affordance 805 displays a larger amount of information/more detailed information (e.g., as compared to the compact state). In some examples, the device 800 defaults to displaying the response affordance 805 in the first state, e.g., such that the device 800 initially displays (fig. 8E-8G) the response affordance 805 in the first state.

Fig. 8E-8G show the response affordance 805 in a first state. As shown, the response affordance 805 compactly provides weather information, such as by providing current temperature and status and omitting more detailed weather information (e.g., hourly weather information). FIG. 8G illustrates the device 800 receiving a user input 806 (e.g., a tap gesture) corresponding to a selection of the response affordance 805 in the first state. While fig. 8G-8P generally illustrate that the user input corresponding to the respective selection of the response affordance is a touch input, in other examples, the user input corresponding to the selection of the response affordance is another type of input, such as a voice input (e.g., "show me more information") or a peripheral device input (e.g., an input from a mouse or a touch pad). FIG. 8H illustrates that in response to receiving the user input 806, the device 800 replaces the display of the response affordance 805 in the first state with the display of the response affordance 805 in the second state. As shown, the response affordance 805 in the second state now includes more detailed weather information.

In some examples, while displaying the response affordance 805 in the second state, the device 800 receives a user input requesting that the response affordance 805 be displayed in the first state. In some examples, in response to receiving the user input, the device 800 replaces the display of the response affordance 805 in the second state with the display of the response affordance 805 in the first state. For example, in fig. 8H, the DA user interface 803 includes a selectable element (e.g., back button) 807. User input selecting selectable element 807 causes device 800 to revert to the display of FIG. 8F.

In some examples, the device 800 receives user input corresponding to selection of the response affordance 805 when the response affordance 805 is displayed in the second state. In response to receiving the user input, device 800 displays a user interface corresponding to the application in response to affordance 805. For example, fig. 8I illustrates the device 800 receiving a user input 808 (e.g., a tap gesture) corresponding to a selection of the response affordance 805. Fig. 8J illustrates that in response to receiving the user input 808, the device 800 displays a user interface 809 for a weather application.

In some examples, device 800 displays a selectable DA indicator when displaying a user interface of an application. For example, fig. 8J shows an optional DA indicator 810. In some examples, device 800 additionally or alternatively displays an indicator 804, e.g., an indicator in an idle state, at a first portion of display 801 when displaying a user interface of an application.

In some examples, device 800 receives user input selecting a selectable DA indicator while displaying a user interface of an application. In some examples, in response to receiving the user input, device 800 replaces the display of the user interface of the application with DA user interface 803. In some examples, DA user interface 803 is a DA user interface displayed immediately prior to displaying the user interface of the application. For example, fig. 8K shows device 800 receiving a user input 811 (e.g., a tap gesture) selecting DA indicator 810. Fig. 8L illustrates the device 800 replacing the display of the user interface 809 of the weather application with the display of the DA user interface 803 in response to receiving the user input 811.

User input 806 in FIG. 8G corresponds to selection of the first portion of response affordance 805. In some examples, when the device 800 displays the response affordance 805 in a first state (e.g., a compact state), the device 800 receives a user input corresponding to a selection of a second portion of the response affordance 805. In some examples, a first portion (e.g., a bottom portion) of the response affordance 805 includes information intended to answer the user request. In some examples, a second portion (e.g., a top portion) of the response affordance 805 includes a logo indicating a category of the response affordance 805 and/or associated text. Exemplary categories of response affordances include weather, stocks, knowledge, calculators, messages, music, maps, and so forth. These categories may correspond to the categories of services that the DA may provide. In some examples, the first portion of the response affordance 805 occupies a larger display area than the second portion of the response affordance 805.

In some examples, in response to receiving user input corresponding to selection of the second portion of the response affordance 805, the device 800 displays a user interface of the application corresponding to the response affordance 805 (e.g., without displaying the response affordance 805 in the second state). For example, fig. 8M illustrates the device 800 receiving a user input 812 (e.g., a tap gesture) selecting a second portion of the response affordance 805 displayed in the first state. FIG. 8N illustrates that, in response to receiving the user input 812, the device 800 displays a user interface 809 for a weather application (e.g., without displaying the response affordance 805 in an expanded state). In this way, the user may provide input selecting different portions of the response affordance 805 to expand the response affordance 805 or cause an application corresponding to the response affordance 805 to be displayed, as shown in FIGS. 8G-8H and 8M-8N.

Fig. 8N also shows that upon displaying user interface 809, device 800 displays selectable DA indicator 810. User input selecting DA indicator 810 causes device 800 to revert to the display of fig. 8M, e.g., similar to the examples shown by fig. 8K-8L. In some examples, while displaying the user interface 809, the device 800 displays a DA indicator 804 (e.g., a DA indicator in an idle state) at a first portion of the display 801.

In some examples, for some types of response affordances, user input corresponding to selection of any portion of the response affordance causes device 800 to display a user interface of an application corresponding to the response affordance. In some examples, this is because the response affordance cannot be displayed in a more detailed manner (e.g., in the second state). For example, there may not be additional information that the DA may provide in response to the natural language input. For example, consider how much the natural language input "5 times 6 equals? ". Fig. 8O shows the DA user interface 803 displayed in response to natural language input. DA user interface 803 includes a response affordance 813 displayed in a first state. Response affordance 813 includes the answer "5 × 6 ═ 30," but there is no additional information that the DA may provide. FIG. 8O also shows that device 800 receives a user input 814 (e.g., a tap gesture) selecting a first portion of response affordance 813. FIG. 8P illustrates that, in response to receiving user input 814, device 800 displays a user interface 815, e.g., a calculator application user interface, corresponding to an application that responds to affordance 813.

In some examples, the response affordance includes a selectable element, such as selectable text indicating a link. Fig. 8Q shows DA user interface 803 displayed in response to the natural language input "tell me more information about Famous Band". DA user interface 803 includes a response affordance 816. Response affordance 816 includes information about "Famous Band" and selectable element 817 of member #1 corresponding to "Famous Band". In some examples, device 800 receives user input corresponding to selection of a selectable element and, in response, displays an affordance (second response affordance) corresponding to the selectable element over the response affordance. Fig. 8R illustrates that device 800 receives user input 818 (e.g., a tap gesture) selecting selectable element 817. FIG. 8S illustrates that in response to receiving the user input 818, the device 800 displays a second response affordance 819 that includes information about member #1 over the response affordance 816 to form a response affordance overlay.

In some examples, while displaying the second response affordance over the response affordance, device 800 visually hides the user interface at or at a third portion of display 801 (e.g., the portion does not display any response affordance or indicator 804). In some examples, visually obscuring the user interface includes darkening the user interface or obscuring the user interface. FIG. 8S illustrates the user interface 802 at the third portion of the display 801 being visually obscured by the device 800 while the second response affordance 819 is displayed over the response affordance 816.

FIG. 8S illustrates that when the second response affordance 819 is displayed over a portion of the response affordance 816, the portion remains visible. In other examples, the second response affordance 819 replaces the display of the response affordance 816 such that no portion of the response affordance 816 is visible.

FIG. 8T illustrates the device 800 receiving a user input 820 (e.g., a flick gesture) selecting a selectable element 821 ("detroit") in the second response affordance 819. FIG. 8U illustrates that, in response to receiving the user input 820, the device 800 displays a third response affordance 822 over the second response affordance 819. The third response affordance 822 includes information about detroit (the place of birth of member # 1). Fig. 8U shows that the user interface 802 continues to be visually obscured at the third portion of the display 801.

Fig. 8U also shows that although there are three response affordances (e.g., 816, 819, and 822) in the stack of response affordances, the device 800 indicates only two response affordances in the stack. For example, a portion of the third response affordance 822 and the second response affordance 819 are displayed, but no portion of the response affordance 816 is displayed. Thus, in some examples, when more than two response affordances are stacked, device 800 only visually indicates that there are two response affordances in the stack. In other examples, when the response affordances are stacked, the device 800 visually indicates only a single response affordance of the stack (e.g., such that display of a next response affordance completely replaces display of a previous response affordance).

8V-8Y illustrate a user providing an input to return to a previous response affordance in the overlay. Specifically, in FIG. 8V, the device 800 receives a user input 823 (e.g., a swipe gesture) on the third response affordance 822 back to the second response affordance 819. FIG. 8W illustrates that in response to receiving the user input 823, the device 800 ceases to display the third response affordance 822 and displays the second response affordance 819 in its entirety. The device 800 also displays (e.g., reveals) a portion of the response affordance 816. FIG. 8X illustrates the device 800 receiving a user input 824 (e.g., a swipe gesture) requesting a return of the second response affordance 819 to the response affordance 816. FIG. 8Y illustrates that in response to receiving the user input 824, the device 800 ceases to display the second response affordance 819 and displays the response affordance 816 in its entirety. In some examples, device 800 receives an input (e.g., a swipe gesture in the opposite direction) to display the next responsive affordance in the overlay, and in response, displays the next responsive affordance in the overlay in a manner similar to that described above. In other examples, navigating through the responsive affordances in the overlay relies on other input means (e.g., user selection of a displayed "back" or "next" button) in a manner similar to that described above.

Fig. 8Y also shows that the user interface 802 is no longer visually obscured at the third portion of the display 801. Thus, in some examples, as shown in fig. 8Q-8Y, the user interface 802 is visually masked when the response affordance is stacked and is not visually masked when the affordance is not stacked. For example, when the initial response affordance 816 is not displayed (or only partially displayed), the user interface 802 is visually obscured, and when the initial response affordance 816 is displayed in its entirety, the user interface 802 is not visually obscured.

In some examples, the user interface (e.g., the user interface on which DA user interface 803 is displayed) includes an input field occupying a fourth portion (e.g., the "input field portion") of display 801. The input field includes an area where a user can provide natural language input. In some examples, the input field corresponds to an application program, such as a messaging application, an email application, a note-taking application, a reminder application, a calendar application, and so forth. Fig. 8Z shows a user interface 825 of the messaging application that includes an input field 826 that occupies a fourth portion of the display 801.

Fig. 8AA shows DA user interface 803 displayed over user interface 825. Device 800 responds to the natural language input "what is the title of the song? "and displays the user interface 803. DA user interface 803 includes indicator 804 at a first portion of display 801 and response affordance 827 (indicating a song identified by the DA) at a second portion of display 801.

In some examples, device 800 receives a user input corresponding to a displacement from a first portion of display 801 to a fourth portion of display 801 in response to an affordance. In response to receiving the user input, device 800 replaces the display of the response affordance at the first portion of display 801 with the display of the response affordance in the input field. For example, fig. 8AB through 8AD show that device 800 receives user input 828 that displaces a response affordance 827 from a first portion of display 801 to an input field 826. The user input 828 corresponds to a drag gesture from the first portion of the display 801 to the fourth portion of the display 801 and ends with a lift-off event (e.g., a finger lift-off event) at the display of the input field 826.

In some examples, as shown in fig. 8AB through 8AD, upon receiving user input 828, device 800 continuously shifts response affordance 827 from a first portion of display 801 to a fourth portion of display 801. For example, when response affordance 827 is shifted, device 800 displays response affordance 827 at a location corresponding to a respective currently displayed touch location of user input 828. In some examples, as response affordance 827 is shifted, the display size of response affordance 827 decreases, e.g., such that response affordance 827, when shifted, shrinks under a user's finger (or other input device). Fig. 8AB through 8AD also show that indicator 804 stops displaying when there is a continuous shift response affordance 827.

Fig. 8AD shows that the response affordance 827 is now displayed in the input field 826 of the messaging application. FIG. 8AE shows device 800 receiving a user input 830 (e.g., a tap gesture) corresponding to a selection of send message affordance 829. Fig. 8AF shows that in response to receiving user input 830, device 800 sends response affordance 827 as a message. In this way, the user can send the response affordance in a communication (e.g., text message, email) by providing an input (e.g., drag and drop) to shift the response affordance into the appropriate input field. In other examples, the user may include the response affordance in a similar manner in notes, calendar entries, word processing documents, reminder entries, and the like.

In some examples, user input corresponding to displacement of the affordance from the first portion of the display 801 to the fourth portion of the display 801 (that displays the input field) corresponds to selection of the affordance. In some examples, the affordance is a share affordance (e.g., share response affordance in a communication) or a save affordance (e.g., save affordance in a note or reminder entry). For example, when device 800 displays DA user interface 803 over a user interface that includes an input field, the response affordance includes a share affordance or a save affordance, depending on the type of user interface. For example, when the user interface corresponds to a communication application (e.g., messaging or email), the response affordance includes a share affordance, and when the user interface corresponds to another type of application having an input field (e.g., word processing, reminders, calendars, notes), the response affordance includes a save affordance. User input selecting a sharing or saving affordance causes the device 800 to replace the display of a response affordance at the first portion of the display 801 with the display of a response affordance in the input field in a manner similar to that described above. For example, device 800 stops displaying indicator 804 when a response affordance is displayed in the input field.

In some examples, the user interface (e.g., the user interface on which DA user interface 803 is displayed) includes a desktop applet region occupying a fifth portion (e.g., "desktop applet portion") of display 801. In the example of fig. 8AG, device 800 is a tablet device. The device 800 displays a user interface 831 including a desktop applet region 832 occupying a fifth portion of the display 801 on the display 801. Device 800 also displays DA user interface 803 over user interface 831. The DA user interface 803 is displayed in response to the natural language input "track flight 23". The DA user interface 803 includes an indicator 804 displayed at a first portion of the display 801 and a responsive affordance 833 (including information about the flight 23) displayed at a second portion of the display 801.

In some examples, device 800 receives a user input corresponding to a displacement from a first portion of display 801 to a fifth portion of display 801 in response to an affordance. In some examples, in response to receiving the user input, the device 800 replaces the display of the response affordance at the first portion of the display with the display of the response affordance in the desktop widget region. For example, fig. 8 AH-8 AJ illustrate the device 800 receiving a user input 834 that displaces the response affordance 833 from the first portion of the display 801 to the desktop applet region 832. The user input 834 corresponds to a drag gesture from the first portion of the display 801 to the fifth portion of the display 801 and ends with a lift-off event at the display of the desktop applet region 832. In some examples, shifting the response affordance 833 from the first portion of the display 801 to the fifth portion of the display 801 is performed in a manner similar to the shifting of the response affordance 827 described above. For example, indicator 804 ceases to display when response affordance 833 is shifted.

FIG. 8AJ shows that the response affordance 833 is now displayed in the desktop applet area 832 with the displayed calendar and music desktop applet. In this way, the user can provide input (e.g., drag and drop) to shift the response affordance 833 to the desktop applet region 832 to add the response affordance 833 as a desktop applet.

In some examples, the user input corresponding to the displacement of the affordance from the first portion of the display 801 to the fifth portion of the display 801 corresponds to a selection of the affordance. In some examples, the affordance is a "show in desktop applet" affordance. For example, when the device 800 displays the DA user interface 803 over a user interface that includes a desktop applet region, the response affordance includes a "display in desktop applet" affordance. Selection of a user input of the "display in desktop applet" affordance causes device 800 to replace the display of the response affordance at the first portion of display 801 with the display of the response affordance in the desktop applet region in a manner similar to that described above.

In some examples, the response affordance corresponds to an event, and the device 800 determines completion of the event. In some examples, in response to determining completion of the event, device 800 stops displaying the response affordance in the desktop applet region (e.g., for a predetermined duration after determining completion). For example, the response affordance 833 corresponds to a flight, and in response to determining that the flight has completed (e.g., landed), the device 800 stops displaying the response affordance 833 in the desktop applet region 832. As another example, the response affordance corresponds to a sports game, and in response to determining that the sports game has ended, the device 800 stops displaying the response affordance in the desktop widget area.

Fig. 8AK through 8AN illustrate various exemplary types of response affordances. Specifically, fig. 8AK shows "how old the celebrity X is? "and the displayed compact response affordance 835. Compact response affordance 835 includes a direct answer to the request (e.g., "30 years old") and does not include further information (e.g., additional information about celebrity X). In some examples, all of the compact response affordances have the same maximum size, such that the compact response affordance can only occupy a (relatively small) area of the display 801. FIG. 8AL illustrates a detailed response affordance 836 displayed in response to a natural language request "give statistics about team # 1". The detailed response affordance 836 includes detailed information (e.g., various statistical information) about team #1 and has a larger display size than the compact response affordance 835. FIG. 8AM shows a list response affordance 837 displayed in response to the natural language "show me a list of nearby restaurants". The list response affordance 837 includes a list of options (e.g., restaurants) and has a larger display size than the compact response affordance 835. FIG. 8AN illustrates a disambiguation response affordance 838 displayed in response to a natural language request "Call Neal". The disambiguation response affordance includes selectable disambiguation options: (1) neal Ellis, (2) Neal Smith, and (3) Neal Johnson. Device 800 also provides a query "which Neal? "audio output.

As shown in fig. 8AK through 8AN, the type of response affordance displayed (e.g., compact, detailed, list, disambiguation) depends on the content of the natural language input and/or the interpretation of the natural language input by the DA. In some examples, the affordance construction rule specifies a particular type of response affordance to display for a particular type of natural language input. In some examples, the construction rule specifies a default attempt to display the compact response affordance, e.g., such that the device 800 displays the compact response affordance in response to a natural language input that may be sufficiently answered by the compact response affordance. In some examples, when the response affordance can be displayed in different states (e.g., a first compact state and a second expanded (detailed) state), the build rule specifies that the response affordance is initially displayed as a compact affordance. As described with respect to fig. 8G-8H, a detailed version of the compact affordance is available for display in response to receiving an appropriate user input. It should be appreciated that some natural language inputs (e.g., "give me statistical information about team # 1" and "show me a list of nearby restaurants") may not be adequately answered with a compact affordance (or may not be desirable to answer the input with a compact affordance). Thus, a build rule may specify a particular type of affordance (e.g., a detailed list) to display for such input.

In some examples, the DA determines a plurality of results corresponding to the received natural language input. In some examples, device 800 displays a response affordance that includes a single result of the multiple results. In some examples, other ones of the plurality of results are not displayed while the response affordance is displayed. For example, consider the natural language input "recent coffee". The DA determines a plurality of results (a plurality of nearby coffee shops) corresponding to the input. Fig. 8AO illustrates a response affordance 839 (e.g., a compact affordance) displayed in response to an input. The response affordance 839 includes a single result of the plurality of results (the coffee shop closest to the location of the device 800). The device 800 also provides a speech output "this is the closest coffee shop". Thus, for a natural language request involving multiple results, the DA initially may provide a single result, e.g., the most relevant result.

In some examples, after providing a single result (e.g., displaying the response affordance 839), the DA provides the next result in the plurality of results. For example, in fig. 8AP, device 800 replaces response affordance 839 with response affordance 840 that includes the second closest coffee shop. The device 800 also provides a speech output "this is the second closest coffee shop". In some examples, device 800 transitions from fig. 8AO to fig. 8AP in response to receiving a user input that rejects a single result (e.g., "i don't want to go to that coffee shop") or a user input indicating that a next result is to be provided. In some examples, device 800 transitions from fig. 8AO to fig. 8AP within a predetermined duration after displaying affordance 839 and/or after providing speech output "this is the closest coffee shop," for example, if no user input is received selecting affordance 839. In this way, device 800 may sequentially provide results for natural language input that involves multiple results.

In some examples, the response affordance includes one or more task affordances. User input (e.g., a flick gesture) selecting a task affordance causes the device 800 to perform a corresponding task. For example, in FIG. 8AN, response affordance 838 includes task affordances 841, 842, and 843. User selection of task affordance 841 causes device 800 to initiate a telephone call to Neal Ellis, user selection of task affordance 842 causes device 800 to initiate a telephone call to Neal Smith, and so on. As another example, response affordance 839 includes task affordance 844 and response affordance 840 includes task affordance 845. User selection of the task affordance 844 causes the device 800 to launch a map application that displays a route to a closest coffee shop, while user selection of the task affordance 845 causes the device 800 to launch a map application that displays a route to a second closest coffee shop.

In some examples, device 800 simultaneously displays multiple response affordances in response to natural language input. In some examples, each of the plurality of response affordances corresponds to a different possible domain of the natural language input. In some examples, device 800 displays the plurality of response affordances when the natural language input is determined to be ambiguous (e.g., correspond to a plurality of domains).

For example, consider the natural language input "beyond. FIG. 8AQ illustrates response affordances 846, 847, and 848 concurrently displayed in response to natural language input. Response affordances 846, 847, and 848 correspond to news domains (e.g., news users request about Beyone), music domains (e.g., music users request to play Beyone), and knowledge domains (e.g., information users request about Beyone), respectively. In some examples, respective user inputs corresponding to selection of response affordances 846, 847, and 848 cause device 800 to perform corresponding actions. For example, selection of response affordance 846 causes display of a detailed response affordance including news about Beyone, selection of response affordance 847 causes device 800 to launch a music application including a song of Beyone, and selection of response affordance 848 causes display of a detailed response affordance including information about Beyone.

In some examples, the response affordance includes a field of editable text including text determined from the natural language input. For example, FIG. 8AR shows a response affordance 849 displayed in response to the natural language speech input "text mom I'm home". The response affordance 849 includes an editable text field 850 that includes the text "I'm hole," e.g., because the DA incorrectly identified "I'm hole" as "I'm hole. The response affordance also includes a task affordance 851. User input selecting task affordance 851 causes device 800 to send a text message.

In some examples, device 800 receives user input corresponding to selection of the editable text field and, in response, displays the keyboard while displaying the response affordance. For example, fig. 8AS shows device 800 receiving a user input 852 (e.g., a flick gesture) selecting an editable text field 850. Fig. 8AT shows that in response to receiving user input 852, device 800 displays keyboard 853 while displaying response affordance 849. As shown, device 800 displays a keyboard 853 over a user interface 802 (e.g., a user interface over which DA user interface 803 is displayed). While fig. 8 AT-8 AV illustrate that a portion of the user interface 802 is not visually obscured when the response affordance and keyboard are displayed over the user interface 802, in other examples, AT least a portion of the user interface 802 (e.g., the portion of the display 801 that does not display the keyboard or the response affordance 849) is visually obscured.

In some examples, device 800 receives one or more keyboard inputs and, in response, updates text in the editable text field in accordance with the one or more keyboard inputs. For example, fig. 8AU shows that device 800 has received keyboard input that corrects "hole" to "home". The device 800 displays the corrected text in the editable text field 850 in response to the affordance 849.

In other examples, device 800 receives a speech input requesting editing of text displayed in an editable text field. In response to receiving the speech input, device 800 updates the text in the editable text field according to the speech input. For example, in fig. 8AR, the user may provide the speech input "No, I said I'm home" to cause device 800 to update the text in editable text field 850 accordingly.

In some examples, after updating text in the editable text field, device 800 receives user input requesting performance of a task associated with the affordance. In response to receiving the user input, device 800 performs the requested task based on the updated text. For example, FIG. 8AV shows that after editing "hole" to "home," device 800 receives user input 854 (e.g., a tap gesture) corresponding to selection of task affordance 851. Fig. 8AW illustrates the device 800 sending a message "I'm home" to the user's mom in response to receiving user input 854. The device 800 also displays a logo 855 indicating completion of the task. Fig. 8AW further illustrates that in response to receiving user input 854, the device 800 ceases to display the keyboard 853 to display (e.g., reveal) a portion of the user interface 802, and the device 800 displays the indicator 804.

In this way, the user may edit the text included in the response affordance (e.g., if the DA incorrectly recognizes the user's voice input) and cause the DA to perform an action using the correct text. Although fig. 8AR through 8AW illustrate examples of editing and sending text messages, in other examples, a user may edit and save (or send) notes, calendar entries, reminder entries, email entries, etc. in a similar manner.

In some examples, device 800 receives a user input that eliminates the DA. In some examples, eliminating the DA includes ceasing to display the DA user interface 803. DA elimination is discussed in more detail below with respect to fig. 10A-10V. In some examples, after eliminating the DA, device 800 receives user input to reinitiate the DA (e.g., user input meeting criteria for initiating the DA). In some examples, upon receiving a user input to re-initiate the DA, device 800 displays a DA user interface that includes the same response affordance, e.g., a response affordance that is displayed before the DA is dismissed.

In some examples, device 800 displays the same response affordance in accordance with a determination that the same response affordance corresponds to a response to a received natural language input (e.g., an input intended for a re-initiated DA). For example, fig. 8AX shows DA user interface 803 including response affordance 856. Device 800 responds to the natural language input "how much weather? And DA user interface 803 is displayed. Fig. 8AY shows that device 800 receives a user input 857 that cancels the DA, e.g., a tap gesture corresponding to a selection of user interface 802. Fig. 8AZ shows device 800 dismissing the DA, e.g., ceasing to display DA user interface 803, in response to receiving user input 857. Fig. 8BA shows that the device 800 has received an input to re-initiate the DA and is currently receiving a natural language input "will wind? ". Fig. 8BB shows device 800 displaying DA user interface 803 that includes the same response affordance 856 and provides the speech output "yes, windy". For example, the DA has determined that the same response affordance 856 corresponds to the natural language input "how does weather? "and" will wind? ". Thus, if the previous response affordance is relevant to the current natural language request, the previous response affordance may be included in a subsequently initiated DA user interface.

In some examples, device 800 displays the same response affordance in accordance with a determination that a user input to re-initiate the DA is received within a predetermined duration of eliminating the DA. For example, fig. 8BC shows how much are "3 times 5 equal to? "and DA user interface 803 displayed. DA user interface 803 includes a response affordance 858. Fig. 8BD shows that DA has been eliminated at the first time. Fig. 8BE shows that device 800 has received a user input to reinitiate the DA within a predetermined duration (e.g., 5 seconds) of the first time. For example, device 800 has received any of the types of input described above that satisfy the criteria for initiating a DA, but has not received another natural language input that includes a different request for a DA. Thus, in FIG. 8BE, device 800 displays DA user interface 803 including the same response affordance 858 and indicator 804 in a listening state. In this way, if the user quickly re-initiates the DA, for example because the user previously accidentally dismissed the DA, the previous response affordance may be included in the subsequently initiated DA user interface.

Fig. 8BF shows the apparatus 800 in a landscape orientation. In some examples, because device 800 is in a landscape orientation, device 800 displays the user interface in landscape mode. For example, FIG. 8BF illustrates a messaging application user interface 859 displayed in landscape mode. In some examples, device 800 displays DA user interface 803 in landscape mode over the user interface in landscape mode. For example, fig. 8BG shows DA user interface 803 displayed in landscape mode over user interface 859. It should be appreciated that the user may provide one or more inputs to interact with the DA user interface 803 in landscape mode in a manner consistent with the techniques discussed herein.

In some examples, some user interfaces do not have a landscape mode. For example, the display of the user interface is the same regardless of whether the device 800 is in a landscape orientation or a portrait orientation. Exemplary user interfaces without landscape mode include a home screen user interface and a lock screen user interface. Fig. 8BH illustrates a home screen user interface 860 (which does not have landscape mode) displayed when device 800 is in a landscape orientation.

In some examples, when device 800 is in landscape orientation, device 800 displays DA user interface 803 over a user interface that does not have landscape mode. In some examples, when DA user interface 803 (in landscape mode) is displayed over a user interface without landscape mode, device 800 visually hides the user interface, e.g., does not display a portion of DA user interface 803 over the visually hidden user interface. For example, fig. 8BI shows the device 800 in landscape orientation displaying the DA user interface 803 in landscape mode over the home screen user interface 860. The Home screen user interface 860 is displayed in portrait mode (although the device 800 is in landscape orientation) because the Home screen user interface 860 does not have landscape mode. As shown, device 800 visually hides the home screen user interface 860. In this way, the device 800 avoids displaying both the DA user interface 803 in landscape mode and the user interface in portrait mode (e.g., home screen user interface 860) that is not visually obscured, which may provide a confusing user visual experience.

In some examples, device 800 visually hides the predetermined type of user interface when device 800 displays DA user interface 803 over the predetermined type of user interface. Exemplary predetermined types of user interfaces include lock screen user interfaces. Fig. 8BJ illustrates device 800 displaying an exemplary lock screen user interface 861. FIG. 8BK shows device 800 displaying DA user interface 803 above lock screen user interface 861. As shown, the device 800 visually hides the lock screen user interface 861 at the portion of the lock screen user interface 861 above which the DA user interface 803 is not displayed.

In some examples, DA user interface 803 includes a dialog affordance. In some examples, the dialog affordance includes a dialog generated by the DA in response to the received natural language input. In some examples, the dialog affordance is displayed at a sixth portion of the display 801 (e.g., a "conversation portion"), the sixth portion of the display 801 being located between the first portion of the display 801 (that displays the DA indicator 804) and the second portion of the display 801 (that displays the response affordance). For example, fig. 8BL shows a dialog affordance 862 that includes a dialog generated by the DA in response to the natural language input "play Frozen," as discussed further below. Fig. 8BM shows a dialog affordance 863 that includes a dialog generated by the DA in response to the natural language input "delete conference #1," as discussed further below. Fig. 8BM also shows that the device 800 displays a dialog affordance 863 at a sixth portion of the display 801, the sixth portion being between the display of the indicator 804 and the display of the response affordance 864.

In some examples, the DA determines a plurality of selectable disambiguation options for the received natural language input. In some examples, the dialog of the dialog affordance includes the plurality of selectable disambiguation options. In some examples, the plurality of disambiguation options are determined from a DA determining that the natural language input is ambiguous. Ambiguous natural language input corresponds to a plurality of possible actionable intents, e.g., each actionable intent has a relatively high (and/or equal) confidence score. For example, consider the natural language input "play Frozen" in fig. 8 BL. The DA determines two selectable disambiguation options: option 865 "play movie" (e.g., user wants to play movie "Frozen") and option 866 "play music" (e.g., user wants to play music in movie "Frozen"). Dialog affordance 862 includes options 865 and 866, where user selection of option 865 causes device 800 to play the movie "Frozen" and user selection of option 866 causes device 800 to play music in the movie "Frozen". As another example, consider the natural language input "delete meeting # 1" in fig. 8BM, where "meeting # 1" is a repeat meeting. The DA determines two selectable disambiguation options: option 867 "delete single" (e.g., the user wants to delete a single instance in meeting # 1), and option 868 "delete all" (e.g., the user wants to delete all instances in meeting # 1). The dialog affordance 863 includes options 867 and 868, and a cancel option 869.

In some examples, the DA determines that additional information is needed to perform the task based on the received natural language input. In some examples, the dialog affordance dialog includes one or more selectable options for the DA to recommend additional information as desired. For example, the DA may have determined a domain of the received natural language input, but may not be able to determine the parameters needed to complete the task associated with the domain. For example, consider the natural language input "call". The DA determines that the domain of the natural language input is a phone call domain (e.g., a domain associated with an actionable intent to make a phone call), but cannot determine a parameter (i.e., who called). In some examples, the DA thus determines one or more selectable options as recommendations for parameters. For example, device 800 displays selectable options in the dialog affordance that correspond to contacts that the user calls most frequently. User selection of any of the selectable options causes the device 800 to call the corresponding contact.

In some examples, the DA determines a primary user intent based on the received natural language input and determines an alternate user intent based on the received natural language input. In some examples, the primary intent is the highest ranked executable intent, and the alternate user intent is the second highest ranked executable intent. In some examples, the displayed response affordance corresponds to a primary user intent, while a dialog of the concurrently displayed dialog affordance includes selectable options corresponding to alternate user intentions. For example, FIG. 8BN shows DA user interface 803 displayed in response to the natural language input "route to Phil". The DA determines a primary user intent, i.e., the user wants to get a route to "Phil coffee", and an alternate user intent, i.e., the user wants to get a route to the home of the contact named "Phil". The DA user interface 803 includes a response affordance 870 and a dialog affordance 871 that correspond to primary user intent. Dialog 872 of dialog affordance 871 corresponds to a secondary user intent. User input selecting dialog 872 causes device 800 to obtain a route to the home of the contact named "Phil" while user input selecting responsive affordance 870 causes device 800 to obtain a route to "Phil coffee".

In some examples, the dialog affordance is displayed in a first state. In some examples, the first state is an initial state, e.g., a description of the dialog affordance is initially displayed prior to receiving user input to interact with the dialog affordance. FIG. 8BO shows the DA user interface 803 including a dialog affordance 873 displayed in an initial state. Device 800 responds to the natural language input "how much weather? And DA user interface 803 is displayed. The dialog affordance 873 includes at least a portion of a dialog generated by the DA in response to the input, e.g., "current air temperature 70 degrees, and at wind … …". Further description regarding whether to display dialogs generated by the DA will be discussed below with respect to FIGS. 11-16.

In some examples, device 800 receives user input corresponding to selection of a dialog affordance displayed in a first state. In response to receiving the user input, the device 800 replaces the display of the dialog affordance in the first state with the display of the dialog affordance in the second state. In some examples, the second state is an expanded state in which the display size of the dialog affordance in the expanded state is greater than the display size of the dialog affordance in the initial state, and/or in which the dialog affordance in the expanded state is displayed a greater amount of content than the dialog affordance in the initial state. FIG. 8BP illustrates the device 800 receiving a user input 874 (e.g., a drag gesture) corresponding to selection of a dialog affordance 873 displayed in an initial state. FIG. 8BQ illustrates the device 800 replacing the display of the dialog affordance 873 in the initial state with the display of the dialog affordance 873 in the expanded state in response to receiving the user input 874 (or a portion thereof). As shown, the dialog affordance 873 in FIG. 8BQ has a larger display size and includes a larger amount of text than the dialog affordance in FIG. 8 BP.

In some examples, the display size of the dialog affordance (in the second state) is proportional to a length of the user input that caused the dialog affordance to be displayed in the second state. For example, in fig. 8 BP-8 BQ, the display size of the dialog affordance 873 increases in proportion to the length (e.g., physical distance) of the drag gesture 874. In this way, the user may provide a continuous drag gesture to expand the response affordance 873 according to the drag length of the drag gesture. Further, while fig. 8BO through 8BQ illustrate the device 800 initially displaying the dialog affordance 873 as shown in fig. 8BO and then expanding the dialog affordance in fig. 8BQ, in other examples, the device 800 initially displays the dialog affordance 873 as shown in fig. 8 BQ. Thus, in some examples, the device 800 initially displays the dialog affordance such that the dialog affordance displays a maximum amount of content, e.g., without obscuring (overlaying) any concurrently displayed response affordances.

In some examples, the display of the dialog affordance masks the display of the concurrently displayed response affordance. In particular, in some examples, the display of the dialog affordance in the second (e.g., expanded) state occupies at least a portion of the second portion (of the display response affordance) of the display 801. In some examples, displaying the dialog affordance in the second state further includes displaying the dialog affordance over at least a portion of the response affordance. For example, FIG. 8BQ shows that the drag gesture 874 continues. FIG. 8BR illustrates that in response to receiving the continue drag gesture 874, the device 800 launches display of a dialog affordance 873 over display of the response affordance 875.

In some examples, the response affordance is displayed in an initial state before receiving user input that causes the dialog affordance to be displayed (e.g., expanded) in a second state. In some examples, the initial state describes a state of the response affordance before the dialog affordance (or a portion thereof) is displayed over the response affordance. For example, fig. 8BO through 8BQ show response affordances 875 displayed in an initial state. In some examples, displaying the dialog affordance in the second (e.g., expanded) state over at least a portion of the response affordance includes replacing a display of the response affordance in the initial state with a display of the response affordance in the overlaid state. Fig. 8BR shows a response affordance 875 displayed in an overlaid state. In some examples, the display size of the response affordance shrinks (e.g., relative to the initial state) and/or dims (e.g., the color of the display is darker than the initial state) when displayed in the overlaid state. In some examples, the degree to which the response affordance shrinks and/or darkens is proportional to the amount of the dialog affordance displayed over the response affordance.

In some examples, the dialog affordance has a maximum display size, and a second (e.g., expanded) state of the dialog affordance corresponds to the maximum display size. In some examples, the dialog affordance displayed at the maximum display size cannot be further expanded in response to a user input, such as a drag gesture. In some examples, the dialog affordance displayed at the maximum display size displays the entire content of the dialog affordance. In other examples, the dialog affordance displayed at the maximum display size does not display the entire content of the dialog affordance. Thus, in some examples, when the device 800 displays the dialog affordance (which has a maximum display size) in the second state, the device 800 enables user input (e.g., a drag/swipe gesture) to scroll through content of the dialog affordance. FIG. 8BS shows the dialog affordance 873 displayed at a maximum display size. Specifically, in FIG. 8BR, the drag gesture 874 continues. In response to receiving the continue drag gesture 874, in FIG. 8BS, the device 800 displays (e.g., expands) the dialog affordance 873 to its maximum display size. The dialog affordance 873 includes a scroll indicator 876 that indicates that a user can provide input to scroll through the content of the dialog affordance 873.

In some examples, when the dialog affordance is displayed in the second state (and at its maximum size), a portion of the response affordance remains visible. Thus, in some examples, the device 800 constrains a maximum size of the dialog affordance displayed over the response affordance such that the dialog affordance does not completely overlap the response affordance. In some examples, the portion of the response affordance that remains visible is a second portion of the response affordance described above with respect to fig. 8M. For example, the portion is a top portion of the response affordance that includes a glyph that indicates a category of the response affordance and/or associated text. FIG. 8BS shows that when the device 800 displays the dialog affordance 873 at a maximum size over the response affordance 875, the top portion of the response affordance 875 remains visible.

In some examples, the device 800 receives a user input corresponding to a selection of a portion of the response affordance that remains visible (when the dialog affordance is displayed in the second state over the response affordance). In response to receiving the user input, the device displays a response affordance at a first portion of the display 801, e.g., displays the response affordance in its initial state. In response to receiving the user input, the device 800 further replaces the display of the dialog affordance in the second (e.g., expanded) state with the display of the dialog affordance in the third state. In some examples, the third state is a compressed state in which the dialog affordance in the third state has a smaller display size (as compared to the dialog affordance in the initial state or the expanded state) and/or the dialog affordance includes a smaller amount of content (as compared to the dialog affordance in the initial state or the expanded state). In other examples, the third state is the first state (e.g., the initial state). Fig. 8BT illustrates the device 800 receiving a user input 877 (e.g., a tap gesture) selecting a top portion of the response affordance 875. Fig. 8BU illustrates that in response to receiving the user input 877, the device 800 replaces the display of the conversation affordance 873 in the expanded state (fig. 8BT) with the display of the conversation affordance 873 in the compressed state. The device 800 further displays a response affordance 875 in an initial state.

In some examples, device 800 receives a user input corresponding to a selection of a dialog affordance displayed in a third state. In response to receiving the user input, the device 800 replaces the display of the response affordance in the third state with the display of the dialog affordance in the first state. For example, in fig. 8BU, the user may provide an input (e.g., a tap gesture) that selects the dialog affordance 873 displayed in a compressed state. In response to receiving the input, the device 800 displays the dialog affordance in an initial state, e.g., reverts to the display of FIG. 8 BO.

In some examples, the device 800 receives user input corresponding to selection of a concurrently displayed response affordance when the dialog affordance is displayed in a first state or a second state (e.g., an initial state or an expanded state). In response to receiving the user input, the device 800 replaces the display of the dialog affordance in the first state or the second state with the display of the dialog affordance in the third (e.g., compressed) state. For example, fig. 8BV illustrates DA user interface 803 displayed in response to a natural language input of "show me list of team # 1". The DA user interface 803 includes a detailed response affordance 878 and a dialog affordance 879 that is displayed in an initial state. Fig. 8BV also illustrates the device 800 receiving a user input 880 (e.g., a drag gesture) selecting the responsive affordance 878. Fig. 8BW illustrates the device 800 replacing the display of the dialog affordance 879 in the initial state with the display of the dialog affordance 879 in the compressed state in response to receiving a user input 880.

In some examples, the device 800 receives user input corresponding to selection of a dialog affordance when displayed in a first state or a second state (e.g., an initial state or an expanded state). In response to receiving the user input, the device 800 replaces the display of the dialog affordance in the first state or the second state with the display of the dialog affordance in the third (e.g., compressed) state. For example, fig. 8BX shows what music you can provide me in response to a natural language input? "and DA user interface 803 displayed. The DA user interface 803 includes a response affordance 881 and a dialog affordance 882 that is displayed in an initial state. FIG. 8BX also shows that device 800 receives a user input 883 (e.g., a drag-down or swipe gesture) selecting a dialog affordance 882. FIG. 8BY illustrates that in response to receiving the user input 883, the device 800 replaces the display of the dialog affordance 882 in an initial state with the display of the dialog affordance 882 in a compressed state. While fig. 8 BX-8 BY illustrate that the user input corresponding to selection of a dialog affordance is a drag or swipe gesture, in other examples, the user input is selection of a displayed affordance included in the dialog affordance. For example, a user input (e.g., a tap gesture) selecting a "compact" affordance in a dialog affordance displayed in a first state or a second state causes the device 800 to replace a display of the dialog affordance in the first state or the second state with a display of the dialog affordance in a third state.

In some examples, device 800 displays a transcription of the received natural language speech input in a dialog affordance. The transcription is obtained by performing Automatic Speech Recognition (ASR) on a natural language speech input. Fig. 8BZ shows "how does the weather? And DA user interface 803 displayed. The DA user interface includes a response affordance 884 and a dialog affordance 885. The dialog affordance 885 includes a transcription 886 of the speech input and a dialog 887 generated by the DA in response to the speech input.

In some examples, the device 800 by default does not display a transcription of the received natural language speech input. In some examples, device 800 includes settings that, when activated, cause device 800 to always display a transcription of the natural language speech input. Various other examples are now discussed in which the device 800 may display a transcription of a received natural language speech input.

In some examples, the natural language speech input (with the displayed transcription) is continuous with a second natural language speech input received prior to the natural language speech input. In some examples, the display transcription is performed in accordance with a determination that the DA cannot determine the user intent of the natural language speech input and cannot determine a second user intent of a second natural language speech input. Thus, in some examples, if the DA cannot determine the actionable intent of two subsequent natural language inputs, the device 800 displays a transcription of the natural language input.

For example, fig. 8CA shows that device 800 has received a voice input "how far to Dish n' Dash? ", and the DA cannot determine the user intent of the natural language input. For example, the device 800 provides an audio output of "I'm not sure I understand, can you please say that again? ". Thus, the user repeats the voice input. For example, fig. 8CB shows that device 800 receives a continuing speech input of "how far to Dish n' Dash? ". FIG. 8CC shows that the DA is still unable to determine the user's intent for continuous speech input. For example, the device 800 provides an audio output of "I'm not sure I understand". Thus, the device 800 also displays a transcription 889 "how far to fish and Rash? "is used to indicate 888. In this example, the transcription 889 revealed that DA mistakenly twice will "how far to Dish n' Dash? "identify as" how far to fish and Rash? ". Since "Rish and Rash" may not be a true location, the DA cannot determine the user intent of the two speech inputs.

In some examples, the transcription of the received natural language speech input is performed in accordance with a determination that the natural language speech input repeats a previous natural language speech input. For example, fig. 8CD shows "where is Starbucks? "and DA user interface 803 displayed. The DA incorrectly recognizes the speech input as "where is Star Mall? ", and thus display a response affordance 890 that includes" Star Mall ". The user repeats the voice input because the DA incorrectly understands the voice input. For example, fig. 8CE shows that the device 800 receives the previous speech input "where is Starbucks? "is repeated (e.g., successive repeats). The DA determines that the voice input repeats the previous voice input. FIG. 8CF illustrates that, based on such a determination, the device 800 displays a dialog affordance 891 that includes a transcription 892. Transcription 892 reveals that DA (e.g., twice) incorrectly will "where is Starbucks? "is identified as" where is Star Mall? ".

In some examples, after receiving the natural language speech input (e.g., for which a transcription is to be displayed), the device receives a second natural speech input that is subsequent to the natural language speech input. In some examples, the display transcription is performed in accordance with a determination that the second natural language speech input indicates a speech recognition error. Thus, in some examples, if the subsequent speech input indicates that the DA incorrectly recognized the previous speech input, the device 800 displays a transcription of the previous speech input. For example, FIG. 8CG shows the DA user interface 803 displayed in response to the speech input "set a timer for 15 minutes". The DA incorrectly identifies "15 minutes" as "50 minutes". The DA user interface 803 thus includes a response affordance 893 indicating that the timer is set to 50 minutes. Because the DA incorrectly recognized the speech input, the user provides a second speech input (e.g., "that's not what I said," "you board me wrong," "that's incorrect," etc.) indicating that the speech recognition was incorrect. For example, FIG. 8CH shows device 800 receiving a second speech input "that's not while I said". The DA determines that the second speech input indicates a speech recognition error. FIG. 8CI illustrates that, based on such a determination, the device 800 displays a dialog affordance 894 that includes a transcription 895. Transcription 895 revealed that DA incorrectly recognized "15 minutes" as "50 minutes".

In some examples, device 800 receives user input corresponding to a selection of a displayed transcription. In response to receiving the user input, device 800 simultaneously displays a keyboard and an editable text field including a transcript, e.g., displays the keyboard and the editable text field over a user interface on which DA user interface 803 is displayed. In some examples, device 800 also visually hides at least a portion of the user interface (e.g., a portion of display 801 that does not display a keyboard or editable text field). Continuing with the example of fig. 8CI, fig. 8CJ shows the device 800 receiving a user input 896 (e.g., a tap gesture) selecting a transcription 895. Fig. 8CK illustrates that, in response to receiving user input 896, device 800 displays a keyboard 897 and an editable text field 898 including a transcription 895. Fig. 8CK also shows that device 800 visually obscures a portion of user interface 802.

FIG. 8CL illustrates that the device 800 has received one or more keyboard inputs and has edited the transcript 895 in accordance with the one or more keyboard inputs, e.g., "set a timer for 50 minutes" as "set a timers for 15 minutes". Fig. 8CL also shows that the device 800 receives a user input 899 (e.g., a tap gesture) corresponding to selection of the completion key 8001 of the keyboard 897. Fig. 8CM shows that in response to receiving user input 899, the DA performs a task based on the current (e.g., edited) transcription 895. For example, device 800 displays DA user interface 803 that includes a response affordance 8002 indicating that the timer is set to 15 minutes. The device 800 also provides the speech output "Ok, I set the timer for 15 minutes". In this way, the user may manually correct an incorrect transcription (e.g., using keyboard input) so that the correct task is performed.

In some examples, device 800 receives user input corresponding to selection of a visually masked user interface while displaying a keyboard and a field of editable text. In some examples, in response to receiving the user input, device 800 stops displaying the keyboard and the editable text field. In some examples, device 800 additionally or alternatively ceases to display DA user interface 803. For example, in fig. 8 CK-8 CL, a user input (e.g., a tap gesture) selecting a visually masked user interface 802 may cause device 800 to revert to the display of fig. 8CI or cause device 800 to cease displaying DA user interface 803 and display user interface 802 in its entirety, as shown in fig. 8A.

In some examples, the device 800 presents the digital assistant results (e.g., the response affordance and/or the audio output) at a first time. In some examples, in accordance with a determination that the digital assistant result corresponds to a predetermined type of digital assistant result, device 800 automatically stops displaying DA user interface 803 for a predetermined duration after the first time. Thus, in some examples, device 800 may eliminate DA user interface 803 quickly (e.g., within 5 seconds) after providing the predetermined type of result. Exemplary predetermined types of results correspond to completed tasks that require no further user input (or no further user interaction). For example, such results include results confirming that a timer has been set, that a message has been sent, and that a home appliance (e.g., a lamp) has changed state. Examples of results that do not correspond to the predetermined type include results that the DA requires further user input, and results that the DA provides information (e.g., news, wikipedia articles, location) in response to a user's information request.

For example, FIG. 8CM shows that device 800 is presenting the results at a first time, e.g., completing the provision of the speech output "Ok, I set the timer for 15 minutes". Because the results correspond to a predetermined type, fig. 8CN shows that the device 800 automatically eliminates the DA for a predetermined duration (e.g., 5 seconds) after the first time (e.g., without further user input).

Fig. 8 CO-8 CT show examples of DA user interface 803 and an exemplary user interface when device 800 is a tablet device. It should be understood that any of the techniques discussed herein with respect to device 800 being a tablet device are equally applicable when device 800 is another type of device (and vice versa).

Fig. 8CO shows a device 800 displaying a user interface 8003. The user interface 8003 includes a taskbar region 8004. In fig. 8CO, device 800 displays DA user interface 803 on top of user interface 8003. DA user interface 803 includes an indicator 804 displayed at a first portion of display 801 and a responsive affordance 8005 displayed at a second portion of display 801. As shown, a portion of the user interface 8003 remains visible (e.g., not visually obscured) at a third portion of the display 801. In some examples, the third portion is located between the first portion of the display 801 and the second portion of the display 801. In some examples, as shown in fig. 8CO, the display of the DA user interface 803 does not visually obscure the taskbar area 8004, e.g., no portion of the DA user interface 803 is displayed above the taskbar area 8004.

Fig. 8CP illustrates a device 800 displaying a DA user interface 803 including a dialog affordance 8006. As shown, the conversation affordance 8006 is displayed at a portion of the display 801 that is between a first portion of the display 801 (that displays the indicator 804) and a second portion of the display (that displays the response affordance 8005). Displaying the dialog affordance 8006 also causes the response affordance 8005 to shift (from FIG. 8CO) toward a top portion of the display 801.

Fig. 8CQ illustrates a device 800 displaying a user interface 8003 that includes a media panel 8007 that indicates that media is currently playing. Fig. 8CR shows device 800 displaying DA user interface 803 on top of user interface 8003. DA user interface 803 includes a response affordance 8008 and an indicator 804. As shown, the display of DA user interface 803 does not visually obscure media panel 8007. For example, as shown, display elements (e.g., indicator 804, response affordance 8008, conversation affordance) of DA user interface 803 cause media panel 8007 to shift toward a top portion of display 801.

Fig. 8CS shows a device 800 displaying a user interface 8009 including a keyboard 8010. Fig. 8CT shows the DA user interface 803 displayed on top of the user interface 8009. As shown in fig. 8CT, in some examples, displaying DA user interface 803 over user interface 8009 including keyboard 8010 causes device 800 to visually obscure (e.g., graying out) keys of keyboard 8010.

Fig. 9A-9C illustrate multiple devices that determine which device should respond to a voice input according to various examples. In particular, fig. 9A shows devices 900, 902, and 904. Devices 900, 902, and 904 are each implemented as device 104, device 122, device 200, or device 600. In some examples, devices 900, 902, and 904 each implement, at least in part, DA system 700.

In fig. 9A, when a user provides a voice input that includes a trigger phrase (e.g., "hey, Siri") for initiating a DA, e.g., "hey, Siri, how does the weather? "the respective displays of devices 900, 902, and 904 are not displayed. In some examples, when a user provides speech input, a respective display of at least one of devices 900, 902, and 904 displays a user interface (e.g., home screen user interface, application-specific user interface). FIG. 9B shows that in response to receiving a speech input comprising a trigger phrase, devices 900, 902, and 904 each display indicator 804. In some examples, each indicator 804 is displayed in a listening state, e.g., indicating that the respective device is sampling audio input.

In fig. 9B, devices 900, 902, and 904 coordinate with each other (or via a fourth device) to determine which device should respond to the user request. Exemplary techniques for device coordination to determine which device should respond to a user request are described in U.S. patent No.10,089,072 entitled "INTELLIGENT DEVICE association AND CONTROL" on 2018, 10, month 2 AND U.S. patent application No.63/022,942 entitled "DIGITAL ASSISTANT HARDWARE abstrction" filed on 2020, 5, month 11, the contents of which are hereby incorporated by reference in their entirety. As shown in fig. 9B, each device only displays the indicator 804 when each device determines whether to respond to the user request. For example, respective portions of the non-display indicators 804 of the displays of the devices 900, 902, and 904 are each not displayed. In some examples, when at least one of devices 900, 902, and 904 displays a user interface (a previous user interface) when a user provides voice input, the at least one device additionally displays indicator 804 only over the previous user interface when the at least one device determines whether to respond to the user request.

Fig. 9C shows the device 902 determined to be a device responding to the user request. As shown, in response to determining that the other device (e.g., device 902) should respond to the user request, the display of devices 900 and 904 stops displaying (or stops displaying indicator 804 to fully display the previous user interface). As further shown, in response to determining that device 902 should respond to the user request, device 902 displays a user interface 906 (e.g., a lock screen user interface) and DA user interface 803 over user interface 906. DA user interface 803 includes a response to the user request. In this way, visual distraction is minimized when determining which of the multiple devices should respond to speech input. For example, in FIG. 9B, the display of the device determined not to respond to the user request only displays indicator 804, e.g., as opposed to displaying the user interface with the entire display.

Determining which device of the multiple devices should respond to the voice input in the manner shown and described above provides feedback to the user that the voice input has been received and is being processed. Moreover, providing feedback in such a manner may advantageously reduce unnecessary visual or audible interference in response to a voice input. For example, the user is not required to manually cause the non-selected devices to cease displaying and/or cease audible output, and visual interference with the user interfaces of the non-selected devices is minimized (e.g., if the user was previously interacting with the user interfaces of the non-selected devices). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing the amount of user input required to expect to perform a requested task), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

Fig. 10A-10V illustrate a user interface and a digital assistant user interface according to various examples. Fig. 10A to 10V are used to explain processes described below, including the processes in fig. 18A to 18B.

Fig. 10A shows a device 800. The device 800 displays a DA user interface 803 on the display 801 over the user interface. In fig. 10A, device 800 displays DA user interface 803 over home screen user interface 1001. In other examples, the user interface is another type of user interface, such as a lock screen user interface or an application specific user interface.

In some examples, DA user interface 803 includes an indicator 804 displayed at a first portion (e.g., an "indicator portion") of display 801 and a response affordance displayed at a second portion (e.g., a "response portion") of display 801. A third portion (e.g., a "UI portion") of the display 801 displays a portion of the user interface (the user interface on which the DA user interface 803 is displayed). For example, in FIG. 10A, a first portion of the display 801 displays the indicator 804, a second portion of the display 801 displays the response affordance 1002, and a third portion of the display 801 displays a portion of the home screen user interface 1001.

In some examples, device 800 receives user input corresponding to selection of the third portion of display 801 when DA user interface 803 is displayed over the user interface. The device 800 determines whether the user input corresponds to a first type of input or a second type of input. In some examples, the first type of user input includes a tap gesture and the second type of user input includes a drag or swipe gesture.

In some examples, in accordance with a determination that the user input corresponds to the first type of input, device 800 stops displaying DA user interface 803. The stop displaying DA user interface 803 includes stopping displaying any portion of the DA user interface 803, e.g., the indicator 804, the response affordance, and the conversation affordance (if included). In some examples, ceasing to display the DA user interface 803 includes replacing the display of the elements of the DA user interface 803 at their respective portions of the display 801 with the display of the user interface at the respective portions. For example, device 800 replaces display of indicator 804 with display of a first portion of the user interface at a first portion of display 801 and replaces display of the response affordance with display of a second portion of the user interface at a second portion of display 801.

For example, fig. 10B shows device 800 receiving user input 1003 (e.g., a tap gesture) corresponding to a selection of a third portion of display 801. The device 800 determines that the user input 1003 corresponds to a first type of input. Fig. 10C shows that, in accordance with such a determination, device 800 ceases to display DA user interface 803 and displays user interface 1001 in its entirety.

In this way, the user may dismiss the DA user interface 803 by providing an input selecting a portion of the display 801 that does not display any portion of the DA user interface 803. For example, in fig. 8S-8X above, a tap gesture selecting the portion of the display 801 that displays the home screen user interface 802 that is visually hidden causes the device 800 to revert to the display of fig. 8A.

In some examples, the user input corresponds to a selection of a selectable element displayed in the third portion of the display 801. In some examples, in accordance with a determination that the user input corresponds to a first type of input, device 800 displays a user interface corresponding to the selectable element. For example, device 800 replaces the display of the portion of the user interface (displayed at the third portion of display 801), the display of the response affordance, and the display of indicator 804 with the display of the user interface corresponding to the selectable element.

In some examples, the user interface is a home screen user interface 1001, the selectable element is an application affordance of the home screen user interface 1001, and the user interface corresponding to the selectable element is a user interface corresponding to the application affordance. For example, fig. 10D shows DA user interface 803 displayed over home screen user interface 1001. The display 801 displays an indicator 804 at a first portion, a response affordance 1004 at a second portion, and a portion of a user interface 1001 at a third portion. FIG. 10E illustrates device 800 receiving a user input 1005 (e.g., a tap gesture) selecting the wellness application affordance 1006 displayed in the third portion. FIG. 10F illustrates that in accordance with the device 800 determining that the user input 1005 corresponds to a first type of input, the device 800 ceases to display the indicator 804, the response affordance 1004, and the portion of the user interface 1001. The device 800 also displays a user interface 1007 corresponding to a wellness application.

In some examples, the selectable element is a link and the user interface corresponding to the selectable element is a user interface corresponding to the link. For example, fig. 10G shows DA user interface 803 displayed over web browsing application user interface 1008. The display 801 displays an indicator 804 at a first portion, a response affordance 1009 at a second portion, and a portion of a user interface 1008 at a third portion. Fig. 10G also shows that device 800 receives a user input 1010 (e.g., a tap gesture) that selects a link 1011 (e.g., a web page link) displayed in the third portion. FIG. 10H illustrates that, in accordance with the device 800 determining that the user input 1010 corresponds to a first type of input, the device 800 ceases to display the indicator 804, the response affordance 1009, and the portion of the user interface 1008. The device 800 also displays a user interface 1012 corresponding to the web page link 1011.

In this way, user input selecting the third portion of the display 801 may dismiss the DA user interface 803 and additionally cause an action to be performed (e.g., update the display 801) according to the content selected by the user.

In some examples, in accordance with a determination that the user input corresponds to a second type of input (e.g., a drag or swipe gesture), device 800 updates a display of the user interface at the third portion of display 801 in accordance with the user input. In some examples, when device 800 updates the display of the user interface at the third portion of display 801, device 800 continues to display at least some elements of DA user interface 803 at respective displayed portions of the elements of DA user interface. For example, device 800 displays (e.g., continues to display) the response affordance at a second portion of display 801. In some examples, device 800 also displays (e.g., continues to display) indicator 804 at the first portion of display 801. In some examples, updating the display of the user interface at the third portion includes scrolling content of the user interface.

For example, fig. 10I shows DA user interface 803 displayed over web browser application user interface 1013 displaying a web page. Display 801 displays indicator 804 at a first portion, response affordance 1014 at a second portion, and a portion of user interface 1013 at a third portion. FIG. 10I also shows that device 800 receives a user input 1015 to select the third portion (e.g., a drag gesture). Fig. 10J illustrates that, in accordance with device 800 determining that user input 1015 corresponds to a second type of input, device 800 updates (e.g., scrolls through) content of user interface 1013, such as scrolling through content of a web page, in accordance with user input 1015. 10I-10J illustrate that upon updating the user interface 1013 (at a third portion of the display 801), the device 800 continues to display the indicator 804 at the first portion of the display 801 and the response affordance 1014 at the second portion of the display 801.

As another example, fig. 10K shows DA user interface 803 displayed on home screen user interface 1001. The display 801 displays the indicator 804 at a first portion, the response affordance 1016 at a second portion, and a portion of the user interface 1001 at a third portion. Fig. 10K also shows that device 800 receives a user input 1017 (e.g., a swipe gesture) that selects the third portion. FIG. 10L illustrates the device 800 updating the contents of the user interface 1001 in accordance with the user input 1017, in accordance with the device 800 determining that the user input 1017 corresponds to a second type of input. For example, as shown, device 800 updates user interface 1001 to display a secondary home screen user interface 1018 that includes one or more application affordances that are different from the application affordance of home screen user interface 1001. 10K-10L illustrate that while updating the user interface 1001, the device 800 continues to display the indicator 804 at the first portion of the display 801 and the response affordance 1016 at the second portion of the display 801.

In this way, the user may provide input to update the user interface on which the DA user interface 803 is displayed without the input causing the DA user interface 803 to dismiss.

In some examples, updating the display of the user interface at the third portion of the display 801 is performed in accordance with a determination that the DA is in a listening state. Thus, the device 800 may enable a drag or swipe gesture to update the user interface (on which the DA user interface 803 is displayed) only when the DA is in a listening state. In such an example, if the DA is not in a listening state, in response to receiving a user input corresponding to the second type (and corresponding to selection of the third portion of the display 801), the device 800 does not update the display 801 or stop displaying the DA user interface 803 in response to the user input. In some examples, when the display of the user interface is updated while the DA is in a listening state, the display size of the indicator 804 varies based on the amplitude of the received speech input, as described above.

In some examples, device 800 receives the second user input when device 800 displays DA user interface 803 over the user interface. In some examples, in accordance with a determination that the second user input corresponds to a third type of input, device 800 stops displaying DA user interface 803. In some examples, the third type of input includes a swipe gesture originating from the bottom of the display 801 towards the top of the display 801. The third type of input is sometimes referred to as a "home swipe" because receipt of such input while device 800 displays a user interface different from the home screen user interface (and does not display DA user interface 803) causes device 800 to revert to display of the home screen user interface.

Fig. 10M shows device 800 displaying DA user interface 803 on top of home screen user interface 1001. DA user interface 803 includes a response affordance 1020 and an indicator 804. FIG. 10M also shows that device 800 receives user input 1019, i.e., a swipe gesture from the bottom of display 801 toward the top of display 801. FIG. 10N illustrates that the device 800 ceases to display the response affordance 1020 and the indicator 804 in accordance with the device 800 determining that the user input 1019 corresponds to a third type of input.

In some examples, the user interface (over which DA user interface 803 is displayed) is an application-specific user interface. In some examples, device 800 receives the second user input when device 800 displays DA user interface 803 over the application-specific user interface. In some examples, in accordance with a determination that the second user input corresponds to a third type of input, the device stops displaying the DA user interface 803 and additionally displays a home screen user interface. For example, FIG. 10O shows device 800 displaying DA user interface 803 on top of health application user interface 1022. DA user interface 803 includes a response affordance 1021 and an indicator 804. FIG. 10O also shows device 800 receiving user input 1023, a swipe gesture from the bottom of display 801 toward the top of display 801. Fig. 10P illustrates that, in accordance with device 800 determining that user input 1023 corresponds to a third type of input, device 800 displays home screen user interface 1001. For example, as shown, device 800 replaces display of indicator 804, response affordance 1021, and messaging application user interface 1022 with display of home screen user interface 1001.

In some examples, when device 800 displays DA user interface 803 over the user interface, device 800 receives a third user input corresponding to selection of the response affordance. In response to receiving the third user input, device 800 stops displaying DA user interface 803. For example, fig. 10Q shows DA user interface 803 displayed over home screen user interface 1001. DA user interface 803 includes a response affordance 1024, a dialog affordance 1025, and an indicator 804. FIG. 10Q also shows device 800 receiving a user input 1026 selecting a response affordance 1024 (e.g., a swipe or drag gesture upward). Fig. 10R shows that device 800 ceases to display DA user interface 803 in response to receiving user input 1026.

In some examples, when device 800 displays user interface 803 over the user interface, device 800 receives a fourth user input corresponding to a displacement of indicator 804 from the first portion of display 801 to an edge of display 801. In response to receiving the fourth user input, device 800 stops displaying DA user interface 803. For example, fig. 10S shows DA user interface 803 displayed over home screen user interface 1001. In fig. 10S, device 800 receives a user input 1027 (e.g., a drag or swipe gesture) that shifts an indicator from a first portion of display 801 to an edge of display 801. Fig. 10S-10V illustrate that in response to receiving user input 1027 (e.g., in response to indicator 804 reaching an edge of display 801), device 800 stops displaying DA user interface 803.

5. Digital assistant response mode

Fig. 11 illustrates a system 1100 for selecting a DA response mode and for presenting responses according to the selected DA response mode, according to various examples. In some examples, system 1100 is implemented on a stand-alone computer system (e.g., device 104, 122, 200, 400, 600, 800, 900, 902, or 904). The system 1100 is implemented using hardware, software, or a combination of hardware and software to perform the principles discussed herein. In some examples, the modules and functionality of system 1100 are implemented within a DA system, as described above with respect to fig. 7A-7C.

System 1100 is exemplary, and thus system 1100 may have more or fewer components than illustrated, may combine two or more components, or may have a different configuration or arrangement of components. Further, while the following discussion describes functions performed at a single component of the system 1100, it should be understood that such functions may be performed at other components of the system 1100, and that such functions may be performed at more than one component of the system 1100.

Fig. 12 illustrates a device 800 that presents responses to received natural language input according to different DA response modes, according to various examples. In fig. 12, for each instantiation of the device 800, the device 800 has initiated the DA and presented the "how weather" for the speech input according to the silent response mode, the mixed response mode, or the voice response mode described below? "is detected. The device 800 implementing the system 1100 selects a DA response mode and presents a response according to the selected response mode using techniques described below.

The system 1100 includes an acquisition module 1102. The retrieval module 1102 retrieves a response package in response to the natural language input. The response package includes content (e.g., chatable text) intended as a response to the natural language input. In some examples, the response package includes first text (content text) associated with a digital assistant response affordance (e.g., response affordance 1202) and second text (title text) associated with the response affordance. In some examples, the title text is less lengthy (e.g., includes fewer words) than the content text. The content text may provide a complete response to the user request, while the title text may provide a short (e.g., incomplete) response to the request. For a complete response to the request, the device 800 may present the title text and the response affordance simultaneously, e.g., while the presentation of the content text may not require a complete response in response to the presentation of the affordance.

For example, consider the natural language input "how weather? ". The content text is that the current air temperature is 70 ℃, the probability of raining is zero on a sunny day. Today the highest air temperature will reach 75 degrees and the lowest air temperature will reach 60 degrees ". The title text is simply "good weather today". As shown, the title text is intended to be presented with a response affordance 1202 that visually indicates information of the content text. Thus, presentation of the content text alone may fully answer the request, while presentation of both the title text and the response affordance may fully answer the request.

In some examples, the acquisition module 1102 locally acquires the response package, for example, by the device 800 processing the natural language input as described with respect to fig. 7A-7C. In some examples, the obtaining module 1102 obtains the response package from an external device, such as the DA server 106. In such examples, DA server 106 processes the natural language input as described with respect to fig. 7A-7C to determine the response package. In some examples, the obtaining module 1102 obtains a portion of the response packet locally and another portion of the response packet from the external device.

The system 1100 includes a mode selection module 1104. The selection module 1104 selects a DA response mode from a plurality of DA response modes based on context information associated with the device 800. The DA response mode specifies the manner (e.g., format) in which the DA presents a response to the natural language input (e.g., response package).

In some examples, after device 800 receives the natural language input, selection module 1104 selects the DA response mode, for example, based on current context information obtained after receiving the natural language input. In some examples, after the obtaining module 1102 obtains the response packet, the selecting module 1104 selects the DA response mode, for example, based on current context information obtained after obtaining the response packet. The current context information describes the context information when the selection module 1104 selects the DA response mode. In some examples, the time is after the natural language input is received and before the response to the natural language input is presented. In some examples, the plurality of DA response modes include a mute response mode, a mixed response mode, and a voice response mode, as will be discussed further below.

System 1100 includes a formatting module 1106. In response to the selection module 1104 selecting the DA response mode, the formatting module 1106 causes the DA to present the response package according to the selected DA response mode (e.g., in a format consistent with the selected DA response mode). In some examples, the selected DA response mode is a silent response mode. In some examples, presenting the response package according to the silent response mode includes displaying the response affordance and displaying the caption text without providing an audio output (and without providing the content text) that represents (e.g., speaks) the caption text. In some examples, the selected DA response mode is a hybrid response mode. In some examples, presenting the response package according to the hybrid response mode includes displaying the response affordance and speaking the title text, without displaying the title text (and without providing the context text). In some examples, the selected DA response mode is a voice response mode. In some examples, presenting the response package according to the voice response mode includes speaking content text, e.g., without presenting title text and/or without displaying the response affordance.

For example, in fig. 12, presenting the response package according to the silent response mode includes displaying the response affordance 1202, and displaying the heading text "weather today is good" in the dialog affordance 1204 without speaking the heading text. Presenting the response package according to the mixed response mode includes displaying the response affordance 1202 and speaking the heading text "weather today is good" without displaying the heading text. Presenting the response package according to the voice response mode includes speaking the content text "current air temperature 70 degrees, sunny day, rain probability is zero. Today the highest air temperature will reach 75 degrees and the lowest air temperature will reach 60 degrees ". Although fig. 12 shows the device 800 displaying the response affordance 1202 when presenting the response packet according to the voice response mode, in other examples, the response affordance is not displayed when presenting the response packet according to the voice response mode.

In some examples, when the DA presents a response according to the silent response mode, the device 800 displays the response affordance without displaying the dialog affordance (e.g., including text). In some examples, device 800 foregoes providing text in accordance with determining that the response affordance includes a direct answer to the natural language request. For example, device 800 determines that the headline text and the response affordance each include corresponding matching text that each answers the user request (thus presenting headline text redundancy). For example, for a natural language request "what is the temperature? If the response affordance includes the current temperature, then in the silent mode, the device 800 does not display any title text because the title text including the current temperature is redundant to the response affordance. In contrast, consider an exemplary natural language request "cold? A "response to request affordance may include the current temperature and weather state, but may not include a direct (e.g., explicit) answer to the request, such as" yes "or" no ". Thus, for such natural language input, in silent mode, device 800 displays a response affordance and includes a direct answer to the request, e.g., "no, no cold. "to the text of the title.

Fig. 12 illustrates that, in some examples, selecting the DA response mode includes determining whether to (1) display the heading text without speaking the heading text or (2) speak the heading text without displaying the heading text. In some examples, selecting the response mode includes determining whether to speak the content text.

Generally, a silent response mode may be appropriate when a user desires to view a display and does not desire audio output. The mixed response mode may be appropriate when the user desires to view the display and desires audio output. The voice response mode may be appropriate when the user does not desire (or is unable to) view the display. Various techniques for selecting the DA response mode and the contextual information selection module 1104 will now be discussed.

Fig. 13 illustrates an example process 1300 implemented by the selection module 1104 to select a DA response mode, in accordance with various examples. In some examples, selection module 1104 implements process 1300 as computer-executable instructions, for example, stored in a memory of device 800.

At block 1302, the selection module 1104 obtains (e.g., determines) current context information. At block 1304, module 1104 determines whether to select a speech mode based on the current context information. If module 1104 determines that a voice mode is selected, module 1104 selects a voice mode at block 1306. If module 1104 determines that a voice mode is not selected, process 1300 proceeds to block 1308. At block 1308, module 1104 selects between a mute mode and a hybrid mode. If module 1104 determines that the muting mode is selected, module 1104 selects the muting mode at block 1310. If module 1104 determines to select the hybrid mode, module 1104 selects the hybrid mode at block 1312.

In some examples, blocks 1304 and 1308 are implemented using a rule-based system. For example, at block 1304, module 1104 determines whether the current context information satisfies a particular condition for selecting a speech mode. If certain conditions are met, then module 1104 selects a voice mode. If a particular condition is not met (meaning that the current context information meets the conditions for selecting a hybrid mode or a voice mode), module 1104 proceeds to block 1308. Similarly, at block 1308, module 1104 determines whether the current context information satisfies a particular condition for selecting a muting mode or a mixing mode, and selects the muting mode or the mixing mode accordingly.

In some examples, blocks 1304 and 1308 are implemented using a probabilistic (e.g., machine learning) system. For example, at block 1304, module 1104 determines a probability of selecting a voice mode and a probability of not selecting a voice mode (e.g., a probability of selecting a silent mode or a mixed mode) based on the current context information, and selects the branch with the highest probability. At block 1308, module 1104 determines a probability of selecting a mixed mode and a probability of selecting a silent mode based on current context information, and selects the mode with the highest probability. In some examples, the sum of the voice mode, mixed mode, and silent mode probabilities is 1.

Various types of current context information for determining blocks 1304 and/or 1308 will now be discussed.

In some examples, the context information includes whether the device 800 has a display. In a rule-based system, it is determined that the device 800 does not have a display satisfying the conditions for selecting a voice mode. In a probabilistic system, determining that the device 800 does not have a display increases the probability of a speech mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode.

In some examples, the context information includes whether the device 800 detected a voice input (e.g., "hey, Siri") that initiated the DA. In a rule-based system, it is detected that a voice input initiating the DA satisfies a condition for selecting a voice mode. In a rule-based system, it is not detected that the voice input initiating the DA does not satisfy the conditions for selecting the voice mode (and thus the conditions for selecting the mixed mode or the silent mode). In a probabilistic system, in some examples, detecting a voice input that initiates a DA increases the probability of a voice mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, not detecting a voice input that initiates a DA reduces the probability of a voice mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the context information includes whether the device 800 detects physical contact with the device 800, the physical contact being used to initiate the DA. In a rule-based system, no physical contact is detected that satisfies the conditions for selecting a voice mode. In a rule-based system, it is detected that physical contact does not satisfy the conditions for selecting a voice mode. In a probabilistic system, in some examples, not detecting physical contact increases the probability of a voice mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, detecting physical contact reduces the probability of a voice mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the context information includes whether the device 800 is in a locked state. In a rule-based system, determining that device 800 is in a locked state satisfies the conditions for selecting a voice mode. In a rule-based system, determining that the device 800 is not in a locked state does not satisfy the conditions for selecting a voice mode. In a probabilistic system, determining that the device 800 is in a locked state increases the probability of a voice mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode, in some examples. In a probabilistic system, determining that the device 800 is not in a locked state reduces the probability of a voice mode and/or increases the probability of a mixed mode and increases the probability of a silent mode, in some examples.

In some examples, the context information includes whether a display of device 800 is being displayed prior to initiating the DA. In a rule-based system, it is determined that the display does not show satisfaction of a condition for selecting a voice mode prior to initiating a DA. In a rule-based system, it is determined that a display is displaying before initiating a DA does not satisfy a condition for selecting a voice mode. In a probabilistic system, in some examples, determining that the display does not show prior to initiating DA increases the probability of a speech mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, it is determined that the display is displaying before initiating DA reduces the probability of a speech mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the contextual information includes a display orientation of the device 800. In a rule-based system, it is determined that the display is facing down to satisfy the conditions for selecting the voice mode. In a rule-based system, it is determined that the condition for selecting a voice mode is not satisfied by the display facing upward. In a probabilistic system, in some examples, determining that the display is facing down increases the probability of a speech mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, determining that the display is facing up reduces the probability of voice mode and/or increases the probability of mixed mode and increases the probability of silent mode.

In some examples, the contextual information includes whether a display of the device 800 is obscured. For example, device 800 uses one or more sensors (e.g., light sensor, microphone, proximity sensor) to determine if the user cannot view the display. For example, the display may be located in an at least partially enclosed space (e.g., a pocket, bag, or drawer) or may be covered by an object. In a rule-based system, it is determined that the display is occluded to satisfy a condition for selecting a voice mode. In a rule-based system, determining that the display is not occluded does not satisfy the conditions for selecting a voice mode. In a probabilistic system, in some examples, determining that the display is occluded increases the probability of a speech mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, determining that the display is not occluded reduces the probability of a speech mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the context information includes whether device 800 is coupled to an external audio output device (e.g., headphones, bluetooth device, speaker). In a rule-based system, it is determined that the condition for selecting a voice mode is satisfied by the coupling of device 800 to an external device. In a rule-based system, determining that the device 800 is not coupled to an external device does not satisfy the conditions for selecting a voice mode. In a probabilistic system, in some examples, determining that device 800 is coupled to an external device increases the probability of a voice mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, determining that device 800 is not coupled to an external device reduces the probability of voice mode and/or increases the probability of mixed mode and increases the probability of silent mode, in some examples.

In some examples, the contextual information includes whether the direction the user gazed at is pointing at the device 800. In a rule-based system, it is determined that the direction in which the user gazes is not pointing at the device 800 satisfies the conditions for selecting the voice mode. In a rule-based system, it is determined that the direction pointing device 800 at which the user is gazing does not satisfy the conditions for selecting a voice mode. In a probabilistic system, determining that the direction the user is gazing is not pointing at the device 800 increases the probability of a voice mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode, in some examples. In a probabilistic system, in some examples, determining the direction the user gazes at pointing device 800 reduces the probability of voice mode and/or increases the probability of mixed mode and increases the probability of silent mode.

In some examples, the context information includes whether a predetermined type of gesture of the device 800 was detected within a predetermined duration of time before the response mode was selected. The predetermined types of gestures include, for example, lift and/or rotate gestures that cause device 800 to open a display. In a rule-based system, a predetermined type of gesture is not detected for a predetermined duration of time to satisfy the conditions for selecting a voice mode. In a rule-based system, it is detected that a predetermined type of gesture does not satisfy the conditions for selecting a voice mode for a predetermined duration. In a probabilistic system, in some examples, not detecting a gesture of a predetermined type for a predetermined duration increases the probability of a voice mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, detecting a gesture of a predetermined type for a predetermined duration reduces the probability of a speech mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the contextual information includes a direction of the natural language input. In a rule-based system, determining that the direction of the natural language input is not oriented toward the device 800 satisfies a condition for selecting a voice mode. In a rule-based system, it is determined that the direction of the natural language input is oriented toward the device 800 does not satisfy the conditions for selecting a voice mode. In a probabilistic system, in some examples, determining that the direction of the natural language input is not oriented toward the device 800 increases the probability of a speech mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, determining that the direction of the natural language input is oriented toward device 800 decreases the probability of a speech mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the context information includes whether the device 800 detected a touch performed on the device 800 (e.g., a user input of a selection response affordance) within a predetermined duration of time before the selection response mode. In a rule-based system, no touch is detected for a predetermined duration to satisfy the conditions for selecting a voice mode. In a rule-based system, a touch is detected for a predetermined duration that does not satisfy the conditions for selecting a speech mode. In a probabilistic system, in some examples, not detecting a touch for a predetermined duration increases the probability of a voice mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, detecting a touch for a predetermined duration reduces the probability of a voice mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the contextual information includes whether the natural language input is a typed input, e.g., as opposed to a spoken input. In a rule-based system, it is determined that the natural language input is not a typed input that satisfies a condition for selecting a voice mode. In a rule-based system, it is determined that the natural language input is a typed input that does not satisfy a condition for selecting a voice mode. In a probabilistic system, determining that the natural language input is not a typed input increases the probability of a speech mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode in some examples. In a probabilistic system, determining that the natural language input is a typed input reduces the probability of a speech mode and/or increases the probability of a mixed mode and increases the probability of a silent mode in some examples.

In some examples, the context information includes whether the device 800 received a notification (e.g., a text message, an email message, an application notification, a system notification) within a predetermined duration (e.g., 10, 15, 30 seconds) before the response mode was selected. In a rule-based system, the condition for selecting a voice mode is satisfied by not receiving a notification for a predetermined duration. In a rule-based system, receiving a notification within a predetermined duration of time does not satisfy the conditions for selecting a voice mode. In a probabilistic system, in some examples, failure to receive a notification for a predetermined duration increases the probability of a speech mode being fired and/or decreases the probability of a mixed mode and decreases the probability of a silent mode. In a probabilistic system, in some examples, receiving a notification within a predetermined duration reduces the probability of a voice mode and/or increases the probability of a mixed mode and increases the probability of a silent mode.

In some examples, the context information includes an ambient noise level detected by the device 800. An ambient noise level above a threshold may indicate that the user is unable to hear the audio output, for example, because the user is in a noisy environment. Thus, detecting an ambient noise level above a threshold may recommend selecting a silent mode (since the device 800 will provide audio output in both the voice mode and the mixed mode). Thus, in a rule-based system, it is determined that the ambient noise level is below a threshold satisfies a condition for selecting a speech mode, satisfies a condition for selecting a hybrid mode (at block 1308), and does not satisfy a condition for selecting a silence mode (at block 1308). In a rule-based system, it is determined that the ambient noise level above the threshold does not satisfy the conditions for selecting the speech mode, does not satisfy the conditions for selecting the hybrid mode (block 1308), and satisfies the conditions for selecting the silence mode (block 1308). In a probabilistic system, in some examples, determining that the ambient noise level is below a threshold increases the probability of a speech mode, increases the probability of a mixed mode, and decreases the probability of a silence mode. In a probabilistic system, in some examples, determining that the ambient noise level is above a threshold reduces the probability of a speech mode, reduces the probability of a mixed mode, and increases the probability of a silence mode.

In some examples, the contextual information includes whether the natural language input corresponds to a low-pitched input. The user's low-pitched natural language speech input may indicate that the user does not desire audio output, for example, because the user is in a quiet environment, such as a movie theater. Thus, determining that the natural language input corresponds to a low-sound input may recommend selecting a silent mode. Thus, in a rule-based system, it is determined that the natural language input does not correspond to a bass input that satisfies the conditions for selecting a speech mode, satisfies the conditions for selecting a hybrid mode (at block 1308), and does not satisfy the conditions for selecting a silence mode (at block 1308). In a rule-based system, it is determined that the natural language input corresponds to a bass input that does not satisfy the conditions for selecting a speech mode, does not satisfy the conditions for selecting a hybrid mode (block 1308), and satisfies the conditions for selecting a silence mode (block 1308). In a probabilistic system, in some examples, determining that the natural language input does not correspond to a low-voice input increases the probability of a speech mode, increases the probability of a mixed mode, and decreases the probability of a silent mode. In a probabilistic system, in some examples, determining that the natural language input corresponds to a low-pitched input reduces the probability of a speech mode, reduces the probability of a mixed mode, and increases the probability of a silent mode.

In some examples, the context information includes whether the user's schedule information indicates that the user is busy (e.g., in a meeting). Schedule information indicating that the user is busy may recommend selecting a silent mode. Thus, in a rule-based system, it is determined that the schedule information indicates that the user is not busy satisfying the conditions for selecting the voice mode, satisfying the conditions for selecting the mixed mode (at block 1308), and not satisfying the conditions for selecting the silent mode (at block 1308). In a rule-based system, it is determined that the schedule information indicates that the user is busy not meeting the conditions for selecting the voice mode, not meeting the conditions for selecting the mixed mode (block 1308), and meeting the conditions for selecting the silent mode (block 1308). In a probabilistic system, in some examples, determining that the schedule information indicates that the user is not busy increases the probability of a voice mode, increases the probability of a mixed mode, and decreases the probability of a silent mode. In a probabilistic system, in some examples, it is determined that the schedule information indicates that the user is busy reducing the probability of a voice mode, reducing the probability of a mixed mode, and increasing the probability of a silent mode.

In some examples, the context information includes whether the device 800 is in a vehicle. In some examples, the device 800 determines whether the device is in the vehicle by detecting pairing with the vehicle (e.g., CarPlay via bluetooth or via Apple inc.) or by determining activation of a setting that indicates the device 800 is in the vehicle (e.g., a do not disturb while driving setting). In some examples, the device 800 uses the position and/or speed of the device 800 to determine whether it is in a vehicle. For example, data indicating that device 800 is traveling 65 miles per hour on a highway may indicate that device 800 is in a vehicle.

In a rule-based system, it is determined that the device 800 satisfies the conditions for selecting a voice mode in the vehicle. In a rule-based system, it is determined that the device 800 is not in a vehicle and does not satisfy the conditions for selecting a voice mode. In a probabilistic system, in some examples, the determination device 800 increases the probability of voice mode and/or decreases the probability of mixed mode and decreases the probability of silent mode in the vehicle. In a probabilistic system, in some examples, determining that the device 800 is not in a vehicle reduces the probability of voice mode and/or increases the probability of mixed mode and increases the probability of silent mode.

Fig. 14 illustrates a device 800 that presents a response according to a voice response pattern when a user is determined to be in a vehicle (e.g., driving), according to various examples. As shown, device 800 displays DA user interface 803 on top of driving user interface 1400. To minimize visual distraction while the user is driving, the DA user interface 803 does not include a response affordance and only includes the indicator 804. In response to the natural language input "how much weather? ", DA says the content text" the current air temperature is 70 ℃, the probability of raining is zero on a sunny day. Today the highest air temperature will reach 75 degrees and the lowest air temperature will reach 60 degrees ". Thus, the DA may respond to the user's request in a manner that reduces visual distraction while the user is driving.

In some examples, the context information includes whether the device 800 is executing a predetermined type of application. In some examples, the predetermined type of application includes a navigation application. In a rule-based system, it is determined that the device 800 is executing a predetermined type of application that satisfies the conditions for selecting a voice mode. In a rule-based system, it is determined that the condition for selecting a speech mode is not satisfied by the device 800 not executing a predetermined type of application. In a probabilistic system, determining that device 800 is executing a predetermined type of application increases the probability of a speech mode and/or decreases the probability of a mixed mode and decreases the probability of a silent mode, in some examples. In a probabilistic system, determining that the device 800 is not executing a predetermined type of application reduces the probability of a speech mode and/or increases the probability of a mixed mode and increases the probability of a silent mode in some examples.

Fig. 15 illustrates a device 800 that presents responses according to a voice response mode when the device 800 is executing a navigation application according to various examples. As shown, the device 800 displays a DA user interface 803 on top of the navigation application user interface 1500. To minimize visual interference with the user interface 1500, the DA user interface 803 does not include a response affordance (or dialog affordance) and only includes the indicator 804. In response to the natural language input "how much weather? ", DA says the content text" the current air temperature is 70 ℃, the probability of raining is zero on a sunny day. Today the highest air temperature will reach 75 degrees and the lowest air temperature will reach 60 degrees ". Thus, the DA may respond to the user's request in a manner that reduces visual interference with the executing navigation application.

Returning to FIG. 13, at block 1308, module 1104 selects between a mute mode and a hybrid mode. In some examples, module 1104 selects a mode that has met certain conditions (recall that execution block 1304 may also determine whether current context information meets conditions for selecting a hybrid mode or conditions for selecting a silent mode). In some examples, module 1104 selects the mode with the highest probability (recall that execution block 1304 may determine the respective probabilities of the silent mode and the mixed mode). In some examples, at block 1308, module 1104 selects between a silent mode and a hybrid mode based on current context information, as described below.

In some examples, the context information includes DA voice feedback settings indicating whether the DA should provide audio output in response to a user request. In some examples, the voice feedback setting indication (e.g., always) provides voice feedback. In a rule-based system, determining that the voice feedback setting indicates that the voice feedback to be provided satisfies a condition for selecting a mixed mode and does not satisfy a condition for selecting a silent mode. In a probabilistic system, in some examples, determining that the voice feedback setting indicates that voice feedback is to be provided increases the probability of a mixed mode and decreases the probability of a silent mode.

In some examples, the DA voice feedback setting indicates that voice feedback is controlled with a switch (e.g., a ring tone device switch) of device 800. For example, the voice feedback setting indicates that voice feedback is provided when the ring device switch is open and that voice feedback is not provided when the ring device switch is closed. In such an example, in a rule-based system, it is determined that the ringtone device switch on (the voice feedback setting indicates that voice feedback is to be provided) satisfies the conditions for selecting the mixed mode and does not satisfy the conditions for selecting the silent mode. In a rule-based system, it is determined that the ringtone device switch off (voice feedback setting indicates that no voice feedback is provided) satisfies the conditions for selecting the silent mode and does not satisfy the conditions for selecting the mixed mode. In a probabilistic system, in some examples, determining that the ring device switch is open increases the mixed mode probability and decreases the silent mode probability. In a probabilistic system, determining that the ring device switch is off reduces the mixed mode probability and increases the silent mode probability in some examples.

In some examples, the DA voice feedback setting indicates that voice feedback is to be provided in a "hands-free" context. For example, the DA voice feedback settings specify that voice feedback is only provided if the DA or device is initiated using voice input to couple/pair with an external device (e.g., a headset, a bluetooth device, or a device that implements caroplay of Apple inc.). In some examples, determining that the voice feedback settings indicate that voice feedback is to be provided in a "hands-free" context causes module 1104 to determine whether device 800 detects physical contact initiating a DA. In a rule-based system, the determination device 800 detects that the physical contact satisfies the condition for selecting the silent mode and does not satisfy the condition for selecting the mixed mode. In a rule-based system, it is determined that the device 800 does not detect that physical contact satisfies the conditions for selecting the mixed mode and does not satisfy the conditions for selecting the silent mode. In a probabilistic system, in some examples, determining that the device 800 detects physical contact increases the silent mode probability and decreases the mixed mode probability. In a probabilistic system, determining that device 800 does not detect physical contact reduces the silent mode probability and increases the mixed mode probability in some examples. In some examples, determining that the voice feedback setting does not indicate that voice feedback is to be provided in a "hands-free" context causes module 1104 to select a mixed mode or silent mode (e.g., to control voice feedback with a ring device switch or always provide voice feedback) according to another voice feedback setting, as described above.

In some examples, in a rule-based system, module 1104 selects a particular DA response mode even if one or more conditions for selecting the particular mode are not met (or are not determined), e.g., as long as other conditions for selecting the particular mode are met. In some examples, the conditions for selecting a particular mode are sequential. For example, after module 1104 determines that the context information does (or does not) satisfy a condition for selecting a particular mode, module 1104 determines whether the context information satisfies another condition for selecting a particular mode, and so on, to select a particular mode. In some examples, certain conditions for selecting a particular mode are prioritized over other conditions, e.g., such that if certain conditions are met, module 1104 selects the particular mode regardless of whether other conditions are met. The particular conditions and sequences under which the various conditions are met (or not met) to select a particular mode may vary according to various implementations of the module 1104. For example, if device 800 is determined to be in a vehicle, module 1104 selects the voice response mode even if device 800 detects physical contact initiating the DA that satisfies the conditions for selecting the mixed mode or silent mode instead of the voice mode.

In some examples, the particular type of context information is not determined in the probabilistic system. In some examples, in a probabilistic system, the amount by which module 1104 increases or decreases the respective response mode probability varies based on the particular type of contextual information being considered, e.g., such that different types of contextual information have different weights when a particular response mode is selected. For example, module 1104 increases the probability of the particular mode by a first amount in response to determining that the first context information indicates an increase in the probability and increases the probability by a second, different amount in response to determining that the second, different context information indicates an increase in the probability. As a specific example, the determination device 800 is in the vehicle and increases the voice pattern probability by a larger amount, while the determination device 800 is in the locked state and increases the voice pattern probability by a smaller amount. In some examples, module 1104 selects a particular mode when the probability of the mode exceeds a threshold. In some examples, the particular type of context information does not affect the probability of the particular mode, e.g., such that the context information has no weight when the particular mode is selected. For example, contextual information indicating that the device 800 did not receive a voice input originating the DA does not affect the probability of selecting a voice mode, a mixed mode, and a silent mode, or a sub-combination thereof.

It should be appreciated that process 1300 is exemplary and not limiting of the manner in which module 1104 may select a response mode. Accordingly, the present disclosure contemplates other ways of selecting a response mode based on the context information described above. For example, rather than first determining whether to select a voice mode, module 1104 concurrently determines respective probabilities of a voice mode, a silence mode, and a mixed mode based on context information. As another example, module 1104 implements a decision tree or flow diagram to select a response mode based on whether the context information satisfies a particular condition in a manner consistent with the teachings herein. The particular configuration of the decision tree or flow diagram may vary depending on various implementations of the module 1104.

In some examples, the selected DA response mode changes throughout the multi-turn DA interaction. The multi-turn DA interaction describes an interaction in which a user provides a first natural language input to the DA and the DA presents a response requesting further user input. Thus, in some examples, the device 800 receives a first natural language input, and the DA presents a first response package according to a first selected response mode (in response to the first natural language input). Presenting the first response package includes requesting further user input. Thus, after presenting the first response package, the device 800 receives the second natural language input in response to the presentation of the first response package. The device 800 retrieves a second response package in response to the second natural language input. After receiving the second natural language input, device 800 further selects a second DA response mode (different from the first DA response mode) from the plurality of DA response modes. In response to selecting the second response mode, the DA presents a second response packet according to the second response mode.

FIG. 16 illustrates a change in response pattern throughout a multi-turn DA interaction, according to various examples. In FIG. 16, at time T1, the user has initiated the DA and provided a first speech input "Send message to Sam". The device 800 retrieves a first response packet in response to the first voice input. The first response package includes the content text "what do you want to say in the message to Sam? "and title text" what to say? ". Device 800 also selects the hybrid response mode, e.g., because the user initiated the DA by physically touching device 800 and/or the DA voice feedback settings of device 800 indicated that voice feedback is to be provided. Thus, at time T2, the DA presents the first response packet according to the hybrid response pattern. Specifically, the device 800 speaks the headline text "what is said? ", and displays a response affordance 1600 indicating a message to Sam.

At time T3, the user has placed the display of device 800 face down on the table and provided a second speech input, "what was dinner? ". The device 800 retrieves a second response packet in response to the second voice input. The second response packet includes the header text "is this your message, ready to send? "and the content text" do you say 'what dinner did you give Sam' message? Is' ready to send? ". The device 800 also selects the voice response mode, e.g., because the display of the device 800 is facing down after receiving the second speech input. Therefore, at time T4, the DA presents the second response packet according to the voice response mode. Specifically, device 800 speaks content text (not title text) "do you say 'what dinner did you say to Sam' message? Is' ready to send? ".

In this way, the DA may respond intelligently in a manner appropriate to the current context of the device 800. For example, at time T2, the blend mode is appropriate because the user can view the display 801. Thus, at time T2, the response affordance 1600 visually indicates a message to Sam, while the DA does not audibly indicate a message to Sam, as the device 800 simply says "what? ". The DA does not speak the longer content text (message indicated to Sam), thus improving interaction efficiency. However, at time T4, the user cannot view the display 801. Because the user cannot visually confirm the message content, the DA does not merely present the headline text "is this your message, ready to send? ". Instead, the DA speaks more content text of the message to audibly confirm the message content.

6. Process for operating a digital assistant

Fig. 17A-17F illustrate a process 1700 for operating a digital assistant, according to various examples. Process 1700 is performed, for example, using one or more electronic devices implementing a digital assistant. In some examples, process 1700 is performed using a client-server system (e.g., system 100), and the blocks of process 1700 are divided in any way between a server (e.g., DA server 106) and a client device (e.g., devices 800, 900, 902, or 904). In other examples, the blocks of process 1700 are divided between a server and multiple client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1700 are described herein as being performed by a particular device of a client-server system, it should be understood that process 1700 is not so limited. In other examples, process 1700 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1700, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1700.

Generally, process 1700 is illustrated using fig. 8A-8 CT, as described above. However, it should be understood that the other figures described above may be equally applicable to the process 1700.

At block 1701, a user input is received while a user interface (e.g., user interface 802 in fig. 8A) other than a digital assistant user interface is displayed (e.g., at display 801).

At block 1702, in accordance with a determination that the user input satisfies the criteria for initiating the digital assistant: a digital assistant user interface (e.g., DA user interface 803 in fig. 8F) is displayed over the user interface. The digital assistant user interface includes a digital assistant indicator (e.g., indicator 804 in fig. 8F) displayed at a first portion of the display and a response affordance (e.g., response affordance 805 in fig. 8F) displayed at a second portion of the display. A portion of the user interface remains visible at the third portion of the display. In some examples, the third portion is located between the first portion and the second portion. In some examples, the portion of the user interface is displayed at a third portion of the display prior to receiving the user input. In some examples, the user interface is a home screen user interface (e.g., user interface 802 in fig. 8A) or an application-specific user interface (e.g., user interface 809 in fig. 8J).

In some examples, the response affordance (e.g., response affordance 805 in fig. 8G) is displayed in a first state. In some examples, at block 1703, a second user input (e.g., input 806 in fig. 8G) corresponding to selection of the response affordance is received while the digital assistant user interface is displayed over the user interface. In some examples, at block 1704, in response to receiving the second user input, the display of the response affordance in the first state is replaced with the display of the response affordance in the second state (e.g., the response affordance 805 in fig. 8H). In some examples, the first state is a compact state and the second state is an expanded state.

In some examples, at block 1705, while displaying the response affordance in the second state, a third user input requesting that the response affordance be displayed in the first state is received. In some examples, at block 1706, in response to receiving the third user input, the display of the response affordance in the second state is replaced with the display of the response affordance in the first state.

In some examples, at block 1707, while the response affordance is displayed in the second state, a fourth user input (e.g., input 808 in fig. 8I) is received corresponding to selection of the response affordance. In some examples, at block 1708, in response to receiving the fourth user input, a user interface (e.g., user interface 809 in fig. 8J) corresponding to the application represented in the response affordance is displayed.

In some examples, the second user input corresponds to a selection of a first portion of the response affordance (e.g., a selected portion of the response affordance 805 in fig. 8G). In some examples, at block 1709, while displaying a digital assistant user interface over the user interface that includes the response affordance displayed in the first state, a fifth user input (e.g., input 812 in fig. 8M) is received that corresponds to a selection of a second portion of the response affordance. In some examples, at block 1710, in response to receiving the fifth user input, a second user interface (e.g., user interface 809 in fig. 8N) corresponding to the second application represented in the response affordance is displayed. In some examples, at block 1711, a selectable digital assistant indicator (e.g., indicator 810 in fig. 8N) is displayed while displaying the second user interface of the second application.

In some examples, the response affordance (e.g., response affordance 816 in fig. 8Q) includes a selectable element (e.g., selectable element 817 in fig. 8Q). In some examples, at block 1712, a user input (e.g., input 818 in fig. 8R) corresponding to the selection of the selectable element is received. In some examples, at block 1713, in response to receiving user input corresponding to selection of the selectable element, an affordance corresponding to the selectable element is displayed over the response affordance (e.g., the affordances 819 in fig. 8S). In some examples, at block 1714, the user interface at the third portion of the display (e.g., user interface 802 in fig. 8S) is visually obscured when the affordance corresponding to the selectable element is displayed over the response affordance.

In some examples, the user interface includes an input field (e.g., input field 826 in fig. 8Z) that occupies a fourth portion of the display. In some examples, at block 1715, a sixth user input (e.g., input 828 in fig. 8AB through 8AC) is received corresponding to the response affordance representing a displacement from the first portion of the display to the fourth portion of the display. In some examples, at block 1716, in response to receiving the sixth user input, the display of the response affordance at the first portion of the display is replaced with the display of the response affordance in the input field (e.g., fig. 8 AD). In some examples, the input field corresponds to a messaging application, an email application, or a note-taking application. In some examples, at block 1717, the response affordance is continuously shifted from the first portion of the display to a fourth portion of the display (e.g., fig. 8AB through 8AC) upon receiving the sixth user input. In an example, at block 1718, the digital assistant indicator ceases to be displayed while the response affordance is continuously shifted.

In some examples, the user interface includes a desktop applet area (e.g., desktop applet area 832 in fig. 8 AG) that occupies a fifth portion of the display. In some examples, at block 1719, a seventh user input (e.g., user input 834 in fig. 8 AH-8 AI) is received corresponding to the response affordance representing a displacement from the first portion of the display to the fifth portion of the display. In some examples, at block 1720, in response to receiving the seventh user input, replacing the display of the response affordance at the first portion of the display with the display of the response affordance in the desktop applet region (e.g., fig. 8 AJ). In some examples, the response affordance corresponds to an event. In some examples, at block 1721, completion of the event is determined. In some examples, at block 1722, in response to determining completion of the event, display of the response affordance in the desktop applet region is stopped.

In some examples, at block 1723, a natural language input is received and the response affordance corresponds to a response of the digital assistant to the natural language input. In some examples, the digital assistant determines a plurality of results corresponding to the natural language input, and the response affordance includes a single result of the plurality of results (e.g., response affordance 839 in fig. 8 AO). In some examples, the response affordance includes an editable text field including text determined from the natural language input (e.g., the editable text field 850 in fig. 8 AR).

In some examples, the digital assistant user interface includes a dialog affordance (e.g., dialog affordance 863 in fig. 8 BM). In some examples, at block 1724, a dialog affordance is displayed at a sixth portion of the display. In some examples, the sixth portion is located between the first portion and the second portion. In some examples, the dialog affordance includes a dialog generated by the digital assistant in response to a natural language input.

In some examples, at block 1725, a plurality of selectable disambiguation options for the natural language input are determined by the digital assistant. In some examples, the dialog includes the plurality of selectable disambiguation options (e.g., options 865 and 866 in fig. 8 BL).

In some examples, at block 1726, a primary user intent is determined based on the natural language input. In some examples, the response affordance corresponds to a primary user intent (e.g., response affordance 870 in fig. 8 BN). In some examples, at block 1727, an alternative user intent is determined based on the natural language input. In some examples, the dialog includes a selectable option corresponding to an alternative user intent (e.g., option 872 in fig. 8 BN).

In some examples, the dialog affordance is displayed in a third state (e.g., dialog affordance 873 in fig. 8 BO). In some examples, at block 1728, an eighth user input (e.g., user input 874 in fig. 8 BP-8 BR) corresponding to selection of a dialog affordance is received. In some examples, at block 1729, in response to receiving the eighth user input, the display of the dialog affordance in the third state is replaced with the display of the dialog affordance in the fourth state (e.g., the dialog affordance in fig. 8BQ, 8BR, 8BS, or 8 BT). In some examples, the fourth state corresponds to a maximum size of the dialog affordance. In some examples, when the dialog affordance is displayed in the fourth state, the user input is enabled to scroll through content of the dialog affordance (e.g., fig. 8 BS).

In some examples, the display of the dialog affordance in the fourth state occupies at least a portion of the first portion of the display (e.g., fig. 8 BR-8 BT). In some examples, at block 1730, displaying the dialog affordance in the fourth state includes displaying the dialog affordance over at least a third portion of the response affordance (e.g., fig. 8BR through 8 BT).

In some examples, prior to receiving the eighth user input, the response affordance (e.g., response affordance 875 in fig. 8 BO) is displayed in a fifth state. In some examples, displaying the dialog affordance in the fourth state at block 1731 includes replacing display of the response affordance in the fifth state with display of a response affordance in the sixth state (e.g., the response affordance 875 of fig. 8 BR-8 BT).

In some examples, the fourth state corresponds to a second maximum size of the dialog affordance. In some examples, when the dialog affordance is displayed in the fourth state, a fourth portion of the response affordance remains visible (e.g., fig. 8 BS-8 BT).

In some examples, at block 1732, a ninth user input (e.g., input 877 in fig. 8BT) is received corresponding to selection of the fourth portion of the response affordance. In some examples, at block 1733, in response to receiving the ninth user input, the display of the dialog affordance in the fourth state is replaced with the display of the dialog affordance in the seventh state (e.g., dialog affordance 873 in fig. 8 BU). In some examples, at block 1734, in response to receiving the ninth user input, a response affordance (e.g., response affordance 875 in fig. 8 BU) is displayed at the first portion of the display.

In some examples, at block 1735, a tenth user input corresponding to selection of the dialog affordance is received (e.g., input 883 in fig. 8 BX) while the dialog affordance is displayed in the fourth state. In some examples, at block 1736, in response to receiving the tenth user input, the display of the dialog affordance in the eighth state (e.g., the dialog affordance 882 in fig. 8 BY) is replaced with the display of the dialog affordance in the fourth state.

In some examples, at block 1737, while the dialog affordance is displayed in the fourth state, an eleventh user input (e.g., input 880 in fig. 8 BV) is received corresponding to selection of a response affordance. In some examples, at block 1738, in response to receiving the eleventh user input, the display of the dialog affordance in the fourth state is replaced with the display of the dialog affordance in the ninth state (e.g., the dialog affordance 879 in fig. 8 BW).

In some examples, the natural language input is a natural language speech input. In some examples, at block 1739, a transcription of the natural language speech input is displayed in the dialog affordance (fig. 8 BZ).

In some examples, the natural language speech input is subsequent to a second natural language speech input received prior to the natural language speech input. In some examples, at block 1740, the display transcription is performed in accordance with a determination that the digital assistant is unable to determine the user intent of the natural language speech input and unable to determine a second user intent of a second natural language speech input (e.g., fig. 8 CA-8 CC).

In some examples, at block 1741, display transcription is performed in accordance with a determination that the natural language speech input repeats a previous natural language speech input (e.g., fig. 8CD through fig. 8 CF).

In some examples, at block 1742, after receiving the natural language speech input, a second natural language speech input is received that is subsequent to the natural language speech input. In some examples, at block 1743, the display transcription is performed in accordance with a determination that the second natural language speech input indicates a speech recognition error (e.g., fig. 8CG through fig. 8 CI).

In some examples, the digital assistant results are presented at a first time. In some examples, at block 1744, in accordance with a determination that the digital assistant result corresponds to a predetermined type of digital assistant result, automatically ceasing to display the digital assistant user interface for a predetermined duration after the first time (e.g., fig. 8 CM-fig. 8 CN).

The operations described above with reference to fig. 17A-17F are optionally implemented by the components depicted in fig. 1-4, 6A-6B, 7A-7C, and 8A-8 CT. For example, the operations of the process 1700 may be implemented by the device 800. Those of ordinary skill in the art will clearly know how to implement other processes based on the components depicted in fig. 1-4, 6A-6B, and 7A-7C.

Note that the details of process 1700 described above with respect to fig. 17A-17F also apply in a similar manner to process 1800 described below. For example, the process 1800 optionally includes one or more of the features of the process 1700 described above (and vice versa). For example, when interacting with a user interface described below with respect to process 1800, a user can provide one or more inputs to interact with a digital assistant user interface, as described with respect to process 1700. For the sake of brevity, these details are not repeated in the following.

7. Process for operating a digital assistant

Fig. 18A-18B illustrate a process 1800 for operating a digital assistant, according to various examples. Process 1800 is performed, for example, using one or more electronic devices implementing a digital assistant. In some examples, process 1800 is performed using a client-server system (e.g., system 100), and the blocks of process 1800 are divided in any way between a server (e.g., DA server 106) and a client device (e.g., devices 800, 900, 902, or 904). In other examples, the blocks of process 1800 are divided between a server and multiple client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1800 are described herein as being performed by a particular device of a client-server system, it should be understood that process 1800 is not so limited. In other examples, process 1800 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1800, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1800.

Generally, process 1800 is illustrated using fig. 10A-10V, as described above. However, it should be understood that the other figures described above may be equally applicable to process 1800.

At block 1801, a digital assistant user interface (e.g., user interface 803 in fig. 10A) is displayed over a user interface (e.g., user interface 1001 in fig. 10A). The digital assistant user interface includes a digital assistant indicator (e.g., indicator 804 in fig. 10A) displayed at a first portion of the display and a response affordance (e.g., response affordance 1002 in fig. 10A) displayed at a second portion of the display.

At block 1802, while displaying the digital assistant user interface over the user interface, a user input (e.g., input 1003 in fig. 10B or input 1015 in fig. 10I) corresponding to a selection of a third portion of the display is received. The third portion displays a portion of the user interface. In some examples, the user interface is different from a digital assistant user interface.

At block 1803, in accordance with a determination that the user input corresponds to a first type of input (e.g., input 1003 in fig. 10B), display of the digital assistant indicator and the response affordance (e.g., fig. 10C) is ceased. In some examples, the first type of input includes a tap gesture. In some examples, at block 1804, ceasing to display the digital assistant indicator and responding to the affordance includes replacing, at the first portion of the display, display of the digital assistant indicator with display of the first portion of the user interface. In some examples, at block 1805, ceasing to display the digital assistant indicator and the response affordance includes replacing, at the second portion of the display, display of the response affordance with display of the second portion of the user interface.

In some examples, the user input corresponds to a selection of a selectable element displayed in the third portion of the display (e.g., selectable element 1006 in fig. 10E or selectable element 1011 in fig. 10G). In some examples, at block 1806, in accordance with a determination that the user input corresponds to the first type of input, a user interface corresponding to the selectable element is displayed (e.g., user interface 1007 in fig. 10F or user interface 1012 in fig. 10H). In some examples, at block 1807, displaying the user interface corresponding to the selectable element includes replacing the display of the portion of the user interface, the display of the response affordance, and the display of the digital assistant indicator with the display of the user interface corresponding to the selectable element.

In some examples, the selectable element is a link (e.g., link 1011 in fig. 10G), and the user interface corresponding to the selectable element is a user interface corresponding to the link (user interface 1012 in fig. 10H). In some examples, the user interface is a home screen user interface (e.g., user interface 1001 in fig. 10E), the selectable element is an application affordance of the home screen user interface (e.g., application affordance 1006 in fig. 10E), and the user interface corresponding to the selectable element is a user interface corresponding to the application affordance (e.g., user interface 1007 in fig. 10F).

In some examples, at block 1808, in accordance with a determination that the user input corresponds to a second type of input (e.g., input 1015 in fig. 10I) different from the first type of input, while the response affordance is displayed at the second portion, a display of the user interface at a third portion is updated in accordance with the user input (e.g., fig. 10J). In some examples, the second type of input includes a drag gesture. In some examples, at block 1809, updating the display of the user interface at the third portion includes scrolling content of the user interface (e.g., fig. 10I-10J and 10K-10L). In some examples, at block 1810, updating the display of the user interface at the third portion is performed while the digital assistant indicator is displayed at the first portion (e.g., fig. 10I-10J and 10K-10L). In some examples, updating the display of the user interface at the third portion is performed further in accordance with a determination that the digital assistant corresponding to the digital assistant user interface is in the listening state.

In some examples, at block 1811, a second user input (e.g., input 1019 in fig. 10M or input 1023 in fig. 10O) is received while the digital assistant user interface is displayed over the user interface. In some examples, at block 1812, in accordance with a determination that the second user input corresponds to a third type of input, ceasing to display the response affordance and the digital assistant indicator (e.g., fig. 10M-10N or fig. 10O-10P). In some examples, the user interface is an application-specific user interface (e.g., user interface 1022 in fig. 10O). In some examples, at block 1813, in accordance with a determination that the second user input corresponds to a third type of input, a home screen user interface (e.g., user interface 1001 in fig. 10P) is displayed.

In some examples, at block 1814, a third user input (e.g., input 1026 in fig. 10Q) corresponding to the selection of the response affordance is received while the digital assistant user interface is displayed on the user interface. In some examples, at block 1815, in response to receiving the third user input, the response affordance and the digital assistant indicator (e.g., fig. 10R) cease to be displayed.

The operations described above with reference to fig. 18A-18B are optionally implemented by the components depicted in fig. 1-4, 6A-6B, 7A-7C, and 10A-10V. For example, the operations of process 1800 may be implemented by device 800. Those of ordinary skill in the art will clearly know how to implement other processes based on the components depicted in fig. 1-4, 6A-6B, and 7A-7C.

Note that the details of process 1800 described above with respect to fig. 18A-18B also apply in a similar manner to process 1900 described below. For example, process 1900 optionally includes one or more of the features of process 1800 described above (and vice versa). For example, when the digital assistant presents a response according to the selected digital assistant response mode, the user can provide one or more inputs to interact with the digital assistant user interface (as described with respect to process 1800), as described below with respect to process 1900. For the sake of brevity, these details are not repeated in the following.

8. Process for selecting a digital assistant response mode

Fig. 19A-19E illustrate a process 1900 for selecting a digital assistant response mode, according to various examples. Process 1900 is performed, for example, using one or more electronic devices implementing a digital assistant. In some examples, process 1900 is performed using a client-server system (e.g., system 100), and the blocks of process 1900 are divided in any way between a server (e.g., DA server 106) and a client device (e.g., devices 800, 900, 902, or 904). In other examples, the blocks of process 1900 are divided between a server and multiple client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1900 are described herein as being performed by a particular device of a client-server system, it should be understood that process 1900 is not so limited. In other examples, process 1900 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1900, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1900.

Generally, process 1900 is illustrated using fig. 11-16, as described above. However, it should be understood that the other figures described above may be equally applicable to process 1900.

At block 1901, a natural language input is received (e.g., by device 800).

At block 1902, a digital assistant is initiated (e.g., by device 800).

At block 1903, a response package is obtained (e.g., by module 1102) in response to the natural language input, in accordance with the initiating digital assistant. In some examples, the response package includes a first text associated with the digital assistant response affordance; and a second text associated with the digital assistant response affordance. In some examples, the second text has fewer words than the first text.

At block 1904, after receiving the natural language input, a first response mode of the digital assistant is selected from a plurality of digital assistant response modes (e.g., by module 1104) based on contextual information associated with the electronic device. In some examples, the plurality of digital assistant response modes include a silent response mode, a mixed response mode, and a voice response mode (e.g., fig. 12). In some examples, the selection of the first response mode of the digital assistant is performed after the response package is obtained. In some examples, at block 1905, selecting the first response mode includes determining: whether to display the second text without providing an audio output representing the second text, or to provide an audio output representing the second text without displaying the second text. In some examples, selecting the first response mode includes determining whether to provide an audio output representing the first text at block 1906.

At block 1907, responsive to selecting the first response mode, the response package is presented by the digital assistant in accordance with the first response mode (e.g., using formatting module 1106).

In some examples, the first response mode is a silent response mode, and presenting, by the digital assistant, the response packet according to the first response mode includes: the digital assistant is displayed responsive to the affordance and displays the second text without providing a second audio output representing the second text, as shown at block 1908.

In some examples, the context information includes digital assistant voice feedback settings, and the silent response mode is selected based on determining that the digital assistant voice feedback settings indicate that no voice feedback is provided, as shown at block 1909.

In some examples, the context information includes detection of physical contact of the electronic device, the physical contact being used to initiate the digital assistant, and a silent response mode is selected based on the detection of the physical contact, as shown in block 1910.

In some examples, the context information includes whether the electronic device is in a locked state, and the silent response mode is selected based on determining that the electronic device is not in a locked state, as shown at block 1911.

In some examples, the context information includes whether a display of the electronic device is being displayed prior to initiating the digital assistant, and the silent response mode is selected based on determining that the display is being displayed prior to initiating the digital assistant, as shown at block 1912.

In some examples, the context information includes detection of a touch performed on the electronic device for a predetermined duration before the silent response mode is selected, and the silent response mode is selected based on the detected touch, as shown at block 1913.

In some examples, the context information includes detection of a predetermined gesture of the electronic device for a second predetermined duration before the silent response mode is selected, and the silent response mode is selected based on detecting the predetermined gesture, as shown at block 1914.

In some examples, the first response mode is a hybrid response mode, and presenting, by the digital assistant, the response packet according to the first response mode includes: the digital assistant is displayed responsive to the affordance and providing a second audio output representing the second text without displaying the second text, as shown at block 1915.

In some examples, the context information includes digital assistant voice feedback settings, and the hybrid response mode is selected based on determining that the digital assistant voice feedback settings indicate that voice feedback is to be provided, as shown at block 1916.

In some examples, the context information includes detection of physical contact of the electronic device, the physical contact being used to initiate the digital assistant, and the hybrid response mode is selected based on the detection of the physical contact, as shown at block 1917.

In some examples, the context information includes whether the electronic device is in a locked state, and the hybrid response mode is selected based on determining that the electronic device is not in a locked state, as shown at block 1918.

In some examples, the context information includes whether a display of the electronic device is displaying before initiating the digital assistant and selecting the mixed response mode based on determining that the display is displaying before initiating the digital assistant, as shown at block 1919.

In some examples, the context information includes detection of a touch performed on the electronic device for a predetermined duration before the hybrid response mode is selected, and the hybrid response mode is selected based on detecting the touch, as shown in block 1920.

In some examples, the context information includes detection of a predetermined gesture of the electronic device within a second predetermined duration before the hybrid response mode is selected, and the hybrid response mode is selected based on detecting the predetermined gesture, as shown at block 1921.

In some examples, the first response mode is a voice response mode, and presenting, by the digital assistant, the response packet according to the first response mode includes: an audio output representing the first text is provided, as indicated at block 1922.

In some examples, the context information includes determining that the electronic device is in a vehicle, and selecting a voice response mode in the vehicle based on the determining that the electronic device is, as shown at block 1923.

In some examples, the context information includes determining that the electronic device is coupled to the external audio output device and selecting a voice response mode based on the determination that the electronic device is coupled to the external audio output device, as shown at block 1924.

In some examples, the context information includes detection of a voice input that initiated the digital assistant, and a voice response mode is selected based on detecting the voice input, as shown at block 1925.

In some examples, the context information includes whether the electronic device is in a locked state, and the voice response mode is selected based on determining that the electronic device is in the locked state, as shown at block 1926.

In some examples, the context information includes whether a display of the electronic device is displaying before the digital assistant is initiated and the selected voice response mode is based on determining that the display of the electronic device is not displaying before the digital assistant is initiated, as shown at block 1927.

In some examples, at block 1928, after the response package is presented by the digital assistant, a second natural language input is received (e.g., by device 800) in response to the presentation of the response package.

In some examples, at block 1929, a second response packet is obtained (e.g., by module 1102) in response to the second natural language input.

In some examples, at block 1930, after receiving the second natural language speech input, a second response mode of the digital assistant is selected (e.g., by module 1104) from the plurality of digital assistant response modes, wherein the second response mode is different from the first response mode.

In some examples, at block 1931, in response to selecting the second response mode, a second response packet (e.g., fig. 16) is presented by the digital assistant in accordance with the second response mode (e.g., using module 1106).

The operations described above with reference to fig. 19A-19E are optionally implemented by the components depicted in fig. 1-4, 6A-6B, 7A-7C, 11, and 12. For example, the operations of process 1900 may be implemented by device 800 implementing system 1100. Those of ordinary skill in the art will clearly know how to implement other processes based on the components depicted in fig. 1-4, 6A-6B, and 7A-7C.

According to some implementations, a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) is provided that stores one or more programs for execution by one or more processors of an electronic device, the one or more programs including instructions for performing any of the methods or processes described herein.

According to some implementations, an electronic device (e.g., a portable electronic device) is provided that includes means for performing any of the methods and processes described herein.

According to some implementations, an electronic device (e.g., a portable electronic device) is provided that includes a processing unit configured to perform any of the methods and processes described herein.

According to some implementations, an electronic device (e.g., a portable electronic device) is provided that includes one or more processors and memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for performing any of the methods and processes described herein.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the technology and its practical applications. Those skilled in the art are thus well able to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

Some exemplary items according to the present disclosure will be described below.

Item 1. a method, comprising:

at an electronic device with a display and a touch-sensitive surface:

receiving a user input while displaying a user interface different from the digital assistant user interface;

in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

a response affordance displayed at a second portion of the display; wherein:

a portion of the user interface remains visible at a third portion of the display; and is

The third portion is located between the first portion and the second portion.

Item 2. the method of item 1, wherein the response affordance is in a first state

And displaying, wherein the method further comprises:

receiving a second user input corresponding to selection of the response affordance while the digital assistant user interface is displayed over the user interface; and

In response to receiving the second user input, replace the display of the response affordance in the first state with the display of the response affordance in a second state.

Item 3. the method of item 2, wherein the first state is a compact state and the second state is an expanded state.

Item 4. the method of any of items 2 to 3, further comprising:

while displaying the response affordance in the second state, receiving a third user input requesting that the response affordance be displayed in the first state; and

in response to receiving the third user input, replacing display of the response affordance in the second state with display of the response affordance in the first state.

Item 5. the method of any of items 2 to 4, further comprising:

while the response affordance is displayed in the second state, receiving a fourth user input corresponding to a selection of the response affordance; and

in response to receiving the fourth user input, displaying a user interface of an application corresponding to the response affordance.

Item 6. the method of any of items 2-5, wherein the second user input corresponds to a selection of a first portion of the responsive affordance, the method further comprising:

receiving a fifth user input corresponding to a selection of a second portion of the response affordance while the digital assistant user interface is displayed over the user interface; and

in response to receiving the fifth user input, displaying a second user interface of a second application corresponding to the response affordance.

Item 7. the method of item 6, further comprising:

displaying a selectable digital assistant indicator while displaying the second user interface of the second application.

Item 8. the method of any of items 1 to 7, wherein the response affordance includes a selectable element, the method further comprising:

receiving a user input corresponding to a selection of the selectable element; and

in response to receiving user input corresponding to selection of the selectable element, an affordance corresponding to the selectable element is displayed over the response affordance.

Item 9. the method of item 8, further comprising:

Visually obscuring the user interface at the third portion of the display when the affordance corresponding to the selectable element is displayed over the response affordance.

Item 10. the method of any of items 1 to 9, wherein the user interface includes an input field occupying a fourth portion of the display, the method further comprising:

receiving a sixth user input corresponding to a displacement of the response affordance from the first portion of the display to the fourth portion of the display; and

in response to receiving the sixth user input, replace display of the response affordance at the first portion of the display with display of the response affordance in the input field.

Item 11 the method of item 10, wherein the input field corresponds to a messaging application, an email application, or a note-taking application.

Item 12. the method of any of items 10 to 11, further comprising:

upon receiving the sixth user input, successively shifting the response affordance from the first portion of the display to the fourth portion of the display; and

Ceasing to display the digital assistant indicator while continuously shifting the response affordance.

Item 13. the method of any of items 1 to 12, wherein the user interface includes a desktop applet region occupying a fifth portion of the display, the method further comprising:

receiving a seventh user input corresponding to displacement of the response affordance from the first portion of the display to the fifth portion of the display; and

in response to receiving the seventh user input, replace display of the response affordance at the first portion of the display with display of the response affordance in the desktop widget region.

Item 14. the method of item 13, wherein the response affordance corresponds to an event, the method further comprising:

determining completion of the event; and

in response to determining completion of the event, ceasing to display the response affordance in the desktop applet region.

Item 15. the method of any one of items 1 to 14, further comprising:

receiving a natural language input, wherein the response affordance corresponds to a response by the digital assistant to the natural language input.

Item 16. the method of item 15, wherein:

the digital assistant determining a plurality of results corresponding to the natural language input; and is

The response affordance includes a single result of the plurality of results.

Item 17. the method of any of items 15 to 16, wherein the response affordance includes an editable text field including text determined from the natural language input.

Item 18. the method of any one of items 15 to 17, wherein:

the digital assistant user interface further comprises a dialog affordance displayed at a sixth portion of the display; and is

The sixth portion is located between the first portion and the second portion.

Item 19. the method of item 18, wherein the dialog affordance includes a dialog generated by the digital assistant that is responsive to the natural language input.

Item 20. the method of item 19, further comprising:

determining, by the digital assistant, a plurality of selectable disambiguation options for the natural language input, wherein the conversation includes the plurality of selectable disambiguation options.

Item 21. the method of any one of items 19 to 20, further comprising:

determining a primary user intent based on the natural language input, wherein the response affordance corresponds to the primary user intent; and

determining an alternative user intent based on the natural language input, wherein the dialog includes a selectable option corresponding to the alternative user intent.

Item 22. the method of any of items 18 to 21, wherein the dialog affordance is displayed in a third state, the method further comprising:

receiving an eighth user input corresponding to a selection of the dialog affordance; and

in response to receiving the eighth user input, replacing display of the dialog affordance in the third state with display of the dialog affordance in a fourth state.

Item 23. the method of item 22, wherein the fourth state corresponds to a maximum size of the dialog affordance, the method further comprising:

when the dialog affordance is displayed in the fourth state, user input is enabled to scroll through content of the dialog affordance.

Item 24. the method of any one of items 22 to 23, wherein:

Display of the dialog affordance in the fourth state occupies at least a portion of the first portion of the display; and is

Displaying the dialog affordance in the fourth state includes displaying the dialog affordance over at least a third portion of the response affordance.

Item 25. the method of item 24, wherein:

prior to receiving the eighth user input, the response affordance is displayed in a fifth state; and is

Displaying the dialog affordance in the fourth state includes replacing display of the response affordance in a fifth state with display of the response affordance in a sixth state.

Item 26. the method of any one of items 24 to 25, wherein:

the fourth state corresponds to a second maximum size of the dialog affordance; and is

A fourth portion of the response affordance remains visible while the dialog affordance is displayed in the fourth state.

Item 27. the method of item 26, further comprising:

receiving a ninth user input corresponding to selection of the fourth portion of the response affordance; and

In response to receiving the ninth user input:

replacing display of the dialog affordance in the fourth state with display of the dialog affordance in a seventh state; and is

Displaying the response affordance at the first portion of the display.

Item 28. the method of any one of items 22 to 27, further comprising:

receiving a tenth user input corresponding to selection of the dialog affordance while the dialog affordance is displayed in the fourth state; and

in response to receiving the tenth user input, replacing display of the dialog affordance in the fourth state with display of the dialog affordance in an eighth state.

Item 29. the method of any of items 22 to 28, further comprising:

receiving an eleventh user input corresponding to selection of the response affordance while the dialog affordance is displayed in the fourth state; and

in response to receiving the eleventh user input, replacing display of the dialog affordance in the fourth state with display of the dialog affordance in a ninth state.

Item 30. the method of any of items 18 to 29, wherein the natural language input is a natural language speech input, the method further comprising:

displaying a transcription of the natural language speech input in the dialog affordance.

Item 31. the method of item 30, wherein:

the natural language speech input is subsequent to a second natural language speech input received prior to the natural language speech input; and is

In accordance with a determination that the digital assistant is unable to determine the user intent for the natural language speech input and unable to determine a second user intent for the second natural language speech input, performing displaying the transcription.

Item 32. the method of item 30, wherein displaying the transcription is performed in accordance with a determination that the natural language speech input repeats a previous natural language speech input.

Item 33. the method of item 30, further comprising:

after receiving the natural language speech input, receiving a second natural language speech input that is subsequent to the natural language speech input, wherein displaying the transcription is performed in accordance with a determination that the second natural language speech input indicates a speech recognition error.

Item 34. the method of any of items 1 to 33, wherein, at the first time

Presenting the digital assistant results, the method further comprising:

in accordance with a determination that the digital assistant result corresponds to a predetermined type of digital assistant result, automatically ceasing to display the digital assistant user interface for a predetermined duration after the first time.

Item 35. the method of any of items 1 to 34, wherein the user interface is a home screen user interface or an application specific user interface.

Item 36. the method of any of items 1 to 35, wherein the portion of the user interface is displayed at the third portion of the display prior to receiving the user input.

Item 37. a method, comprising:

at an electronic device with a display and a touch-sensitive surface:

displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

a response affordance displayed at a second portion of the display;

While displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface;

in accordance with a determination that the user input corresponds to a first type of input:

ceasing to display the digital assistant indicator and the response affordance; and is

In accordance with a determination that the user input corresponds to a second type of input different from the first type of input:

updating display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

Item 38. the method of item 37, wherein the first type of input comprises a tap gesture.

Item 39. the method of any of items 37-38, wherein the second type of input comprises a drag gesture.

Item 40. the method of any of items 37-39, wherein ceasing to display the digital assistant indicator and the response affordance includes:

replacing display of the digital assistant indicator with display of a first portion of the user interface at the first portion of the display; and

Replacing display of the response affordance with display of a second portion of the user interface at the second portion of the display.

Item 41. the method of any of items 37-40, wherein the user input corresponds to a selection of a selectable element displayed in the third portion of the display, the method further comprising:

in accordance with a determination that the user input corresponds to the first type of input:

displaying a user interface corresponding to the selectable element.

Item 42. the method of item 41, wherein displaying the user interface corresponding to the selectable element comprises replacing the display of the portion of the user interface, the display of the response affordance, and the display of the digital assistant indicator with the display of the user interface corresponding to the selectable element.

Item 43. the method of any of items 41-42, wherein the selectable element is a link and the user interface corresponding to the selectable element is a user interface corresponding to the link.

Item 44. the method of any one of items 41 to 42, wherein:

The user interface is a home screen user interface;

the selectable element is an application affordance of the home screen user interface; and is

The user interface corresponding to the selectable element is a user interface corresponding to the application affordance.

Item 45. the method of any one of items 37 to 43, further comprising:

receiving a second user input while the digital assistant user interface is displayed over the user interface; and

in accordance with a determination that the second user input corresponds to a third type of input, ceasing to display the response affordance and the digital assistant indicator.

Item 46. the method of item 45, wherein the user interface is an application-specific user interface, the method further comprising:

in accordance with a determination that the second user input corresponds to the third type of input:

a home screen user interface is displayed.

Item 47. the method of any one of items 37 to 46, further comprising:

receiving a third user input corresponding to a selection of the response affordance while the digital assistant user interface is displayed over the user interface; and

In response to receiving the third user input, ceasing to display the response affordance and the digital assistant indicator.

Item 48. the method of any of items 37 to 47, wherein updating the display of the user interface at the third portion comprises scrolling content of the user interface.

Item 49 the method of any of items 37-48, wherein updating the display of the user interface at the third portion is performed further in accordance with a determination that a digital assistant corresponding to the digital assistant user interface is in a listening state.

Item 50. the method of any of items 37-49, wherein updating the display of the user interface at the third portion is performed while the digital assistant indicator is displayed at the first portion.

Item 51. the method of any of items 37 to 50, wherein the user interface is different from the digital assistant user interface.

Item 52. a method for operating a digital assistant, the method comprising:

at an electronic device with one or more processors, memory, and a display:

receiving a natural language input;

initiating the digital assistant;

In accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input;

after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and

in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

Item 53. the method of item 52, wherein the response packet comprises:

a first text associated with the digital assistant response affordance; and

a second text associated with the digital assistant response affordance.

Item 54. the method of item 53, wherein the second text has fewer words than the first text.

Item 55. the method of any one of items 53 to 54, wherein selecting the first response mode comprises determining:

displaying the second text without providing an audio output representing the second text; or also

Providing the audio output representing the second text without displaying the second text.

Item 56. the method of any of items 53-55, wherein selecting the first response mode includes determining whether to provide an audio output representing the first text.

Item 57. the method of any one of items 53 to 56, wherein:

the first response mode is a silent response mode; and is

Presenting, by the digital assistant, the response package according to the first response mode comprises:

displaying the digital assistant response affordance; and

displaying the second text without providing a second audio output representing the second text.

Item 58. the method of item 57, wherein:

the contextual information comprises digital assistant voice feedback settings; and is

Selecting the first response mode based on determining that the digital assistant voice feedback setting indicates that no voice feedback is provided.

Item 59. the method of any one of items 57 to 58, wherein:

the contextual information comprises a detection of physical contact of the electronic device, the physical contact being used to initiate the digital assistant; and is

Selecting the first response mode based on detecting the physical contact.

Item 60. the method of any one of items 57 to 59, wherein:

the context information includes whether the electronic device is in a locked state; and is

Selecting the first response mode based on determining that the electronic device is not in the locked state.

Item 61. the method of any one of items 57 to 60, wherein:

the contextual information comprises whether a display of the electronic device is being displayed prior to initiating the digital assistant; and is

Selecting the first response mode based on determining that the display is displaying prior to initiating the digital assistant.

Item 62. the method of any one of items 57 to 61, wherein:

the contextual information comprises detection of a touch performed on the electronic device for a predetermined duration of time prior to selection of the first response mode; and is

Selecting the first response mode based on detecting the touch.

Item 63. the method of any one of items 57 to 62, wherein:

the contextual information comprises detection of a predetermined gesture of the electronic device for a second predetermined duration before the first response mode is selected; and is

Selecting the first response mode based on detecting the predetermined gesture.

Item 64. the method of any one of items 53 to 56, wherein:

the first response mode is a hybrid response mode; and is

Presenting, by the digital assistant, the response package according to the first response mode comprises: displaying the digital assistant responsive to the affordance and providing a second audio output representing the second text without displaying the second text.

Item 65. the method of item 64, wherein:

the contextual information comprises digital assistant voice feedback settings; and is

Selecting the first response mode based on determining that the digital assistant voice feedback setting indicates that voice feedback is to be provided.

Item 66. the method of any one of items 64 to 65, wherein:

the contextual information comprises a detection of physical contact of the electronic device, the physical contact being used to initiate the digital assistant; and is

Selecting the first response mode based on detecting the physical contact.

Item 67. the method of any one of items 64 to 66, wherein:

the context information includes whether the electronic device is in a locked state; and is

Selecting the first response mode based on determining that the electronic device is not in the locked state.

Item 68. the method of any one of items 64 to 67, wherein:

The contextual information comprises whether a display of the electronic device is being displayed prior to initiating the digital assistant; and is

Selecting the first response mode based on determining that the display is displaying prior to initiating the digital assistant.

Item 69. the method of any one of items 64 to 68, wherein:

the contextual information comprises detection of a touch performed on the electronic device for a predetermined duration of time prior to selection of the first response mode; and is

Selecting the first response mode based on detecting the touch.

Item 70. the method of any one of items 64 to 69, wherein:

the contextual information comprises detection of a predetermined gesture of the electronic device for a second predetermined duration before the first response mode is selected; and is

Selecting the first response mode based on detecting the predetermined gesture.

Item 71. the method of any one of items 53 to 56, wherein:

the first response mode is a voice response mode; and is

Presenting, by the digital assistant, the response package according to the first response mode comprises: providing an audio output representing the first text.

Item 72. the method of item 71, wherein:

the contextual information includes determining that the electronic device is in a vehicle; and is

Selecting the first response mode based on determining that the electronic device is in the vehicle.

Item 73. the method of any one of items 71 to 72, wherein:

the contextual information includes determining that the electronic device is coupled to an external audio output device; and is

Selecting the first response mode based on determining that the electronic device is coupled to the external audio output device.

Item 74. the method of any one of items 71 to 73, wherein:

the contextual information comprises a detection of a voice input for initiating the digital assistant; and is

Selecting the first response mode based on detection of the voice input.

Item 75. the method of any one of items 71 to 74, wherein:

the context information includes whether the electronic device is in a locked state; and is

Selecting the first response mode based on determining that the electronic device is in the locked state.

Item 76. the method of any one of items 71 to 75, wherein:

the contextual information comprises whether a display of the electronic device is being displayed prior to initiating the digital assistant; and is

Selecting the first response mode based on determining that the display of the electronic device is not being displayed prior to initiating the digital assistant.

Item 77. the method of any one of items 52 to 76, further comprising:

after presenting the response package by the digital assistant, receiving a second natural language input in response to the presentation of the response package;

retrieving a second response package in response to the second natural language input; and

after receiving the second natural language speech input, selecting a second response mode of the digital assistant from the plurality of digital assistant response modes, wherein the second response mode is different from the first response mode; and

in response to selecting the second response mode, presenting, by the digital assistant, the second response package in accordance with the second response mode.

Item 78. the method of any of items 52 to 77, wherein the selecting of the first response mode of the digital assistant is performed after the obtaining of the response package.

Item 79. an electronic device, comprising:

a display;

a touch-sensitive surface;

one or more processors;

a memory; and

One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for:

receiving a user input while displaying a user interface different from the digital assistant user interface;

in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

a response affordance displayed at a second portion of the display; wherein:

a portion of the user interface remains visible at a third portion of the display; and is

The third portion is located between the first portion and the second portion.

Item 80. an electronic device, comprising:

a display;

a touch-sensitive surface;

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for:

Displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

a response affordance displayed at a second portion of the display;

while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface;

in accordance with a determination that the user input corresponds to a first type of input:

ceasing to display the digital assistant indicator and the response affordance; and is

In accordance with a determination that the user input corresponds to a second type of input different from the first type of input:

updating display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

Item 81. an electronic device, comprising:

a display;

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for:

Receiving a natural language input;

initiating a digital assistant;

in accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input;

after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and

in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and a touch-sensitive surface, cause the electronic device to:

receiving a user input while displaying a user interface different from the digital assistant user interface;

in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

A response affordance displayed at a second portion of the display; wherein:

a portion of the user interface remains visible at a third portion of the display; and is

The third portion is located between the first portion and the second portion.

A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and a touch-sensitive surface, cause the electronic device to:

displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

a response affordance displayed at a second portion of the display;

while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface;

in accordance with a determination that the user input corresponds to a first type of input:

Ceasing to display the digital assistant indicator and the response affordance; and is

In accordance with a determination that the user input corresponds to a second type of input different from the first type of input:

updating display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

Item 84. a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display, cause the electronic device to:

receiving a natural language input;

initiating a digital assistant;

in accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input;

after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and

in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

Item 85. an electronic device, comprising:

Means for performing the following:

receiving a user input while displaying a user interface different from the digital assistant user interface;

in accordance with a determination that the user input satisfies criteria for initiating a digital assistant: displaying the digital assistant user interface over the user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

a response affordance displayed at a second portion of the display; wherein:

a portion of the user interface remains visible at a third portion of the display; and is

The third portion is located between the first portion and the second portion.

Item 86. an electronic device, comprising:

means for performing the following:

displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

a response affordance displayed at a second portion of the display;

while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface;

In accordance with a determination that the user input corresponds to a first type of input:

ceasing to display the digital assistant indicator and the response affordance; and is

In accordance with a determination that the user input corresponds to a second type of input different from the first type of input:

updating display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

Item 87. an electronic device, comprising:

means for performing the following:

receiving a natural language input;

initiating a digital assistant;

in accordance with initiating the digital assistant, obtaining a response package responsive to the natural language input;

after receiving the natural language input, selecting a first response mode of the digital assistant from a plurality of digital assistant response modes based on contextual information associated with the electronic device; and

in response to selecting the first response mode, presenting, by the digital assistant, the response package in accordance with the first response mode.

Item 88. an electronic device, comprising:

a display;

a touch-sensitive surface;

one or more processors;

a memory; and

One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of items 1 to 36.

Item 89 an electronic device, comprising:

a display;

a touch-sensitive surface;

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of items 37-51.

Item 90. an electronic device, comprising:

a display;

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any of items 52-78.

Item 91. a non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and a touch-sensitive surface, cause the electronic device to perform the method of any of items 1-36.

Item 92. a non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and a touch-sensitive surface, cause the electronic device to perform the method of any of items 37-51.

Item 93. a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display, cause the electronic device to perform the method of any of items 52-78.

Item 94. an electronic device, comprising:

means for performing the method of any of items 1 to 36.

Item 95. an electronic device, comprising:

means for performing the method of any of items 37 to 51.

Item 96. an electronic device, comprising:

means for performing the method of any of items 52-78.

Although the present disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. It is to be understood that such changes and modifications are to be considered as included within the scope of the disclosure and examples as defined by the following claims.

As described above, one aspect of the present technology is to collect and use data from a variety of sources to improve the format in which a digital assistant presents responses to a user request. The present disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personal information data in the present technology may be useful to benefit the user. For example, the personal information data may be used to adjust the response of the digital assistant to suit the user's current context. In addition, the present disclosure also contemplates other uses for which personal information data is beneficial to a user. For example, health and fitness data may be used to provide insight into the overall health condition of a user, or may be used as positive feedback for individuals using technology to pursue health goals.

The present disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should enforce and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data is collected and/or used. Personal information from the user should be collected for legitimate and legitimate uses by the entity and not shared or sold outside of these legitimate uses. Furthermore, such acquisition/sharing should be performed after receiving user informed consent. Furthermore, such entities should consider taking any necessary steps to defend and secure access to such personal information data, and to ensure that others who have access to the personal information data comply with their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to the particular type of personal information data collected and/or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state laws, such as the health insurance association and accountability act (HIPAA); while other countries may have health data subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained for different personal data types in each country.

Regardless of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, to the extent that contextual data is collected to select a digital assistant response mode, the present technology may be configured to allow a user to opt-in or opt-out of participating in the collection of personal information data during registration service or at any time thereafter. As another example, the user may choose not to allow the device to collect context data for selecting a digital assistant response mode. As another example, the user may choose to limit the length of time that the context data is maintained. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that their personal information data is to be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and deleting data. In addition, and when applicable, including in certain health-related applications, data de-identification may be used to protect the privacy of the user. Where appropriate, de-identification may be facilitated by removing certain identifiers (e.g., date of birth, etc.), controlling the amount or characteristics of data stored (e.g., collecting location data at the city level rather than the address level), controlling the manner in which data is stored (e.g., aggregating data among users), and/or other methods.

Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be implemented without the need to access such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, when contextual data is not available (e.g., if a user refrains from collecting contextual data to select a digital assistant response mode), the device may select a default digital assistant response mode, or a digital assistant response mode based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with the user, other non-personal information available to the device (e.g., whether the device is in a locked state), or publicly available information.

Claims (17)

1. A method, comprising:

at an electronic device with a display and a touch-sensitive surface:

displaying a digital assistant user interface over a user interface, the digital assistant user interface comprising:

a digital assistant indicator displayed at a first portion of the display; and

A response affordance displayed at a second portion of the display;

while displaying the digital assistant user interface over the user interface, receiving user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface;

in accordance with a determination that the user input corresponds to a first type of input:

ceasing to display the digital assistant indicator and the response affordance; and is

In accordance with a determination that the user input corresponds to a second type of input different from the first type of input:

updating display of the user interface at the third portion in accordance with the user input while the response affordance is displayed at the second portion.

2. The method of claim 1, wherein the first type of input comprises a tap gesture.

3. The method of any of claims 1-2, wherein the second type of input comprises a drag gesture.

4. The method of any of claims 1-3, wherein ceasing to display the digital assistant indicator and the response affordance comprises:

Replacing display of the digital assistant indicator with display of a first portion of the user interface at the first portion of the display; and

replacing display of the response affordance with display of a second portion of the user interface at the second portion of the display.

5. The method of any of claims 1-4, wherein the user input corresponds to a selection of a selectable element displayed in the third portion of the display, the method further comprising:

in accordance with a determination that the user input corresponds to the first type of input:

displaying a user interface corresponding to the selectable element.

6. The method of claim 5, wherein displaying the user interface corresponding to the selectable element comprises replacing display of the portion of the user interface, display of the response affordance, and display of the digital assistant indicator with display of the user interface corresponding to the selectable element.

7. The method of any of claims 5-6, wherein the selectable element is a link and the user interface corresponding to the selectable element is a user interface corresponding to the link.

8. The method of any of claims 5 to 6, wherein:

the user interface is a home screen user interface;

the selectable element is an application affordance of the home screen user interface; and is

The user interface corresponding to the selectable element is a user interface corresponding to the application affordance.

9. The method of any of claims 1 to 7, further comprising:

receiving a second user input while the digital assistant user interface is displayed over the user interface; and

in accordance with a determination that the second user input corresponds to a third type of input, ceasing to display the response affordance and the digital assistant indicator.

10. The method of claim 9, wherein the user interface is an application-specific user interface, the method further comprising:

in accordance with a determination that the second user input corresponds to the third type of input:

a home screen user interface is displayed.

11. The method of any of claims 1 to 10, further comprising:

receiving a third user input corresponding to a selection of the response affordance while the digital assistant user interface is displayed over the user interface; and

In response to receiving the third user input, ceasing to display the response affordance and the digital assistant indicator.

12. The method of any of claims 1-11, wherein updating the display of the user interface at the third portion includes scrolling content of the user interface.

13. The method of any of claims 1-12, wherein updating the display of the user interface at the third portion is performed further in accordance with a determination that a digital assistant corresponding to the digital assistant user interface is in a listening state.

14. The method of any of claims 1-13, wherein updating the display of the user interface at the third portion is performed while the digital assistant indicator is displayed at the first portion.

15. The method of any of claims 1-14, wherein the user interface is different from the digital assistant user interface.

16. An electronic device, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of claims 1-15.

17. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any of claims 1-15.

Images