Device control using gaze information

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 62/739,087, entitled "DEVICE CONTROL USING GAZE INFORMATION," filed September 28, 2018, the entire contents of which are incorporated herein by reference.

The present disclosure relates generally to computer user interfaces, and more particularly to techniques for controlling electronic devices using gaze information.

Users often provide inputs, such as key presses and voice inputs, to control electronic devices. For example, users activate buttons on the device or speak trigger phrases to start applications on the device. Such inputs often require the user to be within reach or within range of a microphone.

Intelligent automated assistants (or digital assistants) can provide a useful interface between human users and electronic devices. Such assistants can enable users to interact with devices or systems using natural language in spoken and/or textual form. For example, a user can provide speech input containing a user request to a digital assistant running on an electronic device. The digital assistant can interpret the user's intent from the speech input, actuate the user's intent into a task, and perform the task. In some systems, performing a task in this manner can be constrained by the way the task is recognized. However, in some cases, a user is limited to a specific set of commands, and the user may not be able to easily instruct the digital assistant to perform a task using natural language speech input. Furthermore, in many cases, digital assistants are unable to adapt based on previous user behavior, similarly lacking desirable optimization of the user experience.

However, some techniques for controlling electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. In another example, some existing techniques require the user to be within arm's length to activate a button on the device. Existing techniques take longer than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

The present techniques thus provide electronic devices with faster and more efficient methods and interfaces for controlling the electronic device. Such methods and interfaces optionally complement or replace other methods for controlling electronic devices. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and extend the time between battery charges. Such techniques also enable users to more efficiently interact with electronic devices in environments where the user is not within reach of the electronic device and/or where the user is in a noisy environment (e.g., including audio-based noise being generated by the electronic device).

According to some embodiments, a method is provided. The method is executed on an electronic device. The method includes: acquiring first gaze information using one or more camera sensors while a digital assistant of the electronic device is not activated; activating the digital assistant of the electronic device according to a determination that the first gaze information satisfies a set of one or more activation criteria; and providing an indication that the set of one or more activation criteria has been met.

According to some embodiments, a non-transitory computer-readable storage medium is provided. The medium stores one or more programs configured to be executed by one or more processors of an electronic device. The one or more programs include instructions for acquiring first gaze information using one or more camera sensors while a digital assistant of the electronic device is not activated, instructions for activating the digital assistant of the electronic device according to a determination that the first gaze information satisfies a set of one or more activation criteria, and instructions for providing an indication that the set of one or more activation criteria has been met.

According to some embodiments, a temporary computer-readable storage medium is provided. The medium stores one or more programs configured to be executed by one or more processors of an electronic device. The one or more programs include instructions for acquiring first gaze information using one or more camera sensors while a digital assistant of the electronic device is not activated, instructions for activating the digital assistant of the electronic device according to a determination that the first gaze information satisfies a set of one or more activation criteria, and instructions for providing an indication that the set of one or more activation criteria has been met.

According to some embodiments, an electronic device is provided, the electronic device comprising: 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 acquiring first gaze information using one or more camera sensors while a digital assistant of the electronic device is not activated; instructions for activating the digital assistant of the electronic device according to a determination that the first gaze information satisfies a set of one or more activation criteria; and instructions for providing an indication that the set of one or more activation criteria is satisfied.

According to some embodiments, an electronic device is provided, comprising: means for acquiring first gaze information using one or more camera sensors while a digital assistant of the electronic device is not activated; and means for activating the digital assistant of the electronic device according to a determination that the first gaze information satisfies a set of one or more activation criteria and providing an indication that the set of one or more activation criteria has been met.

According to some embodiments, a method is provided, the method being executed on an electronic device, that includes receiving, while a first external device is in a first state, a voice user input request to execute a first command, acquiring first gaze information using one or more camera sensors, and, pursuant to determining, using the first gaze information, that a set of one or more gaze criteria are satisfied for the first external device, transmitting, based on the first command, an instruction to transition the first external device from the first state to a second state.

According to some embodiments, a non-transitory computer-readable storage medium is provided. The medium stores one or more programs configured to be executed by one or more processors of an electronic device. The one or more programs include instructions for receiving a voice user input request to execute a first command while a first external device is in a first state, instructions for acquiring first gaze information using one or more camera sensors, and instructions for transmitting an instruction to transition the first external device from the first state to a second state based on the first command in accordance with determining, using the first gaze information, that a set of one or more gaze criteria has been met for the first external device.

According to some embodiments, a temporary computer-readable storage medium is provided, the medium storing one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for receiving a voice user input request to execute a first command while a first external device is in a first state, instructions for acquiring first gaze information using one or more camera sensors, and instructions for transmitting an instruction to transition the first external device from the first state to a second state based on the first command in accordance with determining, using the first gaze information, that a set of one or more gaze criteria has been met for the first external device.

According to some embodiments, an electronic device is provided, comprising: 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 receiving, while a first external device is in a first state, a voice user input request to perform a first command, instructions for acquiring, using one or more camera sensors, first gaze information, and, pursuant to determining, using the first gaze information, that a set of one or more gaze criteria is satisfied for the first external device, transmitting, based on the first command, an instruction to transition the first external device from the first state to a second state.

According to some embodiments, an electronic device is provided, comprising: means for receiving a voice user input request to execute a first command while a first external device is in a first state, acquiring first gaze information using one or more camera sensors, and means for transmitting an instruction to transition the first external device from the first state to a second state based on the first command in accordance with a determination using the first gaze information that a set of one or more gaze criteria has been met for the first external device.

According to some embodiments, a method is provided, the method being performed on an electronic device, and including: receiving a vocal request for user input; updating a value of a characteristic of an indicator to a first value corresponding to the first user in accordance with a determination that the vocal request for user input corresponds to a first user; updating a value of the characteristic of the indicator to a second value corresponding to the second user, the second value being different from the first value, in accordance with a determination that the vocal request for user input corresponds to a second user different from the first user; and responding to the vocal request for user input using an indicator including the updated value of the characteristic.

According to some embodiments, a non-transitory computer-readable storage medium is provided. The medium stores one or more programs configured to be executed by one or more processors of an electronic device. The one or more programs include instructions for receiving a vocal user input request; updating a value of a characteristic of an indicator to a first value corresponding to the first user in accordance with a determination that the vocal user input request corresponds to a first user; updating a value of the characteristic of the indicator to a second value corresponding to the second user, the second value being different from the first value, in accordance with a determination that the vocal user input request corresponds to a second user different from the first user; and responding to the vocal user input request with an indicator including the updated value of the characteristic.

According to some embodiments, a transient computer-readable storage medium is provided. The medium stores one or more programs configured to be executed by one or more processors of an electronic device. The one or more programs include instructions for receiving a vocal user input request; updating a value of a characteristic of an indicator to a first value corresponding to the first user in accordance with a determination that the vocal user input request corresponds to a first user; updating a value of the characteristic of the indicator to a second value corresponding to the second user, the second value being different from the first value, in accordance with a determination that the vocal user input request corresponds to a second user different from the first user; and responding to the vocal user input request with an indicator including the updated value of the characteristic.

According to some embodiments, an electronic device is provided, comprising: 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 receiving a vocal user input request; updating a value of a characteristic of an indicator to a first value corresponding to the first user in accordance with a determination that the vocal user input request corresponds to a first user; updating a value of the characteristic of the indicator to a second value corresponding to the second user, the second value being different from the first value, in accordance with a determination that the vocal user input request corresponds to a second user different from the first user; and responding to the vocal user input request with an indicator including the updated value of the characteristic.

According to some embodiments, an electronic device is provided, comprising: means for receiving a vocal user input request; means for updating a value of a characteristic of an indicator to a first value corresponding to the first user in accordance with a determination that the vocal user input request corresponds to a first user; means for updating a value of a characteristic of the indicator to a second value different from the first value in accordance with a determination that the vocal user input request corresponds to a second user different from the first user; and means for responding to the vocal user input request with an indicator, the indicator including the updated value of the characteristic.

Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

As such, the device provides faster and more efficient methods and interfaces for controlling electronic devices, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for controlling electronic devices.

For a better understanding of the various described embodiments, reference should be made to the following Detailed Description of the Invention in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

<figref num="1A">1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.</figref>

<figref num="1B">FIG. 2 is a block diagram illustrating exemplary components for event processing according to some embodiments.</figref>

<figref num="1C">FIG. 1 is a block diagram illustrating a system and environment for implementing a digital assistant according to some embodiments.</figref>

<figref num="2">FIG. 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.</figref>

<figref num="3">FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.</figref>

<figref num="4A">1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.</figref>

<figref num="4B">1A-1C illustrate exemplary user interfaces for a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.</figref>

<figref num="5A">FIG. 1 illustrates a personal electronic device according to some embodiments.</figref>

<figref num="5B">FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.</figref>

<figref num="6A">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6B">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6C">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6D">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6E">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6F">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6G">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6H">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6I">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6J">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6K">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6L">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6M">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6N">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref><figref num="6O">1 illustrates an example technique for using gaze information to activate a digital assistant.</figref>

<figref num="7A">FIG. 1 is a flow diagram illustrating a method for using gaze information to activate a digital assistant.</figref><figref num="7B">FIG. 1 is a flow diagram illustrating a method for using gaze information to activate a digital assistant.</figref>

<figref num="8A">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8B">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8C">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8D">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8E">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8F">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8G">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8H">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8I">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8J">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8K">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref><figref num="8L">1 illustrates an exemplary technique for using gaze information to provide context to commands.</figref>

<figref num="9A">FIG. 10 is a flow diagram illustrating a method for using gaze information to provide context to commands.</figref><figref num="9B">FIG. 10 is a flow diagram illustrating a method for using gaze information to provide context to commands.</figref>

<figref num="10A">1 illustrates an exemplary technique for providing indications that distinguish between different speakers.</figref><figref num="10B">1 illustrates an exemplary technique for providing indications that distinguish between different speakers.</figref><figref num="10C">1 illustrates an exemplary technique for providing indications that distinguish between different speakers.</figref><figref num="10D">1 illustrates an exemplary technique for providing indications that distinguish between different speakers.</figref>

<figref num="11A">FIG. 1 is a flow diagram illustrating a method for providing indications that distinguish between different speakers.</figref><figref num="11B">FIG. 1 is a flow diagram illustrating a method for providing indications that distinguish between different speakers.</figref>

The following description sets forth example methods, parameters, etc. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but rather is provided as a description of example embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for controlling electronic devices. For example, eliminating or reducing the need for a user to provide tactile or verbal input to activate a digital assistant allows the user to more effectively control the electronic device. In another example, identifying an external device through a user's gaze eliminates or reduces the need to provide context and complex, time-consuming user input to identify such a device. Such techniques can reduce the cognitive burden on users controlling electronic devices, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

1A-1C, 2, 3, 4A-4B, and 5A-5B provide a description of an exemplary device for performing techniques for controlling an electronic device. FIGS. 6A-6O illustrate exemplary user interfaces for activating a digital assistant using gaze information. FIGS. 7A-7B are flow diagrams illustrating a method for activating a digital assistant using gaze information, according to some embodiments. The user interfaces of FIGS. 6A-6O are used to illustrate processes described below, including the processes of FIGS. 7A-7B. FIGS. 8A-8L illustrate exemplary user interfaces for providing context to commands using gaze information. FIGS. 9A-9B are flow diagrams illustrating a method for providing context to commands using gaze information, according to some embodiments. The user interfaces of FIGS. 8A-8L are used to illustrate processes described below, including the processes of FIGS. 9A-9B. FIGS. 10A-10D illustrate exemplary user interfaces for providing instructions to distinguish between different speakers. 11A-11B are flow diagrams illustrating a method for providing instructions to distinguish between different speakers, according to some embodiments. The user interfaces of FIGS. 10A-10D are used to illustrate the processes described below, including the process of FIGS. 11A-11B.

In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch, without departing from the scope of the various embodiments described. Although a first touch and a second touch are both touches, they are not the same touch.

The terminology used in the description of various embodiments set forth herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various embodiments set forth and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Also, as used herein, the term "and/or" should be understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and/or "comprising," as used herein, specify the presence of 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.

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

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and/or touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and/or touchpad).

In the following discussion, electronic devices are described that include a display and a touch-sensitive surface. However, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

Various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or changed for each application and/or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications, including user interfaces that are intuitive and transparent to the user.

Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112, according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

As used herein and in the claims, the term intensity of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and/or change in the contact area detected on the touch-sensitive surface, the capacitance and/or change in the capacitance of the touch-sensitive surface proximate the contact, and/or the resistance and/or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure of the contact force or pressure is converted to an estimate of the force or pressure, and the estimate of the force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows users to access additional device functionality that may not otherwise be accessible to them on devices of reduced size with limited footprint, to display affordances (e.g., on a touch-sensitive display) and/or to receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical control such as a knob or button).

As used herein and in the claims, the term tactile output refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a user's touch-sensitive surface (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of the touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a downclick or upclick of a physical actuator button. In some cases, a user feels a tactile sensation such as a downclick or upclick even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of a device, or a component of a device, that produces the described sensory perception for a typical (or average) user.

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

Memory 102 optionally includes high-speed random access memory, and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and/or instruction sets stored in memory 102 to perform various functions and process data for device 100. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates with the Internet, also called the World Wide Web (WWW), an intranet, and/or a cellular telephone network, a wireless local area network (LAN), and/or a metropolitan area network (MEN). The RF circuitry 108 communicates with networks, such as wireless networks such as Mobile Access Networks (MANs), and with other devices via wireless communications. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range radios. The wireless communications are optionally supported by, but are not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (Dual-Cell HSPA), and other wireless technologies. HSPA, DC-HSPA, long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP)), 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 Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMSP) The present invention may use any of a number of communication standards, protocols, and technologies, including SMS (Speech Processing Service), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and/or transmitted to memory 102 and/or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and a detachable audio input/output peripheral, such as an output-only headphone or a headset with both an output (e.g., mono or binaural headphones) and an input (e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I/O subsystem 106 optionally includes display controller 156, light sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive/send electrical signals from/to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, input controller 160 is optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up/down buttons for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2).

As described in U.S. Patent Application No. 11/322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety, a quick press of a push button optionally unlocks touchscreen 112 or, optionally, initiates the process of unlocking the device using gestures on the touchscreen. A longer press of a push button (e.g., 206) optionally turns power on or off to device 100. The functionality of one or more of the buttons is optionally customizable by the user. Touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and/or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, animation, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.

Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and/or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and/or instruction sets in memory 102) detects contacts (and any movement or cessation of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more softkeys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the user's finger.

Touchscreen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally detect contact and any movement or disruption thereof using any of a number of now known or later developed touch sensing technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch-sensing touchpad described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication No. 2002/0015024 A1, each of which is incorporated by reference herein in its entirety. However, touchscreen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

Touch-sensitive displays in some embodiments of touchscreen 112 are described in the following applications:

(1) U.S. patent application Ser. No. 11/381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller"; (2) U.S. patent application Ser. No. 10/840,862, filed May 6, 2004, entitled "Multipoint Touchscreen"; (3) U.S. patent application Ser. No. 10/903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices"; (4) U.S. patent application Ser. No. 11/048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices"; (5) U.S. patent application Ser. No. 11/038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input"; "Virtual Input Device Placement On A Touch Screen User Interface," (6) U.S. Patent Application No. 11/228,758, filed September 16, 2005, (7) U.S. patent application Ser. No. 11/228,700, filed Sep. 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) U.S. patent application Ser. No. 11/228,737, filed Sep. 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. patent application Ser. No. 11/367,749, filed Mar. 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entirety.

Touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to operate primarily using finger-based contact and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touchscreen. In some embodiments, the device translates the coarse finger input into precise pointer/cursor positions or commands to perform the action desired by the user.

In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad for activating or deactivating certain 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 optionally a touch-sensitive surface separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with generating, managing, and distributing electrical power within a portable device.

Device 100 also optionally includes one or more light sensors 164. Figure 1A shows a light sensor coupled to a light sensor controller 158 in I/O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CCD). The optical sensor 164 includes a CMOS (complementary metal-oxide semiconductor) phototransistor. The optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. The optical sensor 164 optionally works in conjunction with the imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the optical sensor is located on the back of the device 100 opposite the touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for still image and/or video capture. In some embodiments, the optical sensor is located on the front of the device so that an image of the user is optionally captured for video conferencing while the user views other video conference participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single optical sensor 164 is used for both video conferencing and still image and/or video capture, along with the touchscreen display.

Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I/O subsystem 106. Depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 is optionally used to determine a depth map of various portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 to obtain images of the user with depth information for videoconferences and to capture selfie images with depth map data while the user views other videoconference participants on a touchscreen display. In some embodiments, depth camera sensor 175 is located on the back of the device or on both the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that the depth camera sensor 175 is used for both video conferencing and capturing still images and/or video, along with a touchscreen display.

