Multi-modal digital assistant

Abstract

The invention relates to a multi-modal digital assistant. Systems and processes for a multi-modal digital assistant are provided. An example method includes receiving, at a computer system, a natural language speech input indicative of a task while operating in a hands-free mode of operation; in response to receiving the natural language speech input, initiating execution of the task; and providing an output corresponding to the task, where providing the output includes displaying a first user interface associated with an application, the first user interface being displayed according to the hands-free mode of operation; receiving, via one or more input devices, a touch input at a location corresponding to the first user interface while displaying the first user interface; and transitioning from the hands-free mode of operation to a manual mode of operation different from the hands-free mode of operation in response to the touch input; and launching the application, wherein launching the application includes displaying a second user interface according to the manual operation mode.

Description

[0001] This application is a divisional application of invention patent application 202480030971.2 entitled "Multimodal Digital Assistant", filed on April 26, 2024. Technical Field

[0002] This invention relates generally to intelligent automation assistants, and more specifically, to operating intelligent automation assistants in various modes. Background Technology

[0003] Intelligent automated assistants (or digital assistants) provide a beneficial interface between human users and electronic devices. Such assistants allow users to interact with devices or systems using natural language in voice and / or text. For example, a user can provide voice input containing their request to a digital assistant running on an electronic device. The digital assistant can interpret the user's intent from this voice input and act it out as a task. 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. Summary of the Invention

[0004] This document discloses an example method. One example method includes: at a computer system communicating with a display generation component and one or more input devices: displaying a user interface including a user interface object corresponding to a digital assistant of the computer system via the display generation component; detecting user input via the one or more input devices at a location corresponding to the user interface; disabling the user interface object based on determining that the user input meets a set of input criteria; modifying the visual characteristics of the user interface object; abandoning the disabling of the user interface object based on determining that the user input does not meet the set of input criteria; and maintaining the visual characteristics of the user interface object.

[0005] An example method includes, at a computer system communicating with a display generation component and one or more input devices: determining that a first set of proximity criteria has been met; in response to detecting that the first set of proximity criteria has been met, displaying a user interface via the display generation component at a first magnification level; while displaying the user interface, receiving natural language speech input instructing a task via the one or more input devices; in response to the natural language speech input, initiating execution of the task, wherein initiating execution of the task includes updating a first portion of the user interface; determining that a second set of proximity criteria different from the first set of proximity criteria has been met; and in response to detecting that the second set of proximity criteria has been met, displaying a second portion of the user interface via the display generation component at a second magnification level different from the first magnification level.

[0006] An example method includes: at a computer system communicating with a display generation component and one or more input devices: displaying a user interface including a user interface object corresponding to a digital assistant of the computer system via the display generation component; detecting user input via the one or more input devices at a location corresponding to the user interface; disabling the user interface object based on determining that the user input meets a set of input criteria; modifying the visual characteristics of the user interface object; abandoning the disabling of the user interface object based on determining that the user input does not meet the set of input criteria; and maintaining the visual characteristics of the user interface object.

[0007] An example method includes: at a computer system communicating with a display generation component and one or more input devices: displaying a user interface including a user interface object, the user interface object corresponding to a digital assistant of the computer system, via the display generation component; when the user interface is displayed, detecting input corresponding to a location of the user interface object via the one or more input devices; in response to the input corresponding to the location of the user interface object: performing a function associated with the user interface object based on determining that a set of enable criteria are met for the user interface object; and abandoning the performance of the function associated with the user interface object based on determining that a set of enable criteria are not met for the user interface object.

[0008] This document discloses an example non-transitory computer-readable medium. An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for: displaying a user interface including a user interface object corresponding to a digital assistant of the computer system via a display generation component; detecting user input at a location corresponding to the user interface via the one or more input devices; disabling the user interface object based on determining that the user input meets a set of input criteria; modifying the visual characteristics of the user interface object; abandoning the disabling of the user interface object based on determining that the user input does not meet the set of input criteria; and maintaining the visual characteristics of the user interface object.

[0009] An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for: determining that a first set of proximity criteria has been met; in response to detecting that the first set of proximity criteria has been met, displaying a user interface at a first magnification level via a display generation component; receiving natural language speech input instructing a task via the one or more input devices while displaying the user interface; in response to the natural language speech input, initiating execution of the task, wherein initiating execution of the task includes updating a first portion of the user interface; determining that a second set of proximity criteria different from the first set of proximity criteria has been met; and in response to detecting that the second set of proximity criteria has been met, displaying a second portion of the user interface at a second magnification level different from the first magnification level via the display generation component.

[0010] An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for: displaying a user interface including a user interface object corresponding to a digital assistant of the computer system via a display generation component; detecting user input at a location corresponding to the user interface via the one or more input devices; disabling the user interface object based on determining that the user input meets a set of input criteria; modifying the visual characteristics of the user interface object; abandoning the disabling of the user interface object based on determining that the user input does not meet the set of input criteria; and maintaining the visual characteristics of the user interface object.

[0011] An example of a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for: displaying a user interface including a user interface object, the user interface object corresponding to a digital assistant of the computer system, via a display generation component; detecting input corresponding to a location of the user interface object via the one or more input devices when the user interface is displayed; in response to the input corresponding to the location of the user interface object: performing functions associated with the user interface object based on determining that a set of enable criteria are met for the user interface object; and abandoning the execution of functions associated with the user interface object based on determining that a set of enable criteria are not met for the user interface object.

[0012] This document discloses example computer systems (e.g., devices). One example computer system includes one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a user interface including a user interface object corresponding to a digital assistant of the computer system via a display generation component; detecting user input at a location corresponding to the user interface via the one or more input devices; disabling the user interface object based on determining that the user input meets a set of input criteria; modifying the visual characteristics of the user interface object; abandoning the disabling of the user interface object based on determining that the user input does not meet the set of input criteria; and maintaining the visual characteristics of the user interface object.

[0013] An example computer system includes one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: determining that a first set of proximity criteria has been met; in response to detecting that the first set of proximity criteria has been met, displaying a user interface at a first magnification level via a display generation component; receiving natural language speech input indicating a task via the one or more input devices when the user interface is displayed; in response to the natural language speech input, initiating execution of the task, wherein initiating execution of the task includes updating a first portion of the user interface; determining that a second set of proximity criteria different from the first set of proximity criteria has been met; and in response to detecting that the second set of proximity criteria has been met, displaying a second portion of the user interface at a second magnification level different from the first magnification level via the display generation component.

[0014] An example computer system includes one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a user interface including a user interface object corresponding to a digital assistant of the computer system via a display generation component; detecting user input at a location corresponding to the user interface via the one or more input devices; disabling the user interface object based on determining that the user input meets a set of input criteria; modifying the visual characteristics of the user interface object; abandoning the disabling of the user interface object based on determining that the user input does not meet the set of input criteria; and maintaining the visual characteristics of the user interface object.

[0015] An example computer system includes one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a user interface including a user interface object via a display generation component, the user interface object corresponding to a digital assistant of the computer system; detecting input corresponding to a location of the user interface object via the one or more input devices when the user interface is displayed; in response to the input corresponding to the location of the user interface object: performing functions associated with the user interface object based on determining that a set of enable criteria are met for the user interface object; and abandoning the execution of functions associated with the user interface object based on determining that a set of enable criteria are not met for the user interface object.

[0016] An example computer system includes: components for displaying a user interface including a user interface object via the display generation component, the user interface object corresponding to a digital assistant of the computer system; components for detecting user input via the one or more input devices at a location corresponding to the user interface; components for performing the following operations based on determining that the user input meets a set of input criteria: disabling the user interface object; and modifying the visual characteristics of the user interface object; and components for performing the following operations based on determining that the user input does not meet the set of input criteria: abandoning the disabling of the user interface object; and maintaining the visual characteristics of the user interface object.

[0017] An example computer system includes: components for determining that a first set of proximity criteria has been met; components for displaying a user interface at a first magnification level via a display generation component in response to detecting that the first set of proximity criteria has been met; components for receiving natural language speech input instructing a task via the one or more input devices when the user interface is displayed; components for initiating execution of the task in response to the natural language speech input, wherein initiating execution of the task includes updating a first portion of the user interface; components for determining that a second set of proximity criteria different from the first set of proximity criteria has been met; and components for displaying a second portion of the user interface at a second magnification level different from the first magnification level via the display generation component in response to detecting that the second set of proximity criteria has been met.

[0018] An example computer system includes: components for displaying a user interface including a user interface object via the display generation component, the user interface object corresponding to a digital assistant of the computer system; components for detecting user input via the one or more input devices at a location corresponding to the user interface; components for performing the following operations based on determining that the user input meets a set of input criteria: disabling the user interface object; and modifying the visual characteristics of the user interface object; and components for performing the following operations based on determining that the user input does not meet the set of input criteria: abandoning the disabling of the user interface object; and maintaining the visual characteristics of the user interface object.

[0019] An example computer system includes: components for displaying a user interface including a user interface object via the display generation component, the user interface object corresponding to a digital assistant of the computer system; components for detecting input corresponding to a location of the user interface object via the one or more input devices when the user interface is displayed; and components for performing the following operations in response to the input corresponding to the location of the user interface object: executing a function associated with the user interface object based on determining that a set of enable criteria are met for the user interface object; and abandoning the execution of the function associated with the user interface object based on determining that a set of enable criteria are not met for the user interface object.

[0020] Operating the computer system in both hands-free and hands-free modes allows operation whether the user is near or away from the system, providing appropriate operation in various usage scenarios. This makes operating the computer system more convenient and intuitive, which in turn reduces power consumption and improves battery life by enabling the user to use the device more quickly and efficiently. Attached Figure Description

[0021] Figure 1 These are block diagrams illustrating various examples of systems and environments used to implement digital assistants.

[0022] Figure 2A This is a block diagram illustrating a portable multi-functional device that implements the client-side portion of a digital assistant according to various examples.

[0023] Figure 2B This is a block diagram illustrating exemplary components for event handling based on various examples.

[0024] Figure 3 Portable multi-functional devices that implement the client-side portion of a digital assistant according to various examples are illustrated.

[0025] Figure 4This is a block diagram of an exemplary multifunctional device with a display and a touch-sensitive surface, based on various examples.

[0026] Figure 5A Exemplary user interfaces for application menus on portable multi-functional devices, based on various examples, are shown.

[0027] Figure 5B Exemplary user interfaces of multifunctional devices having a touch-sensitive surface separate from the display are illustrated according to various examples.

[0028] Figure 6A Examples of personal electronic devices are shown, based on various examples.

[0029] Figure 6B This is a block diagram illustrating various examples of personal electronic devices.

[0030] Figure 7A It is a block diagram illustrating a digital assistant system or its server portion according to various examples.

[0031] Figure 7B Examples are shown based on various examples. Figure 7A The digital assistant functions shown.

[0032] Figure 7C Examples are provided for a portion of the knowledge ontology based on various examples.

[0033] Figures 8A to 8J Exemplary user interfaces for performing tasks are illustrated according to various examples.

[0034] Figure 9 It is a flowchart of an exemplary process for performing a task, based on various examples.

[0035] Figure 10 It is a flowchart of an exemplary process for performing a task, based on various examples.

[0036] Figures 11A to 11C Exemplary techniques for performing tasks are illustrated according to various examples.

[0037] Figure 12 It is a flowchart of an exemplary process for performing a task, based on various examples.

[0038] Figure 13 It is a flowchart of an exemplary process for performing a task, based on various examples. Detailed Implementation

[0039] The accompanying drawings will be referenced in the following description of the examples, which illustrate specific examples that can be implemented by way of example. It should be understood that other examples may be used and structural changes may be made without departing from the scope of the individual examples.

[0040] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, without departing from the various examples described, 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 and second inputs are inputs, and in some cases, they are independent and distinct inputs.

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

[0042] Depending on the context, the term "if" can be interpreted as meaning "when," "at," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrases "if it is determined that..." or "if [the stated condition or event] is detected" can be interpreted as meaning "when it is determined that..." or "in response to determination that..." or "when [the stated condition or event] is detected," or "in response to detection of [the stated condition or event]."

[0043] 1. System and Environment

[0044] Figure 1A block diagram of system 100 according to various examples is illustrated. In some examples, system 100 implements a digital assistant. The terms "digital assistant," "virtual assistant," "intelligent automated assistant," or "automatic digital assistant" refer to any information processing system that interprets natural language input in spoken and / or textual form to infer user intent and 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 having steps and parameters designed to achieve the inferred user intent; inputting a specific request into the task flow based on the inferred user intent; executing the task flow by invoking programs, methods, services, APIs, etc.; and generating an output response to the user in an audible (e.g., voice) and / or visual form.

[0045] Specifically, a digital assistant can accept user requests, at least in part, in the form of natural language commands, requests, statements, narration, and / or inquiries. Typically, user requests seek an informational response or task from the digital assistant. A satisfactory response to a user request includes providing the requested informational response, performing the requested task, or a combination of both. For example, a user asks a digital assistant a question such as, “Where am I now?” Based on the user’s current location, the digital assistant replies, “You are near the west entrance of Central Park.” The user also requests a task, such as, “Please invite my friends to my girlfriend’s birthday party next week.” In response, the digital assistant confirms the request by saying “Okay, coming right away,” and then sends the appropriate calendar invitations to each of the user’s friends listed in the user’s electronic address book. During the performance of the requested task, the digital assistant sometimes interacts with the user in a sustained conversation involving multiple exchanges of information over extended periods. Many other methods exist for interacting with a digital assistant to request information or perform various tasks. In addition to providing verbal responses and taking programmed actions, digital assistants also provide responses in other forms of video or audio, such as text, alerts, music, video, animation, etc.

[0046] like Figure 1 As 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") executing on user device 104 and a server-side portion 106 (hereinafter referred to as "DA server 106") executing on server system 108. DA client 102 communicates with DA server 106 via one or more networks 110. DA client 102 provides client-side functionality, such as user-oriented input and output processing, and communication with DA server 106. DA server 106 provides server-side functionality for any number of DA clients 102, each residing on a corresponding user device 104.

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

[0048] User equipment 104 can be any suitable electronic device. In some examples, user equipment 104 is a portable multi-functional device (e.g., see reference below). Figure 2A The described device 200), multi-functional device (e.g., see reference below) Figure 4 The described device 400) or personal electronic device (e.g., referred to below) Figures 6A to 6B The described device (600) is a portable multi-functional device, for example, a mobile phone that also includes other functions such as PDA and / or music player functionality. Specific examples of portable multi-functional devices include the Apple Watch from Apple Inc. (Cupertino, California). ® iPhone ® iPod Touch ® and iPad ® Devices. Other examples of portable multifunction devices include, but are not limited to, earbuds / headphones, speakers, and laptops or tablets. Additionally, in some examples, user device 104 is a non-portable multifunction device. Specifically, user device 104 is a desktop computer, game console, speaker, television, or set-top box. In some examples, user device 104 includes a touch-sensitive surface (e.g., a touchscreen display and / or touchpad). Furthermore, user device 104 optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick. Various examples of electronic devices such as multifunction devices are described in more detail below.

[0049] Examples of communication networks 110 include local area networks (LANs) and wide area networks (WANs), such as the Internet. Communication network 110 is implemented using any known network protocol, including various wired or wireless protocols such as Ethernet, Universal Serial Bus (USB), FireWire, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi, Voice over Internet Protocol (VoIP), Wi-MAX, or any other suitable communication protocol.

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

[0051] In some examples, user equipment 104 communicates with DA server 106 via a second user equipment 122. The second user equipment 122 is similar to or identical to user equipment 104. For example, the second user equipment 122 is similar to the one described below. Figure 2A , Figure 4 and Figures 6A to 6B The described devices are 200, 400, or 600. User equipment 104 is configured to be communicatively coupled to a second user equipment 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 equipment 122 is configured to act as a proxy between user equipment 104 and DA server 106. For example, a DA client 102 of user equipment 104 is configured to send information (e.g., a user request received at user equipment 104) to DA server 106 via the second user equipment 122. DA server 106 processes the information and returns relevant data (e.g., data content in response to the user request) to user equipment 104 via the second user equipment 122.

[0052] In some examples, user equipment 104 is configured to send a shortened request for data to a second user equipment 122 to reduce the amount of information sent from user equipment 104. The second user equipment 122 is configured to determine supplementary information to add to the shortened request to generate a complete request to be sent to DA server 106. This system architecture can advantageously allow user equipment 104 (e.g., a watch or similar compact electronic device) with limited communication capabilities and / or limited battery power (e.g., a second user equipment 122 with strong communication capabilities and / or battery power, such as a mobile phone, laptop computer, tablet computer, etc.) acting as a proxy to DA server 106 to access the services provided by DA server 106. Although Figure 1 Only two user devices 104 and 122 are shown in this document, but it should be understood that in some examples, system 100 may include any number and type of user devices configured in this agent configuration to communicate with DA server system 106.

