Intelligent device identification

Abstract

Systems and processes for intelligent device identification are provided. In one example process, audio input may be sampled with a microphone at each of two or more of the plurality of electronic devices. A first electronic device of the plurality of electronic devices for determining a task associated with sampled audio input may be identified. The process may determine the task based on the sampled audio input with the first electronic device and identify identifying a second electronic device of the plurality of electronic devices for performing the task. The task be performed with the second electronic device. The second electronic device is not the first electronic device in some examples.

Description

FIELD

This relates generally to multi-device systems and, more specifically, to intelligent identification of devices in multi-device systems.

BACKGROUND

Many contemporary devices offer virtual assistant services to perform various tasks in response to spoken user input. In some circumstances, multiple devices may concurrently operate, for instance, in a shared environment. As a result, a single user input may cause each of the multiple devices to perform a same requested task. This in turn may result in either duplicative or conflicting operation by the devices.

SUMMARY

Systems and processes for intelligent device identification are provided. In one example process, audio input may be sampled with a microphone at each of two or more of the plurality of electronic devices. A first electronic device of the plurality of electronic devices for determining a task associated with sampled audio input may be identified. The process may determine the task based on the sampled audio input with the first electronic device and identify a second electronic device of the plurality of electronic devices for performing the task. The task to be performed with the second electronic device. The second electronic device is not the first electronic device in some examples.

In one example process, data indicative of a task may be received. The task may be associated with an audio input. The process may determine at a first electronic device whether the first electronic device or a second electronic device is to perform the task. In accordance with a determination that the task is associated with the first electronic device, the task may be performed by the first electronic device. In accordance with a determination that the task is associated with the second electronic device, data indicative of the task may be caused to be transmitted to the second electronic device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating a multifunction device with a touch-sensitive display in accordance with some embodiments of the disclosure.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments of the disclosure.

FIG. 2 illustrates a multifunction device having a touch screen in accordance with some embodiments of the disclosure.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments of the disclosure.

FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIGS. 5A-5B illustrate block diagrams of exemplary architectures for devices according to some embodiments of the disclosure.

FIG. 6A-6F illustrate a plurality of electronic devices according to various examples.

FIGS. 7A-7C illustrate a plurality of electronic devices according to various examples.

FIGS. 8A-8E illustrate a process for identifying an electronic device to perform a task according to various examples.

FIGS. 9A-9C illustrate a process for identifying an electronic device to perform a task according to various examples.

FIG. 10 illustrates a functional block diagram of an electronic device according to various examples.

DETAILED DESCRIPTION

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

Virtual assistant services may be provided by any number of devices of a user. For example, a user may simultaneous use a mobile device and a wearable device, each of which may provide respective virtual assistant services. Because a user may request one or more devices perform a task while using and/proximate multiple devices, there is a need for intelligent device identification of devices for performing respective tasks such that user requests are fulfilled intuitively.

Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.

The terminology used in the description of the various described embodiments 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 described embodiments and the appended claims, the singular forms “a”, “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The term “if” may be construed 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 construed 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.

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 communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, 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 may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout 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.

The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

1. Exemplary Devices for Performing Language Input Correction

Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), 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 for detecting intensity of contacts 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 outputs on device 100 (e.g., generating tactile outputs 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 over one or more communication buses or signal lines 103.

As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (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 of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath 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., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” 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 movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

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

Memory 102 may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. The computer-readable storage medium may store instructions for performing processes 800 and 900, described below. Memory 102 may include high-speed random access memory and may also include 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 may control access to memory 102 by other components of device 100.

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

RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the 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, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

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

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

A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.

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

Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 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, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

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

Device 100 optionally also 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 collocated with, or proximate to, a 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 touch screen display 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 may be coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator 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 a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs 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 are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 may be coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 may perform 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 Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, 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: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.

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 for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling 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 coupling directly to other devices or indirectly over 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, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

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

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

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

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

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, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input). In particular, text input module 134 can include one or more geometry models and one or more language models, described below, for language input correction.

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

Applications 136 may include 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;
  • Video conference module 139;
  • E-mail client module 140;
  • Instant messaging (IM) module 141;
  • Workout support module 142;
  • Camera module 143 for still and/or video images;
  • Image management module 144;
  • Video player module;
  • Music player module;
  • Browser module 147;
  • Calendar module 148;
  • Widget modules 149, which may include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
  • Widget creator module 150 for making user-created widgets 149-6;
  • Search module 151;
  • Video and music player module 152, which merges video player module and music player module;
  • Notes module 153;
  • Map module 154; and/or
  • Online video module 155.

Examples of other applications 136 that may be 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 replication.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced 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).

In conjunction with RF circuitry 108, touch screen 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, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

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

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). 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 and a JavaScript file (e.g., Yahoo! Widgets).

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

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

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.

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

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.

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

In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver 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, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.

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 that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). 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 the 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., receiving 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 for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

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

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

Active event recognizer determination module 173 determines which view or views within a 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 include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.

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