In some embodiments, a depth map (e.g., a depth map image) contains information (e.g., values) about the distance of objects in a scene from a viewpoint (e.g., a camera, light sensor, depth camera sensor). In one embodiment of a depth map, each depth pixel defines a position on the Z axis of the viewpoint where its corresponding two-dimensional pixel is located. In some embodiments, the depth map is made up of pixels, each defined by a value (e.g., 0 to 255). For example, a value of "0" represents a pixel located furthest in a "3D" scene, and a value of "255" represents a pixel located closest to the viewpoint (e.g., a camera, light sensor, depth camera sensor) in the "3D" scene. In other embodiments, the depth map represents the distance between objects in a scene and the plane of the viewpoint. In some embodiments, the depth map contains information about the relative depth of various features of an object of interest as seen by a depth camera (e.g., the relative depth of the eyes, nose, mouth, and ears on a user's face). In some embodiments, the depth map contains information that allows the device to determine the contours in the z-direction of the object of interest.

Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

Device 100 also optionally includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 within I/O subsystem 106. Proximity sensor 166 may optionally be coupled to one or more proximity sensors 166, as described in U.S. patent applications Ser. Nos. 11/241,839, "Proximity Detector In Handheld Device," 11/240,788, "Proximity Detector In Handheld Device," 11/620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output," 11/586,862, "Automated Response To And Sensing Of User Activity In Portable Devices," and 11/638,251, "Methods And Systems For Automatic Configuration Of Peripherals." In some embodiments, when the multifunction device is placed near a user's ear (e.g., when the user is making a phone call), the proximity sensor turns off and disables touchscreen 112.

Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and/or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates tactile outputs by moving the touch-sensitive surface vertically (e.g., in/out of the surface of device 100) or horizontally (e.g., back and forth within the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 is optionally coupled to an input controller 160 in I/O subsystem 106, as described in 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 On An In some embodiments, information is displayed on the touchscreen display in portrait or landscape orientation based on an analysis of data received from one or more accelerometers. In addition to accelerometer 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the location and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a touch/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 136, a GPS module (or instruction set) 138, a GPS receiver (or instruction set) 139, a GPS receiver (or instruction set) 140, a GPS receiver (or instruction set) 141, a GPS receiver (or instruction set) 142, a GPS receiver (or instruction set) 143, a GPS receiver (or instruction set) 144, a GPS receiver (or instruction set) 145, a GPS receiver (or instruction set) 146, a GPS receiver (or instruction set) 147, a GPS receiver (or instruction set) 148, a GPS receiver (or instruction set) 149, a GPS receiver (or instruction set) 150, a GPS receiver (or instruction set) 151, a GPS receiver (or instruction set) 152, a GPS receiver (or instruction set) 153, a GPS receiver (or instruction set) 154, a GPS receiver (or instruction set) 155, a GPS receiver (or instruction set) 156, a GPS receiver (or instruction set) 157, a GPS receiver (or instruction set) 158, a GPS receiver (or instruction set) 159, a GPS receiver (or instruction set) 160, a GPS receiver (or instruction set) 161, a GPS receiver (or instruction set) 162, a GPS receiver (or instruction set) 163, a GPS receiver (or instruction set) 164, a GPS receiver (or instruction set) 165, a GPS receiver (or instruction set) 166, a GPS receiver (or instruction set) 167, a GPS receiver (or instruction set) 168, a GPS receiver (or instruction set) 1 1A and 3, includes a GPS (Global Positioning System) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/global internal state 157, as shown in FIGS. 1A and 3. Device/global internal state 157 includes one or more of an active application state indicating which applications, if any, are currently active; a display state indicating which applications, views, or other information occupy various regions of touchscreen display 112; a sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and/or orientation.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers that control and manage general system tasks (e.g., memory management, storage control, power management, etc.) and facilitate communication between various hardware and software components.

Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for direct coupling to other devices or indirect coupling via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, similar to, and/or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130, optionally in cooperation with display controller 156, detects contact with touchscreen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is contact movement and tracking the movement across 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-up event or an interruption of the contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the contact point. These actions are optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contacts on the touchpad.

In some embodiments, contact/motion module 130 uses one or more sets of intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has clicked on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator, but can be adjusted without modifying the physical hardware of device 100). For example, the mouse click threshold of a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without modifying the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting multiple intensity thresholds at once via a system-level click intensity parameter).

Contact/motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and/or strength of the detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphic" includes any object that 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, video, animation, etc.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying a graphic to be displayed, including coordinate data and other graphic characteristic data as needed, from an application or the like, and then generates screen image data to output to display controller 156.

The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator 167, which generates tactile outputs at one or more locations on the device 100 in response to a user's interaction with the device 100.

Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based dialing, to the camera 143 as photo/video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map/navigation widgets).

Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof:

Contacts module 137 (sometimes called an address book or contact list), Telephone module 138, Videoconferencing module 139, Email client module 140, Instant messaging a video and music player module 149-6; a search module 151; a video and music player module 152; a training support module 142; a camera module 143 for still images and/or video; an image management module 144; a video player module; a music player module; a browser module 147; a calendar module 148; a widget module 149 optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, and user-created widgets 149-6; a widget creator module 150 for creating user-created widgets 149-6; a search module 151; a video and music player module 152 integrating a video player module and a music player module; a notes module 153; a maps module 154; and/or an online video module 155.

Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

Contacts module 137, in conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, is optionally used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), which may include adding names to the address book, removing name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and/or facilitate communication by telephone 138, videoconferencing module 139, email 140, or IM 141, etc.

Telephone module 138, in conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, place calls, and disconnect and hang up when the call is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

Videoconferencing module 139 includes executable instructions to cooperate with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, light sensor 164, light sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138 to initiate, conduct, and end a videoconference between a user and one or more other participants according to the user's instructions.

Email client module 140 includes executable instructions for coordinating with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134 to create, send, receive, and manage emails in response to user instructions. Email client module 140 also cooperates with image management module 144 to greatly facilitate the creation and sending of emails that include still or video images captured by camera module 143.

Instant messaging module 141 includes executable instructions, in cooperation with RF circuitry 108, touchscreen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, for inputting character sequences corresponding to instant messages, modifying previously input characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and/or received instant messages are optionally transmitted using MMS and/or Enhanced Messaging Service (EMS) protocols. This includes graphics, photos, audio files, video files, and/or other attachments such as those supported by the Instant Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

The training support module 142 includes executable instructions to cooperate with the RF circuitry 108, touchscreen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module to create workouts (e.g., with time, distance, and/or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor workouts, select and play music for workouts, and display, store, and transmit workout data.

Camera module 143, in conjunction with touchscreen 112, display controller 156, light sensor 164, light sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying the characteristics of the still images or video, or deleting the still images or video from memory 102.

Image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still and/or video images in conjunction with touchscreen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143.

Browser module 147, in conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet according to user directions, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

Calendar module 148 includes executable instructions to cooperate with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147 to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) according to user instructions.

Widget module 149, in conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch/motion module 130, graphics module 132, text input module 134, and browser module 147, optionally provides mini-applications (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) downloaded and used by a user, or mini-applications (e.g., user-created widget 149-6) created by a user. In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file. Language (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! Widgets).

The widget creator module 150, in conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the text input module 134, and the browser module 147, is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

The search module 151 includes executable instructions for working in conjunction with the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, and the text input module 134 to search for text, music, sound, images, video, and/or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

Video and music player module 152 includes executable instructions that, in conjunction with touchscreen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, enable a user to download and play pre-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 videos (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

The notes module 153 includes executable instructions for working with the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, and the text input module 134 to create and manage notes, to-do lists, and the like as directed by a user.

Map module 154, in conjunction with RF circuitry 108, touchscreen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, is used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data about businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.

Online video module 155, in conjunction with touchscreen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, contains instructions that enable a user to access, browse for, receive (e.g., by streaming and/or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. For additional description of online video applications, see 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 entireties.

The above-identified modules and applications each correspond to sets of executable instructions that perform one or more of the functions previously described and methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed solely via a touchscreen and/or touchpad. Using the touchscreen and/or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

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

1B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., within operating system 126) and a respective application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).

Event sorter 170 receives the event information and determines application 136-1 and application view 191 of application 136-1 to which to send the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view that is displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is currently active, and application internal state 192 is used by event sorter 170 to determine application view 191 to which the event information is sent.

In some embodiments, application internal state 192 includes additional information such as one or more of resume information to be used when application 136-1 resumes execution, user interface state information indicating information being displayed or ready to be displayed by application 136-1, state cues that allow the user to return to a previous state or view of application 136-1, and redo/undo cues for previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch as part of a multi-touch gesture on touch-sensitive display 112). Peripherals interface 118 communicates information received from I/O subsystem 106 or from sensors such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (via audio circuitry 110). The information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input above a predetermined noise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173 .

Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

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

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

Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-events are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 transmits the event information to the event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores the event information obtained by each event receiver 182 in an event queue.

In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In still other embodiments, event sorter 170 is a stand-alone module or is part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other attributes. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of metadata 183 and event transmission instructions 188 (optionally including sub-event transmission instructions).

Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves a movement of a touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's attitude).

The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events within an event (187) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object relative to a predetermined phase (touch start), a first lift-off (touch end) relative to the predetermined phase, a second touch on a displayed object relative to the predetermined phase (touch start), and a second lift-off (touch end) relative to the predetermined phase. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) on the displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, if a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

In some embodiments, each event 187 definition also includes a delay action that delays transmission of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event-disabled, event-failed, or event-ended state and thereafter ignores subsequent sub-events for the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events for the ongoing touch-based gesture.

In some embodiments, each event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate to actively participating event recognizers how the event transmission system should perform sub-event transmission. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact with each other or are enabled to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are transmitted to various levels in the view or programmatic hierarchy.

In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 transmits event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) sub-events to the respective hit view. In some embodiments, the event recognizer 180 sets a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predetermined process.

In some embodiments, the event transmission instructions 188 include sub-event transmission instructions that transmit event information about a sub-event without activating an event handler. Instead, the sub-event transmission instructions transmit the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs predetermined processing.

In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, although not all of them are initiated on the touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movement, biometric input, and/or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define a recognized event.

1C illustrates a block diagram of a system 2100 according to various embodiments. In some embodiments, the system 2100 implements a digital assistant. The terms digital assistant,virtual assistant,intelligent automated assistant, or automated digital assistant refer to any information processing system that infers user intent by interpreting natural language input in spoken and/or textual form and performs actions based on the inferred user intent. For example, to act based on the inferred user intent, the system may perform one or more of: identifying a task flow having steps and parameters designed to realize the inferred user intent; inputting specific requirements from the inferred user intent into the task flow; executing the task flow by invoking a program, method, service, API, or the like; and generating an output response to the user in audible (e.g., spoken) and/or visual form.

Specifically, a digital assistant can accept user requests, at least in part, in the form of natural language commands, requests, opinions, discourse, and/or queries. Typically, a user request seeks either an informational answer or the performance of a task by the digital assistant. A satisfactory response to a user request includes providing the requested informational answer, performing the requested task, or a combination of the two. For example, a user may ask a digital assistant, "Where am I right now?" The digital assistant may ask a question such as, "Where are you now?" Based on the user's current location, the digital assistant may respond, "You are in Central Park near the West Gate." The user may also request a task to be performed, such as, "Please invite my friends to my girlfriend's birthday party next week." In response, the digital assistant may acknowledge the request by stating, "Yes, right now," and then send appropriate calendar invitations on behalf of the user to each of the user's friends listed in the user's electronic address book. During the performance of a requested task, the digital assistant may interact with the user in a continuous conversation involving multiple information exchanges over time. There are numerous other ways to interact with a digital assistant to request information or the performance of various tasks. In addition to providing verbal responses and taking programmed actions, digital assistants also provide responses in other visual or audio formats, such as text, alerts, music, video, animation, etc.

1C , in some embodiments, the digital assistant is implemented according to a client-server model. The digital assistant includes a client-side portion 2102 (hereinafter, "DA client 2102") that runs on user device 104 and a server-side portion 2106 (hereinafter, "DA server 2106") that runs on server system 2108. DA client 2102 communicates with DA server 2106 over one or more networks 2110. DA client 2102 provides client-side functionality, such as user-responsive input and output processing and communication with DA server 2106. DA server 2106 provides server-side functionality to any number of DA clients 2102, each resident on a respective user device 2104.

In some embodiments, the DA server 2106 includes a client-facing I/O interface 2112, one or more processing modules 2114, data and models 2116, and an I/O interface to external services 2118. The client-facing I/O interface 2112 facilitates client-facing input and output processing of the DA server 2106. The one or more processing modules 2114 utilize the data and models 2116 to process speech input and determine user intent based on natural language input. Furthermore, the one or more processing modules 2114 perform task execution based on the inferred user intent. In some embodiments, the DA server 2106 communicates with external services 120 over network(s) 2110 to complete tasks or obtain information. The I/O interface to external services 2118 facilitates such communication.

User device 2104 can be any suitable electronic device. In some examples, user device 2104 is a portable multifunction device (e.g., device 100 described above with reference to FIG. 1A), a multifunction device, or a portable multifunction device (e.g., devices 600, 800, 1000). A portable multifunction device is, for example, a mobile phone that also includes other functions, such as PDA and/or music player functionality. Examples of portable multifunction devices include the Apple Watch®, iPhone®, and iPod® by Apple Inc. (Cupertino, California). Touch®, and iPad® devices. Other examples of portable multifunction devices include, but are not limited to, earphones/headphones, speakers, and laptop or tablet computers. Furthermore, in some examples, user device 2104 is a non-portable multifunction device. Specifically, user device 2104 is a desktop computer, a game console, a speaker, a television, or a television set-top box. In some examples, user device 2104 includes a touch-sensitive surface (e.g., a touchscreen display and/or a touchpad). Furthermore, user device 2104 optionally includes one or more other physical user interface devices, such as a physical keyboard, a mouse, and/or a joystick. Various examples of electronic devices, such as multifunction devices, are described in further detail below.

Examples of the communication network(s) 2110 include a local area network (LAN) and a wide area network (WAN), such as the Internet. The communication network(s) 2110 may be, for example, 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), and the like. It may be implemented using any known network protocol, including various wired or wireless protocols, such as VoIP (Voice over IP) Protocol, Wi-MAX, or any other suitable communication protocol.

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

In some embodiments, the user device 2104 communicates with the DA server 2106 via a second user device 2122. The second user device 2122 is similar to or identical to the user device 2104. The user device 2104 is configured to be communicatively coupled to the second user device 2122 via a direct communication connection, such as Bluetooth, NFC, or BTLE, or via a wired or wireless network, such as a local Wi-Fi network. In some embodiments, the second user device 2122 is configured to act as a proxy between the user device 2104 and the DA server 2106. For example, the DA client 2102 of the user device 2104 is configured to send information (e.g., a user request received at the user device 2104) to the DA server 2106 via the second user device 2122. The DA server 2106 processes the information and returns relevant data (e.g., data content responsive to the user request) to the user device 2104 via the second user device 2122.

In some embodiments, the user device 2104 is configured to reduce the amount of information transmitted from the user device 2104 by communicating an abbreviated request for data to the second user device 2122. The second user device 2122 is configured to determine supplemental information to add to the abbreviated request and generate a complete request to transmit to the DA server 2106. This system architecture can advantageously allow a user device 2104 (e.g., a watch or similar small electronic device) with limited communication capabilities and/or limited battery power to access services provided by the DA server 2106 by using a second user device 2122 (e.g., a mobile phone, laptop computer, tablet computer, etc.) with greater communication capabilities and/or battery power as a proxy to the DA server 2106. While only two user devices 2104 and 2122 are shown in FIG. 1C , it should be understood that the system 2100, in some embodiments, includes any number and type of user devices configured to communicate with the DA server system 2106 in this proxy configuration.

1C includes both a client-side portion (e.g., DA client 2102) and a server-side portion (e.g., DA server 2106), although in some examples, the digital assistant's functionality is implemented as an independent application installed on a user device. Furthermore, the allocation of functionality between the client and server portions of the digital assistant may vary depending on the implementation. For example, in some embodiments, the DA client is a thin client that provides only user-facing input and output processing functionality and delegates all other digital assistant functionality to a back-end server.