[0053] Although Figure 1 The digital assistant shown includes both a client-side component (e.g., DA client 102) and a server-side component (e.g., DA server 106), but in some examples, the digital assistant's functionality is implemented as a standalone application installed on the user's device. Furthermore, the functional division between the client and server components of the digital assistant can vary in different 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 the backend server.

[0054] 2. Electronic equipment

[0055] Now let’s turn our attention to the implementation of electronic devices for the client-side portion of a digital assistant. Figure 2AThis is a block diagram illustrating a portable multi-functional device 200 with a touch-sensitive display system 212 according to some embodiments. The touch-sensitive display 212 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” 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 interface 218, RF circuitry 208, audio circuitry 210, a speaker 211, a microphone 213, an input / output (I / O) subsystem 206, other input control devices 216, and an external port 224. Device 200 optionally includes one or more optical sensors 264. Device 200 optionally includes one or more contact strength sensors 265 for detecting the intensity of contact on device 200 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 212 of device 200). Device 200 optionally includes one or more haptic output generators 267 for generating haptic outputs on device 200 (e.g., generating haptic outputs on a touch-sensitive surface such as the touch-sensitive display system 212 of device 200 or the touchpad 455 of device 400). These components optionally communicate via one or more communication buses or signal lines 203.

[0056] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of 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 tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or change of the contact area detected on the touch-sensitive surface, the capacitance and / or change of the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change of the touch-sensitive surface adjacent to the contact are optionally used as substitutes 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 an 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 an 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 user input allows users to access additional device functionality that would otherwise be inaccessible to the user on a space-constrained, scaled-down device used (e.g., on a touch-sensitive display) to display an indication and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0057] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the 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., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with the touch-sensitive surface, which has been physically pressed (e.g., displaced) by the user's movement, does not move. As another example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or perceived by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of the user (e.g., "release click", "press click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception described by a typical (or common) user.

[0058] It should be understood that device 200 is merely an example of a portable multifunctional device, and device 200 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 2A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

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

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

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

[0062] RF (Radio Frequency) circuit 208 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 208 converts electrical signals into electromagnetic signals / 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 circuitry 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, subscriber identity module (SIM) cards, memory, etc. RF circuit 208 optionally communicates wirelessly with networks (such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs))) and other devices. RF circuit 208 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via short-range communication radio components. Wireless communication may optionally employ 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, Pure Data (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), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging 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 date of this document submission.

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

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

[0065] A rapid press of the down button disengages the touchscreen 212 from its lock or initiates a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 and U.S. Patent No. 7,657,849, filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A longer press of the down button (e.g., 306) powers the device 200 on or off. The user can customize the function of one or more buttons. The touchscreen 212 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0066] The touch-sensitive display 212 provides input and output interfaces between the device and the user. The display controller 256 receives electrical signals from and / or transmits electrical signals to the touchscreen 212. The touchscreen 212 displays visual output to the user. Visual output includes graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects.

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

[0068] Touchscreen 212 uses LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies may be used in other embodiments. Touchscreen 212 and display controller 256 use any of a variety of touch sensing technologies currently known or to be developed thereafter, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 212, to detect contact and any movement or interruption thereof. These various touch sensing technologies include, but are 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 iPhone from Apple Inc. (Cupertino, California). ® and iPod Touch ® The technology used.

[0069] In some embodiments, the touchscreen 212's touch-sensitive display is similar to the multi-touch panel described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman) and / or U.S. Patent Publication 2002 / 0015024A1, all of which are incorporated herein by reference in their entirety. However, the touchscreen 212 displays visual output from the device 200, while the touch-sensitive panel does not provide visual output.

[0070] The touch-sensitive display in some embodiments of the touchscreen 212 is described in the following applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, “Gestures For Touch Sensitive Input Devices”; (5) U.S. Patent Application No. 11 / 038,590, filed January 18, 2005, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”; (6) U.S. Patent Application No. 11 / 228,758, filed September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, “Multi-Functional Hand-Held Device”. The full text of all these applications is incorporated herein by reference.

[0071] Touchscreen 212 has a video resolution of over 100 dpi, for example. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. The user interacts with touchscreen 212 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to function primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positioning or commands for performing the user-desired actions.

[0072] In some embodiments, in addition to the touchscreen, 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 touchscreen, does not display visual output. The touchpad is a touch-sensitive surface separate from the touchscreen 212, or an extension of the touch-sensitive surface formed by the touchscreen.

[0073] The device 200 also includes a power system 262 for supplying power to various components. The 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 circuitry, a power converter or inverter, a power status indicator (e.g., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0074] The device 200 also includes one or more optical sensors 264. Figure 2A An optical sensor 264 is shown coupled to an optical sensor controller 258 in the I / O subsystem 206. The optical sensor 264 includes a charge-coupled device (CCD) or 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 an imaging module 243 (also called a camera module), the optical sensor 264 captures still images or video. In some embodiments, the optical sensor is located at the rear of the device 200, opposite to the touchscreen display 212 at the front of the device, such that the touchscreen display is used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located at the front of the device, such that an image of the user is acquired for use in video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the positioning of the optical sensor 264 can be changed by the user (e.g., by rotating the lenses and sensors in the device housing), such that a single optical sensor 264 is used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0075] The device 200 may optionally also include one or more contact strength sensors 265. Figure 2A A contact strength sensor 265 is shown coupled to a strength sensor controller 259 in I / O subsystem 206. The contact strength sensor 265 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 265 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 212). In some embodiments, at least one contact strength sensor is located on the rear of device 200, opposite to a touchscreen display 212 located on the front of device 200.

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

[0077] The device 200 optionally also includes one or more tactile output generators 267. Figure 2AA haptic output generator coupled to a haptic feedback controller 261 in I / O subsystem 206 is shown. The haptic output generator 267 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 265 receives haptic feedback generation instructions from a haptic feedback module 233 and generates a haptic output on device 200 that can be felt by a user of device 200. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 212) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 200) or laterally (e.g., back and forth in the same plane as the surface of device 200). In some implementations, at least one haptic output generator sensor is located on the rear of the device 200, opposite to the touch screen display 212 located on the front of the device 200.

[0078] The device 200 also includes one or more accelerometers 268. Figure 2A An accelerometer 268 coupled to a peripheral device interface 218 is shown. Alternatively, the accelerometer 268 is coupled to an input controller 260 in an I / O subsystem 206. The accelerometer 268 performs as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices” and U.S. Patent Publication No. 20060017692, “Methods and Apparatuses for Operating a Portable Device Based OnAn Accelerometer,” the entire contents of which are incorporated herein by reference. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. The device 200 optionally includes, in addition to the accelerometer 268, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for acquiring information about the location and orientation (e.g., portrait or landscape) of the device 200.

[0079] In some embodiments, 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. Additionally, memory 202 stores data and models, such as user data and models 231. Furthermore, in some embodiments, memory 202 ( Figure 2A ) or 470 ( Figure 4 Storage device / global internal state 257, such as Figure 2A and Figure 4 As shown in the diagram. Device / global internal state 257 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touchscreen display 212; sensor state, which includes information obtained from various sensors and input control devices 216 of the device; and position information relating to the device's position and / or orientation.

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

[0081] The communication module 228 facilitates communication with other devices via one or more external ports 224 and includes various software components for processing data received by the RF circuitry 208 and / or the external ports 224. The external ports 224 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is for use with an iPod. ® (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0082] The contact / motion module 230 optionally detects contact with the touchscreen 212 (in conjunction with the display controller 256) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). The contact / motion module 230 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking 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 a contact break). 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 which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 230 and the display controller 256 detect contact on the touchpad.

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

[0084] The touch / motion module 230 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). 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-off (lift-away) event at the same (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 subsequently detecting a finger lift-off (lift-away) event.

[0085] The graphics module 232 includes various known software components for rendering and displaying graphics on the touchscreen 212 or other displays, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0086] In some implementations, the graphics module 232 stores data representing the 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 applications, etc., and also receives coordinate data and other graphic attribute data if necessary, and then generates screen image data for output to the display controller 256.

[0087] The haptic feedback module 233 includes various software components for generating instructions which are used by the haptic output generator 267 to generate haptic output at one or more locations on the device 200 in response to user interaction with the device 200.

[0088] In some examples, the text input module 234, which is a component of the graphics module 232, provides a soft keyboard for entering text in various applications, such as contacts 237, email 240, IM 241, browser 247, and any other application that requires text input.

[0089] GPS module 235 determines the location of the device and provides that information for use in various applications (e.g., to telephone 238 for use in location-based dialing; to camera 243 as image / video metadata; and to applications that provide location-based services, such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0090] The digital assistant client module 229 includes various client-side digital assistant commands to provide client-side functionality for the digital assistant. For example, the digital assistant client module 229 can accept voice input (e.g., voice 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 audio output (e.g., speech output), visual output, and / or tactile output through various output interfaces of the portable multifunction device 200 (e.g., speaker 211, touch-sensitive display system 212, one or more haptic output generators 267, etc.). For example, output can be provided as voice, sound, alarms, text messages, menus, graphics, video, animation, vibration, and / or combinations of both or more of these. During operation, the digital assistant client module 229 communicates with the DA server 106 using RF circuitry 208.

[0091] 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 lists, shopping lists, etc.) to provide client-side functionality for the digital assistant. Additionally, 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 ontology, task flow models, service models, etc.).

[0092] In some examples, the digital assistant client module 229 utilizes 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 contextual information, or a subset thereof, along with the user input to the DA server 106 to help infer the user's intent. In some examples, the digital assistant also uses the contextual information to determine how to prepare output and deliver it to the user. This contextual information is referred to as contextual data.

[0093] In some examples, the contextual information accompanying user input includes sensor information such as lighting, ambient noise, ambient temperature, and images or videos of the surrounding environment. 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 mode, and cellular signal strength. In some examples, information related to the software state of the DA server 106, such as the operation of the portable multifunction device 200, installed programs, past and current network activity, background services, error logs, and resource usage, is provided to the DA server 106 as contextual information associated with the user input.

[0094] In some examples, the digital assistant client module 229 selectively provides information (e.g., user data 231) stored on the portable multifunction device 200 in response to a request from the DA server 106. In some examples, the digital assistant client module 229 also elicits additional input from the user via natural language dialogue or other user interfaces when requested by the DA server 106. The digital assistant client module 229 transmits this additional input to the DA server 106 to assist the DA server 106 in intent inference and / or to realize the user intent expressed in the user request.

[0095] The following is for reference. Figures 7A to 7C A more detailed description of the digital assistant follows. It should be understood that the digital assistant client module 229 may include any number of sub-modules of the digital assistant module 726 described below.

[0096] Application 236 includes the following modules (or instruction sets) or subsets or supersets:

[0097] • Contacts module 237 (sometimes called address book or contact list);

[0098] • Telephone module 238;

[0099] • Video conferencing module 239;

[0100] • Email client module 240;

[0101] • Instant Messaging (IM) module 241;

[0102] • Fitness support module 242;

[0103] • Camera module 243 for still images and / or video images;

[0104] • Image management module 244;

[0105] • Video player module;

[0106] • Music player module;

[0107] • Browser module 247;

[0108] • Calendar module 248;

[0109] • Widget module 249, which in some examples includes one or more of the following: weather widget 249-1, stock market widget 249-2, calculator widget 249-3, alarm clock widget 249-4, dictionary widget 249-5 and other widgets obtained by the user and widgets created by the user 249-6;

[0110] • Widget creator module 250 for creating user-created widgets 249-6;

[0111] • Search module 251;

[0112] • Video and music player module 252, which combines a video player module and a music player module;

[0113] • Memo module 253;

[0114] • Map module 254; and / or

[0115] • Online video module 255.

[0116] 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 access control, speech recognition, and speech duplication.

[0117] In conjunction with touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, contact module 237 manages an address book or contact list (e.g., stored in application internal state 292 of contact module 237 in memory 202 or memory 470), including: adding names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 238, video conferencing module 239, email 240, or IM 241; and so on.

[0118] Combining RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, touchscreen 212, display controller 256, contact / motion module 230, graphics module 232, and text input module 234, telephone module 238 is used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 237, modify already entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication uses any of a variety of communication standards, protocols, and technologies.

[0119] Combining RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, touchscreen 212, display controller 256, optical sensor 264, optical sensor controller 258, contact / motion module 230, graphics module 232, text input module 234, contact module 237, and telephone module 238, video conferencing module 239 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0120] Incorporating RF circuitry 208, touchscreen 212, display controller 256, touch / 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 commands. Combined with image management module 244, email client module 240 makes it very easy to create and send emails containing still images or video images captured by camera module 243.

[0121] In conjunction with RF circuitry 208, touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, instant messaging module 241 includes executable instructions for performing the following operations: entering a character sequence corresponding to an instant message, modifying previously entered characters, sending a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing received instant messages. In some embodiments, the sent and / or received instant messages include graphics, photographs, audio files, video files, and / or other attachments supported as in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages delivered using SMS or MMS) and internet-based messages (e.g., messages delivered using XMPP, SIMPLE, or IMPS).

[0122] Incorporating RF circuitry 208, touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234, GPS module 235, map module 254, and music player module, fitness support module 242 includes executable instructions for performing the following operations: creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (exercise equipment); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

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

[0124] In conjunction with the touchscreen 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 performing operations such as arranging, modifying (e.g., editing) or otherwise manipulating, marking, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0125] Incorporating RF circuitry 208, touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, browser module 247 includes executable instructions for performing the following operations: browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

[0126] Combining RF circuitry 208, touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234, email client module 240, and browser module 247, calendar module 248 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0127] In conjunction with RF circuitry 208, touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234, and browser module 247, widget module 249 is a micro-application that can be downloaded and used by a user (e.g., weather widget 249-1, stock market widget 249-2, calculator widget 249-3, alarm clock widget 249-4, and dictionary widget 249-5) or a user-created micro-application (e.g., user-created widget 249-6). In some embodiments, the widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! widgets).

[0128] Combining RF circuit 208, touch screen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234 and browser module 247, widget creator module 250 is used by the user to create widgets (e.g., to turn user-specified parts of a webpage into widgets).

[0129] In conjunction with the touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, the search module 251 includes executable instructions for performing the following operations: 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) according to user instructions.

[0130] Combining touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, audio circuitry 210, speaker 211, RF circuitry 208, and browser module 247, the video and music player module 252 includes executable instructions allowing users 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 touchscreen 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 (a trademark of Apple Inc.).

[0131] Combining the touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, the memo module 253 includes executable instructions for creating and managing memos, to-do items, etc., according to user instructions.

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

[0133] Incorporating touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, audio circuitry 210, speaker 211, RF circuitry 208, text input module 234, email client module 240, and browser module 247, the online video module 255 includes instructions for performing the following operations: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on a touchscreen or on an external display connected via external port 224), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 241 is used instead of the email client module 240 to send links to specific online videos. Additional descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed 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 December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0134] Each of the modules and applications described above corresponds to an executable set of instructions for performing one or more functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as standalone software programs, processes, or modules, and therefore various subsets of these modules can be combined or otherwise rearranged in various embodiments. For example, a video player module can be combined with a music player module into a single module (e.g., Figure 2A(e.g., video and music player module 252). In some embodiments, memory 202 stores a subset of the aforementioned modules and data structures. Additionally, memory 202 stores additional modules and data structures not described above.

[0135] In some implementations, device 200 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for the operation of device 200, the number of physical input control devices (such as push-buttons, dials, etc.) on device 200 is reduced.

[0136] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, is optionally included for navigation between user interfaces. In some implementations, the touchpad, when touched by a user, navigates device 200 from any user interface displayed on device 200 to the main menu, main desktop menu, or root menu. In such implementations, a "menu button" is implemented using the touchpad. In some other implementations, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

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

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

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

[0140] Event monitor 271 receives event information from peripheral device interface 218. The event information includes information about sub-events, such as a user touch on touch-sensitive display 212 as part of a multi-touch gesture. Peripheral device 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 (via audio circuitry 210). The information received by peripheral device interface 218 from I / O subsystem 206 includes information from touch-sensitive display 212 or touch-sensitive surfaces.

[0141] In some implementations, event monitor 271 sends requests to peripheral device interface 218 at predetermined intervals. In response, peripheral device interface 218 sends event information. In other implementations, peripheral device interface 218 sends event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0142] In some implementations, the event classifier 270 also includes a hit view determination module 272 and / or an activity event recognizer determination module 273.

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

[0144] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected corresponds to a procedural level within the application's procedural hierarchy or view hierarchy. For example, the lowest-level view in which a touch is detected is called the hit view, and the set of events considered as correct input is determined at least in part based on the hit view of the initial touch that initiates the touch-based gesture.

[0145] 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 hierarchical structure, the hit view determination module 272 identifies the hit view as the lowest-level view in the hierarchical structure from which 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 forming an event or potential event) occurs. Once the 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 to which it was identified as the hit view.

