Digital Assistant User Interface and Response Patterns

Abstract

The present disclosure relates to digital assistant user interfaces and response modes. An exemplary process includes: receiving user input while displaying a user interface different from a digital assistant user interface; based on determining that the user input meets the criteria for initiating a digital assistant: displaying the digital assistant user interface on top of the user interface, the digital assistant user interface including: a digital assistant indicator, the digital assistant indicator is displayed at a first portion of the display; and a response enable indication, the response enable indication is 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

[0001] This application is a divisional application of the invention patent application with application date of September 16, 2020, application number 202010977583.9, and invention name “Digital Assistant User Interface and Response Mode”. Technical Field

[0002] 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 Art

[0003] Intelligent automated assistants (or digital assistants) can provide a favorable interface between human users and electronic devices. Such assistants can allow users to interact with devices or systems using natural language in voice form and / or text form. For example, a user can provide a voice input containing a user request to a digital assistant running on an electronic device. The digital assistant can interpret the user's intent from the voice input and operationalize the user's intent into tasks. These tasks can then be performed by executing one or more services of the electronic device, and relevant output in response to the user's request can be returned to the user.

[0004] The displayed user interface of the digital assistant may sometimes obscure other displayed elements that the user may be interested in. In addition, the digital assistant may sometimes provide responses in a format that is not expected for the user's current context. For example, the digital assistant may provide displayed output when the user does not desire (or cannot) view the device display. Summary of the invention

[0005] Exemplary methods are disclosed herein. An exemplary method includes, at an electronic device having a display and a touch-sensitive surface: receiving user input while displaying a user interface different from a digital assistant user interface; based on determining that the user input meets 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, the digital assistant indicator displayed at a first portion of the display; and a response enable indication, the response enable indication 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.

[0006] An exemplary non-transitory computer-readable medium is disclosed herein. An exemplary non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions, which, when executed by one or more processors of an electronic device having a display and a touch-sensitive surface, cause the electronic device to: receive user input when displaying a user interface different from a digital assistant user interface; based on determining that the user input meets the criteria for initiating a digital assistant: display the digital assistant user interface on top of the user interface, the digital assistant user interface including: a digital assistant indicator, the digital assistant indicator is displayed at a first portion of the display; and a response enable indication, the response enable indication is 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.

[0007] An exemplary electronic device is 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, and the one or more programs include instructions for the following operations: receiving user input while displaying a user interface different from a digital assistant user interface; based on determining that the user input meets the criteria for initiating a digital assistant: displaying the digital assistant user interface on top of the user interface, the digital assistant user interface including: a digital assistant indicator, the digital assistant indicator is displayed at a first portion of the display; and a response enable indication, the response enable indication is 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.

[0008] An exemplary electronic device includes a device for performing the following operations: receiving user input while displaying a user interface different from a digital assistant user interface; and based on determining that the user input meets 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, the digital assistant indicator displayed at a first portion of the display; and a response enable indication, the response enable indication 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.

[0009] Displaying a digital assistant user interface on top of a user interface (where a portion of the user interface remains visible at a portion of the display) can improve the effectiveness of the digital assistant and reduce the visual interference of the digital assistant with the user-device interaction. For example, information included in the underlying visible user interface can allow the user to better clarify the request to the digital assistant. For another example, displaying the user interface in such a manner can facilitate the interaction between elements of the digital assistant user interface and the underlying user interface (e.g., a digital assistant response included in a message of the underlying messaging user interface). In addition, having the digital assistant user interface and the underlying user interface coexist on the display allows user interaction with both user interfaces at the same time, thereby better integrating the digital assistant into the user-device interaction. In this way, the user-device interface can be more effective (e.g., by enabling the digital assistant to perform the tasks requested by the user more accurately and more efficiently, by reducing the visual interference of the digital assistant with the content that the user is viewing, by reducing the number of user inputs required to operate the device as needed), 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 more efficiently.

[0010] Exemplary methods are disclosed herein. An exemplary method includes, at an electronic device having a display and a touch-sensitive surface: displaying a digital assistant user interface on a user interface, the digital assistant user interface including: a digital assistant indicator, the digital assistant indicator displayed at a first portion of the display; and a response enable indication, the response enable indication displayed at a second portion of the display; while the digital assistant user interface is displayed on the user interface, receiving a user input corresponding to a selection of a third portion of the display, the third portion displaying a portion of the user interface; based on determining that the user input corresponds to a first type of input: stopping displaying the digital assistant indicator and the response enable indication; and based on determining that the user input corresponds to a second type of input different from the first type of input: while displaying the response enable indication at the second portion, updating the display of the user interface at the third portion based on the user input.

[0011] An exemplary non-transitory computer-readable medium is disclosed herein. An exemplary non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions, which, when executed by one or more processors of an electronic device having a display and a touch-sensitive surface, cause the electronic device to: display a digital assistant user interface on a user interface, the digital assistant user interface including: a digital assistant indicator, the digital assistant indicator is displayed at a first portion of the display; and a response enable indication, the response enable indication is displayed at a second portion of the display; when the digital assistant user interface is displayed on the user interface, receive a user input corresponding to a selection of a third portion of the display, the third portion displays a portion of the user interface; based on determining that the user input corresponds to a first type of input: stop displaying the digital assistant indicator and the response enable indication; and based on determining that the user input corresponds to a second type of input different from the first type of input: when the response enable indication is displayed at the second portion, update the display of the user interface at the third portion according to the user input.

[0012] An exemplary electronic device is 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, and the one or more programs include instructions for the following operations: displaying a digital assistant user interface on a user interface, the digital assistant user interface including: a digital assistant indicator, the digital assistant indicator is displayed at a first portion of the display; and a response enable indication, the response enable indication is displayed at a second portion of the display; while the digital assistant user interface is displayed on the user interface, receiving a user input corresponding to a selection of a third portion of the display, the third portion displays a portion of the user interface; based on determining that the user input corresponds to a first type of input: stopping displaying the digital assistant indicator and the response enable indication; and based on determining that the user input corresponds to a second type of input different from the first type of input: when the response enable indication is displayed at the second portion, updating the display of the user interface at the third portion according to the user input.

[0013] An exemplary electronic device includes a device for the following operations: displaying a digital assistant user interface on top of a user interface, the digital assistant user interface including: a digital assistant indicator, which is displayed at a first portion of the display; and a response enable indication, which is displayed at a second portion of the display; while the digital assistant user interface is displayed on 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; based on determining that the user input corresponds to a first type of input: stopping displaying the digital assistant indicator and the response enable indication; and based on determining that the user input corresponds to a second type of input different from the first type of input: while displaying the response enable indication at the second portion, updating the display of the user interface at the third portion based on the user input.

[0014] Stopping the display of the digital assistant indicator and the response affordance based on determining that the user input corresponds to the first type of input can provide an intuitive and effective way to eliminate the digital assistant. For example, the user can simply provide an input to select the underlying user interface to eliminate the digital assistant user interface, thereby reducing the interference of the digital assistant on the user-device interaction. The display of the user interface at the third portion is updated according to the user input when the response affordance is displayed at the second portion, providing an intuitive way for the digital assistant user interface to coexist with the underlying user interface. For example, the user can provide an input to select the underlying user interface so that the underlying user interface is updated, just as if the digital assistant user interface is not displayed. In addition, retaining 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 can reduce the interference of the digital assistant on the underlying user interface. In this way, the user-device interface can be more effective (for example, by allowing the user input to interact with the underlying user interface when the digital assistant user interface is displayed, by reducing the visual interference of the digital assistant on the content that the user is viewing, by reducing the number of user inputs required to operate the device as needed), 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 more efficiently.

[0015] An exemplary method is disclosed herein. An exemplary method includes, at an electronic device having one or more processors, a memory, and a display: receiving a natural language input; initiating the digital assistant; obtaining a response packet in response to the natural language input in accordance with initiating the digital assistant; 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 context information associated with the electronic device; and in response to selecting the first response mode, presenting the response packet by the digital assistant in accordance with the first response mode.

[0016] An exemplary non-transitory computer-readable medium is disclosed herein. An exemplary 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: receive natural language input; initiate the digital assistant; obtain a response packet in response to the natural language input based on initiating the digital assistant; after receiving the natural language input, select a first response mode of the digital assistant from multiple digital assistant response modes based on context information associated with the electronic device; and in response to selecting the first response mode, present the response packet by the digital assistant according to the first response mode.

[0017] An exemplary electronic device is 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, and the one or more programs include instructions for performing the following operations: receiving natural language input; initiating the digital assistant; obtaining a response packet in response to the natural language input in accordance with initiating the digital assistant; 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 context information associated with the electronic device; and in response to selecting the first response mode, presenting the response packet by the digital assistant in accordance with the first response mode.

[0018] An exemplary electronic device includes a device for performing the following operations: receiving natural language input; initiating the digital assistant; obtaining a response package in response to the natural language input based on initiating the digital assistant; 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 context information associated with the electronic device; and in response to selecting the first response mode, presenting the response package by the digital assistant according to the first response mode.

[0019] Presenting the response packet by the digital assistant according to the first response mode allows the digital assistant response to be presented in an informative manner appropriate to the user's current context. For example, when the user's current context indicates that visual user-device interaction is not expected (or possible), the digital assistant may present the response in an audio format. As another example, when the user's current context indicates that auditory user-device interaction is not expected, the digital assistant may present the response in a visual format. As another example, when the user's current context indicates that both auditory and visual user-device interaction are expected, the digital assistant may present a response having a visual component and a concise audio component, thereby reducing the length of the digital assistant's audio output. In addition, selecting the first response mode after receiving the natural language input (and before presenting the response packet) allows the user's current context (and therefore the appropriate response mode) to be more accurately determined. In this way, the user-device interface can be more efficient and secure (e.g., by reducing visual distractions from the digital assistant, by effectively presenting responses in an informative manner, by intelligently adjusting 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A block diagram is shown of a system and environment for implementing a digital assistant according to various examples.

[0021] Figure 2A A block diagram of a portable multifunction device that implements the client-side portion of a digital assistant according to various examples is shown.

[0022] Figure 2B is a block diagram illustrating exemplary components for event processing according to various examples.

[0023] Figure 3 A portable multifunction device implementing the client-side portion of a digital assistant according to various examples is shown.

[0024] Figure 4 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to various examples.

[0025] Figure 5A An exemplary user interface of a menu of applications on a portable multifunction device is shown according to various examples.

[0026] Figure 5B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is shown according to various examples.

[0027] Fig. 6AA personal electronic device according to various examples is shown.

[0028] Figure 6B A block diagram illustrating a personal electronic device according to various examples is shown.

[0029] Fig. 7A A block diagram of a digital assistant system or a server portion thereof according to various examples is shown.

[0030] Figure 7B According to various examples, Fig. 7A The capabilities of the digital assistant shown in .

[0031] Figure 7C A portion of an ontology according to various examples is shown.

[0032] Figure 8A to Figure 8CT User interfaces and digital assistant user interfaces according to various examples are shown.

[0033] 9A to 9C Multiple devices are shown determining which device should respond to voice input according to various examples.

[0034] Figure 10A to Figure 10V User interfaces and digital assistant user interfaces according to various examples are shown.

[0035] Fig.11 Systems for selecting a digital assistant response mode and for presenting responses based on the selected digital assistant response mode are shown according to various examples.

[0036] Fig.12 Devices are shown for presenting responses to received natural language input according to different digital assistant response modes according to various examples.

[0037] Fig.13 An exemplary process implemented to select a digital assistant response mode according to various examples is shown.

[0038] Fig.14 An apparatus is shown that presents a response according to a voice response mode when it is determined that the user is in a vehicle (e.g., driving) according to various examples.

[0039] Fig.15 A device is shown that presents responses according to a voice response mode when the device is executing a navigation application according to various examples.

[0040] Fig.16 Response pattern changes throughout a multi-turn DA interaction according to various examples are shown.

[0041] FIG. 17A to FIG. 17FA process for operating a digital assistant according to various examples is shown.

[0042] FIG. 18A to FIG. 18B A process for operating a digital assistant according to various examples is shown.

[0043] FIG. 19A to FIG. 19E A process for selecting a digital assistant response mode according to various examples is shown. DETAILED DESCRIPTION

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

[0045] 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 simply used to distinguish one element from another. For example, without departing from the scope of the various described examples, a first input may be referred to as a second input, and similarly, a second input may be referred to as a first input. Both the first input and the second input are inputs, and in some cases are independent and different inputs.

[0046] The terms used in the description of the various described examples herein are for the purpose of describing specific examples only and are not intended to be limiting. As used in the description of the various described examples and in 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" used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms "includes", "including", "comprises" and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their groupings.

[0047] Depending on the context, the term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" may be interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]" or "in response to detecting [a stated condition or event]," depending on the context.

[0048] 1. System and Environment

[0049] Figure 1 A block diagram of a system 100 according to various examples is shown. In some examples, the 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 performs actions based on the inferred user intent. For example, to act on an inferred user intent, the system performs one or more of the following steps: identifying a task flow with steps and parameters designed to implement the inferred user intent, inputting specific requirements into the task flow according to the inferred user intent; executing the task flow by calling a program, method, service, API, etc.; and generating an output response to the user in an audible (e.g., voice) and / or visual form.

[0050] Specifically, the digital assistant is capable of accepting user requests in the form of at least partially natural language commands, requests, statements, narrations and / or inquiries. Typically, the user requests to seek an informative answer or perform a task from the digital assistant. A satisfactory response to the user's request includes providing the requested informative answer, performing the requested task, or a combination of the two. For example, the user asks the digital assistant a question, such as "Where am I now?" Based on the user's current location, the digital assistant answers "You are near the West Gate of Central Park." The user also requests to perform a task, such as "Please invite my friends to my girlfriend's birthday party next week." In response, the digital assistant can confirm the request by saying "OK, right away", and then send a suitable calendar invitation to each of the user's friends listed in the user's electronic address book on behalf of the user. During the execution of the requested task, the digital assistant sometimes interacts with the user in a continuous dialogue involving multiple information exchanges over a long period of time. There are many other methods of interacting with the 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 video or audio forms, such as text, alarms, music, videos, animations, etc.

[0051] like Figure 1As shown, in some examples, the digital assistant is implemented according to a client-server model. The digital assistant includes a client-side portion 102 (hereinafter referred to as "DA client 102") executed on a user device 104 and a server-side portion 106 (hereinafter referred to as "DA server 106") executed on a server system 108. The DA client 102 communicates with the DA server 106 via one or more networks 110. The DA client 102 provides client-side functionality, such as user-oriented input and output processing, and communication with the DA server 106. The DA server 106 provides server-side functionality for any number of DA clients 102, each located on a corresponding user device 104.

[0052] In some examples, the 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 of the DA server 106. One or more processing modules 114 utilize the data and models 116 to process voice input and determine user intent based on natural language input. In addition, one or more processing modules 114 perform task execution based on inferred user intent. In some examples, the DA server 106 communicates with external services 120 via one or more networks 110 to complete tasks or collect information. The I / O interface 118 to external services facilitates such communications.

[0053] User device 104 can be any suitable electronic device. In some examples, user device 104 is a portable multi-function device (e.g., Figure 2A The device 200 described above), a multifunctional device (eg, as described below with reference to Figure 4 The device 400) or a personal electronic device (eg, as described below) FIG. 6A to FIG. 6B The portable multifunction device is, for example, a mobile phone that also includes other functions such as a PDA and / or a music player. Specific examples of portable multifunction devices include the Apple iPod and Device. Other examples of portable multifunction devices include, but are not limited to, earbuds / headphones, speakers, and laptops or tablets. In addition, in some examples, user device 104 is a non-portable multifunction device. Specifically, user device 104 is a desktop computer, a game console, a speaker, a television, or a television set-top box. In some examples, user device 104 includes a touch-sensitive surface (e.g., a touch screen display and / or a trackpad). In addition, user device 104 optionally includes one or more other physical user interface devices, such as a physical keyboard, a mouse, and / or a joystick. Various examples of electronic devices such as multifunction devices are described in more detail below.

[0054] Examples of one or more communication networks 110 include local area networks (LANs) and wide area networks (WANs), such as the Internet. One or more communication networks 110 are implemented using any known network protocols, 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.

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

[0056] In some examples, the user device 104 communicates with the DA server 106 via a second user device 122. The second user device 122 is similar or identical to the user device 104. For example, the second user device 122 is similar to the user device 104 described below with reference to Figure 2A , Figure 4 and FIG. 6A to FIG. 6BThe device 200, 400 or 600 described. 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 Wi-Fi network). In some examples, the second user device 122 is configured to act as a proxy between the user device 104 and the DA server 106. For example, the DA client 102 of the user device 104 is configured to transmit information (e.g., a user request received at the user device 104) to the DA server 106 via the second user device 122. The DA server 106 processes the information and returns relevant data (e.g., data content in response to the user request) to the user device 104 via the second user device 122.

[0057] In some examples, the user device 104 is configured to send an abbreviated request for data to a second user device 122 to reduce the amount of information transmitted from the user device 104. The second user device 122 is configured to determine supplemental information to add to the abbreviated request to generate a complete request for transmission to the DA server 106. The system architecture can advantageously allow user devices 104 with limited communication capabilities and / or limited battery power (e.g., a watch or similar compact electronic device) to access services provided by the 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 the DA server 106. Although Figure 1 Only two user devices 104 and 122 are shown, but it should be understood that in some examples, the system 100 may include any number and type of user devices configured to communicate with the DA server system 106 in this proxy configuration.

[0058] Although Figure 1 The digital assistant shown in includes both a client-side portion (e.g., DA client 102) and a server-side portion (e.g., DA server 106), but in some examples, the functionality of the digital assistant is implemented as a stand-alone application installed on a user device. In addition, the division of functionality between the client and server portions of the digital assistant may vary in different specific implementations. For example, in some examples, the DA client is a thin client that only provides user-facing input and output processing functions and delegates all other functions of the digital assistant to a backend server.

[0059] 2. Electronic devices

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

[0061] 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 surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a 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 a 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 the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a 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 its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0062] As used in this specification and claims, the term "tactile 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 the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to 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 does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

[0063] 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 the components. Figure 2A The various components shown in the EMBODIMENTS 2000 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0064] The 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 includes a high-speed random access memory and also includes a non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory controller 222 controls other components of the device 200 to access the memory 202.

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

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