2 illustrates portable multifunction device 100 having touchscreen 112, according to some embodiments. The touchscreen optionally displays a user interface. Device 100 displays one or more graphics within a UI (user interface, UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and/or downward), and/or rolling (right to left, left to right, upward and/or downward) of a finger in contact with device 100. In some implementations or situations, accidental contact with a graphic does not select the graphic. For example, optionally, a swipe gesture sweeping over an application icon does not select the corresponding application if the gesture corresponding to selection is a tap.

Device 100 also optionally includes one or more physical buttons, such as a "home" button or menu button 204. As previously mentioned, menu button 204 is optionally used to navigate to any application 136 within a set of applications running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touchscreen 112.

In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbuttons 206 for powering the device on/off and locking the device, volume control buttons 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking/charging port 124. Pushbutton 206 is optionally used to power the device on/off by pressing and holding the button down for a predetermined time interval, to lock the device by pressing and releasing the button before the predetermined time interval has elapsed, and/or to unlock the device or initiate the unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and/or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes input/output (I/O) interface 330, including display 340, which is typically a touchscreen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A ) that generates tactile output on device 300, and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and/or contact intensity sensors similar to contact intensity sensor 165 described above with reference to FIG. 1A ). Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the function described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

Attention is now optionally directed to user interface embodiments, for example, as implemented on portable multifunction device 100.

4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

signal strength indicator(s) 402 for wireless communication(s) such as cellular and Wi-Fi signals; time of day 404; Bluetooth indicator 405; battery status indicator 406; tray 408 with icons of frequently used applications, such as: icon 416 for phone module 138 labeled "Phone" that optionally includes an indicator 414 of the number of missed calls or voicemail messages; icon 418 for email client module 140 labeled "Mail" that optionally includes an indicator 410 of the number of unread emails; icon 420 for browser module 147 labeled "Browser"; and icon 430 for iPod (Apple an icon 422 for the video and music player module 152, also referred to as the "Video and Music Player" module 152 (trademark of Microsoft Corporation, Inc.); and icons for other applications, such as: an icon 424 for the IM module 141 labeled "Messages," an icon 426 for the calendar module 148 labeled "Calendar," an icon 428 for the image management module 144 labeled "Photos," an icon 430 for the camera module 143 labeled "Camera," an icon 432 for the online video module 155 labeled "Online Video," and an icon 432 for the stock widget labeled "Stock Prices." 149-2, icon 436 of map module 154 labeled "Maps", icon 438 of weather widget 149-1 labeled "Weather", icon 440 of alarm clock widget 149-4 labeled "Clock", icon 442 of training support module 142 labeled "Training Support", icon 444 of notes module 153 labeled "Notes", and icon 446 of a settings application or module labeled "Settings", which provides access to settings for device 100 and its various applications 136.

4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "music" or "music player," although other labels are optionally used for various application icons. In some embodiments, the label of each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

4B shows an example user interface on a device (e.g., device 300 of FIG. 3 ) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451, and/or one or more tactile output generators 357 that generate a tactile output for a user of device 300.

Although some of the following examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a primary axis (e.g., 452 in FIG. 4B ) that corresponds to a primary axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) at locations that correspond to respective locations on the display (e.g., in FIG. 4B , 460 corresponds to 468 and 462 corresponds to 470). In this way, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

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

FIG. 5A shows an exemplary personal electronic device 500. Device 500 includes a main body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B ). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of contact (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface actions on device 500.

For exemplary techniques for detecting and processing touch intensity, see, for example, related applications International Patent Application No. PCT/US2013/040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Patent Application No. WO/2013/169849, and International Patent Application No. PCT/US2013/069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," published as International Patent Application No. WO/2014/105276, each of which is incorporated herein by reference in its entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, may be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.

FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 operably coupling an I/O section 514 to one or more computer processors 516 and memory 518. I/O section 514 can be connected to a display 504, which can have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, I/O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 is optionally a rotatable input device or a depressible and rotatable input device, for example. In some examples, input mechanism 508 is optionally a button.

In some examples, the input mechanism 508 is optionally a microphone. The personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and/or combinations thereof, all of which may be operably connected to the I/O section 514.

The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700, 900, and 1100 (FIGS. 7A-7B, 9A-9B, and 11A-11B). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions used by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic, optical, and/or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of Figure 5B and may include other or additional components in multiple configurations.

As used herein, the term "affordance" optionally refers to a user-interactive graphical user interface object displayed on a display screen of device 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each, optionally, constitute an affordance.

As used herein, the term focus selector refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations involving a cursor or other position marker, the cursor acts as the focus selector, such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the focus selector, such that when input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface through which the user intends to interact). For example, while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, contact, or selection box) over the respective button indicates that the user intends to activate the respective button (rather than other user interface elements shown on the device's display).

As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and/or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean intensity of the contact, the average intensity of the contact, the top 10 percentile intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action, and a contact having a characteristic intensity that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather is used to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to forgo performing the respective action).

In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start position to an end position, where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contact at the end position), rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for purposes of determining the characteristic intensity.

The intensity of a contact on the touch-sensitive surface is optionally characterized with respect 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 action typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an action different from an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is not detected), the device follows the movement of the contact on the touch-sensitive surface and moves the focus selector without performing an action associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across various sets of values for a user interface.