[0146] The activity event recognizer determination module 273 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 273 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 273 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

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

[0148] In some implementations, operating system 226 includes event classifier 270. Alternatively, application 236-1 includes event classifier 270. In yet another implementation, event classifier 270 is a separate module or part of another module (such as contact / motion module 230) stored in memory 202.

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

[0150] The corresponding event identifier 280 receives event information (e.g., event data 279) from the event classifier 270 and identifies the event based on 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 at least one subset of metadata 283 and event delivery instructions 288 (which includes sub-event delivery instructions).

[0151] Event receiver 282 receives event information from event classifier 270. The event information includes information about sub-events such as touch or touch movement. 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 touch movement, 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 (e.g., from a portrait orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device pose).

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

[0153] In some implementations, event definition 287 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 284 performs a hit test to determine which user interface object is associated with the 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 the event handler associated with the sub-event and the object that triggered the hit test.

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

[0155] When the corresponding event recognizer 280 determines that the sub-event sequence 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 based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

[0156] In some embodiments, the corresponding event recognizer 280 includes metadata 283 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 283 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 283 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0157] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 280 activates the event handler 290 associated with the event. In some implementations, the corresponding event recognizer 280 delivers event information associated with the event to the event handler 290. Activating the event handler 290 is different from delivering (and deferred delivering) the sub-events to the corresponding hit view. In some implementations, the event recognizer 280 throws a flag associated with the identified event, and the event handler 290 associated with the flag acquires the flag and performs a predefined process.

[0158] In some implementations, event delivery instruction 288 includes a sub-event delivery instruction that delivers 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 the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined process.

[0159] In some implementations, 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 implementations, 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 positioning of user interface objects. GUI updater 278 updates the GUI. For example, GUI updater 278 prepares display information and transmits that display information to graphics module 232 for display on a touch-sensitive display.

[0160] In some implementations, event handler 290 includes, or has access to, a data updater 276, an object updater 277, and a GUI updater 278. In some implementations, 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 implementations, they are included in two or more software modules.

[0161] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 200 using an input device, and not all user input is initiated on a touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0162] Figure 3A portable multifunction device 200 with a touchscreen 212 is illustrated according to some embodiments. The touchscreen 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 graphics by gesturing over the graphics, for example, 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, selection of one or more graphics occurs when the user breaks contact with one or more graphics. 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 scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 200. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0163] Device 200 also includes one or more physical buttons, such as a "home" or menu button 304. As previously described, menu button 304 is used to navigate to any application 236 of a set of applications running on device 200. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touchscreen 212.

[0164] In some embodiments, device 200 includes a touchscreen 212, a menu button 304, a push-button 306 for powering on / off and locking the device, one or more volume control buttons 308, a SIM card slot 310, a headset jack 312, and a docking / charging external port 224. The push-button 306 is optionally used to: power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or unlock the device or initiate an unlocking process. In another embodiment, device 200 also accepts voice input via microphone 213 for activating or deactivating certain functions. Device 200 also optionally includes one or more contact strength sensors 265 for detecting the intensity of contact on the touchscreen 212, and / or one or more haptic output generators 267 for generating haptic outputs for the user of device 200.

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

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

[0167] Now let’s turn our attention to implementations of user interfaces that can be implemented, for example, on a portable multi-functional device 200.

[0168] Figure 5A An exemplary user interface for an application menu on a portable multifunction device 200 according to some embodiments is illustrated. 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:

[0169] Signal strength indicator 502 for wireless communications such as cellular signals and Wi-Fi signals;

[0170] • Time 504;

[0171] • Bluetooth indicator 505;

[0172] • Battery status indicator 506;

[0173] • Tray 508 features icons for frequently used applications, such as:

[0174] The telephone module 238 has an icon 516 labeled "telephone", which optionally includes an indicator 514 indicating the number of missed calls or voicemail messages.

[0175] The email client module 240 has an icon 518 labeled "Mail", which optionally includes an indicator 510 for the number of unread emails;

[0176] The browser module 247 has an icon 520 labeled "Browser"; and

[0177] o The video and music player module 252 (also known as the iPod (Apple Inc. trademark) module 252) is marked with an icon 522 labeled "iPod"; and

[0178] • Icons of other applications, such as:

[0179] The icon 524 of oIM module 241 marked as "message";

[0180] The icon 526 labeled "Calendar" in the calendar module 248;

[0181] The image management module 244 has an icon 528 labeled "Photo";

[0182] The icon 530 of the camera module 243 is labeled "camera";

[0183] o The icon 532 of the online video module 255, which is labeled "online video";

[0184] The stock market widget 249-2 has an icon 534 labeled "Stock Market";

[0185] The icon 536 labeled "map" in the map module 254;

[0186] The weather widget 249-1 has icon 538 labeled "weather";

[0187] The alarm clock widget 249-4 has an icon 540 labeled "clock";

[0188] The icon 542 labeled "Fitness Support" in the fitness support module 242;

[0189] The icon 544 labeled "Memo" in the memo module 253; and

[0190] o A settings icon 546 labeled "Settings" is used to set up an application or module, which provides access to the settings of the device 200 and its various applications 236.

[0191] It should be pointed out that, Figure 5A The illustrated icon labels are merely exemplary. For example, the icon 522 of the video and music player module 252 may optionally be labeled "Music" or "Music Player". Other labels may optionally be used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0192] Figure 5B An example is illustrated having a touch-sensitive surface 551 (e.g., separate from the display 550 (e.g., touchscreen display 212)). Figure 4 A tablet device or touchpad 455) device (e.g., Figure 4An exemplary user interface on the device 400. The device 400 also optionally includes one or more contact intensity sensors (e.g., one or more sensors in sensor 459) for detecting the intensity of contact on the tactile surface 551 and / or one or more tactile output generators 457 for generating tactile outputs for the user of the device 400.

[0193] While some examples of input on a reference touchscreen display 212 (which combines a touch-sensitive surface and a display) are given in the following examples, in some implementations, the device detects input on a touch-sensitive surface separate from the display, such as... Figure 5B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 5B 551) has a spindle (e.g., on the display (e.g., 550) with the spindle on the display (e.g., 551). Figure 5B The main axis corresponding to 553 in the middle (e.g., Figure 5B (552 in the example). According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., in the example). Figure 5B In the middle, 560 corresponds to 568 and 562 corresponds to 570) is in contact with the touch-sensitive surface 551 (e.g., Figure 5B 560 and 562 in the example). Thus, when the touch-sensitive surface (e.g., Figure 5B 551 in the middle) and the display of a multi-functional device (e.g., Figure 5B When 550 is separated from 560, user input detected by the device on the touch-sensitive surface (e.g., contact with 560 and 562 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may be optionally used for other user interfaces described herein.

[0194] Additionally, while the examples below are given primarily with reference to finger input (e.g., finger touch, finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the touch). As another example, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0195] Figure 6AAn exemplary personal electronic device 600 is illustrated. Device 600 includes a body 602. In some embodiments, device 600 includes components relative to devices 200 and 400 (e.g., Figures 2A to 4 The device 600 may contain some or all of the features described herein. In some embodiments, the device 600 has a touch-sensitive display 604, referred to below as a touchscreen 604. Alternatively, or in addition to the touchscreen 604, the device 600 may also have a display and a touch-sensitive surface. Similar to the cases of devices 200 and 400, in some embodiments, the touchscreen 604 (or touch-sensitive surface) has one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). The one or more intensity sensors of the touchscreen 604 (or touch-sensitive surface) provide output data representing the intensity of the touch. The user interface of the device 600 responds to touches based on the touch intensity, meaning that touches of different intensities may invoke different user interface operations on the device 600.

[0196] Techniques for detecting and processing touch intensity may exist, for example, in the relevant applications: International Patent Application Serial No. PCT / US2013 / 040061, filed May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” and International Patent Application Serial No. PCT / US2013 / 069483, filed November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” each of which is incorporated herein by reference in its entirety.

[0197] In some embodiments, device 600 has one or more input mechanisms 606 and 608. Input mechanisms 606 and 608, if included, are physical in form. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 600 has one or more attachment mechanisms. Such attachment mechanisms, if included, allow device 600 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 600.

[0198] Figure 6BAn exemplary personal electronic device 600 is depicted. In some embodiments, device 600 includes... Figure 2A , Figure 2B and Figure 4 Some or all of the components described. Device 600 has a bus 612 that operatively couples I / O portion 614 to memory 618 and one or more computer processors 616. I / O portion 614 is connected to display 604, which may have touch-sensitive component 622 and optionally also has touch intensity-sensitive component 624. Furthermore, I / O portion 614 is connected to 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 pressable input device, and a rotatable input device. In some examples, input mechanism 608 is a button.

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

[0200] The memory 618 of the personal electronic device 600 is a non-transitory computer-readable storage medium for storing computer-executable instructions, which, when executed by one or more computer processors 616, cause the computer processors to perform the techniques and processes described above. The computer-executable instructions are also stored and / or transported, for example, in any non-transitory computer-readable storage medium, for use by or in conjunction with an instruction execution system, apparatus, or device, such as a computer-based system, a processor-containing system, or other system capable of retrieving and executing instructions from and from an instruction execution system, apparatus, or device. The personal electronic device 600 is not limited to... Figure 6B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0201] As used herein, the term "power indication" refers, for example, in devices 200, 400, 600, 800 and / or 1100 ( Figure 2A , Figure 4 , Figures 6A to 6B , Figures 8A to 8J , Figures 11A to 11C A graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each constitute a representation.

[0202] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other positional 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), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 4 The touchpad 455 or Figure 5B When an input (e.g., a press input) is detected on the touch-sensitive surface 551 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of direct interaction with user interface elements on a touchscreen display) that enable direct interaction with user interface elements on the touchscreen display. Figure 2A The touch-sensitive display system 212 or Figure 5A In some embodiments of the touchscreen 212, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that conveys the user's expected interaction with the user interface (e.g., by indicating to the device the elements of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0203] As used in the specification and claims, the term "characteristic strength" of a contact refers to a characteristic of the contact based on one or more strengths of the contact. In some embodiments, the characteristic strength is based on multiple strength samples. The characteristic strength is optionally based on a predefined number of strength samples or a set of strength samples collected over 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, before or after contact begins to move, before contact ends, before or after contact strength is detected to increase, and / or before or after contact strength is detected to decrease). The characteristic strength of the contact is optionally based on one or more of the following: the maximum value of the contact strength, the mean value of the contact strength, the average value of the contact strength, the value at the top 10% of the contact strength, the half maximum value of the contact strength, the 90% maximum value of the contact strength, etc. In some embodiments, the duration of the contact is used when determining the characteristic strength (e.g., when the characteristic strength is the average value of the contact strength over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether a user has performed an action. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abort performing the corresponding action), rather than to determine whether to perform the first or second action.

[0204] In some implementations, a portion of the gesture is identified for determining the characteristic intensity. For example, a touch-sensitive surface receives a series of swipes that transition from a starting position to an ending position, where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the ending position is based only on a portion of the series of swipes, rather than the entire swipe (e.g., the swipe contact is only the portion at the ending position). In some implementations, a smoothing algorithm is applied to the intensity of the swipe contact before determining its characteristic intensity. For example, the smoothing algorithm optionally includes one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

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

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

[0207] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including 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 intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

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

[0209] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength to below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength to below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0210] 3. Digital Assistant System

[0211] Figure 7A Block diagrams of digital assistant systems 700 according to various examples are illustrated. In some examples, the digital assistant system 700 is implemented on a standalone computer system. In some examples, the digital assistant system 700 is distributed across multiple computers. In some examples, some of the modules and functions of the digital assistant are divided into server and client parts, wherein the client part resides on one or more user devices (e.g., devices 104, 122, 200, 400, 600, 800, and / or 1100) and communicates with the server part (e.g., server system 108) via one or more networks, for example, as... Figure 1As shown in the image. In some examples, the digital assistant system 700 is... Figure 1 The specific implementation of server system 108 (and / or DA server 106) shown is illustrated. It should be noted that digital assistant system 700 is merely one example of a digital assistant system, and that digital assistant system 700 may have more or fewer components than shown, combine two or more components, or have different configurations or layouts of components. Figure 7A The various components shown 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.

[0212] 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.

[0213] 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).

[0214] In some examples, I / O interface 706 couples input / output devices 716 of digital assistant system 700, such as a display, keyboard, touchscreen, and microphone, to user interface module 722. I / O interface 706, together with user interface module 722, receives user input (e.g., voice input, keyboard input, touch input, etc.) and processes this input accordingly. In some examples, for instance, when the digital assistant is implemented on a standalone user device, digital assistant system 700 includes a user interface module 722. Figure 2A , Figure 4 , Figures 6A to 6B , Figures 8A to 8J and Figures 11A to 11C Any of the components and I / O communication interfaces described in devices 200, 400, 600, 800, or 1100. In some examples, digital assistant system 700 represents the server portion of a digital assistant implementation and can interact with the user through a client-side portion located on a user device (e.g., device 104, 200, 400, 600, 800, or 1100).

[0215] In some examples, the network communication interface 708 includes one or more wired communication ports 712 and / or wireless transmitting and receiving circuitry 714. The one or more wired communication ports receive and transmit communication signals via one or more wired interfaces such as Ethernet, Universal Serial Bus (USB), FireWire, etc. The wireless circuitry 714 receives RF signals and / or optical signals from the communication network and other communication devices, and transmits RF signals and / or optical signals to the 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 via networks such as the Internet, intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs).

[0216] In some examples, memory 702 or its computer-readable storage medium 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 applications 724, and digital assistant module 726. Specifically, memory 702 or its computer-readable storage medium stores instructions for performing the above-described processes. One or more processors 704 execute these programs, modules, and instructions, and read data from or write data to data structures.

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

[0218] The communication module 720 facilitates communication between the digital assistant system 700 and other devices via the network communication interface 708. For example, the communication module 720 communicates with electronic devices (such as those in…) Figure 2A , Figure 4 , Figures 6A to 6B The device 200, 400, or 600 shown communicates with the RF circuit 208. The communication module 720 also includes various components for processing data received by the wireless circuit 714 and / or the wired communication port 712.

[0219] The user interface module 722 receives commands and / or input from the user (e.g., from a keyboard, touchscreen, 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, icons, vibration, haptic 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.).

[0220] Application 724 includes programs and / or modules configured to be executed by one or more processors 704. For example, if the digital assistant system is implemented on a standalone user device, application 724 includes user applications such as games, calendar applications, navigation applications, or email applications. If the digital assistant system 700 is implemented on a server, application 724 includes, for example, resource management applications, diagnostic applications, or scheduling applications.

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

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

[0223] In some examples, such as Figure 7B As shown, the I / O processing module 728 can... Figure 7A The I / O device 716 in the middle interacts with the user or through Figure 7AThe network communication interface 708 interacts with user equipment (e.g., device 104, device 200, device 400, or device 600) to receive 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 receives contextual information associated with the user input from the user equipment along with or shortly after receiving the user input. The contextual information includes user-specific data, vocabulary, and / or preferences associated with the user input. In some examples, the contextual information also includes the software and hardware states of the user equipment at the time the user request is received, and / or information related to the user's surrounding environment at the time the user request is received. In some examples, the I / O processing module 728 also transmits follow-up questions related to the user request to the user and receives answers from the user. When a 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 a speech recognizer) for speech-to-text conversion.

[0224] STT processing module 730 includes one or more ASR systems 758. The one or more ASR systems 758 can process speech input received through I / O processing module 728 to produce recognition results. 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 a Fourier transform on the speech input to extract spectral features characterizing the speech input as a sequence of representative multidimensional vectors. Additionally, 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 grammar language models, and other statistical models. Examples of speech recognition engines include engines based on Dynamic Time Warping (VTW) 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 representative features extracted by the front-end speech preprocessor to produce intermediate recognition results (e.g., phonemes, phoneme strings, and sub-words), and finally to produce text recognition results (e.g., words, word strings, or token sequences). In some examples, the speech input is processed at least in part by a third-party service or on the user's device (e.g., device 104, device 200, device 400, or device 600) to produce the recognition results. Once the STT processing module 730 produces a recognition result containing a text string (e.g., words, or sequences of words, or token sequences), the recognition result is passed to the natural language processing module 732 for intent inference. In some examples, the STT processing module 730 produces multiple candidate text representations of the speech input. Each candidate text representation is a sequence of words or tokens corresponding to the speech input. In some examples, each candidate text representation is associated with a speech recognition confidence score. Based on the speech recognition confidence 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. In another example, the five highest-ranked (n=5) candidate text representations are passed to the natural language processing module 732 for intent inference.

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