In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of 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 (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective 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 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update the 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 data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

A respective 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 delivery instructions 188 (which may include sub-event delivery instructions).

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

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected 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, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

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

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

In some embodiments, event handler(s) 190 includes or has 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 a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs 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 (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with 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 industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 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 remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, 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, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

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

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

FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces may be 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 404;
  • Bluetooth indicator 405;
  • Battery status indicator 406;
  • Tray 408 with icons for frequently used applications, such as:
    • Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages;
    • Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails;
    • Icon 420 for browser module 147, labeled “Browser;” and
    • Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
  • Icons for other applications, such as:
    • Icon 424 for IM module 141, labeled “Messages;”
    • Icon 426 for calendar module 148, labeled “Calendar;”
    • Icon 428 for image management module 144, labeled “Photos;”
    • Icon 430 for camera module 143, labeled “Camera;”
    • Icon 432 for online video module 155, labeled “Online Video;”
    • Icon 434 for stocks widget 149-2, labeled “Stocks;”
    • Icon 436 for map module 154, labeled “Maps;”
    • Icon 438 for weather widget 149-1, labeled “Weather;”
    • Icon 440 for alarm clock widget 149-4, labeled “Clock;”
    • Icon 442 for workout support module 142, labeled “Workout Support;”
    • Icon 444 for notes module 153, labeled “Notes;” and
    • Icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for device 100 and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 may optionally be labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 359 for generating tactile outputs for a user of device 300.

Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs 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). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 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 inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the 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 other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), 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., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes 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 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. As with devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) may have one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches. 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 operations on device 500.

Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, each of which is hereby incorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can 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, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts 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 bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, touch-intensity sensitive component 524. In addition, I/O section 514 can be connected with communication unit 530 for receiving 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 may be a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 may be a button, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personal electronic device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 800 (FIGS. 8A-8E) and 900 (e.g., FIGS. 9A-9C). The computer-executable instructions can also be stored and/or transported within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) may each constitute an affordance.

As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).

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

In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.

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

An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

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

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

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

2. Exemplary Techniques for Intelligent Device Identification

FIGS. 6A-6F illustrate exemplary techniques for intelligent device identification in accordance with some embodiments. These figures are also used to illustrate the processes described below, including the processes in FIGS. 8A-8E and FIGS. 9A-9C.

FIG. 6A illustrates electronic device 602, 604, 606, and 608 of user 600. One or more of the devices 602-608 may be any of devices 104, 122, 200, 400, and 1000 (FIGS. 1, 2, 4, and 10) in some embodiments. In some examples, the electronic device 602 is a wearable electronic device, such as a smart watch, and is powered off when in a lowered position, as illustrated. In some examples, the electronic device 604 is a mobile device, such as a mobile phone, the electronic device 606 is an electronic device having relatively large display capabilities, such as a television, and the electronic device 608 is a device having auditory output capabilities, such as a speaker dock. While the illustrated example is described herein with reference to electronic devices 602-608, it will be appreciated that a fewer or greater number of devices may be used in other implementations.

FIG. 6B illustrates user 600 lifting the electronic device 602 into a raised position. In response to the movement, device 602 powers on a touch screen of the electronic device 602. In accordance with the touch screen of the electronic device 602 powering on, electronic device 602 also begins to sample audio input through its microphone to listen for spoken input from user 600. One or more other electronic devices, such as the electronic devices 604, 606, and 608, may also begin to sample audio input to listen for spoken input from user 600. Each of the electronic devices 604, 606, and 608 may begin to sample audio input for instance, in response to detecting proximity of user 600 or may continuously sample audio input.

As illustrated, user 600 provides spoken instructions 612 while one or more of the electronic devices 602-608 is sampling audio input. Each electronic device 602-608 detects spoken instruction 612 while sampling audio input and determines whether the spoken instruction 612 contains a phrase for triggering a virtual assistant service of the respective device. For each of the electronic devices 602-608, if the sampled input is determined to contain a spoken trigger, the virtual assistant is triggered. Optionally, an output indicating that the sampled audio input includes a spoken trigger may also be provided. The output may be visual (e.g., a display notification or LED toggle), auditory, or haptic. If the sampled audio input is determined to not contain the spoken trigger, audio input may be further sampled for a predetermined amount of time or indefinitely.

In the illustrated example, the spoken trigger is the phrase “Hey Siri.” Thus, spoken instruction 612 triggers a respective virtual assistant in each electronic device sampling the spoken instruction 612. In addition to the spoken trigger, the spoken instruction 612 includes a natural language input (e.g., “give me a TV episode”) that at least one of the virtual assistants of the respective devices resolves (e.g., operationalizes) into one or more tasks.

In some examples, natural language inputs are resolved into one or more tasks by a single device of the electronic devices 602-608. For example, once the spoken audio input has been sampled, one of the electronic devices 602-608 may be identified as a first device used to determine the task based on the sampled audio input. The first device used to determine the task may, for instance, be identified based a set of prioritization rules. By way of example, the first device may be the device whose sampled audio input has the greatest quality of speech, sound pressure level, and/or volume. In another example, the first device may be the device closest to the user 600. In yet another example, the first device may be identified based on a type of the respective devices. For instance, in a system including a mobile device and other non-wearable devices, the mobile device may be the first device used to determine the task. In a system including a wearable device, the wearable device may be the first device used to determine the task. Accordingly, in the illustrated example, the device 602 may be identified as a device for determining the task based on the sampled audio input.

Tasks may be determined locally or remotely. A device, such as the electronic device 602, may locally determine the task using the sampled audio input or may transmit data representing the sampled audio input to one or more servers. The task may be determined by the one or more servers based on the transmitted data and provided to the device. Optionally, one or more devices may provide an output after the task has been determined. With reference to FIGS. 6C-6F, any of the electronic devices 602-608, respectively, may provide an output acknowledging the task has been determined. In some examples, multiple devices provide an output after the task has been determined. The manner in which the output is provided may, for instance, indicate which of the devices was used to determine the task.