An increase in the characteristic intensity of a contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as inputting a "light press." An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light pressure intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold may be referred to as detecting a lift-off of the contact from the touch surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed by a respective contact (or multiple contacts), where the respective press inputs are detected based at least in part on detecting an increase in intensity of the contact (or multiple contacts) above a press input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact above the press input intensity threshold (e.g., a downstroke of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press input intensity threshold followed by a decrease in intensity of the contact below the press input intensity threshold, and the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an upstroke of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental input, sometimes referred to as jitter, and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of each contact above the press input intensity threshold followed by a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a respective action is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., an upstroke of each press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or a gesture including a press input, are optionally triggered in response to detecting any of: an increase in the intensity of the contact above the press input intensity threshold; an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold; a decrease in the intensity of the contact below the press input intensity threshold; and/or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

Attention is now directed to embodiments of user interfaces (UIs) and related processes implemented on an electronic device such as portable multifunction device 100, device 300, or device 500.

6A-6O show exemplary user interfaces for activating and interacting with a digital assistant using glance and voice commands, according to some embodiments. These figures are used to illustrate the processes described below, including the processes of FIGS. 7A-7B.

6A-6D show a user 620 activating an exemplary digital assistant on electronic device 600 by glancing at electronic device 600. Once the digital assistant is activated, user 620 turns on a table lamp by speaking commands 624A-624B to the digital assistant.

6A shows the digital assistant on electronic device 600 in an inactive state indicated by display 602 being off. In some embodiments, the digital assistant is in an inactive state when electronic device 600 does not detect a user's gaze, i.e., when user 620 is looking at electronic device 600. In some embodiments, the digital assistant is in an inactive state before electronic device 600 detects a button press (or other activation command) and/or when another device (e.g., watch 630) receives the activation command. Before sending an activation command to the electronic device, the digital assistant is in an inactive state. User 620 can glance at electronic device 600 to trigger activation of the digital assistant when gaze information based on user 620's gaze meets one or more activation criteria. Electronic device 600 acquires gaze information about user 620's gaze, optionally using one or more camera sensors installed on external device 616A and/or integrated into electronic device 600, such as camera 616B. Camera sensor 616A may be wirelessly or wired to electronic device 600. The one or more camera sensors include an infrared camera sensor and/or a visible light sensor that measures gaze information as soon as a gaze is detected. The gaze information optionally includes one or more of the location of the user's head position, the gaze stasis time or duration, the gaze direction, the gaze field of view 606, and whether an object (e.g., electronic device 600 or an external device such as table lamp 618) is within the gaze field of view 606.

The electronic device 600 determines whether the gaze information obtained from one or more camera sensors 616A-616B satisfies one or more sets of activation criteria. In other words, the electronic device 600 determines whether the user 620 intended to look at the electronic device 600 to activate the digital assistant. The set of one or more activation criteria optionally includes a direction criterion that is met when the user's gaze is directed toward the electronic device 600. The set of one or more activation criteria also optionally includes a stationary time criterion that is met when the electronic device 600 detects a stationary time or duration of gaze in the direction of the electronic device 600 that exceeds a non-zero predetermined time (e.g., several seconds). If the stationary time or duration of the gaze is less than a threshold time, this may indicate that the user does not intend to trigger the digital assistant. Therefore, a stationary time less than the threshold time does not satisfy the activation criterion, and the digital assistant is not activated.

6A , the user 620 is not looking at the electronic device 600, and the electronic device 600 determines that the device 600 is not within the field of view 606 of the user 620. As described further below, the field of view criterion is met when the electronic device 600 is determined to be within the field of view 606 of the user 620, but is not met when the electronic device 600 is determined to be not within the field of view 606 of the user 620. Using the field of view 606 to determine whether the user 602 is looking at a target electronic device (e.g., device 600) increases the gaze detection rate because a gaze can be detected within the field of view when the user is not looking directly at the target electronic device but is still attempting to identify (or activate) the target electronic device.

The field of view 606 is a range of degrees above and below the user's line of sight 612, as indicated by a threshold offset angle 604. In some embodiments, the field of view criterion is met when the electronic device 600 is directly within the user's line of sight 612, i.e., the determined offset degree is zero. In some embodiments, the field of view criterion is met when the determined offset angle 622 of the gaze is less than the threshold offset angle 604 (e.g., the maximum allowable deviation from the line of sight 612 of the user 620 looking directly at the electronic device, as shown in FIG. 6B ). The determined offset angle 622 and the threshold offset angle 604 (in this example) are greater than zero degrees (e.g., 30 degrees). The determined offset angle 622 is calculated based on the angle formed between the line of sight 612 from the user's 620 gaze (e.g., where the user is actually looking) and a calculated line of sight 608 from the user 620 to the electronic device 600 (e.g., the ideal path for the user to look directly at the electronic device 600). When offset angle 622 is greater than threshold offset angle 604, as shown in FIG. 6A , the field of view criterion is not met because electronic device 600 is outside field of view 606, and as a result, the digital assistant remains deactivated. In some embodiments, if electronic device 600 is determined to be located more than a non-zero threshold degree (e.g., more than 30 degrees) outside field of view 606 of user 620, electronic device 600 is not within the user's gaze and the digital assistant is not activated. In some embodiments, line of sight 612 is measured based on the user's head position. In some embodiments, the user's head position is based on the tilt or rotation (e.g., yaw, pitch, and/or roll) of the user's head.

In FIG. 6A, as described above, the camera sensors (e.g., 616A, 61B The digital assistant on the electronic device 600 is not activated because the gaze information obtained from the gaze information acquisition unit 606 does not meet a set of one or more activation criteria. The electronic device 600 determines that the user 620 is not looking at the electronic device 600 if the quiescence time of the user's gaze is less than a threshold quiescence time or if the electronic device 600 is not within the user's field of view. In some embodiments, the field of view criterion is not met when the determined offset angle 622 between the user's line of sight 612 and the calculated line of sight 608 is greater than the threshold offset angle 604. If the digital assistant is not activated and the gaze information does not meet a set of one or more activation criteria, the electronic device 600 refrains from activating the digital assistant. When the digital assistant is not activated, electronic device 600 optionally does not turn on one or more of the microphone or speaker, does not record audio, and/or does not enable processing of recorded audio for the purpose of executing spoken commands (e.g., electronic device 600 can still process audio to detect trigger words, but does not process the audio for the execution of commands other than activation). In some embodiments, electronic device 600 does not provide any indication using a visual or audio indicator when the digital assistant is not activated (e.g., the state of electronic device 600 remains unchanged). In some embodiments, electronic device 600 remains in the same inactive state that it was in before determining that the gaze information did not satisfy one or more sets of activation criteria.

In FIG. 6A, user 620 begins speaking portion 624A of command 624A-624B, "Turn...," of "Turn on the table lamp," before the digital assistant is activated. In some embodiments, as discussed further below, if the digital assistant is not subsequently activated (e.g., within a set (non-zero) duration), portion 624A of command 624A-624B is not processed, canceled, and/or ignored by the digital assistant. In some embodiments, as discussed further below, if the digital assistant is activated (e.g., by user 620 looking at electronic device 600 and meeting one or more sets of activation criteria) before completing commands 624A-624B (or within a set duration), portion 624A of command 624A-624B received by electronic device 600 is processed before the digital assistant is activated.

6B, a user 620 is looking at the electronic device 600, and the electronic device 600 determines that the electronic device 600 is within the field of view 606 of the user 620. Gaze information obtained from the camera sensors (e.g., 616A, 616B) meets a set of one or more activation criteria.

6C, electronic device 600 determines that gaze information obtained from a camera sensor (e.g., 616A, 616B) meets one or more activation criteria and, accordingly, activates the digital assistant. Activating the digital assistant optionally includes one or more of turning on a microphone or speaker, recording audio, and enabling processing of the recorded audio for the purpose of executing spoken commands (rather than simply detecting a trigger phrase). Electronic device 600 optionally provides an indication (e.g., via indicators 610A, 610B, or 610C) that one or more activation criteria have been met and/or that the digital assistant has been activated. The indicator is optionally a visual indication 610A, an audio indication 610B, a confirmation 610C spoken by the digital assistant, or any combination of different indicators. Providing the visual indication 610A optionally includes one or more of turning on the display 602 of the electronic device 600, turning on an LED of the electronic device 600, displaying a light, a light pattern, or a visual output on the display 602 of the electronic device 600 of a particular color (e.g., blue or a color other than a default color when the digital assistant is not activated), a particular color (e.g., blue), or a color other than a default color when the digital assistant is not activated). In some embodiments, the visual indicator 610A indicating that the digital assistant is activated is different from the visual indicator 610A indicating when the digital assistant has executed a command or is in an inactive state. For example, the electronic device displays a first color of the visual indicator 610A in response to a set of one or more activation conditions being met, a second color of the visual indicator 610A in response to the digital assistant being activated, a third color of the visual indicator 610A in response to a determination that the digital assistant has executed a command, and/or a fourth color of the visual indicator 610A in response to a change to deactivating the digital assistant. The audio prompt 610B optionally includes one or more of playing a sound, a phrase, a word, or a tone. In some embodiments, the audio prompt 610B indicating that the digital assistant is activated (or that one or more sets of activation criteria have been met) is different from the audio prompt 610B indicating when the digital assistant executes a command (e.g., 624A) or is in an inactive state. The digital assistant optionally provides a digital assistant voice confirmation 610C (e.g., "How can we help you?") indicating that the digital assistant has been activated or that one or more sets of activation criteria have been met. In some examples, as described in more detail with respect to FIGS. 10A-10D , the electronic device outputs the audio confirmation using a particular voice (e.g., an accent, a male or female voice) based on the detected user.

In FIG. 6C , following the electronic device activating the digital assistant and providing instructions using display 602, the electronic device detects that user 620 has completed uttering the remaining portion 624B "...on the table lamp" of command 624C "Turn on the table lamp." In some embodiments, electronic device 600 detects that user 620 utters the entire command 624C "turn on the table lamp" after the digital assistant is activated. Optionally, electronic device 600 provides instructions 610C in accordance with a determination that a set of one or more activation criteria was met before starting to receive commands 624A-624B, and electronic device 600 does not provide instructions 610C in accordance with a determination that a set of one or more activation criteria was met after (but not before) starting to receive commands 624A-624B.

In some embodiments, electronic device 600 generates audio output at a first volume, such as playing music, before receiving remaining portion 624B of commands 624A-624B. In some embodiments, in response to electronic device 600 receiving first portion 624A of commands 624A-624B, electronic device 600 lowers the first volume of audio output to a second volume lower than the first volume, as if ducking. The second volume is optionally based on the distance between user 620 and electronic device 600. The first volume of audio output is lowered to reduce interference from background noise and enable electronic device 600 to better detect words. In some embodiments, the first volume is lowered in response to determining that a set of one or more activation criteria is met. In some embodiments, the amount of volume reduction is based on the distance between the user 620 and the electronic device 600 when the first portion 624A (but not the second portion 624B) of the command 624A-624B is received. The electronic device 600 determines the distance between the user 620 and the electronic device 600 using an external camera sensor 616A and/or a camera sensor 616B on the electronic device 600. In some embodiments, the electronic device 600 variably reduces the volume of the audio output by muting or lowering the volume of the audio output while detecting that the user 620 is speaking. The electronic device 600 returns the volume of the audio output to the first volume after detecting the end of the command 624B. The volume change is not based on the content of the request. In some embodiments, even if electronic device 600 detects that user 620 utters first portion 624A of command 624A-624B before activating the digital assistant, the digital assistant can still process the command (including 624A) if a set of one or more execution criteria is met. When the set of one or more execution criteria is met, the digital assistant executes the command based on the content of the request. The set of one or more execution criteria optionally includes one or more of command completion criteria, enablement criteria, and activation criteria. The command completion criteria are met when electronic device 600 detects the end of a received voice command (e.g., a voice-based user input request). The end of command 624A-624B is determined by electronic device 600 detecting a pause in the received voice (i.e., no user voice is received) that exceeds a non-zero predetermined period. In some embodiments, the command completion criteria are not met if the detected pause is less than a non-zero predetermined period (e.g., the user has not completed uttering the command). The enablement criteria are met when the electronic device 600 determines that the received command is executable (e.g., the device has the authority and/or capability to execute the command). In some embodiments, if the command is to access information from an account and the electronic device has not received authorization to access the account, the command is not executable because the device does not have the authority to access the account. In some embodiments, the enablement criteria are not met when the electronic device 600 cannot process the received request into a command that the digital assistant can execute or send (e.g., the command is to "turn on the TV" but there is no TV in the room where the corresponding instruction can be sent). The activation criteria are met when the digital assistant is activated.

FIG. 6D shows that the digital assistant executes a command if a set of one or more execution criteria is met while the digital assistant is activated. If the digital assistant successfully processes the command and determines that the execution criteria are met, the digital assistant sends an instruction to change the state of the appropriate device. In this example, an instruction is sent to table lamp 618 (an external device) to turn on. In some embodiments, the determination of which external device to function is made according to the description of FIGS. 8A-8C , as described in more detail below. After the digital assistant executes the command, electronic device 600 optionally provides an indicator (e.g., indicators 610A, 610B, 610C) that indicates whether commands 624A-624B were successfully executed. In some embodiments, the indicator is a visual indicator 610A that displays a particular color of light (e.g., blue or a color other than the default color when the digital assistant is not activated) or a light pattern to indicate that the digital assistant executed commands 624A-624B. In some embodiments, the indicator is an audio indicator 610B that plays a sound, phrase, word, or tone. In some embodiments, as described with respect to FIGS. 10A-10D , the indicator is a confirmation 610C spoken by the digital assistant that can be spoken in a particular voice (e.g., an accent, male, or female voice) when the digital assistant executes command 624A-624B. In some embodiments, user 620 can customize the visual indicator, audio indicator, or digital assistant indicator to include values for characteristics associated with the user's profile (e.g., username, particular user preferences for light colors, patterns, sounds, voices, accents), as described below with respect to FIGS. 10A-10D . For example, in FIG. 6D , the digital assistant can provide the confirmation, "Jack, the table lamp is turned on." The user's 620's name is obtained from the user profile of user 620, which user 620 provided during registration, and is determined as described below with respect to FIGS. 10A-10D . The registration process is described in more detail below with respect to FIGS. 10A-10D and method 1100. The digital assistant can use settings from the user 620 profile to further customize the indicator to reflect which user (e.g., Jack) spoke the command.

If one or more sets of execution criteria are not met, the electronic device 600 refrains from executing the command based on the content of the command. In some embodiments, if the enablement criteria are not met, the one or more sets of execution criteria are not met. If the enablement criteria are not met, the electronic device 600 optionally generates a head-shake prompt, as shown in FIG. 6O, to indicate that the command cannot be executed because the digital assistant was unable to process the command, lacked authorization, or was incapable of executing the command. The head-shake prompt in FIG. 6O includes a light or light pattern 602A on a first side of the display 602 of the electronic device 600 (as shown in 6O-A), followed by a light pattern 602B on a second side of the display 602 (as shown in 6O-B), followed by a light pattern 602A on the first side of the display 602 (as shown in 6O-C), which simulates a person shaking their head. In some embodiments, when the execution criteria are not met, a particular indicator (e.g., a light pattern, color, or a particular sound) is generated by electronic device 600. The particular indicator may correspond to a particular error code that indicates why the digital assistant was unable to execute the command (e.g., a blue light indicates that the command was not understood, purple indicates lack of authorization, etc.). In some embodiments, the indicator generated when the digital assistant cannot execute the command is different from the indicator generated when the digital assistant is able to execute the command.

6E-6G illustrate another embodiment in which a user 620 activates a digital assistant on a wearable or mobile electronic device 630. In FIG. 6E, the digital assistant on the electronic device 630 is activated when the electronic device 630 detects user input or a gesture, such as lifting the wrist. In some embodiments, the user 620 may also optionally activate the digital assistant on the electronic device 630 by pressing a button, rotating the crown, or providing voice user input. Once the digital assistant is activated, the electronic device 630 optionally provides a visual indicator 610A (e.g., a light), an audio indicator 610B (e.g., a sound, tone, word), or a voice confirmation 610C of the digital assistant to indicate that the digital assistant has been activated or that one or more sets of activation criteria have been met. Various types of indicators are described above with respect to FIG. 6B.

In FIG. 6F, electronic device 630 detects a spoken command from user 620, including command 624C, "Turn on the table lamp." After receiving the spoken command, the digital assistant determines whether one or more sets of execution criteria (e.g., actionable criteria, command completion criteria, activation criteria) are met. As described above, if one or more execution criteria are met, the digital assistant executes the command based on the content of the voice input request. As shown in FIG. 6F, the electronic device optionally also determines whether the user's gaze meets one or more sets of gaze criteria to identify an external device to act on. The one or more sets of gaze criteria are described in further detail below.

6G shows that electronic device 630 provides indicators (e.g., 610A, 610B, 610C) that a command was successfully executed when turning a table lamp on from an off state. Indicators that display successful execution of a command are described above with respect to FIG. 6E.

6H-6J show cases where the set of one or more execution criteria is not met and the digital assistant does not execute the command associated with the spoken command 624A-624B because the user 620 broke their gaze while speaking the command 642A-624B. The set of one or more execution criteria includes a continuous gaze criterion that is met when the electronic device 600 determines that second gaze information (e.g., acquired by the electronic device 600 using one or more camera sensors 616A, 616B (while the user 620 is speaking)) indicates that the user 620 did not break their gaze toward the electronic device 600 for more than a threshold duration between the activation of the digital assistant and the completion of the spoken command 624A-624B. In some embodiments, the threshold duration is zero, meaning that the user cannot break their gaze while speaking. In some embodiments, the threshold duration is a non-zero period, which allows the user to temporarily look away without canceling the command.

In FIGS. 6H-6I, the user 602 utters the command 624A-624B, "Turn on the table lamp," while the electronic device 600 is activated, and during that time, breaks gaze toward the electronic device 600. As shown in FIG. 6H, while the electronic device 600 receives the first portion 624A of the command 624A-624B, "turn...," the electronic device 600 determines that the user 620 is looking at the electronic device. In FIG. 6I, the electronic device 600 detects the user's break in gaze when the user 620 turns 180 degrees away from the electronic device 600 and looks away before completing the remainder 624B of the command 624A-624B, "...on the table lamp." The user's gaze is broken from the electronic device 600 when the electronic device 600 determines that the user's gaze does not meet the visual field criteria for a non-zero threshold duration (e.g., 3 seconds).

FIG. 6J illustrates that the electronic device 600 "turns on that" even if one or more sets of activation criteria are met (e.g., FIG. 6H). indicates that execution of commands 624A-624B, "light," will be postponed. As a result, table lamp 618 remains off because the digital assistant did not send it an instruction to turn it on. Electronic device 600 optionally generates an indicator (e.g., 610A, 610B, 610C) indicating that the command has not been executed. In some embodiments, the indicator may be a visual indicator 610A (e.g., a colored light or light pattern), an audio indicator 610B (e.g., a sound, speech, or a particular voice), or a digital audio confirmation 620C, as described above. The indicators (e.g., 610A, 610B, 610C) provided by electronic device 600 when commands 624A-624B are not executed are optionally different from the indicators (e.g., 610A, 610B, 610C) provided by electronic device 600 when commands 624A-624B are successfully executed.

6K-6N illustrate that even if electronic device 600 detects that user 620 breaks their gaze on electronic device 600 while electronic device 600 is receiving commands 624D-624F (when electronic device 600 is activated), the continuous gaze criterion is still met if the break in gaze is less than a threshold duration. FIG. 6K illustrates that electronic device 600 is activating a digital assistant and is receiving portion 624D "turn..." of commands 624D-624F "turn on the table lamp" from user 620. In FIG. 6L, electronic device 600 continues to receive second portion 624E "...on the..." of commands 624D-624F from user 620, but electronic device 600 detects a break in the user's gaze when the user looks away from electronic device 600.

In FIG. 6M, electronic device 600 detects that user 620 has returned gaze to electronic device 600 within a threshold duration (e.g., 3 seconds). The electronic device continues to receive the last portion 624F of commands 624D-624F, "...table lamp." Because the gaze break is less than the threshold duration, the continuous gaze criterion is still met. In FIG. 6N, once the continuous gaze criterion is met, the digital assistant executes commands 624D-624F, "Turn on table lamp," and provides instructions (e.g., visual 610A instruction, audio 610B instruction, and digital assistant confirmation 610C instruction) when table lamp 618 is turned on.

7A-7B are flow diagrams illustrating a method 700 for using an electronic device according to some embodiments. Method 700 is performed on an electronic device (e.g., 100, 300, 500, 600, 630, 800, 1000). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, method 700 provides an intuitive way to activate a digital assistant on an electronic device by glancing at the electronic device. This method reduces the cognitive burden on a user when providing user input (e.g., speech input or touch input via button press) to activate the digital assistant. In some situations, a user may be unable to effectively use voice activation (e.g., in a noisy room) or unable to provide tactile user input (e.g., pressing a button). Thus, being able to activate a digital assistant by looking at an electronic device allows a user to interact with the digital assistant using a more efficient user-device interface.

While the digital assistant of the electronic device (e.g., 600) is not activated (702), the electronic device (e.g., 600) acquires first gaze information (e.g., of a user 620) using one or more camera sensors (e.g., cameras 616A, 616B) (704). For example, the one or more camera sensors are infrared camera sensor(s) and/or visible light sensor(s). For example, the one or more camera sensors are external to the electronic device (e.g., 600), such as by being wirelessly connected to the electronic device.

Upon determining (706) that the first gaze information satisfies one or more set of activation criteria (e.g., while the digital assistant is not activated) (e.g., the gaze angle is less than a threshold degree relative to the line of sight, the gaze is in a particular direction, the duration of the gaze is equal to or greater than a predetermined period), the electronic device (e.g., 600) activates (708) the digital assistant of the electronic device (e.g., 600) (e.g., by turning on the microphone and enabling processing of recorded audio).

Using gaze detection to activate a digital assistant when a set of one or more activation criteria is met provides the user with a more efficient user interface for activating the digital assistant, particularly in contexts where the user cannot press a button or where the room is noisy and voice control cannot be used. Providing an improved user interface for activating a digital assistant that does not require tactile user input (e.g., a button press) or voice input improves the usability of the digital assistant and makes the user interface of the digital assistant interface more efficient. Additionally, using gaze detection reduces the number of user inputs required to activate the digital assistant and execute commands, improving the usability of the electronic device.

In some embodiments, the set of one or more activation criteria includes a field of view criterion that is met when the determined offset angle (e.g., 622) is less than a threshold offset angle (e.g., 604) (e.g., a non-zero degree value that is the maximum allowable deviation from the user looking directly at the device), where the determined offset angle (e.g., 622) is the angle formed between the line of sight (e.g., 612) of the user's (e.g., 620) gaze (e.g., determined from gaze information) and the calculated line of sight (e.g., 608) from the user (e.g., 620) to the electronic device (e.g., 600).

Using the field of view criterion as the activation criterion allows for detection of a user's gaze even when the user (e.g., 620) is not directly looking at the electronic device (e.g., 600). As long as the electronic device (e.g., 600) is within the field of view (e.g., 606) of the user's gaze, the user's gaze satisfies the activation criterion, and the digital assistant can be activated. Using the field of view criterion allows for more successful activation of the digital assistant via gaze, thereby improving the usability of the digital assistant and making gaze detection more efficient (e.g., the digital assistant has a higher activation rate because the electronic device (e.g., 600) does not need to be within the user's (e.g., 620) direct line of sight (e.g., 612).

In some embodiments, if the electronic device (e.g., 600) is determined to be located beyond a threshold degree (e.g., outside the field of view 606 of the gaze), the electronic device (e.g., 600) is not within the user's gaze and the digital assistant is not activated. In some embodiments, when the electronic device (e.g., 600) is within the field of view of the gaze (e.g., 606) by being within the threshold degree range, the digital assistant is activated.

In some embodiments, the line of sight (e.g., 612) of a user (e.g., 620) is based on the head position of the user (e.g., 620). In some examples, the user's head position can be affected by tilt or rotation (e.g., yaw, pitch, and roll of the user's head).

In some embodiments, the set of one or more activation criteria includes a rest time criterion that is met when the rest time (e.g., duration) of the gaze determined from the first gaze information exceeds a threshold time (e.g., a non-zero threshold time). In some examples, if the rest time of the gaze is less than the threshold time, the digital assistant is not activated.

Further, in accordance with determining (706) that the first gaze information satisfies the set of one or more activation criteria, the electronic device (e.g., 600) provides (710) an indication that the set of one or more activation criteria has been met and/or that the digital assistant of the electronic device is transitioning or transitioning to activation.

Feedback about the current state of the digital assistant is provided to the user by providing an indication (e.g., 610A, 610B, 610C) that a set of one or more activation criteria has been met and the digital assistant is activated. The indication (e.g., 610A, 610B, 610C) can be a visual confirmation, an audio confirmation, or a digital assistant voice confirmation, providing customizable feedback for various contexts. For example, in a context where a sound indicator is not audible (e.g., a noisy room), providing visual feedback (e.g., 610A) allows the user (e.g., 620) to know whether the digital assistant is activated and can process commands. Providing customized feedback of the digital device's status improves the usability of the digital assistant and makes the user-device interface more efficient, for example, by informing the user (e.g., 620) when the digital assistant is available to process commands (e.g., activated) and when it is unavailable (e.g., inactive) (e.g., the user (e.g., 620) does not issue commands if the digital assistant is not active). Additionally, feedback of the digital assistant's state may enable a user (e.g., 620) to use the digital assistant more efficiently.

In some embodiments, the indication (712) is a visual indication (e.g., 610A) (such as electronic device 600 turning on a display, LED, or light on electronic device 600) that the digital assistant is activated. In some embodiments, the indication (714) is an audio indication (e.g., 610B) (such as electronic device 600 playing a sound through a speaker on electronic device 600) to indicate that the digital assistant is now activated.