[0226] In some examples, the STT processing module 730 includes a vocabulary of recognizable words and / or accesses that vocabulary via the speech-to-letter conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations of a word represented in the speech recognition alphabet. Specifically, the vocabulary of recognizable words includes words associated with multiple candidate pronunciations. For example, the vocabulary includes the word “tomato” associated with candidate pronunciations of / tə'meɪɾoʊ / and / tə'mɑtoʊ / . Additionally, the vocabulary words are associated with custom candidate pronunciations based on previous speech input from the user. Such custom candidate pronunciations are stored in the STT processing module 730 and associated with a specific user via a user profile on the device. In some examples, candidate pronunciations of words are determined based on the spelling of the words and one or more linguistic and / or phonetic rules. In some examples, candidate pronunciations are generated manually, for example, based on known standard pronunciations.

[0227] In some examples, candidate pronunciations are ranked based on their prevalence. For example, the candidate pronunciation / tə'meɪɾoʊ / ranks higher than / tə'mɑtoʊ / because the former is a more commonly used pronunciation (e.g., among all users, for users in a specific geographic region, or for any other suitable subset of users). In some examples, candidate pronunciations are ranked based on whether they are custom candidate pronunciations associated with a user. For example, custom candidate pronunciations rank higher than standard candidate pronunciations. This can be used to identify proper nouns with unique pronunciations that deviate from the canonical pronunciation. In some examples, candidate pronunciations are associated with one or more phonological features such as geographic origin, country, or ethnicity. For example, the candidate pronunciation / tə'meɪɾoʊ / is associated with the United States, while the candidate pronunciation / tə'mɑtoʊ / is associated with the United Kingdom. Furthermore, the ranking of candidate pronunciations is based on one or more features of a user (e.g., geographic origin, country, ethnicity, etc.) stored in a user profile on the device. For example, it can be determined from the user profile that the user is associated with the United States. Based on the user's association with the United States, the candidate pronunciation / tə'meɪɾoʊ / (associated with the United States) may rank higher than the candidate pronunciation / tə'mɑtoʊ / (associated with the United Kingdom). In some examples, one of the ranked candidate pronunciations may be selected as the predicted pronunciation (e.g., the most likely pronunciation).

[0228] Upon receiving voice input, the STT processing module 730 is used (e.g., using an acoustic model) to determine the phonemes corresponding to the voice input, and then attempts (e.g., using a language model) to determine the word that matches the phonemes. For example, if the STT processing module 730 first identifies the phoneme sequence / tə'meɪɾoʊ / corresponding to a portion of the voice input, then it can subsequently determine, based on the vocabulary index 744, that the sequence corresponds to the word "tomato".

[0229] In some examples, the STT processing module 730 uses fuzzy matching techniques to determine words in a utterance. Thus, for example, the STT processing module 730 determines that the phoneme sequence / tə'meɪɾoʊ / corresponds to the word "tomato," even if that particular phoneme sequence is not a candidate phoneme sequence for that word.

[0230] The digital assistant's natural language processing module 732 ("natural language processor") acquires 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 intentions" recognized by the digital assistant. An "executable intention" (or "user intention") represents a task that can be performed by the digital assistant and may have an associated task flow implemented in the task flow model 754. An associated task flow is a series of programmed actions and steps taken by the digital assistant to perform the task. The capabilities of the digital assistant depend on the number and type of task flows implemented and stored in the task flow model 754, or in other words, on the number and type of "executable intentions" recognized by the digital assistant. However, the effectiveness of the digital assistant also depends on its ability to infer the correct "one or more executable intentions" from user requests expressed in natural language.

[0231] 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, for example, contextual information associated with the user request from the I / O processing module 728. The natural language processing module 732 optionally uses the contextual information to clarify, supplement, and / or further define the information contained in the candidate text representation received from the STT processing module 730. Contextual information includes, for example, user preferences, the hardware and / or software state of the user's device, sensor information collected before, during, or shortly after the user request, previous interactions (e.g., conversations) between the digital assistant and the user, and so on. As described herein, in some examples, the contextual information is dynamic and varies with the time, location, content, and other factors of the conversation.

[0232] In some examples, natural language processing is based on, for example, a knowledge ontology 760. Knowledge ontology 760 is a hierarchical structure containing many nodes, each node representing an "executable intent" or an "attribute" associated with one or more of the "executable intent" or other "attributes." As mentioned above, an "executable intent" represents a task that a digital assistant can perform; that is, the task is "executable" or can be done. An "attribute" represents a parameter associated with a sub-aspect of an executable intent or another attribute. The connections between executable intent nodes and attribute nodes in knowledge ontology 760 define how the parameters represented by the attribute nodes are subordinate to the task represented by the executable intent nodes.

[0233] In some examples, the knowledge ontology 760 consists of executable intent nodes and attribute nodes. Within the knowledge ontology 760, each executable intent node is directly connected to or connected to one or more attribute nodes via one or more intermediate attribute nodes. Similarly, each attribute node is directly connected to or connected to one or more executable intent nodes via one or more intermediate attribute nodes. For example, as... Figure 7C As shown, knowledge ontology 760 includes a "Restaurant Reservation" node (i.e., an executable intent node). The attribute nodes "Restaurant", "Date / Time" (for reservations) and "Party Attendees" are all directly connected to the executable intent node (i.e., the "Restaurant Reservation" node).

[0234] Furthermore, the attribute nodes "Cuisine," "Price Range," "Phone Number," and "Location" are child nodes of the attribute node "Restaurant," and all are linked to the "Restaurant Reservation" node (i.e., the executable intent node) through the intermediate attribute node "Restaurant." For example, ... Figure 7C As shown, knowledge ontology 760 also includes a "Set Reminder" node (i.e., another executable intent node). The attribute nodes "Date / Time" (for setting reminders) and "Topic" (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 knowledge ontology 760.

[0235] An executable intent node, along with its linked attribute nodes, is described as a "domain." 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 knowledge ontology 760 shown includes examples of a restaurant reservation domain 762 and a reminder domain 764 within the knowledge ontology 760. The restaurant reservation domain includes an actionable intent node “Restaurant Reservation”, attribute nodes “Restaurant”, “Date / Time”, and “Participant Size”, and sub-attribute nodes “Cuisine”, “Price Range”, “Phone Number”, and “Location”. The reminder domain 764 includes an actionable intent node “Set Reminder” and attribute nodes “Topic” and “Date / Time”. In some examples, the knowledge 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 associated with many different domains (e.g., itinerary domain, travel booking domain, movie ticket domain, etc.).

[0236] although Figure 7C Two example fields within knowledge ontology 760 are illustrated, but other fields include, for example, "Find a movie," "Initiate a phone call," "Find directions," "Schedule a meeting," "Send a message," and "Provide answers to questions," "Reading lists," "Provide navigation instructions," and "Provide instructions for a task," etc. The "Send a message" field is associated with the "Send a message" executable intent node and further includes attribute nodes such as "One or more recipients," "Message type," and "Message body." The attribute node "Recipient" is further defined, for example, by sub-attribute nodes such as "Recipient name" and "Message address."

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

[0238] In some examples, nodes associated with multiple related executable intents are clustered under a “superdomain” in Knowledge Ontology 760. For example, the “Travel” superdomain includes clusters of travel-related attribute nodes and executable intent nodes. Travel-related executable intent nodes include “Flight Booking,” “Hotel Booking,” “Car Rental,” “Route Planning,” “Find Points of Interest,” and so on. Executable intent nodes under the same superdomain (e.g., the “Travel” superdomain) have multiple shared attribute nodes. For example, executable intent nodes for “Flight Booking,” “Hotel Booking,” “Car Rental,” “Get Route,” and “Find Points of Interest” share one or more of the attribute nodes “Starting Location,” “Destination,” “Departure Date / Time,” “Arrival Date / Time,” and “Number of People in Party.”

[0239] 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 called the "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, returning... Figure 7B The vocabulary associated with nodes of the "restaurant" attribute includes words such as "food," "drinks," "cuisine," "hunger," "eat," "pizza," "fast food," and "meals." Similarly, the vocabulary associated with nodes of the "initiate a phone call" action includes words and phrases such as "call," "make a phone call," "dial," "talk to," "call this number," and "make a phone call." The vocabulary index 744 optionally includes words and phrases from different languages.

[0240] Natural Language Processing (NLP) module 732 receives candidate text representations (e.g., one or more text strings or one or more sequences of symbols) from STT processing module 730 and, for each candidate representation, determines which nodes a word in the candidate text representation relates to. In some examples, if a word or phrase in a candidate text representation is found to be associated with one or more nodes in knowledge ontology 760 (via lexical index 744), then that word or phrase "triggers" or "activates" those nodes. Based on the number and / or relative importance of the activated nodes, NLP module 732 selects one executable intent as the task 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 individual 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, such as whether the digital assistant has previously correctly interpreted similar requests from the user, are also considered in the node selection process.

[0241] 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- or long-term information for each user. In some examples, the natural language processing module 732 uses user-specific information to supplement the information contained in the user input to further refine the user's intent. For example, in response to a user request "Invite my friends to my birthday party," the natural language processing module 732 can access user data 748 to determine who the "friends" are and when and where the "birthday party" will be held, without requiring the user to explicitly provide such information in their request.

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

[0243] Further details regarding the symbol string-based search of knowledge ontology are described in U.S. Utility Model Patent Application Serial No. 12 / 341743, entitled "Method and Apparatus for Searching Using An Active Ontology," filed on December 22, 2008, the entire disclosure of which is incorporated herein by reference.

[0244] In some examples, once the natural language processing module 732 identifies an executable intent (or domain) based on a user request, it 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 these parameters are populated with specific information and requirements specified in the user request. For example, a user says, “Reserve a table at a sushi restaurant for 7 pm.” 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 for the “restaurant reservation” domain includes parameters such as {cuisine}, {time}, {date}, {number of people}, 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 partially structured query for the restaurant reservation domain, where the partially structured query includes the parameters {cuisine = “sushi”} and {time = “7 pm”}. However, in this example, the user's utterance contains insufficient information to complete a structured query associated with the domain. Therefore, based on the currently available information, no other necessary parameters such as {number of people at the party} and {date} are specified in the structured query. In some examples, the natural language processing module 732 uses the received context information to populate some parameters of the structured query. For example, in some examples, if a user requests a "nearby" sushi restaurant, the natural language processing module 732 uses GPS coordinates from the user's device to populate the {location} parameter in the structured query.

[0245] In some examples, the Natural Language Processing (NLP) module 732 identifies multiple candidate executable intents for each candidate text representation received from the STT processing module 730. Additionally, in some examples, a corresponding structured query (partially or entirely) is generated for each identified candidate executable intent. The NLP module 732 determines an intent confidence score for each candidate executable intent and ranks the candidate executable intents based on the intent confidence scores. In some examples, the NLP module 732 transmits one or more of the generated 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 intents 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 intents, along with corresponding one or more candidate text representations, are provided to the task flow processing module 736.

[0246] Further details regarding the inference of user intent based on multiple candidate executable intents determined from multiple candidate text representations of speech input are described in U.S. Utility Model Patent Application Serial No. 14 / 298,725, filed June 6, 2014, entitled “System and Method for Inferring UserIntent from Speech Inputs,” the entire disclosure of which is incorporated herein by reference.

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

[0248] As described above, to complete a structured query, task flow processing module 736 needs to initiate additional dialogue with the user to obtain additional information and / or clarify potentially ambiguous statements. When such interaction is necessary, task flow processing module 736 invokes dialogue flow processing module 734 to participate in the dialogue with the user. In some examples, dialogue flow processing module 734 determines how (and / or when) to request additional information from the user and receives and processes user responses. Questions are presented to the user and answers are received from the user via I / O processing module 728. In some examples, dialogue flow processing module 734 presents dialogue output to the user via audible and / or visual output and receives input from the user via verbal or physical (e.g., click) responses. Continuing with the above example, when task flow processing module 736 invokes dialogue flow processing module 734 to determine the "party size" and "date" information for a structured query associated with the domain "restaurant reservation," dialogue flow processing module 734 generates questions such as "How many people in a row?" and "Which day to book?" and presents them to the user. Once a response is received from the user, the dialogue flow processing module 734 either fills 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.

[0249] Once the task flow processing module 736 has completed the structured query for the executable intent, it begins executing 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 based on 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 the restaurant and actually requesting a reservation for a specific number of people at a specific time for a specific party. For example, using a structured query such as: {restaurant reservation, restaurant = ABC Cafe, date = 3 / 12 / 2012, time = 7pm, number of people = 5}, the task flow processing module 736 can perform the following steps: (1) log in to ABC Cafe's server or such as OPENTABLE. ® The restaurant reservation system, (2) inputs date, time and party number information on the website, (3) submits the form, and (4) creates a calendar entry for the reservation in the user's calendar.

[0250] In some examples, task flow processing module 736, with the assistance of service processing module 738 (“service processing module”), completes the task requested in the user input or provides the informational answer requested in the user input. For example, service processing module 738, on behalf of task flow processing module 736, initiates a phone call, sets a calendar entry, invokes a map search, invokes or interacts with other user applications installed on the user's device, and invokes or interacts with third-party services (e.g., restaurant reservation portals, social networking sites, bank portals, etc.). In some examples, the protocols and application programming interfaces (APIs) required for each service are specified through the corresponding service model in service model 756. Service processing module 738 accesses the appropriate service model for a service and, based on the service model, generates a request for that service according to the protocols and APIs required by that service.

[0251] For example, if a restaurant has enabled an online reservation service, it submits a service model that specifies the necessary parameters for making a reservation and the values ​​of those parameters to be transmitted to the online reservation service's API. 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 transmit the necessary reservation parameters (e.g., time, date, number of party members) to the online reservation interface in a format appropriate to the online reservation service's API.

[0252] In some examples, the natural language processing module 732, the dialogue flow processing module 734, and the task flow processing module 736 are used together and repeatedly to infer and define the user's intent, obtain information to further clarify and refine the user's intent, and ultimately generate a response (i.e., output to the user, or to complete a task) to satisfy the user's intent. The generated response is a dialogue response to the voice input that at least partially satisfies the user's intent. Additionally, in some examples, the generated response is output as speech output. In these examples, the generated response is passed to the speech synthesis processing module 740 (e.g., a speech synthesizer), which processes the generated response to synthesize the dialogue response in speech form. In other examples, the generated response is data content related to satisfying a user request in the voice input.

[0253] 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 a first structured query of the received structured queries to attempt to complete the first structured query and / or execute one or more tasks or actions represented by the first structured query. In some examples, the first structured query corresponds to the highest-ranking executable intent. In other examples, the first structured query is selected from structured queries received based on a 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 necessary parameters), the task flow processing module 736 may continue to select and process a second structured query from the received structured queries that corresponds to a lower-ranking executable intent. For example, the second structured query may be selected based on the speech recognition confidence score of the corresponding candidate text representation, the intent confidence score of the corresponding candidate executable intent, missing necessary parameters in the first structured query, or any combination thereof.

[0254] The speech synthesis processing module 740 is configured to synthesize speech output for presentation to a user. The speech synthesis processing module 740 synthesizes speech output based on text provided by a 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 audible speech output. The speech synthesis processing module 740 uses any appropriate speech synthesis technique to generate speech output from text, including but not limited to: concatenation synthesis, unit selection synthesis, diphone synthesis, domain-specific synthesis, formant synthesis, articulation synthesis, Hidden Markov Model (HMM) based synthesis, 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 those words. For example, phoneme strings are associated with words in the generated dialogue response. The phoneme strings are stored in metadata associated with the words. The speech synthesis processing module 740 is configured to directly process the phoneme strings in the metadata to synthesize words in speech form.

[0255] In some examples, instead of using a speech synthesis processing module 740 (or otherwise), speech synthesis is performed on a remote device (e.g., server system 108), and the synthesized speech is transmitted to a user device for output to the user. For example, this could occur in some implementations where the output of a digital assistant is generated at the server system. And since server systems typically have greater processing power or more resources than user devices, they are likely to achieve higher quality speech output than client-side synthesis would achieve.

[0256] Additional details regarding digital assistants can be found in U.S. Utility Model Patent Application No. 12 / 987,982, filed January 10, 2011, entitled “Intelligent Automated Assistant,” and U.S. Utility Model Patent Application No. 13 / 251,088, filed September 30, 2011, the entire disclosure of which is incorporated herein by reference.

[0257] Figures 8A to 8J Exemplary user interfaces for performing tasks are illustrated according to various examples. These figures also illustrate the processes described below, including... Figure 9 process 900 and Figure 10 The process is 1000.

[0258] Figure 8A Examples include electronic devices 800 (e.g., devices 104, 122, 200, 600, or 700). In Figures 8A to 8J In the non-limiting exemplary embodiment illustrated, electronic device 800 is a smartphone. In other embodiments, electronic device 800 may be different types of electronic devices, such as wearable devices (e.g., smartwatches, headsets), smart speakers, and / or set-top boxes. In some examples, electronic device 800 has a display 801, one or more input devices (e.g., a touchscreen, buttons, microphone of display 801), and wireless communication radio components. In some examples, electronic device 800 includes one or more forward and / or rearward cameras. In some examples, the electronic device includes one or more biometric sensors, which optionally include cameras, such as infrared cameras, thermal imaging cameras, or combinations thereof.