[0067] RF (radio frequency) circuit 208 receives and sends RF signals, also known as electromagnetic signals. RF circuit 208 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 208 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memory, etc. RF circuit 208 optionally communicates with networks and other devices through wireless communications, 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)). RF circuit 208 optionally includes well-known circuits for detecting near field communication (NFC) fields, such as through short-range communication radio components. Wireless communication optionally uses any of a variety 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, 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, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (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 for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols that have not yet been developed as of the filing date of this document.

[0068] The audio circuit 210, speaker 211, and microphone 213 provide an audio interface between a user and the device 200. The audio circuit 210 receives audio data from the peripheral device interface 218, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 211. The speaker 211 converts the electrical signals into sound waves audible to humans. The audio circuit 210 also receives electrical signals converted from sound waves by the microphone 213. The audio circuit 210 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 218 for processing. The audio data is retrieved from and / or transmitted to the memory 202 and / or the RF circuit 208 via the peripheral device interface 218. In some embodiments, the audio circuit 210 also includes a headset jack (e.g., Figure 3 The headset jack provides an interface between the audio circuit 210 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both output (e.g., a single-ear headset or a dual-ear headset) and input (e.g., a microphone).

[0069] The I / O subsystem 206 couples input / output peripherals on the device 200, such as a touch screen 212 and other input control devices 216, to a peripheral device interface 218. The I / O subsystem 206 optionally includes a display controller 256, an optical sensor controller 258, an intensity sensor controller 259, a tactile feedback controller 261, and one or more input controllers 260 for other input or control devices. One or more input controllers 260 receive / send electrical signals from 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, etc. In some alternative embodiments, the input controller 260 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 3 308 in ) optionally includes an up / down button for volume control of the speaker 211 and / or the microphone 213. The one or more buttons optionally include a push button (e.g., Figure 3 306 in ).

[0070] A quick press of the push button disengages the lock of the touch screen 212 or begins the process of using gestures on the touch screen to unlock the device, as described in U.S. Patent Application 11 / 322,549, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," filed on December 23, 2005, U.S. Patent 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 306) turns the device 200 on or off. The user can customize the function of one or more buttons. The touch screen 212 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0071] 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 sends electrical signals to the touch screen 212. The touch screen 212 displays visual output to the user. The visual output includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects.

[0072] The touch screen 212 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 212 and display controller 256 (together with any associated modules and / or instruction sets in memory 202) detect contact (and any movement or interruption of the contact) on the touch screen 212 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 212. In an exemplary embodiment, the point of contact between the touch screen 212 and the user corresponds to the user's finger.

[0073] 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. The touch screen 212 and display controller 256 use any of a variety of touch sensing technologies now known or later developed, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 212 to detect contact and any movement or interruption thereof, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in

[0074] In some embodiments, the touch-sensitive display of the touch screen 212 is similar to the multi-touch-sensitive trackpads described in U.S. Patents 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication 2002 / 0015024A1, all of which are hereby incorporated by reference in their entirety. However, the touch screen 212 displays visual output from the device 200, whereas the touch-sensitive trackpad does not provide visual output.

[0075] In some embodiments, the touch-sensitive display of the touch screen 212 is as described in the following applications: (1) U.S. patent application 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application No. 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application No. 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application No. 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application No. 11 / 086,864, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 and (9) U.S. patent application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0076] The touch screen 212 has, for example, a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user contacts the touch screen 212 using any suitable object or appendage, such as a stylus, a finger, etc. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

[0078] 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., batteries, alternating current (AC)), a recharging system, power fault detection circuits, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0079] The device 200 also includes one or more optical sensors 264 . Figure 2A An optical sensor coupled to an optical sensor controller 258 in the I / O subsystem 206 is shown. 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 a static image or video. In some embodiments, the optical sensor is located at the rear of the device 200, opposite to the touch screen display 212 at the front of the device, so that the touch screen display is used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located at the front of the device so that the user's image is obtained for video conferencing while the user views other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 264 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 264 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0080] Device 200 optionally also includes one or more contact intensity sensors 265 . Figure 2A A contact force sensor is shown coupled to a force sensor controller 259 in the I / O subsystem 206. The contact force 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 force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact force sensor 265 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 212). In some embodiments, at least one contact force sensor is located on the rear of the device 200, opposite the touch screen display 212 located on the front of the device 200.

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

[0082] Device 200 optionally also includes one or more tactile output generators 267. Figure 2AA tactile output generator coupled to a tactile feedback controller 261 in the I / O subsystem 206 is shown. The tactile output generator 267 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 265 receives tactile feedback generation instructions from the tactile feedback module 233 and generates a tactile output on the device 200 that can be felt by a user of the device 200. In some embodiments, at least one tactile output generator is arranged in juxtaposition or proximity to a touch-sensitive surface (e.g., a touch-sensitive display system 212) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 200) or laterally (e.g., backward and forward in the same plane as the surface of the device 200). In some embodiments, at least one tactile output generator sensor is located on the back of the device 200, opposite the touch screen display 212 located on the front of the device 200.

[0083] Device 200 also includes one or more accelerometers 268 . Figure 2A An accelerometer 268 coupled to the peripheral device interface 218 is shown. Alternatively, the accelerometer 268 is coupled to the input controller 260 in the I / O subsystem 206. The accelerometer 268 is implemented as described in the following U.S. patent publications: U.S. Patent Publication 20050190059, "Acceleration-basedTheft Detection System for Portable Electronic Devices" and U.S. Patent Publication 20060017692, "Methods And Apparatuses For Operating A Portable Device Based OnAn 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. The device 200 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to one or more accelerometers 268 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 200.

[0084] In some embodiments, the software components stored in memory 202 include an operating system 226, a communication module (or instruction set) 228, a contact / motion module (or instruction set) 230, a graphics module (or instruction set) 232, a text input module (or instruction set) 234, a global positioning system (GPS) module (or instruction set) 235, a digital assistant client module 229, and an application (or instruction set) 236. In addition, memory 202 stores data and models, such as user data and models 231. In addition, in some embodiments, memory 202 ( Figure 2A ) or 470( Figure 4 ) storage device / global internal state 257, such as Figure 2A and Figure 4 . The device / global internal state 257 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 212; a sensor state, including information obtained from the device's various sensors and input control devices 216; and position information about the device's position and / or posture.

[0085] The operating system 226 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system 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 facilitating communication between various hardware components and software components.

[0086] The communication module 228 facilitates communication with other devices through one or more external ports 224, and also includes various software components for processing data received by the RF circuit 208 and / or the external port 224. The external port 224 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

[0087] 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 touchpad or 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 press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 230 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction) and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 230 and display controller 256 detect contact on the touch pad.

[0088] 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 a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 200). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0089] The contact / motion module 230 optionally detects gesture input from a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

[0090] The graphics module 232 includes various known software components for rendering and displaying graphics on the 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 "graphics" includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0091] In some embodiments, the 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 the graphics to be displayed from an application program, etc., along with coordinate data and other graphic attribute data if necessary, and then generates screen image data to be output to the display controller 256.

[0092] The tactile feedback module 233 includes various software components for generating instructions used by the one or more tactile output generators 267 to produce tactile outputs at one or more locations on the device 200 in response to user interaction with the device 200 .

[0093] The text input module 234, which in some examples is a component of the 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 requiring text input).

[0094] 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 the Weather widget, the Local Pages widget, and the Maps / Navigation widget).

[0095] The digital assistant client module 229 includes various client-side digital assistant instructions to provide the client-side functions of the digital assistant. For example, the digital assistant client module 229 can accept voice input (e.g., speech input), text input, touch input and / or gesture input through various user interfaces of the portable multifunction device 200 (e.g., microphone 213, one or more accelerometers 268, touch-sensitive display system 212, one or more optical sensors 264, other input control devices 216, etc.). The digital assistant client module 229 can also provide output in the form of audio (e.g., voice output), output in the form of visual output and / or output in the form of tactile output through various output interfaces of the portable multifunction device 200 (e.g., speaker 211, touch-sensitive display system 212, 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 above. During operation, the digital assistant client module 229 uses the RF circuit 208 to communicate with the DA server 106.

[0096] User data and models 231 include 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, to-do items, shopping lists, etc.) to provide client-side functionality of the digital assistant. In addition, user data and models 231 include various models for processing user input and determining user intent (e.g., speech recognition models, statistical language models, natural language processing models, knowledge ontologies, task flow models, service models, etc.).

[0097] In some examples, the digital assistant client module 229 utilizes the various sensors, subsystems, and peripherals of the portable multifunction device 200 to collect additional information from the surrounding environment 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, to the DA server 106 along with the user input to help infer the user's intent. In some examples, the digital assistant also uses the context information to determine how to prepare and transmit output to the user. The context information is referred to as context data.

[0098] In some examples, contextual information accompanying the user input includes sensor information, such as lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, etc. In some examples, the contextual information may also include the physical state of the device, such as device orientation, device location, device temperature, power level, speed, acceleration, motion pattern, cellular signal strength, etc. 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.

[0099] In some examples, the digital assistant client module 229 selectively provides information stored on the portable multifunction device 200 (e.g., user data 231) 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 transmits the additional input to the DA server 106 to assist the DA server 106 in inferring intent and / or implementing the user intent expressed in the user request.

[0100] Reference below 7A to 7C A more detailed description of the digital assistant is provided. 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.

[0101] The application 236 includes the following modules (or instruction sets) or a subset or superset thereof:

[0102] Contacts module 237 (sometimes referred to as address book or contact list);

[0103] Telephone module 238;

[0104] Video conferencing module 239;

[0105] Email client module 240;

[0106] Instant messaging (IM) module 241;

[0107] Fitness support module 242;

[0108] A camera module 243 for still images and / or video images;

[0109] Image management module 244;

[0110] Video player module;

[0111] Music player module;

[0112] Browser module 247;

[0113] Calendar module 248;

[0114] A widget module 249, which in some examples includes one or more of the following: a weather widget 249-1, a stock widget 249-2, a calculator widget 249-3, an alarm widget 249-4, a dictionary widget 249-5, and other widgets acquired by the user and a widget 249-6 created by the user;

[0115] A widget creator module 250 for forming a user-created widget 249-6;

[0116] Search module 251;

[0117] Video and music player module 252, which combines the video player module and the music player module;

[0118] Notepad module 253;

[0119] Map module 254; and / or

[0120] Online video module 255.

[0121] Examples of other applications 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.

[0122] In combination with the touch screen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, the contact module 237 is used to manage an address book or contact list (for example, stored in the application internal state 292 of the contact module 237 in memory 202 or memory 470), including: adding one or more names to the address book; deleting names from the address book; associating telephone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing telephone numbers or email addresses to initiate and / or facilitate communications via telephone 238, video conferencing module 239, email 240, or IM 241; and the like.

[0123] In conjunction with RF circuit 208, audio circuit 210, speaker 211, microphone 213, touch screen 212, display controller 256, contact / motion module 230, graphics module 232, and text input module 234, phone module 238 is used to enter a character sequence corresponding to a phone number, access one or more phone numbers in contact 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 communications use any of a variety of communication standards, protocols, and technologies.

[0124] In combination with the RF circuit 208, the audio circuit 210, the speaker 211, the microphone 213, the touch screen 212, the display controller 256, the optical sensor 264, the optical sensor controller 258, the contact / motion module 230, the graphics module 232, the text input module 234, the contact module 237 and the telephone module 238, the video conferencing module 239 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0125] In conjunction with RF circuit 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 for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 244, email client module 240 makes it very easy to create and send emails with still images or video images captured by camera module 243.

[0126] In conjunction with the RF circuit 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 messaging module 241 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages include graphics, photos, audio files, video files, and / or other attachments such as those supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

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

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

[0129] In conjunction with the touch screen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234, and 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 show or album), and storing still images and / or video images.

[0130] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232 and the text input module 234, the browser module 247 includes executable instructions for browsing the Internet in accordance with 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.

[0131] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / 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 for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0132] In combination with the RF circuit 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 widget module 249 is a mini-application that can be downloaded and used by the user (e.g., the weather desktop widget 249-1, the stock desktop widget 249-2, the calculator desktop widget 249-3, the alarm desktop widget 249-4, and the dictionary desktop widget 249-5) or a mini-application created by the user (e.g., the user-created desktop widget 249-6). In some embodiments, the desktop widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the desktop widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., the Yahoo! desktop widget).

[0133] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234 and the browser module 247, the desktop widget creator module 250 is used by users to create desktop widgets (for example, to turn a user-specified portion of a web page into a desktop widget).

[0134] In combination with the touch screen 212, display controller 256, contact / motion module 230, graphics module 232 and text input module 234, the search module 251 includes executable instructions for searching the 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) in accordance with user instructions.

[0135] In conjunction with touch screen 212, display controller 256, contact / motion module 230, graphics module 232, audio circuitry 210, speaker 211, RF circuitry 208, and browser module 247, video and music player module 252 includes executable instructions that allow a user to download and play back 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, presenting, or otherwise playing back video (e.g., on touch screen 212 or on an external display connected via external port 224). In some embodiments, device 200 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple Inc.).

[0136] In conjunction with the touch screen 212, display controller 256, contact / motion module 230, graphics module 232 and text input module 234, the notepad module 253 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

[0137] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234, the GPS module 235 and the browser module 247, the map module 254 is used to receive, display, modify and store maps and data associated with the 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) in accordance with user instructions.

[0138] In conjunction with the 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, the online video module 255 includes instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on a connected external display via external port 224), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats (such as H.264). In some embodiments, the instant messaging module 241 is used instead of the email client module 240 to send a link to a specific online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0139] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as separate software programs, processes, or modules, and therefore 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., Figure 2AIn some embodiments, the memory 202 stores a subset of the above modules and data structures. In addition, the memory 202 stores additional modules and data structures not described above.

[0140] In some embodiments, the 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 touch pad. By using a touch screen and / or a touch pad as the primary input control device for the operation of the device 200, the number of physical input control devices (such as push buttons, dials, etc.) on the device 200 is reduced.

[0141] A predefined set of functions that are performed exclusively through a touch screen and / or a touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates the device 200 to a main menu, a home menu, or a root menu from any user interface displayed on the device 200. In such embodiments, a touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

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

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

[0144] In some embodiments, the application internal state 292 includes additional information, such as one or more of the following: resumption information to be used when the application 236-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed 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.

[0145] Event monitor 271 receives event information from peripherals interface 218. Event information includes information about sub-events (e.g., a user touch on 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 circuit 210). The information that peripherals interface 218 receives from I / O subsystem 206 includes information from touch-sensitive display 212 or a touch-sensitive surface.

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

[0147] In some embodiments, the event classifier 270 also includes a hit view determination module 272 and / or an active event identifier determination module 273.

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

[0149] 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 views (of the respective application) in which a touch is detected correspond to a programmatic level within a programmatic hierarchy of applications or a view hierarchy. For example, the lowest level view in which a touch is detected is called a hit view, and the set of events that are considered to be correct input is determined at least in part based on the hit view of the initial touch that started the touch-based gesture.

[0150] The hit view determination module 272 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, the hit view determination module 272 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by the 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.

[0151] Active event recognizer determination module 273 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 273 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 273 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

[0152] Event distributor module 274 distributes event information to event identifiers (e.g., event identifier 280). In embodiments including active event identifier determination module 273, event distributor module 274 delivers the event information to the event identifier determined by active event identifier determination module 273. In some embodiments, event distributor module 274 stores the event information in an event queue, which is retrieved by corresponding event receiver 282.

[0153] In some embodiments, operating system 226 includes event classifier 270. Alternatively, application 236-1 includes event classifier 270. In yet another embodiment, event classifier 270 is a standalone module or is part of another module stored in memory 202, such as contact / motion module 230.

[0154] In some embodiments, the application 236-1 includes multiple event handlers 290 and one or more application views 291, each of which includes instructions for handling touch events occurring in a corresponding view of the user interface of the application. Each application view 291 of the application 236-1 includes one or more event identifiers 280. Typically, the corresponding application view 291 includes multiple event identifiers 280. In other embodiments, one or more event identifiers in the event identifier 280 are part of an independent module, which is a higher-level object such as a user interface toolkit (not shown) or the application 236-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 290 includes one or more of the following: data updater 276, object updater 277, GUI updater 278, and / or event data 279 received from the event classifier 270. The event handler 290 utilizes or calls the data updater 276, object updater 277, or GUI updater 278 to update the application internal state 292. Alternatively, one or more of the application views in the application views 291 include one or more corresponding event handlers 290. In addition, in some embodiments, one or more of the data updater 276, the object updater 277, and the GUI updater 278 are included in the corresponding application view 291.

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

[0156] The event receiver 282 receives event information from the event classifier 270. The event information includes information about sub-events such as touches or touch movements. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (e.g., from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0157] Event comparator 284 compares event information with 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 event definition 286. Event definition 286 includes the definition of an event (e.g., a predefined sequence of sub-events), 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 a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (287-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 212, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 290.

[0158] In some embodiments, event definition 287 includes a definition of an event for a corresponding user interface object. 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 displaying three user interface objects on touch-sensitive display 212, when a touch is detected on touch-sensitive display 212, 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 corresponding event handler 290, the event comparator uses the result of the hit test to determine which event handler 290 should be activated. For example, event comparator 284 selects an event handler associated with a sub-event and the object that triggered the hit test.

[0159] In some embodiments, the definition of the corresponding event (287) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

[0160] When a corresponding event recognizer 280 determines that a sequence of sub-events does not match any event in event definition 286, the corresponding event recognizer 280 enters an event impossible, 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.

[0161] In some embodiments, the corresponding event identifier 280 includes metadata 283 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event identifiers. In some embodiments, metadata 283 includes configurable properties, flags, and / or lists that indicate how event identifiers interact or can interact with each other. In some embodiments, metadata 283 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0162] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event identifier 280 activates the event handler 290 associated with the event. In some embodiments, the corresponding event identifier 280 delivers the event information associated with the event to the event handler 290. Activating the event handler 290 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event identifier 280 throws a tag associated with the identified event, and the event handler 290 associated with the tag obtains the tag and performs a predefined process.

[0163] In some embodiments, event delivery instructions 288 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with a sub-event sequence or to an actively participating view. An event handler associated with a sub-event sequence or with an actively participating view receives the event information and executes a predetermined process.

[0164] In some embodiments, data updater 276 creates and updates data used in application 236-1. For example, data updater 276 updates phone numbers used in contact module 237 or stores video files used in video player module. In some embodiments, object updater 277 creates and updates objects used in application 236-1. For example, object updater 277 creates new user interface objects or updates the position of user interface objects. 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 a touch-sensitive display.

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

[0166] It should be understood that the above discussion of event processing of user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 200, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining the event to be recognized.

[0167] Figure 3A portable multifunction device 200 with a touch screen 212 according to some embodiments is shown. The touch screen optionally displays one or more graphics within a user interface (UI) 300. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using 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, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 200 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will 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.

[0168] 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 button is implemented as a soft key in a GUI displayed on the touch screen 212.

[0169] In some embodiments, the device 200 includes a touch screen 212, a menu button 304, a push button 306 for powering the device on / off and for locking the device, one or more volume adjustment buttons 308, a user identity module (SIM) card slot 310, an earphone jack 312, and a docking / charging external port 224. The push button 306 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 200 also accepts speech input for activating or deactivating certain functions through a microphone 213. The device 200 also optionally includes one or more contact strength sensors 265 for detecting the strength of contact on the touch screen 212, and / or one or more tactile output generators 267 for generating tactile output for a user of the device 200.