In some embodiments, the electronic device (e.g., 600) refrains from activating the digital assistant in accordance with a determination (716) that the first gaze information (e.g., while the digital assistant is not activated) does not satisfy one or more activation criteria (e.g., the electronic device (e.g., 600) is not within the user's field of view (e.g., 606), the gaze is in the wrong direction, the duration of the gaze is shorter than a predetermined period). In some embodiments, refraining from activating the digital assistant includes leaving the digital assistant inactive, or the electronic device (e.g., 600) not enabling the microphone or processing recorded audio. In some examples, if the first set of gaze information does not satisfy one or more activation criteria, the electronic device (e.g., 600) also refrains from providing an indicator (e.g., 610A, 610B, 610C) that one or more activation criteria have been met.

In some embodiments, the electronic device (e.g., 600) receives a voiced user input request to execute a command (e.g., 624A-624B, 624C) (718). In response to the electronic device (e.g., 600) receiving a voiced user input request to execute a command (e.g., 624A-624B, 624C) (720), (or in response to the digital assistant interpreting the command (e.g., 624A-624B, 624C)) and in response to determining that one or more sets of execution criteria (e.g., enablement criteria, command completion criteria, activation criteria) have been met, the electronic device (e.g., 600) executes the command (e.g., 624A-624B, 624C) based on the content of the voiced user input request (722). In some embodiments, in response to receiving a voice input request and in response to a failure to interpret a command (e.g., 624A-624B, 624C), the electronic device (e.g., 600) refrains from executing the command (e.g., 624A-624B, 624C), and the electronic device (e.g., 600) provides an indication (e.g., 610A, 610B, 610C) (e.g., displaying a visual indication, such as a head shake indication) that the command (e.g., 624A-624B, 624C) was not interpreted. Thus, the electronic device (e.g., 600) provides an indication (e.g., 610A, 610B, 610C) if the digital assistant does not understand the voice input. In some embodiments, if the digital assistant is not activated, the digital assistant refrains from executing the received command (e.g., 624A-624B, 624C).

In some embodiments, in response to the electronic device (e.g., 600) receiving a vocal user input request to execute a command (e.g., 624A-624B, 624C) and in accordance with determining that one or more sets of execution criteria (e.g., enablement criteria, command completion criteria, activation criteria) are not met, the electronic device (e.g., 600) provides a head shake instruction. The head shake instruction includes the electronic device (e.g., 600) displaying a first light pattern on a first side of a display (e.g., 602) of the electronic device (e.g., 600). Following displaying the first light pattern, the electronic device (e.g., 600) displays a second light pattern on a second side of the display (e.g., 602) of the electronic device (e.g., 600). Following displaying the second light pattern, the electronic device (e.g., 600) displays the first light pattern on the first side of the display (e.g., 602) of the electronic device (e.g., 600).

Providing a visual indication (e.g., 610A) that one or more sets of execution criteria are not met (e.g., a head shake indication (e.g., 602A-602B)) provides feedback to the user that the command issued by the user cannot be processed. Providing customizable indications, such as a head shake indication (e.g., 602A-602B), that indicate when a command (e.g., 624A-624B, 624C) will not be processed improves the usability of the digital assistant and makes the user-device interface more efficient by informing the user (e.g., 602) that the command (e.g., 624A-624B, 624C) will not be executed. Furthermore, customized indications (e.g., 610A, 610B, 610C) corresponding to error codes provide improved feedback to the user that conveys why the command (e.g., 624A-624B, 624C) was not executed, thereby making the user-device interface more efficient.

In some embodiments, the set of one or more execution criteria includes a completion criterion that is met when the electronic device (e.g., 600) detects the end of the received voice command (e.g., the end of a voice-based user input request, a pause in voice that exceeds a predetermined period). In some examples, the set of one or more execution criteria includes an enablement criterion that is met when the electronic device (e.g., 600) determines that the received command is executable (e.g., the digital assistant has the authority and/or capability to execute the command).

In some embodiments, the electronic device (e.g., 600) begins receiving a voice-based user input request while the digital assistant is not activated. In some examples, the digital assistant is inactive because the gaze information has not yet satisfied one or more activation conditions. This can occur, for example, when the user (e.g., 620) begins uttering a command (e.g., 624A-624B, 624C) before looking at the digital assistant. In some examples, the first gaze information satisfies one or more activation criteria, and in response, the digital assistant is activated before the electronic device (e.g., 600) has finished receiving a voice-based user input request to execute the command.

Being able to receive a voice user input request before the digital assistant is activated allows a user (e.g., 602) to begin speaking even if the user (e.g., 602) has not yet activated the digital assistant. Detecting a voice user input request when a set of activation conditions has not yet been met improves the operability of the digital assistant and makes the device-user interface more efficient because activations and commands (e.g., 624A-624B, 624C) do not need to be performed in order.

In some embodiments, in response to the electronic device (e.g., 600) receiving a voice-based user input request to execute a command (e.g., 124C), and in accordance with a determination that one or more sets of execution criteria are not met (e.g., various criteria that must be met for the electronic device (e.g., 600) to execute a command (e.g., 624A-624B, 624C)), the electronic device (e.g., 600) refrains from executing the command (e.g., 624A-624B, 624C) based on the content of the voice-based user input request (724), the set of one or more execution criteria including a continuous gaze criterion that is met when the electronic device (e.g., 600) determines that second gaze information (e.g., acquired by the electronic device using one or more camera sensors) indicates that the user (e.g., 602) does not break their gaze toward the electronic device (e.g., 600) for more than a threshold duration (e.g., a non-zero duration) between activation of the digital assistant and completion of the voice-based user input request. In some embodiments, the digital assistant does not execute a command (e.g., 624A-624B, 624C) because the user (e.g., 602) breaks gaze on the device (e.g., the user (e.g., 602) looks away before the command is completed, the user (e.g., 602) looks away for more than one second at a time). In some embodiments, the threshold duration is 0 seconds. In some embodiments, the threshold duration is a non-zero duration (e.g., 0.5 seconds).

In some embodiments, an electronic device (e.g., 600) generates an audio output (e.g., the electronic device (e.g., 600) is playing music), and the audio output is generated at a first volume before receiving a request for vocal user input. In response to starting to receive the request for vocal user input, the electronic device (e.g., 600) reduces the volume of the audio output to a second volume lower than the first volume, where the second volume is based on a distance between a user (e.g., a user providing the request for vocal user input) and the electronic device (e.g., 600). In some examples, the electronic device (e.g., 600) uses an external sensor (e.g., 616A) or a sensor (e.g., 616B) on the electronic device (e.g., 600) to determine the distance between the user (e.g., 602) and the electronic device (e.g., 600) and determines whether to mute or reduce the volume of music (e.g., variably lower the audio output to accommodate head retraction) while the user (e.g., 602) is speaking. In some embodiments, the electronic device may return the volume to the first volume after detecting the end of the command (e.g., 624C). In some embodiments, the volume change is not based on the content of the request.

By reducing the audio output volume or muting the audio output when the electronic device receives a voice-based user input request, the voice-based user input request can be processed more easily, and as a result, the command (e.g., 624C) derived from the voice-based user input request is more likely to be understood by the electronic device because environmental noise is reduced. Removing environmental noise or sound that may interfere with the command (e.g., 624C) being processed by the digital assistant improves the operability of the digital assistant and makes the user-device interface more efficient by increasing the accuracy of executing the correct command, thereby improving the user experience because the user (e.g., 602) does not need to repeat the command again when the digital assistant cannot process the command (e.g., 624C).

It should be noted that the details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7B) are also applicable in an analogous manner to the methods described below. For example, method 700 may include one or more of the features of the various methods described below with reference to the processes of FIGS. 9A, 9B, 11A, and 11B. For the sake of brevity, these details will not be repeated below.

It should be understood that the particular order in which operations are described in Figures 9A-9B and 11A-11B below is exemplary and is not intended to indicate that the described order is the only order in which operations may be performed. Those skilled in the art will recognize various ways to rearrange the order of operations described herein, as well as the exclusion of certain operations. For the sake of brevity, those details will not be repeated here. Furthermore, it should be noted that aspects of the methods and processes described throughout this description may be integrated with one another.

8A-8L show exemplary user interfaces for an electronic device to use gaze information to determine a context for executing a command after a digital assistant is activated (e.g., a device to which the command is directed), according to some embodiments. The techniques shown in FIGS. 8A-8L optionally work in conjunction with or include the techniques shown in FIGS. 6A-6O, which disclose how a user can activate a digital assistant by looking at an electronic device and issuing a command. Thus, the techniques described below include one or more of the characteristics of the various techniques described above with reference to FIGS. 6A-6O and method 700. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 9A and 9B.

8A-8C show electronic device 800 receiving a voiced user input request from user 820 to execute a first command 824A-824B when a digital assistant in electronic device 800 is activated. The digital assistant is activated based on a trigger word, a gaze (e.g., as described above with respect to FIGS. 6A-6O), a button press, a wrist lift while the user is wearing a wearable electronic device (e.g., a watch) ( FIGS. 6E-6G ), and/or the detection of an external device (e.g., a phone) pointed at electronic device 800. The electronic device (e.g., 800) optionally provides a visual or voiced indication 810A-810B to indicate that the digital assistant has been activated.

In FIG. 8A , user 820 is standing in a room with table lamp 818 and floor lamp 814. The digital assistant of electronic device 800 has been activated based on one or more sets of activation criteria being determined by electronic device 800 to be met as described above with respect to method 700 (e.g., device 800 has determined that user 820 is looking at device 800). When the digital assistant is activated, electronic device detects user 820 uttering portion 824A of full command 824A-B, "turn...." In some embodiments, full command 824A-B is applicable to multiple external devices (e.g., table lamp 818, floor lamp 814) that may be present in the room. In some embodiments, user's commands 824A-B do not include sufficient detail for the digital assistant to determine which external device (e.g., table lamp 818, floor lamp 814) the commands 824A-B are directed to. Therefore, the electronic device 800 cannot determine whether "the light" refers to the table lamp 818 or the floor lamp 814 based solely on the commands 824A-824B.