Once the task has been determined, one of the electronic devices 602-608 may be identified as a second device used to perform the task. The second device may be identified by the first device and further may be the first device or a device other than the first device. In some examples, the second device may be identified based on task requirements. A task may require, for instance, that the task be performed by a device having a particular capability (e.g., functionality). In the illustrated example, for instance, the task may be directed to playback of an episode of a TV program and require display capability. Accordingly, the electronic device 602 may determine which of the electronic devices 602-608 satisfies the display capability requirement. In other embodiments, a task may require it be performed with a mobile device. In yet other embodiment, a task may require it be performed with a device plugged into an electrical outlet. If a requirement of a task cannot be satisfied by any of the electronic devices 602-608, one or more of the devices 602-608 may forego performing the task.

Because multiple devices may satisfy a task requirement, the second device may additionally or alternatively be identified in accordance with a plurality of prioritization rules. In some examples, the second device may be a device “best suited” to perform the task. For tasks directed to video playback, for instance, the second device may be an electronic device having a largest display. In the illustrated example, the electronic device 602 may determine that the electronic device 606 is best suited for video playback, for instance, based on relative display sizes of the electronic devices 602-606. For tasks directed to mapping functions, the second device may be a mobile device. In some examples, the second device may be identified based on prior use. For example, the device typically used to perform a task may be identified to perform subsequent iterations of the task or similar tasks. In some embodiments, the second device may be identified based on signal strength between the first device and each of the other devices.

Once the second device has been identified, the task may be provided to the second device by the first device. As illustrated in FIG. 6C, responsive to the sampling of audio input containing instruction 612, electronic device 602 provides the task to the electronic device 606, which in turn performs the task by playing the requested episode. In some examples, the task is provided from the device 602 to the device 606 directly and in other examples is provided via one or more intermediary devices, such as the device 604. Once the task has been received by the second device, the second device may perform the task.

In some examples, the second device may delay performance of the task. A task may, for instance, include one or more criteria that must be satisfied prior to the task being performed. A task may require a user cease driving (e.g., as determined by GPS) prior to the task being performed, and/or may require a particular form of connectivity (e.g., Bluetooth) prior to the task being performed, for example.

As another example, a task may require that a user be authenticated prior to the task being performed. With reference to FIG. 7A, a user may provide audio input 702 requesting playback of an R-rated movie and the request may be resolved into a task, for instance, by the device 602, for playback of an R-rated movie on the electronic device 606. Because of the nature of the movie's rating, the task may first require that the user be authenticated. Authentication may be implemented using biometric authentication (e.g., fingerprint authentication) and/or credential authentication (e.g., username and password). With reference to FIG. 7B, the device 604 may provide input requests 712, 714 requesting input of biometric input (e.g., touch ID), respectively. As illustrated in FIG. 7C, the user may provide a biometric input and the device 604 may authenticate the user. In some examples, the device 604 may provide outputs 722, 724 respectively acknowledging completion of authentication and that the R-rated movie is being played on the device 606. It will be appreciated that authentication may be employed using any of the electronic devices 602-608 including but not limited to those devices used to resolve and/or perform tasks.

3. Processes for Identifying an Electronic Device to Perform a Task

FIGS. 8A-8E illustrate a process for identifying an electronic device to perform a task according to various examples. In some examples, process 800 can be employed using a digital assistant, for instance, implemented on one or more electronic devices. In some examples, process 800 can be performed using a client-server system (e.g., system 100) implementing a digital assistant. It should be recognized that in other examples, the individual blocks of process 800 can be distributed in any appropriate manner among one or more computers, systems, or electronic devices. For instances, in some examples, process 800 can be performed entirely on an electronic device (e.g., devices 104, 200, 400). Further, while the following discussion describes process 800 as being performed by a digital assistant system (e.g., system 100), it should be recognized that the process or any particular part of the process is not limited to performance by any particular device, combination of devices, or implementation.

At block 802, audio input can be sampled at each of two of more of a plurality of electronic devices (e.g., device 104, 200, 400). In particular, the audio input can be received from a user of the plurality of electronic devices. The audio input can be received in the course of, or as part of, an interaction with a respective or same digital assistant implemented on each of the plurality of electronic devices. In some examples, the audio input can be received via a microphone (e.g., microphone 113) of the electronic device. The received audio input can be processed (e.g., using audio circuitry 210 or processor(s) 220) and converted into a representative form such as, for example, an electronic signal (digital or analog) or one or more audio files.

In some examples, the audio input can represent and/or contain a user request. For example, the audio input may include the request “Play the latest episode of Game of Thrones,” thereby requesting playback of the most recent episode of the television show Game of Thrones. Further, in some examples, the audio input may not explicitly contain a user request, but rather the user request can be implied based on the context in which the audio input is received. In particular, the user request can be implied based on the input field and/or application to which the audio input is directed. For example, while focus is currently directed to the search field of the maps application the audio input can include the word “restaurant”. In this example, the audio input can represent a user request to obtain location information of restaurants in a particular geographic area.

It should be recognized that in some examples, text input can be received at block 802 instead of audio input. For example, text input representing a user request can be received from the user via a suitable user interface on one or more of the plurality of electronic devices. Examples of suitable user interfaces for receiving text input can include a virtual keyboard, a handwriting recognition interface, a gesture recognition interface, and the like.