[0170] Figure 44 is a block diagram of an exemplary multi-function device with a display and a touch-sensitive surface according to some embodiments. Device 400 does not have to be portable. In some embodiments, device 400 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). Device 400 typically includes one or more processing units (CPUs) 410, one or more network or other communication interfaces 460, a memory 470, and one or more communication buses 420 for interconnecting these components. Communication bus 420 optionally includes circuits (sometimes referred to as chipsets) that interconnect system components and control communications between system components. Device 400 includes an input / output (I / O) interface 430 with a display 440, which is typically a touch screen display. I / O interface 430 also optionally includes a keyboard and / or mouse (or other pointing device) 450 and a touchpad 455, a tactile output generator 457 for generating tactile output on device 400 (e.g., similar to the above reference Figure 2A The one or more tactile output generators 267 described above), sensors 459 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or contact intensity sensors (similar to those described above with reference to Figure 2A The memory 470 may include one or more storage devices located away from the CPU 410. In some embodiments, the memory 470 stores information related to the portable multifunction device 200 ( Figure 2A ) or a subset thereof. 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 portable multifunction device 200( Figure 2A )'s memory 202 optionally does not store these modules.

[0171] Figure 4Each of the above-mentioned elements in some examples is stored in one or more previously mentioned memory devices. Each module in the above-mentioned modules corresponds to an instruction set for performing the above-mentioned functions. The above-mentioned modules or programs (e.g., instruction sets) do not have to be implemented as independent software programs, processes or modules, so the various subsets of these modules are combined or otherwise rearranged in various embodiments. In some embodiments, memory 470 stores a subset of the above-mentioned modules and data structures. In addition, memory 470 stores additional modules and data structures not described above.

[0172] Attention is now turned to embodiments of a user interface that may be implemented on, for example, portable multifunction device 200.

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

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

[0175] Time 504;

[0176] Bluetooth indicator 505;

[0177] Battery status indicator 506;

[0178] A tray 508 with icons for commonly used applications, such as:

[0179] o an icon 516 of the phone module 238 labeled “Phone” which optionally includes an indicator 514 of the number of missed calls or voice messages;

[0180] o an icon 518 of the email client module 240 labeled “Mail”, which optionally includes an indicator 510 of the number of unread emails;

[0181] o An icon 520 labeled "Browser" of the browser module 247; and

[0182] o an icon 522 labeled “iPod” of a video and music player module 252 (also referred to as an iPod (trademark of Apple Inc.) module 252); and

[0183] Icons of other applications, such as:

[0184] o Icon 524 of IM module 241 labeled “Message”;

[0185] o Icon 526 labeled “Calendar” of calendar module 248;

[0186] o Icon 528 labeled “Photos” of the image management module 244;

[0187] o An icon 530 labeled “Camera” of the camera module 243;

[0188] o Icon 532 labeled “Online Video” of the online video module 255;

[0189] o Icon 534 labeled "Stock Market" of the Stock Market widget 249-2;

[0190] o an icon 536 labeled “Map” of the map module 254;

[0191] o Icon 538 labeled "Weather" of the Weather widget 249-1;

[0192] o Icon 540 labeled “Clock” of the Alarm Clock widget 249-4;

[0193] o an icon 542 labeled “Fitness Support” of the fitness support module 242;

[0194] o An icon 544 of the notepad module 253 labeled "Notepad"; and

[0195] o An icon 546 labeled “Settings” for a settings application or module that provides access to settings for the device 200 and its various applications 236.

[0196] It should be noted that Figure 5A The icon labels shown in are exemplary only. For example, icon 522 of video and music player module 252 is optionally labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of the corresponding application icon includes the name of the application corresponding to the corresponding 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.

[0197] Figure 5B A touch-sensitive surface 551 (eg, touch screen display 212) is shown having a touch-sensitive surface 551 (eg, Figure 4 tablet or touch pad 455) of the device (e.g., Figure 4Device 400 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 457) for detecting intensity of contacts on touch-sensitive surface 551 and / or one or more tactile output generators 459 for generating tactile output for a user of device 400.

[0198] Although some of the examples that follow will be given with reference to input on a touch screen display 212 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 5B In some embodiments, the touch-sensitive surface (e.g., Figure 5B 551) has a main axis (e.g., Figure 5B 553) corresponding to the principal axis (for example, Figure 5B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 5B , 560 corresponds to 568 and 562 corresponds to 570) at a contact with touch-sensitive surface 551 (eg, Figure 5B Thus, on a touch-sensitive surface (e.g., Figure 5B 551) and a display of a multi-function device (e.g., Figure 5B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 560 and 562 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

[0200] Fig. 6AAn exemplary personal electronic device 600 is shown. Device 600 includes a body 602. In some embodiments, device 600 includes a body 602 relative to devices 200 and 400 (e.g., Figures 2A to 4 ) or some or all of the features described in the foregoing. In some embodiments, device 600 has a touch-sensitive display screen 604, referred to hereinafter as touch screen 604. As an alternative or in addition to touch screen 604, 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 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 the touch. The user interface of device 600 responds to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 600.

[0201] Technology for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application PCT / US2013 / 040061, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying UserInterface Objects Corresponding to an Application,” and International Patent Application PCT / US2013 / 069483, filed on November 11, 2013, entitled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” each of which is hereby incorporated by reference in its entirety.

[0202] In some embodiments, the device 600 has one or more input mechanisms 606 and 608. The input mechanisms 606 and 608, if included, are physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 600 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow the device 600 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 600.

[0203] Figure 6BAn exemplary personal electronic device 600 is shown. In some embodiments, the device 600 includes a Figure 2A , Figure 2B and Figure 4 Some or all of the components described. Device 600 has a bus 612 that operatively couples an I / O portion 614 to one or more computer processors 616 and a memory 618. I / O portion 614 is connected to a display 604, which may have a touch-sensitive component 622 and, optionally, also a touch-intensity sensitive component 624. In addition, I / O portion 614 is connected to a communication unit 630 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication 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.

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

[0205] 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 one or more computer processors 616, for example, cause the computer processors to perform the above-described techniques and processes. The computer-executable instructions are also stored and / or transmitted, for example, in any non-transitory computer-readable storage medium for use by or in conjunction with an instruction execution system, device, or apparatus, such as a computer-based system, a system containing a processor, or other system that can obtain instructions from an instruction execution system, device, or apparatus and execute the instructions. The personal electronic device 600 is not limited to Figure 6B components and configurations, but may include other components or additional components in a variety of configurations.

[0206] As used herein, the term “indicative representation” refers to, for example, a display in device 200, 400, 600, 800, 900, 902, or 904 ( Figure 2A , Figure 4 , FIG. 6A to FIG. 6B , Figure 8A to Figure 8CT , 9A to 9C , Figure 10A to Figure 10V , Fig.12 , Fig.14 , Fig.15 and Fig.16) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) each constitute an affordance.

[0207] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 4 Touchpad 455 or Figure 5B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 551 in FIG. 5 , the particular user interface element is adjusted according to the detected input. In the case that a touch screen display (e.g., Figure 2A A touch sensitive display system 212 or Figure 5A In some implementations of the touch screen 212 in FIG. 1 , a contact detected 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 the 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 moves 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 using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the 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 of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a trackpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0208] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected 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 contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half-maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or give up performing the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

[0209] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, a touch-sensitive surface receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the strength 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, rather than the entire swipe contact (e.g., the swipe contact is only located at the portion at the end position). In some embodiments, a smoothing algorithm is applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding 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 peaks or depressions in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

[0210] The intensity of a contact on a 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 at which the device will perform an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.

[0211] An increase in contact feature intensity from an intensity below a 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. An increase in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a 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 contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting contact lifted 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.

[0212] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0213] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a 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, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "upward stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the circumstances).

[0214] 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 including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is 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.

[0215] 3. Digital Assistant System

[0216] Fig. 7A A block diagram of a digital assistant system 700 according to various examples is shown. In some examples, the digital assistant system 700 is implemented on a stand-alone computer system. In some examples, the digital assistant system 700 is distributed across multiple computers. In some examples, some of the modules and functions 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) via one or more networks, such as Figure 1In some examples, the digital assistant system 700 is Figure 1 Specific implementation of the server system 108 (and / or DA server 106) shown in . It should be noted that the digital assistant system 700 is only one example of a digital assistant system, and 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. Fig. 7A The various components shown in the drawings 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.

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

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

[0219] In some examples, the I / O interface 706 couples the input / output devices 716 of the digital assistant system 700, such as a display, keyboard, touch screen, and microphone, to the user interface module 722. The I / O interface 706 and the user interface module 722 receive user input (e.g., voice input, keyboard input, touch input, etc.) and process the input accordingly. In some examples, for example, when the digital assistant is implemented on a stand-alone user device, the digital assistant system 700 includes a plurality of components related to the user interface module 722. Figure 2A , Figure 4 , FIG. 6A to FIG. 6B , Figure 8A to Figure 8CT , 9A to 9C , Figure 10A to Figure 10V , Fig.12 , Fig.14 , Fig.15 and Fig.16 In some examples, digital assistant system 700 represents a server portion of a specific implementation of a digital assistant, and can 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).

[0220] In some examples, the network communication interface 708 includes one or more wired communication ports 712 and / or wireless transmission and reception circuits 714. The wired communication port receives and sends communication signals via one or more wired interfaces such as Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wireless circuit 714 receives RF signals and / or optical signals from a communication network and other communication devices and sends RF signals and / or optical signals to a communication network and other communication devices. Wireless communication uses any of a variety of communication standards, protocols and technologies, such as GSM, EDGE, CDMA, TDMA, Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communication protocol. The network communication interface 708 enables the digital assistant system 700 to communicate with other devices through 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).

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

[0222] The operating system 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OSX, WINDOWS, or an embedded operating system 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.