[0259] In some examples, electronic device 800 is configured to operate according to one or more modes, including hands-free mode and hands-free mode. Typically, when operating in hands-free mode, electronic device 800 operates in a manner that allows operation without requiring the user to approach (e.g., near, hold) electronic device 800. As an example, when operating in hands-free mode, electronic device 800 displays a user interface that is easier to view from a distance (e.g., 3 feet, 6 feet, 10 feet). As an example, the user interface displayed when electronic device 800 is in hands-free mode may be magnified at a specific magnification level (e.g., 2X) relative to a baseline magnification level (e.g., 1X). As another example, the user interface displayed when electronic device 800 is in hands-free mode may be simplified compared to the user interface displayed when electronic device 800 is not in hands-free mode (e.g., in hands-free mode). In some examples, electronic device 800 operates in hands-free mode only when the hands-free option is enabled for electronic device 800.

[0260] When operated in hands-free mode, electronic device 800 operates in a manner that allows a user to operate electronic device 800 by approaching (e.g., nearing, holding) electronic device 800. As an example, when operated in hands-free mode, electronic device 800 displays the user interface at a baseline magnification level (e.g., 1X) and optionally includes one or more features that may not be available in the user interface displayed when electronic device 800 is operated in hands-free mode, such as options that are needed or otherwise best suited for touch-based input.

[0261] In some examples, electronic device 800 selects an operating mode based on multiple criteria (e.g., proximity criteria). One example criterion is met when electronic device 800 is coupled to (e.g., a specific type of) charger, stand, base, housing, or combinations thereof and / or oriented in a lateral orientation. Another example criterion is met based on the user's distance from electronic device 800 (e.g., at least a threshold distance and / or within a threshold distance). Another example criterion is met when a predetermined type of input and / or a user's face is detected. Electronic device 800 may, for example, detect touch input and / or the presence of a user's face (e.g., as indicated by the field of view of electronic device 800's camera) and switch from hands-free mode to hands-free mode in response. Additionally, electronic device 800 may detect no input and / or the absence of a user's face within a predetermined amount of time and switch from hands-free mode to hands-free mode.

[0262] exist Figure 8AWhen the electronic device 800 is oriented in portrait orientation and in a hands-free mode, the electronic device 800 displays a user interface 810 on the display 801. In some examples, the electronic device 800 operates in hands-free mode in response to being oriented in portrait orientation. In some examples, the electronic device 800 operates in hands-free mode because the electronic device 800 is not coupled to a charger or dock.

[0263] Because Figure 8A In this context, electronic device 800 is operating in hands-free mode, so electronic device 800 displays user interface 810 (e.g., main interface) at a baseline magnification level (e.g., 1X), as described. As shown, user interface 810 includes one or more indicators (e.g., complex function blocks, interactive objects, icons, graphical data items, power indicators, widgets), such as media indicator 811, weather indicators 812a-812c, reminder indicators 813a-813b, and time indicator 814. In some examples, the indicators of user interface 810 are configurable. For example, the user of electronic device 800 can optionally add any number of indicators to user interface 800 and / or remove any number of indicators from the user interface. For example, the selection to edit power indicator 815 initiates a process for adding and / or removing indicators from user interface 810.

[0264] exist Figure 8A In this configuration, when the user interface 810 is displayed, the electronic device 800 is rotated (e.g., in direction 803) such that the electronic device 800 is oriented in a horizontal orientation (and optionally coupled (e.g., attached to, mounted on) a charging dock). Therefore, the electronic device transitions to a hands-free operation mode and displays the user interface 810 in a horizontal configuration. Figure 8B As shown, because the electronic device 800 is operating in hands-free mode, the electronic device 800 displays the user interface 810 (e.g., the main interface) at a predetermined magnification level (e.g., 2X), as described. In some examples, the electronic device modifies the user interface 810 when switching from hands-free mode to hands-free mode. As an example, the user interface 810 may be adjusted to fit a landscape orientation and / or may be modified to include (or omit) one or more objects (e.g., indicator 812b may be modified to indicate the probability of precipitation, and the editable indicator 815 may be omitted).

[0265] When user interface 810 is displayed, electronic device 800 (e.g., via microphone of electronic device 800) receives user input 810a. In some examples, user input 810a is natural language voice input instructing a request directed to the digital assistant of electronic device 800 (e.g., “Hey assistant, send a message to Nadia 'Are you free at 12 o’clock?’”). User input 810a may include, for example, a voice trigger for activating the digital assistant (e.g., “Hey assistant”). In some examples, user input 810a may include any request that may be directed to the digital assistant. By way of example, the portion of user input 810a stating “send a message to Nadia 'Are you free at 12 o’clock?’” may request the digital assistant of electronic device 800 to initiate a process for providing a message with specified message content (e.g., “Are you free at 12 o’clock?”) to the contact Nadia.

[0266] In some examples, electronic device 800 displays a digital assistant indicator 820 to indicate that the digital assistant of electronic device 800 is active (e.g., activated). For example, in response to receiving user input 810a (recalling user input 810a including voice triggering), electronic device 800 may activate its digital assistant and display the digital assistant indicator 820. In some examples, the digital assistant indicator 820 overlays the user interface 810 and is optionally positioned such that the digital assistant indicator 820 does not interfere with the display of one or more objects on the user interface 810. In some examples, (e.g., using touch input) selection of the digital assistant indicator 820 causes electronic device 800 to perform one or more functions associated with the digital assistant. In at least one example, selection of the digital assistant indicator 820 causes electronic device 800 to stop any current operation performed by the digital assistant of the electronic device, and optionally, resets the digital assistant of the electronic device to an initial state (e.g., a state where the digital assistant is ready to receive commands). Additionally or alternatively, in some examples, selection of the digital assistant indicator 820 causes electronic device 800 to modify one or more visual characteristics of the digital assistant indicator 820. Modifying visual characteristics in this way includes, for example, changing the color and / or size of the digital assistant indicator 820 (e.g., shrinking it).

[0267] In response to user input 810a, electronic device 800 activates its digital assistant, and the digital assistant initiates the execution of a task corresponding to input 810a. In some examples, initiating the execution of a task also includes providing output corresponding to that task. In some examples, electronic device 800 provides output confirming that the task has been initiated and / or indicating that further user input is needed to execute the task (e.g., natural language speech output). For example, see reference... Figure 8CElectronic device 800 provides output 822a, which describes the contact and content of the message the user intends to send and requests confirmation that the message should be sent (e.g., “Recipient: Nadia, ‘Are you free at 12 o’clock?’ Send it?”). The user can then provide a response to the output (e.g., “Yes, send.”) (e.g., response 822b), thereby causing electronic device 800 to send the message. Figure 8D As shown, for example, instructing electronic device 800 to transmit a message causes electronic device 800 to display user interface 832. User interface 832 includes message history 833 indicating that a task has been performed (e.g., a message has been transmitted).

[0268] In some examples, the electronic device 800 provides output by displaying a user interface corresponding to the task. (Reference) Figure 8C For example, electronic device 800 displays a user interface 824 for transmitting messages requested by a user. In the illustrated example, electronic device 800 maintains operation in hands-free mode. Therefore, electronic device 800 displays user interface 824 at a predetermined magnification level. Although in the illustrated example, electronic device 800 is shown replacing the display of user interface 810 with user interface 824, it should be understood that in some examples, user interface 824 overlays a portion of user interface 810, thereby maintaining the display of at least a portion of user interface 810.

[0269] User interface 824 includes a contact identifier 826 and a message content 828, respectively corresponding to a specified contact and message content. User interface 824 also includes a cancel enable indicator 830a, which, when selected, causes electronic device 800 to cancel execution of a task. In response to canceling execution of a task, electronic device optionally returns to user interface 810 (e.g., restores its display).

[0270] The user interface also includes a transmission power indicator 830b, which, when selected, causes the electronic device 800 to perform a task. For example, when the user interface 824 is displayed, the electronic device 800 detects a selection of the transmission power indicator 830b. This selection is a tap gesture 824a on the transmission power indicator 830b. In response to detecting the tap gesture 824a, the electronic device 800 performs the task and displays the user interface 832. Figure 8D ), as described.

[0271] In some examples, a user may wish to interact with electronic device 800 regarding an initiated task. The user may, for example, want to launch and / or otherwise access an application associated with the task, such as to specify additional parameters and / or modify existing parameters of the task. By way of example, user interface 824 includes an application icon 825, selecting which causes electronic device 800 to launch a messaging application. In some examples, launching an application in this manner also includes preloading the application with one or more parameters (e.g., specifying contacts and message content). In some examples, launching the application puts electronic device 800 into hands-free mode. Therefore, in some examples, because user interface 824 is displayed when electronic device 800 is operating in hands-free mode, selecting application icon 825 switches the electronic device from hands-free mode to hands-free mode.

[0272] In some examples, users might want to specify additional parameters and / or modify existing parameters of the task, for example, without launching the application. See the examples below. Figure 8C When the user interface 824 is displayed, the electronic device 800 detects a selection of the message content 828. In the illustrated example, the selection is a tap gesture 824b on the message content 828; however, it should be understood that in other examples, the selection of the message content 828 is a selection of a field or portion of the user interface 824 that includes the message content 828.

[0273] As described, in some examples, electronic device 800 can switch from hands-free mode to hands-free mode based on multiple criteria, including whether electronic device 800 has detected one or more inputs and / or detected the user's face. In the illustrated example, for example, in response to a tap gesture 824b, electronic device 800 switches from hands-free mode to hands-free mode and displays user interface 834, as shown. Figure 8EAs shown. Because the electronic device 800 displays a user interface 834 when operating in hands-free mode, the user interface 834 is displayed at a baseline (e.g., 1X) zoom level and optionally includes one or more features not included in the user interface 824 (e.g., a virtual keyboard 844, which can be used to edit and / or otherwise modify message content). In some examples, the user interface 834 is a modified (e.g., updated) version of the user interface 824. Therefore, the user interface 834 may include one or more portions of the user interface 824 and / or one or more objects (e.g., interactive graphical user interface objects) included in the user interface 824. Because the user interfaces 824 and 834 can be displayed at different zoom levels (recall that these interfaces can be displayed in different modes respectively), objects (and / or portions of the user interface) may be displayed at a first zoom level (e.g., 2X, 3X) in the user interface 824 and at a second zoom level in the user interface 834. As an example, the user interface 834 includes a contact identifier 836 and message content 838, which may correspond to the user interface 824 ( Figure 8C The contact identifier 824 and message content 828 are displayed in the user interface 824 at a first zoom level (e.g., a relatively high zoom level, 2X), and the contact identifier 836 and message content 838 are displayed at a second zoom level (e.g., a relatively low zoom level, 1X) different from the first zoom level.

[0274] User interface 834 includes an application icon 840 that indicates an application associated with the task and / or user interface 834. Selecting the application icon 840 causes the electronic device 800 to launch the associated application. In the illustrated example, for instance, selecting the application icon 840 causes the electronic device 800 to launch a messaging application. In some examples, launching an application in this manner also includes preloading the application with one or more parameters (e.g., specifying contacts and message content). In some examples, the user interface of the launched application is displayed according to the hands-on mode.

[0275] User interface 834 also includes a cancel enable indicator 842a, which, when selected, causes electronic device 800 to cancel execution of a task. In response to canceling execution of a task, electronic device may optionally return to user interface 810 (e.g., restore its display). User interface also includes a transmit enable indicator 842b, which, when selected, causes electronic device 800 to execute a task, as described.

[0276] In some examples, after displaying user interface 834, electronic device 800 resumes operation in hands-free mode. In at least one example, if no user input and / or user face is detected within a threshold time period, electronic device 800 resumes operation in hands-free mode and optionally resumes display of user interface 810. In another example, electronic device 800 resumes operation in hands-free mode in response to performing a task. Electronic device 800 may, for example, switch to hands-free mode when displaying user interface 832.

[0277] In some examples, during or after a task is performed, the user can provide a specific type of input (e.g., a swipe gesture) to cause the electronic device 800 to display a main interface (e.g., user interface 824). In some examples, providing input in this way causes the electronic device 800 to cancel the execution of the task if it has not yet been completed. Reference Figure 8D When user interface 832 is displayed, electronic device 800 detects input 832a. In some examples, input 832a is a swipe gesture (e.g., an up swipe gesture). In response to detecting input 832a, electronic device 800 displays the main interface (e.g., restores its display). For example, as... Figure 8F As shown, in response to input 832a, electronic device 800 displays user interface 810 (e.g., restores its display).

[0278] exist Figure 8F When operating in hands-free mode, the electronic device 800 displays the user interface 810 on the display 801. Because... Figure 8F In this context, the electronic device 800 is operating in hands-free mode, so the electronic device 800 displays the user interface 810 at a predetermined magnification level (e.g., 2X), as described. As shown, the user interface 810 includes one or more indicators, such as weather indicators 812a to 812c and a time indicator 814. In some examples, the indicators of the user interface 810 are configurable. For example, the user of the electronic device 800 may optionally add any number of indicators to the user interface 800 and / or remove any number of indicators from the user interface.

[0279] exist Figure 8FIn this example, electronic device 800 operates according to one of a set of caption patterns, which determines how captions are displayed for dialogue between the user and the digital assistant of electronic device 800. In the illustrated example, electronic device 800 operates in a mode that provides captions for all dialogue between the user and the digital assistant of electronic device 800. In another example, electronic device 800 operates in a mode that provides captions if it determines that a user is near electronic device 800. In yet another example, electronic device 800 operates in a mode that provides captions for dialogue provided by the digital assistant of electronic device 800 (rather than the user). In yet another example, captions are provided for user interactions that operate electronic device 800. For example, if a task is initiated to cause the electronic device to display a user-interactive object, electronic device 800 provides captions for that object.

[0280] As shown in the figure, when the user interface 810 is displayed, the electronic device 800 (e.g., via the microphone of the electronic device 800) receives user input 810b. In some examples, user input 810b is natural language voice input instructing a request directed to the digital assistant of the electronic device 800 (e.g., "Hey assistant, set the timer to 10 minutes"). User input 810b may include, for example, a voice trigger for activating the digital assistant (e.g., "Hey assistant"). In some examples, user input 810b may include a request directed to the digital assistant. By way of example, the statement "set the timer to 10 minutes" in user input 810b may request the digital assistant of the electronic device 800 to initiate a process for starting the timer. Because the electronic device 800 operates in caption mode, displaying all dialogue between the user and the digital assistant of the electronic device 800, the electronic device 800 displays caption 816a corresponding to user input 810b.

[0281] In response to user input 810b, electronic device 800 activates its digital assistant, and the digital assistant initiates the execution of a task corresponding to input 810b (e.g., starting a timer for a specified duration). In some examples, initiating the execution of the task also includes providing output corresponding to that task. (See reference) Figure 8G The electronic device 800 provides output confirming that a task has been initiated (e.g., natural language speech output). For example, the electronic device 800 provides output 810c stating that a timer has been started ("10 minutes, countdown") and displays a timer indicator 817 corresponding to the started timer. In some examples, the electronic device 800 displays the timer indicator 817 such that it is persistent (e.g., overlaid on any number of user interfaces). Because the electronic device 800 operates in caption mode, displaying all dialogue between the user and the digital assistant of the electronic device 800, the electronic device 800 displays caption 816b corresponding to output 810c.

[0282] Subsequently, electronic device 800 (e.g., via its microphone) receives user input 810d. In some examples, user input 810c is natural language voice input instructing a request directed to the digital assistant of electronic device 800 (e.g., "Hey assistant, find me coffee"). User input 810c may include, for example, a voice trigger for activating the digital assistant (e.g., "Hey assistant"). In some examples, user input 810c may include a request directed to the digital assistant. By way of example, the statement "Find me coffee" in user input 810d may request the digital assistant of electronic device 800 to initiate a process for locating a coffee shop near the user's location.

[0283] In response to user input 810d, electronic device 800 activates its digital assistant, and the digital assistant initiates the execution of a task corresponding to input 810d (e.g., locating a coffee shop). In some examples, initiating the execution of a task also includes providing output corresponding to that task. As an example, electronic device 800 provides output 810e indicating that a task has been initiated (“Looking for coffee”). Because electronic device 800 operates in caption mode, displaying all dialogue between the user and its digital assistant, electronic device 800 displays captions 816c and 816d corresponding to user input 810d and output 810e.

[0284] refer to Figure 8H The electronic device 800 then displays a user interface 850 including a result 852 corresponding to the task. The electronic device 800 also provides output 810f, which includes an indication that the task has been performed (“These are the results I found.”) and a query asking the user if they want a route corresponding to one of these results (“Need directions to EndlessCoffee?”). Because the electronic device 800 operates in caption mode, displaying all conversations between the user and the digital assistant of the electronic device 800, the electronic device 800 displays caption 816e corresponding to output 810f.