In some examples, sampling the audio input at the block 802 may include determining whether the audio input comprises a spoken trigger. A spoken trigger may include any predetermined keyword, phrase, or other spoken input that triggers one or more electronic devices of the plurality of electronic devices to analyze subsequent input for a user request. For example, the spoken trigger may include the phrase “Hey Siri.” In response, each of the electronic devices may sample subsequent audio input. In some examples, an output may be provided acknowledging the sampling of the audio output. The output may, for instance, be provided in accordance with a determination that the audio input comprises a spoken trigger.

At block 806, a first electronic device of the plurality of electronic devices for determining a task associated with sampled audio input may be identified. In some examples, an electronic device is identified based on the quality of speech received by the device. Quality of speech may vary, for instance, based on distance between the user and each of the plurality electronic devices and/or one or more other acoustic characteristics of the environment in which the plurality of electronic devices operate. In an example in which the plurality of devices includes a mobile phone and a television, the mobile phone may be identified in the event that the mobile phone is closer to the user. In some examples, identifying the first electronic device includes determining the respective quality of speech in the audio input sampled at each of the two or more electronic devices. Quality of speech may, for instance, be determined based on acoustic environmental noise, minimum volume, maximum volume, volume variance, frequency, or a combination thereof.

Devices may further be identified based on a predetermined set of prioritization rules specifying which types of electronic devices are to be prioritized over other types. For instance, in some examples, identifying the first electronic device includes determining whether the two or more electronic devices include a wearable electronic device (e.g., smart watch). If so, the wearable electronic device is identified as the first electronic device.

In some examples, identifying the first electronic device includes determining the respective sound pressure levels of the sampled audio input at each of the two or more electronic devices. The electronic device identified as having the highest sound pressure level may be identified as the first electronic device.

At block 818, a task may be determined based on the sampled audio input. The task may be determined by the first electronic device in some examples. In at least one embodiment, the first electronic device resolves the audio input into a task locally. That is, the audio input is resolved on the first electronic device. In other embodiments, the audio input is resolved remotely. The first electronic device may, for instance, communicate with a service, such as a cloud-based virtual assistance service, and provide the audio input to the service which in turn may resolve the audio input into a task. The task may thereafter be provided by the service to the first electronic device. Example tasks may include, but are not limited to, any number of playback, mapping, lookup, and storing functions.

In some examples, after the audio input has been sampled, an output may be provided acknowledging that the task has been determined based on the sampled audio input. The output may be provided by one or more of the electronic devices and may be a visual, auditory, and/or haptic output. In some examples, the output serves as an acknowledgment that the user's audio input has been received. In some examples, the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device. By way of example, the user may speak into a wearable electronic device and another device, such as a speaker dock, may output audio reciting “I'm playing your playlist now.” In some examples, the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device sampling and/or resolving the audio input and a second electronic device performing the task. By way of example, the user may speak into a first electronic device (e.g., mobile phone), and a wearable electronic device of the user (e.g., smart watch) may provide an output, such as vibration indicating that the task is being provided to a third device (e.g., television).

In some examples, a first output may be provided acknowledging the sampling of audio input and after the audio input has been sampled, a second output may be provide indicating that the task has been determined based on the sampled audio input. The first and second outputs have different characteristics in some examples. The first output may be provided by the two or more electronic devices in some examples. For instance, in some embodiments, multiple electronic devices of the plurality of electronic devices provide relatively less perceptible indication, such as the lighting of an LED, that audio input is being sampled, while a particular electronic devices provide relatively more perceptible indication that sampled audio input is resolved, such as an auditory (e.g., verbal) indication. In this manner, the user is made aware that one or more electronic devices are processing the audio input, but a select electronic device provides acknowledgment that the task is to be performed based on the audio input.

At block 824, a second electronic device for performing the task may be identified. The second electronic device may, for instance, be identified by the first electronic device, by another electronic device of the plurality of devices, and/or by a service used to resolve the audio input (block 818).

In some examples, identifying the second electronic device includes determining signal strength of a wireless communication (e.g., Bluetooth, Bluetooth LE, WiFi) between the first electronic device and one or more other electronic devices of the plurality of electronic devices. Signal strength may be measured using signal reliability and/or data throughput, for instance. The electronic device having the highest signal strength may be identified as the second electronic device.

In some examples, the second electronic device may be identified by obtaining an indication of a display screen size of an electronic device of the plurality of electronic devices. A determination whether the indication meets a requirement of the task may then be made. For example, it may be determined whether the task requires a screen size greater than a threshold size or less than a threshold size. The electronic device may be identified as the second electronic device in accordance with a determination that the indication meets the requirement. For example, the first electronic device may identify the electronic device as the second electronic device. The electronic device may not be identified as the second electronic device in accordance with a determination that the indication does not meet the requirement. For example, the first electronic device may forego identification of the electronic device as the second electronic device.

In some examples, the second electronic device may be identified by determining whether an electronic device of the plurality of electronic devices is a mobile electronic device. In some examples, a mobile device may be any device that is battery-powered. The electronic device may be identified as the second electronic device in accordance with a determination that the electronic device is a mobile device. For example, the first electronic device may identify the electronic device as the second electronic device. The electronic device may not be identified as the second electronic device in accordance with a determination that the electronic device is not a mobile device. For example, the first electronic device may forego identification of the electronic device as the second electronic device.

In some examples, the second electronic device may be identified by determining whether an electronic device of the plurality of electronic devices is being powered by an electrical outlet. The electronic device may be identified as the second electronic device in accordance with a determination that the electronic device is being powered by an electrical outlet. For example, the first electronic device may identify the electronic device as the second electronic device. The electronic device may not be identified as the second electronic device in accordance with a determination that the electronic device is not being powered by an electrical outlet. For example, the first electronic device may forego identification of the electronic device as the second electronic device.