In FIG. 8B, a user 820 indicates which external device (e.g., a light) they want to activate by looking at a table lamp 818, and then enters the remaining portion 824B of commands 824A-824B "turn on that light" ("...on that light"). The user 820 finishes saying "the light." The electronic device receives gaze information based on the user's gaze while the user 820 is speaking and uses it to determine that the table lamp 818 is the targeted device when the user's gaze meets a set of one or more gaze criteria. The electronic device 800 obtains information about the user's gaze via one or more camera sensors that may be located on an external device 816A and/or integrated into the electronic device 800 with a camera 816B. The camera 816A is wirelessly connected to the electronic device 800 but may alternatively be wired. The one or more camera sensors may include an infrared camera sensor and/or a visible light sensor and measure the gaze information once a gaze is detected. The gaze information optionally includes one or more of the user's head position, gaze stasis time or duration, gaze direction, field of view 806 of the gaze, gaze direction, and whether an object (e.g., electronic device 800 or an external device (e.g., lamps 814, 818) is within the field of view 806 of the gaze (e.g., the external device is within a threshold offset angle 804 from the user's line of sight 812).

In some embodiments, electronic device 800 determines that a set of one or more gaze criteria is met when a direction criterion, a stationary time criterion, and/or a field of view criterion are met. The set of one or more gaze criteria optionally includes a direction criterion that is met when the gaze is directed toward table lamp 818.

The set of one or more gaze criteria includes a stillness time criterion that is met when the electronic device 800 detects a stillness or duration of gaze in the direction of the table lamp 818 that exceeds a non-zero predetermined period (e.g., 2 seconds, a threshold time). In some examples, the electronic device 800 uses the stillness time to determine whether the user 820 is looking at the table lamp 818 to determine which external object to act on (e.g., to send a command). If the stillness or duration of the gaze is too short or less than the threshold time, this indicates that the user does not intend the particular external device (e.g., the table lamp 818) to be the target device for the commands 824A-824B. In some embodiments, a stillness time less than the threshold time does not meet the gaze criterion, and as a result, the commands 824A-824B are not sent to the particular external device identified by the electronic device 800. In some embodiments, a stillness time less than the threshold time results in the electronic device 800 not identifying any external devices.

The set of one or more gaze criteria optionally includes a field of view criterion. The field of view criterion is met for a particular external device, such as a table lamp 818, when it is determined that the external device is within the field of view 806 of the user 820. The table lamp 818 is determined to be within the field of view 806 of the user 820 when the table lamp 818 is within a threshold offset angle 804 from the user's line of sight 812. Using the field of view to determine whether the user is looking at the external device of interest (e.g., table lamp 818, floor lamp 814) increases the gaze detection rate because a gaze can be detected within the field of view even when the user is not looking directly at the device of interest. In some embodiments, the field of view criterion is met for a table lamp 818 when it is directly within the line of sight 812 of the user 820. In some embodiments, the field of view criterion is met for a particular external device when the determined offset angle of the gaze is less than a threshold offset angle 804 for the external device (e.g., a maximum allowable deviation from the line of sight 812 of the user 820 looking directly at the table lamp 818). The threshold offset angle 804 is greater than zero degrees (e.g., 30 degrees). The determined offset angle is calculated based on the angle formed between the line of sight 812 from the user's gaze and the calculated line of sight from the user 820 to the electronic device 800. In the example of FIG. 8B , the user 820 is looking directly at the table lamp 818. In some embodiments, when the table lamp 818 is within the user's direct line of sight and thus within the field of view of the gaze, the field of view criterion is met for the table lamp 818, and the electronic device 800 optionally sends a command to the table lamp 818. When the offset angle is greater than the threshold offset angle 804, the field of view criterion is not met, and as a result, the digital assistant does not send a command to the table lamp 818, which is outside the field of view 806 of the user 820. In some embodiments, if the table lamp 818 is determined to be located outside the field of view 808 of the user 820 by more than a threshold degree, the table lamp 818 is determined to not be within the user's gaze, and the electronic device 800 does not send commands to the table lamp 818. In some embodiments, the line of sight 812 is measured based on the user's head position. In some embodiments, the user's head position is based on the tilt or rotation (e.g., yaw, pitch, and/or roll) of the user's head. Aspects of these techniques are illustrated and described in further detail above with respect to FIGS. 6B-6C .

Electronic device 800 optionally provides an indication (e.g., indicators 810A, 810B, 810C) when a set of one or more gaze criteria is met for table lamp 818. The indication optionally indicates that commands 824A-824B from the received voice user input request are associated with or directed at table lamp 818. The indication may be a visual 810A or audio 810B indicator that indicates that the digital assistant has identified table lamp 818 based on the user's gaze. In some embodiments, the indicator is visual indicator 810A that displays a particular color of light (e.g., blue or a color other than the default color when table lamp 818 is identified) or a light pattern to indicate that the digital assistant has identified table lamp 818 based on the user's gaze. In some embodiments, the indicator is audio indicator 810B that plays a sound, word, sound, tone, or speaks in a particular voice (e.g., an accented, male, or female voice) when the digital assistant has identified table lamp 818. In some embodiments, the digital assistant provides a voice confirmation ("Turn on the table lamp") indicating that the electronic device 800 has identified the external device to act on (e.g., turn on).

In FIG. 8C , when the electronic device determines that a set of one or more gaze criteria is met for table lamp 818, the digital assistant sends an instruction to act on the command. For example, the electronic device determines that the command is to perform a "turn on" function and that the function should be directed to a particular device (table lamp 818). Thus, the electronic device sends an instruction (e.g., to table lamp 818 or to another device that controls table lamp 818) to change the table light from an off state to an on state. In some embodiments, the digital assistant sends an instruction to change a task as a result of an external device transitioning from a first state to a second state. For example, the digital assistant may send an instruction to an external device (e.g., a computer or phone) to transition from a first state to a second state when the external device changes music, transition from performing one task to performing another task (e.g., from playing music to providing the weather), or transition from an inactive state to an active state or vice versa.

As shown in FIG. 8C , when multiple external devices (e.g., table lamp 818, floor lamp 814) are present in a room (or accessible by electronic device 800), electronic device 800 can distinguish between the multiple external devices and send commands only to the intended external device (e.g., table lamp 818, floor lamp 814). Electronic device 800 identifies the intended external device (e.g., table lamp 818, floor lamp 814) by determining whether a set of one or more gaze criteria is met for the particular external device (e.g., table lamp 818, floor lamp 814). In other words, electronic device 800 uses gaze information to determine which external device (e.g., table lamp 818, floor lamp 814) the user is looking at when a set of one or more gaze criteria is met. In some embodiments, when electronic device 800 sends a command (e.g., "turn on") to the identified first external device (table lamp 818), the second external device in the room (floor lamp 814) is not affected because it is not an external device identified by the gaze information. Floor lamp 814 (second external device) may be in an on or off state. For example, in FIG. 8C , a command is sent to table lamp 818 to turn table lamp 818 on, but no command is sent to floor lamp 814, which remains off (floor lamp 814 was previously in an off state). Thus, the sent command does not change the state of floor lamp 814. In some embodiments, when user 820 glances at floor lamp 814 but not table lamp 818, a set of one or more gaze criteria is satisfied by floor lamp 814 but not table lamp 818. Thus, the digital assistant sends commands to floor lamp 814 while table lamp 818 remains unaffected (e.g., table lamp 818 remains on if it was previously on, and remains off if it was previously off).

When the digital assistant sends a command to the corresponding external device, the electronic device 800 optionally provides an indicator (e.g., indicators 810A, 810B, 810C) indicating that the table lamp 818 has transitioned from a first state to a second state. In some embodiments, the indicator is a visual indicator 810A that displays a light or light pattern of a particular color (e.g., blue or a color other than the default color) to indicate that the table lamp 818 has been turned on from an off state as a result of receiving the command. In some embodiments, the indicator is an audio indicator 810B that is a sound, one or more words, or a tone. In some embodiments, the indicator is an audio confirmation 810C from the digital assistant, such as "Ok, Jack, the table lamp is on." The user can customize the indicator to include characteristics associated with the user's profile (e.g., username, light color, pattern, sound, voice, particular user preferences for accent) that the user 820 provided during registration. The registration process is described in more detail below in connection with FIGS. 10A-10D and method 1100. The digital assistant customizes the indicator to reflect which user (e.g., Jack) is recognized, as described below with respect to FIGS. 10A-10D and method 1100. In some embodiments, electronic device 800 provides an indicator (e.g., 810A, 810B, 810C) when the digital assistant successfully sends a command to table lamp 818, regardless of whether table lamp 818 is actually turned on. In some embodiments, electronic device 800 provides an indicator (e.g., 810A, 810B, 810C) in response to determining that table lamp 818 has been turned on. Optionally, electronic device 800 provides a different indicator (e.g., 810A, 810B, 810C) when table lamp 818 fails to execute the "turn on" command and remains off. In some embodiments, the electronic device 800 may provide different indicators (eg, 810A, 810B, 810C) to indicate a particular error code when a command 824A-824B fails to execute.

The indicators (e.g., 810A, 810B, 810C) are optionally domain (e.g., music) specific. In some embodiments, electronic device 800 determines that a command refers to an action in a particular domain (e.g., a "Love that song" command in the music domain). Following a determination that the command is for a first domain (e.g., music), the indication is a first type of indication (e.g., a particular set of sound or light indicators). Following a determination that the command is for a second domain (e.g., email) different from the first domain, the indication is a second type of indication (e.g., a different set of sound or light indicators) different from the first type of indication. Having different indicators (e.g., 810A, 810B, 810C) for different domains allows a user to easily recognize when a command was successfully executed and when a command failed to execute.

FIG. 8D shows that when the digital assistant sends a command to turn on table lamp 818, user 820 can further change the external device's settings (e.g., the lamp's brightness) by providing input to a second external device (e.g., by rotating crown 832 of watch 830 worn by user 820). Watch 830 does not have access to contextual information about which external device to control. Instead, the user simply uses crown 832 of watch 830 as an extended input mechanism to control the lamp. Watch 830 detects the user input and sends an indication of the user input to electronic device 800. Electronic device 800 receives the indication of the user input and determines that table lamp 818 is the intended external device (e.g., table lamp 818, floor lamp 814) that should receive the command. In FIG. 8D, user 820 rotates crown 842 to increase the brightness of table lamp 818 to brightness 80. In some examples, electronic device 800 determines that table lamp 818 is the intended external device based on the recency with which electronic device 800 sent a command to table lamp 818 based on the actions of user 820. In some embodiments, electronic device 800 sends a command (based on user input at watch 830) to the most recent device (e.g., table lamp 818) that electronic device 800 commanded. For example, if electronic device 800 just commanded a computer to play music, the user rotating crown 842 on watch 840 will cause electronic device 800 to send a command to the computer to increase (or decrease) the volume of the computer. In some embodiments, electronic device 800 is paired with table lamp 818. In some embodiments, electronic device 800 detects that user 820 is wearing watch 840 while watch 840 is paired with electronic device 800. In some embodiments, watch 840 is (also) paired with table lamp 818. When electronic device 800 sends a command to table lamp 818, electronic device 800 provides an indicator (e.g., 810A, 810B, 810C) that indicates the command was successfully sent. In some embodiments, electronic device 800 provides a different indicator (e.g., 810A, 810B, 810C) that indicates the command was not successfully sent to table lamp 818.

8E shows electronic device 800 receiving an additional user input instruction from watch 830 to dim the light of table lamp 818 to a lower brightness corresponding to the amount of rotation of crown 832 by user 820. In response to receiving the input instruction from watch 830, electronic device 800 sends a command to table lamp 818 to dim the light from brightness 80 to a reduced brightness of 20 based on the recency of the command to turn on table lamp 818. In some embodiments, user 820 uses watch 830 to directly control table lamp 818 once it is turned on, without having to provide an additional command to a digital assistant. When electronic device 800 sends the command to table lamp 818, electronic device 800 provides an indicator (e.g., 810A, 810B, 810C) indicating that the command was successfully sent. In some embodiments, the electronic device 800 provides different indicators (eg, 810A, 810B, 810C) that indicate that a command was not successfully sent to the table lamp 818.

In some embodiments, as shown in FIGS. 8F-8H , when multiple external devices (e.g., floor lamp 814, table lamp 818) are present in a room, electronic device 800 uses the user's gaze information to identify a particular external device as the intended external device based on the user's gaze. Electronic device 800 identifies the intended external device based on the gaze information by determining whether a set of one or more gaze criteria is met for the particular external device. If the set of one or more gaze criteria is not met for any external device, electronic device 800 refrains from sending a command because it cannot identify the external device from the gaze information. As a result, the external devices in the room remain in their original states.

8F shows that electronic device 800 detects gaze information of user 820, and in accordance with a determination that a set of one or more activation criteria is met (e.g., as described above with respect to FIGS. 6A-6D), the electronic device activates the digital assistant. The electronic device may optionally provide a visual indicator 810A (e.g., turning on display 802), an audio indicator 810B, or a digital audio confirmation 810C to indicate that the digital assistant has been activated.

8G shows table lamp 818 initially on and floor lamp 814 initially off. Electronic device 800 detects that user 820 utters second command 824C, "Turn on the light." However, user 820 is not looking at floor lamp 814, the intended external device of command 824C. Electronic device 800 acquires second gaze information via one or more camera sensors 816A, which may be located on the external device and/or integrated into electronic device 800 with camera 816B. The second gaze information optionally includes one or more of the user's head position, gaze dwell time or duration, gaze direction, field of view 806 of gaze, gaze direction, and whether floor lamp 814 is within field of view 806 of gaze.

8H , the electronic device 800 determines that the second gaze information obtained from the one or more camera sensors 816 does not satisfy a set of one or more gaze criteria. As described above, the set of one or more gaze criteria optionally includes a direction criterion that is satisfied for the floor lamp 814 when the gaze is directed in the direction of the floor lamp 814. The set of one or more gaze criteria optionally includes a stationary time criterion that is satisfied for the floor lamp 814 when the electronic device 800 detects a stationary time or duration of the gaze in the direction of the floor lamp 814 that exceeds a predetermined period (e.g., a non-zero threshold, 2 seconds). The set of one or more gaze criteria optionally includes a field of view criterion. The field of view criterion is satisfied for the floor lamp 814 when the floor lamp 814 is determined to be within the field of view 808 of the user 820. 8G-8H show that floor lamp 814 and table lamp 818 are not determined to be within user 820's field of view 808 because the determined offset angle is greater than a threshold offset angle from user 820's line of sight 812. The threshold offset angle 804 is greater than zero degrees (e.g., 30 degrees). If a set of one or more gaze criteria is not met because one or more of the duration criterion, the still time criterion, and/or the field of view criterion are not met for any external device, electronic device 800 cannot determine which external device (floor lamp 814, table lamp 818) user 820 intends to act on (e.g., turn on).

8H shows that electronic device 800 refrains from sending a "turn that light on" command to transition an external device, floor lamp 814 or table lamp 818, from a first state (e.g., off) to a second state (e.g., on) because a set of one or more gaze criteria was not met for any external device. As a result, floor lamp 814 remains off and table lamp 818 remains off, which were the initial states of the external devices before electronic device 800 detected user 820 uttering command 824C. For example, table lamp 818 remains in its on state because no command has been sent to table lamp 818 to change its initial on state.

Based on user 820's gaze information, electronic device 800 optionally generates a specific indicator (e.g., 810A, 810B, 810C) (e.g., a series of lights such as a head shake instruction (e.g., FIG. 6O or sound)) indicating that electronic device 800 did not send the command because it was unable to identify floor lamp 814 (or any other device) as the intended external device. In some embodiments, the specific indicator (e.g., a pattern of lights, colors, or a specific sound) may correspond to a specific error code as to why the digital assistant was unable to determine the external device associated with command 824C. The indicator generated when the digital assistant is unable to send the command is optionally different from the indicator generated when the digital assistant is able to send the command. In some embodiments, no indicator is generated if the digital assistant does not send the command associated with command 824C.

FIG. 8I shows another embodiment in which multiple external devices (e.g., floor lamp 814 and table lamp 818) are present in a room and paired with electronic device 800. In this example, the digital assistant is activated by a glance from user 820. In other examples, the digital assistant is activated by a word, a glance, or a button press, as described above. As shown in FIG. 8I, table lamp 818 is already in an on state and floor lamp 814 is in an off state before the user in FIGS. 8J-8L utters commands 824A-824B.

8J , electronic device 800 detects that user 820 utters portion 824A "Turn..." of second command 824A-824B "turn on that light" while detecting that user 820 is looking at floor lamp 814. In FIG. 8J , electronic device 800 acquires second gaze information based on the user glancing at floor lamp 814 via one or more camera sensors 816A, which may be located on an external device and/or integrated into electronic device 800 at camera 816B. The second gaze information optionally includes one or more of the user's head position, gaze dwell time or duration, gaze direction, gaze field of view, gaze direction, and whether floor lamp 814 is within the gaze field of view based on the offset angle.

The electronic device 800 determines whether the second gaze information obtained from the one or more camera sensors 816A-816B satisfies a set of one or more gaze criteria. When the set of one or more gaze criteria is satisfied with respect to the floor lamp 814, the electronic device 800 can determine that the user 820 intended to apply the second command 824A-824B to the floor lamp 814. As described above, the set of one or more gaze criteria optionally includes a direction criterion that is satisfied with respect to the floor lamp 814 when the gaze is directed in the direction of the floor lamp 814. The set of one or more gaze criteria optionally includes a stationary time criterion that is satisfied when the electronic device 800 detects a stationary time or duration of the gaze in the direction of the floor lamp 814 that exceeds a non-zero predetermined time (e.g., two seconds). The set of one or more gaze criteria optionally includes a field of view criterion. The field of view criterion is satisfied when the external device, the floor lamp 814, is determined to be within the field of view 808 of the user 820. A floor lamp 814 is determined to be within the field of view 808 of a user 820 when the floor lamp 814 is within a threshold offset angle 804 from the user's line of sight 812. In some embodiments, the field of view criterion is met when the floor lamp 814 is directly within the line of sight 812 of the user 820, as shown in FIG. 8J . In some embodiments, the field of view criterion is met when the determined offset angle of the gaze is less than a threshold offset angle (e.g., a maximum allowable deviation from the line of sight 812 of the user 820 looking directly at the floor lamp 814). The threshold offset angle 804 is optionally greater than 0 degrees (e.g., 30 degrees). The determined offset angle is calculated based on the angle formed between the line of sight 812 from the user's 820 gaze and the calculated line of sight 808 from the user 820 to the electronic device 800. In some examples, the field of view criterion is met for a floor lamp 814 when the floor lamp 814 is within a threshold degree from the user's direct line of sight 812 and thus within the field of view of the gaze.

In some embodiments, as shown in FIG. 8K, the user 820 breaks their gaze on the floor lamp 814 while uttering the remaining portion 824B of the second command 824A-824B. FIG. 8K shows the electronic device 800 detecting that the user 820 breaks their gaze on the floor lamp 814 while uttering the second portion 824B of the second command 824A-824B by looking away from the floor lamp 814. In some embodiments, when the electronic device 800 has already determined that the floor lamp 814 is the intended external device before the user 820 looks away, a set of one or more gaze criteria is still met even though the user 820 breaks their gaze before completing the second command 824A-824B. In some embodiments, if the electronic device 800 detects that the user 820 returns their gaze to the floor lamp 814 within a threshold duration before completing the commands 824A-824B (e.g., Figures 6E-6G), the electronic device 800 still identifies the floor lamp 814 as an external device.

When a set of one or more gaze criteria is met, the electronic device sends a command to the floor lamp 814, thereby transitioning the floor lamp 814 from an OFF state to an ON state, as shown in FIG. 8L. Because the table lamp 818 does not meet one or more set of gaze criteria, the table lamp 818 remains in its previous ON state, and therefore the electronic device does not send a command to change the state of the table lamp 818. In some embodiments, if the command 824C received by the electronic device 800 is directed to the floor lamp 814 and determines that it includes "turn off that light," when a set of one or more gaze criteria is met for the floor lamp 814, the electronic device 800 sends a command to turn the floor lamp 814 OFF, while the table lamp 818, which was already in the ON state, remains in the ON state.

FIG. 8L shows that when electronic device 800 sends a command to floor lamp 814, electronic device 800 optionally provides an indicator (e.g., indicators 810A, 810B, 810C) indicating that floor lamp 814 transitioned from an off state to an on state. In some embodiments, the indicator is visual indicator 810A that displays a light or light pattern of a particular color (e.g., blue or a color other than a default color) to indicate that table lamp 818 was turned on from an off state as a result of receiving the command. In some embodiments, the indicator is audio indicator 810B that plays a sound, one or more words, or a tone. In some embodiments, the digital assistant speaks confirmation 810C. In some embodiments, user 820 can customize the audio and visual indicators to include characteristics associated with the user's user profile (e.g., username, particular user preferences for light color, pattern, sound, voice, accent). In FIG. 8K, the digital assistant provides an audio indicator that reads, "Jack, your floor lamp is on." The audio indicator provides confirmation that the command was executed. The audio indicator also includes the name of the user 820, which the user 820 provided during registration, obtained from the user profile of the user 820. The registration process is described in more detail below with respect to FIGS. 10A-10D. The digital assistant can utilize settings from the user 820's profile to further customize the indicator to reflect which user (e.g., Jack) spoke the command. In some embodiments, the electronic device 800 provides an indicator when the electronic device successfully sends a "turn on" command to the floor lamp 814, regardless of whether the floor lamp 814 is actually on. Optionally, the electronic device 800 provides a different indicator when the floor lamp 814 fails to execute the "turn on" command and remains off. In some embodiments, the indicator when the command 824C is unsuccessfully executed includes different indicators for different error codes.

9A-9B are flow diagrams illustrating a method 900 of using an electronic device, according to some embodiments. The method 900 is performed on an electronic device (e.g., 100, 300, 500, 600, 640, 800, 1000) having a display device. Some operations of the method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, method 900 provides an intuitive way for a user (e.g., 820) to provide context about a voice user input request to a digital assistant on an electronic device (e.g., 800) by having the user glance at the external device (e.g., 814, 818) that the voice user input request is intended to act on. This method reduces the cognitive burden on the user (e.g., 820) when providing a voice user input request to the digital assistant (e.g., having to remember to mention the external device in the command). Thus, the digital assistant can determine the external device (e.g., 814, 818) for a command by monitoring the user's gaze (e.g., 820).

While the first external device (e.g., 818) is in a first state (e.g., the first external device (e.g., 818) is on or off, the first external device (e.g., 818) is playing a particular media item) (902), the electronic device (e.g., 800) receives a user input request (e.g., user speech input) to execute a first command (e.g., 824A-824B) (e.g., transition the external device to a second state and tell the digital assistant to "turn on that light") (904). In some embodiments, the electronic device receives a voice-based user input request (904) while the digital assistant on the electronic device (e.g., 800) is active (e.g., based on a trigger word, gaze, and/or button press).

While the first external device (e.g., 818) is in a first state (902), the electronic device acquires first gaze information (906) from a camera(s) external to the electronic device (e.g., 800), such as wirelessly connected to the electronic device (e.g., 800) or to a portion of the electronic device (e.g., 800), using one or more camera sensors (e.g., 816A, 816B) (e.g., infrared camera sensor(s), visible light sensor(s)). (e.g., the electronic device (e.g., 800) detects gaze information directed at the first external device (e.g., 818). In some examples, the electronic device (e.g., 800) uses the first gaze information to determine whether a set of one or more gaze criteria is met for the particular external device.

Using the first gaze information, upon determining (908) that a set of one or more gaze criteria is met for a first external device (e.g., 818) (e.g., an appliance such as a lamp, television, or computer) (and optionally, upon the electronic device (e.g., 800) receiving a voice-based user input request), the electronic device (e.g., 800) sends (910) an instruction (e.g., to the first external device (e.g., 818)) to transition the first external device (e.g., 818) from a first state to a second state based on the first command (e.g., the digital assistant performs an action on the external device (e.g., 818) by transitioning the external device (e.g., 818) from an on state to an off state or from an off state to an on state).

Using gaze detection to determine which external device (e.g., 814, 818) is associated with a command (e.g., 824A-824B) when a set of one or more gaze criteria is met provides a more efficient user interface for the user, providing context to the digital assistant by simply looking at the external device (e.g., 814, 818) without having to answer follow-up questions from the digital assistant to clarify which external device (e.g., 814, 818) is intended. By providing the digital assistant with an improved user interface that provides context to commands (e.g., 824A-824B) without the digital assistant having to interact with the user to obtain more information, the user interface of the digital assistant becomes more efficient. Additionally, using gaze detection reduces the number of inputs required to activate the digital assistant and execute a command (e.g., 824A-824B), thereby improving usability of the digital assistant.

In some embodiments, pursuant to determining that a set of one or more gaze criteria are met (e.g., angle, duration, and direction of gaze) for the first external device (e.g., 818), the electronic device (e.g., 800) provides (912) an indication (e.g., 810A, 810B, 810c) (e.g., a visual or audio indication) that the set of one or more gaze criteria are met (e.g., indicating that a first command (e.g., 824A-824B) is associated with the first external device (e.g., 818)).

The digital assistant provides feedback to the user regarding whether a command (e.g., 824A-824B) was executed by providing an indication that one or more sets of gaze criteria were met and that the digital assistant successfully sent the command to the external device (e.g., 800). The indication (e.g., 810A, 810B, 810C) can be a visual confirmation, an audio confirmation, or a digital assistant audio confirmation, providing customizable feedback for various contexts. For example, in a context where sound is not audible (e.g., a noisy room), providing visual feedback allows the user to know whether the digital assistant sent the command (e.g., 824C). Providing customized feedback of the digital device's status improves the usability of the digital assistant, and notifying the user when the digital assistant successfully sent a command to an external device makes the user-device interface more efficient (e.g., the user does not need to repeat a command because they are unsure whether the command was executed by the digital assistant). Furthermore, feedback of the digital assistant's status allows users to use the device quickly and efficiently.

In some embodiments, the instructions (e.g., 810A, 810B, 810C) (e.g., visual or audio instructions) are domain-specific (914) (e.g., music domain, weather domain, messaging domain). In some examples, the electronic device (e.g., 800) determines that the command (e.g., 824C) is for a particular domain. Pursuant to determining that the command (e.g., 824C) is for a first domain, the instructions (e.g., 810A, 810B, 810C) are a first type of instruction. Pursuant to determining that the command (e.g., 824C) is for a second domain different from the first domain, the instructions (e.g., 810A, 810B, 810C) are a second type of instruction different from the first type of instruction.

By providing domain-specific instructions, the digital assistant quickly notifies the user (e.g., 820) whether the digital assistant was able to successfully transmit the command (e.g., 824C). By associating a specific visual, audio, or digital audio indicator with a specific domain, the user is quickly provided with an improved user interface that allows the user to quickly determine whether further action needs to be taken if the command (e.g., 824C) is not successfully executed. For example, the user can quickly determine whether the command "love that" is being executed. When a user says, "I love that song," the user (e.g., 820) is quickly notified that the song has been added to their favorites list by a specific tone associated with the command, without the user having to confirm whether it was successful. This quickly reduces the user's cognitive burden, as the association of a specific action in a specific domain with a successful tone provides immediate confirmation that the task has been accomplished. Furthermore, feedback of the digital assistant's state enables the user (e.g., 820) to use the digital assistant more quickly and efficiently.

In some embodiments, the electronic device (e.g., 800) is paired (916) with a first external device (e.g., 814, 818) (e.g., a paired lamp, television, computer, phone, or watch).

In some embodiments, using the first gaze information, for the first electronic device (e.g., 814, 818), pursuant to determining that a set of one or more gaze criteria is not met (e.g., the user breaks gaze, the user does not look at the external device for a threshold time), the electronic device (e.g., 800) refrains from sending an instruction to transition the first external device (e.g., 818) from the first state to the second state. In some examples, the digital assistant does not execute a command (e.g., 824C) when a set of one or more gaze criteria is not met.

In some embodiments, the set of one or more activation criteria includes a line-of-sight criterion that is met when the determined offset angle (e.g., 810) is less than a threshold offset angle (e.g., 804) (e.g., a maximum allowable deviation from the user looking directly at the device, a non-zero threshold offset angle, a threshold offset angle greater than zero degrees), where the determined offset angle (e.g., 810) is the angle formed between the line-of-sight (e.g., 812) of the user's gaze (e.g., determined from gaze information) and a calculated line-of-sight (e.g., 808) from the user (e.g., 820) to the electronic device (e.g., 818). In some examples, if the first external device (e.g., 818) is determined to be located more than the threshold degree (e.g., outside the field of view (e.g., 806) of the gaze), the first external device (e.g., 818) is not within the user's line-of-sight, and no command is sent to the first external device (e.g., 818). In some examples, when the first external device (e.g., 818) is within the field of view (e.g., 806) of gaze by being within a threshold degree, the digital assistant sends a command to the first external device (e.g., 818).

Using the field of view criterion as the gaze criterion allows a user's gaze to be detected without the user having to look directly at the external device (e.g., 818). Instead, as long as the external device (e.g., 818) is within the field of view of the user's gaze, the user's gaze satisfies the gaze criterion, thereby allowing the electronic device (e.g., 800) to determine which external device (e.g., 814, 818) is intended. Using the field of view criterion allows the external device (e.g., 818) to be determined without requiring further interaction with the user, thereby improving the usability of the digital assistant and making gaze detection by the electronic device (e.g., 800) more efficient (e.g., the external device (e.g., 818) is more easily identified because it does not need to be within the user's (e.g., 820) direct line of sight).

In some embodiments, the line of sight (e.g., 812) of a user (e.g., 820) is based on the head position of the user (e.g., 820) (e.g., the same user from whom the voice user input request was received). In some examples, the user's head position can be affected by the tilt or rotation (e.g., yaw, pitch, and roll) of the user's head. In some examples, head position tracking is used to determine whether a first external device (e.g., 818) is within the field of view (e.g., 806).

In some embodiments, the set of one or more gaze criteria includes a stillness time criterion that is met for the first external device (e.g., 818) when a stillness time (e.g., duration) of the gaze determined from the first gaze information exceeds a threshold time (e.g., a non-zero time). In some examples, when a stillness time of the gaze of the user (e.g., 820) is less than the threshold time.

In some embodiments, following the electronic device (e.g., 8000) sending a command (e.g., to the first external device (e.g., 818)) to transition the first external device (e.g., 818) from the first state to the second state, the electronic device (e.g., 800) provides an indication (e.g., 810A, 810B, 810C) (e.g., audio or visual) that the first external device (e.g., 818) is in the second state (e.g., the electronic device (e.g., 800) provides a visual indication (e.g., 810A) that the first external device (e.g., 818) is turned on). In some examples, the electronic device (e.g., 800) provides a different indication (e.g., 810A, 810B, 810C) when the command (e.g., 824C) could not be executed (e.g., the first external device (e.g., 818) is still in the first state).

In some embodiments, upon determining using the first gaze information that the first external device (e.g., 818) is in a first state, the second external device is in a third state, and a set of one or more gaze criteria is met for the second external device (e.g., an appliance such as a lamp, television, or computer) (and optionally, upon receiving a voice user input request), the electronic device (e.g., 800) sends an instruction (e.g., to the first external device (e.g., 818)) to transition the second external device (e.g., 814) from the third state to a fourth state based on the first command (e.g., 824C) (e.g., the electronic device (e.g., 800) performs an action on the second external device (e.g., 814) by transitioning the second external device from an on state to an off state or from an off state to an on state).

Upon determining using the first gaze information that a set of one or more gaze criteria is not met for a second external device (e.g., 814) (e.g., an appliance such as a lamp, television, or computer) (and optionally, upon receiving a voice user input request), the electronic device (e.g., 800) refrains from sending (e.g., to the first external device) an instruction to transition the second external device (e.g., 814) from a third state to a fourth state based on the first command (e.g., 824C) (e.g., the electronic device (e.g., 800) refrains from performing an action on the second external device, such as by refraining from transitioning the second external device from an on state to an off state or from an off state to an on state).

In some embodiments, while the first external device (e.g., 818) is in the second state (e.g., the first external device 9, e.g., 818) can also be in the first state) and the second external device (e.g., 814) is in the third state (918), the electronic device (e.g., 800) receives (920) a second user input request (e.g., user speech input) including a second command (e.g., 826C).