[0285] As described, in some examples, one or more objects (such as timer indicator 817) are persistent, and in some cases, although an object may be persistent, its position and / or visual characteristics may be modified when displayed in a new user interface. For example, in the illustrated example, the position of one or more results 852 may be displayed in user interface 850 relative to user interface 810. Figure 8FThe timer indicator 817 is displayed at a position corresponding to the position of the timer indicator 817 in the user interface 850. Therefore, in the user interface 850, the electronic device 800 may display the timer indicator 817 at a position that avoids displaying the timer indicator 817 at the same position as the result 852 and / or one or more other objects of the user interface 850. Furthermore, the timer indicator 817 may optionally be displayed in the user interface 850 in a different manner than in the user interface 810. For example, this can provide greater flexibility for the electronic device 800 in combining various ways of displaying the timer indicator 817 with objects of the user interface.

[0286] exist Figure 8I When operating in hands-free mode, the electronic device 800 displays the user interface 810 on the display 801. Because... Figure 8I In this context, electronic device 800 is operating in hands-free mode, so electronic device 800 displays user interface 810 at a predetermined magnification level (e.g., 2X), as described. As shown, user interface 810 includes one or more indicators, such as weather indicators 812a to 812c, time indicator 814, and timer indicator 817. In some examples, the indicators of user interface 810 are configurable. For example, the user of electronic device 800 may optionally add any number of indicators to user interface 800 and / or remove any number of indicators from the user interface.

[0287] When user interface 810 is displayed, electronic device 800 (e.g., via microphone of electronic device 800) receives user input 810g. In some examples, user input 810g is natural language voice input instructing a request to the digital assistant of electronic device 800 (e.g., “Hey assistant, play Petey Oh’s Track One”). User input 810g may include, for example, a voice trigger for activating the digital assistant (e.g., “Hey assistant”). In some examples, user input 810d may include a request that can be directed to the digital assistant. By way of example, the part of user input 810d that states “play Petey Oh’s Track One” may request the digital assistant of electronic device 800 to initiate a process for playing the song “Track One” by the artist “Petey Oh”.

[0288] In response to user input 810d, electronic device 800 activates its digital assistant, and the digital assistant initiates the execution of a task corresponding to input 810g (e.g., playing back the requested song). In some examples, initiating the execution of a task also includes providing output corresponding to that task. As an example, electronic device 800 provides output 810h indicating that a task has been initiated ("Playing Petey Oh's Track One").

[0289] In some examples, one or more additional devices may be used to partially perform the task. For example, such as Figure 8J As shown, the electronic device initiates playback of the requested song on the electronic device 805 and displays a user interface 860 including controls 862 for managing the playback on the electronic device 805.

[0290] In some examples, electronic device 800 selects a device from a plurality of electronic devices to perform a task. Electronic device 800 may, for example, detect other electronic devices operating on the same network as electronic device 800, and / or detect other electronic devices associated with the same ecosystem (e.g., a home automation system) and / or user account. In some examples, electronic device 800 may select the electronic device to perform the task based on one or more metrics indicating which electronic device is best suited or most intended for the task. As an example, in the case of audio playback, electronic device 800 may select a device with optimal audio output capabilities (e.g., the loudest speaker) and / or optimal location (e.g., closest to the user).

[0291] Once a device is selected, electronic device 800 can instruct the device to perform one or more aspects of the requested task. Instructions provided in this manner can be provided via self-organizing connections or via one or more intermediate devices, such as communication networks (e.g., LAN, WAN, Internet).

[0292] Figure 9This is a flowchart of an exemplary process 900 for performing a task, based on various examples. For example, process 900 may be performed using one or more computer systems implementing a digital assistant (e.g., electronic devices, such as electronic device 800). In some examples, process 900 may be performed using a client-server system (e.g., system 100), and the boxes of process 900 may be divided in any way between a server (e.g., DA server 106) and client devices. In other examples, the boxes of process 900 may be divided between a server and multiple client devices (e.g., mobile phones and smartwatches). Therefore, while portions of process 900 are described herein as being performed by a specific device of a client-server system, it should be understood that process 900 is not limited thereto. In other examples, process 900 may be performed using only client devices (e.g., user device 104) or only multiple client devices. In process 900, some boxes may be optionally combined, the order of some boxes may be optionally changed, and some boxes may be optionally omitted. In some examples, additional steps may be performed in conjunction with process 900.

[0293] In some embodiments, the electronic device (e.g., 800) is a computer system (e.g., a personal electronic device (e.g., a mobile device (e.g., iPhone), tablet computer (e.g., iPad), smartwatch (e.g., Apple Watch), desktop computer (e.g., iMAC), or laptop computer (e.g., MacBook))) or a public electronic device (e.g., a smart TV (e.g., Apple TV) or smart speaker (e.g., HomePod))). The computer system optionally communicates with a display generating component (e.g., an integrated display and / or display controller) and with one or more input devices (e.g., a touch-sensitive surface (e.g., a touchscreen), a mouse, and / or a keyboard) (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as display via a CRT monitor, via an LED display, or via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0294] When operating in a hands-free operating mode (e.g., the hands-free operating mode of the computer system in which one or more functions of the computer system are adapted to be used without the use of touch input), the computer system receives (905) natural language speech input (e.g., 810a, 810b, 810d, 810e, 810g) that instructs a task. In some examples, the computer system receives from the user input that includes or otherwise identifies the task, such as speech input (e.g., natural language speech input).

[0295] In response to receiving the natural language speech input, the computer system initiates (910) the execution of the task.

[0296] The computer system provides (915) output (e.g., response) corresponding to the task (e.g., 810c, 810e, 810f, 817 and / or interfaces 822a, 824, 850, 860 including 817). In some examples, providing the output includes displaying a first user interface (e.g., 824, 850, 860) associated with an application (e.g., a first-party application, a third-party application). In some examples, the first user interface is displayed according to the hands-free operation mode. In some examples, when the computer system operates in the first mode, the computer system displays the first user interface in response to voice input. In some examples, the computer system is configured such that the computer system displays the first user interface only when operating in the first mode.

[0297] In some examples, when the first user interface is displayed, the computer system receives (920) touch input (e.g., 824b) at a location corresponding to the first user interface via one or more input devices.

[0298] In response to the touch input (925), the computer system transitions (930) from the hands-free operating mode to a hands-on operating mode different from the hands-free operating mode (e.g., one or more functions of the computer system are adapted to use the hands-on operating mode of the computer system by using touch input). In some examples, when operating in the first operating mode, the computer system receives touch input and, in response, transitions from the first operating mode to a second operating mode. In some examples, the touch input instructs the computer system that the user approaches and / or at least partially holds the computer system, and the appropriate operating mode is the second operating mode involving hands-on operation. In response to the touch input, the computer system initiates (935) (e.g., executes, launches) the application. In some examples, initiating the application includes displaying a second user interface according to the hands-on operating mode.

[0299] In some examples, displaying the first user interface includes displaying a first user interface object (e.g., a graphical object) at a first magnification (e.g., 812a to 812c, 814, 817, 820, 826, 828, 830a, 830b). In some examples, displaying the second user interface includes displaying the first user interface object at a second magnification different from the first magnification.

[0300] In some examples, the first magnification is greater than the second magnification.

[0301] In some examples, the computer system determines whether a set of proximity criteria is met. In some examples, this set of proximity criteria includes criteria met when the user is within a threshold distance of the computer system. In some examples, this set of proximity criteria includes criteria met when the computer system detects, for example, a specific user's face within the field of view of the computer system's camera. In some examples, this set of proximity criteria includes criteria met when the computer system detects touch input within a specific time period (e.g., a threshold amount of time after transitioning to hands-free mode). In some examples, based on the determination that the set of proximity criteria is met, the computer system maintains operation in the hands-free mode. In some examples, based on the determination that the set of proximity criteria is not met, the computer system transitions from the hands-free mode to the hands-free mode.

[0302] In some examples, the transition from the hands-free operating mode to the hands-free operating mode includes displaying a third user interface (e.g., 810, 832). In some examples, the third user interface is substantially similar to the first user interface. In some examples, the third user interface is substantially different from the first user interface associated with the application (e.g., a first-party application, a third-party application). In some examples, the third user interface is displayed according to the hands-free operating mode.

[0303] In some examples, the first user interface includes a second user interface object (e.g., 812a to 812c, 814, 817, 820, 826, 828, 830a, 830b), and the second user interface includes the second user interface object. In some examples, one or more objects (or portions thereof) of the first user interface are included in the second user interface. In some examples, the one or more objects are displayed at a first zoom level in the first user interface and at a second zoom level in the second user interface. In some examples, the first zoom level is greater than the second zoom level.

[0304] In some examples, the second user interface object corresponds to a digital assistant of a computer system. In some examples, the first user interface includes the second user interface object at a first location. In some examples, displaying the second user interface includes stopping the display of the second user interface object at the first location and displaying the second user interface object at a second location different from the first location. In some examples, displaying the second user interface includes moving the graphical user interface object to a new location on the display generating component.

[0305] In some examples, the first user interface includes a third user interface object corresponding to the application. In some examples, receiving the touch input at the location corresponding to the first user interface includes receiving the touch input at the location corresponding to the third user interface object.

[0306] The above references Figure 9 The described operation is optionally determined by Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C as well as Figures 8A to 8J The components depicted herein are used for implementation. For example, the operation of process 900 can be implemented by electronic device 800 and optionally a digital assistant executed thereon. Those skilled in the art will clearly understand how to implement... Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C and Figures 8A to 8J The components described herein are used to implement other processes.

[0307] Figure 10 This is a flowchart of an exemplary process 1000 for performing a task, based on various examples. For example, process 1000 may be performed using one or more electronic devices implementing a digital assistant. In some examples, process 1000 may be performed using a client-server system (e.g., system 100), and the boxes of process 1000 may be divided in any way between a server (e.g., DA server 106) and client devices. In other examples, the boxes of process 1000 may be divided between a server and multiple client devices (e.g., mobile phones and smartwatches). Therefore, while portions of process 1000 are described herein as being performed by a specific device of a client-server system, it should be understood that process 1000 is not limited thereto. In other examples, process 1000 may be performed using only client devices (e.g., user device 104) or only multiple client devices. In process 1000, some boxes may be optionally combined, the order of some boxes may be optionally changed, and some boxes may be optionally omitted. In some examples, additional steps may be performed in conjunction with process 1000.

[0308] In some embodiments, the electronic device (e.g., 800) is a computer system (e.g., a personal electronic device (e.g., a mobile device (e.g., iPhone), tablet computer (e.g., iPad), smartwatch (e.g., Apple Watch), desktop computer (e.g., iMAC), or laptop computer (e.g., MacBook))) or a public electronic device (e.g., a smart TV (e.g., Apple TV) or smart speaker (e.g., HomePod))). The computer system optionally communicates with a display generating component (e.g., an integrated display and / or display controller) and with one or more input devices (e.g., a touch-sensitive surface (e.g., a touchscreen), a mouse, and / or a keyboard) (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as display via a CRT monitor, via an LED display, or via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0309] The computer system (e.g., via one or more input devices) determines (1005) that a first set of proximity criteria has been met. In some examples, the first set of proximity criteria is met when the user is at least a threshold distance from the computer system. In some examples, the set of proximity criteria includes criteria met when the computer system is coupled to, for example, a specific type of charger. In some examples, the set of proximity criteria includes criteria met when the computer system is a device positioned in a lateral orientation.

[0310] In response to the detection that the first set of proximity criteria has been met, the computer system displays (1010) a user interface (e.g., 810) via the display generation component (e.g., 801). In some examples, the first user interface is a system user interface (e.g., a home screen) including one or more graphical objects (e.g., 812a to 812c, 814, 820). In some examples, the first user interface is a user interface for an application of the computer system (e.g., a first-party application, a third-party application) at a first zoom level. In some examples, the first user interface includes one or more user interface objects. In some examples, one or more of these objects (e.g., graphical objects) correspond to a current task; in one example, the task is a timer, in which case the object could be a countdown timer; as another example, the task is to provide a weather report, in which case the object could be a graphical representation of the weather (e.g., clouds, sun), and / or a numerical representation of temperature. In some examples, one or more of these objects are user-interactive; as an example, a user can select a graphical object to launch an application corresponding to that object (e.g., selecting a cloud launches a weather application). In some examples, the object is displayed at a predetermined magnification. In some examples, the magnification of the object is based at least in part on whether the first set of proximity criteria is met. In some examples, if the first set of proximity criteria is met, the object is displayed at a first (e.g., a greater) magnification.

[0311] When the user interface is displayed, the computer system receives (1015) natural language speech input (e.g., 810a, 810b, 810d, 810g) instructing a task via the one or more input devices. In some examples, the computer system receives input from the user that includes or otherwise identifies the task, such as speech input (e.g., natural language speech input).

[0312] In response to the natural language speech input, the computer system initiates (1020) the execution of the task. In some examples, in response to receiving the input from the user, the computer system identifies the task identified by the input and initiates the execution of the task. In some examples, initiating the execution of the task includes updating a first part of the user interface (e.g., 810, 824).

[0313] The computer system (e.g., via one or more input devices) determines (1025) that a second set of proximity criteria, different from the first set of proximity criteria, has been met. In some examples, the second set of user proximity criteria is met when the computer system determines that a user is near the computer system. In some examples, the computer system determines that a user is near the device when the user is within a certain distance of the computer system. In some examples, the computer system determines that a user is near the device when it detects the user's face. In some examples, the computer system determines that a user is near the computer system when it detects the faces of one or more pre-determined users (e.g., by authenticating the faces of the one or more pre-determined users). In some examples, the computer system determines that a user is near the device when it detects user input (such as touch input or gestures).

[0314] In response to the detection that the second set of proximity criteria has been met, the computer system displays (1030) a second portion of the user interface at a second magnification level different from the first magnification level via the display generation component. In some examples, if the second set of user proximity criteria is met (e.g., it is determined that a user is close to the computer system), the object is displayed at a second (e.g., a lower magnification).

[0315] In some examples, the first magnification level is greater than the second magnification level.

[0316] In some examples, displaying the user interface at the first zoom level includes displaying a first user interface object (e.g., a display, an interactive user interface object, text, or a graphical object) at the first zoom level (e.g., 812a to 812c, 814, 817, 820). In some examples, displaying the second portion of the user interface at a second zoom level different from the first zoom level includes displaying the first user interface object at the second zoom level.

[0317] In some examples, displaying a second portion of the user interface at a second magnification level different from the first magnification level includes modifying one or more objects of the second portion of the user interface. In some examples, the computer system modifies one or more aspects of the user interface when displaying the user interface (or a portion thereof). In some examples, modifying the user interface in this way includes stopping the display of one or more objects of the user interface that are included in the user interface when displayed at the first magnification level. In some examples, modifying the user interface in this way includes displaying one or more additional objects that are not included in the user interface when displayed at the first magnification level. In some examples, modifying the user interface in this way includes repositioning (e.g., shifting and / or rotating) and / or visually modifying one or more objects that are included in the user interface when displayed at the first magnification level.

[0318] In some examples, determining that the second set of proximity criteria has been met includes determining that a user is near the computer system. In some examples, the one or more input devices include a camera. In some examples, determining that a user is near the computer system includes detecting the user's face within the camera's field of view. In some examples, the computer system includes a camera optionally used to detect the user's presence. In some examples, the camera is used to detect the user's face. In some examples, the second set of proximity criteria includes criteria for a specific user (or a group of users) to be near the computer system, and the computer system uses the detected user face to authenticate the user.

[0319] In some examples, determining that a user is near the computer system includes detecting touch input via one or more input devices.

[0320] In some examples, when the second portion of the user interface is displayed at a second magnification level different from the first magnification level, the computer system displays the second portion of the user interface at the first magnification level based on the determination that the second set of proximity criteria has not been met within a threshold time period (e.g., no input, such as touch or voice input, is received within the threshold time period, and / or no user face is detected within the threshold time period). In some examples, if the computer system does not detect input and / or does not detect a face within the threshold time period, the computer system stops displaying the user interface (or a portion thereof) at the second magnification level and optionally resumes displaying the user interface at the first magnification level.

[0321] In some examples, when the second portion of the user interface is displayed at a second magnification level different from the first magnification level, the computer system detects user input via the one or more input devices (e.g., 832a). In some examples, based on determining that the user input is a swipe gesture, the computer system displays the main interface. In some examples, the user interface is the home screen user interface. In some examples, the main interface is displayed at the second magnification level. In some examples, based on determining that the user input is a selection of a second user interface object of the user interface, the computer system switches from hands-free operation mode to hands-free operation mode. In some examples, based on determining that the user input is a selection of a second user interface object of the user interface, the computer system launches an application associated with the second user interface object of the user interface.