In some examples, the second electronic device may be determined based on the task. For instance, as described, the task may specify one or more requirements and an electronic device best suited for performing the task in accordance with the specified one or more requirements may be selected. By way of example, a task may require use of mapping services and accordingly, a device having cellular and/or Internet connectivity, such as a mobile phone, may be determined.

At block 868, the task may be performed, for instance, using the second electronic device. The second electronic device is not the first electronic device in some examples.

Optionally, prior to performing the task with the second electronic device, the user is prompted for input. Input provided in this manner may include biometric input and/or input of a password or other credential. In some examples, prompted input may be received using a biometric sensor, such as a fingerprint reader. After receiving the prompted input, the second electronic device performs the task. In some examples, a third electronic device of the plurality of electronic devices is identified. The third electronic device may have an input interface configured to detect the prompted input.

Optionally, performance of the task may be delayed until a criterion is met. The delay may be performed by the second electronic device in some examples. Criteria relied on in this manner may include criteria directed to user activity and/or a state of one or more electronic devices. For example, a first criterion may require that a user has stopped driving as determined by GPS coordinates and a second criterion may include Bluetooth connectivity. In some examples, an output providing the criteria for performing the task may be provided, for instance, by the second electronic device. The output providing the criteria may be visual, auditory, and/or haptic.

FIGS. 9A-9C illustrate a process for identifying an electronic device to perform a task according to various examples. In some examples, process 900 can be employed using a digital assistant, for instance, implemented on one or more electronic devices. In some examples, process 900 can be performed using a client-server system (e.g., system 100) implementing a digital assistant. It should be recognized that the individual blocks of process 900 can be distributed in any appropriate manner among one or more computers, systems, or electronic devices. For instances, in some examples, process 900 can be performed entirely on an electronic device (e.g., devices 104, 200, 400). Further, while the following discussion describes process 900 as being performed by a digital assistant system (e.g., system 100), it should be recognized that the process or any particular part of the process is not limited to performance by any particular device, combination of devices, or implementation.

At block 902, data indicative of a task may be received at a first electronic device (e.g., device 104, 200, 400). Data indicative of the task may be data representative of a task, data corresponding to a task, data associated with a task and/or data from which a task may otherwise be derived. Data indicative of the task may be received from a user of the first electronic device. In some examples, the data indicative of the task can be received in the course of, or as part of, an interaction with a respective or same digital assistant implemented on the first electronic device. In some embodiments, the task is resolved locally and in other embodiments is resolved remotely (e.g., server-side). Tasks include, but are not limited to, any number of playback, mapping, lookup, and storing functions. The task is associated with an audio input in some examples. The audio input may comprise a speaking trigger (e.g., “Hey Siri”) and/or one or more user requests or commands.

In some examples, receiving data indicative of the task includes receiving the audio input via a microphone (e.g., microphone 113) of the first electronic device. The received audio input can be processed (e.g., using audio circuitry 210 or processor(s) 220) and converted into a representative form such as, for example, an electronic signal (digital or analog) or one or more audio files. In response to receipt of the audio input, the data indicative of the task may be generated based on the received audio input. The data indicative of the task may be generated by the first electronic device.

In some examples, receiving data indicative of the task includes receiving the audio input via a microphone (e.g., microphone 113) of the first electronic device. Data representing the received audio input may be provided (e.g., transmitted) to one or more servers, and data indicative of the task may be received from the one or more servers. In some examples, the task is determined by the one or more servers based on the data representing the received audio input.

It should be recognized that in some examples, text input can be received at block 902 instead of audio input. For example, text input representing a user request can be received from the user via a suitable user interface on one or more of the plurality of electronic devices. Examples of suitable user interfaces for receiving text input can include a virtual keyboard, a handwriting recognition interface, a gesture recognition interface, and the like.

At block 914, a determination is made whether the first electronic device or a second electronic device is to perform the task. The determination is made with the first electronic device in some examples.

In some examples, determining whether the first electronic device or second electronic device is to perform the task includes determining whether the task is associated with the first electronic device or the second electronic device in accordance with a plurality of prioritization rules. Prioritization rules may be task-specific and/or device-specific in some examples. For instance, prioritization rules may specify which devices are to perform respective tasks based on type, capabilities, and/or use (e.g., recency of use, frequency of use, tasks performed during use) of each electronic device. Determining whether the task is associated with the first electronic device or the second electronic device in accordance with a plurality of prioritization rules may include determining whether the task is associated with the first electronic device or the second electronic device based on a display capability of the first electronic device, mobility of the first electronic device, or combination thereof. The electronic device having the larger display may be determined as the electronic device to perform the task. In another example, this determination may include determining whether the task is associated with the first electronic device or the second electronic device based on prior use of the first and second electronic devices. The electronic device most recently used may be determined as the electronic device to perform a task, or the electronic device most recently performing a particular task may be determined as the electronic device to perform the task.

At block 922, the task may be performed with the first electronic device in accordance with a determination that the task is associated with the first electronic device.

In some examples, performing the task with the first electronic device includes performing a first task associated with a first user and a second task associated with a second user different than the first user may be performed. For example, the first electronic device may perform playback of a song for the first user and provide directions to a restaurant for a second user.