[0223] The communication module 720 facilitates communication between the digital assistant system 700 and other devices through the network communication interface 708. For example, the communication module 720 and the electronic devices (such as Figure 2A , Figure 4 , FIG. 6A to FIG. 6B The communication module 720 also includes various components for processing data received by the wireless circuit 714 and / or the wired communication port 712.

[0224] The user interface module 722 receives commands and / or input from the user (e.g., from a keyboard, touch screen, pointing device, controller, and / or microphone) via the I / O interface 706 and generates user interface objects on the display. The user interface module 722 also prepares output (e.g., speech, sound, animation, text, icon, vibration, tactile feedback, lighting, etc.) and transmits it to the user via the I / O interface 706 (e.g., through a display, audio channel, speaker, touchpad, etc.).

[0225] Applications 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 stand-alone user device, 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, applications 724 include, for example, resource management applications, diagnostic applications, or scheduling applications.

[0226] The memory 702 also stores a digital assistant module 726 (or the server portion of the digital assistant). In some examples, the digital assistant module 726 includes the following submodules or subsets or supersets 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 of the digital assistant module 726 or a subset or superset thereof: a knowledge ontology 760, a vocabulary index 744, user data 748, a task flow model 754, a service model 756, and an ASR system 758.

[0227] In some examples, using the processing modules, data, and models implemented in the digital assistant module 726, the digital assistant may perform at least some of the following: converting voice input into text; recognizing user intent expressed in natural language input received from a user; proactively eliciting and obtaining information needed to fully infer user intent (e.g., by disambiguating words, games, intents, etc.); determining a task flow for satisfying the inferred intent; and executing the task flow to satisfy the inferred intent.

[0228] In some examples, such as Figure 7B As shown in FIG. , the I / O processing module 728 can be Fig. 7A The I / O device 716 interacts with the user or through Fig. 7AThe network communication interface 708 in interacts with a user device (e.g., device 104, 200, 400, 600, or 800) 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 context information associated with the user input from the user device along with or shortly after receiving the user input. The context information includes user-specific data, vocabulary, and / or preferences related to the user input. In some examples, the context information also includes the software state and hardware state of the user device when the user request is received, and / or information related to the user's surrounding environment when the user request is received. In some examples, the I / O processing module 728 also sends follow-up questions related to the user request to the user and receives answers from the user. When the user request is received by the I / O processing module 728 and the user request includes voice input, the I / O processing module 728 forwards the voice input to the STT processing module 730 (or speech recognizer) for speech-to-text conversion.

[0229] The STT processing module 730 includes one or more ASR systems 758. The one or more ASR systems 758 can process the speech input received by the I / O processing module 728 to produce a recognition result. Each ASR system 758 includes a front-end speech preprocessor. The front-end speech preprocessor extracts representative features from the speech input. For example, the front-end speech preprocessor performs Fourier transform on the speech input to extract the spectral features that characterize the speech input as a sequence of representative multidimensional 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 engines based on dynamic time warping and engines based on weighted finite state transformers (WFST). One or more speech recognition models and one or more speech recognition engines are used to process the extracted representative features of the front-end speech preprocessor to produce intermediate recognition results (e.g., phonemes, phoneme strings and sub-words), and finally produce text recognition results (e.g., words, word strings, or symbol sequences). In some examples, the voice input is at least partially processed by a third-party service or processed on the user's device (e.g., device 104, 200, 400, 600 or 800) to produce recognition results. Once the STT processing module 730 generates a recognition result containing a text string (e.g., a word, or a sequence of words, or a sequence of symbols), the recognition result is transmitted to the natural language processing module 732 for intention inference. In some examples, the STT processing module 730 generates multiple candidate text representations of the voice input. Each candidate text representation is a sequence of words or symbols corresponding to the voice input. In some examples, each candidate text representation is associated with a voice recognition confidence score. Based on the speech recognition confidence score, the STT processing module 730 ranks the candidate text representations and provides the n best (e.g., the n highest ranked) candidate text representations to the 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 the natural language processing module 732 for intent inference. For another example, the 5 highest ranked (n=5) candidate text representations are delivered to the natural language processing module 732 for intent inference.

[0230] Further details regarding speech-to-text processing are described in U.S. Utility Patent Application Serial No. 13 / 236,942, filed on September 20, 2011, entitled “Consolidating Speech Recognition Results,” the entire disclosure of which is incorporated herein by reference.

[0231] In some examples, the STT processing module 730 includes a vocabulary of recognizable words and / or accesses the vocabulary via the speech-to-alphabet conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations of the word represented in the speech recognition phonetic alphabet. Specifically, the vocabulary of recognizable words includes words associated with multiple candidate pronunciations. For example, the vocabulary includes words associated with and In some examples, the candidate pronunciations for the words are associated with candidate pronunciations for the word "tomato". Additionally, 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 processing module 730 and associated with a particular user via a user profile on the device. In some examples, the candidate pronunciations for the words are determined based on the spelling of the words and one or more linguistic and / or phonetic rules. In some examples, the candidate pronunciations are manually generated, for example, based on a known standard pronunciation.

[0232] In some examples, candidate pronunciations are ranked based on their prevalence. Ranked higher than Because the former is a more common pronunciation (e.g., among all users, for users in a particular geographic region, or for any other suitable subset of users). In some examples, the candidate pronunciations are ranked based on whether the candidate pronunciation is a custom candidate pronunciation associated with the user. For example, a custom candidate pronunciation is ranked higher than a standard candidate pronunciation. This can be used to identify proper nouns with unique pronunciations that deviate from the standard pronunciation. In some examples, the candidate pronunciation is associated with one or more speech features such as geographic origin, country, or ethnicity. For example, the candidate pronunciation associated with the United States, while the candidate pronunciation associated with the United Kingdom. In addition, the ranking of the candidate pronunciations is based on one or more characteristics of the user (e.g., geographic origin, country, ethnicity, etc.) in a user profile stored on the device. For example, it may be determined from the user profile that the user is associated with the United States. Based on the user being associated with the United States, the candidate pronunciations are ranked (associated with the United States) Comparable candidate pronunciations (associated with the United Kingdom) is ranked higher. In some examples, one of the ranked candidate pronunciations may be selected as the predicted pronunciation (eg, the most likely pronunciation).

[0233] When speech input is received, the STT processing module 730 is used to determine (e.g., using an acoustic model) a phoneme corresponding to the speech input and then attempts to determine (e.g., using a language model) a word that matches the phoneme. For example, if the STT processing module 730 first identifies a phoneme sequence corresponding to a portion of the speech input It can then determine based on the lexical index 744 that the sequence corresponds to the word "tomato".

[0234] In some examples, the STT processing module 730 uses fuzzy matching techniques to determine words in an utterance. Thus, for example, the STT processing module 730 determines the phoneme sequence corresponds to the word "tomato", even though this particular phoneme sequence is not a candidate phoneme sequence for that word.

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

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

[0237] In some examples, natural language processing is based on, for example, knowledge ontology 760. Knowledge ontology 760 is a hierarchical structure containing many nodes, each node representing an "executable intent" or an "attribute" related to one or more of the "executable intent" or other "attributes". As described above, an "executable intent" represents a task that the digital assistant can perform, that is, the task is "executable" or can be performed. "Attributes" represent parameters associated with sub-aspects of an executable intent or another attribute. The connection between executable intent nodes and attribute nodes in knowledge ontology 760 defines how the parameters represented by the attribute nodes are subordinate to the tasks represented by the executable intent nodes.

[0238] In some examples, the knowledge ontology 760 is composed of executable intent nodes and attribute nodes. In the knowledge ontology 760, each executable intent node is directly connected to or connected to one or more attribute nodes through one or more intermediate attribute nodes. Similarly, each attribute node is directly connected to or connected to one or more executable intent nodes through one or more intermediate attribute nodes. For example, Figure 7C As shown, ontology 760 includes a "restaurant reservation" node (i.e., an executable intent node). The attribute nodes "restaurant", "date / time" (for reservations), and "party size" are all directly connected to the executable intent node (i.e., the "restaurant reservation" node).

[0239] In addition, the attribute nodes "cuisine", "price range", "telephone number", and "location" are child nodes of the attribute node "restaurant", and are all connected to the "restaurant reservation" node (i.e., executable intent node) through the intermediate attribute node "restaurant". Figure 7C As shown, ontology 760 also includes a "set reminder" node (i.e., another executable intent node). The attribute nodes "date / time" (for setting reminders) and "subject" (for reminders) are both connected to the "set reminder" node. Since the attribute "date / time" is related to both the task of making a restaurant reservation and the task of setting a reminder, the attribute node "date / time" is connected to both the "restaurant reservation" node and the "set reminder" node in ontology 760.

[0240] Executable intent nodes, together with their linked attribute nodes, are described as "domains". In this discussion, each domain is associated with a corresponding executable intent and refers to a set of nodes (and the relationships between these nodes) associated with a particular executable intent. For example, Figure 7CThe ontology 760 shown in includes an example of a restaurant reservation domain 762 and an example of a reminder domain 764 within the ontology 760. The restaurant reservation domain includes an executable intent node "restaurant reservation", attribute nodes "restaurant", "date / time" and "party size", and sub-attribute nodes "cuisine", "price range", "phone number" and "location". The reminder domain 764 includes an executable intent node "set reminder" and attribute nodes "subject" and "date / time". In some examples, the ontology 760 consists 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 domain 762 and the reminder domain 764, the "date / time" attribute node is also associated with many different domains (e.g., itinerary scheduling domain, travel booking domain, movie ticket domain, etc.).

[0241] although Figure 7C Two exemplary domains within ontology 760 are shown, but other domains include, for example, "find a movie," "make a phone call," "find directions," "schedule a meeting," "send a message," and "provide answers to questions," "read a list," "provide navigation instructions," "provide instructions for a task," etc. The "send message" domain is associated with the "send message" executable intent node, and further includes attribute nodes such as "one or more recipients," "message type," and "message body." The attribute node "recipients" is further defined, for example, by child attribute nodes such as "recipient name" and "message address."

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

[0243] In some examples, nodes associated with multiple related executable intents are clustered under a "superdomain" in the knowledge ontology 760. For example, the "travel" superdomain includes a cluster of attribute nodes and executable intent nodes related to travel. Executable intent nodes related to travel include "ticket booking", "hotel booking", "car rental", "route planning", "find points of interest", etc. Executable intent nodes under the same superdomain (e.g., the "travel" superdomain) have multiple shared attribute nodes. For example, the executable intent nodes for "ticket booking", "hotel booking", "car rental", "get directions", and "find points of interest" share one or more of the attribute nodes "starting location", "destination", "departure date / time", "arrival date / time", and "party size".

[0244] In some examples, each node in the knowledge ontology 760 is associated with a set of words and / or phrases related to the attribute or executable intent represented by the node. The corresponding set of words and / or phrases associated with each node is a so-called "vocabulary" associated with the node. The corresponding set of words and / or phrases associated with each node is stored in the vocabulary index 744 associated with the attribute or executable intent represented by the node. For example, return Figure 7B , the vocabulary associated with the node of the "restaurant" attribute includes words such as "food", "drinks", "cuisine", "hunger", "eat", "pizza", "fast food", "meals", etc. For another example, the vocabulary associated with the node of the "make phone call" executable intent includes words and phrases such as "call", "make a phone call", "dial", "talk to...", "call the number", "call", etc. The vocabulary index 744 optionally includes words and phrases in different languages.

[0245] 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 involve. In some examples, if a word or phrase in the candidate text representation is found to be associated with one or more nodes in the knowledge ontology 760 (via the vocabulary index 744), the word or phrase "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 executable intents as the task that the user intends 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 various triggered nodes) is selected. In some examples, the domain is selected based on a combination of the number and importance of the triggered nodes. In some examples, additional factors are also considered in the process of selecting nodes, such as whether the digital assistant has previously correctly interpreted similar requests from the user.

[0246] User data 748 includes user-specific information, such as user-specific vocabulary, user preferences, user address, user's default second language, 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 the information contained in the user input to further qualify the user's intent. For example, for a user request to "invite my friends to my birthday party," natural language processing module 732 can access user data 748 to determine who "friends" are and when and where the "birthday party" will be held, without requiring the user to explicitly provide such information in their request.

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

[0248] Additional details of searching knowledge ontologies based on symbolic strings are described in U.S. Utility Patent Application Serial No. 12 / 341,743, filed on December 22, 2008, entitled “Method and Apparatus for Searching Using An Active Ontology,” the entire disclosure of which is incorporated herein by reference.

[0249] In some examples, once the natural language processing module 732 identifies an executable intent (or domain) based on a user request, the 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 of the executable intent, and at least some of the parameters are filled with specific information and requirements specified in the user request. For example, the user says "help me reserve a seat at 7pm at the sushi restaurant." In this case, the natural language processing module 732 is able to correctly identify the executable intent as "restaurant reservation" based on the user input. According to the knowledge ontology, the structured query of the "restaurant reservation" domain includes parameters such as {cuisine}, {time}, {date}, {party number}, etc. In some examples, based on voice input and text derived from the voice input using the STT processing module 730, the natural language processing module 732 generates a partial structured query for the restaurant reservation domain, wherein the partial structured query includes parameters {cuisine = "sushi type"} and {time = "7pm"}. However, in this example, the user utterance contains insufficient information to complete the structured query associated with the domain. Therefore, based on the currently available information, other necessary parameters such as {number of party members} and {date} are not specified in the structured query. In some examples, the 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 restaurant "nearby", the natural language processing module 732 populates the {location} parameter in the structured query with the GPS coordinates from the user's device.

[0250] In some examples, the natural language processing module 732 identifies multiple candidate executable intentions for each candidate text representation received from the STT processing module 730. In addition, in some examples, a corresponding structured query is generated (partially or completely) for each identified candidate executable intention. The natural language processing module 732 determines the intent confidence score for each candidate executable intention and ranks the candidate executable intention based on the intent confidence score. In some examples, the natural language processing module 732 transmits the generated one or more structured queries (including any completed parameters) to the task flow processing module 736 ("task flow processor"). In some examples, one or more structured queries for the m best (e.g., the m highest ranked) candidate executable intentions are provided to the task flow processing module 736, where m is a predetermined integer greater than zero. In some examples, one or more structured queries for the m best candidate executable intentions are provided to the task flow processing module 736 together with the corresponding one or more candidate text representations.

[0251] Additional details for inferring user intent based on multiple candidate executable intents determined based on multiple candidate textual representations of speech input are described in U.S. utility model patent application 14 / 298,725, entitled “System and Method for Inferring User Intent From Speech Inputs,” filed on June 6, 2014, the entire disclosure of which is incorporated herein by reference.

[0252] The task flow processing module 736 is configured to receive one or more structured queries from the 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 complete these tasks are provided in the task flow model 754. In some examples, the task flow model 754 includes a process for obtaining additional information from the user, and a task flow for performing actions associated with an executable intent.

[0253] As described above, in order to complete the structured query, the task flow processing module 736 needs to initiate an additional dialogue with the user in order to obtain additional information and / or clarify the utterances that may be ambiguous. When it is necessary to conduct such an interaction, the task flow processing module 736 calls the dialogue flow processing module 734 to participate in the dialogue with the user. In some examples, the dialogue flow processor module 734 determines how (and / or when) to request additional information from the user, and receives and processes the user response. The question is provided to the user and the answer is received from the user through the I / O processing module 728. In some examples, the dialogue flow processing module 734 presents the dialogue output to the user via an audible output and / or a visual output, and receives input from the user via a verbal or physical (e.g., click) response. Continuing the above example, when the task flow processing module 736 calls the dialogue flow processing module 734 to determine the "party number" and "date" information for the structured query associated with the domain "restaurant reservation", the dialogue flow processing module 734 generates questions such as "how many people in a row?" and "which day to book?" and passes them to the user. Once the answer is received from the user, the dialog flow processing module 734 fills in the structured query with the missing information, or passes the information to the task flow processing module 736 to complete the missing information based on the structured query.

[0254] Once the task flow processing module 736 has completed the structured query for the executable intent, the task flow processing module 736 begins to execute the final task associated with the executable intent. Therefore, the task flow processing module 736 executes the steps and instructions in the task flow model according to the specific parameters contained in the structured query. For example, the task flow model for the executable intent "restaurant reservation" includes steps and instructions for contacting a restaurant and actually requesting a reservation for a specific party size at a specific time. For example, using a structured query such as: {restaurant reservation, restaurant = ABC Cafe, date = 3 / 12 / 2012, time = 7pm, party size = 5}, the task flow processing module 736 can perform the following steps: (1) Log in to the server of ABC Cafe or such A restaurant reservation system that (2) enters date, time, and party size information into a form on the website, (3) submits the form, and (4) creates a calendar entry for the reservation in the user's calendar.

[0255] In some examples, the task flow processing module 736 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 a phone call, sets a calendar entry, invokes a map search, 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 the corresponding service models in the service model 756. The service processing module 738 accesses the appropriate service model for the service and generates a request for the service according to the protocol and API required by the service based on the service model.

[0256] For example, if the restaurant has enabled an online reservation service, the restaurant submits a service model that specifies the necessary parameters for making a reservation and transmits the values ​​of the necessary parameters to the API of the online reservation service. When requested by the task flow processing module 736, the service processing module 738 can use the web address stored in the service model to establish a network connection with the online reservation service and send the necessary parameters for the reservation (e.g., time, date, party size) to the online reservation interface in a format according to the API of the online reservation service.

[0257] In some examples, the natural language processing module 732, the dialog flow processing module 734, and the task flow processing module 736 are used together and repeatedly to infer and define the user's intention, obtain information to further clarify and refine the user's intention, and finally generate a response (i.e., output to the user, or complete the task) to meet the user's intention. The generated response is a dialogue response to the voice input that at least partially meets the user's intention. In addition, in some examples, the generated response is output as a voice 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 can be processed to synthesize the dialogue response in the form of speech. In other examples, the generated response is data content related to satisfying the user request in the voice input.

[0258] In an example 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 the first structured query of the received structured query in an attempt to complete the first structured query and / or perform one or more tasks or actions represented by the first structured query. In some examples, the first structured query corresponds to the highest-ranked executable intent. In other examples, the first structured query is selected from the structured query received based on the combination of the corresponding speech recognition confidence score and the corresponding intent confidence score. In some examples, if the task flow processing module 736 encounters an error during the processing of the first structured query (e.g., due to the inability to determine the necessary parameters), the task flow processing module 736 may continue to select and process the second structured query corresponding to the executable intent with a lower ranking in the received structured query. For example, the second structured query is selected based on the speech recognition confidence score represented by the corresponding candidate text, the intent confidence score of the corresponding candidate executable intent, the missing necessary parameters in the first structured query, or any combination thereof.

[0259] The speech synthesis processing module 740 is configured to synthesize speech output for presentation to the user. The speech synthesis processing module 740 synthesizes speech output based on the text provided by the digital assistant. For example, the generated dialogue response is in the form of a text string. The speech synthesis processing module 740 converts the text string into an audible speech output. The speech synthesis processing module 740 uses any appropriate speech synthesis technology to generate speech output from the text, including but not limited to: concatenation synthesis, unit selection synthesis, diphone synthesis, domain-specific synthesis, formant synthesis, pronunciation synthesis, synthesis based on hidden Markov model (HMM) and sine wave synthesis. In some examples, the speech synthesis processing module 740 is configured to synthesize individual words based on phoneme strings corresponding to these words. For example, the phoneme string is associated with the words in the generated dialogue response. The phoneme string is stored in the metadata associated with the word. The speech synthesis processing module 740 is configured to directly process the phoneme string in the metadata to synthesize the words in speech form.

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

[0261] Additional details about digital assistants can be found in U.S. utility patent application 12 / 987,982, entitled “Intelligent Automated Assistant,” filed on January 10, 2011, and U.S. utility patent application 13 / 251,088, entitled “Generating and Processing Task Items That Represent Tasks to Perform,” filed on September 30, 2011, the entire disclosures of which are incorporated herein by reference.

[0262] 4. Digital Assistant User Interface

[0263] Figure 8A to Figure 8CT User interfaces and digital assistant user interfaces according to various examples are shown. Figure 8A to Figure 8CT To illustrate the process described below, which includes FIG. 17A to FIG. 17F process.

[0264] Fig. 8A An electronic device 800 is shown. Device 800 is implemented as device 104, device 122, device 200, or device 600. In some examples, device 800 at least partially implements digital assistant system 700. Fig. 8A In the example of the embodiment, device 800 is a smart phone 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.

[0265] exist Fig. 8A In the embodiment, the device 800 displays a user interface 802 on a display 801 that is different from a digital assistant (DA) user interface 803, as described below. Fig. 8A In the example of , 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, such as 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, etc.

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

[0267] In some examples, based on determining that the user input meets the criteria for initiating a DA, the device 800 displays the DA user interface 803 on top of the user interface. In some examples, displaying the DA user interface 803 (or another displayed element) on top of 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, based on determining that the user input does not meet the criteria for initiating a DA, the device 800 abandons displaying the DA user interface 803 and instead performs an action in response to the user input (e.g., updating the user interface 802).

[0268] Figure 8B DA user interface 803 is shown displayed on top of user interface 802. In some examples, such as Figure 8B As shown, the DA user interface 803 includes a DA indicator 804. In some examples, the indicator 804 is displayed in different states to indicate the corresponding state of the DA. The DA state includes a listening state (indicating that the DA is sampling voice input), a processing state (indicating that the DA is processing a natural language request), a speaking state (indicating that the DA is providing audio and / or text output), and an idle state. In some examples, the indicator 804 includes different visualization effects indicating different DA states, respectively. Figure 8B An indicator 804 is shown in a listening state as the DA is ready to accept voice input after initiating the DA based on detecting that the user input meets the criteria.

[0269] In some examples, the size of the indicator 804 in the listening state changes based on the received natural language input. For example, the indicator 804 expands and contracts in real time according to the amplitude of the received voice input. Figure 8C An indicator 804 of the listening state is shown. Figure 8C, the device 800 receives a natural language voice input "What's the weather like today?", and the indicator 804 expands and contracts in real time according to the voice input.

[0270] Fig.8D An indicator 804 of a processing state is shown, for example, indicating that the DA is processing the request "What's the weather like today?". Fig. 8E An indicator 804 of an in-speak state is shown, for example, indicating that the DA is currently providing an audio output in response to a request "It's a nice day today." Fig.8F Indicator 804 is shown in an idle state. In some examples, user input selecting indicator 804 in an idle state causes the DA (and indicator 804) to enter a listening state, eg, by activating one or more microphones to sample audio input.

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

[0272] 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 Device 800 is shown displaying a response affordance 805 including weather information in response to received voice input.

[0273] like FIG. 8E to FIG. 8F As shown, device 800 displays indicator 804 at a first portion of display 801 and displays response affordance 805 at a second portion of display 801. A portion of DA user interface 803 displayed above user interface 802 remains visible (e.g., not visually obscured) at a third portion of display 801. For example, before receiving user input that initiates 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 portion, the second portion, and the third portion of the display 801 are respectively referred to as the "indicator portion," the "response portion," and the "user interface (UI) portion."

[0274] In some examples, the UI portion is located between the indicator portion (displaying indicator 804) and the response portion (displaying response affordance 805). Fig.8F In some examples, the UI portion of user interface 802 includes (or is) a display area 8011 (e.g., a rectangular area) between the bottom of responsive affordance 805 and the top of indicator 804, wherein the side edges of display area 8011 are defined by the side edges of responsive affordance 805 (or 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, such as links and / or affordances, such as Fig.8F The home screen application display is displayed.

[0275] In some examples, device 800 displays response enable indication 805 in a first state. In some examples, the first state includes a compact state in which the display size of response enable indication 805 is smaller (e.g., compared to an expanded response enable indication state described below) and / or response enable indication 805 displays information in a compact (e.g., overview) form (e.g., compared to the expanded response enable indication state). In some examples, device 800 receives user input corresponding to a selection of response enable indication 805 in the first state, and in response, replaces the display of response enable indication 805 in the first state with the display of response enable indication 805 in a second state. In some examples, the second state is an expanded state in which the display size of response enable indication 805 is larger (e.g., compared to the compact state) and / or response enable indication 805 displays a larger amount of information / more detailed information (e.g., compared to the compact state). In some examples, device 800 displays response enable indication 805 in the first state by default, e.g., such that device 800 initially displays ( FIG. 8E to FIG. 8G )Response indication indicates 805.

[0276] FIG. 8E to FIG. 8G Response affordance 805 is shown in a first state. As shown, response affordance 805 compactly provides weather information, for example, by providing current temperature and conditions and omitting more detailed weather information (eg, hourly weather information). Figure 8G Device 800 is shown receiving user input 806 (e.g., a tap gesture) corresponding to selection of response affordance 805 in a first state. Figure 8G to Figure 8P The user input corresponding to the corresponding selection of the response enable indication is shown as a touch input, but in other examples, the user input corresponding to the selection of the response enable indication is another type of input, such as voice input (e.g., "show me more information") or peripheral device input (e.g., input from a mouse or trackpad). Figure 8HIt is shown that in response to receiving user input 806, device 800 replaces the display of response affordance 805 in the first state with the display of response affordance 805 in the second state. As shown, response affordance 805 in the second state now includes more detailed weather information.

[0277] In some examples, while displaying response-enabling indication 805 in the second state, device 800 receives user input requesting display of response-enabling indication 805 in the first state. In some examples, in response to receiving the user input, device 800 replaces display of response-enabling indication 805 in the second state with display of response-enabling indication 805 in the first state. Figure 8H In the example, the DA user interface 803 includes a selectable element (e.g., a back button) 807. User input selecting the selectable element 807 causes the device 800 to revert to the Fig.8F display.

[0278] In some examples, when response affordance 805 is displayed in the second state, device 800 receives user input corresponding to a selection of response affordance 805. In response to receiving the user input, device 800 displays a user interface of an application corresponding to response affordance 805. For example, Figure 8I Device 800 is shown receiving user input 808 (e.g., a tap gesture) corresponding to selection of response affordance 805. Figure 8J In response to receiving user input 808 , device 800 is shown displaying user interface 809 of a weather application.

[0279] In some examples, device 800 displays a selectable DA indicator when displaying a user interface of an application. For example, Figure 8J A selectable DA indicator 810 is shown. In some examples, while displaying the user interface of the application, the device 800 additionally or alternatively displays an indicator 804 at the first portion of the display 801, such as an indicator in an idle state.

[0280] In some examples, while displaying the user interface of the application, the device 800 receives user input selecting a selectable DA indicator. In some examples, in response to receiving the user input, the device 800 replaces the display of the user interface of the application with the DA user interface 803. In some examples, the DA user interface 803 is the DA user interface displayed immediately before the user interface of the application is displayed. For example, Figure 8K Device 800 is shown receiving user input 811 (eg, a tap gesture) selecting DA indicator 810 . Figure 8LIt is shown that in response to receiving user input 811, device 800 replaces display of the weather application's user interface 809 with display of the DA user interface 803.

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

[0282] In some examples, in response to receiving user input corresponding to a selection of the second portion of response-enabling indication 805, device 800 displays a user interface of an application corresponding to response-enabling indication 805 (e.g., without displaying response-enabling indication 805 in the second state). Figure 8M Device 800 is shown receiving user input 812 (e.g., a tap gesture) selecting a second portion of response affordance 805 to be displayed in a first state. Figure 8N Device 800 is shown displaying user interface 809 for a weather application (e.g., without displaying response affordance 805 in an expanded state) in response to receiving user input 812. Thus, a user may provide input that selects different portions of response affordance 805 to expand response affordance 805 or cause an application corresponding to response affordance 805 to be displayed, such as Figures 8G to 8H and Figures 8M to 8N shown.

[0283] Figure 8N Also shown is that when displaying user interface 809, device 800 displays a selectable DA indicator 810. User input selecting DA indicator 810 causes device 800 to revert to Figure 8M The display, for example, is similar to that of Figures 8K to 8L In some examples, while displaying the user interface 809 , the device 800 displays a DA indicator 804 (eg, a DA indicator in an idle state) at a first portion of the display 801 .

[0284] In some examples, for some types of response-indicating representations, user input corresponding to a selection of any portion of the response-indicating representation causes device 800 to display a user interface of an application corresponding to the response-indicating representation. In some examples, this is because the response-indicating representation cannot be displayed in a more detailed manner (e.g., in a second state). For example, there may be no additional information that the DA can provide in response to the natural language input. For example, consider the natural language input "What is 5 times 6?". Fig.8O DA user interface 803 displayed in response to natural language input is shown. DA user interface 803 includes response affordance 813 displayed in a first state. Response affordance 813 includes the answer "5 x 6 = 30", but there is no additional information that the DA can provide. Fig.8O Also shown is device 800 receiving user input 814 (e.g., a tap gesture) selecting a first portion of response indication 813. Figure 8P It is shown that in response to receiving user input 814, device 800 displays a user interface 815 corresponding to an application corresponding to response enable indication 813, such as a calculator application user interface.

[0285] In some examples, the response affordance includes a selectable element, such as selectable text indicating a link. Figure 8Q DA user interface 803 is shown displayed in response to the natural language input "Tell me more about Famous Band." DA user interface 803 includes response affordance 816. Response affordance 816 includes information about "Famous Band" and a selectable element 817 corresponding to member #1 of "Famous Band." In some examples, device 800 receives user input corresponding to selection of a selectable element and, in response, displays an affordance corresponding to the selectable element over the response affordance (a second response affordance). Figure 8R Device 800 is shown receiving user input 818 (eg, a tap gesture) selecting selectable element 817 . Figure 8S It is shown that in response to receiving user input 818, device 800 displays a second response-enabling representation 819 including information about member #1 over response-enabling representation 816 to form a response-enabling representation stack.

[0286] In some examples, when displaying the second response enable representation over the response enable representation, device 800 visually conceals a user interface at or a portion of a third portion (e.g., the portion does not display any response enable representation or indicator 804) of display 801. In some examples, visually concealing the user interface includes dimming the user interface or blurring the user interface. Figure 8SDevice 800 is shown visually obscuring user interface 802 at a third portion of display 801 while second response enable indication 819 is displayed over response enable indication 816 .

[0287] Figure 8S It is shown that when second response-enabling representation 819 is displayed over a portion of response-enabling representation 816, that portion remains visible. In other examples, second response-enabling representation 819 replaces the display of response-enabling representation 816 so that no portion of response-enabling representation 816 is visible.

[0288] Figure 8T Device 800 is shown receiving user input 820 (e.g., a tap gesture) selecting selectable element 821 (“Detroit”) in second response affordance 819. Figure 8U Device 800 is shown displaying, in response to receiving user input 820, third response-enabling indication 822 over second response-enabling indication 819. Third response-enabling indication 822 includes information regarding Detroit, the birthplace of member #1. Figure 8U The user interface 802 is shown continuing to be visually obscured at the third portion of the display 801 .

[0289] Figure 8U It is also shown that although there are three response enable representations (e.g., 816, 819, and 822) in the response enable representation stack, the device 800 only indicates two response enable representations in the stack. For example, the third response enable representation 822 and a portion of the second response enable representation 819 are displayed, but no portion of response enable representation 816 is displayed. Therefore, in some examples, when more than two response enable representations are stacked, the device 800 only visually indicates that there are two response enable representations in the stack. In other examples, when the response enable representations are stacked, the device 800 only visually indicates a single response enable representation of the stack (e.g., such that the display of the next response enable representation completely replaces the display of the previous response enable representation).

[0290] Figure 8V to Figure 8Y The user is shown providing input to return to a previous response affordance in the stack. Specifically, Figure 8V , device 800 receives user input 823 (e.g., a swipe gesture) on third response enable indication 822 requesting return to second response enable indication 819. Figure 8W Device 800 is shown to cease displaying third response-enabling representation 822 and fully display second response-enabling representation 819 in response to receiving user input 823. Device 800 also displays (eg, reveals) a portion of response-enabling representation 816. Figure 8XDevice 800 is shown receiving user input 824 (e.g., a swipe gesture) on second response-enabling indication 819 requesting return to response-enabling indication 816. Figure 8Y It is shown that in response to receiving user input 824, device 800 stops displaying second response-enabling representation 819 and fully displays response-enabling representation 816. In some examples, device 800 receives input to display the next response-enabling representation in the stack (e.g., a swipe gesture in the opposite direction), and in response, displays the next response-enabling representation in the stack in a manner similar to that described above. In other examples, navigating among response-enabling representations in the stack relies on other input methods (e.g., user selection of a displayed "back" or "next" button) in a manner similar to that described above.

[0291] Figure 8Y It is also shown that the user interface 802 is no longer visually obscured at the third portion of the display 801. Thus, in some examples, such as Figure 8Q to Figure 8Y As shown, user interface 802 is visually obscured when the response affordances are stacked, and is not visually obscured when the affordances are not stacked. For example, when initial response affordance 816 is not displayed (or only partially displayed), user interface 802 is visually obscured, and when initial response affordance 816 is fully displayed, user interface 802 is not visually obscured.

[0292] In some examples, a user interface (e.g., a user interface on which DA user interface 803 is displayed) includes an input field that occupies a fourth portion (e.g., an "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, such as a messaging application, an email application, a note-taking application, a reminder application, a calendar application, etc. Figure 8Z A user interface 825 of a messaging application is shown that includes an input field 826 occupying a fourth portion of the display 801 .

[0293] Figure 8AA DA user interface 803 is shown displayed over user interface 825. Device 800 displays user interface 803 in response to the natural language input "What is the title of this song?" 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.

[0294] In some examples, device 800 receives user input corresponding to a displacement of a response affordance from a first portion of display 801 to a fourth portion of display 801. In response to receiving the user input, device 800 replaces display of the response affordance at the first portion of display 801 with display of the response affordance in the input field. For example, Figures 8AB to 8AD Device 800 is shown receiving user input 828 to shift response affordance 827 from the first portion of display 801 to input field 826. User input 828 corresponds to a drag gesture from the first portion of display 801 to a fourth portion of display 801 and ends with a lift-off event (e.g., a finger lift-off event) at the display of input field 826.

[0295] In some examples, such as Figures 8AB to 8AD As shown, upon receiving user input 828, device 800 continuously shifts response enable indication 827 from the first portion of display 801 to the fourth portion of display 801. For example, as response enable indication 827 is shifted, device 800 displays response enable indication 827 at a location corresponding to the corresponding current displayed contact location of user input 828. In some examples, as response enable indication 827 is shifted, the displayed size of response enable indication 827 is reduced, e.g., such that response enable indication 827 shrinks under the user's finger (or other input device) as it is shifted. Figures 8AB to 8AD It is also shown that when the continuous shift response indication 827 is enabled, the indicator 804 stops being displayed.

[0296] Figure 8AD A response enable indication 827 is shown now displayed in the input field 826 of the messaging application. Figure 8AE Device 800 is shown receiving user input 830 (e.g., a tap gesture) corresponding to a selection of send message enable indication 829. Figure 8AF In response to receiving user input 830, device 800 is shown sending response affordance 827 as a message. Thus, a user can send a response affordance in a communication (e.g., a text message, an email) by providing input (e.g., dragging and dropping) to shift the response affordance into the appropriate input field. In other examples, a user can include a response affordance in a note, a calendar entry, a word processing document, a reminder entry, etc. in a similar manner.

[0297] In some examples, user input corresponding to a displacement of a response affordance from a first portion of display 801 to a fourth portion of display 801 (displaying an input field) corresponds to a selection of an affordance. In some examples, the affordance is a share affordance (e.g., share the response affordance in a communication) or a save affordance (e.g., save the affordance in a note or reminder entry). For example, when device 800 displays DA user interface 803 on top of 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 with an input field (e.g., word processing, reminders, calendar, notes), the response affordance includes a save affordance. User input selecting to share or save affordance causes device 800 to replace display of the response affordance at the first portion of display 801 with display of the response affordance in the input field in a manner similar to that described above. For example, when a response enable indication is displayed in the input field, the device 800 stops displaying the indicator 804.

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

[0299] In some examples, device 800 receives user input corresponding to a displacement of the responsive affordance from the first portion of display 801 to the fifth portion of display 801. In some examples, in response to receiving the user input, device 800 replaces display of the responsive affordance at the first portion of the display with display of the responsive affordance in the widget area. For example, Figures 8AH to 8AJDevice 800 is shown receiving user input 834 to shift response enable indication 833 from the first portion of display 801 to widget area 832. User input 834 corresponds to a drag gesture from the first portion of display 801 to the fifth portion of display 801 and ends with a lift-off event at the display of widget area 832. In some examples, shifting response enable indication 833 from the first portion of display 801 to the fifth portion of display 801 is performed in a manner similar to the shifting of response enable indication 827 described above. For example, while response enable indication 833 is shifted, indicator 804 ceases to be displayed.

[0300] Figure 8AJ It is shown that response affordance 833 is now displayed in widget area 832 along with the displayed calendar and music widgets. In this way, the user can provide input (e.g., drag and drop) to shift response affordance 833 to widget area 832 to add response affordance 833 as a widget.

[0301] In some examples, user input corresponding to a displacement of the responsive enable representation from the first portion of the display 801 to the fifth portion of the display 801 corresponds to a selection of the enable representation. In some examples, the enable representation is a "show in widget" enable representation. For example, when the device 800 displays the DA user interface 803 over a user interface that includes a widget area, the responsive enable representation includes a "show in widget" enable representation. User input selecting the "show in widget" enable representation causes the device 800 to replace display of the responsive enable representation at the first portion of the display 801 with display of the responsive enable representation in the widget area in a manner similar to that described above.

[0302] In some examples, the response enable indication corresponds to an event, and the device 800 determines completion of the event. In some examples, in response to determining completion of the event, the device 800 stops displaying the response enable indication in the desktop widget area (e.g., within a predetermined duration after determining completion). For example, the response enable indication 833 corresponds to a flight, and in response to determining that the flight has been completed (e.g., landed), the device 800 stops displaying the response enable indication 833 in the desktop widget area 832. For another example, the response enable indication corresponds to a sports game, and in response to determining that the sports game has ended, the device 800 stops displaying the response enable indication in the desktop widget area.

[0303] Figures 8AK to 8AN Various exemplary types of response affordances are shown. Specifically, Figure 8AKCompact response affordances 835 are shown displayed in response to a natural language request, “How old is celebrity X?” Compact response affordances 835 include a direct answer to the request (e.g., “30 years old”) without further information (e.g., additional information about celebrity X). In some examples, all compact response affordances have the same maximum size, so that the compact response affordances can only occupy a (relatively small) area of ​​display 801. Figure 8AL Detailed response affordance 836 is shown displayed in response to a natural language request “Give me statistics about team #1.” Detailed response affordance 836 includes detailed information about team #1 (e.g., various statistics) and has a larger display size than compact response affordance 835. Figure 8AM List response affordance 837 is shown displayed in response to the natural language “Show me a list of nearby restaurants.” List response affordance 837 includes a list of options (e.g., restaurants) and has a larger display size than compact response affordance 835. Figure 8AN A disambiguation response affordance 838 is shown 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 an audio output asking "Which Neal?"

[0304] like Figures 8AK to 8AN As shown, the type of response affordance displayed (e.g., compact, detailed, list, disambiguation) depends on the content of the natural language input and / or the DA's interpretation of the natural language input. In some examples, the affordance construction rule specifies a particular type of response affordance to be displayed for a particular type of natural language input. In some examples, the construction rule specifies a default attempt to display a compact response affordance, e.g., causing the device 800 to display a compact response affordance in response to a natural language input that can be adequately answered by a compact response affordance. In some examples, when a response affordance can be displayed in different states (e.g., a first compact state and a second expanded (detailed) state), the construction rule specifies that the response affordance is initially displayed as a compact affordance. As relative to Figures 8G to 8H As described, in response to receiving appropriate user input, a detailed version of the compact affordance may be made available for display. It should be appreciated that some natural language inputs (e.g., "Give me statistics about Team #1" and "Show me a list of nearby restaurants") cannot be adequately answered with a compact affordance (or it may not be desirable to answer the input with a compact affordance). Therefore, a construction rule may specify a particular type of affordance (e.g., a detailed list) to be displayed for such input.

[0305] In some examples, the DA determines multiple results corresponding to the received natural language input. In some examples, the device 800 displays a response-enabling representation that includes a single result from the multiple results. In some examples, when the response-enabling representation is displayed, other results from the multiple results are not displayed. For example, consider the natural language input "nearest coffee." The DA determines multiple results (multiple nearby coffee shops) corresponding to the input. Figure 8AO A response affordance 839 (e.g., a compact affordance) is shown displayed in response to the input. Response affordance 839 includes a single result from the multiple results (the coffee shop closest to the location of device 800). Device 800 also provides speech output "This is the closest coffee shop." In this way, for a natural language request involving multiple results, the DA can initially provide a single result, e.g., the most relevant result.

[0306] In some examples, after providing a single result (e.g., displaying response affordance 839), the DA provides the next result in the plurality of results. Figure 8AP , device 800 replaces response affordance 839 with response affordance 840 including the second closest coffee shop. Device 800 also provides speech output “This is the second closest coffee shop.” In some examples, in response to receiving user input rejecting a single result (e.g., “I don’t want to go to that coffee shop”) or indicating that the next result should be provided, device 800 replaces response affordance 839 with response affordance 840 including the second closest coffee shop. Device 800 also provides speech output “This is the second closest coffee shop.” Figure 8AO Transformed into Figure 8AP In some examples, after displaying affordance 839 and / or within a predetermined duration after providing voice output “This is the nearest coffee shop,” if, for example, no user input selecting affordance 839 is received, device 800 may exit from Figure 8AO Transformed into Figure 8AP In this way, device 800 can sequentially provide results for natural language input involving multiple results.

[0307] In some examples, the response affordance includes one or more task affordances. User input (e.g., a tap gesture) that selects a task affordance causes device 800 to perform the corresponding task. Figure 8AN, response affordance 838 includes task affordances 841, 842, and 843. The user's selection of task affordance 841 causes device 800 to initiate a phone call to Neal Ellis, the user's selection of task affordance 842 causes device 800 to initiate a phone 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. The user's selection of task affordance 844 causes device 800 to launch a map application that displays a route to the nearest coffee shop, and the user's selection of task affordance 845 causes device 800 to launch a map application that displays a route to the second nearest coffee shop.

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

[0309] For example, consider the natural language input "Beyoncé". Figure 8AQ Response affordances 846, 847, and 848 are shown displayed simultaneously in response to natural language input. Response affordances 846, 847, and 848 correspond to a news domain (e.g., a user requests news about Beyoncé), a music domain (e.g., a user requests to play Beyoncé's music), and a knowledge domain (e.g., a user requests information about Beyoncé), respectively. In some examples, corresponding user input corresponding to selection of response affordances 846, 847, and 848 causes device 800 to perform corresponding actions. For example, selection of response affordance 846 causes display of a detailed response affordance including news about Beyoncé, selection of response affordance 847 causes device 800 to launch a music application including songs by Beyoncé, and selection of response affordance 848 causes display of a detailed response affordance including information about Beyoncé.

[0310] In some examples, the response affordance includes an editable text field that includes text determined based on natural language input. Figure 8ARResponse affordance 849 is shown displayed in response to the natural language speech input "text mom I'm home". Response affordance 849 includes an editable text field 850 that includes the text "I'm hole", for example, because the DA mistakenly identified "I'm home" as "I'm hole". Response affordance also includes task affordance 851. User input selecting task affordance 851 causes device 800 to send a text message.

[0311] In some examples, device 800 receives user input corresponding to a selection of an editable text field and, in response, displays a keyboard while displaying a response affordance. Figure 8AS Device 800 is shown receiving user input 852 (eg, a tap gesture) selecting editable text field 850 . Figure 8AT In response to receiving user input 852, device 800 is shown displaying keyboard 853 while displaying response affordance 849. As shown, device 800 displays keyboard 853 on top of user interface 802 (e.g., a user interface on which DA user interface 803 is displayed). Figure 8AT to Figure 8AV It is shown that when the response enable indication and the keyboard are displayed over the user interface 802, a portion of the user interface 802 is not visually obscured, but in other examples, at least a portion of the user interface 802 (e.g., a portion of the display 801 that does not display the keyboard or the response enable indication 849) is visually obscured.

[0312] In some examples, device 800 receives one or more keyboard inputs and, in response, updates text in the editable text field based on the one or more keyboard inputs. Figure 8AU Device 800 is shown to have received keyboard input correcting "hole" to "home." Device 800 displays the corrected text in editable text field 850 in response to affordance 849.

[0313] In other examples, device 800 receives a voice input requesting to edit text displayed in an editable text field. In response to receiving the voice input, device 800 updates the text in the editable text field according to the voice input. Figure 8AR , the user may provide voice input "No, I said I'm home" to cause the device 800 to update the text in the editable text field 850 accordingly.

[0314] In some examples, after updating the text in the editable text field, device 800 receives user input requesting to perform 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, Figure 8AV It is shown that after editing "hole" to "home", device 800 receives user input 854 (e.g., a tap gesture) corresponding to selection of task enable representation 851. Figure 8AW Device 800 is shown sending a message "I'm home" to the user's mom in response to receiving user input 854. Device 800 also displays a flag symbol 855 indicating completion of the task. Figure 8AW Further illustrated is that in response to receiving user input 854 , device 800 ceases to display keyboard 853 to display (eg, reveal) a portion of user interface 802 , and device 800 displays indicator 804 .

[0315] In this way, the user can edit the text included in the response affordance (e.g., if the DA incorrectly recognized the user's voice input) and have the DA perform an action using the correct text. Figure 8AR to Figure 8AW An example of editing and sending a text message is shown, but in other examples, a user may similarly edit and save (or send) notes, calendar entries, reminder entries, email entries, etc.

[0316] In some examples, device 800 receives user input to eliminate DA. In some examples, eliminating DA includes stopping displaying DA user interface 803. Figure 10A to Figure 10V DA elimination is discussed in more detail. In some examples, after eliminating the DA, the device 800 receives user input to re-initiate the DA (e.g., user input that meets the criteria for initiating the DA). In some examples, based on receiving the user input to re-initiate the DA, the device 800 displays a DA user interface that includes the same response enable representation, e.g., the response enable representation displayed before the DA was eliminated.

[0317] In some examples, device 800 displays the same response affordance based on determining that the same response affordance corresponds to a response to a received natural language input (e.g., input intended for a reinitiated DA). Figure 8AX DA user interface 803 is shown including response affordance 856. Device 800 displays DA user interface 803 in response to the natural language input "What's the weather like?" Figure 8AY Device 800 is shown receiving user input 857 to dismiss the DA, such as a tap gesture corresponding to selection of user interface 802 . Figure 8AZIt is shown that in response to receiving user input 857, the device 800 eliminates the DA, for example, stops displaying the DA user interface 803. Figure 8BA It is shown that the device 800 has received an input to reinitiate the DA and is currently receiving the natural language input "Will it be windy?". Figure 8BB Device 800 is shown displaying a DA user interface 803 that includes the same response-indicator 856 and provides a speech output of “Yes, it will be windy.” For example, the DA has determined that the same response-indicator 856 corresponds to the natural language inputs “What’s the weather like?” and “Will it be windy?” Thus, a previous response-indicator may be included in a subsequently initiated DA user interface if the previous response-indicator is relevant to the current natural language request.

[0318] In some examples, device 800 displays the same response affordance based on determining that user input to re-initiate the DA is received within a predetermined duration of eliminating the DA. Figure 8BC DA user interface 803 is shown displayed in response to the natural language input "What is 3 times 5?" DA user interface 803 includes response affordance 858. Figure 8BD It shows that DA has been eliminated for the first time. Figure 8BE It is shown that within a predetermined duration (e.g., 5 seconds) of the first time, the device 800 has received a user input to re-initiate a DA. For example, the device 800 has received any of the types of inputs that meet the criteria for initiating a DA described above, but has not yet received another natural language input that includes a different request for a DA. Figure 8BE , device 800 displays a DA user interface 803 including the same response enable representation 858 and the indicator 804 of the listening state. In this way, if the user quickly re-initiates the DA, for example because the user accidentally eliminated the DA previously, the previous response enable representation can be included in the subsequently initiated DA user interface.

[0319] Figure 8BF Device 800 is shown 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, Figure 8BF Messaging application user interface 859 is shown displayed in landscape mode. In some examples, device 800 displays DA user interface 803 in landscape mode on top of the user interface in landscape mode. For example, Figure 8BG DA user interface 803 is shown displayed in landscape mode atop user interface 859. It should be appreciated that a user can provide one or more inputs to interact with DA user interface 803 in landscape mode in a manner consistent with the techniques discussed herein.

[0320] 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 that do not have a landscape mode include a home screen user interface and a lock screen user interface. Figure 8BH Home screen user interface 860 is shown displayed when device 800 is in a landscape orientation (it does not have a landscape mode).

[0321] In some examples, when device 800 is in landscape orientation, device 800 displays DA user interface 803 on top of a user interface that does not have a landscape mode. In some examples, when DA user interface 803 (in landscape mode) is displayed on top of a user interface that does not have a landscape mode, device 800 visually masks the user interface, e.g., visually masks portions of the user interface that do not display DA user interface 803. For example, Figure 8BI The device 800 in a landscape orientation is shown 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 (even though the device 800 is in a landscape orientation) because the home screen user interface 860 does not have a landscape mode. As shown, the device 800 visually masks the home screen user interface 860. In this way, the device 800 avoids simultaneously displaying the DA user interface 803 in landscape mode and a user interface in portrait mode that is not visually masked (e.g., the home screen user interface 860), which may provide a confusing user visual experience.

[0322] In some examples, when device 800 displays DA user interface 803 over a user interface of a predetermined type, device 800 visually masks the user interface of the predetermined type. An exemplary predetermined type of user interface includes a lock screen user interface. Figure 8BJ Device 800 is shown displaying an exemplary lock screen user interface 861 . Figure 8BK The device 800 is shown displaying the DA user interface 803 over the lock screen user interface 861. As shown, the device 800 visually masks the lock screen user interface 861 at a portion over the lock screen user interface 861 where the DA user interface 803 is not displayed.

[0323] In some examples, the DA user interface 803 includes a conversation affordance. In some examples, the conversation affordance includes a conversation generated by the DA in response to received natural language input. In some examples, the conversation affordance is displayed at a sixth portion (e.g., a "conversation portion") of the display 801, the sixth portion of the display 801 being located between a first portion of the display 801 (displaying the DA indicator 804) and a second portion of the display 801 (displaying the response affordance). For example, Figure 8BL A dialog affordance 862 is shown that includes a dialog generated by the DA in response to the natural language input "Play Frozen," discussed further below. Figure 8BM A dialog affordance 863 is shown that includes a dialog generated by the DA in response to the natural language input "Delete Meeting #1," as will be discussed further below. Figure 8BM Device 800 is also shown displaying a conversation enable indication 863 at a sixth portion of display 801 , the sixth portion being between the display of indicator 804 and the display of response enable indication 864 .

[0324] In some examples, the DA determines a plurality of selectable disambiguation options for the received natural language input. In some examples, the dialog represented by the dialog affordance includes the plurality of selectable disambiguation options. In some examples, the plurality of disambiguation options are determined based on the DA determining that the natural language input is ambiguous. The ambiguous natural language input corresponds to a plurality of possible executable intents, e.g., each executable intent having a relatively high (and / or equal) confidence score. For example, consider Figure 8BL DA determines two selectable disambiguation options: option 865 "Play movie" (e.g., the user wants to play the movie "Frozen") and option 866 "Play music" (e.g., the user wants to play the music in the movie "Frozen"). Dialog affordance 862 includes options 865 and 866, where the user's selection of option 865 causes device 800 to play the movie "Frozen", and the user's selection of option 866 causes device 800 to play the music in the movie "Frozen". For another example, consider Figure 8BM 863 includes options 867 and 868, as well as a cancel option 869.

[0325] In some examples, the DA determines that additional information is required to perform a task based on the received natural language input. In some examples, the conversation represented by the conversation affordance includes one or more selectable options recommended by the DA for the required additional information. For example, the DA may have determined the domain of the received natural language input, but cannot determine the parameters required 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 executable intent to make a phone call), but cannot determine the parameters (i.e., who to call). In some examples, the DA therefore determines one or more selectable options as recommendations for the parameters. For example, the device 800 displays selectable options corresponding to the contacts that the user calls most frequently in the conversation affordance. The user's selection of any of the selectable options causes the device 800 to call the corresponding contact.

[0326] 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 the primary user intent, while the dialog of the simultaneously displayed dialog affordance includes a selectable option corresponding to the alternate user intent. For example, Figure 8BN DA user interface 803 is shown displayed in response to the natural language input "directions to Phil." The DA determines a primary user intent, namely that the user wants to get directions to "Phil's coffee," and an alternative user intent, namely that the user wants to get directions to the home of a contact named "Phil." DA user interface 803 includes response affordance 870 and dialog affordance 871 corresponding to the primary user intent. Dialog 872 of dialog affordance 871 corresponds to the secondary user intent. User input selecting dialog 872 causes device 800 to obtain directions to the home of a contact named "Phil," while user input selecting response affordance 870 causes device 800 to obtain directions to "Phil's coffee."

[0327] In some examples, the conversation affordance is displayed in a first state. In some examples, the first state is an initial state, e.g., a description of how the conversation affordance is initially displayed before receiving user input to interact with the conversation affordance. Figure 8BO DA user interface 803 is shown including a dialog affordance 873 displayed in an initial state. Device 800 displays DA user interface 803 in response to a natural language input, "What's the weather like?" Dialog affordance 873 includes at least a portion of a dialog generated by the DA in response to the input, e.g., "The current temperature is 70 degrees and it's windy...". Figures 11 to 16 Let's discuss further description on whether to display the dialogue generated by DA.

[0328] In some examples, device 800 receives user input corresponding to a selection of a conversation enable representation displayed in a first state. In response to receiving the user input, device 800 replaces the display of the conversation enable representation in the first state with the display of the conversation enable representation in the second state. In some examples, the second state is an expanded state, wherein the display size of the conversation enable representation in the expanded state is larger than the display size of the conversation enable representation in the initial state, and / or wherein the conversation enable representation in the expanded state displays a larger amount of content than the conversation enable representation in the initial state. Figure 8BP Device 800 is shown receiving user input 874 (e.g., a drag gesture) corresponding to a selection of conversation affordance 873 displayed in an initial state. Figure 8BQ 874 (or a portion thereof), device 800 replaces display of dialog affordance 873 in an initial state with display of dialog affordance 873 in an expanded state. Figure 8BP Compared with the dialogic affordances in Figure 8BQ The dialog indicator 873 has a larger display size and includes a larger amount of text.

[0329] In some examples, the displayed size of the dialog affordance (in the second state) is proportional to the length of the user input that caused the dialog affordance to be displayed in the second state. Figure 8BP to Figure 8BQ , the displayed size of dialog affordance 873 increases in proportion to the length (e.g., physical distance) of drag gesture 874. Thus, the user can provide a continuous drag gesture to expand response affordance 873 according to the drag length of the drag gesture. Figure 8BO to Figure 8BQ The device 800 is shown initially displaying Figure 8BO The dialogue affordance shown indicates 873, and then expands Figure 8BQ , but in other examples, the device 800 initially displays Figure 8BQ Conversation affordance 873 is shown. Thus, in some examples, device 800 initially displays the conversation affordance such that the conversation affordance displays a maximum amount of content, e.g., without obscuring (covering) any simultaneously displayed response affordance.

[0330] In some examples, display of the conversation affordance obscures display of a simultaneously displayed response affordance. Specifically, in some examples, display of the conversation affordance in the second (e.g., expanded) state occupies at least a portion of the second portion of display 801 (where the response affordance is displayed). In some examples, displaying the conversation affordance in the second state also includes displaying the conversation affordance over at least a portion of the response affordance. For example, Figure 8BQ Drag gesture 874 is shown continuing. Figure 8BR It is shown that in response to receiving the continue drag gesture 874, the device 800 expands the display of the conversation enable indication 873 on top of the display of the response enable indication 875.

[0331] In some examples, the response affordance is displayed in an initial state prior to receiving user input that causes the conversation affordance to be displayed in a second state (e.g., expanded). In some examples, the initial state describes the state of the response affordance before the conversation affordance (or a portion thereof) is displayed over the response affordance. For example, Figure 8BO to Figure 8BQ Response-enabling representation 875 is shown displayed in an initial state. In some examples, displaying the conversation-enabling representation in a second (e.g., expanded) state over at least a portion of the response-enabling representation includes replacing display of the response-enabling representation in the initial state with display of the response-enabling representation in an overlaid state. Figure 8BR A response affordance 875 is shown displayed in an overlay state. In some examples, when displayed in an overlay state, the display size of the response affordance shrinks (e.g., relative to an initial state) and / or dims (e.g., the color displayed is darker than the initial state). In some examples, the extent to which the response affordance shrinks and / or dims is proportional to the amount of the conversation affordance displayed over the response affordance.

[0332] In some examples, the conversation enable representation has a maximum display size, and the second (e.g., expanded) state of the conversation enable representation corresponds to the maximum display size. In some examples, the conversation enable representation displayed at the maximum display size cannot be further expanded in response to user input such as a drag gesture. In some examples, the conversation enable representation displayed at the maximum display size displays the entire contents of the conversation enable representation. In other examples, the conversation enable representation displayed at the maximum display size does not display the entire contents of the conversation enable representation. Therefore, in some examples, when device 800 displays the conversation enable representation in the second state (which has the maximum display size), device 800 enables user input (e.g., a drag gesture / swipe gesture) to scroll through the contents of the conversation enable representation. Figure 8BS The dialog affordance 873 is shown displayed at the maximum display size. Figure 8BRIn response to receiving the continue drag gesture 874, Figure 8BS , device 800 displays (e.g., expands) dialog affordance 873 to its maximum display size. Dialog affordance 873 includes scroll indicator 876, which indicates that the user can provide input to scroll through the content of dialog affordance 873.

[0333] In some examples, when the conversation affordance is displayed in the second state (and displayed at its maximum size), a portion of the response affordance remains visible. Thus, in some examples, device 800 constrains the maximum size of the conversation affordance displayed over the response affordance so that the conversation affordance does not completely cover the response affordance. In some examples, the portion of the response affordance that remains visible is the portion of the response affordance described above with respect to Figure 8M The second portion of the response affordance, for example, is the top portion of the response affordance including a symbol indicating the category of the response affordance and / or associated text. Figure 8BS It is shown that when device 800 displays conversation enable indication 873 at a maximum size above response enable indication 875, the top portion of response enable indication 875 remains visible.

[0334] In some examples, device 800 receives user input corresponding to a selection of a portion of a response-enable representation that remains visible (when the conversation-enable representation is displayed in a second state over the response-enable representation). In response to receiving the user input, the device displays the response-enable representation at a first portion of display 801, e.g., displaying the response-enable representation in its initial state. In response to receiving the user input, device 800 further replaces display of the conversation-enable representation in the second (e.g., expanded) state with display of the conversation-enable representation in a third state. In some examples, the third state is a compressed state, wherein the conversation-enable representation in the third state has a smaller display size (compared to the conversation-enable representation in the initial state or expanded state), and / or the conversation-enable representation includes a smaller amount of content (compared to the conversation-enable representation in the initial state or expanded state). In other examples, the third state is the first state (e.g., the initial state). Figure 8BT Device 800 is shown receiving user input 877 (e.g., a tap gesture) selecting a top portion of response affordance representation 875. Figure 8BU In response to receiving user input 877, device 800 replaces the display of dialog affordance 873 in an expanded state ( Figure 8BT ) displays a dialog enable indication 873. Device 800 further displays a response enable indication 875 in an initial state.

[0335] In some examples, device 800 receives user input corresponding to a selection of a conversation affordance displayed in the third state. In response to receiving the user input, device 800 replaces display of the response affordance in the third state with display of the conversation affordance in the first state. Figure 8BU In the embodiment of the present invention, the user may provide input (e.g., a tap gesture) to select conversation affordance 873 to be displayed in a compressed state. In response to receiving the input, device 800 displays the conversation affordance in an initial state, e.g., reverting to Figure 8BO display.

[0336] In some examples, when a conversation affordance is displayed in a first state or a second state (e.g., an initial state or an expanded state), device 800 receives user input corresponding to a selection of a simultaneously displayed response affordance. In response to receiving the user input, device 800 replaces display of the conversation affordance in the first state or the second state with display of the conversation affordance in a third (e.g., compressed) state. For example, Figure 8BV DA user interface 803 is shown displayed in response to the natural language input "Show me the roster for team #1." DA user interface 803 includes detailed response affordance 878 and dialog affordance 879 displayed in an initial state. Figure 8BV Also shown is device 800 receiving user input 880 (e.g., a drag gesture) selecting response affordance representation 878. Figure 8BW It is shown that in response to receiving user input 880, device 800 replaces the display of conversation enable indication 879 in the initial state with the display of conversation enable indication 879 in the compressed state.

[0337] In some examples, when the conversation affordance is displayed in a first state or a second state (e.g., an initial state or an expanded state), device 800 receives user input corresponding to a selection of the conversation affordance. In response to receiving the user input, device 800 replaces the display of the conversation affordance in the first state or the second state with the display of the conversation affordance in a third (e.g., a compressed) state. For example, Figure 8BX DA user interface 803 is shown displayed in response to the natural language input "What music can you provide me?" DA user interface 803 includes response affordance 881 and conversation affordance 882 displayed in an initial state. Figure 8BX Also shown is device 800 receiving user input 883 (e.g., a downward drag or swipe gesture) selecting dialog affordance representation 882. Figure 8BY In response to receiving user input 883, device 800 replaces display of dialog affordance 882 in the initial state with display of dialog affordance 882 in the compressed state. Figure 8BX to Figure 8BYThe user input corresponding to selection of a conversation affordance is shown to be a drag or swipe gesture, but in other examples, the user input is a selection of a displayed affordance included in the conversation affordance. For example, a user input (e.g., a tap gesture) selecting to "compress" an affordance in a conversation affordance displayed in a first state or a second state causes device 800 to replace display of the conversation affordance in the first state or the second state with display of the conversation affordance in a third state.

[0338] In some examples, device 800 displays a transcription of the received natural language speech input in the dialog affordance. The transcription is obtained by performing automatic speech recognition (ASR) on the natural language speech input. Figure 8BZ A DA user interface 803 is shown displayed in response to a natural language voice input of "How's the weather?". The DA user interface includes a response affordance 884 and a dialog affordance 885. The dialog affordance 885 includes a transcription 886 of the voice input and a dialog 887 generated by the DA in response to the voice input.

[0339] In some examples, the device 800 does not display the transcription of the received natural language voice input by default. In some examples, the device 800 includes a setting that, when activated, causes the device 800 to always display the transcription of the natural language voice input. Various other examples in which the device 800 can display the transcription of the received natural language voice input are now discussed.

[0340] In some examples, a natural language voice input (with a displayed transcription) is consecutive to a second natural language voice input received prior to the natural language voice input. In some examples, displaying the transcription is performed based on determining that the DA cannot determine the user intent of the natural language voice input and cannot determine the second user intent of the second natural language voice input. Thus, in some examples, if the DA cannot determine an executable intent for two consecutive natural language inputs, the device 800 displays the transcription of the natural language input.

[0341] For example, Figure 8CA It is shown that device 800 has received the voice input "how far to Dish n' Dash?", and the DA cannot determine the user's intention of the natural language input. For example, device 800 provides an audio output "I'm not sure I understand, can you please say that again?". Therefore, the user repeats the voice input. For example, Figure 8CB Device 800 is shown receiving a subsequent voice input of "how far to Dish n'Dash?". Figure 8CCIt is shown that the DA still cannot determine the user intent of the continuous voice input. For example, the device 800 provides an audio output of "I'm not sure I understand". Therefore, the device 800 also displays a dialogue enabling representation 888 including a transcription 889 of the subsequent voice input "how far to Rish and Rash?". In this example, the transcription 889 reveals that the DA incorrectly identified "how far to Dish n'Dash?" as "how far to Rish and Rash?" twice. Since "Rish and Rash" may not be a real location, the DA cannot determine the user intent of the two voice inputs.

[0342] In some examples, transcription of the received natural language speech input is performed based on determining that the natural language speech input repeats a previous natural language speech input. Figure 8CD DA user interface 803 is shown displayed in response to the speech input (previous speech input) "where is Starbucks?" The DA incorrectly recognizes the speech input as "where is Star Mall?" and therefore displays a response affordance 890 including "Star Mall." Because the DA incorrectly understands the speech input, the user repeats the speech input. For example, Figure 8CE Device 800 is shown receiving a repetition (eg, a consecutive repetition) of a previous voice input "where is Starbucks?" The DA determines that the voice input repeats a previous voice input. Figure 8CF It is shown that based on such a determination, device 800 displays conversation affordance 891 including transcription 892. Transcription 892 reveals that the DA (e.g., twice) incorrectly identified "where is Starbucks?" as "where is Star Mall?".

[0343] In some examples, after receiving a natural language voice input (e.g., for which a transcription is to be displayed), the device receives a second natural language voice input subsequent to the natural language voice input. In some examples, displaying the transcription is performed based on determining that the second natural language voice input indicates a voice recognition error. Thus, in some examples, if the subsequent voice input indicates that the DA incorrectly recognized the previous voice input, the device 800 displays a transcription of the previous voice input. For example, Figure 8CGDA user interface 803 is shown displayed in response to speech input "set a timer for 15 minutes". The DA incorrectly recognizes "15 minutes" as "50 minutes". DA user interface 803 therefore includes a response affordance 893 indicating that the timer is set to 50 minutes. Because the DA incorrectly recognizes the speech input, the user provides a second speech input indicating a speech recognition error (e.g., "that's not what I said", "you heard me wrong", "that's incorrect", etc.). For example, Figure 8CH The device 800 is shown receiving a second voice input "that's not what Isaid." The DA determines that the second voice input indicates a voice recognition error. Figure 8CI It is shown that based on such a determination, device 800 displays conversation affordance 894 including transcription 895. Transcription 895 reveals that the DA incorrectly identified "15 minutes" as "50 minutes."

[0344] In some examples, device 800 receives user input corresponding to a selection of the displayed transcript. In response to receiving the user input, device 800 simultaneously displays a keyboard and an editable text field including the transcript, e.g., displaying the keyboard and the editable text field on top of a user interface on which DA user interface 803 is displayed. In some examples, device 800 also visually obscures 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). Figure 8CI For example, Figure 8CJ Device 800 is shown receiving user input 896 (eg, a tap gesture) selecting transcription 895 . Figure 8CK In response to receiving user input 896 , device 800 is shown displaying a keyboard 897 and an editable text field 898 including the transcription 895 . Figure 8CK Device 800 is also shown visually obscuring a portion of user interface 802 .

[0345] Figure 8CL Device 800 is shown to have received one or more keyboard inputs and to have edited transcription 895 based on the one or more keyboard inputs, e.g., editing "set a timer for 50 minutes" to "set a timer for 15 minutes." Figure 8CL The device 800 is also shown receiving user input 899 (eg, a tap gesture) corresponding to selection of the Done key 8001 of the keyboard 897 . Figure 8CMThe DA is shown to perform a task based on the current (e.g., edited) transcription 895 in response to receiving user input 899. For example, device 800 displays DA user interface 803, which includes a response enable representation 8002 indicating that the timer is set to 15 minutes. Device 800 also provides voice output "Ok, I set the timer for 15 minutes". In this way, the user can manually correct the incorrect transcription (e.g., using keyboard input) so that the correct task is performed.

[0346] In some examples, while displaying the keyboard and editable text field, the device 800 receives user input corresponding to a selection of the visually obscured user interface. In some examples, in response to receiving the user input, the device 800 stops displaying the keyboard and editable text field. In some examples, the device 800 additionally or alternatively stops displaying the DA user interface 803. For example, in Figure 8CK to Figure 8CL , a user input (e.g., a tap gesture) selecting the visually obscured user interface 802 may cause the device 800 to return to Figure 8CI or causing the device 800 to stop displaying the DA user interface 803 and fully display the user interface 802, such as Fig. 8A shown.

[0347] In some examples, the device 800 presents a digital assistant result (e.g., a response indication and / or an audio output) at a first time. In some examples, based on determining that the digital assistant result corresponds to a digital assistant result of a predetermined type, the device 800 automatically stops displaying the DA user interface 803 for a predetermined duration after the first time. Thus, in some examples, the device 800 may quickly (e.g., within 5 seconds) eliminate the DA user interface 803 after providing a result of a predetermined type. Exemplary predetermined types of results correspond to completed tasks that do not require further user input (or do not require further user interaction). For example, such results include results confirming that a timer has been set, a message has been sent, and a household appliance (e.g., a light) has changed state. Examples of results that do not correspond to a predetermined type include results in which the DA requires further user input, and results in which the DA provides information (e.g., news, Wikipedia articles, locations) in response to a user's request for information.

[0348] For example, Figure 8CM The device 800 is shown to present the result at the first time, for example, to complete the provision of the speech output "Ok, I set the timer for 15 minutes". Because the result corresponds to a predetermined type, Figure 8CNDevice 800 is shown automatically eliminating the DA within a predetermined duration (eg, 5 seconds) after the first time (eg, without further user input).

[0349] Figure 8CO to Figure 8CT An example of a DA user interface 803 and an exemplary user interface is shown when the device 800 is a tablet device. It should be understood that any techniques discussed herein with respect to the device 800 being a tablet device also apply when the device 800 is another type of device (and vice versa).

[0350] Figure 8CO Device 800 is shown displaying user interface 8003. User interface 8003 includes taskbar area 8004. Figure 8CO , device 800 displays DA user interface 803 over user interface 8003. DA user interface 803 includes indicator 804 displayed at a first portion of display 801 and response affordance 8005 displayed at a second portion of display 801. As shown, a portion of user interface 8003 remains visible (e.g., not visually obscured) at a third portion of display 801. In some examples, the third portion is located between the first portion of display 801 and the second portion of display 801. In some examples, as Figure 8CO As shown, the display of the DA user interface 803 will not visually obscure the taskbar area 8004 , for example, no portion of the DA user interface 803 will be displayed above the taskbar area 8004 .

[0351] Figure 8CP Device 800 is shown displaying DA user interface 803 including conversation affordance 8006. As shown, conversation affordance 8006 is displayed at a portion of display 801 between a first portion of display 801 (displaying indicator 804) and a second portion of the display (displaying response affordance 8005). Displaying conversation affordance 8006 also enables response affordance 8005 (from Figure 8CO ) is shifted toward the top portion of the display 801.

[0352] Figure 8CQ A device 800 is shown displaying a user interface 8003 including a media panel 8007 indicating that media is currently playing. Figure 8CRDevice 800 is shown displaying DA user interface 803 over user interface 8003. DA user interface 803 includes response affordances 8008 and indicators 804. As shown, display of DA user interface 803 does not visually obscure media panel 8007. For example, as shown, display elements of DA user interface 803 (e.g., indicators 804, response affordances 8008, conversation affordances) cause media panel 8007 to shift toward the top portion of display 801.

[0353] Figure 8CS A device 800 is shown displaying a user interface 8009 including a keyboard 8010. Figure 8CT DA user interface 803 is shown displayed on top of user interface 8009. Figure 8CT As shown, in some examples, displaying the DA user interface 803 over a user interface 8009 that includes a keyboard 8010 causes the device 800 to visually mask the keys of the keyboard 8010 (e.g., graying out the keys).

[0354] 9A to 9C Multiple devices for determining which device should respond to voice input according to various examples are shown. Specifically, Fig. 9A Devices 900, 902, and 904 are shown. 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 DA system 700 at least in part.

[0355] exist Fig. 9A In some examples, when the user provides a voice input including a trigger phrase (e.g., “Hey, Siri”) for initiating a DA, such as “Hey, Siri, what’s the weather like?”, the corresponding displays of devices 900, 902, and 904 are not displayed. In some examples, when the user provides the voice input, the corresponding display of at least one of devices 900, 902, and 904 displays a user interface (e.g., a home screen user interface, an application-specific user interface). Fig. 9B Devices 900, 902, and 904 are shown to each display an indicator 804 in response to receiving a voice input including a trigger phrase. In some examples, each indicator 804 is displayed in a listening state, for example, indicating that the corresponding device is sampling audio input.

[0356] exist Fig. 9B, devices 900, 902, and 904 coordinate with each other (or via a fourth device) to determine which device should respond to a 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 ARBITRATION AND CONTROL,” dated October 2, 2018, and U.S. Patent Application No. 63 / 022,942, entitled “DIGITAL ASSISTANT HARDWARE ABSTRACTION,” filed on May 11, 2020, the contents of which are hereby incorporated by reference in their entirety. Fig. 9B As shown, when each device determines whether to respond to the user request, each device only displays the indicator 804. For example, the corresponding parts of the displays of devices 900, 902, and 904 that do not display the indicator 804 are not displayed. In some examples, when at least one of devices 900, 902, and 904 displays a user interface (previous user interface) when the user provides voice input, when the at least one device determines whether to respond to the user request, the at least one device only displays the indicator 804 additionally on top of the previous user interface.

[0357] Fig. 9C Device 902 is shown to be the device that is determined to be responsive to the user request. As shown, in response to determining that another device (e.g., device 902) should respond to the user request, the displays of devices 900 and 904 stop displaying (or stop 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 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 interference is minimized when determining which of multiple devices should respond to voice input. For example, in Fig. 9B 8. In the example of FIG. 8, the display of a device determined not to be responsive to the user request displays only the indicator 804, eg, as opposed to displaying the user interface with the entire display.

[0358] Determining which of the multiple devices should respond to the voice input in the manner shown and described above provides the user with feedback that the voice input has been received and is being processed. In addition, providing feedback in such a manner can advantageously reduce unnecessary visual or auditory interference when responding to the voice input. For example, there is no need for the user to manually stop the display and / or stop the audible output of the unselected device, and minimize visual interference with the user interface of the unselected device (for example, if the user was previously interacting with the user interface of the unselected device). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (for example, by reducing the amount of user input required to expect to perform the 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.

[0359] Figure 10A to Figure 10V User interfaces and digital assistant user interfaces according to various examples are shown. Figure 10A to Figure 10V To illustrate the process described below, which includes FIG. 18A to FIG. 18B process.

[0360] Fig. 10A Device 800 is shown. Device 800 displays a DA user interface 803 on top of the user interface on display 801. 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.

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

[0362] In some examples, while the DA user interface 803 is displayed over the user interface, the device 800 receives a user input corresponding to a selection of the third portion of the display 801. 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.

[0363] In some examples, based on determining that the user input corresponds to a first type of input, the device 800 stops displaying the DA user interface 803. Stopping displaying the DA user interface 803 includes stopping displaying any portion of the DA user interface 803, for example, the indicator 804, the response affordance, and the dialog affordance (if included). In some examples, stopping displaying the DA user interface 803 includes replacing display of elements of the DA user interface 803 at their corresponding portions of the display 801 with display of the user interface at the corresponding portions. For example, the device 800 replaces display of the indicator 804 at a first portion of the display 801 with display of a first portion of the user interface, and replaces display of the response affordance at a second portion of the display 801 with display of a second portion of the user interface.

[0364] For example, Fig. 10B Device 800 is shown receiving user input 1003 (eg, a tap gesture) corresponding to a selection of a third portion of display 801. Device 800 determines that user input 1003 corresponds to an input of the first type. Fig. 10C It is shown that based on such a determination, the device 800 stops displaying the DA user interface 803 and displays the user interface 1001 in its entirety.

[0365] Thus, the user may eliminate 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 the above Figures 8S to 8X , a tap gesture that selects a portion of display 801 showing the home screen user interface 802 that is visually obscured causes device 800 to return to Fig. 8A display.

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

[0367] In some examples, the user interface is home screen user interface 1001, the selectable element is an application affordance of home screen user interface 1001, and the user interface corresponding to the selectable element is a user interface corresponding to the application affordance. Fig. 10D DA user interface 803 is shown displayed over home screen user interface 1001. Display 801 displays indicator 804 at a first portion, displays response affordance 1004 at a second portion, and displays a portion of user interface 1001 at a third portion. Fig. 10E Device 800 is shown receiving user input 1005 (e.g., a tap gesture) selecting health application enable representation 1006 displayed in the third portion. Fig.10F It is shown that based on device 800 determining that user input 1005 corresponds to a first type of input, device 800 ceases to display indicator 804, response affordance 1004, and that portion of user interface 1001. Device 800 also displays user interface 1007 corresponding to a health application.

[0368] 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. Figure 10G DA user interface 803 is shown displayed over web browsing application user interface 1008. Display 801 displays indicator 804 at a first portion, response affordance 1009 at a second portion, and a portion of user interface 1008 at a third portion. Figure 10G Also shown is device 800 receiving user input 1010 (eg, a tap gesture) selecting a link 1011 (eg, a web page link) displayed in the third portion. Fig. 10H It is shown that based on device 800 determining that user input 1010 corresponds to a first type of input, device 800 ceases to display indicator 804, response affordance 1009, and the portion of user interface 1008. Device 800 also displays user interface 1012 corresponding to web page link 1011.

[0369] Thus, 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 (eg, updating the display 801) based on what the user selected.

[0370] In some examples, based on determining that the user input corresponds to a second type of input (e.g., a drag or swipe gesture), the device 800 updates the display of the user interface at the third portion of the display 801 based on the user input. In some examples, when the device 800 updates the display of the user interface at the third portion of the display 801, the device 800 continues to display at least some elements of the DA user interface at corresponding display portions of the elements of the DA user interface 803. For example, the device 800 displays (e.g., continues to display) a response enable representation at the second portion of the display 801. In some examples, the device 800 also displays (e.g., continues to display) the indicator 804 at the first portion of the display 801. In some examples, updating the display of the user interface at the third portion includes scrolling the content of the user interface.

[0371] For example, Fig.10I DA user interface 803 is shown displayed over a 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 shown is device 800 receiving user input 1015 (eg, a drag gesture) selecting the third portion. Fig.10J It is shown that based on the device 800 determining that the user input 1015 corresponds to the second type of input, the device 800 updates (eg, scrolls through) the content of the user interface 1013 based on the user input 1015, such as scrolling through the content of the web page. FIG. 10I to FIG. 10J It is shown that while the user interface 1013 is updated (at the third portion of the display 801 ), the device 800 continues to display the indicator 804 at the first portion of the display 801 and displays the response enable indication 1014 at the second portion of the display 801 .

[0372] Another example: Figure 10K DA user interface 803 is shown displayed on home screen user interface 1001. Display 801 displays indicator 804 at a first portion, displays response affordance 1016 at a second portion, and displays a portion of user interface 1001 at a third portion. Figure 10K Also shown is device 800 receiving user input 1017 (eg, a swipe gesture) selecting the third portion. Fig.10LIt is shown that according to device 800 determining that user input 1017 corresponds to the second type of input, device 800 updates the content of user interface 1001 according to user input 1017. For example, as shown, device 800 updates user interface 1001 to display secondary home screen user interface 1018, which includes one or more application affordances that are different from the application affordances of home screen user interface 1001. Figures 10K to 10L It is shown 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 displays the response enable indication 1016 at the second portion of the display 801 .

[0373] In this way, a user can 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 be eliminated.

[0374] In some examples, updating the display of the user interface at the third portion of the display 801 is performed based on determining 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 examples, if the DA is not in a listening state, in response to receiving a user input corresponding to the second type (and corresponding to a selection of the third portion of the display 801), the device 800 does not update the display 801 or stops displaying the DA user interface 803 in response to the user input. In some examples, when updating the display of the user interface when the DA is in a listening state, the displayed size of the indicator 804 varies based on the amplitude of the received voice input, as described above.

[0375] In some examples, device 800 receives a second user input while device 800 displays the DA user interface 803 over the user interface. In some examples, based on determining that the second user input corresponds to a third type of input, device 800 stops displaying the DA user interface 803. In some examples, the third type of input includes a swipe gesture originating from the bottom of display 801 toward the top of display 801. The third type of input is sometimes referred to as a "home swipe" because receiving such input while device 800 is displaying a user interface other than the home screen user interface (and not displaying the DA user interface 803) causes device 800 to revert to display of the home screen user interface.

[0376] Figure 10M Device 800 is shown displaying DA user interface 803 on top of home screen user interface 1001. DA user interface 803 includes response affordance 1020 and indicator 804. Figure 10MAlso shown is device 800 receiving user input 1019 , namely a swipe gesture from the bottom of display 801 toward the top of display 801 . Fig.10N It is shown that based on the device 800 determining that the user input 1019 corresponds to the third type of input, the device 800 stops displaying the response enable representation 1020 and the indicator 804.

[0377] In some examples, the user interface (on which the DA user interface 803 is displayed) is an application-specific user interface. In some examples, while the device 800 displays the DA user interface 803 on top of the application-specific user interface, the device 800 receives a second user input. In some examples, based on determining that the second user input corresponds to a third type of input, the device stops displaying the DA user interface 803 and displays the home screen user interface in addition. For example, Fig.10O Device 800 is shown displaying DA user interface 803 on top of health application user interface 1022. DA user interface 803 includes response affordance 1021 and indicator 804. Fig.10O Also shown is device 800 receiving user input 1023 , namely a swipe gesture from the bottom of display 801 toward the top of display 801 . Figure 10P It is shown that according to device 800 determining that user input 1023 corresponds to the third type of input, device 800 displays home screen user interface 1001. For example, as shown, device 800 replaces the display of indicator 804, response affordance 1021, and messaging application user interface 1022 with the display of home screen user interface 1001.

[0378] In some examples, when device 800 displays DA user interface 803 on top of the user interface, device 800 receives a third user input corresponding to a selection of a response affordance. In response to receiving the third user input, device 800 stops displaying DA user interface 803. For example, Figure 10Q DA user interface 803 is shown displayed on top of home screen user interface 1001. DA user interface 803 includes response affordance 1024, dialog affordance 1025, and indicator 804. Figure 10Q Also shown is device 800 receiving user input 1026 (e.g., an upward swipe or drag gesture) selecting response enable representation 1024. Figure 10R It is shown that in response to receiving user input 1026, the device 800 stops displaying the DA user interface 803.

[0379] In some examples, when device 800 displays user interface 803 on top of user interface 801, device 800 receives a fourth user input corresponding to a displacement of indicator 804 from a 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 The DA user interface 803 is shown displayed on top of the home screen user interface 1001. Fig. 10S , the device 800 receives user input 1027 (eg, a drag or swipe gesture) to shift the indicator from a first portion of the display 801 to an edge of the display 801 . Figure 10S to Figure 10V The device 800 is shown ceasing to display the DA user interface 803 in response to receiving the user input 1027 (eg, in response to the indicator 804 reaching an edge of the display 801).

[0380] 5. Digital Assistant Response Mode

[0381] Fig.11 A system 1100 for selecting a DA response mode and for presenting a response according to the selected DA response mode is shown according to various examples. In some examples, the 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 functions of the system 1100 are implemented within a DA system, as described above with respect to 7A to 7C described.

[0382] The system 1100 is exemplary, and thus the system 1100 may have more or fewer components than those shown, may combine two or more components, or may have a different configuration or arrangement of components. In addition, although the discussion below describes functions performed at a single component of the system 1100, it should be understood that these functions may be performed at other components of the system 1100, and these functions may be performed at more than one component of the system 1100.

[0383] Fig.12 A device 800 is shown for presenting a response to a received natural language input according to different DA response modes according to various examples. Fig.12 , for each instantiation of device 800, device 800 has initiated DA and presented a response to the speech input "What's the weather like?" according to the silent response mode, the mixed response mode, or the voice response mode described below. Device 800 implementing system 1100 selects a DA response mode and presents a response according to the selected response mode using the techniques described below.

[0384] System 1100 includes acquisition module 1102. Acquisition module 1102 acquires a response packet in response to a natural language input. The response packet includes content (e.g., conversational text) intended as a response to the natural language input. In some examples, the response packet includes a first text (content text) associated with a digital assistant response affordance (e.g., response affordance 1202) and a second text (title text) associated with the response affordance. In some examples, the title text is not as lengthy as the content text (e.g., includes fewer words). The content text may provide a complete response to a user request, while the title text may provide a brief (e.g., incomplete) response to the request. For a complete response to a request, device 800 may simultaneously present the title text and the response affordance, for example, while the presentation of the content text may not require the presentation of the response affordance for a complete response.

[0385] For example, consider Fig.12 , the natural language input is "What's the weather like?". The content text is "The current temperature is 70 degrees, sunny, and there is zero chance of rain. Today's high will be 75 degrees and the low will be 60 degrees." The title text is simply "The weather is great today." As shown, the title text is intended to be presented together with a response affordance 1202 that visually indicates information about the content text. Therefore, presenting the content text alone can fully answer the request, while presenting both the title text and the response affordance can fully answer the request.

[0386] In some examples, the acquisition module 1102, for example, performs the following steps by the device 800: 7A to 7C In some examples, the acquisition module 1102 acquires the response packet from an external device such as the DA server 106. In such examples, the DA server 106 processes the natural language input as described above to acquire the response packet locally. 7A to 7C The natural language input is processed as described above to determine the response packet. In some examples, the acquisition module 1102 acquires a portion of the response packet locally and acquires another portion of the response packet from an external device.

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

[0388] In some examples, after the device 800 receives a natural language input, the selection module 1104 selects a DA response mode, for example, based on current context information acquired after the natural language input is received. In some examples, after the acquisition module 1102 acquires a response packet, the selection module 1104 selects a DA response mode, for example, based on current context information acquired after the response packet is acquired. 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 a response to the natural language input is presented. In some examples, the multiple DA response modes include a silent response mode, a mixed response mode, and a voice response mode, which will be discussed further below.

[0389] System 1100 includes a formatting module 1106. In response to selection module 1104 selecting a DA response mode, formatting module 1106 causes the DA to present a response packet 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 a response packet according to the silent response mode includes displaying a response affordance and displaying a title text without providing an audio output representing (e.g., speaking) the title text (and without providing content text). In some examples, the selected DA response mode is a mixed response mode. In some examples, presenting a response packet according to the mixed response mode includes displaying a response affordance and speaking the title text without displaying the title text (and without providing context text). In some examples, the selected DA response mode is a voice response mode. In some examples, presenting a response packet according to the voice response mode includes speaking the content text, for example, without presenting the title text and / or without displaying the response affordance.

[0390] For example, in Fig.12 , presenting the response packet according to the silent response mode includes displaying the response enable indication 1202, and displaying the title text "The weather is great today" in the dialogue enable indication 1204 without speaking the title text. Presenting the response packet according to the mixed response mode includes displaying the response enable indication 1202, and speaking the title text "The weather is great today" without displaying the title text. Presenting the response packet according to the voice response mode includes speaking the content text "The current temperature is 70 degrees, sunny, and the probability of rain is zero. The highest temperature today will reach 75 degrees and the lowest temperature will reach 60 degrees." Although Fig.12 Device 800 is shown displaying response affordance 1202 when presenting a response packet in accordance with a voice response mode, but in other examples, a response affordance is not displayed when presenting a response packet in accordance with a voice response mode.

[0391] In some examples, when the DA presents a response according to the silent response mode, the device 800 displays a response affordance without displaying a dialog affordance (e.g., including text). In some examples, the device 800 abandons providing text based on determining that the response affordance includes a direct answer to a natural language request. For example, the device 800 determines that the title text and the response affordance each include corresponding matching texts that answer the user's request (thus rendering the title text redundant). For example, for the natural language request "What is the temperature?", if the response affordance includes the current temperature, then in silent mode, the device 800 does not display any title text, because the title text including the current temperature is redundant for the response affordance. In contrast, consider the exemplary natural language request "Is it cold?" The response affordance for the request may include the current temperature and weather conditions, but may not include a direct (e.g., explicit) answer to the request, such as "yes" or "no". Therefore, for such natural language input, in silent mode, the device 800 displays both the response affordance and the title text including a direct answer to the request, such as "No, it's not cold."

[0392] Fig.12 It is shown that in some examples, selecting the DA response mode includes determining whether to (1) display the title text without speaking the title text or (2) speak the title text without displaying the title text. In some examples, selecting the response mode includes determining whether to speak the content text.

[0393] Generally speaking, when the user desires to view the display and does not desire audio output, the silent response mode may be appropriate. When the user desires to view the display and desires audio output, the mixed response mode may be appropriate. When the user does not desire (or cannot) view the display, the voice response mode may be appropriate. Various techniques and context information selection module 1104 for selecting a DA response mode are now discussed.

[0394] Fig.13 An exemplary process 1300 implemented by the selection module 1104 to select a DA response mode is shown according to various examples. In some examples, the selection module 1104 implements the process 1300 as computer-executable instructions, such as those stored in a memory of the device 800.

[0395] At block 1302, the selection module 1104 obtains (e.g., determines) current context information. At block 1304, the module 1104 determines whether to select a voice mode based on the current context information. If the module 1104 determines to select the voice mode, then at block 1306, the module 1104 selects the voice mode. If the module 1104 determines not to select the voice mode, the process 1300 proceeds to block 1308. At block 1308, the module 1104 selects between a silent mode and a mixed mode. If the module 1104 determines to select the silent mode, then at block 1310, the module 1104 selects the silent mode. If the module 1104 determines to select the mixed mode, then at block 1312, the module 1104 selects the mixed mode.

[0396] 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 specific condition for selecting a voice mode. If the specific condition is satisfied, module 1104 selects the voice mode. If the specific condition is not satisfied (meaning that the current context information satisfies the condition for selecting a mixed 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 specific condition for selecting a silent mode or a mixed mode, and selects the silent mode or the mixed mode accordingly.

[0397] 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 the probability of selecting a speech mode and the probability of not selecting a speech mode (e.g., the probability of selecting a silent mode or a mixed mode) based on current context information, and selects the branch with the highest probability. At block 1308, module 1104 determines the probability of selecting a mixed mode and the 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 speech mode, mixed mode, and silent mode probabilities is 1.

[0398] Various types of current context information used to determine blocks 1304 and / or 1308 are now discussed.

[0399] In some examples, the contextual information includes whether the device 800 has a display. In a rule-based system, determining that the device 800 does not have a display satisfies a condition for selecting a voice mode. In a probabilistic system, determining that the device 800 does not have a display increases the probability of a voice mode and / or decreases the probability of a mixed mode and decreases the probability of a silent mode.

[0400] In some examples, the context information includes whether the device 800 detects a voice input that initiates a DA (e.g., "Hey, Siri"). In a rule-based system, detection of a voice input that initiates a DA satisfies a condition for selecting a voice mode. In a rule-based system, failure to detect a voice input that initiates a DA does not satisfy a condition for selecting a voice mode (and therefore satisfies a condition for selecting a mixed mode or a silent mode). In a probabilistic system, in some examples, detection of 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, failure to detect a voice input that initiates a DA decreases the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0401] In some examples, the context information includes whether the device 800 detects physical contact with the device 800, which is used to initiate the DA. In a rule-based system, the absence of detection of physical contact satisfies the condition for selecting the voice mode. In a rule-based system, the detection of physical contact does not satisfy the condition for selecting the voice mode. In a probabilistic system, in some examples, the absence of detection of physical contact increases the probability of the voice mode and / or decreases the probability of the mixed mode and decreases the probability of the silent mode. In a probabilistic system, in some examples, the detection of physical contact decreases the probability of the voice mode and / or increases the probability of the mixed mode and increases the probability of the silent mode.

[0402] In some examples, the context information includes whether the device 800 is in a locked state. In a rule-based system, determining that the device 800 is in a locked state satisfies the condition 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 condition for selecting a voice mode. In a probabilistic system, in some examples, determining that the device 800 is in a locked state increases the probability of a voice mode and / or reduces the probability of a mixed mode and reduces the probability of a silent mode. In a probabilistic system, in some examples, 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.

[0403] In some examples, the contextual information includes whether the display of the device 800 is displaying before the DA is initiated. In a rule-based system, determining that the display is not displaying before the DA is initiated satisfies the conditions for selecting the voice mode. In a rule-based system, determining that the display is displaying before the DA is initiated does not satisfy the conditions for selecting the voice mode. In a probabilistic system, in some examples, determining that the display is not displaying before the DA is initiated increases the probability of the voice mode and / or decreases the probability of the mixed mode and decreases the probability of the silent mode. In a probabilistic system, in some examples, determining that the display is displaying before the DA is initiated decreases the probability of the voice mode and / or increases the probability of the mixed mode and increases the probability of the silent mode.

[0404] In some examples, the contextual information includes the display orientation of the device 800. In a rule-based system, determining that the display is facing down satisfies the condition for selecting a voice mode. In a rule-based system, determining that the display is facing up does not satisfy the condition for selecting a voice mode. In a probabilistic system, in some examples, determining that the display is facing down 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, determining that the display is facing up decreases the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0405] In some examples, the context information includes whether the display of the device 800 is blocked. For example, the device 800 uses one or more sensors (e.g., light sensors, microphones, proximity sensors) to determine whether 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, determining that the display is blocked satisfies the conditions for selecting a voice mode. In a rule-based system, determining that the display is not blocked does not satisfy the conditions for selecting a voice mode. In a probabilistic system, in some examples, determining that the display is blocked increases the probability of a voice mode and / or reduces the probability of a mixed mode and reduces the probability of a silent mode. In a probabilistic system, in some examples, determining that the display is not blocked reduces the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0406] In some examples, the context information includes whether the device 800 is coupled to an external audio output device (e.g., headphones, Bluetooth devices, speakers). In a rule-based system, determining that the device 800 is coupled to an external device satisfies the condition for selecting a voice mode. In a rule-based system, determining that the device 800 is not coupled to an external device does not satisfy the condition for selecting a voice mode. In a probabilistic system, in some examples, determining that the device 800 is coupled to an external device increases the probability of a voice mode and / or reduces the probability of a mixed mode and reduces the probability of a silent mode. In a probabilistic system, in some examples, determining that the device 800 is not coupled to an external device reduces the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0407] In some examples, the context information includes whether the direction of the user's gaze is pointing to the device 800. In a rule-based system, determining that the direction of the user's gaze is not pointing to the device 800 satisfies the condition for selecting a voice mode. In a rule-based system, determining that the direction of the user's gaze is pointing to the device 800 does not satisfy the condition for selecting a voice mode. In a probabilistic system, in some examples, determining that the direction of the user's gaze is not pointing to the device 800 increases the probability of a voice mode and / or reduces the probability of a mixed mode and reduces the probability of a silent mode. In a probabilistic system, in some examples, determining that the direction of the user's gaze is pointing to the device 800 reduces the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0408] In some examples, the context information includes whether a gesture of a predetermined type of the device 800 is detected within a predetermined duration before selecting the response mode. The predetermined type of gesture includes, for example, a lift and / or rotation gesture that causes the device 800 to turn on the display. In a rule-based system, the condition for selecting the voice mode is not satisfied if a gesture of a predetermined type is not detected within a predetermined duration. In a rule-based system, the condition for selecting the voice mode is not satisfied if a gesture of a predetermined type is detected within a predetermined duration. In a probabilistic system, in some examples, the probability of the voice mode is increased and / or the probability of the mixed mode is reduced and the probability of the silent mode is reduced if a gesture of a predetermined type is not detected within a predetermined duration. In a probabilistic system, in some examples, the probability of the voice mode is reduced and / or the probability of the mixed mode is increased and the probability of the silent mode is increased if a gesture of a predetermined type is detected within a predetermined duration.

[0409] In some examples, the context information includes the 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 the condition for selecting a voice mode. In a rule-based system, determining that the direction of the natural language input is not oriented toward the device 800 does not satisfy the condition 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 voice mode and / or reduces the probability of a mixed mode and reduces 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 the device 800 reduces the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0410] In some examples, the contextual information includes whether the device 800 detects a touch performed on the device 800 (e.g., a user input that selects a response affordance) within a predetermined duration before selecting a response mode. In a rule-based system, failure to detect a touch within a predetermined duration satisfies a condition for selecting a voice mode. In a rule-based system, detection of a touch within a predetermined duration does not satisfy a condition for selecting a voice mode. In a probabilistic system, in some examples, failure to detect a touch within 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, detection of a touch within a predetermined duration decreases the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0411] In some examples, the contextual information includes whether the natural language input is a typed input, for example, as opposed to a spoken input. In a rule-based system, determining that the natural language input is not a typed input satisfies a condition for selecting a voice mode. In a rule-based system, determining that the natural language input is a typed input does not satisfy a condition for selecting a voice mode. In a probabilistic system, in some examples, determining that the natural language input is not a typed input 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, determining that the natural language input is a typed input decreases the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0412] 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 selecting a response mode. In a rule-based system, not receiving a notification within a predetermined duration satisfies the condition for selecting a voice mode. In a rule-based system, receiving a notification within a predetermined duration does not satisfy the condition for selecting a voice mode. In a probabilistic system, in some examples, not receiving a notification within 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, receiving a notification within a predetermined duration decreases the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0413] 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 cannot hear the audio output, for example, because the user is in a noisy environment. Therefore, detecting an ambient noise level above a threshold may recommend selecting a silent mode (because the device 800 provides audio output in both voice mode and mixed mode). Therefore, in a rule-based system, determining that the ambient noise level is below a threshold satisfies the condition for selecting a voice mode, satisfies the condition for selecting a mixed mode (at box 1308), and does not satisfy the condition for selecting a silent mode (at box 1308). In a rule-based system, determining that the ambient noise level is above a threshold does not satisfy the condition for selecting a voice mode, does not satisfy the condition for selecting a mixed mode (box 1308), and satisfies the condition for selecting a silent mode (box 1308). In a probabilistic system, in some examples, determining that the ambient noise level is below a threshold increases the probability of a voice mode, increases the probability of a mixed mode, and reduces the probability of a silent 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 silent mode.