The electronic device (e.g., 800) uses one or more camera sensors (e.g., 816A, 816B) to acquire second gaze information (922) (e.g., to tell the digital assistant to turn on "the" light and transition a second external device (e.g., 814) to a second state).

In response to determining, using the second gaze information, that one or more sets of gaze criteria are met for the second external device (e.g., 814) (e.g., the second gaze identifies the second external device (e.g., 814) by satisfying the gaze criteria, such as the gaze angle being within a threshold degree range, the gaze being in a specific direction, and the duration being equal to or greater than a predetermined time), the electronic device (e.g., 800) transmits, based on the second command (e.g., 824C), an instruction to transition the second external device (e.g., 814) from the third state to the fourth state (e.g., changing the state of the second external device (e.g., 814), i.e., turning on the floor lamp) (924). Meanwhile, the first external device (e.g., 818) remains in the second state (e.g., the table lamp remains on without changing the state of the first external device).

In some embodiments, while the second external device (e.g., 814) is in the third state, and pursuant to a determination using the second gaze information that a set of one or more gaze criteria is not met for the second external device (e.g., 814) (e.g., the second external device is not identified), the electronic device (e.g., 800) refrains from sending an instruction to transition the second external device (e.g., 814) from the third state to the fourth state (e.g., the second external device (e.g., 814) remains in the same state as before).

In some embodiments, following sending (e.g., to the second external device (e.g., 814)) an instruction to transition the second external device (e.g., 814) from the third state to the fourth state, the electronic device (e.g., 800) provides an indication (e.g., 810A, 810B, 810C) (e.g., a visual or audio indication) indicating that the second external device (e.g., 814) is in the fourth state (e.g., providing a visual (e.g., 810A) indication or an audio (e.g., 810B) indication indicating that the state of the second external device (e.g., 814) has changed). In some examples, the electronic device (e.g., 800) provides a different indication (e.g., 810A, 810B, 810C) when the second command (e.g., 824C) could not be executed (e.g., the second external device (e.g., 813) is still in the third state).

In some embodiments, following sending (e.g., to the first external device (e.g., 818)) a command to transition the first external device (e.g., 818) from a first state to a second state, the electronic device (e.g., 800) receives from a third external device (e.g., a watch or phone) an indication of an input (e.g., the rotation of a crown (e.g., 832) on the third external device) received by the third external device (e.g., 830). The electronic device (e.g., 800) sends a second command to the first external device (e.g., 818) based on the recency with which the electronic device (e.g., 800) commanded the first external device (e.g., 818) to transition the first external device (e.g., 818) (e.g., dim the brightness of a table lamp after the table lamp was turned on). In some embodiments, a third external device (e.g., 830) may be configured to receive a notification from a third external device (e.g., 840) with which the third external device (e.g., 840) is interacting. The first external device (e.g., 814, 818) does not know which external device (e.g., 814, 818) the electronic device (e.g., 800) is connected to. The third external device (e.g., 830) only receives input and sends user input to the electronic device (e.g., 800), and knows which external device (e.g., 814, 818) the electronic device (e.g., 800) should send a command to (e.g., dim the lights).

A third external device (e.g., 830) is used to further control the proximate external device (e.g., 818) to which the electronic device (e.g., 800) sent commands, thereby providing the user (e.g., 820) with an additional user interface with further control of the external device (e.g., 818).

Providing the user (e.g., 820) with additional user interfaces and mechanisms to control devices without needing to go through the digital assistant provides a more efficient user interface and reduces the number of interactions with the digital assistant required to execute a command. Rather than needing to interact with the digital assistant to process the additional commands, the user (e.g., 820) can simply use the external device (e.g., 830) to provide precise input that may be difficult to describe in words. Receiving additional user input based on input received from a third external device (e.g., 840) improves the usability of the digital assistant and makes the user interface for controlling the external device (e.g., 818) more efficient because additional commands are not required.

It should be noted that the process details described above with respect to method 900 (e.g., FIGS. 9A-9B) are also applicable in a similar manner to the methods described below/above. For example, method 900 optionally includes one or more of the features of the various methods described above with respect to method 700 and below with respect to method 1100. For example, method 900 may include one or more of the features of the various methods described above and below with reference to the processes of FIGS. 7A, 7B, 11A, and 11B. For the sake of brevity, these details will not be repeated below.

It should be understood that the particular order in which the operations in Figures 7A-7B and 11A-11B below are described is exemplary and is not intended to represent the only order in which those operations may be performed. Those skilled in the art will recognize various ways to rearrange the order of the operations described herein, as well as the exclusion of certain operations. For the sake of brevity, those details will not be repeated here. Furthermore, it should be noted that aspects of the methods and processes described throughout this description may be integrated with one another.

10A-10D show exemplary user interfaces for providing different indicators that indicate the digital assistant's recognition of different users (e.g., 1020, 1030) in a room uttering commands at the time the digital assistant is activated, according to some embodiments. The digital assistant is activated based on a trigger word, a gaze as described above with respect to method 700, a button press, a wrist lift while the user is wearing a wearable electronic device (e.g., a watch) (e.g., FIGS. 6E-6G), and/or a user pointing an external device (e.g., a phone) over electronic device 1000. In some examples, electronic device 1000 activates the digital assistant and receives commands when the digital assistant is launched in response to determining that a user (e.g., 1020, 1030) is looking at electronic device 1000 (e.g., in response to determining that one or more sets of activation criteria are met using gaze information, as described above). 10A-10D also optionally include aspects of method 900 and techniques described with respect to FIGS. 8A-8L, which show an electronic device using a user's gaze to determine a particular external object (e.g., table lamp 1018, floor lamp) associated with a command. The techniques in these figures are used to illustrate processes described below, including the processes of FIGS. 11A-11B.

10A-10D, users Jane 1030 and Jack 1020 are in the same room as electronic device 1000. In FIG. 10A, a digital assistant of the electronic device is activated, such as by using aspects of the techniques described above. Electronic device 1000 receives spoken commands (e.g., 1024A, 1024B) from one or more users (e.g., Jane 1030 and Jack 1020) to control various external devices in the room, such as a floor lamp 1014 or a table lamp 1018. In response to electronic device 1000 receiving the commands (e.g., 1024A, 1024B), electronic device 1000 determines the user identities (e.g., 1020, 1030) of the particular users who spoke the commands (e.g., 1024A, 1024B). In some embodiments, an external device (e.g., external camera 1016A, phone, or integrated camera 1016B) determines a user identification corresponding to the command and transmits the user identification to electronic device 1000. In some embodiments, electronic device 1000 acquires information about the speaking user using an external or internal device (e.g., external camera 1016A, phone, or integrated camera 1016B). In some embodiments, electronic device 1000 uses the acquired information to perform facial recognition, voice recognition, or calculate the distance to the speaking user to determine the user identification.

In some embodiments, before the electronic device activates the digital assistant, users Jane 1030 and Jack 1020 optionally register user profiles stored on electronic device 1000. In some embodiments, the user profiles are stored on a server and accessible by electronic device 1000. The user profiles include settings and preferences (e.g., the type of accent of the digital assistant's voice, the gender of the digital assistant's voice, the tone of the indicator, and the color of the LED light) that the electronic device can use to customize indicators 1010A, 1010B, and 1010C used by the electronic device to indicate whether the digital assistant is activated or whether commands 1024A and 1024B have been executed successfully or unsuccessfully. For example, a user can customize digital indicator settings by providing values for each characteristic of the indicator. In some examples, indicator characteristics include the type (e.g., visual, audio, voice confirmation, or any combination of type), the color of the light for the visual indicator, the tone of the audio indicator, and customizations related to the digital voice (e.g., language, accent, and gender type). The user profile also optionally stores information about the user provided by users Jane 1030 and Jack 1020 during registration with the users' consent, such as the user's name, birthdate, gender, and/or address. User profile settings and preferences may be updated at any time. The techniques for user registration on electronic device 1000 described herein may be used in combination with methods 700 and 900, described above with reference to the processes of Figures 7A, 7B, 9A, and 9B. For brevity, these details will not be repeated here.

10A , electronic device 1000 receives command 1024A from Jane 1030 to "turn on the table lamp" when the digital assistant is activated. When electronic device 1000 receives command 1024A spoken by Jane 1030 (or after receiving command 1024A spoken by Jane 1030), electronic device 1000 determines that the speaker is Jane 1030. For example, device 1000 uses external camera 1016B, integrated camera 1016B, and/or microphone to determine that the received command 1024A is coming from the direction in which Jane 1030 is sitting. Thus, electronic device 1000 displays light pattern 1010D (e.g., three illuminated dots) on display 1002 at a position corresponding to the direction in which Jane 1030 is sitting. In some embodiments, electronic device 1000 displays animated light pattern 1010D on display 1002, where the light pattern is animated to point in the direction where Jane 1030 is sitting.