In some examples, performing the task with the first electronic device includes authenticating a user associated with the first electronic device. The first electronic device may authenticate the user using one more credentials, such as a username and password or a numerical key. In at least one embodiment, authenticating a user with the first electronic device includes receiving a biometric input (e.g., fingerprint). Responsive to authenticating the user, the task is performed.

At block 932, data indicative of the task is caused to be transmitted to the second electronic device in accordance with a determination that the task is associated with the second electronic device. For example, causing data to be transmitted in this manner may include providing data indicative of the task to a third electronic device using the second electronic device or may include causing another electronic device to provide data indicative of the task to the third electronic device.

4. Additional Exemplary Electronic Devices

The operations described above with reference to FIGS. 8A-E can be optionally implemented by components depicted in FIGS. 1, 2A, 4, 6A-B, 7A. For example, sampling operation 802, identifying operations 806 and 824, determining operation 818, and performing operation 868 are, optionally implemented by I/O processing module 728, STT processing module 730, natural language processing module 732, and task flow processing module 736. I/O processing module 728 can received a speech input representing a user request and can receive metadata associated with the speech input. STT processing module 730 can determine a text string corresponding to the speech input. Natural language processing module 732 can determine, based on the metadata, whether to perform natural language processing on the text string. In response to determining that natural language processing is to be performed on the text string, natural language processing module 732 can further determine whether the metadata identifies one or more domains corresponding to the user request. In response to determining that the metadata identifies one or more domains corresponding to the user request, natural language processing module 732 can generate, using the text string and based on the one or more domains, a structured query representing an actionable intent associated with the one or more domains. Task flow processing module 736 can execute a task flow associated with the structured query. Task flow processing module 736 can determine whether a result satisfying the user request is obtained from executing the task flow. In response to determining that a result satisfying the user request is obtained from executing the task flow, I/O processing module 728 can output data content containing the result.

In another example, rece sampling operation 802, identifying operations 806 and 824, determining operation 818, and performing operation 868 are, optionally implemented by digital assistant client module 229 and applications 236. Digital assistant client module 229 can receive from microphone 213 a speech input representing a user request. Digital assistant client module 229 can transmit, using RF circuitry 208, the speech input and metadata associated with the speech input. The metadata can identify one or more domains of an ontology and the one or more domains correspond to the user request. Digital assistant client module can receive, using RF circuitry 208, data content in furtherance of satisfying the user request. The data content can be derived from the speech input. Digital assistant client module 229 can determine whether the data content satisfies the user request. In response to determining that the data content satisfies the user request, digital assistant client module 229 and applications 236 can output a result based on the data content.

FIG. 10 shows a functional block diagram of electronic device 1000 configured in accordance with the principles of the various described examples. The functional blocks of the device can be optionally implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 10 can be optionally combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination, separation, or further definition of the functional blocks described herein.

As shown in FIG. 10, electronic device 1000 can include microphone 1002 and processing unit 1008 coupled to microphone 1002. In some examples, processing unit 1008 can include receiving unit 1010, determining unit 1012, performing unit 1014, causing unit 1016, and optionally, providing unit 1018, generating unit 1020, transmitting unit 1022, and authenticating unit 924.

Processing unit 1008 is configured to receive (e.g., with receiving unit 1010), at a first electronic device, data indicative of a task, where the task is associated with an audio input; determine (e.g., with the determining unit 1012), with the first electronic device, whether the first electronic device or a second electronic device is to perform the task; in accordance with a determination that the task is associated with the first electronic device, perform (e.g., with the performing unit 1014) the task with the first electronic device; and in accordance with a determination that the task is associated with the second electronic device, cause (e.g., with the causing unit 1016) data indicative of the task to be transmitted to the second electronic device.

In some examples, causing the data indicative of the task to be provided to a second electronic device comprises providing (e.g., with the providing unit 1018) data indicative of the task to a third electronic device.

In some examples, receiving comprises receiving, at the microphone 1002, the audio input and in response to receipt of the audio input, generating (e.g., with the generating unit 1020), with the first electronic device, the data indicative of the task based at least in part on the received audio input.

In some examples, receiving comprises receiving, at the microphone 1002, the audio input; transmitting (e.g., with the transmitting unit 1022) data representing the received audio input to one or more servers; and receiving (e.g., with the receiving unit 1010) from the one or more servers the data indicative of the task, where the task was determined by the one or more servers based on the data representing the received audio input.

In some examples, determining comprises determining (e.g., with the determining unit 1012) whether the task is associated with the first electronic device or the second electronic device in accordance with a plurality of prioritization rules.

In some examples, determining whether the task is associated with the first electronic device or the second electronic device in accordance with a plurality of prioritization rules comprises determining (e.g., with the determining unit 1012) whether the task is associated with the first electronic device or the second electronic device based on a display capability of the first electronic device, mobility of the first electronic device, or combination thereof.

In some examples, determining whether the task is associated with the first electronic device or the second electronic device in accordance with a plurality of prioritization rules comprises determining (e.g., with the determining unit 1012) whether the task is associated with the first electronic device or the second electronic device based on prior use of the first and second electronic devices.

In some examples, performing the task with the first electronic device comprises performing (e.g., with the performing unit 1014) a first task associated with a first user and wherein the processing unit is further configured to perform (e.g., with the performing unit 1014), with the first electronic device, a second task associated with a second user different from the first user.

In some examples, performing the task with the first electronic device comprises authenticating (e.g., with the authenticating unit 1024) a user associated with the first electronic device; and responsive to authenticating the user, performing (e.g., with the performing unit 1014) the task.