[0322] In some examples, displaying the user interface at the first zoom level includes displaying a third user interface object associated with the digital assistant at a first location on the user interface. In some examples, updating a first portion of the user interface includes displaying the third user interface object associated with the digital assistant at a second location on the user interface, different from the first user interface (e.g., 817). In some examples, updating the user interface (or a portion thereof) includes moving a user interface object that, when selected, invokes a digital assistant function.

[0323] In some examples, updating the first part of the user interface includes: displaying an interactive user interface object (e.g., 852 or a portion thereof) and a first text user interface object (e.g., 816e) corresponding to the interactive user interface object, depending on whether a text object setting is enabled. In some examples, if the text object setting is enabled, the computer system is configured to operate in a mode (e.g., a voice-first mode) such that subtitles (e.g., digital assistant subtitles) are provided (e.g., provided only) for the audio output corresponding to the interactive user interface object displayed by the computer system; for example, a user may ask a digital assistant “When is the Oscars?” and in response, the digital assistant may reply with an answer (e.g., February 12, 2024). The computer system may also provide (1) an object that, when selected, causes a web browser to launch and display the Oscars website, and (2) output that prompts the user to “go to Oscars.org” if the user expects more information on the topic. Because the object is interactive (e.g., can be selected by the user to perform tasks and / or functions), the digital assistant displays captions corresponding to the output (e.g., captions stating "Go to Oscars.org").

[0324] In some examples, initiating the execution of the task includes providing audio output corresponding to the natural language speech input (e.g., 810c, 810e, 810f). In some examples, the digital assistant acknowledges receipt of the natural language speech input and / or indicates that the digital assistant is initiating a task based on the natural language speech input. In some examples, initiating the execution of the task includes displaying a second text user interface object corresponding to the audio output (e.g., 816b, 816d, 816e) upon determining that a user is approaching the computer system. In some examples, the computer system is configured to operate in a mode (e.g., display mode) in which captions are provided (e.g., provided only) for all dialogue provided by the digital assistant when a user is determined to be approaching the computer system (e.g., indicated by touch input or facial detection).

[0325] In some examples, initiating the execution of the task includes providing a response to the natural language speech input as audio output (e.g., 810c, 810e, 810f). In some examples, the digital assistant acknowledges receipt of the natural language speech input and / or indicates that the digital assistant is initiating a task based on the natural language speech input. In some examples, initiating the execution of the task includes displaying a third text user interface object corresponding to the audio output (e.g., 810c, 810e, 810f). In some examples, the computer system is configured to operate in a mode (e.g., dialogue captioning mode) that provides captions for all dialogues provided by the digital assistant, regardless of whether it is determined that the user is near the computer system. In some examples, when operating in this mode, no captions are provided for the user's speech.

[0326] In some examples, initiating the execution of the task includes displaying a fourth text user interface (e.g., 816a, 816c) corresponding to the natural language speech input. In some examples, the computer system is configured to operate in a mode that provides captions for all conversations exchanged between the user and the digital assistant.

[0327] In some examples, determining that the first set of proximity criteria has been met includes determining that the hands-free option is enabled. In some examples, when the hands-free option is enabled, the computer system determines whether each set of proximity criteria is met and / or adjusts the magnification. In some examples, if the hands-free option is not enabled, the computer system abandons displaying the user interface at varying magnification levels based on whether the proximity criteria are met, and instead maintains the same magnification level regardless of whether other proximity criteria are met.

[0328] In some examples, initiating the execution of the task (e.g., media playback) includes providing the task to an electronic device (e.g., a smart speaker, set-top box) (e.g., 805). In some examples, initiating the execution of the task (e.g., media playback) includes updating a first portion of the user interface, including displaying an indication that the task has been provided to the electronic device (e.g., 816h, 860). In some examples, the computer system indicates that the task has been initiated, for example, indicating that the task has been initiated on another device. In some examples, providing the task to the electronic device includes identifying a set of candidate devices for performing the task, the set of candidate devices including the electronic device. In some examples, providing the task to the electronic device includes selecting the electronic device from the set of candidate devices.

[0329] In some examples, updating a first portion of the user interface includes displaying a set of controls (e.g., 862) for controlling the performance of the task on the electronic device. In some examples, the user interface (or a portion thereof) is updated to include a set of controls for controlling the electronic device. In some examples, the controls are used to control how the task is performed on the electronic device; by way of example, the controls may include media controls, such as play, pause, etc., which can be used to control playback on the electronic device.

[0330] The above references Figure 10 The described operation is optionally determined by Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C as well as Figures 8A to 8J The components depicted herein are used for implementation. For example, the operation of process 1000 can be implemented by electronic device 800 and optionally a digital assistant executed thereon. Those skilled in the art will readily understand how to implement... Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C and Figures 8A to 8J The components described herein are used to implement other processes.

[0331] Figures 11A to 11C Exemplary techniques for performing functions, according to various examples, are illustrated. These figures also illustrate the processes described below, including… Figure 12 Process 1200 and Figure 13 The process is 1300.

[0332] Figure 11A Examples include electronic device 100 (e.g., device 104, device 122, device 200, device 600, device 700, or device 800). In Figures 11A to 11CIn the non-limiting exemplary embodiment illustrated, electronic device 1100 is a smartphone. In other embodiments, electronic device 1100 may be different types of electronic devices, such as wearable devices (e.g., smartwatches, headsets), smart speakers, and / or set-top boxes. In some examples, electronic device 1100 has a display 1101, one or more input devices (e.g., a touchscreen, buttons, microphone of display 1101), and wireless communication radio components. In some examples, electronic device 1100 includes one or more forward-facing and / or rear-facing cameras. In some examples, the electronic device includes one or more biometric sensors, which optionally include cameras, such as infrared cameras, thermal imaging cameras, or combinations thereof.

[0333] exist Figure 11A When operating in hands-free mode, the electronic device 1100 displays a user interface 1110 on the display 1101, such as relative to... Figures 8A to 8J As described. As shown in the figure, the user interface 1110 includes one or more indicators, such as a calendar 1112 and a clock 1114. In some examples, the indicators of the user interface 1110 are configurable. For example, a user of the electronic device 1100 may optionally add any number of indicators to the user interface 1100 and / or remove any number of indicators from the user interface.

[0334] When user interface 1110 is displayed, electronic device 1100 (e.g., via microphone of electronic device 1100) receives user input 1110a. In some examples, user input 1110a is natural language voice input instructing a request directed to the digital assistant of electronic device 1100 (e.g., “Hey assistant, text Robert ‘hello’”). User input 1110a may include, for example, a voice trigger for activating the digital assistant (e.g., “Hey assistant”). In some examples, user input 1110a may include any request that may be directed to the digital assistant. By way of example, the statement “text Robert ‘hello’” in user input 1110a may request the digital assistant of electronic device 1100 to initiate a process for providing a message with specified message content (e.g., “hello”) to contact Robert.

[0335] In some examples, electronic device 1100 displays a digital assistant indicator 1118 to indicate that the digital assistant of electronic device 1100 is active (e.g., activated). For example, in response to receiving user input 1110a (recalling user input 1110a including voice triggering), electronic device 1100 may activate its digital assistant and display the digital assistant indicator 1118. In some examples, the digital assistant indicator 1118 overlays on user interface 1110 and is optionally positioned such that the digital assistant indicator 1118 does not interfere with the display of one or more objects on user interface 1110. In some examples, (e.g., using touch input) selection of the digital assistant indicator 1118 causes electronic device 1100 to perform one or more functions associated with the digital assistant. In at least one example, selection of the digital assistant indicator 1118 causes electronic device 1100 to stop any current operation performed by the digital assistant of the electronic device and optionally, resets the digital assistant of the electronic device to an initial state (e.g., a state where the digital assistant is ready to receive commands). Additionally or alternatively, in some examples, selecting the digital assistant indicator 1118 causes the electronic device 1100 to modify one or more visual characteristics of the digital assistant indicator 1118. Modifying visual characteristics in this way includes, for example, changing the color and / or size of the digital assistant indicator 1118 (e.g., reducing its size).

[0336] In response to user input 1110a, electronic device 1100 activates its digital assistant, and the digital assistant initiates the execution of a task corresponding to input 1110a.

[0337] In some examples, the execution of a task may require electronic device 1100 to perform (e.g., on one or more parameters) disambiguation. In the illustrated example, for instance, electronic device 1100 may not be able to determine which "Robert" in user input 1110a refers to (e.g., if the user has multiple contacts with the name "Robert," it may not be easy to discern which "Robert" is being referred to). In some examples, electronic device 1100 disambiguates by providing the user with a query. For example, see [reference]. Figure 11B The electronic device 1100 disambiguates "Robert" by displaying a user interface 1120 including multiple candidate contacts 1122 (e.g., candidate contacts 1122a to 1122e) and providing an output 1110b (e.g., natural language speech output) requesting the user to select the desired candidate contact 1122 ("Which Robert are you referring to?"). The user then selects a candidate contact, and the selected contact is used to perform the task.

[0338] User interface 1120 includes a digital assistant indicator 1118, which, when selected, causes electronic device 1100 to perform one or more functions associated with a digital assistant, as described. In some examples, the digital assistant indicator 1118 covers at least a portion of one or more candidate contacts 1122.

[0339] In some examples, the digital assistant indicator 1118 is selectively enabled. The digital assistant indicator 1118 may be selectively enabled, for example, based on a set of criteria (e.g., input criteria, enable criteria). In some examples, the input criteria include criteria satisfied when the electronic device 1100 detects a specific type of input (e.g., scroll input). In some examples, the input criteria include criteria satisfied when the electronic device 1100 detects input corresponding to a specific location and / or a specific direction of movement (e.g., an upward swipe gesture). In some examples, the input criteria include criteria satisfied when the electronic device 1100 detects input with at least a threshold duration. In some examples, the input criteria include criteria satisfied when the electronic device 1100 operates in hands-free mode, such as relative to... Figures 8A to 8J As described.

[0340] When enabled, the digital assistant indicator 1118 can be selected by a user using one or more inputs. In the illustrated example, for instance, electronic device 1110 may receive input (e.g., touch input 1120a) corresponding to the location of the digital assistant indicator 1118, and in response, electronic device 1100 performs one or more functions associated with the digital assistant, as described. When not enabled (e.g., disabled), the digital assistant indicator 1118 cannot be selected by a user.

[0341] Although Figure 11B Candidate contacts 1122a to 1122e are shown, but it should be understood that any number of candidate contacts may be provided, and additional candidate contacts may be displayed, for example, in response to one or more inputs (such as scroll input). For example, when user interface 1120 is displayed, electronic device 1100 detects input. In some examples, this input is a swipe gesture 1120b (e.g., an up swipe gesture). In response to detecting input 1120b, electronic device 1100 scrolls user interface 1120 in the direction corresponding to input 1120b, as shown. Figure 11C As shown. Because interface 1120 has been scrolled, candidate contacts 1122d and 1122e are displayed, and candidate contacts 1122a and 1122b are no longer displayed.

[0342] In some examples, input 1120b meets the set of criteria, and in response, electronic device 1100 disables digital assistant indicator 1118. In some examples, electronic device 1100 disables digital assistant indicator 1118 for a predetermined amount of time. In other examples, electronic device 1100 disables digital assistant indicator 1118 until electronic device 1100 receives another input. In some examples, disabling digital assistant indicator 1118 in this manner involves modifying one or more visual characteristics of digital assistant indicator 1118. As an example, electronic device 1100 may modify the size and / or color of digital assistant indicator 1118. As another example, electronic device 1100 may modify the contrast and / or brightness level of digital assistant indicator 1118. As yet another example, electronic device 1100 may modify the transparency level of digital assistant indicator 1118. Figure 11C In the interface 1120, the digital assistant indicator 1118 covers a portion of the candidate contact 1122g, and modifying the transparency level of the digital assistant indicator 1118 allows the covered portion of the candidate contact 1122g to be displayed in the user interface 1120.

[0343] As described, digital assistant indicator 1118 can be disabled in response to meeting this set of criteria, and because digital assistant indicator 1118 is disabled, the user can choose not to select it as long as it is disabled. In some examples, when digital assistant indicator 1118 is disabled, objects covered by digital assistant indicator 1118 can be selected (e.g., using input detected at the location corresponding to digital assistant indicator 1118). Reference Figure 11C For example, when the digital assistant indicator 1118 is disabled, the electronic device 1100 can detect input (e.g., touch input 1120b) at the location corresponding to the digital assistant indicator 1118. Because the digital assistant indicator 1118 is overlaid on the candidate contact 1122g, the electronic device determines that the input is a selection of the candidate contact 1122g. The selected candidate contact 1122g is then used to perform the task (e.g., sending a message to contact Robert).

[0344] Figure 12This is a flowchart of an exemplary process 1200 for performing a function, based on various examples. For example, process 1200 may be performed using one or more electronic devices implementing a digital assistant. In some examples, process 1200 may be performed using a client-server system (e.g., system 100), and the boxes of process 1200 may be divided in any way between a server (e.g., DA server 106) and client devices. In other examples, the boxes of process 1200 may be divided between a server and multiple client devices (e.g., mobile phones and smartwatches). Thus, while portions of process 1200 are described herein as being performed by a specific device of a client-server system, it should be understood that process 1200 is not limited thereto. In other examples, process 1200 may be performed using only client devices (e.g., user device 104) or only multiple client devices. In process 1200, some boxes may be optionally combined, the order of some boxes may be optionally changed, and some boxes may be optionally omitted. In some examples, additional steps may be performed in conjunction with process 1200.

[0345] In some embodiments, the electronic device (e.g., 1100) is a computer system (e.g., a personal electronic device (e.g., a mobile device (e.g., iPhone), tablet computer (e.g., iPad), smartwatch (e.g., Apple Watch), desktop computer (e.g., iMAC), or laptop computer (e.g., MacBook))) or a public electronic device (e.g., a smart TV (e.g., Apple TV) or smart speaker (e.g., HomePod))). The computer system optionally communicates with a display generating component (e.g., an integrated display and / or display controller) and with one or more input devices (e.g., a touch-sensitive surface (e.g., a touchscreen), a mouse, and / or a keyboard) (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as display via a CRT monitor, via an LED display, or via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0346] The computer system displays (1205) a user interface (e.g., 1110) including a user interface object (e.g., 1118) via the display generation component (e.g., 1101). In some examples, the user interface object corresponds to the computer system's digital assistant. In some examples, the user interface object is an object that is a graphical user interface object. In some examples, the user interface object is associated with a digital assistant and / or invokes digital assistant functions and / or applications when selected. In some examples, the user interface object overlays one or more other objects on the user interface. In some examples, the user interface object is positioned at a predetermined location on the user interface (e.g., at a specific corner and / or side of the user interface).

[0347] The computer system detects (1210) user input (e.g., tap input, scroll input) at a location corresponding to the user interface (e.g., a location within the user interface) via the one or more input devices (e.g., 1120a, 1120b).

[0348] Based on the determination that the user input meets a set of input criteria (1215), the computer system disables (1220) the user interface object. In some examples, the set of input criteria includes criteria that are met when the user input is a specific type of input (such as scroll input); additionally or alternatively, in some examples, the set of input criteria includes criteria that are met when the user input indicates one or more predetermined directions (e.g., up, down); additionally or alternatively, in some examples, the set of input criteria includes criteria that are met when the user input meets a threshold duration. In some examples, the user interface object is disabled in response to the detection of user input. In some examples, the user interface object is disabled in response to input of a predetermined type (e.g., scroll input). Based on the determination that the user input meets a set of input criteria (1215), the computer system modifies (1225) the visual characteristics of the user interface object (e.g., the visual characteristics of indicator 1118). In some examples, modifying the visual characteristics of the user interface object includes modifying the transparency and / or opacity of the user interface object. In some examples, modifying the visual characteristics of the user interface object includes modifying the brightness, contrast, and / or sharpness of the user interface object. In some examples, modifying the visual properties of user interface objects includes modifying the color, size, and / or shape of the user interface objects.

[0349] Based on the determination that the user input does not meet the set of input criteria (1230), the computer system abandons (1235) disabling the user interface object. Based on the determination that the user input does not meet the set of input criteria (1230), the computer system maintains (1240) the visual characteristics of the user interface object.

[0350] In some examples, after the user interface object is disabled, the computer system receives user input at the location corresponding to the user interface object. In some examples, the computer system detects input at the location of the user interface object within the user interface. In some examples, in response to receiving the user input, the computer system abandons the process of initiating an invocation of the digital assistant. In some examples, the user interface object corresponds to the digital assistant and, when enabled, causes the digital assistant to be invoked upon selection. In some examples, the user interface object does not cause the digital assistant to be invoked upon selection when disabled. In some examples, the user interface object is a first user interface object, and the user interface includes a second user interface object different from the first user interface object. In some examples, in response to receiving user input, the computer system performs a function associated with the second user interface object.