In FIG. 10A , if the digital assistant determines that the speaker of command 1024A is Jane 1030, electronic device 1000 updates the value of a characteristic (e.g., a light color, a particular sound, a word, or a unique digital assistant voice) of an indicator (e.g., visual 1010A, audio 1010B, or digital assistant confirmation 1010C) to a value corresponding to Jane 1030 (e.g., purple light, two-tone tone, Jane's name, British accent, female voice). In some embodiments, the characteristic value is a value obtained from Jane's user profile. For example, the electronic device sets the color of light pattern 1010D (e.g., three illuminated dots) on display 1002 to a color corresponding to Jane 1030 (e.g., purple). As a result, the electronic device 1000 indicates to Jane 1030 and Jack 1020 that the device 1000 recognized the speaker as Jane 1030 and that one or more of Jane's 1030 preferences will be used.

In contrast, in FIG. 10C , if the digital assistant determines that the speaker of command 1024B is Jack 1020, a different user than Jane 1030, electronic device 1000 updates the values of the characteristics (e.g., light color, sound, or digital assistant voice) of the indicator (e.g., visual indicator or audio indicator) to values corresponding to Jack 1020 (e.g., blue light, one-tone tone, Jack's name, Australian accent, male voice), where the values of the characteristics associated with Jack 1020 are different from the values of the characteristics associated with Jane 1030. For example, electronic device sets the color of light pattern 1010E (e.g., three illuminated dots) on display 1002 to a color (e.g., blue) corresponding to Jack 1020. As a result, electronic device 1000 indicates to Jane 1030 and Jack 1020 that it recognizes the speaker as Jack 1020 and that one or more of Jack 1020's preferences will be used.

In some embodiments, Jack 1020 and Jane 1030 may have the same characteristic values associated with each person. For example, Jack 1020 and Jane 1030 may both select an American, female digital assistant voice. In some embodiments, the indicator characteristic values associated with each user are unique. For example, Jane 1030 and Jack 1020 may have different light colors (e.g., Jane's is purple while Jack's is blue) and different sounds (e.g., a two-tone sound versus a one-tone sound) associated with each user.

10B, after electronic device 1000 identifies Jane 1030 as uttering command 1024A, electronic device 1000 determines whether a set of one or more execution criteria are met, as described above with respect to method 900. The set of one or more execution criteria includes one or more of a completion criteria, an actionable criteria, and an activation criteria. If the set of one or more execution criteria is met, electronic device 1000 performs an action, such as sending a command to turn on floor lamp 1014.

When electronic device 1000 executes command 1024A, electronic device 1000 optionally provides an indicator (e.g., indicators 1010A, 1010B, 1010C) using Jane's 1030 preferences to indicate that the command was successfully executed. Types of indicators (e.g., visual confirmation, audio confirmation, and digital voice confirmation) and their characteristics are described above with respect to methods 700 and 900. In FIG. 10B , electronic device 1000 determines that the speaker is Jane 1030 and, based on that determination, provides confirmation using a female digital assistant voice confirmation in an American accent: "Jane, the floor lamp has been turned on." The name "Jane" is obtained from Jane's 1030 user profile, which Jane 1030 provided during registration. Electronic device 1000 uses a female American accent based on previous preferences stored as part of Jane's 1030 user profile. A purple light pattern may be displayed as a visual indicator on electronic device 1000 to indicate that the digital assistant processed Jane's command 1024A. A tone associated with Jane 1030 may also be played as an audio indicator on electronic device 1000 to indicate that the digital assistant processed Jane's 1024A command. As a result, both Jane 1030 and Jack 1020 recognize that Jane has been identified as the speaker.

Similarly, FIG. 10C shows Jack 1020 uttering the command 1024B, "Turn on the floor lamp." The electronic device 1000 determines, for example, using the external camera 1016A, the integrated camera 1016B, and/or the microphone, that the speaker is Jack 1020 and determines that the command 1024B is coming from the direction where Jack 1020 is sitting. In response, the electronic device 1000 displays a light pattern 1010E (e.g., three light dots) on the display 1002 in a position corresponding to the direction where Jack 1020 is standing. In some embodiments, the electronic device 1000 displays an animated light pattern 1010E on the display 1002, where the light pattern is animated to point in the direction where Jack 1020 is standing. For example, the electronic device sets the color of the light pattern 1010E (e.g., three light dots) on the display 1002 to a color (e.g., blue) corresponding to Jack 1020. As a result, the electronic device 1000 indicates to Jane 1030 and Jack 1020 that the device 1000 recognizes the speaker as Jack 1020 and that one or more of Jack's 1020 preferences will be used.

10D , after electronic device 1000 determines that jack 1020 has uttered command 1024B, electronic device 1000 determines whether a set of one or more execution criteria are met, as described above with respect to method 900. The set of one or more execution criteria includes one or more of a completion criteria, an actionable criteria, and an activation criteria. If the set of one or more execution criteria is met, electronic device 1000 performs an action, such as sending a command to turn on floor lamp 1014.

When electronic device 1000 executes command 1024B, electronic device 1000 optionally provides an indicator (e.g., indicators 1010A, 1010B, 1010C) using Jack 1020's preferences to indicate that the command was executed successfully. Types of indicators (e.g., visual confirmation, audio confirmation, and digital audio confirmation) and their characteristics are described above with respect to methods 700 and 900. In FIG. 10D , electronic device 1000 determines that the speaker is Jack 1020 and, based on that determination, provides the confirmation "Jack, the table lamp is turned on" using a male digital assistant voice with an Australian accent. The name "Jack" is obtained from Jack's 1030 user profile, which Jack 1020 provided during registration. Electronic device 1000 uses a male Australian accent based on previous preferences stored as part of Jack's 1020 user profile. A blue light pattern may be displayed as a visual indicator on electronic device 1000 to indicate that the digital assistant has processed Jack's command 1024B. The electronic device optionally plays a custom tone associated with Jack 1020 as an audio indicator to indicate that the digital assistant has processed Jack's command 1024B.

11A-11B are flow diagrams illustrating a method 1100 of using an electronic device, according to some embodiments. Method 1100 is performed on an electronic device (e.g., 100, 300, 500, 600, 640, 800, 1000). Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, method 1100 provides an intuitive way for the digital assistant to indicate recognition of different users (e.g., 1020, 1030) by providing a unique indicator for each person. This method reduces the cognitive burden on users (e.g., 1020, 1030) when multiple users are uttering commands in a room because the user can see when the digital assistant processed a particular user's command. Thus, the digital assistant can provide immediate feedback to indicate which user's command was processed.

After the digital assistant on the electronic device (e.g., 1000) is activated based on a trigger word, gaze, and/or button press, the electronic device 1000 receives a voice-based user input request (e.g., 1024A, 1024B) (1106). In some embodiments, in response to receiving the voice-based user input request (e.g., 1024A, 1024B), the electronic device (e.g., 1000) determines user identification information (e.g., a particular user (e.g., 1020, 1030)) corresponding to the voice-based user input request (e.g., 1024A, 1024B). In some embodiments, a remote device (e.g., camera 1016) determines user identification information corresponding to the voice-based user input request (e.g., 1024A, 1024B), and the electronic device (e.g., 1000) receives the result of the determination.

In some embodiments, before the electronic device (e.g., 1000) receives the voice-based user input request (e.g., 1024A, 1024B), the electronic device (e.g., 1000) receives (1102) registration information (e.g., user profile information). In some embodiments, the electronic device (e.g., 1000) uses the registration information to associate (1104) a first value of a characteristic (e.g., light, sound, digital assistant voice) of an indicator (e.g., 1010A, 1010B) of the electronic device (e.g., 1000) with a first user (e.g., 1020) (and not with a second user) and to associate a second value of the characteristic of the indicator of the electronic device (e.g., 1000) with a second user (e.g., 1030) (and not with the second user). In some embodiments, during the registration process, the electronic device (e.g., 1000) receives the user's name and then associates the name with the user's (e.g., 1020, 1030) voice. In some embodiments, during the registration process, the electronic device (e.g., 1000) associates a visual indicator color (e.g., LED color) with the user (e.g., 1020, 1030).

Associating the characteristic values of the indicators (e.g., 1010A, 1010B, 1010C) with preferences in the user's user profile enables the digital assistant to provide feedback to confirm that the digital assistant has identified the particular user (e.g., 1020, 1030) issuing the command. Providing customized feedback to confirm to the user (e.g., 1020, 1030) improves the usability of the digital assistant, and providing confirmation to the user (e.g., 1020, 1030) using the indicators (e.g., 1010A, 1010B, 1010C) with the user's (e.g., 1020, 1030) preferences makes the user-device interface more efficient (e.g., the user (e.g., 1020, 1030) knows that the digital assistant processed the user's command (1024A, 1024B)). This reduces the cognitive burden on the user (e.g., 1020, 1030) by providing immediate confirmation that the task was performed by associating the success indicator with a particular user's settings, and reduces confusion when multiple users are speaking simultaneously or when there are other speakers in the background. Additionally, feedback of the digital assistant's state allows the user (e.g., 1020, 1030) to use the digital assistant more quickly and efficiently.

The electronic device receives (1106) a request for voice user input.

In some embodiments, the vocal user input requests (e.g., 1024A, 1024B) are user spoken input (e.g., utterances, commands), and the updating (1108) of the value of the property (e.g., light, sound, digital assistant voice) is not based on the transcribed content of the vocal user input requests (e.g., 1024A, 1024B) (e.g., the value of the property is not based on what the user said, but rather on the user's identity).

In response to determining that the voice user input request corresponds to the first user (e.g., 1020) (and optionally, in response to receiving the voice user input request), the electronic device (e.g., 1000) updates (1110) the value of a characteristic (e.g., light color, sound, digital assistant voice) of an indicator (e.g., 1010A, 1010B, 1010C) (e.g., a visual indicator, an audio indicator, or a digital assistant voice confirmation) to a first value corresponding to the first user (e.g., 1020) (e.g., the characteristic value is associated with the identity of the first user).

In response to determining that the voice user input request corresponds to a second user (e.g., 1030) different from the first user (and optionally in response to receiving the voice user input request), the electronic device (1000) updates (1112) the value of a characteristic (e.g., light color, sound, digital assistant voice) of an indicator (e.g., 1010A, 1010B, 1010C) (e.g., a visual indicator, an audio indicator, or a digital assistant voice confirmation) to a second value corresponding to the second user (e.g., 1030) (e.g., the value of the characteristic is associated with the identity of the second user), the second value being different from the first value.

The electronic device (e.g., 1000) responds (1114) to the voice user input request (e.g., 1024A, 1024B) using an indicator (e.g., 1010A, 1010B, 1010C) (e.g., the electronic device (e.g., 1000) displays a light and plays a sound using a particular digital assistant voice or using the user's name in the response). The indicator (e.g., 1010A, 1010B, 1010C) includes an updated value for the characteristic (e.g., light color, sound, or digital assistant voice).

In some embodiments, an electronic device (e.g., 1000) that responds to a vocal user input request (e.g., 1024A, 1024B) using an indicator (e.g., 1010A, 1010B, 1010C) includes an electronic device (e.g., 1000) that displays (1116) a visual indicator (e.g., 1010A) (e.g., a light) using a value of a characteristic (e.g., light color, position of displayed light) corresponding to the user associated with the vocal user input request (e.g., 1024A, 1024B).

In some embodiments, an electronic device (e.g., 1000) that responds to an audio user input request (e.g., 1024A, 1024B) using an indicator includes an electronic device (e.g., 1000) that provides (1118) an audio indicator (e.g., 1010B) (e.g., voice, sound) using a characteristic value (the characteristic value can be an accent, gender, pitch, voice, sound, or a particular digital assistant voice, such as an American female digital assistant voice) that corresponds to a user (e.g., 1020, 1030) associated with the audio user input request (e.g., 1024A, 1024B).

In some examples, the user selected an American female digital assistant voice in the digital assistant voice settings shown in the user's user profile (e.g., 1020, 1030).

In some embodiments, the indicator is a visual indicator (e.g., 1010A), and in response to the electronic device (e.g., 1000) receiving the voice user input request (e.g., 1024A, 1024B) and prior to determining that the voice user input request (e.g., 1024A, 1024B) corresponds to a particular user (e.g., 1020, 1030), the electronic device (e.g., 1000) displays the visual indicator (e.g., 1010A) with a default value (e.g., a white light) of the characteristic (e.g., displaying a first light color when the digital assistant is activated). In some embodiments, the default value of the characteristic is different from the first value and the second value.

In some embodiments, the characteristic of the voice indicator (e.g., 1010B) (e.g., the digital assistant uses a word to provide confirmation) is a term (e.g., the word, name) corresponding to the user associated with (e.g., providing) the voice user input request (e.g., 1024A, 1024B).

Using the user's name (e.g., 1020, 1030) in the digital assistant's voice confirmation indicator (e.g., 1010C) allows the digital assistant to provide feedback to confirm that the digital assistant has identified the specific user (e.g., 1020, 1030) issuing the command. Providing customized feedback to confirm to the user (e.g., 1020, 1030) improves usability of the digital assistant and makes the user-device interface more efficient (e.g., a specific user (e.g., 1020, 1030) knows that the digital assistant has processed their command (e.g., 1024A, 1024B)). Using the username thereby reduces the cognitive burden on the user (e.g., 1020, 1030) by providing immediate confirmation that the task has been accomplished, and reduces confusion when there are multiple users (e.g., 1020, 1030) speaking simultaneously or other speakers in the background. Additionally, feedback of the digital assistant's state allows users (e.g., 1020, 1030) to use the digital assistant more quickly and efficiently.

In some embodiments, the electronic device (e.g., 1000) determines a user associated with a vocal user input request based on one or more of voice recognition, facial recognition, and direction of the vocal user input request.

The foregoing has been described with reference to specific embodiments for purposes of explanation. However, the exemplary discussion above is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments have been chosen and described in order to best explain the principles of the present technology and its practical application. This will enable others skilled in the art to best utilize the present technology and various embodiments with various modifications as suited to the particular applications intended.

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

As mentioned above, one aspect of the present technology is the collection and use of data available from various sources to better enable a user to control their electronic device. This disclosure contemplates that, in some examples, this collected data may include personal information data that uniquely identifies a particular person or that can be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records regarding a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth date, or any other identifying or personal information.

This disclosure recognizes that the use of such personal information data in the present technology can be used to the benefit of the user. For example, personal information data can be used to personalize device interactions. Thus, the use of such personal information data can allow the user to more easily control their electronic device. Furthermore, other uses of personal information data that benefit the user are also contemplated by this disclosure. For example, health and fitness data can be used to provide insight into the user's overall wellness, or can be used as proactive feedback to individuals using the technology to pursue wellness goals.

This disclosure contemplates that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal information data adhere to robust privacy policies and/or privacy practices. Specifically, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining the strict confidentiality of personal information data. Such policies should be easily accessible to users and should be updated as data collection and/or use changes. Personal information from users should be collected for the entity's lawful and legitimate use and should not be shared or sold except for those lawful uses. Furthermore, such collection/sharing should be carried out after the user's informed consent is obtained. Furthermore, such entities should consider taking all necessary measures to protect and secure access to such personal information data and to ensure that others with access to that personal information data comply with their privacy policies and procedures. Furthermore, such entities may be able to undergo third-party assessments to attest to their adherence to widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal data collected and/or accessed and should comply with applicable laws and standards, including jurisdiction-specific considerations. For example, in the United States, the collection of 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 health data in other countries may be subject to other regulations and policies and should be addressed accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which a user selectively blocks use of or access to personal information data. That is, the present disclosure contemplates that hardware and/or software elements may be provided to prevent or block access to such personal information data. For example, in the case of digital assistants, user gaze, and user profiles, users may be able to "opt in" or "opt out" of participating in the collection of personal information data during registration for the service or at any time thereafter. The technology can be configured to allow a user to choose to opt out. In another example, a user can choose not to provide personal information. In yet another example, a user can choose to limit the period for which personal information is maintained or to completely prohibit the development of a baseline profile. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notice regarding the access or use of personal information. For example, a user may be notified upon downloading an app (e.g., a digital assistant app) that accesses the user's personal data, and then again immediately before the app accesses the user's personal information.

Furthermore, it is the intent of this disclosure that personal information data should be managed and handled in a manner that minimizes the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data when it is no longer needed. Furthermore, where applicable, de-identification of data can be used to protect user privacy in certain health-related applications. De-identification can be facilitated, where appropriate, by removing certain identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data at a city level rather than a street address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.

Thus, while this disclosure broadly encompasses the use of personal information data to implement one or more various disclosed embodiments, this disclosure also contemplates that the various embodiments may be implemented without requiring access to such personal information data. That is, various embodiments of the present technology are not rendered inoperable by the absence of all or part of such personal information data. For example, a user may interact with an electronic device based on non-personal information data or a minimal amount of personal information.