In some examples, authenticating the user comprises receiving (e.g., with the receiving unit 1010) a biometric input.

The operations described above with reference to FIGS. 9A-C can be optionally implemented by components depicted in FIG. 1, 2A, 4, 6A-B, 7A, or 10. For example, receiving operation 902, determining operation 914, performing operation 922, and causing operation 932 are, optionally implemented by I/O processing module 728, STT processing module 730, natural language processing module 732, and task flow processing module 736. I/O processing module 728 can received a speech input representing a user request and can receive metadata associated with the speech input. STT processing module 730 can determine a text string corresponding to the speech input. Natural language processing module 732 can determine, based on the metadata, whether to perform natural language processing on the text string. In response to determining that natural language processing is to be performed on the text string, natural language processing module 732 can further determine whether the metadata identifies one or more domains corresponding to the user request. In response to determining that the metadata identifies one or more domains corresponding to the user request, natural language processing module 732 can generate, using the text string and based on the one or more domains, a structured query representing an actionable intent associated with the one or more domains. Task flow processing module 736 can execute a task flow associated with the structured query. Task flow processing module 736 can determine whether a result satisfying the user request is obtained from executing the task flow. In response to determining that a result satisfying the user request is obtained from executing the task flow, I/O processing module 728 can output data content containing the result.

In another example, receiving operation 902, determining operation 914, performing operation 922, and causing operation 932 are, optionally implemented by digital assistant client module 229 and applications 236. Digital assistant client module 229 can receive from microphone 213 a speech input representing a user request. Digital assistant client module 229 can transmit, using RF circuitry 208, the speech input and metadata associated with the speech input. The metadata can identify one or more domains of an ontology and the one or more domains correspond to the user request. Digital assistant client module can receive, using RF circuitry 208, data content in furtherance of satisfying the user request. The data content can be derived from the speech input. Digital assistant client module 229 can determine whether the data content satisfies the user request. In response to determining that the data content satisfies the user request, Digital assistant client module 229 and applications 236 can output a result based on the data content.

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

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

Claims

1. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to: receive, at a first electronic device, data indicative of a task, wherein the task is associated with an audio input;determine, by the first electronic device, a display size requirement for the task;identify, by the first electronic device, a second electronic device from a plurality of electronic devices based on a display size of the second electronic device and the display size requirement, wherein identifying the second electronic device includes determining that the display size of the second electronic device meets the display size requirement;determine, by the first electronic device, that a display size of the first electronic device meets the display size requirement;in response to a determination that both the display size of the first electronic device and the display size of the second electronic device meet the display size requirement, determine, with the first electronic device and based on one or more rules of a plurality of prioritization rules, whether the first electronic device or the second electronic device is to perform the task, wherein the one or more rules of the plurality of prioritization rules are based on a display size of the first electronic device and the display size of the second electronic device;in accordance with a determination that the task is to be performed by the first electronic device based on the display size of the first electronic device, the display size of the second electronic device and the display size requirement for the task: perform the task with the first electronic device; andprovide, with the first electronic device, a first audio output including an indication of the task and an indication of the first electronic device;in accordance with a determination that the task is to be performed by the second electronic device based on the display size of the first electronic device, the display size of the second electronic device and the display size requirement for the task: cause data indicative of the task to be transmitted to the second electronic device; andprovide, with the first electronic device, a second audio output including the indication of the task and an indication of the second electronic device.

2. The non-transitory computer-readable storage medium of claim 1, wherein causing the data indicative of the task to be provided to a second electronic device comprises: providing data indicative of the task to a third electronic device.

3. The non-transitory computer-readable storage medium of claim 1, wherein receiving comprises: receiving, at a microphone of the first electronic device, the audio input; andin response to receipt of the audio input, generating, with the first electronic device, the data indicative of the task based at least in part on the received audio input.

4. The non-transitory computer-readable storage medium of claim 1, wherein receiving comprises: receiving, at a microphone of the first electronic device, the audio input;transmitting data representing the received audio input to one or more servers; andreceiving from the one or more servers the data indicative of the task, wherein the task was determined by the one or more servers based on the data representing the received audio input.

5. The non-transitory computer-readable storage medium of claim 1, wherein one or more rules of the plurality of prioritization rules are based on prior use of the first electronic device and the second electronic device.

6. The non-transitory computer-readable storage medium of claim 1, wherein performing the task with the first electronic device comprises performing a first task associated with a first user, and wherein the instructions, which when executed by the one or more processors of the electronic device, further cause the electronic device to: perform, with the first electronic device, a second task associated with a second user different from the first user.

7. The non-transitory computer-readable storage medium of claim 1, wherein performing the task with the first electronic device comprises: authenticating a user associated with the first electronic device; andresponsive to authenticating the user, performing the task.

8. The non-transitory computer-readable storage medium of claim 7, wherein authenticating the user comprises receiving a biometric input.

9. The non-transitory computer-readable storage medium of claim 1, wherein one or more rules of the plurality of prioritization rules are based on a mobility capability of the first electronic device and a mobility capability of the second electronic device.

10. The non-transitory computer-readable storage medium of claim 1, wherein performing the task with the first electronic device comprises: determining, based on the task, whether user authentication is required to perform the task; andin accordance with a determination that user authentication is required to perform the task: receiving a second input;authenticating a user associated with the first electronic device based on the second input; andin accordance with authenticating the user, performing the task with the first electronic device.