[0414] In some examples, the context information includes whether the natural language input corresponds to a whispered input. A user's whispered natural language voice input may indicate that the user does not expect audio output, for example, because the user is in a quiet environment such as a movie theater. Therefore, determining that the natural language input corresponds to a whispered input may recommend selecting a silent mode. Therefore, in a rule-based system, determining that the natural language input does not correspond to a whispered input satisfies the conditions for selecting a voice mode, satisfies the conditions for selecting a mixed mode (at box 1308), and does not satisfy the conditions for selecting a silent mode (at box 1308). In a rule-based system, determining that the natural language input corresponds to a whispered input does not satisfy the conditions for selecting a voice mode, does not satisfy the conditions for selecting a mixed mode (box 1308), and satisfies the conditions for selecting a silent mode (box 1308). In a probabilistic system, in some examples, determining that the natural language input does not correspond to a whispered input increases the probability of a voice mode, increases the probability of a mixed mode, and reduces the probability of a silent mode. In a probabilistic system, in some examples, determining that the natural language input corresponds to a whispered input reduces the probability of a speech mode, reduces the probability of a mixed mode, and increases the probability of a silent mode.

[0415] In some examples, the contextual 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 silent mode. Therefore, in a rule-based system, determining that the schedule information indicates that the user is not busy satisfies the conditions for selecting voice mode, satisfies the conditions for selecting mixed mode (at box 1308), and does not satisfy the conditions for selecting silent mode (at box 1308). In a rule-based system, determining that the schedule information indicates that the user is busy does not satisfy the conditions for selecting voice mode, does not satisfy the conditions for selecting mixed mode (box 1308), and satisfies the conditions for selecting silent mode (box 1308). In a probabilistic system, in some examples, determining that the schedule information indicates that the user is not busy increases the probability of voice mode, increases the probability of mixed mode, and decreases the probability of silent mode. In a probabilistic system, in some examples, determining that the schedule information indicates that the user is busy reduces the probability of voice mode, reduces the probability of mixed mode, and increases the probability of silent mode.