[0351] In some examples, the set of input criteria includes the requirement that the user input is scrolling input.

[0352] In some examples, disabling the user interface object includes disabling the user interface object for a predetermined amount of time. In some examples, the user interface object is disabled for a predetermined amount of time (e.g., 2 seconds). In some examples, the predetermined amount of time is measured from the end of the user input.

[0353] In some examples, the user interface corresponds to a third-party application. In other examples, the user interface corresponds to an application, such as a first-party application or a third-party application.

[0354] In some examples, modifying the visual properties of the user interface object includes modifying its transparency level.

[0355] In some examples, modifying the visual properties of the user interface object includes modifying the brightness level of the user interface object.

[0356] The above references Figure 12 The described operation is optionally determined by Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C as well as Figures 11A to 11C The components depicted herein are used for implementation. For example, the operation of process 1200 can be implemented by electronic device 800 and optionally a digital assistant executed thereon. Those skilled in the art will readily understand how to implement... Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C and Figures 11A to 11C The components described herein are used to implement other processes.

[0357] Figure 13This is a flowchart of an exemplary process 1300 for managing user interface objects, based on various examples. For example, process 1300 may be performed using one or more electronic devices implementing a digital assistant. In some examples, process 1300 may be performed using a client-server system (e.g., system 100), and the boxes of process 1300 may be divided in any way between a server (e.g., DA server 106) and client devices. In other examples, the boxes of process 1300 may be divided between a server and multiple client devices (e.g., mobile phones and smartwatches). Therefore, while portions of process 1300 are described herein as being performed by a specific device of a client-server system, it should be understood that process 1300 is not limited thereto. In other examples, process 1300 may be performed using only client devices (e.g., user device 104) or only multiple client devices. In process 1300, some boxes may be optionally combined, the order of some boxes may be optionally changed, and some boxes may be optionally omitted. In some examples, additional steps may be performed in conjunction with process 1300.

[0358] In some embodiments, the electronic device (e.g., 1100) is a computer system (e.g., a personal electronic device (e.g., a mobile device (e.g., iPhone), tablet computer (e.g., iPad), smartwatch (e.g., Apple Watch), desktop computer (e.g., iMAC), or laptop computer (e.g., MacBook))) or a public electronic device (e.g., a smart TV (e.g., Apple TV) or smart speaker (e.g., HomePod))). The computer system optionally communicates with a display generating component (e.g., an integrated display and / or display controller) and with one or more input devices (e.g., a touch-sensitive surface (e.g., a touchscreen), a mouse, and / or a keyboard) (e.g., wired communication, wireless communication). The display generating component is configured to provide visual output, such as display via a CRT monitor, via an LED display, or via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0359] The computer system displays (1305) a user interface (e.g., 1110) via the display generation component (e.g., 1101), which includes a user interface object (e.g., 1118) corresponding to the computer system's digital assistant. In some examples, the user interface object is an object that functions as a graphical user interface object. In some examples, the user interface object is associated with a digital assistant and / or invokes digital assistant functions and / or applications when selected. In some examples, the user interface object overlays one or more other objects on the user interface.

[0360] When the user interface is displayed, the computer system detects (1310) input (e.g., 1120a, 1120c) corresponding to the location of the user interface object via the one or more input devices. In some examples, when the user interface is displayed, the computer system receives (e.g., detects) user input at the location corresponding to the user interface object. In some examples, the user input is touch input on the display generating component and / or touch input detected using a touch-sensitive surface.

[0361] In response to the input (1315) corresponding to the location of the user interface object, the computer system executes (1320) a function (e.g., a task or part of a task) associated with the user interface object, based on the determination that a set of enable criteria are met for the user interface object. In some examples, the computer system determines whether a set of enable criteria are met for the user interface object. In some examples, the set of enable criteria are met if the user interface object is enabled and / or has not yet been disabled. In some examples, the user interface object is disabled while the user interface is scrolling and / or has been scrolling for a predetermined amount of time. In some examples, if the set of enable criteria are met, the computer system executes a function associated with the user interface object in response to the input.

[0362] In response to the input (1315) corresponding to the location of the user interface object, the computer system abandons (1325) performing the functions associated with the user interface object based on the determination that a set of enabling criteria are not met for the user interface object. In some examples, if the set of enabling criteria are not met (e.g., the user interface object is not enabled and / or is disabled), the computer system does not perform the functions associated with the user interface object in response to the input.

[0363] In some examples, the computer system determines whether the group's enablement criteria are met.

[0364] In some examples, the user interface object is a first user interface object. In some examples, the user interface includes a second user interface object at the location of the first user interface object (e.g., 1122e). In some examples, the first user interface object overlays the second user interface object. In some examples, when the set of enabling criteria is not met, the first user interface object is transparent, making the second user interface object at least partially visible. In some examples, in response to the input, based on the determination that a set of enabling criteria is not met for the user interface object, the computer system performs a function associated with the second user interface object. In some examples, if the set of enabling criteria is not met, input at the location of each of the first and second user interface objects causes the computer system to perform a function associated with the second user interface object.

[0365] In some examples, the computer system disables the user interface object based on a set of scrolling criteria before detecting input at that location. In other examples, the computer system abandons disabling the user interface object based on a set of scrolling criteria before detecting input at that location.

[0366] In some examples, the set of scrolling criteria includes requirements that must be met while the user interface is currently being scrolled. In some examples, the computer system disables the user interface object in response to a user scrolling the user interface, for example, using scroll input.

[0367] In some examples, the set of scrolling criteria includes requirements that must be met when the user interface has been scrolled over a threshold amount of time. In some examples, the computer system disables the user interface object in response to a user scrolling the user interface over a threshold amount of time (e.g., 4 seconds), for example, using scroll input.

[0368] In some examples, this set of rolling criteria includes requirements that must be met when the device is operated in hands-on mode.

[0369] In some examples, the computer system is configured to operate in the hands-on mode in response to detecting a user's approach to the computer system. In some examples, the computer system determines that the user is approaching the device when the user is within a certain distance of the computer system. In some examples, the computer system determines that the user is approaching the device when it detects the user's face. In some examples, the computer system determines that the user is approaching the computer system when it detects the faces of one or more pre-determined users (e.g., by authenticating the faces of the one or more pre-determined users). In some examples, the computer system determines that the user is approaching the device when it detects user input (such as touch input or gestures).

[0370] In some examples, disabling a user interface object involves modifying the visual properties of the user interface object. In some examples, when the user interface object is disabled, the computer system modifies one or more visual properties of the user interface object, for example, to indicate that the user interface object is disabled. In some examples, modifying visual properties in this way includes changing the transparency level, brightness level, and / or contrast level of the user interface object. In some examples, modifying visual properties in this way includes changing the size and / or color of the user interface object. In some examples, modifying visual properties in this way makes the user interface object less conspicuous relative to one or more other objects in the user interface. In some examples, the user interface object is overlaid on one or more other objects in the user interface, and the transparency of the user interface object is adjusted so that the one or more other objects are visible and / or more conspicuous in the user interface.

[0371] In some examples, modifying the visual properties of the user interface object includes dimming the user interface object. In some examples, dimming the user interface object includes increasing its transparency. In some examples, dimming the user interface object includes decreasing its brightness. In some examples, dimming the user interface object includes decreasing its contrast.

[0372] In some examples, modifying the visual properties of the user interface object includes increasing the transparency level of the user interface object (e.g., decreasing the opacity).

[0373] In some examples, modifying the visual properties of the user interface object includes changing the color of the user interface object, the size of the user interface object, or a combination thereof.

[0374] In some examples, the user interface corresponds to a third-party application. In other examples, the user interface corresponds to an application, such as a first-party application or a third-party application.

[0375] The above references Figure 13 The described operation is optionally determined by Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C as well as Figures 11A to 11C The components depicted herein are used for implementation. For example, the operation of process 1300 can be implemented by electronic device 800 and optionally a digital assistant executed thereon. Those skilled in the art will clearly understand how to implement... Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C and Figures 11A to 11C The components described herein are used to implement other processes.

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

[0377] According to some specific embodiments, an electronic device (e.g., a portable electronic device) is provided, which includes components for performing any of the methods or processes described herein.

[0378] According to some specific embodiments, an electronic device (e.g., a portable electronic device) is provided, the electronic device including a processing unit configured to perform any of the methods or processes described herein.

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

[0380] For purposes of explanation, the foregoing description has been given by reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible based on the teachings above. These embodiments were chosen and described in order to best explain the principles of these techniques and their practical application. Others skilled in the art will thus be able to best utilize these techniques and the various embodiments with various modifications suitable for the particular intended use.

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

[0382] As described above, one aspect of the present invention involves collecting and using data available from various sources to operate computer systems (and digital assistants running thereon) in various modes. This disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or can be used to contact or locate specific individuals. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records relating to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0383] This disclosure recognizes that the use of such personal information data in the techniques of this invention can be beneficial to users. For example, personal information data can be used to perform various tasks that require user-specific data (e.g., sending messages). Furthermore, this disclosure also contemplates other uses of personal information data that are beneficial to users. For example, health and fitness data can be used to provide insights into a user's overall health status or can be used as positive feedback for individuals using technology to pursue health goals.

[0384] This disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with robust privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to privacy policies and measures that are recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. These policies should be readily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for legitimate and reasonable entity purposes and should not be shared or sold outside of these legitimate purposes. Furthermore, such collection / sharing should be conducted only after receiving informed consent from users. Additionally, such entities should consider taking any necessary steps to protect and safeguard the right to access such personal information data and ensure that other entities with access to such personal information data comply with their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and privacy measures. Moreover, policies and measures should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including considerations of specific jurisdictions. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.

[0385] Regardless of the foregoing, this disclosure also anticipates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure anticipates providing hardware and / or software components to prevent or block access to such personal information data. For example, when operating a multimodal computer system, the technology of this invention can be configured to allow users to opt-in or opt-out at any time during or after registering for the service. In addition to providing "opt-in" and "opt-out" options, this disclosure also anticipates providing notifications related to access to or use of personal information. For example, users may be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0386] Furthermore, the intent of this disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by restricting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Where appropriate, deidentification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or characteristics of stored data (e.g., collecting location data at the city level rather than address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0387] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not become inoperable due to the absence of all or part of such personal information data. For example, operating modes and parameters for various tasks can be determined based on non-personal information data or an absolute minimum amount of personal information (such as content requested by a device associated with a user, other available non-personal information, or publicly available information).

Claims

1. A method comprising: at a computer system in communication with a display generation component and one or more input devices: while operating in a hands-free mode of operation, receiving a natural language voice input indicative of a task; in response to receiving the natural language voice input, initiating performance of the task; and providing an output corresponding to the task, wherein providing the output includes displaying a first user interface associated with an application, the first user interface being displayed in accordance with the hands-free mode of operation; while displaying the first user interface, receiving, via the one or more input devices, a touch input at a location corresponding to the first user interface; and in response to the touch input: transitioning from the hands-free mode of operation to a hands-on mode of operation that is different from the hands-free mode of operation; and launching the application, wherein launching the application includes displaying a second user interface in accordance with the hands-on mode of operation.

2. The method of claim 1, wherein: displaying a first user interface includes displaying a first user interface object at a first magnification; and displaying the second user interface includes displaying the first user interface object at a second magnification that is different from the first magnification.

3. The method of claim 2, wherein the first magnification is greater than the second magnification.

4. The method of claim 1, further comprising: determining whether a set of proximity criteria is satisfied; in accordance with a determination that the set of proximity criteria is satisfied, maintaining operation in the hands-on mode of operation; and in accordance with a determination that the set of proximity criteria is not satisfied, transitioning from the hands-on mode of operation to the hands-free mode of operation.

5. The method of claim 4, wherein transitioning from the hands-on mode of operation to the hands-free mode of operation includes displaying a third user interface associated with the application, wherein the third user interface is displayed in accordance with the hands-free mode of operation.

6. The method of claim 1, wherein the first user interface includes a second user interface object, and the second user interface includes the second user interface object.

7. The method of claim 1, wherein: the second user interface object corresponds to a digital assistant of the computer system, the first user interface includes the second user interface object at a first location, and displaying the second user interface includes: stopping display of the second user interface object at the first location; and displaying the second user interface object at a second location that is different from the first location.

8. The method of claim 1, wherein the first user interface includes a third user interface object that corresponds to the application, and receiving the touch input at the location corresponding to the first user interface includes receiving the touch input at a location corresponding to the third user interface object.

9. A computer system comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: ​ when operating in a hands-free mode of operation, receiving a natural language voice input indicative of a task; in response to receiving the natural language voice input, initiating performance of the task; and providing an output corresponding to the task, wherein providing the output includes displaying a first user interface associated with an application, the first user interface being displayed in accordance with the hands-free mode of operation; while displaying the first user interface, receiving, via the one or more input devices, a touch input at a location corresponding to the first user interface; and in response to the touch input: transitioning from the hands-free mode of operation to a hands-on mode of operation that is different from the hands-free mode of operation; and launching the application, wherein launching the application includes displaying a second user interface in accordance with the hands-on mode of operation.

10. The computer system of claim 9, wherein: displaying the first user interface includes displaying a first user interface object at a first magnification; and displaying the second user interface includes displaying the first user interface object at a second magnification that is different from the first magnification.

11. The computer system of claim 10, wherein the first magnification is greater than the second magnification.

12. The computer system of claim 9, wherein the one or more programs further include instructions for: determining whether a set of proximity criteria is satisfied; in accordance with a determination that the set of proximity criteria is satisfied, maintaining operation in the hands-on mode of operation; and in accordance with a determination that the set of proximity criteria is not satisfied, transitioning from the hands-on mode of operation to the hands-free mode of operation.

13. The computer system of claim 12, wherein transitioning from the hands-on mode of operation to the hands-free mode of operation includes displaying a third user interface associated with the application, wherein the third user interface is displayed in accordance with the hands-free mode of operation.

14. The computer system of claim 9, wherein the first user interface includes a second user interface object and the second user interface includes the second user interface object.

15. The computer system of claim 9, wherein: the second user interface object corresponds to a digital assistant of the computer system, the first user interface includes the second user interface object at a first location, and displaying the second user interface includes: stopping display of the second user interface object at the first location; and displaying the second user interface object at a second location that is different from the first location.

16. The computer system of claim 9, wherein the first user interface includes a third user interface object corresponding to the application, and receiving the touch input at the location corresponding to the first user interface includes receiving the touch input at a location corresponding to the third user interface object.

17. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system, the one or more programs including instructions for: when operating in a hands-free mode of operation, receiving a natural language voice input indicative of a task; in response to receiving the natural language voice input, initiating performance of the task; and providing an output corresponding to the task, wherein providing the output includes displaying a first user interface associated with an application, the first user interface being displayed in accordance with the hands-free mode of operation; while displaying the first user interface, receiving a touch input via the one or more input devices at a location corresponding to the first user interface; and in response to the touch input: transitioning from the hands-free mode of operation to a hands-on mode of operation that is different from the hands-free mode of operation; and launching the application, wherein launching the application includes displaying a second user interface in accordance with the hands-on mode of operation.

18. The non-transitory computer-readable storage medium of claim 17, wherein: displaying the first user interface includes displaying a first user interface object at a first magnification; and displaying the second user interface includes displaying the first user interface object at a second magnification that is different from the first magnification.

19. The non-transitory computer-readable storage medium of claim 18, wherein the first magnification is greater than the second magnification.

20. The non-transitory computer-readable storage medium of claim 17, wherein the one or more programs further include instructions for: determining whether a set of proximity criteria is satisfied; in accordance with a determination that the set of proximity criteria is satisfied, maintaining operation in the hands-on mode of operation; and in accordance with a determination that the set of proximity criteria is not satisfied, transitioning from the hands-on mode of operation to the hands-free mode of operation.

21. The non-transitory computer-readable storage medium of claim 20, wherein transitioning from the hands-on mode of operation to the hands-free mode of operation includes displaying a third user interface associated with the application, wherein the third user interface is displayed in accordance with the hands-free mode of operation.

22. The non-transitory computer-readable storage medium of claim 17, wherein the first user interface includes a second user interface object, and the second user interface includes the second user interface object.

23. The non-transitory computer-readable storage medium of claim 17, wherein: the second user interface object corresponds to a digital assistant of the computer system, the first user interface includes the second user interface object at a first location, and displaying the second user interface includes: stopping display of the second user interface object at the first location; and displaying the second user interface object at a second location that is different from the first location.

24. The non-transitory computer-readable storage medium of claim 17, wherein the first user interface includes a third user interface object that corresponds to the application, and receiving the touch input at the location corresponding to the first user interface includes receiving the touch input at a location corresponding to the third user interface object.

25. A computer system, the computer system comprising: means for performing the method of any of claims 1-8.

26. A computer program product, the computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for performing the method of any of claims 1-8.

Images