11. The non-transitory computer-readable storage medium of claim 1, wherein the first audio output further includes an indication that the task is to be performed by the first electronic device, and wherein the second audio output further includes an indication that the task is to be performed by the second electronic device.

12. A method of identifying an electronic device from a plurality of electronic devices for performing a task, the method comprising: receiving, at a first electronic device, data indicative of a task, wherein the task is associated with an audio input;determining, by the first electronic device, a display size requirement for the task;identifying, by the first electronic device, a second electronic device from a plurality of electronic devices based on a display size of the second electronic device and the display size requirement, wherein identifying the second electronic device includes determining that the display size of the second electronic device meets the display size requirement;determining, by the first electronic device, that a display size of the first electronic device meets the display size requirement;in response to a determination that both the display size of the first electronic device and the display size of the second electronic device meet the display size requirement, determining, with the first electronic device and based on one or more rules of a plurality of prioritization rules, whether the first electronic device or the second electronic device is to perform the task, wherein the one or more rules of the plurality of prioritization rules are based on a display size of the first electronic device and the display size of the second electronic device;in accordance with a determination that the task is to be performed by the first electronic device based on the display size of the first electronic device, the display size of the second electronic device and the display size requirement for the task: perform the task with the first electronic device; andprovide, with the first electronic device, a first audio output including an indication of the task and an indication of the first electronic device;in accordance with a determination that the task is to be performed by the second electronic device based on the display size of the first electronic device, the display size of the second electronic device and the display size requirement for the task: cause data indicative of the task to be transmitted to the second electronic device; andprovide, with the first electronic device, a second audio output including the indication of the task and an indication of the second electronic device.

13. The method of claim 12, wherein one or more rules of the plurality of prioritization rules are based on prior use of the first electronic device and the second electronic devices.

14. The method of claim 12, wherein performing the task with the first electronic device comprises performing a first task associated with a first user, and wherein the one or more programs further include instructions for: performing, with the first electronic device, a second task associated with a second user different from the first user.

15. The method of claim 12, wherein performing the task with the first electronic device comprises: authenticating a user associated with the first electronic device; andresponsive to authenticating the user, performing the task.

16. The method of claim 15, wherein authenticating the user comprises receiving a biometric input.

17. The method of claim 12, wherein one or more rules of the plurality of prioritization rules are based on a mobility capability of the first electronic device and a mobility capability of the second electronic device.

18. The method of claim 12 wherein performing the task with the first electronic device comprises: determining, based on the task, whether user authentication is required to perform the task; andin accordance with a determination that user authentication is required to perform the task: receiving a second input;authenticating a user associated with the first electronic device based on the second input; andin accordance with authenticating the user, performing the task with the first electronic device.

19. The method of claim 12, wherein the first audio output further includes an indication that the task is to be performed by the first electronic device, and wherein the second audio output further includes an indication that the task is to be performed by the second electronic device.

20. An electronic device, comprising: one or more processors;a memory; andone or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, at a first electronic device, data indicative of a task, wherein the task is associated with an audio input;determining, by the first electronic device, a display size requirement for the task;identifying, by the first electronic device, a second electronic device from a plurality of electronic devices based on a display size of the second electronic device and the display size requirement, wherein identifying the second electronic device includes determining that the display size of the second electronic device meets the display size requirement;determining, by the first electronic device, that a display size of the first electronic device meets the display size requirement;in response to a determination that both the display size of the first electronic device and the display size of the second electronic device meet the display size requirement, determining, with the first electronic device and based on one or more rules of a plurality of prioritization rules, whether the first electronic device or the second electronic device is to perform the task, wherein the one or more rules of the plurality of prioritization rules are based on a display size of the first electronic device and the display size of the second electronic device;in accordance with a determination that the task is to be performed by the first electronic device based on the display size of the first electronic device, the display size of the second electronic device and the display size requirement for the task:perform the task with the first electronic device; andprovide, with the first electronic device, a first audio output including an indication of the task and an indication of the first electronic device;in accordance with a determination that the task is to be performed by the second electronic device based on the display size of the first electronic device, the display size of the second electronic device and the display size requirement for the task:cause data indicative of the task to be transmitted to the second electronic device; andprovide, with the first electronic device, a second audio output including the indication of the task and an indication of the second electronic device.

21. The electronic device of claim 20, wherein one or more rules of the plurality of prioritization rules are based on prior use of the first electronic device and the second electronic devices.

22. The electronic device of claim 20, wherein performing the task with the first electronic device comprises performing a first task associated with a first user, and wherein the one or more programs further include instructions for: performing, with the first electronic device, a second task associated with a second user different from the first user.

23. The electronic device of claim 20, wherein performing the task with the first electronic device comprises: authenticating a user associated with the first electronic device; andresponsive to authenticating the user, performing the task.

24. The electronic device of claim 23, wherein authenticating the user comprises receiving a biometric input.

25. The electronic device of claim 20, wherein one or more rules of the plurality of prioritization rules are based on a mobility capability of the first electronic device and a mobility capability of the second electronic device.

26. The electronic device of claim 20, wherein performing the task with the first electronic device comprises: determining, based on the task, whether user authentication is required to perform the task; andin accordance with a determination that user authentication is required to perform the task: receiving a second input;authenticating a user associated with the first electronic device based on the second input; andin accordance with authenticating the user, performing the task with the first electronic device.

27. The electronic device of claim 20, wherein the first audio output further includes an indication that the task is to be performed by the first electronic device, and wherein the second audio output further includes an indication that the task is to be performed by the second electronic device.