[0416] In some examples, the contextual information includes whether the device 800 is in a vehicle. In some examples, the device 800 determines whether the device is in a vehicle by detecting pairing with a vehicle (e.g., via Bluetooth or via Apple Inc.'s CarPlay) or by determining activation of a setting indicating that the device 800 is in a vehicle (e.g., a setting for do not disturb while driving). In some examples, the device 800 uses the location and / or speed of the device 800 to determine whether it is in a vehicle. For example, data indicating that the device 800 is traveling 65 miles per hour on a highway may indicate that the device 800 is in a vehicle.

[0417] In a rule-based system, determining that the device 800 is in a vehicle satisfies the condition for selecting a voice mode. In a rule-based system, determining that the device 800 is not in a vehicle does not satisfy the condition for selecting a voice mode. In a probabilistic system, in some examples, determining that the device 800 is in a vehicle 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, determining that the device 800 is not in a vehicle decreases the probability of a voice mode and / or increases the probability of a mixed mode and increases the probability of a silent mode.

[0418] Fig.14 A device 800 is shown that presents a response according to a voice response mode when it is determined that the user is in a vehicle (e.g., driving) according to various examples. As shown, the device 800 displays a DA user interface 803 on top of the driving user interface 1400. In order to minimize visual distractions while the user is driving, the DA user interface 803 does not include a response enable representation and only includes an indicator 804. In response to the natural language input "What's the weather like?", the DA speaks the content text "The current temperature is 70 degrees, sunny, and there is zero chance of rain. The high today will be 75 degrees and the low will be 60 degrees." Therefore, the DA can respond to the user's request in a manner that reduces visual distractions while the user is driving.

[0419] In some examples, the contextual information includes whether the device 800 is executing an application of a predetermined typ...

Claims

1. A method for displaying a user interface, comprising: At electronic devices with displays and touch-sensitive surfaces: receiving user input while displaying a user interface different from the digital assistant user interface; Based on determining that the user input satisfies criteria for initiating a digital assistant: receiving natural language input; In the case of not exiting the digital assistant after receiving the natural language input, displaying the digital assistant user interface on 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 the response affordance includes a selectable element, and wherein the response affordance is displayed concurrently with the digital assistant indicator and corresponds to a response of the digital assistant to the natural language input, and wherein when the response affordance is displayed concurrently with the digital assistant indicator: when the response affordance is initially displayed, a portion of the user interface remains visible at a third portion of the display, the third portion of the display occupying a majority of the display; The third portion is located between the first portion and the second portion; and while the digital assistant user interface is displayed and while the portion of the user interface remains visible at the third portion of the display, receiving a second user input corresponding to selection of the selectable element; and In response to receiving the second user input selecting the selectable element, replacing the display of the response enable representation with the display of the enable representation corresponding to the selectable element, wherein replacing the display of the response enable representation with the display of the enable representation corresponding to the selectable element includes: blurring the user interface at the third portion of the display when the display of the enable representation corresponding to the selectable element replaces the display of the response enable representation and while the user interface remains visible at the third portion of the display.

2. The method of claim 1, wherein the response affordance is initially displayed in a first state, the method 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; as well as In response to receiving the third user input, the display of the response-indicating representation in the first state is replaced with the display of the response-indicating representation in the second state.

3. The method according to claim 2, wherein: The first state is a compact state and the second state is an expanded state.

4. The method according to claim 2, further comprising: while displaying the response affordance in the second state, receiving a fourth user input requesting display of the response affordance in the first state; as well as In response to receiving the fourth user input, the display of the response-indicating representation in the second state is replaced with the display of the response-indicating representation in the first state.

5. The method according to claim 2, further comprising: receiving a fifth user input corresponding to a selection of the response affordance while the response affordance is displayed in the second state; as well as In response to receiving the fifth user input, a user interface corresponding to the application represented by the response enable is displayed.

6. The method according to any one of claims 1 to 5, wherein: The user interface includes an input field occupying a fourth portion of the display, and the method further includes: receiving a sixth user input corresponding to the response affordance indicating a displacement from the first portion of the display to the fourth portion of the display; and In response to receiving the sixth user input, display of the response affordance at the first portion of the display is replaced with display of the response affordance in the input field.

7. The method according to any one of claims 1 to 5, wherein: The response affordance includes an editable text field including text determined from the natural language input.

8. The method according to any one of claims 1 to 5, wherein: The digital assistant user interface also includes a dialog affordance displayed at a sixth portion of the display; and The sixth portion is located between the first portion and the second portion.

9. The method according to claim 8, wherein: The dialog affordance comprises a dialog generated by the digital assistant in response to the natural language input.

10. The method according to claim 9, further comprising: A plurality of selectable disambiguation options for the natural language input is determined by the digital assistant, wherein the dialog includes the plurality of selectable disambiguation options.

11. The method according to claim 9, further comprising: determining a primary user intent based on the natural language input, wherein the response affordance corresponds to the primary user intent; and An alternative user intent is determined based on the natural language input, wherein the dialog includes selectable options corresponding to the alternative user intent.

12. The method according to claim 8, wherein: The dialog affordance is displayed in a third state, and the method further comprises: receiving a seventh user input corresponding to a selection of the conversation affordance; and In response to receiving the seventh user input, display of the conversation affordance in the third state is replaced with display of the conversation affordance in the fourth state.

13. The method according to claim 12, wherein: display of the conversation affordance in the fourth state occupies at least a portion of the first portion of the display; and Displaying the conversation enable indication in the fourth state includes displaying the conversation enable indication over at least a third portion of the response enable indication.

14. The method according to claim 13, wherein: Prior to receiving said seventh user input, said response affordance is displayed in a fifth state; and Displaying the conversation enable representation in the fourth state includes replacing the display of the response enable representation in the fifth state with the display of the response enable representation in the sixth state.

15. The method of claim 13, wherein: The fourth state corresponds to a maximum size of the conversation affordance; and When the conversation affordance is displayed in the fourth state, a fourth portion of the response affordance remains visible.

16. The method according to claim 15, further comprising: receiving an eighth user input corresponding to a selection of the fourth portion of the response affordance; as well as In response to receiving the eighth user input: replacing display of the conversation affordance in the fourth state with display of the conversation affordance in the seventh state; and The response affordance is displayed at the first portion of the display.

17. The method according to claim 12, further comprising: receiving a ninth user input corresponding to a selection of the conversation affordance while the conversation affordance is displayed in the fourth state; as well as In response to receiving the ninth user input, the display of the conversation affordance in the fourth state is replaced with the display of the conversation affordance in the eighth state.

18. The method according to claim 12, further comprising: receiving a tenth user input corresponding to a selection of the response affordance while the conversation affordance is displayed in the fourth state; as well as In response to receiving the tenth user input, the display of the conversation affordance in the fourth state is replaced with the display of the conversation affordance in the ninth state.

19. The method according to claim 8, wherein the natural language input is a natural language speech input, the method further comprising: Display a transcription of the natural language speech input in the conversation affordance.

20. The method of claim 19, wherein: The natural language speech input is subsequent to a second natural language speech input received before the natural language speech input; and Displaying the transcription is performed based on determining that the digital assistant cannot determine user intent for the natural language voice input and cannot determine a second user intent for the second natural language voice input.

21. The method according to claim 19, wherein: Displaying the transcription is performed based on determining that the natural language speech input repeats a previous natural language speech input.

22. The method according to claim 19, wherein: The natural language input is a natural language speech input, and the method further comprises: After receiving the natural language voice input, receiving a second natural language voice input subsequent to the natural language voice input, wherein displaying the transcription is performed based on determining that the second natural language voice input indicates a voice recognition error, and wherein, before determining that the second natural language voice input indicates the voice recognition error, the display does not display any transcription of the natural language voice input.

23. The method according to any one of claims 1 to 5, wherein: Presenting the digital assistant results at the first opportunity, and the method further comprises: Based on determining that the digital assistant result corresponds to a digital assistant result of a predetermined type, the digital assistant user interface is automatically stopped from being displayed for a predetermined duration after the first time.

24. The method according to any one of claims 1 to 5, wherein: The user interface is a home screen user interface or an application-specific user interface.

25. The method according to any one of claims 1 to 5, wherein: Prior to receiving the user input, the portion of the user interface is displayed at the third portion of the display.

26. An electronic device comprising: monitor; Touch-sensitive surfaces; one or more processors; 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 following operations: receiving user input while displaying a user interface different from the digital assistant user interface; Based on determining that the user input satisfies criteria for initiating a digital assistant: receiving natural language input; In the case of not exiting the digital assistant after receiving the natural language input, displaying the digital assistant user interface on 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 the response affordance includes a selectable element, and wherein the response affordance is displayed concurrently with the digital assistant indicator and corresponds to a response of the digital assistant to the natural language input, and wherein when the response affordance is displayed concurrently with the digital assistant indicator: When the response affordance is initially displayed, a portion of the user interface remains visible at a third portion of the display, the third portion of the display occupying a majority of the display; and The third portion is located between the first portion and the second portion; while the digital assistant user interface is displayed and while the portion of the user interface remains visible at the third portion of the display, receiving a second user input corresponding to selection of the selectable element; and In response to receiving the second user input selecting the selectable element, replacing the display of the response enable representation with the display of the enable representation corresponding to the selectable element, wherein replacing the display of the response enable representation with the display of the enable representation corresponding to the selectable element includes: blurring the user interface at the third portion of the display when the display of the enable representation corresponding to the selectable element replaces the display of the response enable representation and while the user interface remains visible at the third portion of the display.

27. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of an electronic device having a display and a touch-sensitive surface, cause the electronic device to: receiving user input while displaying a user interface different from the digital assistant user interface; Based on determining that the user input satisfies criteria for initiating a digital assistant: receiving natural language input; In the case of not exiting the digital assistant after receiving the natural language input, displaying the digital assistant user interface on 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 the response affordance includes a selectable element, and wherein the response affordance is displayed concurrently with the digital assistant indicator and corresponds to a response of the digital assistant to the natural language input, and wherein when the response affordance is displayed concurrently with the digital assistant indicator: When the response affordance is initially displayed, a portion of the user interface remains visible at a third portion of the display, the third portion of the display occupying a majority of the display; and The third portion is located between the first portion and the second portion; while the digital assistant user interface is displayed and while the portion of the user interface remains visible at the third portion of the display, receiving a second user input corresponding to selection of the selectable element; and In response to receiving the second user input selecting the selectable element, replacing the display of the response enable representation with the display of the enable representation corresponding to the selectable element, wherein replacing the display of the response enable representation with the display of the enable representation corresponding to the selectable element includes: blurring the user interface at the third portion of the display when the display of the enable representation corresponding to the selectable element replaces the display of the response enable representation and while the user interface remains visible at the third portion of the display.

Images